Minor fix in NS LCM interface definitions

src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml

@@ -3877,26 +3877,6 @@ definitions:
           - ROLLED_BACK
           - FAILED
 
-  NsLcmOperationStateType:
-    description: >
-      The enumeration NsLcmOperationStateType shall comply with the provisions defined in Table 6.5.4.4-1.
-      Value | Description
-      ------|------------
-      PROCESSING | The LCM operation is currently in execution.
-      COMPLETED | The LCM operation has been completed successfully.
-      PARTIALLY_COMPLETED | The LCM operation has been partially completed with accepTable errors.
-      FAILED_TEMP | The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed.
-      FAILED | The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed.
-      OLLING_BACK | The LCM operation is currently being rolled back.
-      ROLLED_BACK | The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.
-    type: string
-    enum:
-      - PROCESSING
-      - COMPLETED
-      - FAILED_TEMP
-      - FAILED
-      - ROLLING_BACK
-      - ROLLED_BACK
   NsLcmOpType:
     description: >
       The enumeration NsLcmOpType represents those lifecycle operations that trigger a NS lifecycle management operation

src/SOL005/NSLifecycleManagementNotification/definitions/SOL005NSLifecycleManagementNotification_def.yaml

@@ -433,23 +433,6 @@ definitions:
             $ref: "../../definitions/SOL005_def.yaml#/definitions/Link"
 
   NsChangeNotification:
-    description: >
-      This type represents an NS change notification, which informs the receiver of changes on an NS instance caused by 
-      an LCM operation occurrence, which directly or indirectly impacts its NS component and is triggered without any context 
-      of this NS instance. In other words, this notification is triggered by an LCM operation occurrence on one of the components 
-      of the NS instance where aforementioned LCM operation occurrence is not associated to an NS LCM operation occurrence on 
-      the NS instance itself. Examples for such operations are a VNF LCM operation on a constituent VNF instance e.g. requested 
-      by an EM or automatically triggered by a VNFM, or an NS LCM operation on a constituent NS instance executed by either the 
-      same NFVO or another NFVO than the one managing the current NS instance.
-      This notification is different from the NsLcmOperationOccurrenceNotification (see clause 6.5.2.5), which is triggered by 
-      the NS LCM operation occurrence on the current NS instance itself. 
-      It shall comply with the provisions defined in table 6.5.2.8 1. The support of the notification is mandatory.
-      The trigger conditions include:
-      1) NS LCM operation occurrence which directly or indirectly impacts the NS component (start and result).
-      If this is a notification about the start of an LCM operation occurrence impacting the NS component, the notification
-      shall be sent as soon as the impact on the NS component is identified.
-      If this is a notification about a final result state of an NS LCM operation occurrence impacting the NS component, the
-      notification shall be sent after the impact on the NS component has been executed.
     type: object
     required:
       - id