Fix yaml files

Author: pyohannes

docs/attributes-registry/messaging.md

@@ -60,7 +60,8 @@ size should be used.
 | `publish` | One or more messages are provided for publishing to an intermediary. If a single message is published, the context of the "Publish" span can be used as the creation context and no "Create" span needs to be created. |
 | `create` | A message is created. "Create" spans always refer to a single message and are used to provide a unique creation context for messages in batch publishing scenarios. |
 | `receive` | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. |
-| `deliver` | One or more messages are passed to a consumer. This operation refers to push-based scenarios, where consumer register callbacks which get called by messaging SDKs. |
+| `process` | One or more messages are delivered to or processed by a consumer. |
+| `settle` | One or more messages are settled. |
 
 `messaging.system` has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.
 

docs/messaging/messaging-metrics.md

@@ -164,7 +164,7 @@ of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10
 <!-- semconv metric.messaging.process.duration(metric_table) -->
 | Name     | Instrument Type | Unit (UCUM) | Description    |
 | -------- | --------------- | ----------- | -------------- |
-| `messaging.process.duration` | Histogram | `s` | Measures the duration of the process operation. |
+| `messaging.process.duration` | Histogram | `s` | Measures the duration of process operation. |
 <!-- endsemconv -->
 
 ### Metric: `messaging.process.messages`

docs/messaging/messaging-spans.md

@@ -390,13 +390,13 @@ different processes could be listening on TCP port 12345 and UDP port 12345.
 
 `messaging.operation` has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.
 
-| Operation name | Description |
-| -------------- | ----------- |
-| `publish`      | One or more messages are provided for publishing to an intermediary. If a single message is published, the context of the "Publish" span can be used as the creation context and no "Create" span needs to be created. |
-| `create`       | A message is created. "Create" spans always refer to a single message and are used to provide a unique creation context for messages in batch publishing scenarios. |
-| `receive`      | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. |
-| `process`      | One or more messages are delivered to or processed by a consumer. |
-| `settle`       | One or more messages are settled. |
+| Value  | Description |
+|---|---|
+| `publish` | One or more messages are provided for publishing to an intermediary. If a single message is published, the context of the "Publish" span can be used as the creation context and no "Create" span needs to be created. |
+| `create` | A message is created. "Create" spans always refer to a single message and are used to provide a unique creation context for messages in batch publishing scenarios. |
+| `receive` | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. |
+| `process` | One or more messages are delivered to or processed by a consumer. |
+| `settle` | One or more messages are settled. |
 
 `messaging.system` has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.
 

model/registry/messaging.yaml

@@ -142,10 +142,13 @@ groups:
                 One or more messages are requested by a consumer.
                 This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages.
             - id: deliver
-              value: "deliver"
+              value: "process"
               brief: >
-                One or more messages are passed to a consumer.
-                This operation refers to push-based scenarios, where consumer register callbacks which get called by messaging SDKs.
+                One or more messages are delivered to or processed by a consumer.
+            - id: settle
+              value: "settle"
+              brief: >
+                One or more messages are settled.
         brief: >
           A string identifying the kind of messaging operation.
         note: If a custom value is used, it MUST be of low cardinality.