Adapt tests for OpenApi

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

diff --git a/restconf/restconf-openapi/src/test/resources/yang-document/device-action-types.json b/restconf/restconf-openapi/src/test/resources/yang-document/device-action-types.json
index 2e1b3bef9acee8efdee9e24592925c47df055e9d..6a1430c25962c4a609c2db0b00a1ecd0de5ae95a 100644 (file)
--- a/restconf/restconf-openapi/src/test/resources/yang-document/device-action-types.json
+++ b/restconf/restconf-openapi/src/test/resources/yang-document/device-action-types.json
@@ -3,7 +3,7 @@
   "info": {
     "version": "1.0.0",
     "title": "action-types",
-    "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": [
     {