Adapt tests for OpenApi

[netconf.git] / restconf / restconf-openapi / src / test / resources / yang-document / device-typed-params.json

diff --git a/restconf/restconf-openapi/src/test/resources/yang-document/device-typed-params.json b/restconf/restconf-openapi/src/test/resources/yang-document/device-typed-params.json
index 63f4019493d8f4b9606c3ebfa9d28bff0b2df683..77ff3b4ef864229fb3e668e11a0c6333a28d1132 100644 (file)
--- a/restconf/restconf-openapi/src/test/resources/yang-document/device-typed-params.json
+++ b/restconf/restconf-openapi/src/test/resources/yang-document/device-typed-params.json
@@ -3,7 +3,7 @@
   "info": {
     "version": "1.0.0",
     "title": "typed-params",
-    "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": [
     {