Merge branch 'edit-app-service' of https://github.com/jmart1428/azure-docs-pr into edit-app-service

Author: jmart1428

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

@@ -67,7 +67,7 @@ resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' = {
     # [Azure portal](#tab/portal)
 
     1. In the [Azure portal](https://portal.azure.com), go to your App Service plan.
-    1. Select **Settings > Scale out (App Service plan)** in the left navigation pane.
+    1. Select **Settings** > **Scale out (App Service plan)** in the left navigation pane.
     1. Select **Zone Redundancy** to enable zone redundancy. Deselect it to disable it. 
 
         The zone redundancy status of an App Service plan changes almost instantaneously. No downtime or performance problems occur during the process. 
@@ -127,7 +127,7 @@ resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' = {
 
 To check whether an existing App Service plan supports zone redundancy, do the following steps:
 
-1. Determine the maximum number of availability zones that the App Service plan supports by using the Azure portal, Azure CLI, or Bicep and Resource Manager.
+1. Determine the maximum number of availability zones that the App Service plan supports by using the Azure portal, the Azure CLI, or Bicep and Resource Manager.
 
     # [Azure portal](#tab/portal)
     

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

@@ -127,13 +127,13 @@ If you enable your App Service Environment to be zone redundant, you can also se
     # [Azure portal](#tab/portal)
     
     1. In the [Azure portal](https://portal.azure.com), go to your App Service plan.
-    1. Select **Settings > Scale out (App Service plan)** in the left navigation pane.
+    1. Select **Settings** > **Scale out (App Service plan)** in the left navigation pane.
     1. Select **Zone redundancy** to enable zone redundancy. Deselect it to disable it.
      
     :::image type="content" source="./media/configure-zone-redundancy/app-service-plan-zone-redundancy-portal-isolated.png" alt-text="Screenshot of zone redundancy property for an App Service plan in the Azure portal.":::
     
     >[!IMPORTANT]
-    >If you have *Rules Based* scaling enabled, you can't use the Azure portal to enable zone redundancy for your App Service plan. You must use the Azure CLI or Bicep and Resource Manager instead.
+    >If you have *Rules Based* scaling enabled, you can't use the Azure portal to enable zone redundancy for your App Service plan. You must use the Azure CLI or Bicep and Azure Resource Manager instead.
     
     # [Azure CLI](#tab/azurecli)
     

articles/app-service/environment/creation.md

@@ -43,7 +43,7 @@ An [App Service Environment][Intro] is a single-tenant deployment of Azure App S
 
    - *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.
+   - *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 must also pay a discounted App Service plan rate when you create your plans and scale out.
 
      A dedicated host group deployment allocates a finite number of cores, which both the App Service plans and the infrastructure roles use. This type of deployment can't reach the 200 total instance count normally available in App Service Environment. The number of total possible instances is related to the total number of App Service plan instances, plus the load-based number of infrastructure roles.
 
@@ -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.
 
@@ -90,7 +90,7 @@ To create an App Service Environment in the Azure portal, do the following steps
     - Select or create your **Virtual Network**.
     - Select or create your **Subnet**.
 
-     If you create an App Service Environment with an internal VIP, you can:
+     If you create an App Service Environment that has an internal VIP, you can:
 
      - Configure Azure DNS private zones to point your domain suffix to your App Service Environment. For more information, see [DNS configuration](/azure/app-service/environment/using#dns-configuration).
 
@@ -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

@@ -25,10 +25,10 @@ An App Service Environment provides hosting capabilities for various workloads:
 
 App Service Environments are designed to support application workloads that require specific performance and security features:
 
-- Support for high scale.
-- Isolation and secure network access.
-- Support for high memory usage.
-- Ability to handle high requests per second (RPS).
+- Support for high scale
+- Isolation and secure network access
+- Support for high memory usage
+- Ability to handle high requests per second (RPS)
 
 You can create multiple App Service Environments in a single Azure region or across multiple Azure regions. This flexibility makes an App Service Environment ideal for horizontally scaling stateless applications that have a high RPS requirement.
 
@@ -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.
@@ -101,7 +101,7 @@ App Service Environment v3 differs from earlier versions in the following ways:
 
 - It no longer requires front-end scaling adjustments. App Service Environment v3 front ends automatically scale to meet your needs and are deployed on improved hosts.
 
-- It allows scale operations to proceed while another operation is in progress, as long as they involve different OS and size combinations. For example, while your Windows small App Service plan scales, you can start a scale operation for a Windows medium plan or any other plan except Windows small.
+- It allows scale operations to proceed while another operation is in progress, as long as they have different OS and size combinations. For example, while your Windows small App Service plan scales, you can start a scale operation for a Windows medium plan or any other plan except Windows small.
 
 - It supports access to apps in an internal-VIP App Service Environment v3 across global peering. Earlier versions don't support this access.
 

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

@@ -17,4 +17,4 @@ App Service provides the following redundancy features:
 
 - **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.
+    Some capabilities might only be applied to 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-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 @@ The following list describes what to expect when App Service plans are configure
 
 - **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.