corrections wording

SOL002/VNFLifecycleManagement-API/CancelOperationTask.robot

@@ -12,8 +12,8 @@ Suite Setup    Check resource existance
 Post Cancel operation task
     [Documentation]    Test ID: 6.3.5.16.1
     ...    Test title: POST Cancel operation task
-    ...    Test objective: The POST method initiates cancelling an ongoing VNF lifecycle operation while it is being executed or rolled back, i.e. the related "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
+    ...    Test objective: The POST method initiates cancelling an ongoing VNF lifecycle operation while it is being executed or rolled back, i.e. the "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
     ...    Reference:  section 5.4.17.3.1 - SOL002 v2.4.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none

SOL002/VNFLifecycleManagement-API/FailOperationTask.robot

@@ -11,7 +11,7 @@ Post Fail operation task
     [Documentation]    Test ID: 6.3.5.15.1
     ...    Test title: Post Fail operation task
     ...    Test objective: The objective is to test that POST method mark as "finally failed" a VNF lifecycle operation if that operation has experienced a temporary failure
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.16.3.1 - SOL002 v2.4.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
@@ -25,7 +25,7 @@ Post Fail operation task Conflict (Not-FAILED_TEMP)
     [Documentation]    Test ID: 6.3.5.15.2
     ...    Test title: Post Fail operation task
     ...    Test objective: The objective is to test that POST method cannot mark as "finally failed" a VNF lifecycle operation if that operation has experienced a temporary failure
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.16.3.1 - SOL002 v2.4.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none

SOL002/VNFLifecycleManagement-API/NotificationEndpoint.robot

@@ -23,7 +23,7 @@ Deliver a notification - Operation Occurence
 Deliver a notification - Id Creation
      [Documentation]    Test ID: 6.3.5.19.2
     ...    Test title: Deliver a notification - Id Creation
-    ...    Test objective: The objective is to test that POST method trigger a notification about the creation of a VNF identifier and the related to a VNF instance resource.
+    ...    Test objective: The objective is to test that POST method trigger a notification about the creation of a VNF instance resource.
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.20.3.1 - SOL005 v2.4.1
     ...    Config ID: Config_prod_NFVO
@@ -34,7 +34,7 @@ Deliver a notification - Id Creation
 Deliver a notification - Id deletion
     [Documentation]    Test ID: 6.3.5.19.3
     ...    Test title: Deliver a notification - Id deletion
-    ...    Test objective: The objective is to test that POST method trigger A notification about the deletion of a VNF identifier and the related to a VNF instance resource
+    ...    Test objective: The objective is to test that POST method trigger A notification about the deletion of a VNF instance resource
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.20.3.1 - SOL005 v2.4.1
     ...    Config ID: Config_prod_NFVO

SOL002/VNFLifecycleManagement-API/RetryOperationTask.robot

@@ -13,7 +13,7 @@ Post Retry operation task
     [Documentation]    Test ID: 6.3.5.13.1
     ...    Test title: Post Retry operation task
     ...    Test objective: The objective is to test that POST method The POST method initiates retrying a VNF lifecycle operation if that operation has experienced a temporary failure
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.14.3.1 - SOL002 v2.4.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
@@ -27,7 +27,7 @@ Post Retry operation task Conflict (Not-FAILED_TEMP)
     [Documentation]    Test ID: 6.3.5.13.2
     ...    Test title: Post Retry operation task
     ...    Test objective: The objective is to test that the retry operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. (i.e. the VNF instance resource is not in FAILED_TEMP state)
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.14.3.1 - SOL002 v2.4.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none

SOL002/VNFLifecycleManagement-API/RollbackOperationTask.robot

@@ -13,7 +13,7 @@ Post Rollback operation task
     [Documentation]    Test ID: 6.3.5.14.1
     ...    Test title: Post Rollback operation task
     ...    Test objective: The objective is to test that POST method The POST method initiates rollback a VNF lifecycle operation if that operation has experienced a temporary failure
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.15.3.1 - SOL002 v2.4.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none
@@ -27,7 +27,7 @@ Post Rollback operation task Conflict (Not-FAILED_TEMP)
     [Documentation]    Test ID: 6.3.5.14.2
     ...    Test title: Post Rollback operation task
     ...    Test objective: The objective is to test that POST method The POST method initiates rollback a VNF lifecycle operation if that operation has experienced a temporary failure
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.15.3.1 - SOL002 v2.4.1
     ...    Config ID: Config_prod_VE
     ...    Applicability: none

SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot

@@ -11,8 +11,8 @@ Library    JSONSchemaLibrary    schemas/
 Post Cancel operation task
     [Documentation]    Test ID: 7.3.1.16.1
     ...    Test title: POST Cancel operation task
-    ...    Test objective: The POST method initiates cancelling an ongoing VNF lifecycle operation while it is being executed or rolled back, i.e. the related "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
+    ...    Test objective: The POST method initiates cancelling an ongoing VNF lifecycle operation while it is being executed or rolled back, i.e. the "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
     ...    Reference:  section 5.4.17.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none

SOL003/VNFLifecycleManagement-API/CancelOperationWorkflow.robot

@@ -16,7 +16,7 @@ Suite Teardown    Terminate All Processes    kill=true
 
 *** Test Cases ***
 Cancel a VNF LCM Operation - STARTING
-    [Documentation]    Test ID: 7.3.1.25
+    [Documentation]    Test ID: 7.3.1.25 
     ...    Test title: Cancel a VNF LCM Operation
     ...    Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation
     ...    Pre-conditions: The VNF lifecycle management operation occurrence is in STARTING state. NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID: 5.4.20.1)
@@ -32,7 +32,7 @@ Cancel a VNF LCM Operation - STARTING
     Check Postcondition VNF Cancel - STARTING
 
 Cancel a VNF LCM Operation - PROCESSING - ROLLING_BACK
-    [Documentation]    Test ID: 7.3.1.2.2
+    [Documentation]    Test ID: 7.3.1.26
     ...    Test title: Cancel a VNF LCM Operation
     ...    Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation
     ...    Pre-conditions: The VNF lifecycle management operation occurrence is in PROCESSING or ROLLING_BACK state. NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID: 5.4.20.1)

SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot

@@ -11,7 +11,7 @@ Library    JSONSchemaLibrary    schemas/
 POST Change external VNF connectivity 
     [Documentation]    Test ID: 7.3.1.10.1
     ...    Test title: POST Change external VNF connectivity
-    ...    Test objective: The objective is to test that POST method trigger a change in VNF external connectivity
+    ...    Test objective: The objective is to test that POST method trigger a change in VNF external connectivity. Supported types of changes that this operation are: 1. Disconnect the external CPs that are connected to a particular external VL, and connect them to a different external VL. 2. Change the connectivity parameters of the existing external CPs, including changing addresses.
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.11.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM

SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityWorkflow.robot

@@ -16,10 +16,10 @@ Suite Teardown    Terminate All Processes    kill=true
 
 *** Test Cases ***
 Operate a VNF Instance
-    [Documentation]    Test ID: 7.3.1.24
+    [Documentation]    Test ID: 7.3.1.27
     ...    Test title: Change the external connectivity of a VNF instance
     ...    Test objective: The objective is to change the external connectivity of a VNF instance.
-    ...    Pre-conditions: VNF instance in INSTANTIATED state (Test ID: 5.a.b.c)
+    ...    Pre-conditions: VNF instance in INSTANTIATED state 
     ...    Reference: section 5.4.11 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: NFVO is able to receive notifications from VNFM. Change the external connectivity of a VNF instance is supported for the VNF (as capability in the VNFD)

SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot

@@ -12,7 +12,7 @@ POST Change deployment flavour of a vnfInstance
     [Documentation]    Test ID: 7.3.1.6.1
     ...    Test title: POST Change deployment flavour of a vnfInstance
     ...    Test objective: The objective is to test that POST method trigger a change in VNF deployment flavour
-    ...    Pre-conditions: none
+    ...    Pre-conditions: VNF instance resource is not in NOT-INSTANTIATED state
     ...    Reference:  section 5.4.7.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none
@@ -24,8 +24,8 @@ POST Change deployment flavour of a vnfInstance
 Change deployment flavour of a vnfInstance Conflict (Not-Instantiated)
     [Documentation]    Test ID: 7.3.1.6.2
     ...    Test title: POST Change deployment flavour of a vnfInstance
-    ...    Test objective: The objective is to test that POST method can't trigger a change in VNF deployment flavour because of a conflict with the state of the VNF instance resource. 
-    ...    Pre-conditions: VNF instance resource is not in NOT-INSTANTIATED state
+    ...    Test objective: The objective is to test that POST method can't trigger a change in VNF deployment flavour because of a conflict with the state of the VNF instance resource. (VNF instance resource is not in NOT-INSTANTIATED state)
+    ...    Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
     ...    Reference:  section 5.4.7.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none
@@ -40,7 +40,7 @@ Change deployment flavour of a vnfInstance Not Found
     [Documentation]    Test ID: 7.3.1.6.3
     ...    Test title: POST Change deployment flavour of a vnfInstance
     ...    Test objective: The objective is to test that POST method can't trigger a change in VNF deployment flavour because the VNF instance resource is not found. 
-    ...    Pre-conditions: VNF instance resource is not in NOT-INSTANTIATED state
+    ...    Pre-conditions: the VNF instance resource is not existing
     ...    Reference:  section 5.4.7.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none

SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourWorkflow.robot

@@ -16,7 +16,7 @@ Suite Teardown    Terminate All Processes    kill=true
 
 *** Test Cases ***
 Change VNF External Connectivity
-    [Documentation]    Test ID: 5.4.7.1
+    [Documentation]    Test ID: 7.3.1.28
     ...    Test title: Change VNF Flavour Workflow
     ...    Test objective: The objective is to test the workflow for a change flavour of an existing VNF instance
     ...    Pre-conditions: VNF instance in INSTANTIATED state (Test ID: 5.4.4.1). NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID: 5.4.20.1)

SOL003/VNFLifecycleManagement-API/FailOperationTask.robot

@@ -12,7 +12,7 @@ Post Fail operation task
     [Documentation]    Test ID: 7.3.1.15.1
     ...    Test title: Post Fail operation task
     ...    Test objective: The objective is to test that POST method mark as "finally failed" a VNF lifecycle operation if that operation has experienced a temporary failure
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.16.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none
@@ -26,7 +26,7 @@ Post Fail operation task Conflict (Not-FAILED_TEMP)
     [Documentation]    Test ID: 7.3.1.15.2
     ...    Test title: Post Fail operation task
     ...    Test objective: The objective is to test that POST method cannot mark as "finally failed" a VNF lifecycle operation if that operation has experienced a temporary failure
-    ...    Pre-conditions: the related "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
+    ...    Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
     ...    Reference:  section 5.4.16.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none

SOL003/VNFLifecycleManagement-API/HealVNFTask.robot

@@ -12,7 +12,7 @@ POST Heal a vnfInstance
      [Documentation]    Test ID: 7.3.1.8.1
     ...    Test title: POST Heal a vnfInstance
     ...    Test objective: The objective is to test that POST method heal a VNF instance
-    ...    Pre-conditions: none
+    ...    Pre-conditions: the VNF instance resource is not in NOT-INSTANTIATED state
     ...    Reference:  section 5.4.9.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none

SOL003/VNFLifecycleManagement-API/HealVNFWorkflow.robot

@@ -19,7 +19,7 @@ Heal a VNF Instance
     [Documentation]    Test ID: 7.3.1.22
     ...    Test title: Heal a VNF Instance
     ...    Test objective: The objective is to heal a VNF instance.
-    ...    Pre-conditions: VNF instance in INSTANTIATED state (Test ID: 5.a.b.c)
+    ...    Pre-conditions: VNF instance in INSTANTIATED state 
     ...    Reference: section 5.4.9 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: NFVO is able to receive notifications from VNFM. Heal a VNF instance is supported for the VNF (as capability in the VNFD)

SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot

 *** Settings ***
 Resource    environment/configuration.txt
-# Suite setup     Expect spec    SOL002-VNFLifecycleManagement-API.yaml
+# Suite setup     Expect spec    SOL003-VNFLifecycleManagement-API.yaml
 Resource    environment/variables.txt 
 Library    REST    ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT}  
 Resource    VnfLcmMntOperationKeywords.robot
@@ -18,7 +18,7 @@ Post Individual VNFInstance - Method not implemented
     ...    Test title: Post Individual VNFInstance - Method not implemented
     ...    Test objective: The objective is to test that POST method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: section 5.4.3.3.1 - SOL002 v2.4.1
+    ...    Reference: section 5.4.3.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 
@@ -30,7 +30,7 @@ Get Information about an individual VNF Instance
     ...    Test title: Get Information about an individual VNF Instance
     ...    Test objective: The objective is to create a new VNF instance resource
     ...    Pre-conditions: none
-    ...    Reference: section 5.4.3.3.2 - SOL002 v2.4.1
+    ...    Reference: section 5.4.3.3.2 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 
@@ -44,7 +44,7 @@ PUT Individual VNFInstance - Method not implemented
     ...    Test title: PUT Individual VNFInstance - Method not implemented
     ...    Test objective: The objective is to test that PUT method is not implemented
     ...    Pre-conditions: none
-    ...    Reference: section 5.4.3.3.3 - SOL002 v2.4.1
+    ...    Reference: section 5.4.3.3.3 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 
@@ -55,8 +55,8 @@ PATCH Individual VNFInstance
      [Documentation]    Test ID: 7.3.1.2.4
     ...    Test title: PATCH Individual VNFInstance
     ...    Test objective: This method modifies an individual VNF instance resource
-    ...    Pre-conditions: none
-    ...    Reference: section 5.4.3.3.4 - SOL002 v2.4.1
+    ...    Pre-conditions: the VNF instance resource is existing
+    ...    Reference: section 5.4.3.3.4 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 
@@ -69,7 +69,7 @@ PATCH Individual VNFInstance Precondition failed
     ...    Test title: PATCH Individual VNFInstance Precondition failed
     ...    Test objective: The objective is to create a new VNF instance resource
     ...    Pre-conditions:  A precondition given in an HTTP request header is not fulfilled. Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity
-    ...    Reference: section 5.4.3.3.4 - SOL002 v2.4.1
+    ...    Reference: section 5.4.3.3.4 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 
@@ -82,7 +82,7 @@ PATCH Individual VNFInstance Conflict
     ...    Test title: PATCH Individual VNFInstance Precondition failed
     ...    Test objective: The objective is to create a new VNF instance resource
     ...    Pre-conditions: none
-    ...    Reference: section 5.4.3.3.4 - SOL002 v2.4.1
+    ...    Reference: section 5.4.3.3.4 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 
@@ -95,8 +95,8 @@ DELETE Individual VNFInstance
      [Documentation]    Test ID: 7.3.1.2.7
     ...    Test title: DELETE Individual VNFInstance
     ...    Test objective: The objective is to delete a VNF instance
-    ...    Pre-conditions: none
-    ...    Reference: section 5.4.3.3.5 - SOL002 v2.4.1
+    ...    Pre-conditions: the VNF instance resource is existing
+    ...    Reference: section 5.4.3.3.5 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 
@@ -108,7 +108,7 @@ DELETE Individual VNFInstance Conflict
     ...    Test title: DELETE Individual VNFInstance
     ...    Test objective: The objective is to verify that The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. 
     ...    Pre-conditions: VNF instance resource is in INSTANTIATED state
-    ...    Reference: section 5.4.3.3.5 - SOL002 v2.4.1
+    ...    Reference: section 5.4.3.3.5 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 
     ...    Post-Conditions: 

SOL003/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot

@@ -7,16 +7,16 @@ Library    JSONSchemaLibrary    schemas/
 Resource    VnfLcmMntOperationKeywords.robot
 
 *** Test Cases ***
-Post Individual VNF LCM OP occurences - Method not implemented
+Post Individual VNF LCM Operation occurences - Method not implemented
     [Documentation]    Test ID: 7.3.1.12.1
-    ...    Test title: Post Individual VNF LCM OP occurences - Method not implemented
+    ...    Test title: Post Individual VNF LCM Operation occurences - Method not implemented
     ...    Test objective: The objective is to test that POST method is not implemented
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.13.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: none
     ...    Post-Conditions: none 
-    Post Individual VNF LCM OP occurences
+    Post Individual VNF LCM Operation occurences
     Check HTTP Response Status Code Is    405
     
 Get status information about multiple VNF instances 
@@ -34,7 +34,7 @@ Get status information about multiple VNF instances
 
 PUT status information about multiple VNF instances - Method not implemented
     [Documentation]    Test ID: 7.3.1.12.3
-    ...    Test title: Put Individual VNF LCM OP occurences - Method not implemented
+    ...    Test title: Put Individual VNF LCM Operation occurences - Method not implemented
     ...    Test objective: The objective is to test that PUT method is not implemented
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.13.3.3 - SOL003 v2.4.1
@@ -44,9 +44,9 @@ PUT status information about multiple VNF instances - Method not implemented
     Put multiple VNF instances
     Check HTTP Response Status Code Is    405
 
-PATCH status information about multiple VNF instances - Method not implemented 
+PATCH status information about VNF instances - Method not implemented 
     [Documentation]    Test ID: 7.3.1.12.4
-    ...    Test title: Patch Individual VNF LCM OP occurences - Method not implemented
+    ...    Test title: Patch Individual VNF LCM Operation occurences - Method not implemented
     ...    Test objective: The objective is to test that PATCH method is not implemented
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.13.3.4 - SOL003 v2.4.1
@@ -58,7 +58,7 @@ PATCH status information about multiple VNF instances - Method not implemented
     
 DELETE status information about multiple VNF instances - Method not implemented 
     [Documentation]    Test ID: 7.3.1.12.5
-    ...    Test title: Delete Individual VNF LCM OP occurences - Method not implemented
+    ...    Test title: Delete Individual VNF LCM Operation occurences - Method not implemented
     ...    Test objective: The objective is to test that DELETE method is not implemented
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.13.3.5 - SOL003 v2.4.1

SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot

@@ -14,7 +14,7 @@ Instantiate a vnfInstance
     [Documentation]    Test ID: 7.3.1.3.1
     ...    Test title: Post Instantiate Individual VNFInstance 
     ...    Test objective: The objective is to instantiate a VNF instance
-    ...    Pre-conditions: none
+    ...    Pre-conditions: an existing VNF 
     ...    Reference: section 5.4.4.3.1 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: 

SOL003/VNFLifecycleManagement-API/ModifyVNFInformationWorkflow.robot

@@ -16,10 +16,10 @@ Suite Teardown    Terminate All Processes    kill=true
 
 *** Test Cases ***
 Modify info of a VNF Instance
-    [Documentation]    Test ID: 5.x.y.x
+    [Documentation]    Test ID: 7.3.1.24
     ...    Test title: Update information about a VNF instance
     ...    Test objective: The objective is to update information about a VNF instance.
-    ...    Pre-conditions: VNF instance is created (Test ID: 5.a.b.c)
+    ...    Pre-conditions: VNF instance is created 
     ...    Reference: section 5.3.6 - SOL003 v2.4.1
     ...    Config ID: Config_prod_VNFM
     ...    Applicability: NFVO is able to receive notifications from VNFM. Update information of a VNF instance is supported for the VNF (as capability in the VNFD)

SOL003/VNFLifecycleManagement-API/NotificationEndpoint.robot

@@ -27,7 +27,7 @@ Deliver a notification - Operation Occurence
 Deliver a notification - Id Creation
      [Documentation]    Test ID: 7.3.1.19.2
     ...    Test title: Deliver a notification - Id Creation
-    ...    Test objective: The objective is to test that POST method trigger a notification about the creation of a VNF identifier and the related to a VNF instance resource.
+    ...    Test objective: The objective is to test that POST method trigger a notification about the creation a VNF instance resource.
     ...    Pre-conditions: none
     ...    Reference:  section 5.4.20.3.1 - SOL005 v2.4.1
     ...    Config ID: Config_prod_NFVO