wording

Author: dlepow

articles/api-management/api-management-howto-autoscale.md

@@ -36,8 +36,8 @@ To follow the steps from this article, you must:
 
 Certain limitations and consequences of scaling decisions need to be considered before configuring autoscale behavior.
 
-+ The pricing tier of your API Management instance determines the [maximum number of units](upgrade-and-scale.md#upgrade-and-scale) you may set in autoscale rules. The **Standard tier** can be scaled to 4 units. You can add any number of units to the **Premium** tier.
-+ Scaling process will take at least 20 minutes.
++ The pricing tier of your API Management instance determines the [maximum number of units](upgrade-and-scale.md#upgrade-and-scale) you may scale to. The **Standard tier** can be scaled to 4 units. You can add any number of units to the **Premium** tier.
++ The scaling process will take at least 20 minutes.
 + If the service is locked by another operation, the scaling request will fail and retry automatically.
 + If your service instance is deployed in multiple regions (locations), only units in the **Primary location** can be scaled. Units in other locations can't be scaled.
 + If your service instance is configured with [availability zones](zone-redundancy.md) in the **Primary location**, be aware of the number of zones when configuring autoscaling. The counts (API Management units) in autoscale rules and limits must be a multiple of the number of zones.