Merge pull request MicrosoftDocs#2005 from nschonni/fix--MD005-list-indent

fix: MD005/list-indent

Author: Colin Robertson

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

@@ -78,7 +78,7 @@ IntelliSense fails in makefile projects when certain project settings or compile
 
    - Set the **Include Search Path** property to specify the list of directories that the compiler will search to resolve file references that are passed to preprocessor directives in your makefile project. See [/I (Additional Include Directories)](i-additional-include-directories.md), for more information.
 
-    - For projects that are built using CL.EXE from a Command Window, set the **INCLUDE** environment variable to specify directories that the compiler will search to resolve file references that are passed to preprocessor directives in your makefile project.
+   - For projects that are built using CL.EXE from a Command Window, set the **INCLUDE** environment variable to specify directories that the compiler will search to resolve file references that are passed to preprocessor directives in your makefile project.
 
    - Set the **Forced Includes** property to specify which header files to process when building your makefile project. See [/FI (Name Forced Include File)](fi-name-forced-include-file.md), for more information.
 

docs/windows/version-information-editor.md

@@ -27,9 +27,9 @@ Select the item once to choose it, then again to begin editing it. Make changes
 
 When editing the `FILEFLAGS` key in the **Version Information Editor**, notice you can't set the **Debug**, **Private Build**, or **Special Build** properties in the **Properties** window for .rc files:
 
-   - The **Version Information Editor** sets the **Debug** property with a `#ifdef` in the resource script, based on the `_DEBUG` build flag.
+- The **Version Information Editor** sets the **Debug** property with a `#ifdef` in the resource script, based on the `_DEBUG` build flag.
 
-  - If the `Private Build` key has a **Value** set in the **Version Information** table, the corresponding **Private Build** property in the **Properties** window for the `FILEFLAGS` key will be **True**. If **Value** is empty, the property will be **False**. Likewise, the **Special Build** key in the **Version Information** table is tied to the **Special Build** property for the `FILEFLAGS` key.
+- If the `Private Build` key has a **Value** set in the **Version Information** table, the corresponding **Private Build** property in the **Properties** window for the `FILEFLAGS` key will be **True**. If **Value** is empty, the property will be **False**. Likewise, the **Special Build** key in the **Version Information** table is tied to the **Special Build** property for the `FILEFLAGS` key.
 
 You can sort the information sequence of the string block by selecting either the **Key** or the **Value** column headings. These headings automatically rearrange the information into the selected sequence.