Updated per Review feedback

John-Hart · John-Hart · commit 7ef4f3a6ec1b · 2020-11-09T17:29:48.000-08:00
diff --git a/docs/deployment/building-clickonce-applications-from-the-command-line.md b/docs/deployment/building-clickonce-applications-from-the-command-line.md
@@ -174,7 +174,6 @@ For .NET windows applications, this setting remains in the project file
 ::: moniker-end
 
 - `UpdateIntervalUnits` specifies whether the `UpdateInterval` value is in units of hours, days, or weeks.
-   This setting i
 ::: moniker range=">=vs-2019"
    For .NET Core 3.1, or later, this setting is not supported.
 ::: moniker-end
diff --git a/docs/deployment/choosing-a-clickonce-update-strategy.md b/docs/deployment/choosing-a-clickonce-update-strategy.md
@@ -115,7 +115,7 @@ ms.workload:
  No prompting for trust levels will occur if you use Trusted Application Deployment. For more information, see [Trusted application deployment overview](../deployment/trusted-application-deployment-overview.md).
 
 ## See also
- \<xref:System.Deployment.Application>
+- <xref:System.Deployment.Application>
 - [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md)
 - [Choose a ClickOnce deployment strategy](../deployment/choosing-a-clickonce-deployment-strategy.md)
 - [Secure ClickOnce applications](../deployment/securing-clickonce-applications.md)
diff --git a/docs/deployment/deploying-applications-services-and-components-resources.md b/docs/deployment/deploying-applications-services-and-components-resources.md
@@ -25,7 +25,7 @@ Get help for your deployment task:
 
 - Not sure what deployment option to choose? See [What publishing options are right for me?](#what-publishing-options-are-right-for-me)
 - For help with deployment issues for Azure App Service or IIS, see [Troubleshoot ASP.NET Core on Azure App Service and IIS](/aspnet/core/test/troubleshoot-azure-iis).
-- For help to configure .NET deployment settings, see [Configure .NET deployment settings](#configure-net-deployment-settings).
+- For help with configuring .NET deployment settings, see [Configure .NET deployment settings](#configure-net-deployment-settings).
 - To deploy to a new target, if you have previously created a publish profile, select **New** from the **Publish** window for a configured profile.
 
    ![Create a new publish profile](../deployment/media/create-a-new-publish-profile.png)
@@ -110,16 +110,16 @@ For more information:
 
 ### Azure Virtual Machine
 
-[Azure Virtual Machines (VMs)](https://azure.microsoft.com/documentation/services/virtual-machines/) let you create and manage any number of computing resources in the cloud. By assuming responsibility for all software and updates on the VMs, you can customize them as much as desired as required by your application. You can access the virtual machines directly through Remote Desktop, and each one will maintain its assigned IP address as long as desired.
+[Azure Virtual Machines (VMs)](https://azure.microsoft.com/documentation/services/virtual-machines/) lets you create and manage any number of computing resources in the cloud. By assuming responsibility for all software and updates on the VMs, you can customize them as much as desired as required by your application. You can access the virtual machines directly through Remote Desktop, and each one will maintain its assigned IP address as long as desired.
 
 Scaling an application that's hosted on virtual machines involves spinning up additional VMs according to demand and then deploying the necessary software. This additional level of control lets you scale differently in different global regions. For example, if your application is serving employees in a variety of regional offices, you can scale your VMs according to the number of employees in those regions, potentially reducing costs.
 
-For additional information, refer to the [detailed comparison](/azure/architecture/guide/technology-choices/compute-decision-tree) between Azure App Service, Azure Virtual Machines, and other Azure services that you can use as a deployment target using the Custom option in Visual Studio.
+For additional information, see the [detailed comparison](/azure/architecture/guide/technology-choices/compute-decision-tree) between Azure App Service, Azure Virtual Machines, and other Azure services that you can use as a deployment target using the Custom option in Visual Studio.
 
 #### When to choose Azure Virtual Machines
 
 - You want to deploy a web application that's accessible through the Internet, with full control over the lifetime of assigned IP addresses.
-- You need machine-level customizations on your servers, which includes additional software such as a specialized database system, specific networking configurations, disk partitions, and so forth.
+- You need machine-level customizations on your servers, which include additional software such as a specialized database system, specific networking configurations, disk partitions, and so forth.
 - You want a fine level of control over scaling of your web application.
 - You need direct access to the servers hosting your application for any other reason.
 
@@ -140,15 +140,15 @@ For more information, see the following:
 
 ## Folder
 
-Deploying to the file system means to simply copy your application's files to a specific folder on your own computer. This is most often used for testing purposes, or to deploy the application for use by a limited number of people if the computer is also running a server. If the target folder is shared on a network, then deploying to the file system can make the web application files available to others who might then deploy it to specific servers.
+Deploying to the file system means to copy your application's files to a specific folder on your own computer. Deploying to a folder is most often used for testing purposes, or to deploy the application for use by a limited number of people if the computer is also running a server. If the target folder is shared on a network, then deploying to the file system can make the web application files available to others who might then deploy it to specific servers.
 ::: moniker range=">=vs-2019"
 Starting with Visual Studio 2019 16.8, the folder target includes the ability to publish a .Net Windows application using ClickOnce.
 
 If you wish to publish a .NET Core 3.1, or newer, Windows application with ClickOnce, see [Deploy a .NET Windows application using ClickOnce](quickstart-deploy-using-clickonce-folder.md).
 ::: moniker-end
 Any local machines that are running a server can make your application available through the Internet or an Intranet depending on how it's configured and the networks to which it's connected. (If you do connect a computer directly to the Internet, be especially careful to protect it from external security threats.) Because you manage these machines, you're in complete control of the software and hardware configurations.
 
-Note that if for any reason (such as machine access) you are not able to use cloud services like Azure App Service or Azure Virtual Machines, you can use the [Azure Stack](https://azure.microsoft.com/overview/azure-stack/) in your own datacenter. The Azure Stack allows you to manage and use computing resources through Azure App Service and Azure Virtual Machines while yet keeping everything on-premises.
+If for any reason (such as machine access) you are not able to use cloud services like Azure App Service or Azure Virtual Machines, you can use the [Azure Stack](https://azure.microsoft.com/overview/azure-stack/) in your own datacenter. The Azure Stack allows you to manage and use computing resources through Azure App Service and Azure Virtual Machines while yet keeping everything on-premises.
 
 ### When to choose file system deployment
 
@@ -174,7 +174,7 @@ For additional help to choose your settings, see the following:
 
 An FTP/FTPS server lets you deploy your application to a server other than Azure. It can deploy to a file system or any other server (Internet or Intranet) to which you have access, including those on other cloud services. It can work with web deploy (files or .ZIP) and FTP.
 
-When choosing a FTP/FTPS server, Visual Studio prompts you for a profile name, and then collect additional **Connection** information including the target server or location, a site name, and credentials. You can control the following behaviors on the **Settings** tab:
+When choosing a FTP/FTPS server, Visual Studio prompts you for a profile name, and then collects additional **Connection** information including the target server or location, a site name, and credentials. You can control the following behaviors on the **Settings** tab:
 
 - The configuration you want to deploy.
 - Whether to remove existing files from the destination.
@@ -193,7 +193,7 @@ You can create any number of FTP/FTPS deployment profiles in Visual Studio, maki
 
 An IIS web server lets you deploy your application to a web server other than Azure. It can deploy to an IIS server (Internet or Intranet) to which you have access, including those on other cloud services. It can work with Web Deploy or a Web Deploy package.
 
-When choosing an IIS web server, Visual Studio prompts you for a profile name, and then collect additional **Connection** information including the target server or location, a site name, and credentials. You can control the following behaviors on the **Settings** tab:
+When choosing an IIS web server, Visual Studio prompts you for a profile name, and then collects additional **Connection** information including the target server or location, a site name, and credentials. You can control the following behaviors on the **Settings** tab:
 
 - The configuration you want to deploy.
 - Whether to remove existing files from the destination.
@@ -210,7 +210,7 @@ You can create any number of IIS web server deployment profiles in Visual Studio
 
 For more information, see [Quickstart - Deploy to a web site](quickstart-deploy-to-a-web-site.md).
 
-For help troubleshooting ASP.NET Core on IIS, see [Troubleshoot ASP.NET Core on Azure App Service and IIS](/aspnet/core/test/troubleshoot-azure-iis).
+For help with troubleshooting ASP.NET Core on IIS, see [Troubleshoot ASP.NET Core on Azure App Service and IIS](/aspnet/core/test/troubleshoot-azure-iis).
 
 ## Import Profile
 
@@ -221,7 +221,7 @@ Use of a publish settings file can simplify deployment configuration and works b
 ### When to choose import profile
 
 - You're publishing to IIS and want to simplify deployment configuration.
-- You're publishing to IIS or Azure App Service and want to speed up deployment configuration for re-use or for team members publishing to the same service.
+- You're publishing to IIS or Azure App Service and want to speed up deployment configuration for reuse or for team members publishing to the same service.
 
 For more information, see the following:
 
diff --git a/docs/deployment/quickstart-deploy-to-local-folder.md b/docs/deployment/quickstart-deploy-to-local-folder.md
@@ -44,14 +44,15 @@ You can use the **Publish** tool to publish ASP.NET, ASP.NET Core, .NET Core, an
 
 ::: moniker range=">=vs-2019"
 
-1. If you are deploying a .NET Core 3.1, or newer, Windows Application you may need to select **Folder** in the **Specific target** window.
+4. If you are deploying a .NET Core 3.1, or newer, Windows Application you may need to select **Folder** in the **Specific target** window.
 
 ![Choose folder as specific target](../deployment/media/quickstart-publish-folder-targets.png "Choose Specific Target")
 
-1. If you wish to publish a .NET Core 3.1, or newer, Windows application with ClickOnce, see [Deploy a .NET Windows application using ClickOnce](quickstart-deploy-using-clickonce-folder.md).
+5. If you wish to publish a .NET Core 3.1, or newer, Windows application with ClickOnce, see [Deploy a .NET Windows application using ClickOnce](quickstart-deploy-using-clickonce-folder.md).
+
  ::: moniker-end
 
-1. Enter a path or select **Browse** to specify a folder.
+4. Enter a path or select **Browse** to specify a folder.
 
     ![Specify the path to the folder](../deployment/media/quickstart-publish-folder-path.png "Choose Folder")
 
diff --git a/docs/deployment/quickstart-deploy-using-clickonce-folder.md b/docs/deployment/quickstart-deploy-using-clickonce-folder.md
@@ -60,7 +60,7 @@ Also in this page, you can also set the Publish version and if the version will
 > [!NOTE]
 > The Publish version number is unique for each ClickOnce profile. If you plan on having more then one profile, you will need to keep this in mind.
 
-1. In the **Sign manifests** page, you can specify if the manifests should be signed and which certificate to use.
+10. In the **Sign manifests** page, you can specify if the manifests should be signed and which certificate to use.
 
     ![Sign the ClickOnce Manifests](../deployment/media/quickstart-clickonce-sign-manifests.png)
 
