VNFRQTS - Fixing '\' usage

Issue-ID: VNFRQTS-696

Signed-off-by: Hagop Bozawglanian <hagop.bozawglanian@att.com>
Change-Id: Ied87d2502cea2e1b29f75ff585efcadf76e6a300

3 files changed, 16 insertions, 20 deletions

diff --git a/docs/Chapter8/Ansible-Playbook-Examples.rst b/docs/Chapter8/Ansible-Playbook-Examples.rst
index 365d41c..6411a66 100644
--- a/docs/Chapter8/Ansible-Playbook-Examples.rst
+++ b/docs/Chapter8/Ansible-Playbook-Examples.rst
@@ -609,8 +609,6 @@ Server via Rest API as part of request:
 .. code-block:: json
 
   {
-
-
     "NodeList": [
         {
             "vnfc_type": "oam",
@@ -643,8 +641,6 @@ Server via Rest API as part of request:
             ]
         }
     ]
-
-
   }
 
 With no names, only IP addresses, template "InventoryNames": "None" (Default)
diff --git a/docs/Chapter8/Chef-JSON-Key-Value-Description.rst b/docs/Chapter8/Chef-JSON-Key-Value-Description.rst
index 4beeefe..400473d 100644
--- a/docs/Chapter8/Chef-JSON-Key-Value-Description.rst
+++ b/docs/Chapter8/Chef-JSON-Key-Value-Description.rst
@@ -95,20 +95,20 @@ Chef Template example:
  "Environment":{
       "name": "HAR",
       "description": "VNF Chef environment for HAR",
-      "json\_class": "Chef::Environment",
-      "chef\_type": "environment",
-      "default\_attributes": { },
-      "override\_attributes": {
-            "Retry\_Time":"50",
+      "json_class": "Chef::Environment",
+      "chef_type": "environment",
+      "default_attributes": { },
+      "override_attributes": {
+            "Retry_Time":"50",
             "MemCache": "1024",
-            "Database\_IP":"10.10.1.5"
+            "Database_IP":"10.10.1.5"
       },
  }
  }
  "Node": {
       "name" : "signal.network.com "
-      "chef\_type": "node",
-      "json\_class": "Chef::Node",
+      "chef_type": "node",
+      "json_class": "Chef::Node",
       "attributes": {
             "IPAddress1": "192.168.1.2",
             "IPAddress2":"135.16.162.5",
@@ -118,10 +118,10 @@ Chef Template example:
       "default": {},
       "normal":{},
       "automatic":{},
-      "chef\_environment" : "\_default"
-      "run\_list": [ "configure\_signal" ]
+      "chef_environment" : "_default"
+      "run_list": [ "configure_signal" ]
       },
-      "NodeList":["node1.vnf\_a.onap.com", "node2.vnf\_a.onap.com"],
+      "NodeList":["node1.vnf_a.onap.com", "node2.vnf_a.onap.com"],
       "PushJobFlag": "True"
       "CallbackCapable":True
       "GetOutputFlag" : "False"
diff --git a/docs/Chapter8/VES_Registraion_3_2.rst b/docs/Chapter8/VES_Registraion_3_2.rst
index cb24b58..8013157 100644
--- a/docs/Chapter8/VES_Registraion_3_2.rst
+++ b/docs/Chapter8/VES_Registraion_3_2.rst
@@ -160,7 +160,7 @@ Filename
 
 YAML file names should conform to the following naming convention:
 
-    ``{AsdcModel}\_{AsdcModelType}\_{v#}.yml``
+    ``{AsdcModel}_{AsdcModelType}_{v#}.yml``
 
 The ‘#’ should be replaced with the current numbered version of the
 file.
@@ -181,11 +181,11 @@ it appears in the the Service Design and Creation Environment).
 
 For example:
 
--  ``vMRF\_Vnf\_v1.yml``
+-  ``vMRF_Vnf_v1.yml``
 
--  ``vMRF\_Service\_v1.yml``
+-  ``vMRF_Service_v1.yml``
 
--  ``vIsbcSsc\_VfModule\_v1.yml``
+-  ``vIsbcSsc_VfModule_v1.yml``
 
 File Structure
 ~~~~~~~~~~~~~~
@@ -2403,7 +2403,7 @@ Syslog
 
 .. code-block:: yaml
 
-    # registration for Syslog\_vMRF
+    # registration for Syslog_vMRF
 
     # Constants: the values of domain, eventName, priority, lastEpochMicrosec, version,
     # syslogFields.syslogFieldsVersion, syslogFields.syslogTag