@@ -31,9 +31,9 @@ The [/DELAY](../../build/reference/delay-delay-load-import-settings.md) option s
 
 1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../../ide/working-with-project-properties.md).
 
-2. In the **Linker** folder, select the **Input** property page.
+1. In the **Linker** folder, select the **Input** property page.
 
-3. Modify the **Delay Loaded DLLs** property.
+1. Modify the **Delay Loaded DLLs** property.
 
 ### To set this linker option programmatically
 
@@ -42,4 +42,4 @@ The [/DELAY](../../build/reference/delay-delay-load-import-settings.md) option s
 ## See Also
 
 [Setting Linker Options](../../build/reference/setting-linker-options.md)<br/>
-[Linker Options](../../build/reference/linker-options.md)
+[Linker Options](../../build/reference/linker-options.md)
@@ -42,11 +42,11 @@ The **/diagnostics** option is available starting in Visual Studio 2017.
 
 1. Open your project's **Property Pages** dialog box.
 
-2. Under **Configuration Properties**, expand the **C/C++** folder and choose the **General** property page.
+1. Under **Configuration Properties**, expand the **C/C++** folder and choose the **General** property page.
 
-3. Use the dropdown control in the **Diagnostics Format** field to select a diagnostics display option. Choose **OK** or **Apply** to save your changes.
+1. Use the dropdown control in the **Diagnostics Format** field to select a diagnostics display option. Choose **OK** or **Apply** to save your changes.
 
 ## See Also
 
 [Compiler Options](../../build/reference/compiler-options.md)<br/>
-[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
+[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
@@ -56,9 +56,9 @@ BOOL CALLBACK PlainFuncName( Things * lpParams)
 
 1. Open the project's **Property Pages** dialog box. For details, see [Setting Visual C++ Project Properties](../../ide/working-with-project-properties.md).
 
-2. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
+1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
 
-3. Enter the option into the **Additional Options** box.
+1. Enter the option into the **Additional Options** box.
 
 ### To set this linker option programmatically
 
 
@@ -71,11 +71,11 @@ There are four ways to export a definition, listed in recommended order:
 
 1. The [__declspec(dllexport)](../../cpp/dllexport-dllimport.md) keyword in the source code
 
-2. An `EXPORTS` statement in a .DEF file
+1. An `EXPORTS` statement in a .DEF file
 
-3. An [/EXPORT](../../build/reference/export-exports-a-function.md) specification in a LINK command
+1. An [/EXPORT](../../build/reference/export-exports-a-function.md) specification in a LINK command
 
-4. A [comment](../../preprocessor/comment-c-cpp.md) directive in the source code, of the form `#pragma comment(linker, "/export: definition ")`. The following example shows a #pragma comment directive before a function declaration, where `PlainFuncName` is the undecorated name, and `_PlainFuncName@4` is the decorated name of the function:
+1. A [comment](../../preprocessor/comment-c-cpp.md) directive in the source code, of the form `#pragma comment(linker, "/export: definition ")`. The following example shows a #pragma comment directive before a function declaration, where `PlainFuncName` is the undecorated name, and `_PlainFuncName@4` is the decorated name of the function:
 
     ```cpp
     #pragma comment(linker, "/export:PlainFuncName=_PlainFuncName@4")
 
@@ -67,9 +67,9 @@ A listing file named *filename.extension* is placed in the specified *directory*
 
 1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../../ide/working-with-project-properties.md).
 
-2. Select the **Configuration Properties** > **C/C++** > **Output Files** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Output Files** property page.
 
-3. Modify the **Assembler Output** property to set the **/FAc** and **/FAs** options for assembler, machine, and source code. Modify the **Use Unicode For Assembler Listing** property to set the **/FAu** option for ANSI or UTF-8 output. Modify the **ASM List Location** to set the **/Fa** option for listing file name and location.
+1. Modify the **Assembler Output** property to set the **/FAc** and **/FAs** options for assembler, machine, and source code. Modify the **Use Unicode For Assembler Listing** property to set the **/FAu** option for ANSI or UTF-8 output. Modify the **ASM List Location** to set the **/Fa** option for listing file name and location.
 
 Note that setting both **Assembler Output** and **Use Unicode For Assembler Listing** properties can cause [Command-Line Warning D9025](../../error-messages/tool-errors/command-line-warning-d9025.md). To combine these options in the IDE, use the **Additional Options** field in the **Command Line** property page instead.
 
@@ -90,4 +90,4 @@ CL /FAcs HELLO.CPP
 [Output-File (/F) Options](../../build/reference/output-file-f-options.md)<br/>
 [Compiler Options](../../build/reference/compiler-options.md)<br/>
 [Setting Compiler Options](../../build/reference/setting-compiler-options.md)<br/>
-[Specifying the Pathname](../../build/reference/specifying-the-pathname.md)
+[Specifying the Pathname](../../build/reference/specifying-the-pathname.md)
@@ -71,9 +71,9 @@ The **/H** option is deprecated since Visual Studio 2005; the maximum length lim
 
 1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../../ide/working-with-project-properties.md).
 
-2. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
-3. Enter the compiler option in the **Additional Options** box.
+1. Enter the compiler option in the **Additional Options** box.
 
 ### To set this compiler option programmatically
 
@@ -82,4 +82,4 @@ The **/H** option is deprecated since Visual Studio 2005; the maximum length lim
 ## See Also
 
 [Compiler Options](../../build/reference/compiler-options.md)<br/>
-[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
+[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
@@ -35,9 +35,9 @@ The file should contain one MIDL command-line option per line.
 
 1. Open the project's **Property Pages** dialog box. For details, see [Setting Visual C++ Project Properties](../../ide/working-with-project-properties.md).
 
-2. Select the **Configuration Properties** > **Linker** > **Embedded IDL** property page.
+1. Select the **Configuration Properties** > **Linker** > **Embedded IDL** property page.
 
-3. Modify the **MIDL Commands** property.
+1. Modify the **MIDL Commands** property.
 
 ### To set this linker option programmatically
 
@@ -50,4 +50,4 @@ The file should contain one MIDL command-line option per line.
 [/IDLOUT (Name MIDL Output Files)](../../build/reference/idlout-name-midl-output-files.md)<br/>
 [/IGNOREIDL (Don't Process Attributes into MIDL)](../../build/reference/ignoreidl-don-t-process-attributes-into-midl.md)<br/>
 [/TLBOUT (Name .TLB File)](../../build/reference/tlbout-name-dot-tlb-file.md)<br/>
-[Building an Attributed Program](../../windows/building-an-attributed-program.md)
+[Building an Attributed Program](../../windows/building-an-attributed-program.md)
@@ -103,17 +103,17 @@ This unwind code will always appear in a dummy prolog, which is never actually e
 
 1. Pop RIP return address from top of stack into *Temp*
 
-2. Push SS
+1. Push SS
 
-3. Push old RSP
+1. Push old RSP
 
-4. Push EFLAGS
+1. Push EFLAGS
 
-5. Push CS
+1. Push CS
 
-6. Push *Temp*
+1. Push *Temp*
 
-7. Push Error Code (if op info equals 1)
+1. Push Error Code (if op info equals 1)
 
 The simulated `UWOP_PUSH_MACHFRAME` operation decrements RSP by 40 (op info equals 0) or 48 (op info equals 1).
 
@@ -135,4 +135,4 @@ The meaning of these 4 bits depends upon the operation code. To encode a general
 
 ## See Also
 
-[Unwind Data for Exception Handling, Debugger Support](../build/unwind-data-for-exception-handling-debugger-support.md)
+[Unwind Data for Exception Handling, Debugger Support](../build/unwind-data-for-exception-handling-debugger-support.md)
@@ -37,7 +37,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
 
    If you are using a different version of Visual Studio or are running a different version of Windows, look in your Start menu or Start page for a Visual Studio tools folder that contains a developer command prompt shortcut. You can also use the Windows search function to search for "developer command prompt" and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.
 
-2. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like this:
+1. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like this:
 
    ```Output
    C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise>cl
@@ -63,9 +63,9 @@ Before you can build a C or C++ program on the command line, you must verify tha
 
 1. In the developer command prompt window, enter **cd c:\\** to change the current working directory to the root of your C: drive. Next, enter **md c:\simple** to create a directory, and then enter **cd c:\simple** to change to that directory. This is the directory that will contain your source file and the compiled program.
 
-2. Enter **notepad simple.c** at the developer command prompt. In the Notepad alert dialog that pops up, choose **Yes** to create a new simple.c file in your working directory.
+1. Enter **notepad simple.c** at the developer command prompt. In the Notepad alert dialog that pops up, choose **Yes** to create a new simple.c file in your working directory.
 
-3. In Notepad, enter the following lines of code:
+1. In Notepad, enter the following lines of code:
 
     ```C
     #include <stdio.h>
@@ -77,9 +77,9 @@ Before you can build a C or C++ program on the command line, you must verify tha
     }
     ```
 
-4. On the Notepad menu bar, choose **File**, **Save** to save simple.c in your working directory.
+1. On the Notepad menu bar, choose **File**, **Save** to save simple.c in your working directory.
 
-5. Switch back to the developer command prompt window. Enter **dir** at the command prompt to list the contents of the c:\simple directory. You should see the source file simple.c in the directory listing, which looks something like this:
+1. Switch back to the developer command prompt window. Enter **dir** at the command prompt to list the contents of the c:\simple directory. You should see the source file simple.c in the directory listing, which looks something like this:
 
     ```Output
     C:\simple>dir
@@ -98,7 +98,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
 
    The dates and other details will differ on your computer. If you don't see your source code file, simple.c, make sure you've changed to the c:\simple directory you created, and in Notepad, make sure that you saved your source file in this directory. Also make sure that you saved the source code with a .c file name extension, not a .txt extension.
 
-6. To compile your program, enter **cl simple.c** at the developer command prompt.
+1. To compile your program, enter **cl simple.c** at the developer command prompt.
 
    You can see the executable program name, simple.exe, in the lines of output information that the compiler displays:
 
@@ -121,7 +121,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
    > [!NOTE]
    > If you get a different compiler or linker error or warning, review your source code to correct any errors, then save it and run the compiler again. For information about specific errors, use the search box at the top of this page to look for the error number.
 
-7. To run your program, enter **simple** at the command prompt.
+1. To run your program, enter **simple** at the command prompt.
 
    The program displays this text and then exits:
 
 
@@ -40,7 +40,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
 
    If you are using a different version of Visual Studio or are running a different version of Windows, look in your Start menu or Start page for a Visual Studio tools folder that contains a developer command prompt shortcut. You can also use the Windows search function to search for "developer command prompt" and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.
 
-2. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like this:
+1. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like this:
 
    ```Output
    C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise>cl
@@ -64,11 +64,11 @@ Before you can build a C or C++ program on the command line, you must verify tha
 
 1. In the developer command prompt window, enter **md c:\hello** to create a directory, and then enter **cd c:\hello** to change to that directory. This is the directory that your source file and the compiled program are created in.
 
-2. Enter **notepad hello.cpp** in the command prompt window.
+1. Enter **notepad hello.cpp** in the command prompt window.
 
    Choose **Yes** when Notepad prompts you to create a file. This opens a blank Notepad window, ready for you to enter your code in a file named hello.cpp.
 
-3. In Notepad, enter the following lines of code:
+1. In Notepad, enter the following lines of code:
 
    ```cpp
    #include <iostream>
@@ -81,11 +81,11 @@ Before you can build a C or C++ program on the command line, you must verify tha
 
    This is a very simple program that will write one line of text on the screen and then exit. To minimize errors, copy this code and paste it into Notepad.
 
-4. Save your work! In Notepad, on the **File** menu, choose **Save**.
+1. Save your work! In Notepad, on the **File** menu, choose **Save**.
 
    Congratulations, you have created a Visual C++ source file, hello.cpp, that is ready to compile.
 
-5. Switch back to the developer command prompt window. Enter **dir** at the command prompt to list the contents of the c:\hello directory. You should see the source file hello.cpp in the directory listing, which looks something like this:
+1. Switch back to the developer command prompt window. Enter **dir** at the command prompt to list the contents of the c:\hello directory. You should see the source file hello.cpp in the directory listing, which looks something like this:
 
    ```Output
    c:\hello>dir
@@ -104,7 +104,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
 
    The dates and other details will differ on your computer. If you don't see your source code file, hello.cpp, make sure you've changed to the c:\hello directory you created, and in Notepad, make sure that you saved your source file in this directory. Also make sure that you saved the source code with a .cpp file name extension, not a .txt extension.
 
-6. At the developer command prompt, enter `cl /EHsc hello.cpp` to compile your program.
+1. At the developer command prompt, enter `cl /EHsc hello.cpp` to compile your program.
 
    The cl.exe compiler generates an .obj file that contains the compiled code, and then runs the linker to create an executable program named hello.exe. This name appears in the lines of output information that the compiler displays. The output of the compiler should look something like this:
 
@@ -127,7 +127,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
    > [!NOTE]
    > If you get a different compiler or linker error or warning, review your source code to correct any errors, then save it and run the compiler again. For information about specific errors, use the search box on this MSDN page to look for the error number.
 
-7. To run the hello.exe program, at the command prompt, enter `hello`.
+1. To run the hello.exe program, at the command prompt, enter `hello`.
 
    The program displays this text and exits: