Acrolinx

Author: v-dirichards

articles/reliability/migrate-app-service.md

@@ -19,7 +19,7 @@ This guide describes how to migrate a multi-tenant App Service from non-availabi
 > [!NOTE]
 > This article is about availability zones support using multi-tenant environment with App Service Premium v2 or Premium v3 plans.
 
-Your App Service plans an be deployed across [availability zones (AZ)](../reliability/availability-zones-overview.md) to help you achieve resiliency and reliability for your business-critical workloads. This architecture is also known as zone-redundancy.
+Your App Service plans can be deployed across [availability zones (AZ)](../reliability/availability-zones-overview.md) to help you achieve resiliency and reliability for your business-critical workloads. This architecture is also known as zone-redundancy.
 
 When you configure to be zone-redundant, the platform automatically spreads the instances of the Azure App Service plan across three zones in the selected region. This means that the minimum App Service Plan instance count will always be three. If you specify a capacity larger than three, and the number of instances is divisible by three, the instances are spread evenly. Otherwise, instance counts beyond 3*N are spread across the remaining one or two zones.
 

articles/reliability/reliability-app-service.md

@@ -57,7 +57,7 @@ Availability zone support is a property of the App Service plan. The following a
 
 - Availability zones can only be specified when creating a **new** App Service plan. A pre-existing App Service plan can't be converted to use availability zones.
 
-- The following reg ions support Azure App Services running on multi-tenant environments:
+- The following regions support Azure App Services running on multi-tenant environments:
 
     - Australia East
     - Brazil South
@@ -105,7 +105,7 @@ az appservice plan create --resource-group MyResourceGroup --name MyPlan --sku P
 > Since the platform spreads VMs across three zones and you need to account for at least the failure of one zone, multiply peak workload instance count by a factor of zones/(zones-1), or 3/2. For example, if your typical peak workload requires four instances, you should provision six instances: (2/3 * 6 instances) = 4 instances.
 >
 
-# [Azure Portal](#tab/portal)
+# [Azure portal](#tab/portal)
 
 
 To create an App Service with availability zones using the Azure portal, enable the zone redundancy option during the "Create Web App" or "Create App Service Plan" experiences.