[VNFRQTS] updated heat section of document

Change-Id: I48fbb9da5d3672609d81e971648e9eefd46f482b
Issue-ID: VNFRQTS-516
Signed-off-by: weinstock, alan <aw2574@att.com>

2 files changed, 7 insertions, 7 deletions

diff --git a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst
index b8ad7bc..c68cc56 100644
--- a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst
+++ b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst
@@ -324,7 +324,7 @@ IPv4 and/or IPv6 addresses.
 
     When the VNF's Heat Orchestration Template's Resource
     ``OS::Neutron::Port`` is attaching to an external network (per the
-    ECOMP definition, see Requirement R-57424),
+    ONAP definition, see Requirement R-57424),
     and an IPv4 address is assigned
     using the property ``fixed_ips``
     map property ``ip_address`` and the parameter type is defined as a string,
@@ -431,7 +431,7 @@ Parameter Definition*
 
     When the VNF's Heat Orchestration Template's Resource
     ``OS::Neutron::Port`` is attaching to an external network (per the
-    ECOMP definition, see Requirement R-57424),
+    ONAP definition, see Requirement R-57424),
     and an IPv6 address is assigned
     using the property ``fixed_ips``
     map property ``ip_address`` and the parameter type is defined as a string,
@@ -539,7 +539,7 @@ Definition*
 
     When the VNF's Heat Orchestration Template's Resource
     ``OS::Neutron::Port`` is attaching to an internal network (per the
-    ECOMP definition, see Requirements R-52425 and R-46461),
+    ONAP definition, see Requirements R-52425 and R-46461),
     and an IPv4 address is assigned
     using the property ``fixed_ips``
     map property ``ip_address`` and the parameter type is
@@ -647,7 +647,7 @@ Heat Orchestration Template's Environment File.
 
     When the VNF's Heat Orchestration Template's Resource
     ``OS::Neutron::Port`` is attaching to an internal network (per the
-    ECOMP definition, see Requirements R-52425 and R-46461),
+    ONAP definition, see Requirements R-52425 and R-46461),
     and an IPv6 address is assigned
     using the property ``fixed_ips``
     map property ``ip_address`` and the parameter type is defined as a
diff --git a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/{network-role}.rst b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/{network-role}.rst
index 134c383..e38c135 100644
--- a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/{network-role}.rst
+++ b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/{network-role}.rst
@@ -141,7 +141,7 @@ there is no requirement for ``{network-role}`` / ``{network-role-tag}``
 uniqueness across Heat Orchestration Templates for
 different VNFs.
 
-When an external network is created by ECOMP, the network is also assigned a
+When an external network is created by ONAP, the network is also assigned a
 ``{network-role}``.  The ``{network-role}`` of the network is not required to
 match the ``{network-role}`` of the VNF Heat Orchestration Template.
 
@@ -150,9 +150,9 @@ For example, the VNF Heat Orchestration Template can assign a
 of ``oam`` to a network which attaches to an external network with a
 ``{network-role}`` of ``oam_protected`` .
 
-When the Heat Orchestration Template is on-boarded into ECOMP
+When the Heat Orchestration Template is on-boarded into ONAP
   * each ``{network-role}`` value in the Heat Orchestration Template
-    is mapped to the ``{network-role-tag}`` in the ECOMP
+    is mapped to the ``{network-role-tag}`` in the ONAP
     data structure.
   * each ``OS::Neutron::Port`` is associated with the external network it is
     connecting to, thus creating the VNF Heat Orchestration Template