prmerger feedback

Author: cephalin

articles/app-service/app-service-web-tutorial-custom-domain.md

@@ -89,7 +89,27 @@ Create two records according to the following table:
 
 ### [Subdomain (e.g. www.contoso.com)](#tab/subdomain)
 
-[!INCLUDE [dns-record-creation](includes/tutorial-secure-domain-certificate/dns-record-creation.md)]
+#### With an A record
+
+Create two records according to the following table:
+
+|Record type|Host|Value|Comments|
+|--- |--- |--- |--- |
+|A|\<subdomain\> (for example, www)|IP address shown in the **Add custom domain** dialog.| The domain mapping itself. |
+|TXT|asuid.\<subdomain\> (for example, asuid.www)|The domain verification ID shown in the **Add custom domain** dialog.| App Service accesses the `asuid.<subdomain>` TXT record to verify your ownership of the custom domain. |
+
+![Screenshot that shows a DNS records subdomain page.](../../media/app-service-web-tutorial-custom-domain/a-record-subdomain.png)
+
+#### With a CNAME record
+
+Create two records according to the following table:
+
+| Record type | Host | Value | Comments |
+| - | - | - |
+| CNAME | `<subdomain>` (for example, `www`) | `<app-name>.azurewebsites.net` | The domain mapping itself. |
+| TXT | `asuid.<subdomain>` (for example, `asuid.www`) | The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid.<subdomain>` TXT record to verify your ownership of the custom domain. |
+
+![Screenshot that shows the portal navigation to an Azure app.](../../media/app-service-web-tutorial-custom-domain/cname-record.png)
 
 ### [Wildcard (CNAME)](#tab/wildcard)
 

articles/app-service/environment/integrate-with-application-gateway.md

@@ -39,7 +39,7 @@ To integrate your application gateway with your ILB App Service environment, you
 
 ### ILB App Service environment
 
-For details on how to create an ILB App Service environment, see [Create an ASE in the Azure portal][creation] and [Create an ASE with ARM][createfromtemplate].
+For details on how to create an ILB App Service environment, see [Create an ASE in the Azure portal][creation] and [Create an ASE with ARM template][createfromtemplate].
 
 * After ILB ASE is created, the default domain is `<YourAseName>.appserviceenvironment.net`.
 
@@ -108,7 +108,7 @@ In the Azure portal, select **New** > **Network** > **Application Gateway** to c
 
 4. Configuration setting
 
-    In **Configuration** setting, you need to add a routing rule by clicking **Add a routing rule** icon.
+    In **Configuration** setting, you need to add a routing rule by selecting **Add a routing rule** icon.
 
     :::image type="content" source="./media/integrate-with-application-gateway/configuration.png" alt-text="Screenshot of adding a routing rule in configuration setting.":::
 
@@ -143,9 +143,9 @@ In the Azure portal, select **New** > **Network** > **Application Gateway** to c
         | Host type      | Multiple/Wildcard                 | Set to multiple or wildcard website name if listener type is set to multi-sites. |
         | Host name      | For example:  `app.asabuludemo.com` | Set to a routable domain name for App Service              |
         
-        :::image type="content" source="./media/integrate-with-application-gateway/https-routing-rule.png" alt-text="H T T P S listener of the application gateway Routing Rule.":::
+        :::image type="content" source="./media/integrate-with-application-gateway/https-routing-rule.png" alt-text="HTTPS listener of the application gateway Routing Rule.":::
 
-    * You have to configure a **Backend Pool** and **HTTP setting** in **Backend targets**. The Backend pool was configured in previously steps. Click **Add new** link to add an HTTP setting.
+    * You have to configure a **Backend Pool** and **HTTP setting** in **Backend targets**. The Backend pool was configured in previously steps. Select **Add new** link to add an HTTP setting.
 
         :::image type="content" source="./media/integrate-with-application-gateway/add-new-http-setting.png" alt-text="Screenshot of adding new link to add an H T T P setting.":::
 
@@ -166,7 +166,7 @@ In the Azure portal, select **New** > **Network** > **Application Gateway** to c
 
 ## Configure an application gateway integration with ILB ASE
 
-To access ILB ASE from the application gateway, you need to check if a virtual network link to private DNS zone. If there is no virtual network linked to your application gateway's VNet, add a virtual network link with following steps.
+To access ILB ASE from the application gateway, you need to check if a virtual network link to private DNS zone. If there's no virtual network linked to your application gateway's VNet, add a virtual network link with following steps.
 
 ### Configure virtual network links with a private DNS zone
 

articles/app-service/manage-custom-dns-migrate-domain.md

@@ -13,7 +13,7 @@ ms.custom: seodec18
 
 This article shows you how to migrate an active DNS name to [Azure App Service](../app-service/overview.md) without any downtime.
 
-When you migrate a live site and its DNS domain name to App Service, that DNS name is already serving live traffic. You can avoid downtime in DNS resolution during the migration by binding the active DNS name to your App Service app pre-emptively.
+When you migrate a live site and its DNS domain name to App Service, that DNS name is already serving live traffic. You can avoid downtime in DNS resolution during the migration by binding the active DNS name to your App Service app preemptively.
 
 If you're not worried about downtime in DNS resolution, see [Map an existing custom DNS name to Azure App Service](app-service-web-tutorial-custom-domain.md).
 
@@ -23,7 +23,7 @@ To complete the steps, [make sure that your App Service app isn't in FREE tier](
 
 ## 1. Get a domain verification ID
 
-When you bind a custom domain pre-emptively, you accomplish both of the following before making any changes to
+When you bind a custom domain preemptively, you accomplish both of the following before making any changes to
 your existing DNS records:
 
 - Verify domain ownership by adding a domain verification ID with your domain provider.
@@ -81,7 +81,7 @@ Add a TXT record for domain verification. The hostname for the TXT record depend
 
 1. You should see the custom domain added to the list. You may also see a red X with **No binding**. 
 
-    Sinc you selected **Add certificate later**, you see a red X with **No binding**. It will remain until you [add a private certificate for the domain](configure-ssl-certificate.md) and [configure the binding](configure-ssl-bindings.md).
+    Since you selected **Add certificate later**, you see a red X with **No binding**. It will remain until you [add a private certificate for the domain](configure-ssl-certificate.md) and [configure the binding](configure-ssl-bindings.md).
 
     :::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain-preempt-complete.png" alt-text="A screenshot showing the custom domains page with the new secured custom domain." border="true":::
 
@@ -114,10 +114,10 @@ DNS queries should start resolving to your App Service app immediately after DNS
 
 ## Frequently asked questions
 
-- [Can I add a App Service managed certificate when migrating a live domain?](#can-i-add-a-app-service-managed-certificate-when-migrating-a-live-domain)
+- [Can I add an App Service managed certificate when migrating a live domain?](#can-i-add-an-app-service-managed-certificate-when-migrating-a-live-domain)
 - [How do I migrate a domain from another app?](#how-do-i-migrate-a-domain-from-another-app)
 
-#### Can I add a App Service managed certificate when migrating a live domain?
+#### Can I add an App Service managed certificate when migrating a live domain?
 
 You can add an App Service managed certificate to a migrated live domain, but only after you [remap the active DNS name](#4-remap-the-active-dns-name). To add the App Service managed certificate, see [Create a free managed certificate](configure-ssl-certificate.md#create-a-free-managed-certificate).
 

articles/app-service/media/app-service-web-tutorial-custom-domain/mapping-information.png

@@ -63,13 +63,13 @@ If you've installed Visual Studio 2019 already:
 
 1. In **Solution Explorer**, right-click the **myFirstAzureWebApp** project and select **Publish**. 
 
-1. In **Publish**, select **Azure** and click **Next**.
+1. In **Publish**, select **Azure** and select **Next**.
 
 1. Your options depend on whether you're signed in to Azure already and whether you have a Visual Studio account linked to an Azure account. Select either **Add an account** or **Sign in** to sign in to your Azure subscription. If you're already signed in, select the account you want.
 
    ![Sign in to Azure](./media/quickstart-dotnetcore/sign-in-azure-vs2019.png)
 
-1. To the right of **App Service instances**, click **+**.
+1. To the right of **App Service instances**, select **+**.
 
    ![New App Service app](./media/quickstart-dotnetcore/publish-new-app-service.png)
 
@@ -102,7 +102,7 @@ If you've installed Visual Studio 2019 already:
 
 1. Wait for the wizard to finish creating Azure resources. Select **Finish** to close the wizard.
 
-1. In the **Publish** page, click **Publish** to deploy your project. 
+1. In the **Publish** page, select **Publish** to deploy your project. 
 
     <details>
         <summary>What's Visual Studio doing?</summary>
@@ -318,7 +318,7 @@ http://<app_name>.azurewebsites.net
     
     <details>
     <summary>What's <code>az webapp up</code> doing this time?</summary>
-    The first time you ran the command, it saved the app name, resource group, and App Service plan in the <i>.azure/config</i> file from the project root. When you run it again from the project root, it uses the values saved in <i>.azure/config</i>, detects that the App Service resources already exists, and performs Zip deploy again.
+    The first time you ran the command, it saved the app name, resource group, and App Service plan in the <i>.azure/config</i> file from the project root. When you run it again from the project root, it uses the values saved in <i>.azure/config</i>, detects that the App Service resources already exist, and performs Zip deploy again.
     </details>
 
 1. Once deployment has completed, **hit refresh** in the browser window that previously opened.
@@ -333,7 +333,7 @@ http://<app_name>.azurewebsites.net
 
 1. Go to the <a href="https://portal.azure.com" target="_blank">Azure portal</a>.
 
-1. From the left menu, click **App Services**, and then click the name of your Azure app.
+1. From the left menu, select **App Services**, and then select the name of your Azure app.
 
     :::image type="content" source="./media/quickstart-dotnetcore/portal-app-service-list-up.png" alt-text="Screenshot of the App Services page showing an example Azure app selected.":::
 

articles/app-service/quickstart-dotnetcore-uiex.md

@@ -33,7 +33,7 @@ This quickstart configures an App Service app in the **Free** tier and incurs no
 
 - Have an Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?utm_source=campaign&utm_campaign=vscode-tutorial-app-service-extension&mktingSource=vscode-tutorial-app-service-extension).
 - Install [Node.js LTS and npm](https://nodejs.org). Run the command `node --version` to verify that Node.js is installed.
-- Install <a href="/cli/azure/install-azure-cli" target="_blank">Azure CLI</a>, with which you run commands in any shell to provision and configure Azure resources.
+- Install <a href="/cli/azure/install-azure-cli" target="_blank">Azure CLI</a>, with which you run commands in any shell to create and configure Azure resources.
 
 ::: zone-end
 
@@ -42,7 +42,7 @@ This quickstart configures an App Service app in the **Free** tier and incurs no
 
 - Have an Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?utm_source=campaign&utm_campaign=vscode-tutorial-app-service-extension&mktingSource=vscode-tutorial-app-service-extension).
 - Install [Node.js LTS and npm](https://nodejs.org). Run the command `node --version` to verify that Node.js is installed.
-- Have a FTP client (for example, [FileZilla](https://filezilla-project.org)), to connect to your app.
+- Have an FTP client (for example, [FileZilla](https://filezilla-project.org)), to connect to your app.
 
 ::: zone-end
 ## Create your Node.js application
@@ -117,10 +117,10 @@ Before you continue, ensure that you have all the prerequisites installed and co
 2. Right-click on App Services and select **Create new Web App**. A Linux container is used by default. 
 1. Type a globally unique name for your web app and press **Enter**. The name must be unique across all of Azure and use only alphanumeric characters ('A-Z', 'a-z', and '0-9') and hyphens ('-').
 1. In Select a runtime stack, select the Node.js version you want. An **LTS** version is recommended.
-1. In Select a pricing tier, select **Free (F1)** and wait for the resources to be provisioned in Azure.
+1. In Select a pricing tier, select **Free (F1)** and wait for the resources to be created in Azure.
 1. In the popup **Always deploy the workspace "myExpressApp" to \<app-name>"**, select **Yes**. This way, as long as you're in the same workspace, Visual Studio Code deploys to the same App Service app each time.
 
-    While Visual Studio Code provisions the Azure resources and deploys the code, it shows [progress notifications](https://code.visualstudio.com/api/references/extension-guidelines#notifications).
+    While Visual Studio Code creates the Azure resources and deploys the code, it shows [progress notifications](https://code.visualstudio.com/api/references/extension-guidelines#notifications).
 
 1. Once deployment completes, select **Browse Website** in the notification popup. The browser should display the Express default page.
 
@@ -133,10 +133,10 @@ Before you continue, ensure that you have all the prerequisites installed and co
 1. Select **Windows** for the operating system.
 1. Select the location you want to serve your app from. For example, *West Europe*.
 1. Select **Create new App Service plan**, then enter a name for the plan (such as *AppServiceQS-plan*), then select **F1 Free** for the pricing tier.
-1. For **Select an Application Insights resource for your app**, select **Skip for now** and wait the resources to be provisioned in Azure.
+1. For **Select an Application Insights resource for your app**, select **Skip for now** and wait the resources to be created in Azure.
 1. In the popup **Always deploy the workspace "myExpressApp" to \<app-name>"**, select **Yes**. This way, as long as you're in the same workspace, Visual Studio Code deploys to the same App Service app each time.
 
-    While Visual Studio Code provisions the Azure resources and deploys the code, it shows [progress notifications](https://code.visualstudio.com/api/references/extension-guidelines#notifications).
+    While Visual Studio Code creates the Azure resources and deploys the code, it shows [progress notifications](https://code.visualstudio.com/api/references/extension-guidelines#notifications).
 
     > [!NOTE]
     > When deployment completes, your Azure app doesn't run yet because your project root doesn't have a *web.config*. Follow the remaining steps to generate it automatically. For more information, see [You do not have permission to view this directory or page](configure-language-nodejs.md#you-do-not-have-permission-to-view-this-directory-or-page).

articles/app-service/quickstart-nodejs.md

@@ -14,5 +14,5 @@ ms.custom: "include file"
 |-|-|
 | Custom domain | The domain name to add the TLS/SSL binding for. |
 | Private Certificate Thumbprint | The certificate to bind. |
-| TLS/SSL Type | <ul><li>**[SNI SSL](https://en.wikipedia.org/wiki/Server_Name_Indication)** - Multiple SNI SSL bindings may be added. This option allows multiple TLS/SSL certificates to secure multiple domains on the same IP address. Most modern browsers (including Internet Explorer, Chrome, Firefox, and Opera) support SNI (for more information, see [Server Name Indication](https://wikipedia.org/wiki/Server_Name_Indication)).</li><li>**IP SSL** - Only one IP SSL binding may be added. This option allows only one TLS/SSL certificate to secure a dedicated public IP address. After you configure the binding, follow the steps in [Remap records for IP SSL](../articles/app-service/configure-ssl-bindings.md#remap-records-for-ip-ssl).<br/>IP SSL is supported only in **Standard** tier or above. </li></ul> |
+| TLS/SSL Type | - **[SNI SSL](https://en.wikipedia.org/wiki/Server_Name_Indication)**: Multiple SNI SSL bindings may be added. This option allows multiple TLS/SSL certificates to secure multiple domains on the same IP address. Most modern browsers (including Internet Explorer, Chrome, Firefox, and Opera) support SNI (for more information, see [Server Name Indication](https://wikipedia.org/wiki/Server_Name_Indication)).<br />- **IP SSL**: Only one IP SSL binding may be added. This option allows only one TLS/SSL certificate to secure a dedicated public IP address. After you configure the binding, follow the steps in [Remap records for IP SSL](../articles/app-service/configure-ssl-bindings.md#remap-records-for-ip-ssl).<br/>IP SSL is supported only in **Standard** tier or above. |