From a9e10830df468bbcd9dfea1bd841332033c72a37 Mon Sep 17 00:00:00 2001 From: fattore Date: Sun, 8 Mar 2026 12:01:13 +0100 Subject: [PATCH] correcting some typos --- GS_NFV-SOL_026.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/GS_NFV-SOL_026.md b/GS_NFV-SOL_026.md index b0180fe..0251c66 100644 --- a/GS_NFV-SOL_026.md +++ b/GS_NFV-SOL_026.md @@ -462,7 +462,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 6.3- | | | | |This resource endpoint shall be supported if | | | | | |the API producer supports asynchronous operations. | +---------------------------------+-----------------------------------------+---------------------+-----------------+---------------------------------------------------------------------+ -|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI is used by | +|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI is used by | |the API producer to send notifications to the API consumer. This resource is not produced by the API producer.\ | |NOTE 2: The URI of the task monitor is provided in the Location header of the HTTP response to the API consumer | |when the API producer returns a \"202 Accepted\" response. | @@ -863,8 +863,8 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 7.3- | | | | |if the API producer supports asynchronous operations. | +-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+ |NOTE 1: See clause 5.3.4 for the resource URIs of each inventory object collection. | -|NOTE 2: The resource URI of an indivdual object can be acquired from the corresponding object collection in its \"Members\" property. | -|NOTE 3: Notification endpoint resource and the corresponding NotficiationTargetURI | +|NOTE 2: The resource URI of an individual object can be acquired from the corresponding object collection in its \"Members\" property. | +|NOTE 3: Notification endpoint resource and the corresponding NotificationTargetURI | |is used by the API producer to send notifications to the API consumer. | |This resource is not produced by the API producer. \ | |NOTE 4: The URI of the task monitor is provided in the Location header | @@ -1187,7 +1187,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 8.3- | | | | |This resource endpoint shall be supported | | | | | |if the API producer supports asynchronous operations. | +-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+ -|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI | +|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI | |is used by the API producer to send notifications to the API consumer. | |This resource is not produced by the API producer.\ | |NOTE 2: The URI of the task monitor is provided in the Location header | @@ -1613,7 +1613,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 9.3- | | | | |This resource endpoint shall be supported | | | | | |if the API producer supports asynchronous operations. | +-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+ -|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI | +|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI | |is used by the API producer to send notifications to the API consumer. | |This resource is not produced by the API producer. | |NOTE 2: See clause 9.4.8 for the flow related to the API consumers receiving | @@ -1764,7 +1764,7 @@ The querying of information about one or more performance reports, as illustrate ### 9.4.8 Receiving performance reports asynchronously -This clause describes the sequence for receiving performance reports asynchrnously as notifications. +This clause describes the sequence for receiving performance reports asynchronously as notifications. ![Figure 9.4.8-1: Flow of receiving performance reports as notifications](media/image31.png) @@ -2072,7 +2072,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 10.3 | | | | |This resource endpoint shall be supported | | | | | |if the API producer supports asynchronous operations. | +-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+ -|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI | +|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI | |is used by the API producer to send notifications to the API consumer. | |This resource is not produced by the API producer. \ | |NOTE 2: The URI of the task monitor is provided in the Location header | @@ -2268,7 +2268,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 11.3 +-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+ |NOTE 1: Possible URI paths for the LogService and LogEntry resources are specified | |in the Redfish® data model specification [\[3\]](#_ref_3). \ | -|NOTE 2: Notification endpoint resource and the corresponding NotficiationTargetURI | +|NOTE 2: Notification endpoint resource and the corresponding NotificationTargetURI | |is used by the API producer to send notifications to the API consumer. | |This resource is not produced by the API producer. \ | |NOTE 3: The URI of the task monitor is provided in the Location header | @@ -2549,7 +2549,7 @@ The URI query parameters, request and response bodies, and response codes of the ### 11.5.6 Resource: Subscriptions -This resource represents subscriptions related to log management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can be used to create a subscription to receive a notification once the Redfish service has successfully collected logs (diagnostics data) in the respectiv message registry. +This resource represents subscriptions related to log management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can be used to create a subscription to receive a notification once the Redfish® service has successfully collected logs (diagnostics data) in the respectiv message registry. Table 11.5.6-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1). -- GitLab