diff --git a/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample14_AMQPMessage.md b/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample14_AMQPMessage.md
index 0c381ccf1472..f16bf1d72cfd 100644
--- a/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample14_AMQPMessage.md
+++ b/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample14_AMQPMessage.md
@@ -4,7 +4,7 @@ This sample demonstrates how to interact with the underlying AMQP message used b
 
 ## Message body
 
-The most common scenario where you may need to inspect the underlying AMQP message is in interop scenarios where you are receiving a message that has a non-standard body. The [AMQP specification](https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#section-message-format) allows three types of message body: a series of data sections, a value section, or a series of sequence sections. When using the `ServiceBusMessage.Body` property, you are implicitly using a single `data` section as the message body. If you are consuming from a queue or subscription in which the producer is sending messages with a non-standard body, you would need to the following:
+The most common scenario where you may need to inspect the underlying AMQP message is in interop scenarios where you are receiving a message that has a non-standard body. The [AMQP specification](https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#section-message-format) allows three types of message body: a series of data sections, a value section, or a series of sequence sections. When using the `ServiceBusMessage.Body` property, you are implicitly using a single `data` section as the message body. If you are consuming from a queue or subscription in which the producer is sending messages with a non-standard body, you would need to do the following:
 
 ```C# Snippet:ServiceBusInspectMessageBody
 ServiceBusReceiver receiver = client.CreateReceiver(queueName);