Minor tweak

Colin Robertson · Colin Robertson · commit 256d74a2a201 · 2017-08-24T16:29:51.000-07:00
diff --git a/docs/build/setting-the-path-and-environment-variables-for-command-line-builds.md b/docs/build/setting-the-path-and-environment-variables-for-command-line-builds.md
@@ -50,7 +50,7 @@ translation.priority.mt:
 
 The Visual C++ command-line build tools require several environment variables that are customized for your installation. When a C++ workload is installed by the [!INCLUDE[vsprvs](../assembler/masm/includes/vsprvs_md.md)] installer, it creates customized command files that set the required environment variables, and then creates shortcuts for the Windows Start menu that start a command prompt window that already has these variables set. When you want to use the command-line tools, you can run one of these shortcuts, or you can open a plain command prompt window and then run one of the custom command files to set the build configuration environment. For more information, see [Build C/C++ Code on the Command Line](building-on-the-command-line.md).  
   
-The Visual C++ command-line tools use the PATH, TMP, INCLUDE, LIB, and LIBPATH environment variables, and also use other environment variables specific to tools, platforms, and SDKs. Even a simple [!INCLUDE[vsprvs](../assembler/masm/includes/vsprvs_md.md)] installation may set twenty or more environment variables. Because the values of these environment variables are specific to your installation and your choice of build configuration, and can be changed by product updates or upgrades, we strongly recommend that you use a developer command prompt shortcut or one of the customized command files to set them, instead of setting them in the Windows environment yourself. 
+The Visual C++ command-line tools use the PATH, TMP, INCLUDE, LIB, and LIBPATH environment variables, and also use other environment variables specific to your installed tools, platforms, and SDKs. Even a simple [!INCLUDE[vsprvs](../assembler/masm/includes/vsprvs_md.md)] installation may set twenty or more environment variables. Because the values of these environment variables are specific to your installation and your choice of build configuration, and can be changed by product updates or upgrades, we strongly recommend that you use a developer command prompt shortcut or one of the customized command files to set them, instead of setting them in the Windows environment yourself. 
 
 To see which environment variables are set by a developer command prompt shortcut, you can use the SET command. Open a plain command prompt window and capture the output of the SET command for a baseline. Open a developer command prompt window and capture the output of the SET command for comparison. A diff tool such as the one built into the Visual Studio IDE can be useful to compare the environment variables and see what is set by the developer command prompt. For information about the specific environment variables used by the compiler and linker, see [CL Environment Variables](../build/reference/cl-environment-variables.md) and [LINK Environment Variables](../build/reference/link-environment-variables.md).  
   
