Merge pull request #98639 from sffamily/update-scale

minor update of the expected time range.

Author: PRMerger13

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

@@ -4,7 +4,7 @@ description: Learn how to scale an Azure SignalR Service instance to add or redu
 author: sffamily
 ms.service: signalr
 ms.topic: conceptual
-ms.date: 11/21/2019
+ms.date: 12/11/2019
 ms.author: zhshang
 ---
 # How to scale an Azure SignalR Service instance?
@@ -13,12 +13,12 @@ This article shows you how to scale your instance of Azure SignalR Service. Ther
 * [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.
 
-The scale settings take a few minutes to apply. They don't require you to change your code or redeploy your server application.
+The scale settings take a few minutes to apply. In rare cases, it may take around 30 minutes to apply. They don't require you to change your code or redeploy your server application.
 
 For information about the pricing and capacities of individual SignalR Service, see [Azure SignalR Service Pricing Details](https://azure.microsoft.com/pricing/details/signalr-service/).  
 
 > [!NOTE]
-> Changing SignalR Service from **Free** tier to **Standard** tier or vice versa, the public service IP will be changed and it usually takes 3-60 minutes to propagate the change to DNS servers across the entire internet. 
+> Changing SignalR Service from **Free** tier to **Standard** tier or vice versa, the public service IP will be changed and it usually takes 30-60 minutes to propagate the change to DNS servers across the entire internet. 
 > Your service might be unreachable before DNS gets updated. Generally it’s not recommended to change your pricing tier too often.
 
 
@@ -28,15 +28,15 @@ For information about the pricing and capacities of individual SignalR Service,
 
 2. In your SignalR Service page, from the left menu, select **Scale**.
 
-3. Choose your pricing tier, and then click **Select**. You need to set the unit count for **Standard** Tier.
+3. Choose your pricing tier, and then click **Select**. Set the unit count for **Standard** Tier.
 
     ![Scale on Portal](./media/signalr-howto-scale/signalr-howto-scale.png)
 
 4. Click **Save**.
 
 ## Scale using Azure CLI
 
-This script creates a new SignalR Service resource of **Free** Tier and a new resource group, and scale it up to **Standard** Tier. 
+This script creates a new SignalR Service resource of **Free** Tier and a new resource group, and scales it up to **Standard** Tier. 
 
 ```azurecli-interactive
 #!/bin/bash
@@ -82,7 +82,7 @@ For a table of service limits, quotas, and constraints in each tier, see [Signal
 
 In this guide, you learned about how to scale single SignalR Service instance.
 
-Multiple endpoints are also supported for scaling, sharding and cross-region scenarios.
+Multiple endpoints are also supported for scaling, sharding, and cross-region scenarios.
 
 > [!div class="nextstepaction"]
 > [scale SignalR Service with multiple instances](./signalr-howto-scale-multi-instances.md)