clarification on status

Author: spelluru

articles/service-bus-messaging/entity-suspend.md

@@ -2,25 +2,25 @@
 title: Azure Service Bus - suspend messaging entities
 description: This article explains how to temporarily suspend and reactivate Azure Service Bus message entities (queues, topics, and subscriptions).
 ms.topic: article
-ms.date: 09/28/2021 
+ms.date: 09/06/2022 
 ms.custom: devx-track-azurepowershell
 ---
 
 # Suspend and reactivate messaging entities (disable)
 
-Queues, topics, and subscriptions can be temporarily suspended. Suspension puts the entity into a disabled state in which all messages are maintained in storage. However, messages cannot be removed or added, and the respective protocol operations yield errors.
+Queues, topics, and subscriptions can be temporarily suspended. Suspension puts the entity into a disabled state in which all messages are maintained in storage. However, messages can't be removed or added, and the respective protocol operations yield errors.
 
 You may want to suspend an entity for urgent administrative reasons. For example, a faulty receiver takes messages off the queue, fails processing, and yet incorrectly completes the messages and removes them. In this case, you may want to disable the queue for receives until you correct and deploy the code. 
 
-A suspension or reactivation can be performed either by the user or by the system. The system only suspends entities because of grave administrative reasons such as hitting the subscription spending limit. System-disabled entities cannot be reactivated by the user, but are restored when the cause of the suspension has been addressed.
+A suspension or reactivation can be performed either by the user or by the system. The system only suspends entities because of grave administrative reasons such as hitting the subscription spending limit. System-disabled entities can't be reactivated by the user, but are restored when the cause of the suspension has been addressed.
 
 ## Queue status 
 The states that can be set for a **queue** are:
 
 -   **Active**: The queue is active. You can send messages to and receive messages from the queue. 
 -   **Disabled**: The queue is suspended. It's equivalent to setting both **SendDisabled** and **ReceiveDisabled**. 
 -   **SendDisabled**: You can't send messages to the queue, but you can receive messages from it. You'll get an exception if you try to send messages to the queue. 
--   **ReceiveDisabled**: You can send messages to the queue, but you can't receive messages from it. You'll get an exception if you try to receive messages to the queue.
+-   **ReceiveDisabled**: You can send messages to the queue, but you can't receive messages from it. You'll get an exception if you try to receive messages from the queue.
 
 
 ### Change the queue status in the Azure portal: 
@@ -34,7 +34,7 @@ The states that can be set for a **queue** are:
 
     :::image type="content" source="./media/entity-suspend/entity-state-change.png" alt-text="Set state of the queue":::
 
-You can also disable the send and receive operations using the Service Bus [NamespaceManager](/dotnet/api/microsoft.servicebus.namespacemanager) APIs in the .NET SDK, or using an Azure Resource Manager template through Azure CLI or Azure PowerShell.
+You can also disable the send and receive operations using an Azure Resource Manager template through Azure CLI or Azure PowerShell.
 
 ### Change the queue status using Azure PowerShell
 The PowerShell command to disable a queue is shown in the following example. The reactivation command is equivalent, setting `Status` to **Active**.
@@ -54,7 +54,7 @@ You can change topic status in the Azure portal. Select the current status of th
 
 The states that can be set for a **topic** are:
 - **Active**: The topic is active. You can send messages to the topic. 
-- **Disabled**: The topic is suspended. You can't send messages to the topic. 
+- **Disabled**: The topic is suspended. You can't send messages to the topic. Setting **Disabled** is equivalent to setting **SendDisabled** for a topic. 
 - **SendDisabled**: Same effect as **Disabled**. You can't send messages to the topic. You'll get an exception if you try to send messages to the topic. 
 
 ## Subscription status
@@ -64,8 +64,10 @@ You can change subscription status in the Azure portal. Select the current statu
 
 The states that can be set for a **subscription** are:
 - **Active**: The subscription is active. You can receive messages from the subscription.
-- **Disabled**: The subscription is suspended. You can't receive messages from the subscription. 
-- **ReceiveDisabled**: Same effect as **Disabled**. You can't receive messages from the subscription. You'll get an exception if you try to receive messages to the subscription.
+- **Disabled**: The subscription is suspended. You can't receive messages from the subscription. Setting **Disabled** on a subscription is equivalent to setting **ReceiveDisabled**. You'll get an exception if you try to receive messages from the subscription.
+- **ReceiveDisabled**: Same effect as **Disabled**. You can't receive messages from the subscription. You'll get an exception if you try to receive messages from the subscription.
+
+Here's how the behavior is based on the status you set on a topic and its subscription. 
 
 | Topic status | Subscription status | Behavior | 
 | ------------ | ------------------- | -------- |