edits

Author: ktoliver

articles/app-service/app-service-configuration-references.md

@@ -241,7 +241,7 @@ Here's a demonstration template for a function app that has App Configuration re
 
 If a reference isn't resolved properly, the reference value is used instead. For an application setting in this scenario, an environment variable that uses the syntax `@Microsoft.AppConfiguration(...)` is created. The reference might cause an error because the application was expecting a configuration value.
 
-This error most commonly is the result of a misconfiguration of the [App Configuration access policy](#granting-your-app-access-to-app-configuration). But it also might occur if there's a syntax error in the reference or if the configuration key-value pair does not exist in the store.
+This error most commonly is the result of a misconfiguration of the [App Configuration access policy](#grant-app-access-to-app-configuration). But it also might occur if there's a syntax error in the reference or if the configuration key-value pair does not exist in the store.
 
 ## Related content
 

articles/app-service/deploy-local-git.md

@@ -138,6 +138,8 @@ Set-AzResource -PropertyObject $PropertiesObject -ResourceGroupName <group-name>
 
 1. In the Azure portal, go to your app to verify that the content is deployed.
 
+<a name="change-deployment-branch"></a>
+
 ## Change the deployment branch
 
 When you push commits to your App Service repository, App Service deploys the files in the `master` branch by default. Because many Git repositories are moving from `master` to `main`, ensure that you push to the correct branch in the App Service repository in one of two ways:

includes/app-service-security-intro.md

@@ -5,13 +5,13 @@ ms.topic: include
 ms.date: 04/15/2020
 ms.author: cephalin
 ---
-The platform components of App Service, including Azure VMs, storage, network connections, web frameworks, management and integration features, are actively secured and hardened. App Service goes through vigorous compliance checks on a continuous basis to make sure that:
+The platform components of Azure App Service, including Azure virtual machines (VMs), storage, network connections, web frameworks, and management and integration features are actively secured and hardened. App Service goes through vigorous compliance checks on a continuous basis to make sure that:
 
-- Your app resources are [secured](https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox) from the other customers' Azure resources.
-- [VM instances and runtime software are regularly updated](/azure/app-service/overview-patch-os-runtime) to address newly discovered vulnerabilities. 
-- Communication of secrets (such as connection strings) between your app and other Azure resources (such as [SQL Database](https://azure.microsoft.com/services/sql-database/)) stays within Azure and doesn't cross any network boundaries. Secrets are always encrypted when stored.
-- All communication over the App Service connectivity features, such as [hybrid connection](/azure/app-service/app-service-hybrid-connections), is encrypted. 
-- Connections with remote management tools like Azure PowerShell, Azure CLI, Azure SDKs, REST APIs, are all encrypted.
-- 24-hour threat management protects the infrastructure and platform against malware, distributed denial-of-service (DDoS), man-in-the-middle (MITM), and other threats.
+- Your app resources are [secured](https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox) from other customers' Azure resources.
+- [VM instances and runtime software are regularly updated](/azure/app-service/overview-patch-os-runtime) to address newly discovered vulnerabilities.
+- Communication of secrets (such as connection strings) between your app and other Azure resources (such as [Azure SQL Database](https://azure.microsoft.com/services/sql-database/)) stays within Azure and doesn't cross any network boundaries. Secrets are always encrypted when stored.
+- All communication over the App Service connectivity features, such as [hybrid connection](/azure/app-service/app-service-hybrid-connections), is encrypted.
+- Connections with remote management tools like Azure PowerShell, the Azure CLI, Azure SDKs, and REST APIs, are all encrypted.
+- 24-hour threat management protects the infrastructure and platform against malware, distributed denial-of-service (DDoS) attacks, man-in-the-middle (MITM) attacks, and other threats.
 
-For more information on infrastructure and platform security in Azure, see [Azure Trust Center](https://azure.microsoft.com/overview/trusted-cloud/).
+For more information on infrastructure and platform security in Azure, see the [Azure Trust Center](https://azure.microsoft.com/overview/trusted-cloud/).

includes/app-service-ssl-prepare-app.md

@@ -20,21 +20,21 @@ To create custom TLS/SSL bindings or enable client certificates for your App Ser
 
    ![Screenshot of Azure portal, search box, and "App Services" selected.](./media/app-service-ssl-prepare-app/app-services.png)
 
-1. On the **App Services** page, select your web app's name.
+1. On the **App Services** pane, select your web app's name.
 
    ![Screenshot of the App Services page in Azure portal showing a list of all running web apps, with the first app in the list highlighted.](./media/app-service-ssl-prepare-app/select-app.png)
 
    You're now on your web app's management page.
 
 ### Check the pricing tier
 
-1. In the left menu for your web app, under the **Settings** section, select **Scale up (App Service plan)**.
+1. On the resource menu for your web app, in the **Settings** section, select **Scale up (App Service plan)**.
 
    ![Screenshot of web app menu, "Settings" section, and "Scale up (App Service plan)" selected.](./media/app-service-ssl-prepare-app/scale-up-menu.png)
 
-1. Make sure that your web app isn't in the **F1** or **D1** tier, which doesn't support custom TLS/SSL.
+1. Make sure that your web app isn't in the **F1** or **D1** tier, which don't support custom TLS/SSL.
 
-1. If you need to scale up, follow the steps in the next section. Otherwise, close the **Scale up** page, and skip the [Scale up your App Service plan section](#scale-up-your-app-service-plan).
+1. If you need to scale up, follow the steps in the next section. Otherwise, close the **Scale up** pane, and skip the [Scale up your App Service plan section](#scale-up-your-app-service-plan).
 
 ### Scale up your App Service plan