rebase and fix rabbitmq network note

open-telemetry · Mar 8, 2024 · 2b6bade · 2b6bade
1 parent a668af2
commit 2b6bade
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/messaging/rabbitmq.md b/docs/messaging/rabbitmq.md
@@ -25,7 +25,7 @@ In RabbitMQ, the destination is defined by an *exchange* and a *routing key*.
 | [`network.peer.address`](../attributes-registry/network.md) | string | Peer address of the network connection - IP address or Unix domain socket name. [1] | `10.1.2.80`; `/tmp/my.sock` | Recommended |
 | [`network.peer.port`](../attributes-registry/network.md) | int | Peer port number of the network connection. | `65123` | Recommended |
 
-**[1]:** If a database operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
+**[1]:** If an operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
 <!-- endsemconv -->
 
 [DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/document-status.md
diff --git a/model/trace/messaging.yaml b/model/trace/messaging.yaml
@@ -98,7 +98,7 @@ groups:
         tag: tech-specific-rabbitmq
       - ref: network.peer.address
         note: >
-          If a database operation involved multiple network calls (for example retries),
+          If an operation involved multiple network calls (for example retries),
           the address of the last contacted node SHOULD be used.
         tag: tech-specific-rabbitmq
       - ref: network.peer.port