diff --git a/src/SOL002/General_Definitions/SOL002_def.yaml b/src/SOL002/General_Definitions/SOL002_def.yaml
index 72248da0c6e74105984836303be7cf201e9ff262..73624cb997b43b15ad1c955ab33a4c68e51fa27f 100644
--- a/src/SOL002/General_Definitions/SOL002_def.yaml
+++ b/src/SOL002/General_Definitions/SOL002_def.yaml
@@ -654,14 +654,14 @@ definitions:
       * NOTE 1: The information about the VIM connection referenced by the VIM connection id is known to the VNFM. 
                 Moreover, the identifier of the VIM connection provides scope to the resourceId.
 
-      * NOTE 2:	A link port is not needed for an external CP instance that exposes a VIP CP in the following cases:
-                1)  For a VIP CP directly exposed as an external CP:
-                    1.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD.
-                    1.2)  A dedicated IP address is allocated as VIP address, but the NFVO indicates that no port is needed
+      * NOTE 2:	A link port is not needed for an external CP instance that exposes a virtual IP CP in the following cases:
+                1)  For a virtual IP CP directly exposed as an external CP:
+                    1.1)  No dedicated IP address is allocated as virtual IP address, as indicated in the VNFD.
+                    1.2)  A dedicated IP address is allocated as virtual IP address, but the NFVO indicates that no port is needed
                           (createExtLinkPort in VnfExtCpConfig set to false).
-                2)  For a VIP CP exposed as an external CP via a floating IP address:
-                    2.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD, and the VNFC CP
-                          associated to the VIP CP is also exposed via a floating IP address.
+                2)  For a virtual IP CP exposed as an external CP via a floating IP address:
+                    2.1)  No dedicated IP address is allocated as virtual IP address, as indicated in the VNFD, and the VNFC CP
+                          associated to the virtual IP CP is also exposed via a floating IP address.
                 3)  For a VIRTUAL CP exposed as an external CP.
                 4)  For a VNFC CP exposed as an external CP in a secondary container cluster external network.