Minor proof read updates

madsd · madsd · commit 097f51e1d968 · 2021-10-19T16:17:09.000+02:00
diff --git a/articles/app-service/configure-vnet-integration-enable.md b/articles/app-service/configure-vnet-integration-enable.md
@@ -12,8 +12,8 @@ ms.date: 10/20/2021
 
 Through integrating with an Azure virtual network (VNet) from your [App Service app](./overview.md), you can reach private resources from your app within the virtual network. The VNet Integration feature has two variations:
 
-Regional VNet integration: Connect to Azure virtual networks in the same region. You must have a dedicated subnet in the VNet you're integrating with.
-Gateway-required VNet integration: When you connect directly to VNet in other regions or to a Classic virtual network in the same region, you must use the gateway-required VNet integration.
+* Regional VNet integration: Connect to Azure virtual networks in the same region. You must have a dedicated subnet in the VNet you're integrating with.
+* Gateway-required VNet integration: When you connect directly to VNet in other regions or to a classic virtual network in the same region, you must use the gateway-required VNet integration.
 
 This how-to article will describe how to set up regional VNet integration.
 
diff --git a/articles/app-service/overview-vnet-integration.md b/articles/app-service/overview-vnet-integration.md
@@ -38,7 +38,7 @@ Apps in App Service are hosted on worker roles. Regional VNet integration works
 
 :::image type="content" source="./media/overview-vnet-integration/vnetint-how-regional-works.png" alt-text="How regional VNet integration works":::
 
-When regional VNet Iitegration is enabled, your app makes outbound calls through your VNet. The outbound addresses that are listed in the app properties portal are the addresses still used by your app. However, if your outbound call is to a virtual machine or private endpoint in the integration VNet or peered VNet, the outbound address will be an address from the integration subnet. The private IP assigned to an instance is exposed via the environment variable, ```WEBSITE_PRIVATE_IP```.
+When regional VNet integration is enabled, your app makes outbound calls through your VNet. The outbound addresses that are listed in the app properties portal are the addresses still used by your app. However, if your outbound call is to a virtual machine or private endpoint in the integration VNet or peered VNet, the outbound address will be an address from the integration subnet. The private IP assigned to an instance is exposed via the environment variable, ```WEBSITE_PRIVATE_IP```.
 
 When all traffic routing is enabled, all outbound traffic is sent into your VNet. If all traffic routing is not enabled, only private traffic (RFC1918) and service endpoints configured on the integration subnet will be sent into the VNet and outbound traffic to the internet will go through the same channels as normal.
 
@@ -162,7 +162,7 @@ If you create the gateway for use with gateway-required VNet integration, you do
 
 ### How gateway-required VNet integration works
 
-Gateway-required VNet integration is built on top of point-to-site VPN technology. Point-to-site VPNs limit network access to the virtual machine that hosts the app. Apps are restricted to send traffic out to the internet only through Hybrid Connections or through VNet integration. When your app is configured with the portal to use gateway-required VNet integration, a complex negotiation is managed on your behalf to create and assign certificates on the gateway and the application side. The result is that the workers used to host your apps are able to directly connect to the virtual network gateway in the selected VNet.
+Gateway-required VNet integration is built on top of point-to-site VPN technology. Point-to-site VPNs limit network access to the virtual machine that hosts the app. Apps are restricted to send traffic out to the internet only through hybrid connections or through VNet integration. When your app is configured with the portal to use gateway-required VNet integration, a complex negotiation is managed on your behalf to create and assign certificates on the gateway and the application side. The result is that the workers used to host your apps are able to directly connect to the virtual network gateway in the selected VNet.
 
 :::image type="content" source="./media/overview-vnet-integration/vnetint-how-gateway-works.png" alt-text="How gateway-required VNet integration works":::
 
diff --git a/articles/app-service/toc.yml b/articles/app-service/toc.yml
@@ -143,7 +143,7 @@
           href: networking/private-endpoint.md
         - name: Hybrid connections
           href: app-service-hybrid-connections.md
-        - name: Virtual Network Integration
+        - name: Virtual network integration
           href: overview-vnet-integration.md
         - name: Application Gateway integration
           href: networking/app-gateway-with-service-endpoints.md
@@ -301,9 +301,9 @@
           href: manage-disaster-recovery.md
         - name: Enable on Azure Arc
           href: manage-create-arc-environment.md
-        - name: Enable VNet Integration
+        - name: Enable VNet integration
           href: configure-vnet-integration-enable.md
-        - name: Configure VNet Integration routing
+        - name: Configure VNet integration routing
           href: configure-vnet-integration-routing.md
 
     - name: Move app
diff --git a/includes/app-service-web-vnet-types.md b/includes/app-service-web-vnet-types.md
@@ -9,7 +9,7 @@ ms.author: madsd
 * The dedicated compute pricing tiers, which includes the Basic, Standard, Premium, PremiumV2, and PremiumV3.
 * The App Service Environment which deploys directly into your VNet with dedicated supporting infrastructure and is using the Isolated and IsolatedV2 pricing tiers.
 
-The VNet integration feature is used in App Service dedicated compute pricing tiers. If your app is in [App Service Environment](../articles/app-service/environment/overview.md)], then it's already in a VNet and doesn't require use of the VNet integration feature to reach resources in the same VNet. For more information on all of the networking features, see [App Service networking features](../articles/app-service/networking-features.md).
+The VNet integration feature is used in App Service dedicated compute pricing tiers. If your app is in [App Service Environment](../articles/app-service/environment/overview.md), then it's already in a VNet and doesn't require use of the VNet integration feature to reach resources in the same VNet. For more information on all of the networking features, see [App Service networking features](../articles/app-service/networking-features.md).
 
 VNet integration gives your app access to resources in your VNet, but it doesn't grant inbound private access to your app from the VNet. Private site access refers to making an app accessible only from a private network, such as from within an Azure virtual network. VNet integration is used only to make outbound calls from your app into your VNet. The VNet integration feature behaves differently when it's used with VNet in the same region and with VNet in other regions. The VNet integration feature has two variations:
 
