MicrosoftDocs · colin-home · Mar 4, 2019 · Feb 7, 2019
diff --git a/docs/build/active-technology-and-dlls.md b/docs/build/active-technology-and-dlls.md
@@ -14,6 +14,6 @@ If you are writing an Automation server and your server has no user interface, y
 
 - [Automation Servers](../mfc/automation-servers.md)
 
-## See Also
+## See also
 
-[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
+[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
diff --git a/docs/build/automation-in-a-dll.md b/docs/build/automation-in-a-dll.md
@@ -22,6 +22,6 @@ When you choose the Automation option in the MFC DLL Wizard, the wizard provides
 
 - [Automation Servers](../mfc/automation-servers.md)
 
-## See Also
+## See also
 
-[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
+[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
diff --git a/docs/build/batch-mode-rules.md b/docs/build/batch-mode-rules.md
@@ -80,6 +80,6 @@ foo4.cpp
 Generating Code...
 ```
 
-## See Also
+## See also
 
-[Inference Rules](../build/inference-rules.md)
+[Inference Rules](../build/inference-rules.md)
diff --git a/docs/build/build-system-changes.md b/docs/build/build-system-changes.md
@@ -58,6 +58,6 @@ You cannot change the VC++ directories settings if you run [devenv /resetsetting
 
 Migrate VC++ directories settings from a .vssettings file that is created by an earlier release of Visual C++. Open the **Tools** menu, click **Import and Export Settings**, select **Import selected environment settings**, and then follow the directions in the wizard. Or when you start Visual Studio for the first time, on the **Choose Default Environment Settings** dialog box, select **Migrate my eligible settings from a previous version and apply them in addition to the default settings selected below**.
 
-## See Also
+## See also
 
-[MSBuild (Visual C++)](../build/msbuild-visual-cpp.md)
+[MSBuild (Visual C++)](../build/msbuild-visual-cpp.md)
diff --git a/docs/build/building-c-cpp-isolated-applications.md b/docs/build/building-c-cpp-isolated-applications.md
@@ -10,7 +10,7 @@ An isolated application depends only on side-by-side assemblies and binds to its
 
 When you build your native C/C++ application using Visual C++, by default the Visual Studio project system generates a manifest file that describes your application's dependencies on Visual C++ libraries. If these are the only dependencies your application has, then it becomes an isolated application as soon as it is rebuilt with Visual Studio. If your application is using other libraries at runtime, then you may need to rebuild those libraries as side-by-side assemblies following the steps described in [Building C/C++ Side-by-side Assemblies](../build/building-c-cpp-side-by-side-assemblies.md).
 
-## See Also
+## See also
 
 [Concepts of Isolated Applications and Side-by-side Assemblies](../build/concepts-of-isolated-applications-and-side-by-side-assemblies.md)<br/>
-[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
+[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
diff --git a/docs/build/building-c-cpp-side-by-side-assemblies.md b/docs/build/building-c-cpp-side-by-side-assemblies.md
@@ -22,8 +22,8 @@ One or several related DLLs can be repackaged into a side-by-side assembly with
 
 This change may allow deployment of corresponding DLLs as a [private assembly](/windows/desktop/Msi/private-assemblies) in an application local folder or as a [shared assembly](/windows/desktop/Msi/shared-assemblies) in the WinSxS assembly cache. Several steps have to be followed in order to achieve correct runtime behavior of this new assembly; they are described in [Guidelines for Creating Side-by-side Assemblies](/windows/desktop/SbsCs/guidelines-for-creating-side-by-side-assemblies). After an assembly is correctly authored it can deployed as either a shared or private assembly together with an application that depends on it. When installing side-by-side assemblies as a shared assembly, you may either follow the guidelines outlined in [Installing Win32 Assemblies for Side-by-Side Sharing on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-side-by-side-sharing-on-windows-xp) or use [merge modules](/windows/desktop/msi/merge-modules). When installing side-by-side assemblies as a private assembly, you may just copy the corresponding DLL, resources and assembly manifest as part of the installation process to the application local folder on the target computer, ensuring that this assembly can be found by the loader at runtime (see [Assembly Searching Sequence](/windows/desktop/SbsCs/assembly-searching-sequence)). Another way is to use [Windows Installer](/windows/desktop/Msi/windows-installer-portal) and follow the guidelines outlined in [Installing Win32 Assemblies for the Private Use of an Application on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-the-private-use-of-an-application-on-windows-xp).
 
-## See Also
+## See also
 
 [Deployment Examples](../ide/deployment-examples.md)<br/>
 [Building C/C++ Isolated Applications](../build/building-c-cpp-isolated-applications.md)<br/>
-[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
+[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
diff --git a/docs/build/calling-dll-functions-from-visual-basic-applications.md b/docs/build/calling-dll-functions-from-visual-basic-applications.md
@@ -57,6 +57,6 @@ For DLLs to be called by programs written in Visual Basic, the alias technique s
 
 - [Decorated names](../build/reference/decorated-names.md)
 
-## See Also
+## See also
 
 [DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
diff --git a/docs/build/command-macros-and-options-macros.md b/docs/build/command-macros-and-options-macros.md
@@ -17,6 +17,6 @@ Command macros are predefined for Microsoft products. Options macros represent o
 |C++ Compiler|**CXX**|cl|**CXXFLAGS**|
 |Resource Compiler|**RC**|rc|**RFLAGS**|
 
-## See Also
+## See also
 
-[Special NMAKE Macros](../build/special-nmake-macros.md)
+[Special NMAKE Macros](../build/special-nmake-macros.md)
diff --git a/docs/build/command-modifiers.md b/docs/build/command-modifiers.md
@@ -14,6 +14,6 @@ You can specify one or more command modifiers preceding a command, optionally se
 |**-**\[*number*] *command*|Turns off error checking for *command*. By default, NMAKE halts when a command returns a nonzero exit code. If -*number* is used, NMAKE stops if the exit code exceeds *number*. Spaces or tabs cannot appear between the dash and *number.* At least one space or tab must appear between `number` and *command*. Use /I to turn off error checking for the entire makefile; use **.IGNORE** to turn off error checking for part of the makefile.|
 |**!** *command*|Executes *command* for each dependent file if *command* uses <strong>$\*\*</strong> (all dependent files in the dependency) or **$?** (all dependent files in the dependency with a later timestamp than the target).|
 
-## See Also
+## See also
 
 [Commands in a Makefile](../build/commands-in-a-makefile.md)
diff --git a/docs/build/commands-in-a-makefile.md b/docs/build/commands-in-a-makefile.md
@@ -26,6 +26,6 @@ project.obj : project.c project.h ; cl /c project.c
 
 [Inline files in a makefile](../build/inline-files-in-a-makefile.md)
 
-## See Also
+## See also
 
-[NMAKE Reference](../build/nmake-reference.md)
+[NMAKE Reference](../build/nmake-reference.md)
diff --git a/docs/build/comments-in-a-makefile.md b/docs/build/comments-in-a-makefile.md
@@ -32,6 +32,6 @@ To specify a literal number sign, precede it with a caret (**^**), as follows:
 DEF = ^#define  #Macro for a C preprocessing directive
 ```
 
-## See Also
+## See also
 
-[Contents of a Makefile](../build/contents-of-a-makefile.md)
+[Contents of a Makefile](../build/contents-of-a-makefile.md)
diff --git a/docs/build/common-visual-cpp-64-bit-migration-issues.md b/docs/build/common-visual-cpp-64-bit-migration-issues.md
@@ -30,7 +30,7 @@ For more information, see:
 
 - [Migration Tips](/windows/desktop/WinProg64/migration-tips)
 
-## See Also
+## See also
 
 [Configure Visual C++ for 64-bit, x64 targets](../build/configuring-programs-for-64-bit-visual-cpp.md)<br/>
-[Visual C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md)
+[Visual C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md)
diff --git a/docs/build/concepts-of-isolated-applications-and-side-by-side-assemblies.md b/docs/build/concepts-of-isolated-applications-and-side-by-side-assemblies.md
@@ -26,6 +26,6 @@ You can change side-by-side assembly dependencies after an application has been
 
 In Visual Studio 2005 and Visual Studio 2008, redistributable libraries such as ATL, MFC, CRT, Standard C++, OpenMP, and MSDIA were deployed as shared side-by-side assemblies to the native assembly cache. In the current version, the redistributable libraries use central deployment. By default, all applications that are built by using Visual C++ are built with the manifest embedded in the final binary, and the manifest describes the dependencies of the binary on the Visual C++ libraries. To understand manifest generation for Visual C++ applications, see [Understanding Manifest Generation for C/C++ Programs](../build/understanding-manifest-generation-for-c-cpp-programs.md). A manifest is not required for applications that are statically linked to the libraries that they use, or that use local deployment. For more information about deployment, see [Deployment in Visual C++](../ide/deployment-in-visual-cpp.md).
 
-## See Also
+## See also
 
-[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
+[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
diff --git a/docs/build/configuring-programs-for-64-bit-visual-cpp.md b/docs/build/configuring-programs-for-64-bit-visual-cpp.md
@@ -34,6 +34,6 @@ This section contains topics about targeting 64-bit x64 hardware with the Visual
 
 [x64 (amd64) Intrinsics List](../intrinsics/x64-amd64-intrinsics-list.md)
 
-## See Also
+## See also
 
-[Building C/C++ Programs](building-c-cpp-programs.md)
+[Building C/C++ Programs](building-c-cpp-programs.md)
diff --git a/docs/build/contents-of-a-makefile.md b/docs/build/contents-of-a-makefile.md
@@ -26,6 +26,6 @@ Other features you can use in a makefile are [wildcards](../build/wildcards-and-
 
 For a sample, see [Sample Makefile](../build/sample-makefile.md).
 
-## See Also
+## See also
 
-[NMAKE Reference](../build/nmake-reference.md)
+[NMAKE Reference](../build/nmake-reference.md)
diff --git a/docs/build/creating-a-resource-only-dll.md b/docs/build/creating-a-resource-only-dll.md
@@ -38,7 +38,7 @@ The application that uses the resource-only DLL should call [LoadLibrary](../bui
 
 The application should call `FreeLibrary` when it is finished using the resources.
 
-## See Also
+## See also
 
 [Working with Resource Files](../windows/working-with-resource-files.md)<br/>
-[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
+[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
diff --git a/docs/build/creating-inline-file-text.md b/docs/build/creating-inline-file-text.md
@@ -24,6 +24,6 @@ Specify *inlinetext* on the first line after the command. Mark the end with doub
 
 A temporary file exists for the duration of the session and can be reused by other commands. Specify **KEEP** after the closing angle brackets to retain the file after the NMAKE session; an unnamed file is preserved on disk with the generated filename. Specify **NOKEEP** or nothing for a temporary file. **KEEP** and **NOKEEP** are not case sensitive.
 
-## See Also
+## See also
 
-[Inline Files in a Makefile](../build/inline-files-in-a-makefile.md)
+[Inline Files in a Makefile](../build/inline-files-in-a-makefile.md)
diff --git a/docs/build/cumulative-dependencies.md b/docs/build/cumulative-dependencies.md
@@ -45,6 +45,6 @@ climb.exe : up.obj
    echo Building bounce.exe...
 ```
 
-## See Also
+## See also
 
-[Targets](../build/targets.md)
+[Targets](../build/targets.md)
diff --git a/docs/build/defining-a-rule.md b/docs/build/defining-a-rule.md
@@ -21,6 +21,6 @@ Extensions are not case sensitive. Macros can be invoked to represent *fromext*
 
 [Search paths in rules](../build/search-paths-in-rules.md)
 
-## See Also
+## See also
 
-[Inference Rules](../build/inference-rules.md)
+[Inference Rules](../build/inference-rules.md)
diff --git a/docs/build/defining-an-nmake-macro.md b/docs/build/defining-an-nmake-macro.md
@@ -29,6 +29,6 @@ The `string` can be any sequence of zero or more characters. A null string conta
 
 [Precedence in macro definitions](../build/precedence-in-macro-definitions.md)
 
-## See Also
+## See also
 
-[Macros and NMAKE](../build/macros-and-nmake.md)
+[Macros and NMAKE](../build/macros-and-nmake.md)
diff --git a/docs/build/dependency-side-effects.md b/docs/build/dependency-side-effects.md
@@ -41,6 +41,6 @@ bounce.exe : up.obj
 # invokes an inference rule
 ```
 
-## See Also
+## See also
 
-[Targets](../build/targets.md)
+[Targets](../build/targets.md)
diff --git a/docs/build/dependents.md b/docs/build/dependents.md
@@ -14,6 +14,6 @@ In a dependency line, specify zero or more dependents after the colon (:) or dou
 
 [Search paths for dependents](../build/search-paths-for-dependents.md)
 
-## See Also
+## See also
 
-[Description Blocks](../build/description-blocks.md)
+[Description Blocks](../build/description-blocks.md)
diff --git a/docs/build/description-blocks.md b/docs/build/description-blocks.md
@@ -21,6 +21,6 @@ A dependency line specifies one or more targets and zero or more dependents. A t
 
 [Dependents](../build/dependents.md)
 
-## See Also
+## See also
 
-[NMAKE Reference](../build/nmake-reference.md)
+[NMAKE Reference](../build/nmake-reference.md)
diff --git a/docs/build/determining-which-exporting-method-to-use.md b/docs/build/determining-which-exporting-method-to-use.md
@@ -50,6 +50,6 @@ Using `__declspec(dllexport)` is convenient because you do not have to worry abo
 
 - [Decorated names](../build/reference/decorated-names.md)
 
-## See Also
+## See also
 
-[Exporting from a DLL](../build/exporting-from-a-dll.md)
+[Exporting from a DLL](../build/exporting-from-a-dll.md)
diff --git a/docs/build/dll-frequently-asked-questions.md b/docs/build/dll-frequently-asked-questions.md
@@ -58,6 +58,6 @@ DLLs that are implicitly linked to an application are loaded when the applicatio
 
 One possible cause of the memory leak is that MFC creates temporary objects that are used inside message handler functions. In MFC applications, these temporary objects are automatically cleaned up in the `CWinApp::OnIdle()` function that is called in between processing messages. However, in MFC dynamic-link libraries (DLLs), the `OnIdle()` function is not automatically called. As a result, temporary objects are not automatically cleaned up. To clean up temporary objects, the DLL must explicitly call `OnIdle(1)` periodically.
 
-## See Also
+## See also
 
-[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
+[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
diff --git a/docs/build/dot-directives.md b/docs/build/dot-directives.md
@@ -29,6 +29,6 @@ To add additional suffixes to the end of the list, specify
 
 where *suffixlist* is a list of the additional suffixes, separated by one or more spaces or tabs. To see the current setting of **.SUFFIXES**, run NMAKE with /P.
 
-## See Also
+## See also
 
-[NMAKE Reference](../build/nmake-reference.md)
+[NMAKE Reference](../build/nmake-reference.md)
diff --git a/docs/build/environment-variable-macros.md b/docs/build/environment-variable-macros.md
@@ -23,6 +23,6 @@ In this example, changing `PATH` changes the corresponding environment variable
 
 If an environment variable is defined as a string that would be syntactically incorrect in a makefile, no macro is created and no warning is generated. If a variable's value contains a dollar sign ($), NMAKE interprets it as the beginning of a macro invocation. Using the macro can cause unexpected behavior.
 
-## See Also
+## See also
 
-[Special NMAKE Macros](../build/special-nmake-macros.md)
+[Special NMAKE Macros](../build/special-nmake-macros.md)
diff --git a/docs/build/exception-handling-x64.md b/docs/build/exception-handling-x64.md
@@ -494,6 +494,6 @@ typedef struct _RUNTIME_FUNCTION {
     ((PVOID)((PULONG)GetLanguageSpecificData(info) + 1)
 ```
 
-## See Also
+## See also
 
-[x64 software conventions](../build/x64-software-conventions.md)
+[x64 software conventions](../build/x64-software-conventions.md)
diff --git a/docs/build/executing-a-program-in-preprocessing.md b/docs/build/executing-a-program-in-preprocessing.md
@@ -8,6 +8,6 @@ ms.assetid: 5ecf123a-20e5-40cd-b8d8-dd5a9fdd4b24
 
 To use a command's exit code during preprocessing, specify the command, with any arguments, within brackets ([ ]). Any macros are expanded before the command is executed. NMAKE replaces the command specification with the command's exit code, which can be used in an expression to control preprocessing.
 
-## See Also
+## See also
 
-[Expressions in Makefile Preprocessing](../build/expressions-in-makefile-preprocessing.md)
+[Expressions in Makefile Preprocessing](../build/expressions-in-makefile-preprocessing.md)
diff --git a/docs/build/exit-codes-from-nmake.md b/docs/build/exit-codes-from-nmake.md
@@ -19,6 +19,6 @@ NMAKE returns the following exit codes:
 |4|System error — out of memory|
 |255|Target is not up-to-date (issued only when /Q is used)|
 
-## See Also
+## See also
 
-[Running NMAKE](../build/running-nmake.md)
+[Running NMAKE](../build/running-nmake.md)
diff --git a/docs/build/exporting-and-importing-using-afx-ext-class.md b/docs/build/exporting-and-importing-using-afx-ext-class.md
@@ -113,6 +113,6 @@ Because MFC always uses the `AFX_DATA` symbol on data items it defines within it
 
 - [Mutual imports](../build/mutual-imports.md)
 
-## See Also
+## See also
 
-[Exporting from a DLL](../build/exporting-from-a-dll.md)
+[Exporting from a DLL](../build/exporting-from-a-dll.md)
diff --git a/docs/build/exporting-c-functions-for-use-in-c-or-cpp-language-executables.md b/docs/build/exporting-c-functions-for-use-in-c-or-cpp-language-executables.md
@@ -53,6 +53,6 @@ extern "C" {
 
 - [Using extern to Specify Linkage](../cpp/using-extern-to-specify-linkage.md)
 
-## See Also
+## See also
 
-[Exporting from a DLL](../build/exporting-from-a-dll.md)
+[Exporting from a DLL](../build/exporting-from-a-dll.md)
diff --git a/docs/build/exporting-cpp-functions-for-use-in-c-language-executables.md b/docs/build/exporting-cpp-functions-for-use-in-c-language-executables.md
@@ -36,6 +36,6 @@ extern "C" __declspec( dllexport ) int MyFunc(long parm1);
 
 - [Using extern to Specify Linkage](../cpp/using-extern-to-specify-linkage.md)
 
-## See Also
+## See also
 
-[Exporting from a DLL](../build/exporting-from-a-dll.md)
+[Exporting from a DLL](../build/exporting-from-a-dll.md)
diff --git a/docs/build/exporting-from-a-dll-using-declspec-dllexport.md b/docs/build/exporting-from-a-dll-using-declspec-dllexport.md
@@ -68,6 +68,6 @@ As a reference, search through the Win32 Winbase.h header file. It contains exam
 
 - [Mutual imports](../build/mutual-imports.md)
 
-## See Also
+## See also
 
-[Exporting from a DLL](../build/exporting-from-a-dll.md)
+[Exporting from a DLL](../build/exporting-from-a-dll.md)
diff --git a/docs/build/exporting-from-a-dll-using-def-files.md b/docs/build/exporting-from-a-dll-using-def-files.md
@@ -73,6 +73,6 @@ Note that MFC itself uses DEF files to export functions and classes from the MFC
 
 - [Mutual imports](../build/mutual-imports.md)
 
-## See Also
+## See also
 
-[Exporting from a DLL](../build/exporting-from-a-dll.md)
+[Exporting from a DLL](../build/exporting-from-a-dll.md)
diff --git a/docs/build/exporting-from-a-dll.md b/docs/build/exporting-from-a-dll.md
@@ -44,6 +44,6 @@ When exporting functions with either method, make sure to use the [__stdcall](..
 
 - [Mutual imports](../build/mutual-imports.md)
 
-## See Also
+## See also
 
-[Importing and Exporting](../build/importing-and-exporting.md)
+[Importing and Exporting](../build/importing-and-exporting.md)
diff --git a/docs/build/exporting-functions-from-a-dll-by-ordinal-rather-than-by-name.md b/docs/build/exporting-functions-from-a-dll-by-ordinal-rather-than-by-name.md
@@ -18,6 +18,6 @@ The simplest way to export functions from your DLL is to export them by name. Th
 
 - [Use __declspec(dllexport)](../build/exporting-from-a-dll-using-declspec-dllexport.md)
 
-## See Also
+## See also
 
-[Exporting from a DLL](../build/exporting-from-a-dll.md)
+[Exporting from a DLL](../build/exporting-from-a-dll.md)
diff --git a/docs/build/expressions-in-makefile-preprocessing.md b/docs/build/expressions-in-makefile-preprocessing.md
@@ -16,6 +16,6 @@ Expressions can use operators that act on constant values, exit codes from comma
 
 [Executing a program in preprocessing](../build/executing-a-program-in-preprocessing.md)
 
-## See Also
+## See also
 
-[Makefile Preprocessing](../build/makefile-preprocessing.md)
+[Makefile Preprocessing](../build/makefile-preprocessing.md)
diff --git a/docs/build/extension-dlls-overview.md b/docs/build/extension-dlls-overview.md
@@ -32,6 +32,6 @@ Note that the term AFXDLL is no longer used in the Visual C++ documentation. An
 
 - [Creating an MFC DLL](../mfc/reference/mfc-dll-wizard.md)
 
-## See Also
+## See also
 
-[Kinds of DLLs](../build/kinds-of-dlls.md)
+[Kinds of DLLs](../build/kinds-of-dlls.md)