Acrolynx

Author: spelluru

articles/service-bus-messaging/explorer.md

@@ -21,7 +21,7 @@ Operations run on an Azure Service Bus namespace are of two kinds.
 
 > [!IMPORTANT]
 > - Service Bus Explorer doesn't support **management operations** and **sessions**. 
-> - We advice against using the Service Bus Explorer for larger messages, as this may result in timeouts, depending on the message size, network latency between client and Service Bus service etc. Instead, we recommend that you use your own client to work with larger messages, where you can specify your own timeout values.
+> - We advice against using the Service Bus Explorer for larger messages, as it may result in timeouts, depending on the message size, network latency between client and Service Bus service etc. Instead, we recommend that you use your own client to work with larger messages, where you can specify your own timeout values.
 
 
 ## Prerequisites
@@ -43,7 +43,7 @@ To use the Service Bus Explorer tool, you need to do the following tasks:
 
 To use the Service Bus Explorer, navigate to the Service Bus namespace on which you want to do data operations.
 
-1. If you're looking to run operations against a queue, select **Queues** from the navigation menu. If you're looking to run operations against a topic (and it's related subscriptions), select **Topics**. 
+1. If you're looking to run operations against a queue, select **Queues** from the navigation menu. If you're looking to run operations against a topic (and its related subscriptions), select **Topics**. 
 
     :::image type="content" source="./media/service-bus-explorer/queue-topics-left-navigation.png" alt-text="Screenshot of left side navigation, where entity can be selected." lightbox="./media/service-bus-explorer/queue-topics-left-navigation.png":::
 1. After selecting **Queues** or **Topics**, select the specific queue or topic.
@@ -60,7 +60,7 @@ To use the Service Bus Explorer, navigate to the Service Bus namespace on which
    > [!NOTE]
    > When you navigate to Service Bus explorer for an entity in a namespace that has the public access disabled, you see the following message eventhough you access it from a virtual machine that's in the same virtual network as the private endpoint. You can ignore it.
    >
-   > "The namespace has public network access disabled. Data operations such as Peek, Send, or Receive against this Service Bus entity won't work until you switch to all networks or allowlist your client IP in selected networks."
+   > "The namespace has public network access disabled. Data operations such as Peek, Send, or Receive against this Service Bus entit don't work until you switch to all networks or allowlist your client IP in selected networks."
 
 ## Peek a message
 
@@ -90,7 +90,7 @@ With the peek functionality, you can use the Service Bus Explorer to view the to
     > Since peek is not a destructive operation the message **won't** be removed from the entity.
 
     > [!NOTE]
-    > For performance reasons, when peeking messages from a queue or subscription which has it's maximum message size set over 1MB, the message body will not be retrieved by default. Instead, you can load the message body for a specific message by clicking on the **Load message body** button. If the message body is over 1MB it will be truncated before being displayed.
+    > For performance reasons, when peeking messages from a queue or subscription which has it's maximum message size set over 1 MB, the message body is not retrieved by default. Instead, you can load the message body for a specific message by clicking on the **Load message body** button. If the message body is over 1 MB it's not truncated before being displayed.
     > :::image type="content" source="./media/service-bus-explorer/peek-message-from-queue-with-large-message-support.png" alt-text="Screenshot with overview of peeked messages and button to load message body shown." lightbox="./media/service-bus-explorer/peek-message-from-queue-with-large-message-support.png":::
 
 ### Peek a message with advanced options
@@ -137,7 +137,7 @@ The receive function on the Service Bus Explorer permits receiving messages from
     :::image type="content" source="./media/service-bus-explorer/receive-message-from-queue.png" alt-text="Screenshot indicating the Receive button, and a page where the options can be set." lightbox="./media/service-bus-explorer/receive-message-from-queue.png":::
 
     > [!IMPORTANT]
-    > Please note that the ReceiveAndDelete mode is a ***destructive receive***, i.e. the message is removed from the queue when it is displayed on the Service Bus Explorer tool.
+    > Note that the ReceiveAndDelete mode is a ***destructive receive***, i.e. the message is removed from the queue when it is displayed on the Service Bus Explorer tool.
     >
     > To browse messages without removing them from the queue, consider using the **Peek** functionality, or using the **PeekLock** receive mode.
 
@@ -148,7 +148,7 @@ The receive function on the Service Bus Explorer permits receiving messages from
     :::image type="content" source="./media/service-bus-explorer/receive-message-from-queue-3.png" alt-text="Screenshot with overview of received messages and message properties shown." lightbox="./media/service-bus-explorer/receive-message-from-queue-3.png":::
 
     > [!NOTE]
-    > For performance reasons, when receiving messages from a queue or subscription which has it's maximum message size set over 1MB, only one message will be received at a time. If the message body is over 1MB it will be truncated before being displayed.
+    > For performance reasons, when receiving messages from a queue or subscription which has it's maximum message size set over 1 MB, only one message is received at a time. If the message body is over 1 MB it is truncated before being displayed.
 
 After a message is received in **PeekLock** mode, there are various actions you can take on it.
 
@@ -163,7 +163,7 @@ After a message is received in **PeekLock** mode, there are various actions you
     :::image type="content" source="./media/service-bus-explorer/receive-message-from-queue-complete.png" alt-text="Screenshot indicating the Complete button." lightbox="./media/service-bus-explorer/receive-message-from-queue-complete.png":::
 
     > [!IMPORTANT]
-    > Please note that completing a message is a ***destructive receive***, i.e. the message is removed from the queue when **Complete** has been selected in the Service Bus Explorer tool.
+    > Please note that completing a message is a ***destructive receive***, that is, the message is removed from the queue when **Complete** has been selected in the Service Bus Explorer tool.
 
 ### Defer a message
 
@@ -179,7 +179,7 @@ After a message is received in **PeekLock** mode, there are various actions you
 
     :::image type="content" source="./media/service-bus-explorer/receive-message-from-queue-abandon-lock.png" alt-text="Screenshot indicating the Abandon Lock button." lightbox="./media/service-bus-explorer/receive-message-from-queue-abandon-lock.png":::
 
-After the lock is abandoned, the message will be available for receive operations again.
+After the lock is abandoned, the message is available for receive operations again.
 
 ### Dead-letter
 
@@ -188,7 +188,7 @@ After the lock is abandoned, the message will be available for receive operation
 
     :::image type="content" source="./media/service-bus-explorer/receive-message-from-queue-dead-letter.png" alt-text="Screenshot indicating the Dead-letter button." lightbox="./media/service-bus-explorer/receive-message-from-queue-dead-letter.png":::
 
-After a message is dead-lettered, it will be available from the **Dead-letter** subqueue.
+After a message is dead-lettered, it is available from the **Dead-letter** subqueue.
 
 ### Purge messages
 
@@ -218,7 +218,7 @@ To send a message to a **queue** or a **topic**, select the **Send messages** bu
 
 ## Resend a message
 
-After peeking or receiving a message, you can resend it, which will send a copy of the message to the same entity, while allowing us to update it's content and properties. The original remains and isn't deleted even when resend is from the deadletter queue.
+After peeking or receiving a message, you can resend it, which sends a copy of the message to the same entity, while allowing us to update it's content and properties. The original remains and isn't deleted even when resend is from the deadletter queue.
 
 1. In the grid, select one or more messages you want to resend.
 1. Select the **Re-send selected messages** button.
@@ -232,7 +232,7 @@ After peeking or receiving a message, you can resend it, which will send a copy
 
     > [!NOTE] 
     > - The resend operation sends a copy of the original message. It doesn't remove the original message that you resubmit. 
-    > - If you resend a message in a dead-letter queue of a subscription, a copy of the message is sent to the topic. Therefore, all subscriptions will receive a copy of the message. 
+    > - If you resend a message in a dead-letter queue of a subscription, a copy of the message is sent to the topic. Therefore, all subscriptions receive a copy of the message. 
 
 ## Switch authentication type