Refine language and improve clarity in scaling article

Author: JialinXin

articles/azure-signalr/signalr-howto-scale-signalr.md

@@ -9,7 +9,7 @@ ms.author: lianwei
 ms.custom: devx-track-azurecli
 ---
 # How to scale an Azure SignalR Service instance?
-This article shows you how to scale your instance of Azure SignalR Service. There are two scenarios for scaling, scale up and scale out.
+This article shows you how to scale your instance of Azure SignalR Service. There are two scenarios for scaling. Scale up and scale out.
 
 * [Scale up](https://en.wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling): Get more units, connections, messages, and more. You scale up by changing the pricing tier from Free to Standard.
 * [Scale out](https://en.wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling): Increase the number of SignalR units. You can scale out to as many as 100 units. There are limited unit options to select for the scaling: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90 and 100 units for a single SignalR Service instance. If you want to scale beyond 100 units, the [Premium_P2](#enhanced-large-instance-support-with-premium_p2-sku) SKU offers expanded capabilities.
@@ -20,10 +20,10 @@ For information about the pricing and capacities of individual SignalR Service,
 
 > [!NOTE]
 > Scaling Azure SignalR Service between different pricing tiers may result in service downtime.
-> The downtime behavior varies by tier combination and is summarized in the table below.
+> The downtime behavior varies by tier combination and is summarized in the table.
 >
 > | Scale Scenario | Downtime Expected |
-> | -- | -- |
+> |--|--|
 > | Free ↔ Standard / Premium | Yes |
 > | Standard_S1 ↔ Premium_P1 | No |
 > | Premium_P1 ↔ Premium_P2 | No |
@@ -91,7 +91,7 @@ az signalr update \
   --unit-count 50
 ```
 
-Make a note of the actual name generated for the new resource group. You'll use that resource group name when you want to delete all group resources.
+Make a note of the actual name generated for the new resource group. Use that resource group name when you want to delete all group resources.
 
 [!INCLUDE [cli-script-clean-up](../../includes/cli-script-clean-up.md)]
 
@@ -107,10 +107,10 @@ The new Premium_P2 SKU is designed to facilitate extensive scalability for high-
 
 You can scale up the SKU to Premium_P2 using Azure portal or Azure CLI.
 
-The Premium_P2 tier uses a different architecture internally to manage a large amount of underlying resources. Thus, it's expected that scaling operations of this tier might take longer compared to those in smaller SKUs.
+The Premium_P2 tier uses a different architecture internally to manage a large amount of underlying resources. Thus, it's expected that scaling operations of this tier might take longer compared to those tiers in smaller SKUs.
 
 > [!NOTE]
-> Be aware that there is a default quota limit capping the number of SignalR units at **150** per subscription per region. This is a soft limit and can be increased upon request. To do so, simply submit a support ticket to request an adjustment to this quota.
+> There is a default quota limit capping the number of SignalR units at **150** per subscription per region. This is a soft limit and can be increased upon request. To do so, simply submit a support ticket to request an adjustment to this quota.
 
 ## Next steps