diff --git a/src/SOL002/General_Definitions/SOL002_def.yaml b/src/SOL002/General_Definitions/SOL002_def.yaml
index cc85e2c55dd92b2919845448007d431b2d358865..ea4e80c0d67266c162838437780887ccf69f53c6 100644
--- a/src/SOL002/General_Definitions/SOL002_def.yaml
+++ b/src/SOL002/General_Definitions/SOL002_def.yaml
@@ -722,16 +722,16 @@ 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 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
-                          (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.
-                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.
+      * NOTE 2:	 A link port is not needed for an external CP instance that exposes a 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 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.
 
       * NOTE 3: An example of the network attachment definition resource when the container infrastructure service
                 management is a Kubernetes® instance is a network attachment definition (NAD).