Merge pull request #233572 from seligj95/patch-1

Quick clarifications

Author: prmerger-automator[bot]

articles/reliability/reliability-app-service.md

@@ -27,7 +27,7 @@ To explore how Azure App Service can bolster the resiliency of your application
 
 Azure availability zones are at least three physically separate groups of datacenters within each Azure region. Datacenters within each zone are equipped with independent power, cooling, and networking infrastructure. Availability zones are designed to ensure high availability in the case of a local zone failure.  When one zone experiences a failure, the remaining two zones support all regional services, capacity, and high availability.  Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see [Regions and availability zones](/azure/availability-zones/az-overview).
 
-Azure App Service Environment 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.
+Azure App Service 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.
 
@@ -48,8 +48,6 @@ Availability zone support is a property of the App Service plan. The following a
 
 - For dedicated environments, your App Service Environment must be v3. 
 
--  App Service Environment v1 doesn't support availability zones.  
-
     >[!IMPORTANT]
     >[App Service Environment v2 and v1 will be retired on 31 August 2024](https://azure.microsoft.com/updates/app-service-environment-v1-and-v2-retirement-announcement/). App Service Environment v3 is easier to use and runs on more powerful infrastructure. To learn more about App Service Environment v3, see [App Service Environment overview](../app-service/environment/overview.md). If you're currently using App Service Environment v2 or v1 and you want to upgrade to v3, please follow the [steps in this article](../app-service/environment/migration-alternatives.md) to migrate to the new version.
      
@@ -85,7 +83,7 @@ Availability zone support is a property of the App Service plan. The following a
     - West US 3 
 
 
-- To see which regions support App Services for dedicated environments v3, see [Regions](../app-service/environment/overview.md#regions).
+- To see which regions support availability zones for App Service Environment v3, see [Regions](../app-service/environment/overview.md#regions).
 
 ### Create a resource with availability zone enabled
 
@@ -149,7 +147,7 @@ The Azure Resource Manager template snippet below shows the new ***zoneRedundant
 
 #### To deploy a zone-redundant App Service using a dedicated environment
 
-To learn how to create the App Service Environment v3 on Isolated v2 plan, see [Create an App Service Environment](../app-service/environment/creation.md).
+To learn how to create an App Service Environment v3 on the Isolated v2 plan, see [Create an App Service Environment](../app-service/environment/creation.md).
 
 ### Fault tolerance
 
@@ -172,10 +170,10 @@ You cannot migrate existing App Service instances or environment resources from
 
 ### Pricing
 
-There's no additional cost associated with enabling availability zones. Pricing for a zone redundant App Service is the same as a single zone App Service. You'll be charged based on your App Service plan SKU, the capacity you specify, and any instances you scale to based on your autoscale criteria. If you enable availability zones but specify a capacity less than three, the platform will enforce a minimum instance count of three and charge you for those three instances.
+There's no additional cost associated with enabling availability zones. Pricing for a zone redundant App Service is the same as a single zone App Service. You'll be charged based on your App Service plan SKU, the capacity you specify, and any instances you scale to based on your autoscale criteria. If you enable availability zones but specify a capacity less than three, the platform will enforce a minimum instance count of three and charge you for those three instances. For pricing information for App Service Environment v3, see [Pricing](../app-service/environment/overview.md#pricing).
 
 
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Reliability in Azure](/azure/availability-zones/overview)
+> [Reliability in Azure](/azure/availability-zones/overview)