[VNFRQTS] correcting typos and RST format issues 79/99279/1
authorweinstock, alan <aw2574@att.com>
Fri, 6 Dec 2019 21:09:40 +0000 (21:09 +0000)
committerweinstock, alan <aw2574@att.com>
Fri, 6 Dec 2019 21:44:47 +0000 (21:44 +0000)
Issue-ID: VNFRQTS-774
Signed-off-by: weinstock, alan <aw2574@att.com>
Change-Id: Ie5b26f0c7da2cd80a1acd81b54bb27775c682b0e
Signed-off-by: weinstock, alan <aw2574@att.com>
docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Contrail Resource Parameters.rst
docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Resource IDs.rst

index 755d88e..9fec122 100644 (file)
@@ -1271,7 +1271,7 @@ ONAP External Networks
     * Parameter name **MAY** use any naming convention.  That is, there is no
       ONAP mandatory parameter naming convention.
     * Parameter **MAY** be declared as type ``string`` or type
-    ``comma_delimited_list``.
+      ``comma_delimited_list``.
 
     And the ``OS::ContrailV2::VirtualMachineInterface`` resource
     **MUST** contain resource-level ``metadata`` (not property-level).
index 8d5c878..518fd2a 100644 (file)
@@ -373,7 +373,7 @@ OS::Neutron::Port
     A VNF's Heat Orchestration Template's Resource ``OS::Neutron::Port``
     that is attaching to an ONAP internal network
     (per the ONAP definition, see Requirements R-52425 and R-46461 and R-35666),
-    the `OS::Neutron::Port`` Resource ID **MUST**
+    the ``OS::Neutron::Port`` Resource ID **MUST**
     use the naming convention
 
     * ``{vm-type}_{vm-type_index}_int_{network-role}_port_{port-index}``
@@ -405,7 +405,7 @@ OS::Neutron::Port
 
     A VNF's Heat Orchestration Template's Resource ``OS::Neutron::Port``
     that is creating a *Reserve Port* with an IPv4 address, the
-    `OS::Neutron::Port`` Resource ID
+    ``OS::Neutron::Port`` Resource ID
     **SHOULD** use the naming convention
 
     * ``reserve_port_{vm-type}_{network-role}_floating_ip_{index}``