Merge pull request #3564 from MicrosoftDocs/master

5/6/2021 AM Publish

Author: Taojunshen

docs/build/reference/allowbind-prevent-dll-binding.md

@@ -22,7 +22,7 @@ You can edit an existing DLL for /ALLOWBIND functionality with the [/ALLOWBIND](
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Expand **Configuration Properties**, **Linker**, and select **Command Line**.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
 1. Enter `/ALLOWBIND:NO` into **Additional Options**.
 

docs/build/reference/appcontainer-windows-store-app.md

@@ -26,11 +26,7 @@ The /APPCONTAINER option was introduced in Windows 8.
 
 1. Open the project **Property Pages** dialog box. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Expand the **Configuration Properties** node.
-
-1. Expand the **Linker** node.
-
-1. Select the **Command Line** property page.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
 1. In **Additional Options**, enter `/APPCONTAINER` or `/APPCONTAINER:NO`.
 

docs/build/reference/arch-arm.md

@@ -32,9 +32,7 @@ When you use [/clr](clr-common-language-runtime-compilation.md) to compile, **/a
 
 1. Open the **Property Pages** dialog box for the project. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **C/C++** folder.
-
-1. Select the **Command Line** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
 1. In the **Additional options** box, add `/arch:ARMv7VE` or `/arch:VFPv4`.
 

docs/build/reference/arch-x64.md

@@ -49,9 +49,7 @@ The `__AVX__` preprocessor symbol is defined when the **/arch:AVX**, **/arch:AVX
 
 1. Open the **Property Pages** dialog box for the project. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **Configuration Properties**, **C/C++** folder.
-
-1. Select the **Code Generation** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Code Generation** property page.
 
 1. In the **Enable Enhanced Instruction Set** drop-down box, choose **Advanced Vector Extensions (/arch:AVX)**, **Advanced Vector Extensions 2 (/arch:AVX2)** or **Advanced Vector Extensions 512 (/arch:AVX512)**.
 

docs/build/reference/arch-x86.md

@@ -90,9 +90,7 @@ The `_M_IX86_FP`, `__AVX__`, `__AVX2__`, `__AVX512F__`, `__AVX512CD__`, `__AVX51
 
 1. Open the **Property Pages** dialog box for the project. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **Configuration Properties**, **C/C++** folder.
-
-1. Select the **Code Generation** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Code Generation** property page.
 
 1. Modify the **Enable Enhanced Instruction Set** property.
 

docs/build/reference/assemblydebug-add-debuggableattribute.md

@@ -56,9 +56,7 @@ Other linker options that affect assembly generation are:
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **Linker** folder.
-
-1. Click the **Debug** property page.
+1. Select the **Configuration Properties** > **Linker** > **Debug** property page.
 
 1. Modify the **Debuggable Assembly** property.
 

docs/build/reference/assemblylinkresource-link-to-dotnet-framework-resource.md

@@ -49,9 +49,7 @@ Other linker options that affect assembly generation are:
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **Linker** folder.
-
-1. Click the **Command Line** property page.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
 1. Type the option into the **Additional Options** box.
 

docs/build/reference/assemblymodule-add-a-msil-module-to-the-assembly.md

@@ -53,9 +53,7 @@ The MSVC linker accepts .netmodule files as input and the output file produced b
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **Linker** folder.
-
-1. Click the **Input** property page.
+1. Select the **Configuration Properties** > **Linker** > **Input** property page.
 
 1. Modify the **Add Module to Assembly** property.
 

docs/build/reference/assemblyresource-embed-a-managed-resource.md

@@ -50,9 +50,7 @@ Other linker options that affect assembly generation are:
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **Linker** folder.
-
-1. Click the **Input** property page.
+1. Select the **Configuration Properties** > **Linker** > **Input** property page.
 
 1. Modify the **Embed Managed Resource File** property.
 

docs/build/reference/await-enable-coroutine-support.md

@@ -24,7 +24,7 @@ The **/await** option is available beginning in Visual Studio 2015.
 
 1. Open your project's **Property Pages** dialog box.
 
-1. Under **Configuration Properties**, expand the **C/C++** folder and choose the **Command Line** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
 1. Enter the **/await** compiler option in the **Additional Options** box. Choose **OK** or **Apply** to save your changes.
 

docs/build/reference/c-preserve-comments-during-preprocessing.md

@@ -39,9 +39,7 @@ int i;   // a variable
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **C/C++** folder.
-
-1. Click the **Preprocessor** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Preprocessor** property page.
 
 1. Modify the **Keep Comments** property.
 

docs/build/reference/cgthreads-compiler-threads.md

@@ -30,9 +30,7 @@ Multiple levels of parallelism can be specified for a build. The msbuild.exe swi
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **Configuration Properties**, **Linker** folder.
-
-1. Select the **Command Line** property page.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
 1. Modify the **Additional Options** property to include **/CGTHREADS:**`number`, where `number` is a value from 1 to 8, and then choose **OK**.
 

docs/build/reference/clrimagetype-specify-type-of-clr-image.md

@@ -26,11 +26,7 @@ For information about how to determine the CLR image type of a file, see [/CLRHE
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Expand the **Configuration Properties** node.
-
-1. Expand the **Linker** node.
-
-1. Select the **Advanced** property page.
+1. Select the **Configuration Properties** > **Linker** > **Advanced** property page.
 
 1. Modify the **CLR Image Type** property.
 

docs/build/reference/clrsupportlasterror-preserve-last-error-code-for-pinvoke-calls.md

@@ -31,11 +31,9 @@ You can minimize the performance impact by linking with **/CLRSUPPORTLASTERROR:S
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **Linker** folder.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
-1. Click the **Command Line** property page.
-
-1. Type the option into the **Additional Options** box.
+1. Enter the option into the **Additional Options** box.
 
 ### To set this linker option programmatically
 

docs/build/reference/clrthreadattribute-set-clr-thread-attribute.md

@@ -43,11 +43,7 @@ It will be necessary for you to use single-threading, for example, if your CLR p
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Expand the **Configuration Properties** node.
-
-1. Expand the **Linker** node.
-
-1. Select the **Advanced** property page.
+1. Select the **Configuration Properties** > **Linker** > **Advanced** property page.
 
 1. Modify the **CLR Thread Attribute** property.
 

docs/build/reference/clrunmanagedcodecheck-add-suppressunmanagedcodesecurityattribute.md

@@ -33,11 +33,7 @@ See [Secure Coding Guidelines for Unmanaged Code](/dotnet/framework/security/sec
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Expand the **Configuration Properties** node.
-
-1. Expand the **Linker** node.
-
-1. Select the **Advanced** property page.
+1. Select the **Configuration Properties** > **Linker** > **Advanced** property page.
 
 1. Modify the **CLR Unmanaged Code Check** property.
 

docs/build/reference/constexpr-control-constexpr-evaluation.md

@@ -37,9 +37,9 @@ The **/constexpr** options are available beginning in Visual Studio 2015.
 
 1. Open your project's **Property Pages** dialog box.
 
-2. Under **Configuration Properties**, expand the **C/C++** folder and choose the **Command Line** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
-3. Enter any **/constexpr** compiler options in the **Additional Options** box. Choose **OK** or **Apply** to save your changes.
+1. Enter any **/constexpr** compiler options in the **Additional Options** box. Choose **OK** or **Apply** to save your changes.
 
 ### To set this compiler option programmatically
 

docs/build/reference/creating-a-makefile-project.md

@@ -71,9 +71,9 @@ IntelliSense fails in makefile projects when certain project settings or compile
 
 1. Open the **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Expand the **Configuration Properties** node.
+1. Select the **Configuration Properties** > **NMake** property page.
 
-1. Select the **NMake** property page, and then modify properties under **IntelliSense** as appropriate.
+1. Modify properties under **IntelliSense** as appropriate:
 
    - Set the **Preprocessor Definitions** property to define any preprocessor symbols in your makefile project. See [/D (Preprocessor Definitions)](d-preprocessor-definitions.md), for more information.
 
@@ -89,7 +89,7 @@ IntelliSense fails in makefile projects when certain project settings or compile
 
    - Set the **Additional Options** property to specify additional compiler switches to be used by IntelliSense when parsing C++ files.
 
-1. Click **OK** to close the property pages.
+1. Choose **OK** to close the property pages.
 
 1. Use the **Save All** command to save the modified project settings.
 

docs/build/reference/custom-build-step-property-page-general.md

@@ -40,9 +40,9 @@ For the Linux version of this page, see [Custom Build Step Properties (Linux C++
 
 ### To specify a custom build step
 
-1. On the menu bar, choose **Project** > **Properties**. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
+1. On the menu bar, choose **Project** > **Properties** to open the **Property Pages** dialog box. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. In the **Property Pages** dialog box, navigate to the **Configuration Properties** > **Custom Build Step** > **General** page.
+1. Select the **Configuration Properties** > **Custom Build Step** > **General** page.
 
 1. Modify the settings.
 

docs/build/reference/e-preprocess-to-stdout.md

@@ -54,11 +54,9 @@ cl -E test.cpp > test2.cpp
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **C/C++** folder.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
-1. Click the **Command Line** property page.
-
-1. Type the compiler option in the **Additional Options**box.
+1. Enter the compiler option in the **Additional Options** box.
 
 ### To set this compiler option programmatically
 

docs/build/reference/entry-entry-point-symbol.md

@@ -43,9 +43,7 @@ For information on how to define your own `DllMain` entry point, see [DLLs and V
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **Linker** folder.
-
-1. Click the **Advanced** property page.
+1. Select the **Configuration Properties** > **Linker** > **Advanced** property page.
 
 1. Modify the **Entry Point** property.
 

docs/build/reference/ep-preprocess-to-stdout-without-hash-line-directives.md

@@ -34,9 +34,7 @@ You cannot use precompiled headers with the **/EP** option.
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **C/C++** folder.
-
-1. Click the **Preprocessor** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Preprocessor** property page.
 
 1. Modify the **Generate Preprocessed File** property.
 

docs/build/reference/errorreport-report-internal-compiler-errors.md

@@ -25,7 +25,7 @@ The **/errorReport** arguments are overridden by the Windows Error Reporting ser
 
 1. Open the project **Property Pages** dialog box. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Open the **Configuration Properties** > **C/C++** > **Advanced** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Advanced** property page.
 
 1. Modify the **Error Reporting** property.
 

docs/build/reference/errorreport-report-internal-linker-errors.md

@@ -22,7 +22,7 @@ The **/ERRORREPORT** arguments are overridden by the Windows Error Reporting ser
 
 1. Open the project **Property Pages** dialog box. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Open the **Configuration Properties** > **Linker** > **Advanced** property page.
+1. Select the **Configuration Properties** > **Linker** > **Advanced** property page.
 
 1. Modify the **Error Reporting** property.
 

docs/build/reference/execution-charset-set-execution-character-set.md

@@ -36,7 +36,7 @@ If you want to set both the source character set and the execution character set
 
 1. Open the project **Property Pages** dialog box. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Expand the **Configuration Properties**, **C/C++**, **Command Line** folder.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
 1. In **Additional Options**, add the **/execution-charset** option, and specify your preferred encoding.
 

docs/build/reference/f-set-stack-size.md

@@ -37,7 +37,7 @@ You can also set the stack size by:
 
 1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
-1. Type the compiler option in the **Additional Options** box.
+1. Enter the compiler option in the **Additional Options** box.
 
 ### To set this compiler option programmatically
 

docs/build/reference/favor-optimize-for-architecture-specifics.md

@@ -37,9 +37,7 @@ For information about how to program for the x64 architecture, see [x64 Software
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **C/C++** folder.
-
-1. Select the **Command Line** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
 1. Enter the compiler option in the **Additional Options** box.
 

docs/build/reference/fd-program-database-file-name.md

@@ -30,9 +30,7 @@ This option also names the state (.idb) file used for minimal rebuild and increm
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **C/C++** folder.
-
-1. Click the **Output Files** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Output Files** property page.
 
 1. Modify the **Program Database File Name** property.
 

docs/build/reference/fe-name-exe-file.md

@@ -32,7 +32,7 @@ If you specify the [/c (Compile Without Linking)](c-compile-without-linking.md)
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Open the **Configuration Properties** > **Linker** > **General** property page.
+1. Select the **Configuration Properties** > **Linker** > **General** property page.
 
 1. Modify the **Output File** property. Choose **OK** to save your changes.
 

docs/build/reference/fi-name-forced-include-file.md

@@ -24,9 +24,7 @@ This option has the same effect as specifying the file with double quotation mar
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **C/C++** folder.
-
-1. Click the **Advanced** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Advanced** property page.
 
 1. Modify the **Forced Include File** property.
 

docs/build/reference/filealign.md

@@ -31,9 +31,9 @@ Use [DUMPBIN](dumpbin-reference.md) to see information about sections in your ou
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **Command Line** property page in the **Linker** folder.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
-1. Type the option name **/FILEALIGN:** and the size in the **Additional Options** box.
+1. Enter the option name **/FILEALIGN:** and the size in the **Additional Options** box.
 
 ### To set this linker option programmatically
 

docs/build/reference/fixed-fixed-base-address.md

@@ -26,11 +26,9 @@ Specify /FIXED:NO to generate a relocation section in the program.
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **Linker** folder.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
-1. Select the **Command Line** property page.
-
-1. Type the option name and setting in the **Additional Options** box.
+1. Enter the option name and setting in the **Additional Options** box.
 
 ### To set this linker option programmatically
 

docs/build/reference/fm-name-mapfile.md

@@ -18,23 +18,21 @@ Tells the linker to produce a mapfile containing a list of segments in the order
 
 ## Remarks
 
-By default, the mapfile is given the base name of the corresponding C or C++ source file with a .MAP extension.
+By default, the map file is given the base name of the corresponding C or C++ source file with a *`.MAP`* extension.
 
 Specifying **/Fm** has the same effect as if you had specified the [/MAP (Generate Mapfile)](map-generate-mapfile.md) linker option.
 
 If you specify [/c (Compile Without Linking)](c-compile-without-linking.md) to suppress linking, **/Fm** has no effect.
 
-Global symbols in a mapfile usually have one or more leading underscores because the compiler adds a leading underscore to variable names. Many global symbols that appear in the mapfile are used internally by the compiler and the standard libraries.
+Global symbols in a map file usually have one or more leading underscores. It's because the compiler adds a leading underscore to variable names. Many global symbols that appear in the map file are used internally by the compiler and the standard libraries.
 
 ### To set this compiler option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **C/C++** folder.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
-1. Click the **Command Line** property page.
-
-1. Type the compiler option in the **Additional Options** box.
+1. Enter the compiler option in the **Additional Options** box.
 
 ### To set this compiler option programmatically