Update app-service-plan-manage.md

Document quality improvements

Author: apwestgarth

articles/app-service/app-service-plan-manage.md

@@ -102,12 +102,8 @@ When creating or manually scaling out an App Service Plan you may experience sit
 
 The preview of App Service Plan Asynchronous enables you to request your target number of instances and the platform scales out to the target number, without you having to modify your original request and retrying. The platform scales to the number of available instances and then triggers the underlying platform to make more instances available. You can make use of this functionality during scale-out operations or at plan creation time.  This functionality is supported for all Basic, Standard, and Premium pricing plans.
 
-### Cancelling an asynchronous scaling operation
-
-An in-progress aysynchronous scale operation is cancelled only when you explicitly change the TargetWorkerCount property.  Changes to other App Service Plan properties do not cancel the operation, including changes to the SKU, or App Service Plan instance count.  App Service Plan instance count changes that cannot be completed synchronously are ignored unless the TargetWorkerCount is also changed.  To explicitly cancel the scale operation, set the TargetWorkerCount to 0.
-
 > [!NOTE]
-> This behaviour is NOT configurable for App Service Plans created in App Service Environments.  App Service Environments create and scale App Service Plans asynchronously by default.
+> This behavior is NOT configurable for App Service Plans created in App Service Environments.  App Service Environments create and scale App Service Plans asynchronously by default.
 
 ### [Scale-out (CLI)](#tab/asyncscaleout)
 ```azurecli-interactive
@@ -121,9 +117,13 @@ az appservice plan create -g asyncasp -n asyncasplinuxexample --number-of-worker
 
 ### Scaling up or down App Service Plan SKUs
 
-When using asynchronous scaling, it is possible to scale up or down to a larger or smaller SKU.  During this type of operation, no other properties of the App Service Plan can be changed.  Scaling up or down to a new SKU may fail in the event that there are not enough App Service Plan instances available to fully satisfy the request, this is in order to prevent your App Service Plan having fewer workers than requested.
+When using asynchronous scaling, it's possible to scale up or down to a larger or smaller SKU.  During this type of operation, no other properties of the App Service Plan can be changed. Scaling up or down to a new SKU may fail if there aren't enough App Service Plan instances available to fully satisfy the request, this is to prevent your App Service Plan having fewer workers than requested.
+
+If a scale up or down operation fails, you can either scale in or out within the current SKU or perform the operation with the minim number of acceptable workers and then scale out asynchronously to the desired target.
+
+### Cancelling an asynchronous scaling operation
 
-If a scale up or down operation fails you can either scale in or out within the current SKU or perform the operation with the minim number of acceptable workers and then scale out asynchronously to the desired target.
+An in-progress asynchronous scale operation is canceled only when you explicitly change the TargetWorkerCount property. Changes to other App Service Plan properties don't cancel the operation, including changes to the SKU, or App Service Plan instance count. App Service Plan instance count changes that can't be completed synchronously are ignored unless the TargetWorkerCount is also changed. To explicitly cancel the scale operation, set the TargetWorkerCount to 0.
 ---
 
 <a name="delete"></a>