Merge pull request #2547 from v-thepet/cleanup

Cleanup

Author: PRMerger17

docs/msbuild/building-multiple-projects-in-parallel-with-msbuild.md

@@ -23,7 +23,7 @@ You can use MSBuild to build multiple projects faster by running them in paralle
 -   The <xref:Microsoft.Build.Tasks.MSBuild.BuildInParallel%2A> task parameter on an MSBuild task.  
 
 > [!NOTE]
->  The **/verbosity** (**/v**) switch in a command line can also affect build performance. Your build performance might decrease if the verbosity of your build log information is set to detailed or diagnostic, which are used for troubleshooting. For more information, see [Obtaining build logs](../msbuild/obtaining-build-logs-with-msbuild.md) and [Command-line reference](../msbuild/msbuild-command-line-reference.md).  
+>  The **/verbosity** (**/v**) switch in a command line can also affect build performance. Your build performance might decrease if the verbosity of your build log information is set to detailed or diagnostic, which are used for troubleshooting. For more information, see [Obtain build logs](../msbuild/obtaining-build-logs-with-msbuild.md) and [Command-line reference](../msbuild/msbuild-command-line-reference.md).  
   
 ## /maxcpucount Switch  
  If you use the `/maxcpucount` switch, or `/m` for short, MSBuild can create the specified number of *MSBuild.exe* processes that may be run in parallel. These processes are also known as "worker processes." Each worker process uses a separate core or processor, if any are available, to build a project at the same time as other available processors may be building other projects. For example, setting this switch to a value of "4" causes MSBuild to create four worker processes to build the project.  
@@ -66,6 +66,6 @@ msbuild.exe myproj.proj /maxcpucount:3
 ```  
 
 ## See also  
- [Using multiple processors to build projects](../msbuild/using-multiple-processors-to-build-projects.md)   
- [Writing multi-processor-aware loggers](../msbuild/writing-multi-processor-aware-loggers.md)   
+ [Use multiple processors to build projects](../msbuild/using-multiple-processors-to-build-projects.md)   
+ [Write multi-processor-aware loggers](../msbuild/writing-multi-processor-aware-loggers.md)   
  [Tuning C++ build parallelism blog](http://go.microsoft.com/fwlink/?LinkId=251457)

docs/msbuild/comparing-properties-and-items.md

@@ -13,7 +13,7 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# Comparing properties and items
+# Compare properties and items
 MSBuild properties and items are both used to pass information to tasks, evaluate conditions, and store values that can be referenced throughout the project file.  
 
 -   Properties are name-value pairs. For more information, see [MSBuild properties](../msbuild/msbuild-properties.md).  

docs/msbuild/item-metadata-in-task-batching.md

@@ -127,7 +127,7 @@ The [Message task](../msbuild/message-task.md) displays the following informatio
 
  `Number: 3 -- Items in ExampColl: Item3 ExampColl2: Item6`  
 
-## Batching one item at a time  
+## Batch one item at a time  
  Batching can also be performed on well-known item metadata that is assigned to every item upon creation. This guarantees that every item in a collection will have some metadata to use for batching. The `Identity` metadata value is unique for every item, and is useful for dividing every item in an item list into a separate batch. For a complete list of well-known item metadata, see [Well-known item metadata](../msbuild/msbuild-well-known-item-metadata.md).  
 
  The following example shows how to batch each item in an item list one at a time. Because the `Identity` metadata value of every item is unique, the `ExampColl` item list is divided into six batches, each batch containing one item of the item list. The presence of `%(Identity)`in the `Text` attribute notifies [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] that batching should be performed.  
@@ -166,7 +166,7 @@ Identity: "Item5" -- Items in ExampColl: Item5
 Identity: "Item6" -- Items in ExampColl: Item6  
 ```  
 
-## Filtering item lists  
+## Filter item lists  
  Batching can be used to filter out certain items from an item list before passing it to a task. For example, filtering on the `Extension` well-known item metadata value allows you to run a task on only files with a specific extension.  
 
  The following example shows how to divide an item list into batches based on item metadata, and then filter those batches when they are passed into a task. The `ExampColl` item list is divided into three batches based on the `Number` item metadata. The `Condition` attribute of the task specifies that only batches with a `Number` item metadata value of `2` will be passed into the task  

docs/msbuild/msbuild-batching.md

@@ -49,7 +49,7 @@ ms.workload:
 
  For more specific batching examples, see [Item metadata in task batching](../msbuild/item-metadata-in-task-batching.md).  
 
-## Target Batching  
+## Target batching  
  [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] checks if the inputs and outputs of a target are up-to-date before it runs the target. If both inputs and outputs are up-to-date, the target is skipped. If a task inside of a target uses batching, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] needs to determine if the inputs and outputs for each batch of items is up-to-date. Otherwise, the target is executed every time it is hit.  
 
  The following example shows a `Target` element that contains an `Outputs` attribute with the %(\<ItemMetaDataName>) notation. [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] will divide the `Example` item list into batches based on the `Color` item metadata, and analyze the timestamps of the output files for each batch. If the outputs from a batch are not up-to-date, the target is run. Otherwise, the target is skipped.  

docs/msbuild/msbuild-multitargeting-overview.md

@@ -36,10 +36,10 @@ By using MSBuild, you can compile an application to run on any one of several ve
  A Toolset collects together the tools, tasks, and targets that are used to create the application. A Toolset includes compilers such as *csc.exe* and *vbc.exe*, the common targets file (*microsoft.common.targets*), and the common tasks file (*microsoft.common.tasks*). The 4.5 Toolset can be used to target .NET Framework versions 2.0, 3.0, 3.5, 4, and 4.5. However, the 2.0 Toolset can only be used to target the .NET Framework version 2.0. For more information, see [Toolset (ToolsVersion)](../msbuild/msbuild-toolset-toolsversion.md).  
 
 ## Reference assemblies  
- The reference assemblies that are specified in the Toolset help you design and build an application. These reference assemblies not only enable a particular target build, but also restrict components and features in the Visual Studio IDE to those that are compatible with the target. For more information, see [Resolving assemblies at design time](../msbuild/resolving-assemblies-at-design-time.md)  
+ The reference assemblies that are specified in the Toolset help you design and build an application. These reference assemblies not only enable a particular target build, but also restrict components and features in the Visual Studio IDE to those that are compatible with the target. For more information, see [Resolve assemblies at design time](../msbuild/resolving-assemblies-at-design-time.md)  
 
 ## Configure targets and tasks  
- You can configure MSBuild targets and tasks to run out-of-process with MSBuild so that you can target contexts that are considerably different than the one you are running on.  For example, you can target a 32-bit, .NET Framework 2.0 application while the development computer is running on a 64-bit platform with .NET Framework 4.5. For more information, see [Configuring targets and tasks](../msbuild/configuring-targets-and-tasks.md).  
+ You can configure MSBuild targets and tasks to run out-of-process with MSBuild so that you can target contexts that are considerably different than the one you are running on.  For example, you can target a 32-bit, .NET Framework 2.0 application while the development computer is running on a 64-bit platform with .NET Framework 4.5. For more information, see [Configure targets and tasks](../msbuild/configuring-targets-and-tasks.md).  
 
 ## Troubleshooting  
  You might encounter errors if you try to reference an assembly that is not part of the target context. For more information about these errors and what to do about them, see [Troubleshoot .NET Framework targeting errors](../msbuild/troubleshooting-dotnet-framework-targeting-errors.md).

docs/msbuild/registering-extensions-of-the-dotnet-framework.md

@@ -15,7 +15,7 @@ manager: douge
 ms.workload: 
   - "dotnet"
 ---
-# Registering extensions of the .NET Framework
+# Register extensions of the .NET Framework
 You can develop an assembly that extends a specific version of the .NET Framework. To enable the assembly to appear in the Visual Studio **Add References** dialog box, you must add the folder that contains it to the system registry.  
 
  For example, assume that the Trey Research company has developed a library that extends the .NET Framework 4, and wants the library assemblies to appear in the **Add References** dialog box when a project targets the .NET Framework 4. Also assume that the assemblies are 32-bit assemblies running on a 32-bit computer or 64-bit assemblies running on a 64-bit computer, and that they will be installed in the *C:\TreyResearch\Extensions4\\* folder.  
@@ -27,5 +27,5 @@ You can develop an assembly that extends a specific version of the .NET Framewor
   
  To register a 32-bit assembly on a 64-bit computer, use the Wow6432 node, for example: **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\\.NETFramework\v4.0.21006\AssemblyFoldersEx\TreyResearch\\**.  
 
-## See also  
+### See also  
  [Visual Studio integration](../msbuild/visual-studio-integration-msbuild.md)

docs/msbuild/using-memory-efficiently-when-you-build-large-projects.md

@@ -20,5 +20,5 @@ Large projects often contain many subprojects and other dependencies, which may
 
  Version 4.0 handles this memory management automatically, saving projects from having to use properties such as  `UnloadProjectsOnCompletion` and `UseResultsCache`.  
 
-## See also  
- [Building multiple projects in parallel](../msbuild/building-multiple-projects-in-parallel-with-msbuild.md)
+### See also  
+ [Build multiple projects in parallel](../msbuild/building-multiple-projects-in-parallel-with-msbuild.md)

docs/msbuild/using-multiple-processors-to-build-projects.md

@@ -35,5 +35,5 @@ MSBuild can take advantage of systems that have multiple processors, or multiple
  To avoid this problem but still enable multi-processor builds, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] uses "process isolation." By using process isolation, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] can create a maximum of `n` processes, where `n` equals the number of processors available on the system. For example, if [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] builds a solution on a system that has two processors, then only two build processes are created. These processes are re-used to build all the projects in the solution.  
 
 ## See also  
- [Building multiple projects in parallel](../msbuild/building-multiple-projects-in-parallel-with-msbuild.md)   
+ [Build multiple projects in parallel](../msbuild/building-multiple-projects-in-parallel-with-msbuild.md)   
  [Tasks](../msbuild/msbuild-tasks.md)

docs/msbuild/visual-studio-integration-msbuild.md

@@ -176,8 +176,8 @@ Condition=" '$(Something)|$(Configuration)|$(SomethingElse)' == 'xxx|Debug|yyy'
 
 ## See also  
  [How to: Extend the Visual Studio build process](../msbuild/how-to-extend-the-visual-studio-build-process.md)   
- [Starting a build from within the IDE](../msbuild/starting-a-build-from-within-the-ide.md)   
- [Registering extensions of the .NET Framework](../msbuild/registering-extensions-of-the-dotnet-framework.md)   
+ [Start a build from within the IDE](../msbuild/starting-a-build-from-within-the-ide.md)   
+ [Register extensions of the .NET Framework](../msbuild/registering-extensions-of-the-dotnet-framework.md)   
  [MSBuild concepts](../msbuild/msbuild-concepts.md)   
  [Item element (MSBuild)](../msbuild/item-element-msbuild.md)   
  [Property element (MSBuild)](../msbuild/property-element-msbuild.md)