prmerger feedback

cephalin · cephalin · commit 16706b42c542 · 2024-01-30T09:21:44.000+01:00
diff --git a/articles/app-service/deploy-continuous-deployment.md b/articles/app-service/deploy-continuous-deployment.md
@@ -95,7 +95,7 @@ For Windows apps, you can manually configure continuous deployment from a cloud
 
 ## What are the build providers?
 
-Depending on your deployment source in the Deployment Center, you might see a few options to select for build providers. Build providers help you build an CI/CD solution with Azure App Service by automating build, test, and deployment.
+Depending on your deployment source in the Deployment Center, you might see a few options to select for build providers. Build providers help you build a CI/CD solution with Azure App Service by automating build, test, and deployment.
 
 You're not limited to the build provider options found in the Deployment Center, but App Service lets you set them up quickly and offers some integrated deployment logging experience.
 
diff --git a/articles/app-service/deploy-github-actions.md b/articles/app-service/deploy-github-actions.md
@@ -22,7 +22,7 @@ Get started with [GitHub Actions](https://docs.github.com/en/actions/learn-githu
 
 GitHub Actions deployment is integrated into the default [app creation wizard](https://portal.azure.com/#create/Microsoft.WebSite). You just need to set **Continuous deployment** to **Enable** in the Deployment tab, and configure the organization, repository, and branch you want.
 
-:::image type="content" source="media/deploy-github-actions/create-wizard-deployment.png" alt-text="A screenshot showing how to enable GitHub Actions deployment in the App Service create wizard":::
+:::image type="content" source="media/deploy-github-actions/create-wizard-deployment.png" alt-text="A screenshot showing how to enable GitHub Actions deployment in the App Service create wizard.":::
 
 When you enable continuous deployment, the app creation wizard automatically picks the authentication method based on the basic authentication selection and configures your app and your GitHub repository accordingly:
 
@@ -32,7 +32,7 @@ When you enable continuous deployment, the app creation wizard automatically pic
 |Enable| [Basic authentication](configure-basic-auth-disable.md) |
 
 > [!NOTE]
-> If you receive an error when creating your app saying that your Azure account doesn't have certain permissions, it may not have [the required permissions to create and configure the user-assigned identity](deploy-continuous-deployment.md#why-do-i-see-the-error-you-do-not-have-sufficient-permissions-on-this-app-to-assign-role-based-access-to-a-managed-identity-and-configure-federated-credentials). For an alternative, see [Set up GitHub Actions deployment from the Deployment Center](#set-up-github-actions-deployment-from-the-deployment-center)
+> If you receive an error when creating your app saying that your Azure account doesn't have certain permissions, it may not have [the required permissions to create and configure the user-assigned identity](deploy-continuous-deployment.md#why-do-i-see-the-error-you-do-not-have-sufficient-permissions-on-this-app-to-assign-role-based-access-to-a-managed-identity-and-configure-federated-credentials). For an alternative, see [Set up GitHub Actions deployment from the Deployment Center](#set-up-github-actions-deployment-from-the-deployment-center).
 
 ## Set up GitHub Actions deployment from the Deployment Center
 
@@ -48,9 +48,9 @@ For more information, see [Continuous deployment to Azure App Service](deploy-co
 
 You can also deploy a workflow without using the Deployment Center.
 
-- [1. Generate deployment credentials](#1-generate-deployment-credentials)
-- [2. Configure the GitHub secret](#2-configure-the-github-secret)
-- [3. Add the workflow file to your GitHub repository](#3-add-the-workflow-file-to-your-github-repository)
+1. [Generate deployment credentials](#1-generate-deployment-credentials)
+1. [Configure the GitHub secret](#2-configure-the-github-secret)
+1. [Add the workflow file to your GitHub repository](#3-add-the-workflow-file-to-your-github-repository)
 
 ### 1. Generate deployment credentials
 
@@ -218,7 +218,7 @@ At a minimum, the workflow file would have the following distinct steps:
 1. Build the web app.
 1. Deploy the web app.
 
-To deploy your code to an App Service app, you use the [azure/webapps-deploy@v3](https://github.com/Azure/webapps-deploy/tree/releases/v3) action. The action requires the name of your web app in `app-name` and, depending on your language stack, the path of the a *.zip, *.war, *.jar, or folder to deploy in `package`. For a complete list of possible inputs for the `azure/webapps-deploy@v3` action, see the [action.yml](https://github.com/Azure/webapps-deploy/blob/releases/v3/action.yml) definition.
+To deploy your code to an App Service app, you use the [azure/webapps-deploy@v3](https://github.com/Azure/webapps-deploy/tree/releases/v3) action. The action requires the name of your web app in `app-name` and, depending on your language stack, the path of a *.zip, *.war, *.jar, or folder to deploy in `package`. For a complete list of possible inputs for the `azure/webapps-deploy@v3` action, see the [action.yml](https://github.com/Azure/webapps-deploy/blob/releases/v3/action.yml) definition.
 
 The following examples show the part of the workflow that builds the web app, in different supported languages.
 
@@ -236,8 +236,6 @@ The following examples show the part of the workflow that builds the web app, in
 
 -----
 
-## Frequently asked questions
-
 ## Next steps
 
 Check out references on Azure GitHub Actions and workflows:
diff --git a/articles/app-service/quickstart-php.md b/articles/app-service/quickstart-php.md
@@ -77,7 +77,7 @@ You can create the web app using the [Azure CLI](/cli/azure/get-started-with-azu
 
 ### [Azure CLI](#tab/cli)
 
-Azure CLI has a command [`az webapp up`](/cli/azure/webapp#az-webapp-up) that creates the necessary resources and deploy your application in a single step.
+Azure CLI has a command [`az webapp up`](/cli/azure/webapp#az-webapp-up) that creates the necessary resources and deploys your application in a single step.
 
 In the terminal, deploy the code in your local folder using the  [`az webapp up`](/cli/azure/webapp#az-webapp-up) command:
 
@@ -142,12 +142,12 @@ Browse to the deployed application in your web browser at the URL `http://<app-n
     - Under **Runtime stack** select *PHP 8.2*.
     - Under **Operating System**, select *Linux*.
     - Under **Region**, select an Azure region close to you.
-    - **App Service Plan**: Create an app service plan named *myAppServicePlan*.
+    - Under **App Service Plan**, create an app service plan named *myAppServicePlan*.
     - Under **Pricing plan**, select **Free F1**.
     
     :::image type="content" source="./media/quickstart-php/app-service-details-php.png" lightbox="./media/quickstart-php/app-service-details-php.png" alt-text="Screenshot of new App Service app configuration for PHP in the Azure portal.":::
 
-1. Select the **Deployment** tab at the top of the page
+1. Select the **Deployment** tab at the top of the page.
 
 1. Under **GitHub Actions settings**, set **Continuous deployment** to *Enable*.
 
@@ -204,10 +204,10 @@ The PHP sample code is running in an Azure App Service.
 
 1. On your repo page, press `.` to start Visual Studio Code within your browser.
 
-![Screenshot of the forked php-docs-hello-world repo in GitHub with instructions to press the period key on this screen.](media/quickstart-php/forked-github-repo-press-period.png)
+    ![Screenshot of the forked php-docs-hello-world repo in GitHub with instructions to press the period key on this screen.](media/quickstart-php/forked-github-repo-press-period.png)
 
-> [!NOTE]
-> The URL will change from GitHub.com to GitHub.dev. This feature only works with repos that have files. This does not work on empty repos.
+    > [!NOTE]
+    > The URL will change from GitHub.com to GitHub.dev. This feature only works with repos that have files. This does not work on empty repos.
 
 1. Edit **index.php** so that it shows "Hello Azure!" instead of "Hello World!"
 
diff --git a/articles/app-service/tutorial-multi-region-app.md b/articles/app-service/tutorial-multi-region-app.md
@@ -45,7 +45,7 @@ To complete this tutorial:
 
 ## Create two instances of a web app
 
-You need two instances of a web app that run in different Azure regions for this tutorial. You use the [region pair](../availability-zones/cross-region-replication-azure.md#azure-paired-regions) East US/West US as your two regions and create two empty web apps. Feel free to choose you're own regions if needed.
+You need two instances of a web app that run in different Azure regions for this tutorial. You use the [region pair](../availability-zones/cross-region-replication-azure.md#azure-paired-regions) East US/West US as your two regions and create two empty web apps. Feel free to choose your own regions if needed.
 
 To make management and clean-up simpler, you use a single resource group for all resources in this tutorial. Consider using separate resource groups for each region/resource to further isolate your resources in a disaster recovery situation.
 
@@ -469,7 +469,7 @@ Now that you have a service principal that can access your App Service apps, edi
 
 ### How does slot traffic routing allow me to test updates that I make to my apps?
 
-Traffic routing with slots allows you to direct a predefined portion of your user traffic to each slot. Initially, 100% of traffic is directed to the production site. However, you have the ability, for example, to send 10% of your traffic to your staging slot. If you configure slot traffic routing in this way, when users try to access your app, 10% of them is automatically routed to the staging slot with no changes to your Front Door instance. To learn more about slot swaps and staging environments in App Service, see [Set up staging environments in Azure App Service](deploy-staging-slots.md).
+Traffic routing with slots allows you to direct a predefined portion of your user traffic to each slot. Initially, 100% of traffic is directed to the production site. However, you have the ability, for example, to send 10% of your traffic to your staging slot. If you configure slot traffic routing in this way, when users try to access your app, 10% of them are automatically routed to the staging slot with no changes to your Front Door instance. To learn more about slot swaps and staging environments in App Service, see [Set up staging environments in Azure App Service](deploy-staging-slots.md).
 
 ### How do I move my code from my staging slot to my production slot?
 
@@ -483,7 +483,7 @@ az webapp deployment slot swap --resource-group MyResourceGroup -name <web-app-n
 
 After a few minutes, you can navigate to your Front Door's endpoint to validate the slot swap succeeded.
 
-At this point, your apps are up and running and any changes you make to your application source code automatically triggers an update to both of your staging slots. You can then repeat the slot swap process when you're ready to move that code into production.
+At this point, your apps are up and running and any changes you make to your application source code automatically trigger an update to both of your staging slots. You can then repeat the slot swap process when you're ready to move that code into production.
 
 ### How else can I use Azure Front Door in my multi-region deployments?
 
