Merge pull request #2550 from v-thepet/cleanup

PRMerger7 · web-flow · commit db9ee8f188dc · 2018-07-20T07:05:22.000+08:00
gerunds
diff --git a/docs/msbuild/al-assembly-linker-task.md b/docs/msbuild/al-assembly-linker-task.md
@@ -53,7 +53,7 @@ The AL task wraps *AL.exe*, a tool that is distributed with the [!INCLUDE[winsdk
 |`ProductVersion`|Optional `String` parameter.<br /><br /> Specifies a string for the `ProductVersion` field in the assembly. For more information, see the documentation for the `/productv[ersion]` option in [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker).|  
 |`ResponseFiles`|Optional `String[]` parameter.<br /><br /> Specifies the response files that contain additional options to pass through to the Assembly Linker.|  
 |`SdkToolsPath`|Optional `String` parameter.<br /><br /> Specifies the path to the SDK tools, such as resgen.exe.|  
-|`SourceModules`|Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` parameter.<br /><br /> One or more modules to be compiled into an assembly. The modules will be listed in the manifest of the resulting assembly, and will still need to distributed and available in order for the assembly to load. The items passed into this parameter may have additional metadata called `Target`, which specifies the path and filename to which the task copies the file, after which it compiles this new file into the assembly. For more information, see the documentation for [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker). This parameter corresponds to the list of modules passed into Al.exe without a specific switch.|  
+|`SourceModules`|Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` parameter.<br /><br /> One or more modules to be compiled into an assembly. The modules will be listed in the manifest of the resulting assembly, and will still need to distributed and available in order for the assembly to load. The items passed into this parameter may have additional metadata called `Target`, which specifies the path and filename to which the task copies the file, after which it compiles this new file into the assembly. For more information, see the documentation for [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker). This parameter corresponds to the list of modules passed into *Al.exe* without a specific switch.|  
 |`TargetType`|Optional `String` parameter.<br /><br /> Specifies the file format of the output file: `library` (code library), `exe` (console application), or `win` (Windows-based application). The default is `library`. This parameter corresponds to the `/t[arget]` option in [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker).|  
 |`TemplateFile`|Optional `String` parameter.<br /><br /> Specifies the assembly from which to inherit all assembly metadata, except the culture field. The specified assembly must have a strong name.<br /><br /> An assembly that you create with the `TemplateFile` parameter will be a satellite assembly. This parameter corresponds to the `/template` option in [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker).|  
 |`Timeout`|Optional `Int32` parameter.<br /><br /> Specifies the amount of time, in milliseconds, after which the task executable is terminated. The default value is `Int.MaxValue`, indicating that there is no time out period.|  
diff --git a/docs/msbuild/assignculture-task.md b/docs/msbuild/assignculture-task.md
@@ -68,10 +68,10 @@ This task accepts a list of items that may contain a valid .NET culture identifi
   
 |Item collection|Contents|  
 |---------------------|--------------|  
-|`OutAssignedFiles`|`MyResource1.fr.resx (Culture="fr")`<br /><br /> `MyResource2.XX.resx` (no additional metadata)|  
-|`OutAssignedFilesWithCulture`|`MyResource1.fr.resx (Culture="fr")`|  
-|`OutAssignedFilesWithNoCulture`|`MyResource2.XX.resx` (no additional metadata)|  
-|`OutCultureNeutralAssignedFiles`|`MyResource1.resx (Culture="fr")`<br /><br /> `MyResource2.XX.resx (`no additional metadata)|  
+|`OutAssignedFiles`|*MyResource1.fr.resx* (Culture="fr")<br /><br /> *MyResource2.XX.resx* (no additional metadata)|  
+|`OutAssignedFilesWithCulture`|*MyResource1.fr.resx* (Culture="fr")|  
+|`OutAssignedFilesWithNoCulture`|*MyResource2.XX.resx* (no additional metadata)|  
+|`OutCultureNeutralAssignedFiles`|*MyResource1.resx* (Culture="fr")<br /><br /> *MyResource2.XX.resx* (no additional metadata)|  
   
 ## See also  
  [Tasks](../msbuild/msbuild-tasks.md)   
diff --git a/docs/msbuild/build-loggers.md b/docs/msbuild/build-loggers.md
@@ -73,5 +73,5 @@ MSBuild /nologo /noconsolelogger /logger:SimpleLogger.dll /verbosity:Detailed
  [!code-csharp[msbuild_BasicLogger#1](../msbuild/codesnippet/CSharp/build-loggers_5.cs)]  
   
 ## See also  
- [Obtaining build logs](../msbuild/obtaining-build-logs-with-msbuild.md)   
+ [Obtain build logs](../msbuild/obtaining-build-logs-with-msbuild.md)   
  [MSBuild concepts](../msbuild/msbuild-concepts.md)
diff --git a/docs/msbuild/cppclean-task.md b/docs/msbuild/cppclean-task.md
@@ -34,7 +34,7 @@ Deletes the temporary files that MSBuild creates when a Visual C++ project is bu
 |**DoDelete**|Optional **Boolean** parameter.<br /><br /> If `true`, clean temporary build files.|  
 |**FilePatternsToDeleteOnClean**|Required `String` parameter.<br /><br /> Specifies a semicolon-delimited list of file extensions of files to clean.|  
 |**FilesExcludedFromClean**|Optional `String` parameter.<br /><br /> Specifies a semicolon-delimited list of files not to clean.|  
-|**FoldersToClean**|Required `String` parameter.<br /><br /> Specifies a semicolon-delimited list of directories to clean. You can specify a full or a relative path, and the path can contain the wildcard symbol (**\***).|  
+|**FoldersToClean**|Required `String` parameter.<br /><br /> Specifies a semicolon-delimited list of directories to clean. You can specify a full or a relative path, and the path can contain the wildcard symbol (*).|  
   
 ## See also  
  [Task reference](../msbuild/msbuild-task-reference.md)
diff --git a/docs/msbuild/creating-forwarding-loggers.md b/docs/msbuild/creating-forwarding-loggers.md
@@ -35,6 +35,6 @@ Forwarding loggers improve logging efficiency by letting you choose the events y
  When you build a project on a multi-processor system, the build messages from each processor are not automatically interleaved in a unified sequence. Instead, you must establish a message grouping priority by using the <xref:Microsoft.Build.Framework.BuildEventContext> class that is attached to every message. For more information about multi-processor building, see [Logging in a multi-processor environment](../msbuild/logging-in-a-multi-processor-environment.md).  
   
 ## See also  
- [Obtaining build logs](../msbuild/obtaining-build-logs-with-msbuild.md)   
+ [Obtain build logs](../msbuild/obtaining-build-logs-with-msbuild.md)   
  [Build loggers](../msbuild/build-loggers.md)   
  [Logging in a multi-processor environment](../msbuild/logging-in-a-multi-processor-environment.md)
diff --git a/docs/msbuild/customize-your-build.md b/docs/msbuild/customize-your-build.md
@@ -18,7 +18,7 @@ ms.workload:
 
 MSBuild projects that use the standard build process (importing *Microsoft.Common.props* and *Microsoft.Common.targets*) have several extensibility hooks that you can use to customize your build process.
 
-## Adding arguments to command-line MSBuild invocations for your project
+## Add arguments to command-line MSBuild invocations for your project
 
 A *Directory.Build.rsp* file in or above your source directory will be applied to command-line builds of your project. For details, see [MSBuild response files](../msbuild/msbuild-response-files.md#directorybuildrsp).
 
@@ -132,7 +132,7 @@ afterward. This allows installed SDKs to augment the build logic of common proje
 
 The same directory structure is searched in `$(MSBuildUserExtensionsPath)`, which is the per-user folder *%LOCALAPPDATA%\Microsoft\MSBuild*. Files placed in that folder will be imported for all builds of the corresponding project type run under that user's credentials. You can disable the user extensions by setting properties named after the importing file in the pattern `ImportUserLocationsByWildcardBefore{ImportingFileNameWithNoDots}`. For example, setting `ImportUserLocationsByWildcardBeforeMicrosoftCommonProps` to `false` would prevent importing `$(MSBuildUserExtensionsPath)\$(MSBuildToolsVersion)\Imports\Microsoft.Common.props\ImportBefore\*`.
 
-## Customizing the solution build
+## Customize the solution build
 
 > [!IMPORTANT]
 > Customizing the solution build in this way applies only to command-line builds with *MSBuild.exe*. It **does not** apply to builds inside Visual Studio.
diff --git a/docs/msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md b/docs/msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md
@@ -38,7 +38,7 @@ Programming languages that target the .NET Framework use MSBuild project files t
   
 9.   Build incrementally.  
 
-This walkthrough shows how to build the project at the command prompt and examine the results. For more information about MSBuild and how to run MSBuild at the command prompt, see [Walkthrough: Using MSBuild](../msbuild/walkthrough-using-msbuild.md).  
+This walkthrough shows how to build the project at the command prompt and examine the results. For more information about MSBuild and how to run MSBuild at the command prompt, see [Walkthrough: Use MSBuild](../msbuild/walkthrough-using-msbuild.md).  
 
 To complete the walkthrough, you must have the .NET Framework (version 2.0, 3.5, 4.0, or 4.5) installed because it includes MSBuild and the Visual C# compiler, which are required for the walkthrough.  
   
@@ -469,7 +469,7 @@ Your project file should now resemble the following code:
 ```  
   
 ## What's next?  
- Visual Studio can automatically do much of the work that is shown in this walkthrough. To learn how to use Visual Studio to create, edit, build, and test MSBuild project files, see [Walkthrough: Using MSBuild](../msbuild/walkthrough-using-msbuild.md).  
+ Visual Studio can automatically do much of the work that is shown in this walkthrough. To learn how to use Visual Studio to create, edit, build, and test MSBuild project files, see [Walkthrough: Use MSBuild](../msbuild/walkthrough-using-msbuild.md).  
   
 ## See also  
 [MSBuild overview](../msbuild/msbuild.md)  
diff --git a/docs/msbuild/walkthrough-using-msbuild.md b/docs/msbuild/walkthrough-using-msbuild.md
@@ -13,7 +13,7 @@ manager: douge
 ms.workload:
   - "multiple"
 ---
-# Walkthrough: Using MSBuild
+# Walkthrough: Use MSBuild
 MSBuild is the build platform for Microsoft and Visual Studio. This walkthrough introduces you to the building blocks of MSBuild and shows you how to write, manipulate, and debug MSBuild projects. You will learn about:
 
 -   Creating and manipulating a project file.
