addressed comments from SOL WG review

src/SOL009/NFVManoConfigurationAndInformationManagement/components/NFVManoConfigurationAndInformationManagement_def.yaml

@@ -735,6 +735,8 @@ components:
     PeerEntity:
       description: >
         This type represents an individual peer entity.
+        * NOTE:     ETSI GS NFV-IFA 031 defines an additional attribute named "apiDiscoveryEndpoint" in the
+                    PeerManoEntity. The modelling of this attribute is not specified in the present document version.
         * NOTE 1:	The value of the "peerEntityId" attribute is the same as the value of the "id" attribute in the
                     "ManoEntity" of the corresponding NFV-MANO functional entity that acts as peer entity, and shall
                     follow the uniqueness requirements set out in clause 5.6.2.2 for the "id" attribute.
@@ -1567,6 +1569,7 @@ components:
 
             Permitted values:
             - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
+            - TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446.
             - OAUTH2: Using access token, as defined by the OAuth 2.0 specification
             in IETF RFC 6749.
           type: array

src/SOL009/NFVManoFaultManagement/NFVManoFaultManagement.yaml

@@ -20,7 +20,7 @@ info:
 
 externalDocs:
   description: ETSI GS NFV-SOL 009 V3.7.1
-  url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v0307601p.pdf
+  url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v030701p.pdf
 
 servers:
   - url: http://127.0.0.1/nfvmanofm/v1

src/SOL009/NFVManoFaultManagementNotification/NFVManoFaultManagementNotification.yaml

@@ -20,7 +20,7 @@ info:
 
 externalDocs:
   description: ETSI GS NFV-SOL 009 V3.7.1
-  url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v0307601p.pdf
+  url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v030701p.pdf
 
 servers:
   - url: http://127.0.0.1/callback/v1

src/SOL009/NFVManoLogManagement/NFVManoLogManagement.yaml

@@ -688,10 +688,10 @@ components:
 
     Subscriptions.Post.422:
       description: >
-        422 UNPROCESSABLE ENTITY
+        422 UNPROCESSABLE CONTENT
 
         Shall be returned upon the following error: The content type
-        of the payload body is supported and the payload body of a request
+        of the message content is supported and the message content of a request
         contains syntactically correct data but the data cannot be processed.
 
         The general cause for this error and its handling is specified in

src/SOL009/NFVManoPerformanceManagement/NFVManoPerformanceManagement.yaml

@@ -20,8 +20,8 @@ info:
   version: 2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
 
 externalDocs:
-  description: ETSI GS NFV-SOL 009 V3.6.1
-  url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.06.01_60/gs_NFV-SOL009v030601p.pdf
+  description: ETSI GS NFV-SOL 009 V3.7.1
+  url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v030701p.pdf
 
 servers:
   - url: http://127.0.0.1/nfvmanopm/v2
@@ -434,10 +434,10 @@ components:
             $ref: "./components/NFVManoPerformanceManagement_def.yaml#/components/schemas/PmJob"
     pm_jobs.Post.422:
       description: >
-        422 Unprocessable Entity
+        422 Unprocessable Content
 
         Shall be returned upon the following error: The content type
-        of the payload body is supported and the payload body of a request
+        of the message content is supported and the message content of a request
         contains syntactically correct data but the data cannot be processed.
 
         The general cause for this error and its handling is specified in

src/SOL009/components/SOL009_resp.yaml

@@ -74,7 +74,7 @@ components:
         "ProblemDetails" structure to be returned.
 
         If the request is malformed or syntactically incorrect (e.g. if the request URI contains incorrect
-        query parameters or the payload body contains a syntactically incorrect data structure),
+        query parameters or the message content contains a syntactically incorrect data structure),
         the API producer shall respond with this response code. The "ProblemDetails" structure shall be provided,
         and should include in the "detail" attribute more information about the source of the problem.
 
@@ -206,7 +206,7 @@ components:
         This response code is not appropriate in case the resource addressed by the URI is a container resource
         which is designed to contain child resources, but does not contain any child resource at the time
         the request is received. For a GET request to an existing empty container resource, a typical response
-        contains a 200 OK response code and a payload body with an empty array.
+        contains a 200 OK response code and a message content with an empty array.
       headers:
         Content-Type:
           description: The MIME type of the body of the response.
@@ -375,7 +375,7 @@ components:
       description: >
         413 PAYLOAD TOO LARGE
 
-        If the payload body of a request is larger than the amount of data the API producer is willing or able to process,
+        If the message content of a request is larger than the amount of data the API producer is willing or able to process,
         it shall respond with this response code, following the provisions in IETF RFC 7231 for the use
         of the "Retry-After" HTTP header and for closing the connection. The "ProblemDetails" structure may be omitted.
       headers:
@@ -474,9 +474,9 @@ components:
 
     422:
       description: >
-        422 UNPROCESSABLE ENTITY
+        422 UNPROCESSABLE CONTENT
 
-        If the payload body of a request contains syntactically correct data (e.g. well-formed JSON) but the data
+        If the message content of a request contains syntactically correct data (e.g. well-formed JSON) but the data
         cannot be processed (e.g. because it fails validation against a schema), the API producer shall respond
         with this response code. The "ProblemDetails" structure shall be provided, and should include in the "detail"
         attribute more information about the source of the problem.