Adapt tests for OpenApi

[netconf.git] / restconf / restconf-openapi / src / test / resources / yang-document / device-string-from-regex.json

diff --git a/restconf/restconf-openapi/src/test/resources/yang-document/device-string-from-regex.json b/restconf/restconf-openapi/src/test/resources/yang-document/device-string-from-regex.json
index 6df0a4ca7e1117105f2872755ce86b4f745faf33..0214953dfe60044df1f507ba775190a92105956a 100644 (file)
--- a/restconf/restconf-openapi/src/test/resources/yang-document/device-string-from-regex.json
+++ b/restconf/restconf-openapi/src/test/resources/yang-document/device-string-from-regex.json
@@ -3,7 +3,7 @@
   "info": {
     "version": "1.0.0",
     "title": "strings-from-regex",
-    "description": "We are providing full API for configurational data which can be edited (by POST, PUT, PATCH and DELETE).\nFor operational data we only provide GET API.\n\nFor majority of request you can see only config data in examples. That’s because we can show only one example\nper request. The exception when you can see operational data in example is when data are representing\noperational (config false) container with no config data in it."
+    "description": "We are providing full API for configurational data which can be edited (by POST, PUT, PATCH and DELETE).\nFor operational data we only provide GET API.\n\nFor majority of request you can see only config data in examples. That is because we can show only one example\nper request. The exception when you can see operational data in example is when data are representing\noperational (config false) container with no config data in it."
   },
   "servers": [
     {