incorporate review feedback

Author: jmart1428

articles/app-service/configure-zone-redundancy.md

@@ -12,7 +12,7 @@ ms.author: anaharris
 
 Azure App Service provides built-in reliability features to help ensure that your applications remain available and resilient. This article describes how to create an App Service plan that includes zone redundancy. It also covers how to disable and enable zone redundancy on existing plans and how to check for zone redundancy support. For more information about zone redundancy, see [Reliability in App Service](../reliability/reliability-app-service.md).
 
-## Create a new App Service plan that includes zone redundancy
+## Create a new zone-redundant App Service plan
 
 To create a new App Service plan that includes zone redundancy, follow the appropriate steps.
 

articles/app-service/environment/configure-zone-redundancy-environment.md

@@ -18,7 +18,7 @@ For more information about zone redundancy, see [Reliability in an App Service E
 
 ## Configure zone redundancy for an App Service Environment
 
-- **To create a new App Service Environment that includes zone redundancy**, follow the steps to [create an App Service Environment](creation.md). Make sure to select **Enabled** for **Zone redundancy**.
+- **To create a new zone-redundant App Service Environment**, follow the steps to [create an App Service Environment](creation.md). Make sure to select **Enabled** for **Zone redundancy**.
 
 - **To enable or disable zone redundancy** for an existing App Service Environment, use the Azure CLI or Bicep.
 
@@ -69,7 +69,7 @@ For more information about zone redundancy, see [Reliability in an App Service E
 
 All App Service plans created in an App Service Environment must use the Isolated v2 pricing tier.
 
-If you enable your App Service Environment to be zone redundant, you must also set the Isolated v2 App Service plans as zone redundant. Each plan has its own independent zone redundancy setting, so you can manually enable or disable zone redundancy on specific plans in an App Service Environment, as long as the environment is configured to be zone redundant.
+If you enable your App Service Environment to be zone redundant, you can also set the Isolated v2 App Service plans as zone redundant. Each plan has its own independent zone redundancy setting, so you can manually enable or disable zone redundancy on specific plans in an App Service Environment, as long as the environment is configured to be zone redundant.
 
 - **To create a new Isolated v2 App Service plan with zone redundancy**, use the Azure portal, the Azure CLI, or Bicep.
     

articles/app-service/environment/creation.md

@@ -25,13 +25,13 @@ An [App Service Environment][Intro] is a single-tenant deployment of Azure App S
   - Subnet size
   - The name of your App Service Environment
 
-   Ensure that your subnet is large enough to accommodate the maximum scale of your App Service Environment. Use a `/24` subnet with 256 addresses as the recommended size.
+- Ensure that your subnet is large enough to accommodate the maximum scale of your App Service Environment. Use a `/24` subnet with 256 addresses as the recommended size.
 
 - Select your virtual IP (VIP) type. The virtual IP type determines how your apps are accessed.
 
    Choose between the following two virtual IP types:
 
-    - *Internal VIP:* Your apps use an address within your App Service Environment subnet that doesn't appear in public Domain Name System (DNS). When you create an App Service Environment in the Azure portal, you can set up an Azure private DNS zone. Specify an **Inbound IP address** and select either **Automatic** or **Manual**.
+    - *Internal VIP:* Your apps use an address within your App Service Environment subnet that doesn't appear in the public Domain Name System (DNS). When you create an App Service Environment in the Azure portal, you can set up an Azure private DNS zone. Specify an **Inbound IP address** and select either **Automatic** or **Manual**.
 
     - *External VIP:* Your apps use a public-facing address listed in public DNS. You can specify an **Inbound IP address** and select either **Automatic** or **Manual**. If you select **Manual**, you must create a standard public IP address in Azure first.
 
@@ -41,7 +41,7 @@ An [App Service Environment][Intro] is a single-tenant deployment of Azure App S
 
      You must pay a minimum charge for one instance of Windows Isolated v2 in your App Service plan. When you use one or more instances, the charge is removed. This fee isn't additive.
 
-   - *Zone redundant deployment:* Zone redundancy ensures that workloads remain available even if one zone experiences an outage. In regions that support availability zones, you can configure App Service Environments so that apps are distributed across multiple availability zones within the same region. You must include at least two instances in your App Service plan to ensure redundancy across zones. You can scale out by adding one or more instances at a time. For more information, see [Reliability in App Service Environments](../../reliability/reliability-app-service-environment.md).
+   - *Zone redundant deployment:* Zone redundancy ensures that workloads remain available even if one zone experiences an outage. In regions that support availability zones, you can configure App Service Environments so that apps are distributed across multiple availability zones within the same region. You must include at least two instances in your App Service plan to ensure redundancy across zones. You can scale out by adding one or more instances at a time. For more information, see [Reliability in App Service Environment](../../reliability/reliability-app-service-environment.md).
 
    - *Host group deployment:* Your apps are deployed onto a dedicated host group. The dedicated host group isn't zone redundant. You can install and use your App Service Environment on dedicated hardware. There's no minimum instance charge for using an App Service Environment on a dedicated host group. However, you must pay for the host group when you provision the App Service Environment. You also pay a discounted App Service plan rate when you create your plans and scale out.
 

articles/app-service/environment/overview.md

@@ -68,7 +68,7 @@ Most customers don't require isolation down to the hardware level, so consider t
 
 ## Virtual network support
 
-An App Service Environment is a deployment of App Service that runs in a single subnet within a virtual network. When you deploy an app into an App Service Environment, it uses the inbound address assigned to the environment. If your App Service Environment is deployed with an internal virtual IP (VIP) address, the inbound address for all apps is an address within the App Service Environment subnet. If your App Service Environment is deployed with an external VIP address, the inbound address is a public-facing address, and your apps are listed in a public Domain Name System (DNS).
+An App Service Environment is a deployment of App Service that runs in a single subnet within a virtual network. When you deploy an app into an App Service Environment, it uses the inbound address assigned to the environment. If your App Service Environment is deployed with an internal virtual IP (VIP) address, the inbound address for all apps is an address within the App Service Environment subnet. If your App Service Environment is deployed with an external VIP address, the inbound address is a public-facing address, and your apps are listed in the public Domain Name System (DNS).
 
 An App Service Environment v3 in its subnet uses a variable number of addresses, depending on the number of instances and the amount of traffic. Some infrastructure roles scale automatically, depending on the number of App Service plans and the load. Use a `/24` Classless Inter-Domain Routing (CIDR) block that has 256 addresses for your App Service Environment v3 subnet. This size can host an App Service Environment v3 at full scale-out capacity.
 
@@ -93,7 +93,7 @@ App Service Environment v3 differs from earlier versions in the following ways:
   - To make plans zone redundant, the App Service Environment must have zone redundancy enabled.
   - You can scale non-zone-redundant plans down to a single instance.
 
-  For more information, see [Reliability in App Service](../../reliability/reliability-app-service.md?pivots=isolated).
+  For more information, see [Reliability in App Service Environment](../../reliability/reliability-app-service-environment.md).
 
 - You can deploy an App Service Environment v3 on a dedicated host group. Host group deployments aren't zone redundant.
 

articles/reliability/includes/app-service/reliability-architecture-overview.md

@@ -15,6 +15,6 @@ App Service provides the following redundancy features:
 
 - **App scaling:** When you configure your App Service plan to run multiple VM instances, all apps in the plan run on all instances by default. If you configure your plan for autoscaling, all apps scale out together based on the autoscale settings. However, you can customize how many plan instances run a specific app by using [per-app scaling](/azure/app-service/manage-scale-per-app).
 
-- **Scale units:** App Service runs on a platform infrastructure called *scale units*, also known as *stamps*. A scale unit includes all components needed to host and run App Service, including compute, storage, networking, and load balancing. Azure manages scale units to ensure balanced workload distribution, perform routine maintenance, and maintain overall platform reliability.
+- **Scale units:** Internally, App Service runs on a platform infrastructure called *scale units*, also known as *stamps*. A scale unit includes all components needed to host and run App Service, including compute, storage, networking, and load balancing. Azure manages scale units to ensure balanced workload distribution, perform routine maintenance, and maintain overall platform reliability.
 
     Some capabilities might only be applied on specific scale units. For example, some App Service scale units might support zone redundancy, while other scale units in the same region don't.

articles/reliability/includes/app-service/reliability-instance-distribution-across-zones-include.md

@@ -9,7 +9,7 @@
 
 When you create a zone-redundant App Service plan, Azure distributes the plan's instances across availability zones in the region. This distribution ensures that your apps remain available even if one zone experiences an outage.
 
-Instance distribution in a zone-redundant deployment follows specific rules. These rules apply as the app scales in and out:
+Instance distribution in a zone-redundant deployment follows specific rules. These rules also apply as the app scales in and out:
 
 - **Minimum instances:** Your App Service plan must have a minimum of two instances for zone redundancy.
 

articles/reliability/includes/app-service/reliability-normal-operations-include.md

@@ -6,7 +6,7 @@
  ms.author: anaharris
  ms.custom: include file
 ---
-Expect the following outcomes when you configure App Service plans for zone redundancy and all availability zones function properly:
+The following list describes what to expect when App Service plans are configured for zone redundancy and all availability zones are operational:
 
 - **Traffic routing between zones:** During normal operations, traffic is routed between all available App Service plan instances across all availability zones.
 

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

@@ -8,7 +8,7 @@
 ---
 An availability zone outage might affect some aspects of App Service, even though the application continues to serve traffic. These behaviors include App Service plan scaling, application creation, application configuration, and application publishing.
 
-Expect the following outcomes when you configure App Service plans for zone redundancy and one or more availability zones are unavailable:
+The following list describes what to expect when App Service plans are configured for zone redundancy and one or more availability zones are unavailable:
 
 - **Detection and response:** The App Service platform automatically detects failures in an availability zone and initiates a response. No manual intervention is required to initiate a zone failover.
 

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

@@ -29,7 +29,7 @@ For more information about reliability support in App Service, see [Reliability
 
 ## Production deployment recommendations
 
-[Enable zone redundancy](#availability-zone-support) on your environment. Your App Service plans must use a minimum of two instances.
+[Enable zone redundancy](#availability-zone-support) on your environment, which requires that your App Service plans use a minimum of two instances.
 
 ## Reliability architecture overview
 
@@ -55,7 +55,7 @@ To use an App Service Environment, your plans must use the [Isolated v2 pricing
 
 You can configure your App Service Environment as *zone redundant*. You can also configure your App Service plans to be zone redundant, which distributes them across multiple availability zones.
 
-You can enable or disable zone redundancy on each specific plan.
+However, you can enable or disable zone redundancy on each plan. This means that you can have some plans in your environment that are zone redundant and others that aren't.
 
 When you create a zone-redundant App Service plan in your environment, the instances of your App Service plan are distributed across the availability zones in the region. For more information, see [Instance distribution across zones](../reliability/reliability-app-service.md#instance-distribution-across-zones).
 

articles/reliability/reliability-app-service.md

@@ -21,7 +21,7 @@ For more information about reliability support in App Service Environment, see [
 
 ## Production deployment recommendations
 
-For more information about App Service support for reliability requirements and how reliability affects other aspects of your architecture, see [Architecture best practices for the Web Apps feature of App Service](/azure/well-architected/service-guides/app-service-web-apps).
+To learn about how to deploy App Service to support your solution's reliability requirements, and how reliability affects other aspects of your architecture, see [Architecture best practices for App Service (Web Apps) in the Azure Well-Architected Framework](/azure/well-architected/service-guides/app-service-web-apps).
 
 ## Reliability architecture overview