Adapt tests for OpenApi

[netconf.git] / restconf / restconf-openapi / src / test / resources / yang-document / controller-definition-test.json

diff --git a/restconf/restconf-openapi/src/test/resources/yang-document/controller-definition-test.json b/restconf/restconf-openapi/src/test/resources/yang-document/controller-definition-test.json
index d16cd6dd59d3506aba4f29d1fb9fcb5fd9fb81ea..9157d85a222feca682f4bddfca37a47764f4dffc 100644 (file)
--- a/restconf/restconf-openapi/src/test/resources/yang-document/controller-definition-test.json
+++ b/restconf/restconf-openapi/src/test/resources/yang-document/controller-definition-test.json
@@ -3,7 +3,7 @@
   "info": {
     "version": "1.0.0",
     "title": "definition-test",
-    "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": [
     {