diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml
index 08dbadb063302f751dfdf50463db80c290363a35..07fa909d2250a280ba3e1c7af39aebb094878fb8 100644
--- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml
+++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml
@@ -1444,7 +1444,7 @@ paths:
       parameters:
         - name: filter
           description: >
-            Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013.
+            Attribute-based filtering expression according to clause 4.3.2.
             The VNFM shall support receiving this parameter as part of the URI query string.
             The EM/VNF may supply this parameter. All attribute names that appear in the VnfLcmOpOcc
             and in data types referenced from it shall be supported by the VNFM in the filter expression.
@@ -1477,28 +1477,28 @@ paths:
         - name: all_fields
           description: >
             Include all complex attributes in the response.
-            See clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter.
+            See clause 4.3.3 for details. The VNFM shall support this parameter.
           in: query
           required: false
           type: string
         - name: fields
           description: >
             Complex attributes to be included into the response.
-            See clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM should support this parameter.
+            See clause 4.3.3 for details. The VNFM should support this parameter.
           in: query
           required: false
           type: string
         - name: exclude_fields
           description: >
             Complex attributes to be excluded from the response.
-            See clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM should support this parameter.
+            See clause 4.3.3 for details. The VNFM should support this parameter.
           in: query
           required: false
           type: string
         - name: exclude_default
           description: >
             Indicates to exclude the following complex attributes from the response.
-            See clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter.
+            See clause 4.3.3 for details. The VNFM shall support this parameter.
             The following attributes shall be excluded from the VnfLcmOpOcc structure
             in the response body if this parameter is provided, or none of the parameters
             "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
@@ -1513,9 +1513,8 @@ paths:
         - name: nextpage_opaque_marker
           description: >
             Marker to obtain the next page of a paged response.
-            Shall be supported by the VNFM if the VNFM supports 
-            alternative 2 (paging) according to clause 5.4.2.1 
-            of ETSI GS NFV-SOL 013 for this resource.
+            Shall be supported by the VNFM if the VNFM supports alternative 2
+            (paging) according to clause 4.7.2.1 for this resource.
           in: query
           required: false
           type: string
@@ -1524,15 +1523,11 @@ paths:
           description: >
             200 OK
 
-            Status information for zero or more VNF lifecycle management operation 
-            occurrences has been queried successfully.
-            The response body shall contain in an array the status information 
-            about zero or more VNF lifecycle operation occurrences, as defined in 
-            clause 5.5.2.13.
-            If the VNFM supports alternative 2 (paging) according to clause 5.4.2.1 
-            of ETSI GS NFV-SOL 013 for this resource, inclusion of the Link HTTP 
-            header in this response shall follow the provisions in clause 5.4.2.3 
-            of ETSI GS NFV-SOL 013.
+            Status information for zero or more VNF lifecycle management operation occurrences was queried successfully.
+            The response body shall contain in an array the status information about zero or more VNF lifecycle
+            operation occurrences, as defined in clause 5.5.2.13.
+            If the VNFM supports alternative 2 (paging) according to clause 4.7.2.1 for this resource,
+            inclusion of the Link HTTP header in this response shall follow the provisions in clause 4.7.2.3.
           headers:
             Content-Type:
               description: The MIME type of the body of the response.