fix: MD030/list-marker-space

Replace unordered list space after marker inside blockquotes
Find: `^>(\s*)\-  `
Replace: `>$1- `
Filter: *.md

Author: nschonni

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

@@ -50,9 +50,9 @@ In native C++ code, you might have to qualify the context of a variable name. Fo
 >[!CAUTION]
 >Make sure you understand the consequences before you change values and expressions. Some possible issues are:
 >
->-   Evaluating some expressions can change the value of a variable or otherwise affect the state of your program. For example, evaluating `var1 = ++var2` changes the value of both `var1` and `var2`. These expressions are said to have [side effects](https://en.wikipedia.org/wiki/Side_effect_\(computer_science\)). Side effects can cause unexpected results if you are not aware of them.
+>- Evaluating some expressions can change the value of a variable or otherwise affect the state of your program. For example, evaluating `var1 = ++var2` changes the value of both `var1` and `var2`. These expressions are said to have [side effects](https://en.wikipedia.org/wiki/Side_effect_\(computer_science\)). Side effects can cause unexpected results if you are not aware of them.
 >
->-   Editing floating-point values can result in minor inaccuracies because of decimal-to-binary conversion of fractional components. Even a seemingly harmless edit can result in changes to some of the bits in the floating-point variable.
+>- Editing floating-point values can result in minor inaccuracies because of decimal-to-binary conversion of fractional components. Even a seemingly harmless edit can result in changes to some of the bits in the floating-point variable.
 
 ::: moniker range=">= vs-2019" 
 ## Search in the Autos or Locals window

docs/profiling/concurrency-visualizer.md

@@ -22,7 +22,7 @@ ms.workload:
 >
 > - Download the              [Concurrency Visualizer for Visual Studio 2017](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ConcurrencyVisualizer2017#overview) extension.
 > - Download the              [Concurrency Visualizer for Visual Studio 2015](https://marketplace.visualstudio.com/items?itemName=Diagnostics.ConcurrencyVisualizerforVisualStudio2015) extension.
->   -   Download the              [Concurrency Visualizer Collection Tools for Visual Studio 2015](http://www.microsoft.com/download/details.aspx?id=49103).
+>   - Download the              [Concurrency Visualizer Collection Tools for Visual Studio 2015](http://www.microsoft.com/download/details.aspx?id=49103).
 >
 >   The [Concurrency Visualizer Command-Line Utility (CVCollectionCmd)](../profiling/concurrency-visualizer-command-line-utility-cvcollectioncmd.md) lets you collect traces from the command line that you can view in the Concurrency Visualizer for Visual Studio 2015. The tool can be used on computers that do not have Visual Studio installed.
 

docs/vs-2015/cross-platform/build-apps-with-native-ui-using-xamarin-in-visual-studio.md

@@ -38,15 +38,15 @@ Once you've done the steps in [Setup and install](../cross-platform/setup-and-in
 >
 > - Xamarin apps with native UI:
 >
->   -   [Hello, Android](https://developer.xamarin.com/guides/android/getting_started/hello,android/) (simple app with one screen)
->   -   [Hello, Android multiscreen](https://developer.xamarin.com/guides/android/getting_started/hello,android_multiscreen/) (app with navigation between screens)
->   -   [Android Fragments Walkthrough](http://developer.xamarin.com/guides/android/platform_features/fragments/fragments_walkthrough/) (used for master/detail screens, among other things)
->   -   [Hello, iOS](https://developer.xamarin.com/guides/ios/getting_started/hello,_iOS/)
->   -   [Hello, iOS Multiscreen](https://developer.xamarin.com/guides/ios/getting_started/hello,_iOS_multiscreen/)
->   -   Xamarin apps with Xamarin.Forms (shared UI)
+>   - [Hello, Android](https://developer.xamarin.com/guides/android/getting_started/hello,android/) (simple app with one screen)
+>   - [Hello, Android multiscreen](https://developer.xamarin.com/guides/android/getting_started/hello,android_multiscreen/) (app with navigation between screens)
+>   - [Android Fragments Walkthrough](http://developer.xamarin.com/guides/android/platform_features/fragments/fragments_walkthrough/) (used for master/detail screens, among other things)
+>   - [Hello, iOS](https://developer.xamarin.com/guides/ios/getting_started/hello,_iOS/)
+>   - [Hello, iOS Multiscreen](https://developer.xamarin.com/guides/ios/getting_started/hello,_iOS_multiscreen/)
+>   - Xamarin apps with Xamarin.Forms (shared UI)
 >
->   -   [Hello, Xamarin.Forms](https://developer.xamarin.com/guides/cross-platform/xamarin-forms/getting-started/hello-xamarin-forms/quickstart/)
->   -   [Hello, Xamarin.Forms Multiscreen](https://developer.xamarin.com/guides/cross-platform/xamarin-forms/getting-started/hello-xamarin-forms-multiscreen/)
+>   - [Hello, Xamarin.Forms](https://developer.xamarin.com/guides/cross-platform/xamarin-forms/getting-started/hello-xamarin-forms/quickstart/)
+>   - [Hello, Xamarin.Forms Multiscreen](https://developer.xamarin.com/guides/cross-platform/xamarin-forms/getting-started/hello-xamarin-forms-multiscreen/)
 
 ##  <a name="solution"></a> Set up your solution
  These steps create a Xamarin solution with native UI that contains a PCL for shared code and two added NuGet packages.

docs/vs-2015/debugger/create-custom-views-of-native-objects.md

@@ -28,8 +28,8 @@ The Visual Studio Natvis framework lets you customize the way Visual Studio disp
 >  You cannot use the Natvis framework for visualizations when:  
 > 
 > - You are debugging a C++ Windows desktop project with debugger type set to **mixed**.  
->   -   You are doing mixed mode debugging in a Windows desktop application in managed compatibility mode (**Tools / Options / Debugging / General / Use Managed Compatibility Mode**).  
->   -   You are debugging in a Windows desktop application in native compatibility mode (**Tools / Options / Debugging / General / Use Native Compatibility Mode**).  
+>   - You are doing mixed mode debugging in a Windows desktop application in managed compatibility mode (**Tools / Options / Debugging / General / Use Managed Compatibility Mode**).  
+>   - You are debugging in a Windows desktop application in native compatibility mode (**Tools / Options / Debugging / General / Use Native Compatibility Mode**).  
 
 ##  <a name="BKMK_Why_create_visualizations_"></a> Why create Natvis visualizations?  
  You can use the Natvis framework to create visualization rules for the types you create so developers can see them easily during debugging.  

docs/vs-2015/debugger/debug-multiple-processes.md

@@ -63,7 +63,7 @@ Here’s how to start debugging processes, switch between processes, break and c
 > - Attach to the child process after it has been started.  
 > 
 >   -or-  
->   -   Configure Windows to automatically start the child process in a new instance of the debugger.  
+>   - Configure Windows to automatically start the child process in a new instance of the debugger.  
   
 ###  <a name="BKMK_Start_debugging_multiple_processes_in_a_Visual_Studio_solution"></a> Start debugging multiple processes in a Visual Studio solution  
  When you have more than one project in a Visual Studio solution that can run independently (projects that run in separate processes), you can select which projects the debugger starts.  

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

@@ -40,7 +40,7 @@ You can change the format in which a value is displayed in the **Watch** window
 >  The Visual Studio native debugger changed to a new debugging engine. As part of this change, some new format specifiers were added and some old ones were removed. The  older debugger is still used when you do interop (mixed native and managed) debugging with C++/CLI. The following sections in this topic show the format specifiers for each debug engine.  
 > 
 > - [Format Specifiers](#BKMK_Visual_Studio_2012_format_specifiers) describes the format specifiers in the new debugging engine.  
->   -   [Format specifiers for interop debugging with C++/CLI](#BKMK_Format_specifiers_for_interop_debugging_and_C___edit_and_continue) describes the format specifiers in the older debugging engine.  
+>   - [Format specifiers for interop debugging with C++/CLI](#BKMK_Format_specifiers_for_interop_debugging_and_C___edit_and_continue) describes the format specifiers in the older debugging engine.  
   
 ## Using Format Specifiers  
  If you have the following code:  

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

@@ -137,18 +137,18 @@ Get familiar with commands and shortcuts to navigate code in the debugger and th
 >  Setting the next statement causes the program counter to jump directly to the new location. Use this command with caution:  
 > 
 > - Instructions between the old and new execution points are not executed.  
->   -   If you move the execution point backwards, intervening instructions are not undone.  
->   -   Moving the next statement to another function or scope usually results in call-stack corruption, causing a run-time error or exception. If you try moving the next statement to another scope, the debugger opens a dialog box with a warning and gives you a chance to cancel the operation. In Visual Basic, you cannot move the next statement to another scope or function.  
->   -   In native C++, if you have run-time checks enabled, setting the next statement can cause an exception to be thrown when execution reaches the end of the method.  
->   -   When Edit and Continue is enabled, **Set Next Statement** fails if you have made edits that Edit and Continue cannot remap immediately. This can occur, for example, if you have edited code inside a catch block. When this happens, you’ll see an error message that tells you that the operation is not supported.  
+>   - If you move the execution point backwards, intervening instructions are not undone.  
+>   - Moving the next statement to another function or scope usually results in call-stack corruption, causing a run-time error or exception. If you try moving the next statement to another scope, the debugger opens a dialog box with a warning and gives you a chance to cancel the operation. In Visual Basic, you cannot move the next statement to another scope or function.  
+>   - In native C++, if you have run-time checks enabled, setting the next statement can cause an exception to be thrown when execution reaches the end of the method.  
+>   - When Edit and Continue is enabled, **Set Next Statement** fails if you have made edits that Edit and Continue cannot remap immediately. This can occur, for example, if you have edited code inside a catch block. When this happens, you’ll see an error message that tells you that the operation is not supported.  
 > 
 > [!NOTE]
 >  In managed code, you cannot move the next statement under the following conditions:  
 > 
 > - The next statement is in a different method than the current statement.  
->   -   Debugging was started by using Just-In-Time debugging.  
->   -   A callstack unwind is in progress.  
->   -   A System.StackOverflowException or System.Threading.ThreadAbortException exception has been thrown.  
+>   - Debugging was started by using Just-In-Time debugging.  
+>   - A callstack unwind is in progress.  
+>   - A System.StackOverflowException or System.Threading.ThreadAbortException exception has been thrown.  
   
  You cannot set the next statement while your application is actively running. To set the next statement, the debugger must be in break mode.  
 

docs/vs-2015/extensibility/creating-a-basic-project-system-part-1.md

@@ -24,7 +24,7 @@ In Visual Studio, projects are the containers that developers use to organize so
 >  If you need to extend Visual Studio with a custom project type, we strongly recommend leveraging the [Visual Studio Project System](https://github.com/Microsoft/VSProjectSystem) which has a number of advantages over building a project system from scratch:  
 > 
 > - Easier onboarding.  Even a basic project system requires tens of thousands of lines of code.  Leveraging CPS reduces the onboarding cost to a few clicks before you are ready to customize it to your needs.  
->   -   Easier maintenance.  By leveraging CPS, you only need to maintain your own scenarios.  We handle the upkeep of all of the project system infrastructure.  
+>   - Easier maintenance.  By leveraging CPS, you only need to maintain your own scenarios.  We handle the upkeep of all of the project system infrastructure.  
 > 
 >   If you need to target versions of Visual Studio older than Visual Studio 2013, you will not be able to leverage CPS in a Visual Studio extension.  If that is the case, this walkthrough is a good place to get started.  
   

docs/vs-2015/extensibility/shell-isolated-or-integrated.md

@@ -46,7 +46,7 @@ You can create your own Visual Studio-based application in either integrated or
 >  If you collect separate usage data from your customers through your application, you must provide appropriate notice to users of your application of what you collect.  When you distribute either the isolated or integrated shell software as part of your application, according to the Visual Studio Software Development Kit license, you must include one of the following:  
 > 
 > - the End User License Agreement as part of your application license  
->   -   your own EULA that requires your customers to agree to terms that protect the Visual Studio integrated or isolated shell at least as much as the Microsoft End User License Terms for the shell software  
+>   - your own EULA that requires your customers to agree to terms that protect the Visual Studio integrated or isolated shell at least as much as the Microsoft End User License Terms for the shell software  
   
 ## Additional Resources  
  For more information about redistributable packages, see the [Visual Studio Extensibility Downloads](http://go.microsoft.com/fwlink/?LinkID=119298) Web site.  

docs/vs-2015/install/how-to-install-a-specific-release-of-visual-studio.md

@@ -40,18 +40,18 @@ We update Visual Studio setup often so that you get the most current, optimized
 >  Depending on the language that you want to use, please replace "enu" (for English) with one of the following values:
 >
 > - chs (for Chinese (Simplified))
->   -   cht (for Chinese (Traditional))
->   -   csy (for Czech)
->   -   deu (for German)
->   -   esn (for Spanish)
->   -   fra (for French)
->   -   ita (for Italian)
->   -   jpa (for Japanese)
->   -   kor (for Korean)
->   -   plk (for Polish)
->   -   ptb (for Portuguese)
->   -   rus (for Russian)
->   -   trk (for Turkish)
+>   - cht (for Chinese (Traditional))
+>   - csy (for Czech)
+>   - deu (for German)
+>   - esn (for Spanish)
+>   - fra (for French)
+>   - ita (for Italian)
+>   - jpa (for Japanese)
+>   - kor (for Korean)
+>   - plk (for Polish)
+>   - ptb (for Portuguese)
+>   - rus (for Russian)
+>   - trk (for Turkish)
 
 ## See Also
  [Visual Studio Administrator Guide](../install/visual-studio-administrator-guide.md)

docs/vs-2015/profiling/analyze-energy-use-in-store-apps.md

@@ -55,7 +55,7 @@ The Visual Studio **Energy Consumption** profiler helps you analyze the power an
 
 > [!NOTE]
 > - Windows.Foundation.Diagnostics LoggingChannel implements the [Windows.Foundation.IClosable](http://msdn.microsoft.com/library/windows/apps/windows.foundation.iclosable.aspx) interface  (projected as [System.IDisposable](http://msdn.microsoft.com/library/System.IDisposable.aspx) in C# and VB).To avoid leaking operating system resources, call [LoggingChannel.Close](http://msdn.microsoft.com/library/windows/apps/windows.foundation.diagnostics.loggingchannel.close.aspx)() (Windows.Foundation.Diagnostics.LoggingChannel.Dispose() in C# and VB) when you are finished with a logging channel.  
->   -   Each open logging channel must have a unique name. Attempting to create a new logging channel with the same name as an undisposed channel causes an exception.  
+>   - Each open logging channel must have a unique name. Attempting to create a new logging channel with the same name as an undisposed channel causes an exception.  
   
  See the Windows SDK Sample [LoggingSession Sample](http://code.msdn.microsoft.com/windowsapps/LoggingSession-Sample-ccd52336) for examples.  
 
@@ -76,8 +76,8 @@ if (performance && performance.mark) {
 
 > [!TIP]
 > - We don’t recommend energy profiling on the Windows Store simulator or on the Visual Studio computer. Profiling on the actual device provides far more realistic data.  
->   -   Profile on the target device while it is powered by its batteries.  
->   -   Close other apps that might use the same resources (network, CPU, or display).  
+>   - Profile on the target device while it is powered by its batteries.  
+>   - Close other apps that might use the same resources (network, CPU, or display).  
   
 ##  <a name="BKMK_Collect_energy_profile_data_for_your_app"></a> Collect energy profile data for your app  
 

docs/vs-2015/profiling/concurrency-visualizer.md

@@ -24,7 +24,7 @@ NOTE]
 >  The Concurrency Visualizer is an optional extension to Visual Studio. Download the Concurrency Visualizer and the Concurrency Visualizer Collection Tools from the following links:  
 > 
 > - Download the              [Concurrency Visualizer](https://visualstudiogallery.msdn.microsoft.com/a6c24ce9-beec-4545-9261-293061436ee9) extension.  
->   -   Download the              [Concurrency Visualizer Collection Tools for Visual Studio 2015](http://www.microsoft.com/download/details.aspx?id=49103).  
+>   - Download the              [Concurrency Visualizer Collection Tools for Visual Studio 2015](http://www.microsoft.com/download/details.aspx?id=49103).  
 > 
 >   The [Concurrency Visualizer Command-Line Utility (CVCollectionCmd)](../profiling/concurrency-visualizer-command-line-utility-cvcollectioncmd.md) lets you collect traces from the command line that you can view in the Concurrency Visualizer for Visual Studio 2015. The tool can be used on computers that do not have Visual Studio installed.  
   

docs/vs-2015/profiling/how-to-profile-javascript-code-in-web-pages.md

@@ -29,8 +29,8 @@ manager: jillfra
 >  To profile JavaScript in Windows Store apps, see one of the following topics:  
 > 
 > - [JavaScript Function Timing](http://msdn.microsoft.com/library/b2bf49fc-aea7-4d9c-8fcf-cff8b8dd0c03) [JavaScript Function Timing on a Remote Device](http://msdn.microsoft.com/library/d78812b6-a97e-46dc-8d99-e724d1d725d8)  
->   -   [Analyze JavaScript Function Timing data](http://msdn.microsoft.com/library/b5aea8d8-36df-47ba-a7ca-95406700ca9b)  
->   -  
+>   - [Analyze JavaScript Function Timing data](http://msdn.microsoft.com/library/b5aea8d8-36df-47ba-a7ca-95406700ca9b)  
+>   - 
   
  You can use the Profiling Wizard to create a performance session. Specify the instrumentation method and then specify the JavaScript profiling option on the Instrumentation page of the properties dialog box for the performance session.  
 

docs/vs-2015/profiling/memory-usage.md

@@ -47,7 +47,7 @@ Find memory leaks and inefficient memory while you’re debugging with the debug
 
 > [!TIP]
 > - To create a baseline for memory comparisons, consider taking a snapshot at the start of your debugging session.  
->   -   Because it can be challenging to capture the memory profile of an operation that interests you when your app frequently allocates and de-allocates memory, set breakpoints at the start and end of the operation or step through the operation to find the exact point that memory changed.  
+>   - Because it can be challenging to capture the memory profile of an operation that interests you when your app frequently allocates and de-allocates memory, set breakpoints at the start and end of the operation or step through the operation to find the exact point that memory changed.  
   
 ## Viewing memory snapshot details  
  The rows of Memory Usage summary table lists the snapshots that you have taken during the debugging session.