fix: MD006/ul-start-left

Consider starting bulleted lists at the beginning of the line

Author: nschonni

.markdownlint.json

@@ -3,7 +3,6 @@
     "MD001": false,
     "MD002": false,
     "MD004": false,
-    "MD006": false,
     "MD007": false,
     "MD009": false,
     "MD011": false,

docs/code-quality/cpp-core-guidelines-warnings.md

@@ -78,17 +78,17 @@ The C++ Core Guidelines are there to help you write better and safer code. Howev
 
 As new rules are added to the C++ Core Guidelines Checker, the number of warnings that are produced for pre-existing code may increase. You can use predefined rule sets to filter which kinds of rules to enable. As of Visual Studio 2017 version 15.3, the supported rule sets are:
 
-  - **Owner Pointer Rules** enforce [resource-management checks related to owner\<T> from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#r-resource-management).
+- **Owner Pointer Rules** enforce [resource-management checks related to owner\<T> from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#r-resource-management).
 
-  - **Const Rules** enforce [const-related checks from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con-constants-and-immutability).
+- **Const Rules** enforce [const-related checks from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con-constants-and-immutability).
 
-  - **Raw Pointer Rules** enforce [resource-management checks related to raw pointers from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#r-resource-management).
+- **Raw Pointer Rules** enforce [resource-management checks related to raw pointers from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#r-resource-management).
 
-  - **Unique Pointer Rules** enforce [resource-management checks related to types with unique pointer semantics from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#r-resource-management).
+- **Unique Pointer Rules** enforce [resource-management checks related to types with unique pointer semantics from the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#r-resource-management).
 
-  - **Bounds Rules** enforce the [Bounds profile of the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#probounds-bounds-safety-profile).
+- **Bounds Rules** enforce the [Bounds profile of the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#probounds-bounds-safety-profile).
 
-  - **Type Rules** enforce the [Type profile of the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#prosafety-type-safety-profile).
+- **Type Rules** enforce the [Type profile of the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#prosafety-type-safety-profile).
 
 You can choose to limit warnings to just one or a few of the groups. The **Native Minimum** and **Native Recommended** rule sets include C++ Core Check rules in addition to other PREfast checks. To see the available rule sets, open the Project Properties dialog, select **Code Analysis\General**, open the dropdown in the **Rule Sets** combo-box, and pick **Choose multiple rule sets**. For more information about using Rule Sets in Visual Studio, see [Using Rule Sets to Group Code Analysis Rules](using-rule-sets-to-group-code-analysis-rules.md).
 

docs/debugger/autos-and-locals-windows.md

@@ -79,9 +79,9 @@ Set a breakpoint and start debugging. When the breakpoint is hit, execution paus
 
 ## <a name="bkmk_whatvariables"></a> Variables in the Autos window (C#, C++, Visual Basic, Python)
 
- Different code languages display different variables in the **Autos** window.
+Different code languages display different variables in the **Autos** window.
 
- - In C# and Visual Basic, the **Autos** window displays any variable used on the current or preceding line. For example, in C# or Visual Basic code, declare the following four variables:
+- In C# and Visual Basic, the **Autos** window displays any variable used on the current or preceding line. For example, in C# or Visual Basic code, declare the following four variables:
 
    ```csharp
        public static void Main()
@@ -100,7 +100,7 @@ Set a breakpoint and start debugging. When the breakpoint is hit, execution paus
 
    The value of `c` is 0, because the line `c = 3` has not yet been executed.
 
- - In C++, the **Autos** window displays the variables used in at least three lines before the current line where execution is paused. For example, in C++ code, declare six variables:
+- In C++, the **Autos** window displays the variables used in at least three lines before the current line where execution is paused. For example, in C++ code, declare six variables:
 
    ```C++
        void main() {

docs/debugger/debug-using-the-just-in-time-debugger.md

@@ -90,11 +90,11 @@ To enable Just-In-Time debugging instead of standard Windows Form error handling
    For more information, see <xref:System.Diagnostics.DebuggableAttribute>.
 
 ## <a name="BKMK_Using_JIT"></a>Use Just-In-Time debugging
- This example walks you through Just-In-Time debugging when an app throws an error.
+This example walks you through Just-In-Time debugging when an app throws an error.
 
- - You must have Visual Studio installed to follow these steps. If you don't have Visual Studio, you can download the free [Visual Studio Community Edition](https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=15).
+- You must have Visual Studio installed to follow these steps. If you don't have Visual Studio, you can download the free [Visual Studio Community Edition](https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=15).
 
- - Make sure Just-In-Time debugging is [enabled](#BKMK_Enabling) in **Tools** > **Options** > **Debugging** > **Just-In-Time**.
+- Make sure Just-In-Time debugging is [enabled](#BKMK_Enabling) in **Tools** > **Options** > **Debugging** > **Just-In-Time**.
 
 For this example, you'll make a C# console app in Visual Studio that throws a [NullReferenceException](/dotnet/api/system.nullreferenceexception).
 

docs/debugger/historical-debugging.md

@@ -25,8 +25,8 @@ Historical debugging is a mode of debugging that depends on the information coll
 
 ## How do I start using historical debugging?
 
- IntelliTrace is on by default. All you have to do is decide which events and function calls are of interest to you, and whether you want to view snapshots of your full application state. For more information about defining what you want to look for, see [IntelliTrace Features](../debugger/intellitrace-features.md). Feature support varies by language and app type.
+IntelliTrace is on by default. All you have to do is decide which events and function calls are of interest to you, and whether you want to view snapshots of your full application state. For more information about defining what you want to look for, see [IntelliTrace Features](../debugger/intellitrace-features.md). Feature support varies by language and app type.
 
- - To view snapshots with historical debugging, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)
- - To learn how to inspect variables and navigate code, see [Inspect your app with historical debugging](../debugger/historical-debugging-inspect-app.md)
- - To learn more about debugging with IntelliTrace events, see [Walkthrough: Using IntelliTrace](../debugger/walkthrough-using-intellitrace.md).
+- To view snapshots with historical debugging, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)
+- To learn how to inspect variables and navigate code, see [Inspect your app with historical debugging](../debugger/historical-debugging-inspect-app.md)
+- To learn more about debugging with IntelliTrace events, see [Walkthrough: Using IntelliTrace](../debugger/walkthrough-using-intellitrace.md).

docs/extensibility/ux-guidelines/ux-essentials-for-visual-studio.md

@@ -47,11 +47,12 @@ ms.workload:
 ## Screen resolution
 
 ### Minimum resolution
- - The minimum resolution for Visual Studio Dev14 is **1280x720**. This means that it is *possible* to use Visual Studio at this resolution, although it might not be an optimal user experience. There is no guarantee that all aspects will be usable at resolutions lower than 1280x720.
 
- - The target resolution for Visual Studio is **1366x768**. This is the lowest resolution at which we promise a *good* user experience.
+- The minimum resolution for Visual Studio Dev14 is **1280x720**. This means that it is *possible* to use Visual Studio at this resolution, although it might not be an optimal user experience. There is no guarantee that all aspects will be usable at resolutions lower than 1280x720.
 
- - Initial dialog height should be **smaller than 700 pixels**, so it fits within the minimum resolution of the IDE frame at 96 dpi.
+- The target resolution for Visual Studio is **1366x768**. This is the lowest resolution at which we promise a *good* user experience.
+
+- Initial dialog height should be **smaller than 700 pixels**, so it fits within the minimum resolution of the IDE frame at 96 dpi.
 
 ### High-density displays
  UI in Visual Studio must work well in all DPI scaling factors that Windows supports out of the box: 150%, 200%, and 250%.

docs/ide/dotfuscator/install.md

@@ -43,7 +43,7 @@ You can install Dotfuscator Community from the Visual Studio IDE:
 1. In the **Search Box** (Ctrl+Q), type `dotfuscator`. <br/> <br/> ![Search Box](media/install_in_vs19_12.png) <br/> <br/>
 
 2. In the search results shown, under the *Components* heading, select **Install PreEmptive Protection - Dotfuscator**.
-  * If you instead see, under the *Menus* heading, **PreEmptive Protection - Dotfuscator Community**, then Dotfuscator Community is already installed. Select that option to [get started][get-started].
+   * If you instead see, under the *Menus* heading, **PreEmptive Protection - Dotfuscator Community**, then Dotfuscator Community is already installed. Select that option to [get started][get-started].
 
 3. A Visual Studio Installer window will launch, pre-configured to install Dotfuscator Community.
    > [!NOTE]

docs/ide/how-to-view-save-and-configure-build-log-files.md

@@ -14,10 +14,10 @@ ms.workload:
 
 After you build a project in the Visual Studio IDE, you can view information about that build in the **Output** window. By using this information, you can, for example, troubleshoot a build failure. 
 
-  - For C++ projects, you can also view the same information in a *.txt* file that's created and saved automatically. 
+- For C++ projects, you can also view the same information in a *.txt* file that's created and saved automatically. 
+
+- For managed code projects, you can click in the build output window and press **Ctrl**+**S**. Visual Studio prompts you for a location to save the information from the **Output** window into a *.txt* file. 
 
-  - For managed code projects, you can click in the build output window and press **Ctrl**+**S**. Visual Studio prompts you for a location to save the information from the **Output** window into a *.txt* file. 
-  
 You can also use the IDE to specify what kinds of information you want to view about each build.
 
 If you build any kind of project by using MSBuild, you can create a *.txt* file to save information about the build. For more information, see [Obtain build logs](../msbuild/obtaining-build-logs-with-msbuild.md).

docs/ide/reference/generate-constructor.md

@@ -24,11 +24,11 @@ This code generation applies to:
 
 **How:** There are several ways to generate a constructor:
 
-   - [Generate constructor and pick members](#pick)
-   - [Generate constructor from selected fields](#selection)
-   - [Generate constructor from new usage](#usage)
-   - [Add parameter to existing constructor](#addparameter)
-   - [Create and initialize field/property from a constructor parameter](#create)
+- [Generate constructor and pick members](#pick)
+- [Generate constructor from selected fields](#selection)
+- [Generate constructor from new usage](#usage)
+- [Add parameter to existing constructor](#addparameter)
+- [Create and initialize field/property from a constructor parameter](#create)
 
 ## <a id = "pick"></a> Generate constructor and pick members (C# only)
 

docs/install/using-visual-studio-vm.md

@@ -71,13 +71,13 @@ If the images don't include a Visual Studio feature that you require, provide fe
 
 Azure offers a full range of virtual machine sizes. Because Visual Studio is a powerful, multi-threaded application, you want a VM size that includes at least two processors and 7 GB of memory. We recommend the following VM sizes for the Visual Studio images:
 
-   * Standard_D2_v3
-   * Standard_D2s_v3
-   * Standard_D4_v3
-   * Standard_D4s_v3
-   * Standard_D2_v2
-   * Standard_D2S_v2
-   * Standard_D3_v2
+* Standard_D2_v3
+* Standard_D2s_v3
+* Standard_D4_v3
+* Standard_D4s_v3
+* Standard_D2_v2
+* Standard_D2S_v2
+* Standard_D3_v2
 
 For more information on the latest machine sizes, see [Sizes for Windows virtual machines in Azure](/azure/virtual-machines/windows/sizes).
 

docs/javascript/javascript-in-vs-2017.md

@@ -46,14 +46,14 @@ To compile JavaScript files, a `tsconfig.json` file must be added, and some of t
 
 The required settings for the tsconfig file are as follows:
 
- - `allowJs`: This value must be set to `true` for JavaScript files to be recognized. The default value is `false`, because TypeScript compiles to JavaScript, and the compiler should not include files it just compiled.
- - `outDir`: This value should be set to a location not included in the project, in order that the emitted JavaScript files are not detected and then included in the project (see `exclude`).
- - `module`: If using modules, this setting tells the compiler which module format the emitted code should use (for example `commonjs` for Node, or bundlers such as Browserify).
- - `exclude`: This setting states which folders not to include in the project.
- The output location, as well as non-project folders such as `node_modules` or `temp`, should be added to this setting.
- - `enableAutoDiscovery`: This setting enables the automatic detection and download of definition files as outlined previously.
- - `compileOnSave`: This setting tells the compiler if it should recompile any time a source file is saved in Visual Studio.
- - `typeAcquisition`: This set of settings control the behavior of automatic type acquisition (further explain in [this section](/visualstudio/ide/javascript-intellisense#Auto))
+- `allowJs`: This value must be set to `true` for JavaScript files to be recognized. The default value is `false`, because TypeScript compiles to JavaScript, and the compiler should not include files it just compiled.
+- `outDir`: This value should be set to a location not included in the project, in order that the emitted JavaScript files are not detected and then included in the project (see `exclude`).
+- `module`: If using modules, this setting tells the compiler which module format the emitted code should use (for example `commonjs` for Node, or bundlers such as Browserify).
+- `exclude`: This setting states which folders not to include in the project.
+The output location, as well as non-project folders such as `node_modules` or `temp`, should be added to this setting.
+- `enableAutoDiscovery`: This setting enables the automatic detection and download of definition files as outlined previously.
+- `compileOnSave`: This setting tells the compiler if it should recompile any time a source file is saved in Visual Studio.
+- `typeAcquisition`: This set of settings control the behavior of automatic type acquisition (further explain in [this section](/visualstudio/ide/javascript-intellisense#Auto))
 
 In order to convert JavaScript files to CommonJS modules and place them in an `./out` folder, you could use the following `tsconfig.json` file:
 

docs/profiling/shutdown.md

@@ -23,8 +23,8 @@ VSPerfCmd.exe /Shutdown[:Timeout]
 ```
 
 #### Parameters
- `Timeout`
- - (Optional) If specified, the option returns after the specified number of seconds without turning off the profiler or closing the profiling data file.
+`Timeout`
+- (Optional) If specified, the option returns after the specified number of seconds without turning off the profiler or closing the profiling data file.
 
 ## See also
 - [VSPerfCmd](../profiling/vsperfcmd.md)