updated per AcroLinx

Author: WilliamAntonRohm

docs/deployment/application-deployment-prerequisites.md

@@ -26,14 +26,14 @@ ms.workload:
 
 To have your application to install and run successfully, first install all components upon which your application is dependent onto the target computer. For example, most applications created using [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] have a dependency on the [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)]. In this case, the correct version of the common language runtime must be present on the destination computer before the application is installed.  
 
- You can select these prerequisites in the **Prerequisites Dialog Box** and install the .NET Framework and other redistributables as a part of your installation. This practice is known as *bootstrapping*. [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] generates a Windows executable program named *Setup.exe*, also known as a *bootstrapper*. The bootstrapper is responsible for installing these prerequisites before your application runs. For more information about selecting these prerequisites, see [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md).  
+ You can select these prerequisites in the **Prerequisites Dialog Box** and install the .NET Framework and any other redistributable as a part of your installation. This practice is known as *bootstrapping*. [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] generates a Windows executable program named *Setup.exe*, also known as a *bootstrapper*. The bootstrapper is responsible for installing these prerequisites before your application runs. For more information about selecting these prerequisites, see [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md).  
 
  Each prerequisite is a bootstrapper package. A bootstrapper package is a group of directories and files containing the manifest files that describe how the prerequisites are installed. If your application prerequisites are not listed in the **Prerequisite Dialog Box**, you can create custom bootstrapper packages and add them to Visual Studio. Then you can select the prerequisites in the **Prerequisites Dialog Box**. For more information, see [Create bootstrapper packages](../deployment/creating-bootstrapper-packages.md).  
 
  By default, bootstrapping is enabled for ClickOnce deployment. The bootstrapper generated for ClickOnce deployment is signed. You can disable bootstrapping for a component, but only if you are sure that the correct version of the component is already installed on all target computers.  
 
 ## Bootstrapping and ClickOnce deployment  
- Before installing an application on a client computer, [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] examines the client to ensure that it has the requirements specified in the application manifest. These requirements include the following:  
+ Before installing an application on a client computer, [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] examines the client to ensure that it has the requirements specified in the application manifest. These include the following requirements:  
 
 -   The minimum required version of the common language runtime, which is specified as an assembly dependency in the application manifest.  
 
@@ -55,7 +55,7 @@ To have your application to install and run successfully, first install all comp
 
  With [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployment, the *Publish.htm* page generated by the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Publish Wizard points either to a link that installs only the application, or to a link that installs both the application and the bootstrapped components.  
 
- If you generate the bootstrapper by using the ClickOnce Publish Wizard or the Publish Page in Visual Studio, the Setup.exe is automatically signed. However, if you want to use your customer's certificate to sign the bootstrapper, you can sign the file later.  
+ If you generate the bootstrapper by using the ClickOnce Publish Wizard or the Publish Page in Visual Studio, the *Setup.exe* is automatically signed. However, if you want to use your customer's certificate to sign the bootstrapper, you can sign the file later.  
 
 ## Bootstrapping and MSBuild  
  If you do not use [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)], but rather compile your applications on the command line, you can create the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] bootstrapping application by using a Microsoft Build Engine (MSBuild) task. For more information, see [GenerateBootstrapper task](../msbuild/generatebootstrapper-task.md).  
@@ -73,7 +73,7 @@ To have your application to install and run successfully, first install all comp
 |**-url, -componentsurl**|Shows the stored URL and components url for this set up.|  
 |**-url=** `location`|Sets the URL where *Setup.exe* will look for the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application.|  
 |**-componentsurl=** `location`|Sets the URL where *Setup.exe* will look for the dependencies, such as the [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)].|  
-|**-homesite=** `true` **|** `false`|When `true`, downloads the dependencies from the preferred location on the vendor's site. This overrides the **-componentsurl** setting. When `false`, downloads the dependencies from the URL specified by **-componentsurl**.|  
+|**-homesite=** `true` **|** `false`|When `true`, downloads the dependencies from the preferred location on the vendor's site. This setting overrides the **-componentsurl** setting. When `false`, downloads the dependencies from the URL specified by **-componentsurl**.|  
 
 ## Operating system support  
  The Visual Studio bootstrapper is not supported on Windows Server 2008 Server Core or Windows Server 2008 R2 Server Core, as they provide a low-maintenance server environment with limited functionality. For example, the Server Core installation option only supports the .NET Framework 3.5 Server Core profile, which cannot run the Visual Studio features that depend on the full .NET Framework.