Apply suggestions from code review

Co-authored-by: Stephanie Savell <[email protected]>

Author: jmart1428

articles/app-service/environment/creation.md

@@ -55,7 +55,7 @@ To create an App Service Environment in the Azure portal, do the following steps
 
 1. In the **Basics** tab, do the following steps:
 
-   -  Select the subscription.
+   - Select the subscription.
    - Select or create the resource group.
    - Enter the name of your App Service Environment.
 
@@ -111,7 +111,7 @@ To create an App Service Environment in the Azure portal, do the following steps
 
 After you successfully create your App Service Environment, you can select it as a location when you create your apps.
 
-For more information, see [Create an App Service Environment by using an ARM template](how-to-create-from-template.md).
+For more information, see [Create an App Service Environment by using an Azure Resource Manager template](how-to-create-from-template.md).
 
 <!--Links-->
 [Intro]: ./overview.md

articles/app-service/environment/overview.md

@@ -86,7 +86,7 @@ App Service Environment v3 differs from earlier versions in the following ways:
 
 - You can deploy an App Service Environment v3 with zone redundancy enabled. This option is available only in regions where all dependencies support zone redundancy. You can enable zone redundancy at creation or anytime after deployment.
 
-  Consider the following factors for an environment with zone redundancy:
+  Consider the following factors for an environment that has zone redundancy:
 
   - Each App Service plan must have at least two instances to distribute them across zones.
   - Each App Service plan's zone redundancy status is independent, so you can use a mix of zone-redundant and non-zone-redundant plans.

articles/reliability/includes/app-service/reliability-backups-include.md

@@ -7,4 +7,4 @@
  ms.custom: include file
 ---
 
-These capabilities help when redeploying code is difficult or when you store state on disk. Most solutions shouldn't rely exclusively on backups. Instead, use the other capabilities in this guide to support your resiliency requirements. However, backups protect against some risks that other approaches don't. For more information, see [Back up and restore your app in App Service](/azure/app-service/manage-backup).
+These capabilities help when it's difficult to redeploy code or when you store state on disk. Most solutions shouldn't rely exclusively on backups. Instead, use the other capabilities in this guide to support your resiliency requirements. However, backups protect against some risks that other approaches don't. For more information, see [Back up and restore your app in App Service](/azure/app-service/manage-backup).

articles/reliability/includes/app-service/reliability-zone-down-experience-include.md

@@ -14,9 +14,9 @@ Expect the following outcomes when you configure App Service plans for zone redu
 
 - **Notification:** You can monitor zone failure events through Azure Service Health and Azure Resource Health. Set up alerts on these services to receive notifications about zone-level problems.
 
-- **Active requests:** Any requests in progress that connect to an App Service plan instance in the faulty availability zone are terminated. Retry those requests.
+- **Active requests:** Any in-progress requests that connect to an App Service plan instance in the faulty availability zone are terminated. Retry those requests.
 
-- **Traffic rerouting:** App Service detects the lost instances from that zone and attempts to find new replacement instances. After it finds replacements, it distributes traffic across the new instances as needed.
+- **Traffic rerouting:** App Service detects the lost instances from that zone and attempts to find new replacement instances. After App Service finds replacements, it distributes traffic across the new instances as needed.
 
     If autoscale is configured and determines that more instances are needed, it requests instances from App Service. Autoscale behavior operates independently of App Service platform behavior. So your instance count specification doesn't need to be a multiple of two. For more information, see [Scale up an app in App Service](/azure/app-service/manage-scale-up) and [Autoscale overview](/azure/azure-monitor/autoscale/autoscale-overview).
 

articles/reliability/reliability-app-service-environment.md

@@ -33,7 +33,7 @@ For more information about reliability support in App Service, see [Reliability
 
 ## Reliability architecture overview
 
-When you implement an [App Service Environment](/azure/app-service/environment/overview), you deploy the environment as the container for your App Service plans and web apps. During setup, configure core networking settings and optional hardware isolation. Choose whether or not to support zone redundancy on the environment if the region supports availability zones.
+When you implement an [App Service Environment](/azure/app-service/environment/overview), you deploy the environment as the container for your App Service plans and web apps. During setup, configure core networking settings and optional hardware isolation. Choose whether to support zone redundancy on the environment if the region supports availability zones.
 
 After you create your environment, you can create one or more App Service plans.
 
@@ -73,7 +73,7 @@ To enable zone redundancy for your App Service Environment, you must meet the fo
 
 - Use a scale unit that supports availability zones. When you create an App Service Environment, the environment is assigned to a scale unit based on the resource group where the environment resides. If your scale unit doesn't support availability zones, you need to create a new environment in a new resource group.
 
-- Configure your App Service Environment *and* your plans to support zone redundancy. You can enable zone redundancy during the creation of the environment or by updating an existing environment.
+- Configure your App Service Environment and your plans to support zone redundancy. You can enable zone redundancy during the creation of the environment or by updating an existing environment.
 
 ### Instance distribution across zones
 
@@ -95,7 +95,7 @@ If you enable availability zones but specify a capacity of fewer than two instan
 
 ### Configure availability zone support
 
-To learn how to create, enable, or disable a new zone-redundant App Service Environment and new zone-redundant App Service plans, see  [Configure App Service Environments and Isolated v2 App Service plans for zone redundancy](../app-service/environment/configure-zone-redundancy-environment.md).
+To learn how to create, enable, or disable a new zone-redundant App Service Environment and new zone-redundant App Service plans, see [Configure App Service Environments and Isolated v2 App Service plans for zone redundancy](../app-service/environment/configure-zone-redundancy-environment.md).
 
 > [!NOTE]
 > A change in the zone redundancy status of an App Service Environment takes 12 to 24 hours to complete. During the upgrade process, no downtime or performance problems occur.