From 7fe171c4519e8dd903c9bd2b3dc28b172aabc159 Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Wed, 21 Dec 2022 14:23:08 -0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Joao Grassi --- specification/trace/semantic_conventions/messaging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specification/trace/semantic_conventions/messaging.md b/specification/trace/semantic_conventions/messaging.md index 3bc24168ecf..81dd23dff7a 100644 --- a/specification/trace/semantic_conventions/messaging.md +++ b/specification/trace/semantic_conventions/messaging.md @@ -77,11 +77,11 @@ might be another intermediary or a consumer. ### Destinations and sources -A destination is usually identified by some name unique within the messaging system instance, which might look like a URL or a simple one-word identifier. +A destination is usually uniquely identified by name within the messaging system instance. Examples of a destination name would be a URL or a simple one-word identifier. Traditional messaging, such as JMS, involves two kinds of destinations: *topic*s and *queue*s. A message that is sent (the send-operation is often called "*publish*" in this context) to a *topic* is broadcasted to all consumers that have *subscribed* to the topic. -A message submitted to a queue is processed by a message *consumer* (usually exactly once although some message systems support a more performant at-least-once mode for messages with [idempotent][] processing). +A message that is sent to a *queue* is processed by a message *consumer* (usually exactly once although some message systems support a more performant at-least-once mode for messages with [idempotent][] processing). Entity messages are received from is called **source** here. Messages can be routed within one or multiple brokers, so message's *source* and *destination* could be different.