Apply suggestions from code review

Author: jmart1428

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 Environments](../../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.
 
@@ -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).
 

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.
 
@@ -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:** 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.