From ac02a6da633f9058c5d7c847ed4e799efc41be91 Mon Sep 17 00:00:00 2001 From: Liudmila Molkova <limolkova@microsoft.com> Date: Mon, 7 Oct 2024 10:03:32 -0700 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Joao Grassi <5938087+joaopgrassi@users.noreply.github.com> --- docs/messaging/messaging-spans.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/messaging/messaging-spans.md b/docs/messaging/messaging-spans.md index 2af922aca6..572cb6bdf5 100644 --- a/docs/messaging/messaging-spans.md +++ b/docs/messaging/messaging-spans.md @@ -239,12 +239,12 @@ into the message. The "Publish" span SHOULD always link to the creation context that was injected into a message either from a "Create" span or as a custom creation context. -When instrumenting library API that always sends a single message, it's +When instrumenting a library API that always sends a single message, it is RECOMMENDED to create "Publish" span without "Create" span. -When instrumenting library API that usually operate with batches, it's -RECOMMENDED to create "Create" span for each message along with the "Publish" span. -It's also RECOMMENDED to provide a configuration option allowing to disable "Create" +When instrumenting a library API that usually operate with batches, it is +RECOMMENDED to create a "Create" span for each message along with the "Publish" span. +It is also RECOMMENDED to provide a configuration option allowing to disable "Create" span creation. #### Consumer spans