fixed gerunds, capitalization, and formatting

Author: WilliamAntonRohm

docs/deployment/troubleshooting-clickonce-deployments.md

@@ -21,29 +21,29 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# Troubleshooting ClickOnce Deployments
+# Troubleshoot ClickOnce deployments
 This topic helps you diagnose and resolve the most common issues with [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployments.  
 
  In most cases, a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application will download to a user's computer and run without any problems. There are some cases, however, where Web server or application configuration issues can cause unforeseen problems.  
 
- [How to: Set a Custom Log File Location for ClickOnce Deployment Errors](../deployment/how-to-set-a-custom-log-file-location-for-clickonce-deployment-errors.md)  
+ [How to: Set a custom log file location for ClickOnce deployment errors](../deployment/how-to-set-a-custom-log-file-location-for-clickonce-deployment-errors.md)  
  Describes how to redirect all [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] activation failures on a machine to a single log file.  
 
- [How to: Specify Verbose Log Files for ClickOnce Deployments](../deployment/how-to-specify-verbose-log-files-for-clickonce-deployments.md)  
+ [How to: Specify verbose log files for ClickOnce deployments](../deployment/how-to-specify-verbose-log-files-for-clickonce-deployments.md)  
  Describes how to increase the detail that [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] writes to log files.  
 
- [Server and Client Configuration Issues in ClickOnce Deployments](../deployment/server-and-client-configuration-issues-in-clickonce-deployments.md)  
+ [Server and client configuration issues in ClickOnce deployments](../deployment/server-and-client-configuration-issues-in-clickonce-deployments.md)  
  Describes various issues with the configuration of your Web server that could cause difficulty downloading [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications.  
 
- [Security, Versioning, and Manifest Issues in ClickOnce Deployments](../deployment/security-versioning-and-manifest-issues-in-clickonce-deployments.md)  
+ [Security, versioning, and manifest issues in ClickOnce deployments](../deployment/security-versioning-and-manifest-issues-in-clickonce-deployments.md)  
  Describes miscellaneous issues surrounding [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployments.  
 
- [Troubleshooting Specific Errors in ClickOnce Deployments](../deployment/troubleshooting-specific-errors-in-clickonce-deployments.md)  
+ [Troubleshoot specific errors in ClickOnce deployments](../deployment/troubleshooting-specific-errors-in-clickonce-deployments.md)  
  Describes specific scenarios in which a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployment cannot succeed, and provides steps for resolving them.  
 
- [Debugging ClickOnce Applications That Use System.Deployment.Application](../deployment/debugging-clickonce-applications-that-use-system-deployment-application.md)  
+ [Debug ClickOnce applications that use System.Deployment.Application](../deployment/debugging-clickonce-applications-that-use-system-deployment-application.md)  
  Describes a technique for debugging ClickOnce applications that use System.Deployment.Application.  
 
-## See Also  
- [ClickOnce Deployment Manifest](../deployment/clickonce-deployment-manifest.md)   
- [ClickOnce Application Manifest](../deployment/clickonce-application-manifest.md)
+## See also  
+ [ClickOnce deployment manifest](../deployment/clickonce-deployment-manifest.md)   
+ [ClickOnce application manifest](../deployment/clickonce-application-manifest.md)

docs/deployment/troubleshooting-specific-errors-in-clickonce-deployments.md

@@ -22,15 +22,15 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# Troubleshooting Specific Errors in ClickOnce Deployments
+# Troubleshoot specific errors in ClickOnce deployments
 This article lists the following common errors that can occur when you deploy a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application, and provides steps to resolve each problem.  
 
-## General Errors  
+## General errors  
 
 #### When you try to locate an application file, nothing occurs, or XML renders in Internet Explorer, or you receive a Run or Save As dialog box  
  This error is likely caused by content types (also known as MIME types) not being registered correctly on the server or client.  
 
- First, make sure that the server is configured to associate the `.application` extension with content type "application/x-ms-application."  
+ First, make sure that the server is configured to associate the *.application* extension with content type "application/x-ms-application."  
 
  If the server is configured correctly, check that the [!INCLUDE[dnprdnlong](../code-quality/includes/dnprdnlong_md.md)] is installed on your computer. If the [!INCLUDE[dnprdnlong](../code-quality/includes/dnprdnlong_md.md)] is installed, and you are still seeing this problem, try uninstalling and reinstalling the [!INCLUDE[dnprdnlong](../code-quality/includes/dnprdnlong_md.md)] to re-register the content type on the client.  
 
@@ -48,11 +48,11 @@ This article lists the following common errors that can occur when you deploy a
 -   See whether there are network connectivity issues; you can receive this message if your client computer went offline during the download.  
 
 #### Download error when you try to install a ClickOnce application that has a .config file  
- By default, a Visual Basic Windows-based application includes an App.config file. There will be a problem when a user tries to install from a Web server that uses Windows Server 2003, because that operating system blocks the installation of .config files for security reasons. To enable the .config file to be installed, click **Use ".deploy" file extension** in the **Publish Options** dialog box.  
+ By default, a Visual Basic Windows-based application includes an App.config file. There will be a problem when a user tries to install from a Web server that uses Windows Server 2003, because that operating system blocks the installation of *.config* files for security reasons. To enable the *.config* file to be installed, click **Use ".deploy" file extension** in the **Publish Options** dialog box.  
 
  You also must set the content types (also known as MIME types) appropriately for .application, .manifest, and .deploy files. For more information, see your Web server documentation.  
 
- For more information, see "Windows Server 2003: Locked-Down Content Types" in [Server and Client Configuration Issues in ClickOnce Deployments](../deployment/server-and-client-configuration-issues-in-clickonce-deployments.md).  
+ For more information, see "Windows Server 2003: Locked-Down Content Types" in [Server and client configuration issues in ClickOnce deployments](../deployment/server-and-client-configuration-issues-in-clickonce-deployments.md).  
 
 #### Error message: "Application is improperly formatted;" Log file contains "XML signature is invalid"  
  Ensure that you updated the manifest file and signed it again. Republish your application by using [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] or use Mage to sign the application again.  
@@ -97,10 +97,10 @@ This article lists the following common errors that can occur when you deploy a
 
  If you are publishing with a URL, ensure that the destination computer has FrontPage Server Extensions enabled.  
 
-#### Error Message: Unable to create the Web site '\<site>'. The components for communicating with FrontPage Server Extensions are not installed.  
+#### Error message: Unable to create the Web site '\<site>'. The components for communicating with FrontPage Server Extensions are not installed.  
  Ensure that you have the Microsoft Visual Studio Web Authoring Component installed on the machine that you are publishing from. For Express users, this component is not installed by default. For more information, see [http://go.microsoft.com/fwlink/?LinkId=102310](http://go.microsoft.com/fwlink/?LinkId=102310).  
 
-#### Error Message: Could not find file 'Microsoft.Windows.Common-Controls, Version=6.0.0.0, Culture=*, PublicKeyToken=6595b64144ccf1df, ProcessorArchitecture=\*, Type=win32'  
+#### Error message: Could not find file 'Microsoft.Windows.Common-Controls, Version=6.0.0.0, Culture=*, PublicKeyToken=6595b64144ccf1df, ProcessorArchitecture=\*, Type=win32'  
  This error message appears when you attempt to publish a WPF application with visual styles enabled. To resolve this issue, see [How to: Publish a WPF Application with Visual Styles Enabled](../deployment/how-to-publish-a-wpf-application-with-visual-styles-enabled.md).  
 
 ## Using Mage  
@@ -132,6 +132,6 @@ This article lists the following common errors that can occur when you deploy a
 |Shortcuts cannot be activated over the network.|Shortcuts to a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application can only be started on the local hard disk. They cannot be started by opening a URL that points to a shortcut file on a remote server.|  
 |The application is too large to run online in partial trust. Contact the application vendor or your system administrator for assistance.|An application that runs in partial trust cannot be larger than half of the size of the online application quota, which by default is 250 MB.|  
 
-## See Also  
- [ClickOnce Security and Deployment](../deployment/clickonce-security-and-deployment.md)   
- [Troubleshooting ClickOnce Deployments](../deployment/troubleshooting-clickonce-deployments.md)
+## See also  
+ [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md)   
+ [Troubleshoot ClickOnce deployments](../deployment/troubleshooting-clickonce-deployments.md)

docs/deployment/trusted-application-deployment-overview.md

@@ -19,15 +19,15 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# Trusted Application Deployment Overview
+# Trusted Application Deployment overview
 This topic provides an overview of how to deploy [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications that have elevated permissions by using the Trusted Application Deployment technology.  
 
  Trusted Application Deployment, part of the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployment technology, makes it easier for organizations of any size to grant additional permissions to a managed application in a safer, more secure manner without user prompting. With Trusted Application Deployment, an organization  can just configure a client computer to have a list of trusted publishers, who are identified using Authenticode certificates. Thereafter, any [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application signed by one of these trusted publishers receives a higher level of trust.  
 
 > [!NOTE]
 >  Trusted Application Deployment requires one-time configuration of a user's computer. In managed desktop environments, this configuration can be performed by using global policy. If this is not what you want for your application, use permission elevation instead. For more information, see [Securing ClickOnce Applications](../deployment/securing-clickonce-applications.md).  
   
-## Trusted Application Deployment Basics  
+## Trusted Application Deployment basics  
  The following table shows the objects and roles that are involved in Trusted Application Deployment.  
 
 |Object or role|Description|  
@@ -61,10 +61,10 @@ This topic provides an overview of how to deploy [!INCLUDE[ndptecclick](../deplo
 
 5.  Publish the application deployment to client computers.  
 
-### Obtain a Certificate for the Publisher  
+### Obtain a certificate for the publisher  
  Digital certificates are a core component of the Microsoft Authenticode authentication and security system. Authenticode is a standard part of the Windows operating system. All [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications must be signed with a digital certificate, regardless of whether they participate in Trusted Application Deployment. For a full explanation of how Authenticode works with [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)], see [ClickOnce and Authenticode](../deployment/clickonce-and-authenticode.md).  
 
-### Add the Publisher to the Trusted Publishers Store  
+### Add the publisher to the trusted publishers store  
  For your [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application to receive a higher level of trust, you must add your certificate as a trusted publisher to each client computer on which the application will run. Performing this task is a one-time configuration. After it is completed, you can deploy as many [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications signed with your publisher's certificate as you want, and they will all run with high trust.  
 
  If you are deploying your application in a managed desktop environment; for example, a corporate intranet running the Windows operating system; you can add trusted publishers to a client's store by creating a new certificate trust list (CTL) with Group Policy. For more information, see [Create a certificate trust list for a Group Policy object](http://go.microsoft.com/fwlink/?LinkId=102576).  
@@ -73,22 +73,22 @@ This topic provides an overview of how to deploy [!INCLUDE[ndptecclick](../deplo
 
 -   The <xref:System.Security.Cryptography?displayProperty=fullName> namespace.  
 
--   CertMgr.exe, which is a component of Internet Explorer and therefore exists on Windows 98 and all later versions. For more information, see [Certmgr.exe (Certificate Manager Tool)](/dotnet/framework/tools/certmgr-exe-certificate-manager-tool).  
+-   *CertMgr.exe*, which is a component of Internet Explorer and therefore exists on Windows 98 and all later versions. For more information, see [Certmgr.exe (Certificate Manager Tool)](/dotnet/framework/tools/certmgr-exe-certificate-manager-tool).  
 
 ### Create a ClickOnce Application  
  A [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application is a [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)] client application combined with manifest files that describe the application and supply installation parameters. You can turn your program into a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application by using the **Publish** command in [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)]. Alternatively, you can generate all the files required for [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployment by using tools that are included with the [!INCLUDE[winsdklong](../deployment/includes/winsdklong_md.md)]. For detailed steps about [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployment, see [Walkthrough: Manually Deploying a ClickOnce Application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md).  
 
  Trusted Application Deployment is specific to [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)], and can only be used with [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications.  
 
-### Sign the Deployment  
+### Sign the deployment  
  After obtaining your certificate, you must use it to sign your deployment. If you are deploying your application by using the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] Publish wizard, the wizard will automatically generate a test certificate for you if you have not specified a certificate yourself. You can also use the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] Project Designer window, however, to supply a certificate provided by a CA.  Also see [How to: Publish a ClickOnce Application using the Publish Wizard](../deployment/how-to-publish-a-clickonce-application-using-the-publish-wizard.md).  
 
 > [!CAUTION]
 >  We do not recommend that the application be deployed with a test certificate.  
   
- You can also sign the application by using the Mage.exe or MageUI.exe SDK tools. For more information, see [Walkthrough: Manually Deploying a ClickOnce Application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md). For a full list of command-line options related to deployment signing, see [Mage.exe (Manifest Generation and Editing Tool)](/dotnet/framework/tools/mage-exe-manifest-generation-and-editing-tool).  
+ You can also sign the application by using the *Mage.exe* or *MageUI.exe* SDK tools. For more information, see [Walkthrough: Manually deploy a ClickOnce application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md). For a full list of command-line options related to deployment signing, see [Mage.exe (Manifest Generation and Editing Tool)](/dotnet/framework/tools/mage-exe-manifest-generation-and-editing-tool).  
 
-### Publish the Application  
+### Publish the application  
  As soon as you have signed your [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] manifests, the application is ready to publish to your install location. The installation location can be a Web server, a file share, or the local disk. When a client accesses the deployment manifest for the first time, the trust manager must choose whether the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application has been granted authority or not to run at a higher level of trust by an installed trusted publisher. The trust manager makes this choice by comparing the certificate used to sign the deployment with the certificates stored in the client's trusted publisher store. If the trust manager finds a match, the application runs with high trust.  
 
 ## Trusted Application Deployment and Permission Elevation  
@@ -97,6 +97,6 @@ This topic provides an overview of how to deploy [!INCLUDE[ndptecclick](../deplo
 ## Limitations of Trusted Application Deployment  
  You can use Trusted Application Deployment to grant elevated trust to [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications deployed over the Web or through an enterprise file share. You do not have to use Trusted Application Deployment for [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications distributed on a CD, because, by default, these applications are granted full trust.  
 
-## See Also  
+## See also  
  [Mage.exe (Manifest Generation and Editing Tool)](/dotnet/framework/tools/mage-exe-manifest-generation-and-editing-tool)   
- [Walkthrough: Manually Deploying a ClickOnce Application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md)
+ [Walkthrough: Manually deploy a ClickOnce application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md)

docs/deployment/trustinfo-element-clickonce-application.md

@@ -25,7 +25,7 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# <trustInfo> Element (ClickOnce Application)
+# <trustInfo> element (ClickOnce application)
 Describes the minimum security permissions required for the application to run on the client computer.  
 
 ## Syntax  
@@ -62,7 +62,7 @@ Describes the minimum security permissions required for the application to run o
 </trustInfo>  
 ```  
 
-## Elements and Attributes  
+## Elements and attributes  
  The `trustInfo` element is required and is in the `asm.v2` namespace. It has no attributes and contains the following elements.  
 
 ## security  
@@ -263,6 +263,6 @@ Describes the minimum security permissions required for the application to run o
 </trustInfo>  
 ```  
 
-## See Also  
- [Trusted Application Deployment Overview](../deployment/trusted-application-deployment-overview.md)   
- [ClickOnce Application Manifest](../deployment/clickonce-application-manifest.md)
+## See also  
+ [Trusted Application Deployment overview](../deployment/trusted-application-deployment-overview.md)   
+ [ClickOnce application manifest](../deployment/clickonce-application-manifest.md)