acrolinx, correx

v-thepet · v-thepet · commit efff5f615e17 · 2018-07-11T12:59:09.000-07:00
diff --git a/docs/msbuild/how-to-build-specific-targets-in-solutions-by-using-msbuild-exe.md b/docs/msbuild/how-to-build-specific-targets-in-solutions-by-using-msbuild-exe.md
@@ -22,7 +22,7 @@ You can use *MSBuild.exe* to build specific targets of specific projects in a so
   
 1.  At the command line, type `MSBuild.exe <SolutionName>.sln`, where `<SolutionName>` corresponds to the file name of the solution that contains the target that you want to execute.  
   
-2. Specify the target after the `/target:` switch in the format `<ProjectName>:<TargetName>`. If the project name contains any of the characters `%`, `$`, `@`, `;`, `.`, `(`, `)`, or `'`, replace them with an `_` in the specified target name.
+2. Specify the target after the `/target:` switch in the format \<ProjectName>:\<TargetName>. If the project name contains any of the characters `%`, `$`, `@`, `;`, `.`, `(`, `)`, or `'`, replace them with an `_` in the specified target name.
   
 ## Example  
  The following example executes the `Rebuild` target of the `NotInSlnFolder` project, and then executes the `Clean` target of the `InSolutionFolder` project, which is located in the *NewFolder* solution folder.  
diff --git a/docs/msbuild/how-to-clean-a-build.md b/docs/msbuild/how-to-clean-a-build.md
@@ -30,9 +30,10 @@ When you clean a build, all intermediate and output files are deleted, leaving o
   
 2.  Use the [MakeDir](../msbuild/makedir-task.md) task to create the directory if the directory does not exist. For example:  
   
-     `<MakeDir Directories = "$(builtdir)"`  
-  
-     `Condition = "!Exists('$(builtdir)')" />`  
+     ```xml
+     <MakeDir Directories = "$(builtdir)"  
+      Condition = "!Exists('$(builtdir)')" />
+     ```
   
 ## Remove the output items  
  Prior to creating new instances of intermediate and output files, you may want to clear all previous instances of intermediate and output files. Use the [RemoveDir](../msbuild/removedir-task.md) task to delete a directory and all files and directories that it contains from a disk.  
diff --git a/docs/msbuild/how-to-escape-special-characters-in-msbuild.md b/docs/msbuild/how-to-escape-special-characters-in-msbuild.md
@@ -40,5 +40,5 @@ Certain characters have special meaning in [!INCLUDE[vstecmsbuild](../extensibil
   
 ## See also  
  [MSBuild concepts](../msbuild/msbuild-concepts.md)   
- [MSBuild](../msbuild/msbuild.md)
- [Items](../msbuild/msbuild-items.md)
+ [MSBuild](../msbuild/msbuild.md)   
+ [Items](../msbuild/msbuild-items.md)   
diff --git a/docs/msbuild/how-to-exclude-files-from-the-build.md b/docs/msbuild/how-to-exclude-files-from-the-build.md
@@ -120,5 +120,5 @@ In a project file you can use wildcards to include all the files in one director
   
 ## See also  
  [Items](../msbuild/msbuild-items.md)   
- [MSBuild](../msbuild/msbuild.md)
- [How to: Select the files to build](../msbuild/how-to-select-the-files-to-build.md)
+ [MSBuild](../msbuild/msbuild.md)   
+ [How to: Select the files to build](../msbuild/how-to-select-the-files-to-build.md)   
diff --git a/docs/msbuild/how-to-extend-the-visual-studio-build-process.md b/docs/msbuild/how-to-extend-the-visual-studio-build-process.md
@@ -17,14 +17,14 @@ ms.workload:
   - "multiple"
 ---
 # How to: Extend the Visual Studio build process
-The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] build process is defined by a series of [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] *.targets* files that are imported into your project file. One of these imported files, *Microsoft.Common.targets*, can be extended to allow you to run custom tasks at several points in the build process. This topic explains two methods you can use to extend the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] build process:  
+The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] build process is defined by a series of [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] *.targets* files that are imported into your project file. One of these imported files, *Microsoft.Common.targets*, can be extended to allow you to run custom tasks at several points in the build process. This article explains two methods you can use to extend the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] build process:  
   
 -   Overriding specific predefined targets defined in *Microsoft.Common.targets*.  
   
 -   Overriding the "DependsOn" properties defined in *Microsoft.Common.targets*.  
   
 ## Override predefined targets  
- The *Microsoft.Common.targets* file contains a set of predefined empty targets that are called before and after some of the major targets in the build process. For example, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] calls the `BeforeBuild` target before the main `CoreBuild` target and the `AfterBuild` target after the `CoreBuild` target. By default, the empty targets in *Microsoft.Common.targets* do nothing, but you can override their default behavior by defining the targets you want in a project file that imports *Microsoft.Common.targets*. By doing this, you can use [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] tasks to give you more control over the build process.  
+ The *Microsoft.Common.targets* file contains a set of predefined empty targets that is called before and after some of the major targets in the build process. For example, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] calls the `BeforeBuild` target before the main `CoreBuild` target and the `AfterBuild` target after the `CoreBuild` target. By default, the empty targets in *Microsoft.Common.targets* do nothing, but you can override their default behavior by defining the targets you want in a project file that imports *Microsoft.Common.targets*. By overriding the predefined targets, you can use [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] tasks to give you more control over the build process.  
   
 #### To override a predefined target  
   
@@ -45,18 +45,18 @@ The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] build process is d
     ```  
   
 3.  Build the project file.  
-  
- The following table shows all of the targets in *Microsoft.Common.targets* that you can safely override.  
+
+The following table shows all of the targets in *Microsoft.Common.targets* that you can safely override.  
   
 |Target name|Description|  
 |-----------------|-----------------|  
 |`BeforeCompile`, `AfterCompile`|Tasks inserted in one of these targets run before or after core compilation is done. Most customizations are done in one of these two targets.|  
-|`BeforeBuild`, `AfterBuild`|Tasks inserted in one of these targets will run before or after everything else in the build. **Note:**  The `BeforeBuild` and `AfterBuild` targets are already defined in comments at the end of most project files. This allows you to easily add pre- and post-build events to your project file.|  
+|`BeforeBuild`, `AfterBuild`|Tasks inserted in one of these targets will run before or after everything else in the build. **Note:**  The `BeforeBuild` and `AfterBuild` targets are already defined in comments at the end of most project files, allowing you to easily add pre- and post-build events to your project file.|  
 |`BeforeRebuild`, `AfterRebuild`|Tasks inserted in one of these targets run before or after the core rebuild functionality is invoked. The order of target execution in *Microsoft.Common.targets* is: `BeforeRebuild`, `Clean`, `Build`, and then `AfterRebuild`.|  
-|`BeforeClean`, `AfterClean`|Tasks inserted in one of these targets run before or after the core clean functionality is invoked.|  
-|`BeforePublish`, `AfterPublish`|Tasks inserted in one of these targets run before or after the core publish functionality is invoked.|  
-|`BeforeResolveReference`, `AfterResolveReferences`|Tasks inserted in one of these targets run before or after assembly references are resolved.|  
-|`BeforeResGen`, `AfterResGen`|Tasks inserted in one of these targets run before or after resources are generated.|  
+|`BeforeClean`, `AfterClean`|Tasks that are inserted in one of these targets run before or after the core clean functionality is invoked.|  
+|`BeforePublish`, `AfterPublish`|Tasks that are inserted in one of these targets run before or after the core publish functionality is invoked.|  
+|`BeforeResolveReference`, `AfterResolveReferences`|Tasks that are inserted in one of these targets run before or after assembly references are resolved.|  
+|`BeforeResGen`, `AfterResGen`|Tasks that are inserted in one of these targets run before or after resources are generated.|  
   
 ## Override "DependsOn" properties  
  Overriding predefined targets is an easy way to extend the build process, but, because [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] evaluates the definition of targets sequentially, there is no way to prevent another project that imports your project from overriding the targets you already have overridden. So, for example, the last `AfterBuild` target defined in the project file, after all other projects have been imported, will be the one that is used during the build.  
