fix: MD019/no-multiple-space-atx

Multiple spaces after hash on atx style heading
Find: ^(#+) ( +)(.*)\n
Repalace:$1 $3\n
Filter: *.md

Author: nschonni

docs/data-tools/create-a-simple-data-application-by-using-adonet.md

@@ -132,7 +132,7 @@ Create the sample database by following these steps:
 > [!NOTE]
 > In a real application, you should store the connection string securely, as described in [Connection strings and configuration files](/dotnet/framework/data/adonet/connection-strings-and-configuration-files).
 
-##  Write the code for the forms
+## Write the code for the forms
 
 This section contains brief overviews of what each form does. It also provides the code that defines the underlying logic when a button on the form is clicked.
 

docs/debugger/navigating-through-code-with-the-debugger.md

@@ -38,7 +38,7 @@ If you break in code that doesn't have source or symbol (*.pdb*) files loaded, t
 
 You don't always have to start debugging by starting an app at the beginning. You can also press **F11** to [step into code](#BKMK_Step_into__over__or_out_of_the_code), press **F10**  to [step over code](#BKMK_Step_over_Step_out), or [run to a specific location or function](#BKMK_Break_into_code_by_using_breakpoints_or_Break_All).
 
-##  Step through code
+## Step through code
 
 The debugger step commands help you inspect your app state or find out more about its execution flow.
 

docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md

@@ -193,7 +193,7 @@ Build with **/debug** to create a *.pdb* file. You can build applications with *
 
 Set the *web.config* file of your ASP.NET application to debug mode. Debug mode causes ASP.NET to generate symbols for dynamically generated files and enables the debugger to attach to the ASP.NET application. Visual Studio sets this automatically when you start to debug, if you created your project from the web projects template.
 
-##  Manage symbols while debugging
+## Manage symbols while debugging
 
 You can use the **Modules**, **Call Stack**, **Locals**, **Autos**, or any **Watch** window to load symbols or change symbol options while debugging. For more information, see [Get more familiar with how the debugger attaches to your app](../debugger/debugger-tips-and-tricks.md#modules_window).
 

docs/debugger/using-breakpoints.md

@@ -214,7 +214,7 @@ You can use labels to sort and filter the list of breakpoints in the **Breakpoin
 - To export all breakpoints, deselect all boxes and leave the **Search** field blank. Select the **Export all breakpoints matching the current search criteria** icon, and save the file.
 - To import breakpoints, in the **Breakpoints** window, select the **Import breakpoints from a file** icon, navigate to the XML file location, and select **Open**.
 
-##  Breakpoint conditions
+## Breakpoint conditions
  You can control when and where a breakpoint executes by setting conditions. The condition can be any valid expression that the debugger recognizes. For more information about valid expressions, see [Expressions in the debugger](../debugger/expressions-in-the-debugger.md).
 
 **To set a breakpoint condition:**

docs/deployment/how-to-publish-a-wpf-application-with-visual-styles-enabled.md

@@ -26,7 +26,7 @@ Visual styles enable the appearance of common controls to change based on the th
 
   Then, you can move the published files to the location from which you want end users to install the application.
 
-##  Publish the solution without visual styles enabled
+## Publish the solution without visual styles enabled
 
 1. Ensure that your project does not have visual styles enabled. First, check your project's manifest file for the following XML. Then, if the XML is present, enclose the XML with a comment tag.