edits

Author: v-stsavell

articles/app-service/environment/creation.md

@@ -41,7 +41,7 @@ A zone-redundant deployment provides three or four times the infrastructure, dep
 
 In a host group deployment, your apps are deployed onto a dedicated host group. The dedicated host group isn't zone redundant. In a host group deployment, you can install and use your App Service Environment on dedicated hardware. There's no minimum instance charge for using 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 as 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 instances possible is related to the total number of App Service plan instances, plus the load-based number of infrastructure roles.
+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.
 
 ## Create an App Service Environment in the portal
 

articles/app-service/environment/overview.md

@@ -22,7 +22,7 @@ An App Service Environment provides hosting capabilities for various workloads:
 
 - Functions
 
-- Logic apps (standard) - in [supported regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=logic-apps&regions=all)
+- Logic apps (standard) in [supported regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=logic-apps&regions=all)
 
 App Service Environments are designed to support application workloads that require specific performance and security features:
 

articles/reliability/includes/reliability-availability-zone-description-include.md

@@ -9,6 +9,4 @@
  ms.custom: include file
 ---
 
-Availability zones are physically separate groups of datacenters within each Azure region. When one zone fails, services can fail over to one of the remaining zones.
-
-For more information on availability zones in Azure, see [What are availability zones?](/azure/reliability/availability-zones-overview)
+[Availability zones](/azure/reliability/availability-zones-overview) are physically separate groups of datacenters within each Azure region. When one zone fails, services can fail over to one of the remaining zones.

articles/reliability/includes/reliability-transient-fault-description-include.md

@@ -9,6 +9,6 @@
  ms.custom: include file
 ---
 
-Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. They correct themselves after a short period of time. It's important that your applications handle transient faults, usually by retrying affected requests.
+Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. Transient faults correct themselves after a short period of time. It's important that your applications handle transient faults, usually by retrying affected requests.
 
 All cloud-hosted applications should follow the Azure transient fault handling guidance when communicating with any cloud-hosted APIs, databases, and other components. For more information, see [Recommendations for handing transient faults](/azure/well-architected/reliability/handle-transient-faults).