Merge pull request #2493 from v-thepet/msbuild5

MSBuild #10

Author: ktoliver

docs/msbuild/msbuild-api.md

@@ -1,4 +1,16 @@
-# Using the MSBuild API
+---
+title: "MSBuild API | Microsoft Docs"
+ms.custom: ""
+ms.date: "11/04/2016"
+ms.technology: msbuild
+ms.topic: "conceptual"
+author: mikejo5000
+ms.author: mikejo
+manager: douge
+ms.workload: 
+  - "multiple"
+---
+# Use the MSBuild API
 
 MSBuild provides a public API surface so that your program can perform builds and inspect projects.
 

docs/msbuild/msbuild-batching.md

@@ -14,16 +14,16 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# MSBuild Batching
+# MSBuild batching
 [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] has the ability to divide item lists into different categories, or batches, based on item metadata, and run a target or task one time with each batch.  
 
-## Task Batching  
+## Task batching  
  Task batching allows you to simplify your project files by providing a way to divide item lists into different batches and pass each of those batches into a task separately. This means that a project file only needs to have the task and its attributes declared once, even though it can be run several times.  
 
- You specify that you want [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] to perform batching with a task by using the %(*ItemMetaDataName*) notation in one of the task attributes. The following example splits the `Example` item list into batches based on the `Color` item metadata value, and passes each of the batches to the `MyTask` task separately.  
+ You specify that you want [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] to perform batching with a task by using the %(\<ItemMetaDataName>) notation in one of the task attributes. The following example splits the `Example` item list into batches based on the `Color` item metadata value, and passes each of the batches to the `MyTask` task separately.  
 
 > [!NOTE]
->  If you do not reference the item list elsewhere in the task attributes, or the metadata name may be ambiguous, you can use the %(*ItemCollection.ItemMetaDataName*) notation to fully qualify the item metadata value to use for batching.  
+>  If you do not reference the item list elsewhere in the task attributes, or the metadata name may be ambiguous, you can use the %(\<ItemCollection.ItemMetaDataName>) notation to fully qualify the item metadata value to use for batching.  
   
 ```xml  
 <Project  
@@ -47,12 +47,12 @@ ms.workload:
 </Project>  
 ```  
 
- For more specific batching examples, see [Item Metadata in Task Batching](../msbuild/item-metadata-in-task-batching.md).  
+ For more specific batching examples, see [Item metadata in task batching](../msbuild/item-metadata-in-task-batching.md).  
 
 ## 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.  
+ 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.  
 
 ```xml  
 <Project  
@@ -78,9 +78,9 @@ ms.workload:
 </Project>  
 ```  
 
- For another example of target batching, see [Item Metadata in Target Batching](../msbuild/item-metadata-in-target-batching.md).  
+ For another example of target batching, see [Item metadata in target batching](../msbuild/item-metadata-in-target-batching.md).  
 
-## Property Functions Using Metadata  
+## Property functions using metadata  
  Batching can be controlled by property functions that include metadata. For example,  
 
  `$([System.IO.Path]::Combine($(RootPath),%(Compile.Identity)))`  
@@ -93,10 +93,10 @@ ms.workload:
 
  is not allowed.  
 
- For more information about property functions, see [Property Functions](../msbuild/property-functions.md).  
+ For more information about property functions, see [Property functions](../msbuild/property-functions.md).  
 
-## See Also  
- [ItemMetadata Element (MSBuild)](../msbuild/itemmetadata-element-msbuild.md)   
- [MSBuild Concepts](../msbuild/msbuild-concepts.md)   
- [MSBuild Reference](../msbuild/msbuild-reference.md)   
- [Advanced Concepts](../msbuild/msbuild-advanced-concepts.md)
+## See also  
+ [ItemMetadata element (MSBuild)](../msbuild/itemmetadata-element-msbuild.md)   
+ [MSBuild concepts](../msbuild/msbuild-concepts.md)   
+ [MSBuild reference](../msbuild/msbuild-reference.md)   
+ [Advanced concepts](../msbuild/msbuild-advanced-concepts.md)

docs/msbuild/msbuild-best-practices.md

@@ -14,7 +14,7 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# MSBuild Best Practices
+# MSBuild best practices
 We recommend the following best practices for writing MSBuild scripts:  
 
 -   Default property values are best handled by using the `Condition` attribute, and not by declaring a property whose default value can be overridden on the command line. For example, use  
@@ -27,5 +27,5 @@ We recommend the following best practices for writing MSBuild scripts:
 
 -   Avoid wildcards when you select items. Instead, specify files explicitly. This makes it easier to track down errors that may occur when you add or delete files.  
 
-## See Also  
- [Advanced Concepts](../msbuild/msbuild-advanced-concepts.md)
+## See also  
+ [Advanced concepts](../msbuild/msbuild-advanced-concepts.md)