more changes

mikeblome · mikeblome · commit d833b43497fb · 2019-01-08T09:36:08.000-08:00
diff --git a/docs/build/TOC.md b/docs/build/TOC.md
@@ -75,7 +75,7 @@
 ## [Localized Resources in MFC Applications: Satellite DLLs](localized-resources-in-mfc-applications-satellite-dlls.md)
 ## [Importing and Exporting](importing-and-exporting.md)
 ### [Importing into an Application](importing-into-an-application.md)
-#### [Importing into an Application Using __declspec(dllimport)](importing-into-an-application-using-declspec-dllimport.md)
+#### [Import into an application using __declspec(dllimport)](importing-into-an-application-using-declspec-dllimport.md)
 #### [Importing Function Calls Using __declspec(dllimport)](importing-function-calls-using-declspec-dllimport.md)
 #### [Importing Data Using __declspec(dllimport)](importing-data-using-declspec-dllimport.md)
 #### [Importing Using DEF Files](importing-using-def-files.md)
@@ -88,7 +88,7 @@
 #### [Determine Which Exporting Method to Use](determining-which-exporting-method-to-use.md)
 #### [Exporting Functions from a DLL by Ordinal Rather Than by Name](exporting-functions-from-a-dll-by-ordinal-rather-than-by-name.md)
 ### [Mutual Imports](mutual-imports.md)
-### [Importing and Exporting Inline Functions](importing-and-exporting-inline-functions.md)
+### [Importing and exporting inline functions](importing-and-exporting-inline-functions.md)
 ## [Active Technology and DLLs](active-technology-and-dlls.md)
 ## [Automation in a DLL](automation-in-a-dll.md)
 ## [Calling DLL Functions from Visual Basic Applications](calling-dll-functions-from-visual-basic-applications.md)
diff --git a/docs/build/building-on-the-command-line.md b/docs/build/building-on-the-command-line.md
@@ -162,7 +162,7 @@ Describes how to start a command prompt window that has the required environment
 [NMAKE Reference](reference/nmake-reference.md)<br/>
 Provides links to articles that describe the Microsoft Program Maintenance Utility (NMAKE.EXE).
 
-[MSBuild (Visual C++)](msbuild-visual-cpp.md)<br/>
+[MSBuild on the command line - C++](msbuild-visual-cpp.md)<br/>
 Provides links to articles that discuss how to use msbuild.exe from the command line.
 
 ## Related Sections
diff --git a/docs/build/dll-frequently-asked-questions.md b/docs/build/dll-frequently-asked-questions.md
@@ -52,7 +52,7 @@ If your DLL is a regular MFC DLL that is statically linked to MFC, changing it t
 
 If the DLL has a large number of exported functions, use a .def file to export the functions (instead of using **__declspec(dllexport)**) and use the .def file [NONAME attribute](exporting-functions-from-a-dll-by-ordinal-rather-than-by-name.md) on each exported function. The NONAME attribute causes only the ordinal value and not the function name to be stored in the DLL's export table, which reduces the file size.
 
-DLLs that are implicitly linked to an application are loaded when the application loads. To improve the performance when loading, try dividing the DLL into different DLLs. Put all the functions that the calling application needs immediately after loading into one DLL and have the calling application implicitly link to that DLL. Put the other functions that the calling application does not need right away into another DLL and have the application explicitly link to that DLL. For more information, see [Determine which linking method to use](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use).
+DLLs that are implicitly linked to an application are loaded when the application loads. To improve the performance when loading, try dividing the DLL into different DLLs. Put all the functions that the calling application needs immediately after loading into one DLL and have the calling application implicitly link to that DLL. Put the other functions that the calling application does not need right away into another DLL and have the application explicitly link to that DLL. For more information, see [Link an executable to a DLL](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use).
 
 ## <a name="memory_leak"></a> There&#39;s a memory leak in my regular MFC DLL, but my code looks fine. How can I find the memory leak?
 
diff --git a/docs/build/exporting-from-a-dll.md b/docs/build/exporting-from-a-dll.md
@@ -32,7 +32,7 @@ When exporting functions with either method, make sure to use the [__stdcall](..
 
 - [Determine which exporting method to use](determining-which-exporting-method-to-use.md)
 
-- [Determine which linking method to use](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
+- [Link an executable to a DLL](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
 
 - [Initialize a DLL](run-time-library-behavior.md#initializing-a-dll)
 
diff --git a/docs/build/freelibrary-and-afxfreelibrary.md b/docs/build/freelibrary-and-afxfreelibrary.md
@@ -13,9 +13,9 @@ In an MFC application, use [AfxFreeLibrary](../mfc/reference/application-informa
 
 ## What do you want to do?
 
-- [How to link implicitly to a DLL](linking-an-executable-to-a-dll.md#linking-implicitly)
+- [Link an executable to a DLL](linking-an-executable-to-a-dll.md#linking-implicitly)
 
-- [Determine which linking method to use](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
+- [Link an executable to a DLL](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
 
 ## What do you want to know more about?
 
diff --git a/docs/build/getprocaddress.md b/docs/build/getprocaddress.md
@@ -45,9 +45,9 @@ You can only obtain the export ordinal if the DLL you are linking to is built wi
 
 ## What do you want to do?
 
-- [How to link implicitly to a DLL](linking-an-executable-to-a-dll.md#linking-implicitly)
+- [Link an executable to a DLL](linking-an-executable-to-a-dll.md#linking-implicitly)
 
-- [Determine which linking method to use](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
+- [Link an executable to a DLL](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
 
 ## What do you want to know more about?
 
diff --git a/docs/build/how-to-integrate-custom-tools-into-the-project-properties.md b/docs/build/how-to-integrate-custom-tools-into-the-project-properties.md
@@ -31,4 +31,4 @@ This document explains how to create a file in a set directory that contains pro
 
 ## See Also
 
-[MSBuild (Visual C++)](msbuild-visual-cpp.md)
+[MSBuild on the command line - C++](msbuild-visual-cpp.md)
diff --git a/docs/build/how-to-modify-the-target-framework-and-platform-toolset.md b/docs/build/how-to-modify-the-target-framework-and-platform-toolset.md
@@ -53,4 +53,4 @@ You can extend the target platform further by creating a custom platform toolset
 
 ## See Also
 
-[MSBuild (Visual C++)](msbuild-visual-cpp.md)
+[MSBuild on the command line - C++](msbuild-visual-cpp.md)
diff --git a/docs/build/how-to-use-build-events-in-msbuild-projects.md b/docs/build/how-to-use-build-events-in-msbuild-projects.md
@@ -64,5 +64,5 @@ The following example can be added inside of the Project element of the myprojec
 
 ## See Also
 
-[MSBuild (Visual C++)](msbuild-visual-cpp.md)<br/>
+[MSBuild on the command line - C++](msbuild-visual-cpp.md)<br/>
 [Walkthrough: Using MSBuild to Create a Visual C++ Project](walkthrough-using-msbuild-to-create-a-visual-cpp-project.md)
diff --git a/docs/build/importing-and-exporting-inline-functions.md b/docs/build/importing-and-exporting-inline-functions.md
@@ -1,10 +1,10 @@
 ---
-title: "Importing and Exporting Inline Functions"
+title: "Importing and exporting inline functions"
 ms.date: "11/04/2016"
 helpviewer_keywords: ["exporting functions [C++], inline functions", "inline functions [C++], importing", "DLLs [C++], importing", "importing functions [C++]", "DLLs [C++], exporting from", "importing inline functions [C++]", "inline functions [C++], exporting", "functions [C++], importing", "functions [C++], exporting"]
 ms.assetid: 89f488f8-b078-40fe-afd7-80bd7840057b
 ---
-# Importing and Exporting Inline Functions
+# Importing and exporting inline functions
 
 Imported functions can be defined as inline. The effect is roughly the same as defining a standard function inline; calls to the function are expanded into inline code, much like a macro. This is principally useful as a way of supporting C++ classes in a DLL that might inline some of their member functions for efficiency.
 
diff --git a/docs/build/importing-into-an-application-using-declspec-dllimport.md b/docs/build/importing-into-an-application-using-declspec-dllimport.md
@@ -1,11 +1,11 @@
 ---
-title: "Importing into an Application Using __declspec(dllimport)"
+title: "Import into an application using __declspec(dllimport)"
 ms.date: "11/04/2016"
 f1_keywords: ["__declspec", "dllimport"]
 helpviewer_keywords: ["__declspec(dllimport) keyword [C++]", "importing DLLs [C++], __declspec(dllimport)"]
 ms.assetid: edb4da4e-f83a-44cf-a668-9239d49dbe42
 ---
-# Importing into an Application Using __declspec(dllimport)
+# Import into an application using __declspec(dllimport)
 
 A program that uses public symbols defined by a DLL is said to import them. When you create header files for applications that use your DLLs to build with, use **__declspec(dllimport)** on the declarations of the public symbols. The keyword **__declspec(dllimport)** works whether you export with .def files or with the **__declspec(dllexport)** keyword.
 
diff --git a/docs/build/linking-an-executable-to-a-dll.md b/docs/build/linking-an-executable-to-a-dll.md
@@ -16,7 +16,7 @@ An executable can use either linking method to link to the same DLL. Furthermore
 
 <a name="determining-which-linking-method-to-use"></a>
 
-## Determine which linking method to use
+## Link an executable to a DLL
 
 Whether to use implicit linking or explicit linking is an architectural decision you must make for your application. There are advantages and disadvantages to each method.
 
@@ -56,7 +56,7 @@ Here are two hazards of explicit linking to be aware of:
 
 <a name="linking-implicitly"></a>
 
-## How to link implicitly to a DLL
+## Link an executable to a DLL
 
 To use a DLL by implicit linking, client executables must obtain these files from the provider of the DLL:
 
diff --git a/docs/build/loadlibrary-and-afxloadlibrary.md b/docs/build/loadlibrary-and-afxloadlibrary.md
@@ -22,9 +22,9 @@ If Windows cannot load the DLL, the process can attempt to recover from the erro
 
 ## What do you want to do?
 
-- [How to link implicitly to a DLL](linking-an-executable-to-a-dll.md#linking-implicitly)
+- [Link an executable to a DLL](linking-an-executable-to-a-dll.md#linking-implicitly)
 
-- [Determine which linking method to use](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
+- [Link an executable to a DLL](linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
 
 ## What do you want to know more about?
 
diff --git a/docs/build/msbuild-visual-cpp.md b/docs/build/msbuild-visual-cpp.md
@@ -1,11 +1,11 @@
 ---
-title: "MSBuild on the Command Line - C++"
+title: "MSBuild on the command line - C++"
 ms.date: "12/12/2018"
 f1_keywords: ["MSBuild"]
 helpviewer_keywords: ["MSBuild"]
 ms.assetid: 7a1be7ff-0312-4669-adf2-5f5bf507d560
 ---
-# MSBuild (Visual C++)
+# MSBuild on the command line - C++
 
 In general, we recommend that you use Visual Studio to set project properties and invoke the MSBuild system. However, you can use the **MSBuild** tool directly from the command prompt. The build process is controlled by the information in a project file (.vcxproj) that you can create and edit. The project file specifies build options based on build stages, conditions, and events. In addition, you can specify zero or more command-line *options* arguments.
 
diff --git a/docs/build/reference/TOC.md b/docs/build/reference/TOC.md
@@ -1,7 +1,7 @@
 # [C/C++ Building Reference](c-cpp-building-reference.md)
 # [MSBuild reference for C++ projects](msbuild-reference-cpp.md)
 ## [MSBuild internals for C++ projects](msbuild-visual-cpp-overview.md)
-## [Common Macros for Build Commands and Properties](common-macros-for-build-commands-and-properties.md)
+## [Common macros for build commands and properties](common-macros-for-build-commands-and-properties.md)
 ## [File types used in C++ projects](file-types-created-for-visual-cpp-projects.md)
 ### [Project and solution files](project-and-solution-files.md)
 ### [C++ project templates](visual-cpp-project-types.md)
@@ -202,7 +202,7 @@
 #### [/Zs (Syntax Check Only)](zs-syntax-check-only.md)
 #### [/ZW (Windows Runtime Compilation)](zw-windows-runtime-compilation.md)
 ## [Unicode Support in the Compiler and Linker](unicode-support-in-the-compiler-and-linker.md)
-# [MSVC Linker Reference](linking.md)
+# [MSVC linker reference](linking.md)
 ## [MSVC Linker Options](linker-options.md)
 ### [Compiler-Controlled LINK Options](compiler-controlled-link-options.md)
 ### [LINK Input Files](link-input-files.md)
diff --git a/docs/build/reference/c-cpp-building-reference.md b/docs/build/reference/c-cpp-building-reference.md
@@ -16,7 +16,7 @@ Visual C++ provides two ways of building a C/C++ program. The easiest (and most
 [MSVC Compiler Reference](compiling-a-c-cpp-program.md)<br/>
 Describes the MSVC compiler, which creates an object file containing machine code, linker directives, sections, external references, and function/data names.
 
-[MSVC Linker Reference](linking.md)<br/>
+[MSVC linker reference](linking.md)<br/>
 Describes the linker, which combines code from the object files created by the compiler and from statically linked libraries, resolves the name references, and creates an executable file.
 
 [Unicode Support in the Compiler and Linker](unicode-support-in-the-compiler-and-linker.md)
diff --git a/docs/build/reference/dependentloadflag.md b/docs/build/reference/dependentloadflag.md
@@ -44,7 +44,7 @@ If you specify the link option `/DEPENDENTLOADFLAG:0xA00` (the value of the comb
 
 - [MSVC linker reference](linking.md)
 - [MSVC Linker Options](linker-options.md)
-- [How to link implicitly to a DLL](../linking-an-executable-to-a-dll.md#linking-implicitly)
-- [Determine which linking method to use](../linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
+- [Link an executable to a DLL](../linking-an-executable-to-a-dll.md#linking-implicitly)
+- [Link an executable to a DLL](../linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
 - [LoadLibraryEx](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexa)
 - [Dynamic-Link Library Search Order](/windows/desktop/Dlls/dynamic-link-library-search-order)
diff --git a/docs/build/reference/general-property-page-project.md b/docs/build/reference/general-property-page-project.md
@@ -66,7 +66,7 @@ The properties in the General section affect the location of files that are crea
 
    Allows you to specify a non-default location for the log file that is created whenever you build a project. The default location is specified by the macros $(IntDir)$(MSBuildProjectName).log.
 
-   You can use project macros to change the directory location. See [Common Macros for Build Commands and Properties](common-macros-for-build-commands-and-properties.md).
+   You can use project macros to change the directory location. See [Common macros for build commands and properties](common-macros-for-build-commands-and-properties.md).
 
 - **Platform Toolset**
 
diff --git a/docs/build/reference/linker-support-for-delay-loaded-dlls.md b/docs/build/reference/linker-support-for-delay-loaded-dlls.md
@@ -45,4 +45,4 @@ The following topics describe delay loading DLLs:
 ## See Also
 
 [DLLs in Visual C++](../dlls-in-visual-cpp.md)<br/>
-[MSVC Linker Reference](linking.md)
+[MSVC linker reference](linking.md)
diff --git a/docs/build/reference/linking.md b/docs/build/reference/linking.md
@@ -1,5 +1,5 @@
 ---
-title: "MSVC Linker Reference"
+title: "MSVC linker reference"
 ms.date: "12/10/2018"
 ms.assetid: bb736587-d13b-4f3c-8982-3cc2c015c59c
 ---
diff --git a/docs/build/reference/msbuild-reference-cpp.md b/docs/build/reference/msbuild-reference-cpp.md
@@ -15,7 +15,7 @@ If for some reason you wish to use MSBuild directly from the command line, see [
 [MSBuild internals for C++ projects](msbuild-visual-cpp-overview.md)<br/>
 Information about how properties and targets are stored and consumed.
 
-[Common Macros for Build Commands and Properties](common-macros-for-build-commands-and-properties.md)<br/>
+[Common macros for build commands and properties](common-macros-for-build-commands-and-properties.md)<br/>
 Describes macros (compile-time constants) that can be used to define properties such as paths and product versions.
 
 [File types created for C++ projects](file-types-created-for-visual-cpp-projects.md)<br/>
diff --git a/docs/build/reference/project-files.md b/docs/build/reference/project-files.md
@@ -6,7 +6,7 @@ ms.assetid: 5261cf45-3136-40a6-899e-dc1339551401
 ---
 # Project Files
 
-A Visual C++ project file is an XML-based file that has the .vcxproj file name extension and contains information that is required to build a Visual C++ project. Note that the project file imports various project files that have the extension *.props* or *.targets*. These files contain additional build information, and might themselves refer to other *.props* or *.targets* files. The macros in the file path (for example `$(VCTargetsPath)`) are dependent on your Visual Studio installation. For more information about these macros and *.props* and *.targets* files, see [VC++ Directories Property Page](vcpp-directories-property-page.md), [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md) and [Common Macros for Build Commands and Properties](common-macros-for-build-commands-and-properties.md).
+A Visual C++ project file is an XML-based file that has the .vcxproj file name extension and contains information that is required to build a Visual C++ project. Note that the project file imports various project files that have the extension *.props* or *.targets*. These files contain additional build information, and might themselves refer to other *.props* or *.targets* files. The macros in the file path (for example `$(VCTargetsPath)`) are dependent on your Visual Studio installation. For more information about these macros and *.props* and *.targets* files, see [VC++ Directories Property Page](vcpp-directories-property-page.md), [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md) and [Common macros for build commands and properties](common-macros-for-build-commands-and-properties.md).
 
 ## Example
 
diff --git a/docs/build/reference/vcpp-directories-property-page.md b/docs/build/reference/vcpp-directories-property-page.md
@@ -51,7 +51,7 @@ Note: The list is populated as you type. Don't press **Enter**.
 
 For more information about macros and why you should use them instead of hard-coded paths whenever possible, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-For a list of commonly used macros, see [Common Macros for Build Commands and Properties](common-macros-for-build-commands-and-properties.md).
+For a list of commonly used macros, see [Common macros for build commands and properties](common-macros-for-build-commands-and-properties.md).
 
 You can define your own macros in two ways:
 
diff --git a/docs/build/reference/xml-document-generator-tool-property-pages.md b/docs/build/reference/xml-document-generator-tool-property-pages.md
@@ -23,7 +23,7 @@ The XML Document Generator Tool property page exposes the functionality of xdcma
 
 - **Output Document File**
 
-   The name and directory location of the .xml output file. See [Common Macros for Build Commands and Properties](common-macros-for-build-commands-and-properties.md) for information on using macros to specify directory locations.
+   The name and directory location of the .xml output file. See [Common macros for build commands and properties](common-macros-for-build-commands-and-properties.md) for information on using macros to specify directory locations.
 
 - **Document Library Dependencies**
 
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
@@ -20,7 +20,7 @@ To see which environment variables are set by a developer command prompt shortcu
 ## See Also
 
 [Use the MSVC toolset from the command line](building-on-the-command-line.md)<br/>
-[MSVC Linker Reference](reference/linking.md)<br/>
+[MSVC linker reference](reference/linking.md)<br/>
 [MSVC Linker Options](reference/linker-options.md)<br/>
 [MSVC Compiler Reference](reference/compiling-a-c-cpp-program.md)<br/>
 [MSVC Compiler Options](reference/compiler-options.md)
diff --git a/docs/build/specifying-build-events.md b/docs/build/specifying-build-events.md
@@ -27,7 +27,7 @@ For general information on build events, see [Understanding Custom Build Steps a
 
    - In **Command Line**, specify a command as if you were specifying it at the command prompt. Specify a valid command or batch file, and any required input or output files. Specify the **call** batch command before the name of a batch file to guarantee that all subsequent commands are executed.
 
-      Multiple input and output files can be specified symbolically with MSBuild macros. For information on how to specify the location of files, or the names of sets of files, see [Common Macros for Build Commands and Properties](reference/common-macros-for-build-commands-and-properties.md).
+      Multiple input and output files can be specified symbolically with MSBuild macros. For information on how to specify the location of files, or the names of sets of files, see [Common macros for build commands and properties](reference/common-macros-for-build-commands-and-properties.md).
 
       Because the '%' character is reserved by MSBuild, if you specify an environment variable replace each **%** escape character with the **%25** hexadecimal escape sequence. For example, replace **%WINDIR%** with **%25WINDIR%25**. MSBuild replaces each **%25** sequence with the **%** character before it accesses the environment variable.
 
@@ -38,5 +38,5 @@ For general information on build events, see [Understanding Custom Build Steps a
 ## See also
 
 [Understanding Custom Build Steps and Build Events](understanding-custom-build-steps-and-build-events.md)<br>
-[Common Macros for Build Commands and Properties](reference/common-macros-for-build-commands-and-properties.md)<br>
+[Common macros for build commands and properties](reference/common-macros-for-build-commands-and-properties.md)<br>
 [Troubleshooting Build Customizations](troubleshooting-build-customizations.md)
diff --git a/docs/build/specifying-custom-build-tools.md b/docs/build/specifying-custom-build-tools.md
diff --git a/docs/build/understanding-custom-build-steps-and-build-events.md b/docs/build/understanding-custom-build-steps-and-build-events.md

Original file line number	Diff line number	Diff line change
`@@ -31,4 +31,4 @@ This document explains how to create a file in a set directory that contains pro`
`31`	`31`
`32`	`32`	`## See Also`
`33`	`33`
`34`		`-[MSBuild (Visual C++)](msbuild-visual-cpp.md)`
	`34`	`+[MSBuild on the command line - C++](msbuild-visual-cpp.md)`
Original file line number	Diff line number	Diff line change
`@@ -53,4 +53,4 @@ You can extend the target platform further by creating a custom platform toolset`
`53`	`53`
`54`	`54`	`## See Also`
`55`	`55`
`56`		`-[MSBuild (Visual C++)](msbuild-visual-cpp.md)`
	`56`	`+[MSBuild on the command line - C++](msbuild-visual-cpp.md)`