edit pass: two-app-service-articles

Author: ShawnJackson

articles/app-service/configure-grpc.md

@@ -25,14 +25,14 @@ For gRPC client and server samples for each supported language, see the [documen
 
 Create your [web app](getting-started.md) as you normally would. Choose your preferred runtime stack, and choose Linux as your operating system.
 
-After you create your web app, you need to configure the following details to enable gRPC before deploying your application.
+After you create your web app, configure the following details to enable gRPC before you deploy your application.
 
 > [!NOTE]
-> If you're deploying a .NET gRPC app to App Service by using Visual Studio, skip to step 3. Visual Studio sets the HTTP version and the HTTP 2.0 proxy configuration for you.
+> If you're deploying a .NET gRPC app to App Service by using Visual Studio, skip to [step 3](#3-configure-the-http2-port). Visual Studio sets the HTTP version and the HTTP 2.0 proxy configuration for you.
 
 ## 1. Configure the HTTP version
 
-The first setting you need to configure is the HTTP version:
+The first setting that you need to configure is the HTTP version:
 
 1. On the left pane of your web app, under **Settings**, go to **Configuration**.
 2. On the **General Settings** tab, scroll down to **Platform settings**.
@@ -48,11 +48,11 @@ Next, you need to configure the HTTP 2.0 proxy:
 1. In the same **Platform settings** section, find the **HTTP 2.0 Proxy** setting and select **gRPC Only**.
 2. Select **Save**.
 
-This setting configures your site to be forwarded HTTP/2 requests.
+This setting configures your site to receive HTTP/2 requests.
 
 ## 3. Configure the HTTP/2 port
 
-App Service requires an application setting that specifically listens for HTTP/2 traffic in addition to the HTTP/1.1 port. You define the HTTP/2 port in the app settings:
+App Service requires an application setting that specifically listens for HTTP/2 traffic in addition to HTTP/1.1 traffic. You define the HTTP/2 port in the app settings:
 
 1. On the left pane of your web app, under **Settings**, go to **Environment variables**.
 2. On the **App settings** tab, add the following app settings to your application:

articles/app-service/language-support-policy.md

@@ -15,7 +15,7 @@ This article describes the language runtime support policy for updating existing
 
 ## Updates to existing stacks
 
-App Service updates existing stacks after they become available from each community. App Service updates major versions of stacks but can't guarantee any specific minor or patch versions. The platform controls minor and patch versions. For example, App Service updates node 18 but doesn't guarantee a specific Node 18.x.x version. If you need a specific minor or patch version, you can use a [custom container](quickstart-custom-container.md).
+App Service updates existing stacks after they become available from each community. App Service updates major versions of stacks but can't guarantee any specific minor or patch versions. The platform controls minor and patch versions. For example, App Service updates Node 18 but doesn't guarantee a specific Node 18.x.x version. If you need a specific minor or patch version, you can use a [custom container](quickstart-custom-container.md).
 
 ## Retirements
 
@@ -28,7 +28,7 @@ App Service follows community support timelines for the lifecycle of the runtime
 
 End-of-support dates for runtime versions are determined independently by their respective stacks and are outside the control of App Service. App Service sends reminder notifications to subscription owners for upcoming end-of-support runtime versions when they become available for each language.
 
-Those who receive notifications include account administrators, service administrators, and co-administrators. Contributors, readers, or other roles don't directly receive notifications, unless they opt in to receive notification emails through [service health alerts](../service-health/alerts-activity-log-service-notifications-portal.md).
+People who receive notifications include account administrators, service administrators, and co-administrators. Contributors, readers, or other roles don't directly receive notifications, unless they opt in to receive notification emails through [service health alerts](../service-health/alerts-activity-log-service-notifications-portal.md).
 
 ## Timelines for language runtime version support