Edit pass on GitHub Actions CI/CD Publish (#8644)

* edits

* Update tutorial-import-publish-settings-iis.md

* removed unused screenshot

Author: Mikejo5000

docs/debugger/debug-using-the-just-in-time-debugger.md

@@ -2,7 +2,7 @@
 title: Debug using the Just-In-Time Debugger | Microsoft Docs
 description: Debug using the Just-In-Time Debugger in Visual Studio. Just-In-Time debugging can launch Visual Studio automatically when an app errors or crashes.
 ms.custom: SEO-VS-2020
-ms.date: 09/24/2018
+ms.date: 08/24/2021
 ms.topic: how-to
 helpviewer_keywords: 
   - debugging [Visual Studio], Just-In-Time

docs/debugger/just-in-time-debugging-in-visual-studio.md

@@ -2,7 +2,7 @@
 title: "Disable the Just-In-Time Debugger | Microsoft Docs"
 description: The Just-In-Time Debugger dialog box may open when an error occurs in an app. Learn what you can do when this happens, and ways to prevent it.
 ms.custom: SEO-VS-2020
-ms.date: "05/23/2018"
+ms.date: "08/24/2021"
 ms.topic: "troubleshooting"
 helpviewer_keywords:
   - "debugging [Visual Studio], Just-In-Time"

docs/deployment/azure-deployment-using-github-actions.md

@@ -1,8 +1,8 @@
 ---
 title: "Deploy to Azure using GitHub Actions"
 description: "Learn to deploy your application to Azure using GitHub Actions workflows created by Visual Studio"
-ms.date: 08/31/2021
-ms.topic: tutorial
+ms.date: 09/03/2021
+ms.topic: how-to
 helpviewer_keywords:
   - "deployment, GitHub Actions"
   - GitHub Actions, publish
@@ -16,18 +16,20 @@ ms.workload:
 ---
 
 # Deploy your application to Azure using GitHub Actions workflows created by Visual Studio
+
 Starting in Visual Studio 2019 version 16.11, you can create new GitHub Action workflows for .NET projects hosted on GitHub.com.
 
 ## How does it work?
-In Solution Explorer, right-click your GitHub.com hosted project and select **Publish**
+
+In Solution Explorer, right-click your GitHub.com hosted project and choose **Publish**.
 
 ![right-click > Publish](./media/solution-explorer-publish.png)
 
-On the next screen, select **Azure** and **Next**
+On the next screen, select **Azure** and then choose **Next**.
 
 ![select Azure](./media/wizard-azure.png)
 
-Depending on your [project type](#which-project-types-are-supported) you get a different list of Azure services to pick from. Pick one of the [supported Azure services](#which-azure-services-are-supported) that suits your needs.
+Depending on your [project type](#which-project-types-are-supported), you get a different list of Azure services to pick from. Pick one of the [supported Azure services](#which-azure-services-are-supported) that fits your needs.
 
 ![select the appropriate Azure service for your project](./media/wizard-pick-azure-service.png)
 
@@ -39,33 +41,36 @@ Visual Studio generates a new GitHub Actions workflow and asks you to commit it
 
 ![commit and push](./media/summary-commit-and-push.png)
 
-If you complete this step using the [built-in Git tooling](../version-control/git-with-visual-studio.md#git-changes-window) Visual Studio will detect the execution of the workflow.
+If you complete this step using the [built-in Git tooling](../version-control/git-with-visual-studio.md#git-changes-window), Visual Studio will detect the execution of the workflow.
 
 ![workflow is running](./media/summary-workflow-running.png)
 
 ## Setting the GitHub secrets
+
 For the generated workflow to successfully deploy to Azure, it may require access to a [publish profile](/azure/app-service/deploy-github-actions?tabs=applevel#configure-the-github-secret) 
 
 ![one github secret](./media/summary-one-github-secret.png)
 
-A successful deployment may also require access to a [service principal](/azure/app-service/deploy-github-actions?tabs=userlevel#configure-the-github-secret)
+A successful deployment may also require access to a [service principal](/azure/app-service/deploy-github-actions?tabs=userlevel#configure-the-github-secret).
 
 ![two github secrets](./media/summary-two-github-secrets.png)
 
-In all cases, Visual Studio tries to set the GitHub secret on your behalf with the correct value. If it fails, it will let you know and offer you the opportunity to try again.
+In all cases, Visual Studio tries to set the GitHub secret for you with the correct value. If it fails, it will let you know and give you the opportunity to try again.
 
 ![github secret missing](./media/summary-one-github-secret-missing.png)
 
-If it fails to set the secret again, Visual Studio offers you the opportunity to get access to the secret manually, so you can complete the process through your repo's page on github.com.
+If it fails to set the secret again, Visual Studio gives you the opportunity to get access to the secret manually, so you can complete the process through your repo's page on github.com.
 
 ![set missing github secret](./media/summary-set-github-secret.png)
 
 ## Which project types are supported?
- * ASP.NET Core
- * ASP.NET 5 and above
- * Azure Functions
+
+* ASP.NET Core
+* ASP.NET 5 and above
+* Azure Functions
 
 ## Which Azure services are supported?
+
 * Azure Web Apps
 * Azure Functions
 * Azure API Management

docs/deployment/tutorial-import-publish-settings-iis.md

@@ -47,7 +47,11 @@ A publish settings file (*\*.publishsettings*) is different than a publishing pr
     If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/) page to install it for free.
 ::: moniker-end
 
-* On your server, you must be running Windows Server 2012, Windows Server 2016, or Windows Server 2019, and you must have the [IIS Web Server role](/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45) correctly installed (required to generate the publish settings file (*\*.publishsettings*)). Either ASP.NET 4.5 or ASP.NET Core must also be installed on the server. To set up ASP.NET 4.5, see [IIS 8.0 Using ASP.NET 3.5 and ASP.NET 4.5](/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45). To set up ASP.NET Core, see [Host ASP.NET Core on Windows with IIS](/aspnet/core/publishing/iis?tabs=aspnetcore2x#iis-configuration). For ASP.NET Core, make sure you configure the Application Pool to use **No Managed Code**, as described in the article.
+* On your server, you must be running Windows Server 2012, Windows Server 2016, or Windows Server 2019, and you must have the [IIS Web Server role](/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45#solution) correctly installed (required to generate the publish settings file (*\*.publishsettings*)). Either ASP.NET 4.5 or ASP.NET Core must also be installed on the server.
+
+  * To set up ASP.NET 4.5, see [IIS 8.0 Using ASP.NET 3.5 and ASP.NET 4.5](/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45).
+
+  * To set up ASP.NET Core, see [Host ASP.NET Core on Windows with IIS](/aspnet/core/publishing/iis?tabs=aspnetcore2x#iis-configuration). For ASP.NET Core, make sure you configure the Application Pool to use **No Managed Code**, as described in the article.
 
 ## Create a new ASP.NET project in Visual Studio
 

docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md

@@ -2,7 +2,7 @@
 title: Configure unit tests with a .runsettings file
 description: Learn how to use the .runsettings file in Visual Studio to configure unit tests that are run from the command line, from the IDE, or in a build workflow.
 ms.custom: SEO-VS-2020
-ms.date: 07/15/2020
+ms.date: 11/06/2020
 ms.topic: conceptual
 ms.author: mikejo
 manager: jmartens