fix: MD030/list-marker-space

Remove space after marker for list marker in indented blockquote
Find: `^(\s*)>(\s*)\-  `
Replace: `$1>$2- `
Filter: *.md

Author: nschonni

docs/debugger/using-the-intellitrace-stand-alone-collector.md

@@ -165,11 +165,11 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
 
    > [!NOTE]
    > - To avoid slowing down your app, choose a location on a local high-speed disk that's not very active.
-   >   -   You can put .iTrace files and the collector files in the same place. However, if you have a Web app or SharePoint application, make sure this place is outside the directory that hosts the application.
+   >   - You can put .iTrace files and the collector files in the same place. However, if you have a Web app or SharePoint application, make sure this place is outside the directory that hosts the application.
    >
    > [!IMPORTANT]
    > - Restrict the .iTrace file directory only to those identities that must work with the collector. An .iTrace file might contain sensitive information, such as data from users, databases, other source locations, and connection strings because IntelliTrace can record any data that passes into method parameters or as return values.
-   >   -   Make sure those who can open .iTrace files have the authority to view sensitive data. Use caution when sharing .iTrace files. If other people must have access, copy the files to a secure shared location.
+   >   - Make sure those who can open .iTrace files have the authority to view sensitive data. Use caution when sharing .iTrace files. If other people must have access, copy the files to a secure shared location.
 
 2. For a Web app or SharePoint application, give its application pool full permissions to the .iTrace file directory. You can use the Windows **icacls** command or use Windows Explorer (or File Explorer).
 

docs/vs-2015/debugger/using-the-intellitrace-stand-alone-collector.md

@@ -166,11 +166,11 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
 
    > [!NOTE]
    > - To avoid slowing down your app, choose a location on a local high-speed disk that’s not very active.
-   >   -   You can put .iTrace files and the collector files in the same place. However, if you have a Web app or SharePoint application, make sure this place is outside the directory that hosts the application.
+   >   - You can put .iTrace files and the collector files in the same place. However, if you have a Web app or SharePoint application, make sure this place is outside the directory that hosts the application.
    >
    > [!IMPORTANT]
    > - Restrict the .iTrace file directory only to those identities that must work with the collector. An .iTrace file might contain sensitive information, such as data from users, databases, other source locations, and connection strings because IntelliTrace can record any data that passes into method parameters or as return values.
-   >   -   Make sure those who can open .iTrace files have the authority to view sensitive data. Use caution when sharing .iTrace files. If other people must have access, copy the files to a secure shared location.
+   >   - Make sure those who can open .iTrace files have the authority to view sensitive data. Use caution when sharing .iTrace files. If other people must have access, copy the files to a secure shared location.
 
 2. For a Web app or SharePoint application, give its application pool full permissions to the .iTrace file directory. You can use the Windows **icacls** command or use Windows Explorer (or File Explorer).
 

docs/vs-2015/ide/how-to-view-existing-types-class-designer.md

@@ -35,9 +35,9 @@ To see an existing type and its members, add its shape to a class diagram.
    >  If your solution has a project that shares code across multiple apps, you can drag files or code to a class diagram only from these sources:  
    > 
    > - The app project that contains the diagram  
-   >   -   A shared project that was imported by the app project  
-   >   -   A referenced project  
-   >   -   An assembly  
+   >   - A shared project that was imported by the app project  
+   >   - A referenced project  
+   >   - An assembly  
   
     Shapes representing the types defined in the source code file appear on the diagram at the position where you dragged the file.  
 

docs/vs-2015/modeling/add-custom-architecture-validation-to-layer-diagrams.md

@@ -45,7 +45,7 @@ In Visual Studio, users can validate the source code in a project against a laye
    >  To makethe template work properly:  
    > 
    > - Edit calls to `LogValidationError` to remove the optional arguments `errorSourceNodes` and `errorTargetNodes`.  
-   >   -   If you use custom properties, apply the update mentioned in [Add custom properties to layer diagrams](../modeling/add-custom-properties-to-layer-diagrams.md).  
+   >   - If you use custom properties, apply the update mentioned in [Add custom properties to layer diagrams](../modeling/add-custom-properties-to-layer-diagrams.md).  
   
 3. Edit the code to define your validation. For more information, see [Programming Validation](#programming).