fix: MD003/heading-style/header-style

.markdownlint.json

@@ -2,15 +2,13 @@
     "default": true,
     "MD001": false,
     "MD002": false,
-    "MD003": false,
     "MD004": false,
     "MD005": false,
     "MD006": false,
     "MD007": false,
     "MD009": false,
     "MD011": false,
     "MD013": false,
-    "MD020": false,
     "MD022": false,
     "MD024": false,
     "MD025": false,

docs/ide/managing-application-settings-dotnet.md

@@ -78,9 +78,9 @@ If any user-scoped settings are changed during run time, for example in testing
 
 We strongly recommend that you use the `My.Settings` object and the default *.settings* file to access settings. This is because you can use the **Settings Designer** to assign properties to settings, and, additionally, user settings are automatically saved before application shutdown. However, your Visual Basic application can access settings directly. In that case you have to access the `MySettings` class and use a custom *.settings* file in the root of the project. You must save the user settings before ending the application, as you would do for a C# application; this is described in the following section.
 
-<!-- markdownlint-disable MD003 -->
+<!-- markdownlint-disable MD003 MD020 -->
 ## Access or change application settings at run time in C#
-<!-- markdownlint-enable MD003 -->
+<!-- markdownlint-enable MD003 MD020 -->
 
 In languages other than Visual Basic, such as C#, you must access the `Settings` class directly, as shown in the following [!INCLUDE[csprcs](../data-tools/includes/csprcs_md.md)] example.
 

docs/test/how-to-create-a-load-test-plug-in.md

@@ -22,7 +22,9 @@ You can create a load test plug-in to run code at different times while the load
 
 [!INCLUDE [web-load-test-deprecated](includes/web-load-test-deprecated.md)]
 
+<!-- markdownlint-disable MD003 MD020 -->
 ## To create a load test plug-in in C#
+<!-- markdownlint-enable MD003 MD020 -->
 
 1. Open a web performance and load test project that contains a web performance test.
 

docs/vs-2015/csharp-ide/using-the-visual-studio-development-environment-for-csharp.md

@@ -18,7 +18,8 @@ author: gewarren
 ms.author: gewarren
 manager: jillfra
 ---
-# Using the Visual Studio Development Environment for C# #
+# Using the Visual Studio Development Environment for C\#
+
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
 The Visual Studio integrated development environment (IDE) is a collection of development tools exposed through a common user interface. Some of the tools are shared with other [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] languages, and some, such as the C# compiler, are unique to Visual C#. This topic provides links to the most important Visual C# tools.
@@ -43,6 +44,7 @@ The Visual Studio integrated development environment (IDE) is a collection of de
 |[Managing Application Resources (.NET)](../ide/managing-application-resources-dotnet.md)|Shows how to add or edit resources for your project, such as strings, images, icons, audio, and files.|
 
 ## See Also
- [C#](http://msdn.microsoft.com/library/7f4f8103-7068-4f1d-92c7-3c4519b6edbc)
- [Getting Started with C#](http://msdn.microsoft.com/library/d6ec050f-3956-4737-8030-a4fa3521d29f)
- [C# Reference](http://msdn.microsoft.com/library/06de3167-c16c-4e1a-b3c5-c27841d4569a)
+
+- [C#](http://msdn.microsoft.com/library/7f4f8103-7068-4f1d-92c7-3c4519b6edbc)
+- [Getting Started with C#](http://msdn.microsoft.com/library/d6ec050f-3956-4737-8030-a4fa3521d29f)
+- [C# Reference](http://msdn.microsoft.com/library/06de3167-c16c-4e1a-b3c5-c27841d4569a)

docs/vs-2015/debugger/debugging-f-hash.md

@@ -4,12 +4,12 @@ ms.date: 11/15/2016
 ms.prod: "visual-studio-dev14"
 ms.technology: "vs-ide-debug"
 ms.topic: conceptual
-dev_langs: 
+dev_langs:
   - "FSharp"
   - "VB"
   - "CSharp"
   - "C++"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "Debugging [F#]"
   - "F#, debugging"
 ms.assetid: 20bcd51c-2d06-4281-9a1e-ef2b91d1a779
@@ -18,16 +18,18 @@ author: MikeJo5000
 ms.author: mikejo
 manager: jillfra
 ---
-# Debugging F# #
+# Debugging F\#
+
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-Debugging F# is similar to debugging any managed language, with a few exceptions:  
-
-- The **Autos** window does not display F# variables.  
-
-- Edit and Continue is not supported for F#. Editing F# code during a debugging session is possible but should be avoided. Because code changes are not applied during the debugging session, editing F# code during debugging will cause a mismatch between the source code and the code being debugged.  
-
-- The debugger does not recognize F# expressions. To enter an expression in a debugger window or a dialog box during F# debugging, you must translate the expression into C# syntax. When you translate an F# expression into C#, make sure to remember that C# uses == as the comparison operator for equality and that F# uses a single =.  
-
-## See Also  
- [Debugging Managed Code](../debugger/debugging-managed-code.md)
+Debugging F# is similar to debugging any managed language, with a few exceptions:
+
+- The **Autos** window does not display F# variables.
+
+- Edit and Continue is not supported for F#. Editing F# code during a debugging session is possible but should be avoided. Because code changes are not applied during the debugging session, editing F# code during debugging will cause a mismatch between the source code and the code being debugged.
+
+- The debugger does not recognize F# expressions. To enter an expression in a debugger window or a dialog box during F# debugging, you must translate the expression into C# syntax. When you translate an F# expression into C#, make sure to remember that C# uses == as the comparison operator for equality and that F# uses a single =.
+
+## See Also
+
+- [Debugging Managed Code](../debugger/debugging-managed-code.md)

docs/vs-2015/debugger/format-specifiers-in-csharp.md

@@ -4,13 +4,13 @@ ms.date: 11/15/2016
 ms.prod: "visual-studio-dev14"
 ms.technology: "vs-ide-debug"
 ms.topic: conceptual
-dev_langs: 
+dev_langs:
   - "FSharp"
   - "VB"
   - "CSharp"
   - "C++"
   - "CSharp"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "expressions [C#], formatting values"
   - "variables [debugger], watch variable symbols"
   - "symbols, watch variable formatting"
@@ -28,42 +28,46 @@ author: MikeJo5000
 ms.author: mikejo
 manager: jillfra
 ---
-# Format Specifiers in C# #
+# Format Specifiers in C\#
+
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-You can change the format in which a value is displayed in the **Watch** window using format specifiers. You can also use format specifiers in the **Immediate** window, the **Command** window, and even in source windows. If you pause on an expression in those windows, the result will appear in a DataTip. DataTips will reflect the format specifier in the DataTip display.  
-
- To use a format specifier, type the expression followed by a comma. After the comma, add the appropriate specifier.  
-
-## Using Format Specifiers  
- If you have the following code:  
-
-```  
-{  
-    int my_var1 = 0x0065;  
-    int my_var2 = 0x0066;  
-    int my_var3 = 0x0067;  
-}  
-```  
-
- Add the `my_var1` variable to the Watch window (while debugging, **Debug / Windows / Watch / Watch 1**) and set the display to hexadecimal (in the **Watch** window, right-click the variable and select **Hexadecimal Display**). Now the **Watch** window shows that it contains the value 0x0065. To see this value expressed as a decimal integer instead of a hexadecimal integer, in the Name column, after the variable name, add the decimal format specifier: **, d**. The Value column now displays the decimal value 101  
-
- ![WatchFormatCSharp](../debugger/media/watchformatcsharp.png "WatchFormatCSharp")  
-
-## Format Specifiers  
- The following table shows the C# format specifiers recognized by the debugger.  
-
-|Specifier|Format|Original Watch Value|Displays|  
-|---------------|------------|--------------------------|--------------|  
-|ac|Force evaluation of an expression. This can be useful when implicit evaluation of properties and implicit function calls is turned off. See [Side Effects and Expressions](http://msdn.microsoft.com/library/e1f8a6ea-9e19-481d-b6bd-df120ad3bf4e).|Message “Implicit function evaluation is turned off by the user”|\<value>|  
-|d|decimal integer|0x0065|101|  
-|dynamic|Displays the specified object using a Dynamic View|Displays all the members of the object, including the Dynamic View|Displays only the Dynamic View|  
-|h|hexadecimal integer|61541|0x0000F065|  
-|nq|string with no quotes|"My String"|My String|  
-|hidden|Displays all public and non-public members|Displays public members|Displays all members|  
-|raw|Displays item as it appears in the raw item node. Valid on proxy objects only.|Dictionary\<T>|Raw View of Dictionary\<T>|  
-|results|Used with a variable of a type that implements IEnumerable or IEnumerable\<T>, usually the result of a query expression. Displays only the members that contain the query result.|Displays all the members.|Displays the members the meet the conditions of the query.|  
-
-## See Also  
- [Watch and QuickWatch Windows](../debugger/watch-and-quickwatch-windows.md)   
- [Variable Windows](http://msdn.microsoft.com/library/ce0a67f6-2502-4b7a-ba45-cc32f8aeba3e)
+You can change the format in which a value is displayed in the **Watch** window using format specifiers. You can also use format specifiers in the **Immediate** window, the **Command** window, and even in source windows. If you pause on an expression in those windows, the result will appear in a DataTip. DataTips will reflect the format specifier in the DataTip display.
+
+To use a format specifier, type the expression followed by a comma. After the comma, add the appropriate specifier.
+
+## Using Format Specifiers
+
+If you have the following code:
+
+```csharp
+{
+    int my_var1 = 0x0065;
+    int my_var2 = 0x0066;
+    int my_var3 = 0x0067;
+}
+```
+
+Add the `my_var1` variable to the Watch window (while debugging, **Debug / Windows / Watch / Watch 1**) and set the display to hexadecimal (in the **Watch** window, right-click the variable and select **Hexadecimal Display**). Now the **Watch** window shows that it contains the value 0x0065. To see this value expressed as a decimal integer instead of a hexadecimal integer, in the Name column, after the variable name, add the decimal format specifier: **, d**. The Value column now displays the decimal value 101
+
+![WatchFormatCSharp](../debugger/media/watchformatcsharp.png "WatchFormatCSharp")
+
+## Format Specifiers
+
+The following table shows the C# format specifiers recognized by the debugger.
+
+|Specifier|Format|Original Watch Value|Displays|
+|---------------|------------|--------------------------|--------------|
+|ac|Force evaluation of an expression. This can be useful when implicit evaluation of properties and implicit function calls is turned off. See [Side Effects and Expressions](http://msdn.microsoft.com/library/e1f8a6ea-9e19-481d-b6bd-df120ad3bf4e).|Message “Implicit function evaluation is turned off by the user”|\<value>|
+|d|decimal integer|0x0065|101|
+|dynamic|Displays the specified object using a Dynamic View|Displays all the members of the object, including the Dynamic View|Displays only the Dynamic View|
+|h|hexadecimal integer|61541|0x0000F065|
+|nq|string with no quotes|"My String"|My String|
+|hidden|Displays all public and non-public members|Displays public members|Displays all members|
+|raw|Displays item as it appears in the raw item node. Valid on proxy objects only.|Dictionary\<T>|Raw View of Dictionary\<T>|
+|results|Used with a variable of a type that implements IEnumerable or IEnumerable\<T>, usually the result of a query expression. Displays only the members that contain the query result.|Displays all the members.|Displays the members the meet the conditions of the query.|
+
+## See Also
+
+- [Watch and QuickWatch Windows](../debugger/watch-and-quickwatch-windows.md)
+- [Variable Windows](http://msdn.microsoft.com/library/ce0a67f6-2502-4b7a-ba45-cc32f8aeba3e)