fix: MD005/list-indent

Inconsistent indentation for list items at the same level

devices/surface-hub/surface-hub-2s-setup.md

@@ -97,5 +97,5 @@ If you insert a USB thumb drive with a provisioning package into one of the USB
 
     ![* Select a device account and friendly name from your configuration file*](images/sh2-run14.png) <br>
 
- 4. Follow the instructions to complete first time Setup.
+4. Follow the instructions to complete first time Setup.
 

mdop/appv-v4/how-to-manually-install-the-application-virtualization-client.md

@@ -13,10 +13,8 @@ ms.prod: w8
 ms.date: 08/30/2016
 ---
 
-
 # How to Manually Install the Application Virtualization Client
 
-
 There are two types of Application Virtualization Client components: the Application Virtualization Desktop Client, which is designed for installation on desktop computers, and the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services), which you can install on Remote Desktop Session Host (RD Session Host) servers . Although the two client installer programs are different, you can use the following procedure to manually install either the Application Virtualization Desktop Client on a single desktop computer or the Application Virtualization Client for Remote Desktop Services on a single RD Session Host server. In a production environment, you most likely will install the Application Virtualization Desktop Client on multiple desktop computers with an automated scripted installation process. For information about how to install multiple clients by using a scripted installation process, see [How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md).
 
 **Note**  
@@ -24,13 +22,9 @@ There are two types of Application Virtualization Client components: the Applica
 
 2. If you have any configuration on the user’s computer that depends on the client install path, note that the Application Virtualization (App-V) 4.5 client uses a different install folder than previous versions. By default, a new install of the Application Virtualization (App-V) 4.5 client will install to the \\Program Files\\Microsoft Application Virtualization Client folder. If an earlier version of the client is already installed, installing the App-V client will perform an upgrade into the existing installation folder.
 
-
-
 **Note**  
 For App-V version 4.6 and later, when the App-V client is installed, SFTLDR.DLL is installed in the Windows\\system32 directory. If the App-V client is installed on a 64-bit system, SFTLDR\_WOW64.DLL is installed in the Windows\\SysWOW64 directory.
 
-
-
 **To manually install Application Virtualization Desktop Client**
 
 1. After you have obtained the correct installer archive file and saved it to your computer, make sure you are logged on with an account having administrator rights on the computer and double-click the file to expand the archive.
@@ -52,13 +46,9 @@ For App-V version 4.6 and later, when the App-V client is installed, SFTLDR.DLL
     **Note**  
     For App-V version 4.6 and later, the wizard will also install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
 
-    For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see <https://go.microsoft.com/fwlink/?LinkId=150700> (https://go.microsoft.com/fwlink/?LinkId=150700).
+    For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see [https://go.microsoft.com/fwlink/?LinkId=150700](https://go.microsoft.com/fwlink/?LinkId=150700).
 
-
-
-~~~
-If prompted, click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
-~~~
+    If prompted, click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
 
 6. When the **Microsoft Application Virtualization Desktop Client – InstallShield Wizard** is displayed, click **Next**.
 
@@ -85,8 +75,6 @@ If prompted, click **Install**. Installation progress is displayed, and the stat
        **Note**  
        This path must be different for every user, so it should include a user-specific environment variable or a mapped drive or something else that will resolve to a unique path for each user.
 
-
-
     4. When you have finished making the changes, click **Next**.
 
 13. On the **Cache Size Settings** screen, you can accept or change the default cache size. Click one of the following radio buttons to choose how to manage the cache space:
@@ -98,11 +86,7 @@ If prompted, click **Install**. Installation progress is displayed, and the stat
     **Important**  
     To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly. For more information about the cache space management feature, in the Microsoft Application Virtualization (App-V) Operations Guide, see **How to Use the Cache Space Management Feature**.
 
-
-
-~~~
-Click **Next** to continue.
-~~~
+    Click **Next** to continue.
 
 14. In the following sections of the **Runtime Package Policy Configuration** screen, you can change the parameters that affect how the Application Virtualization client behaves during runtime:
 
@@ -117,11 +101,7 @@ Click **Next** to continue.
        **Note**  
        When you install the App-V client to use with a read-only cache, for example, with a VDI server implementation, set **What applications to Auto Load** to **Do not automatically load applications** to prevent the client from trying to update applications in the read-only cache.
 
-
-
-~~~
-Click **Next** to continue.
-~~~
+    Click **Next** to continue.
 
 15. On the **Publishing Server** screen, select the **Set up a Publishing Server now** check box if you want to define a publishing server, or click **Next** if you want to complete this later. To define a publishing server, specify the following information:
 
@@ -144,20 +124,8 @@ Click **Next** to continue.
     **Note**  
     If the installation fails for any reason, you might need to restart the computer before trying the install again.
 
-
-
 ## Related topics
 
-
 [How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
 
 [Stand-Alone Delivery Scenario Overview](stand-alone-delivery-scenario-overview.md)
-
-
-
-
-
-
-
-
-

windows/client-management/mdm/index.md

@@ -44,7 +44,7 @@ The MDM security baseline includes policies that cover the following areas:
 For more details about the MDM policies defined in the MDM security baseline and what Microsoft’s recommended baseline policy values are, see:
 - [MDM Security baseline for Windows 10, version 1903](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1903-MDM-SecurityBaseLine-Document.zip)
 
- - [MDM Security baseline for Windows 10, version 1809](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1809-MDM-SecurityBaseLine-Document-[Preview].zip)
+- [MDM Security baseline for Windows 10, version 1809](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1809-MDM-SecurityBaseLine-Document-[Preview].zip)
 
 For information about the MDM policies defined in the Intune security baseline public preview, see [Windows security baseline settings for Intune](https://docs.microsoft.com/intune/security-baseline-settings-windows)
 

windows/security/threat-protection/microsoft-defender-atp/exposed-apis-create-app-nativeapp.md

@@ -102,7 +102,7 @@ For more details on AAD token, refer to [AAD tutorial](https://docs.microsoft.co
 - Copy/Paste the below class in your application.
 - Use **AcquireUserTokenAsync** method with the your application ID, tenant ID, user name and password to acquire a token.
 
-    ```
+    ```csharp
     namespace WindowsDefenderATP
     {
         using System.Net.Http;
@@ -156,7 +156,8 @@ Sanity check to make sure you got a correct token:
 - The Expiration time of the token is 1 hour (you can send more then one request with the same token)
 
 - Example of sending a request to get a list of alerts **using C#** 
-    ```
+
+    ```csharp
     var httpClient = new HttpClient();
 
     var request = new HttpRequestMessage(HttpMethod.Get, "https://api.securitycenter.windows.com/api/alerts");

windows/security/threat-protection/microsoft-defender-atp/user-roles.md

@@ -42,12 +42,12 @@ The following steps guide you on how to create roles in Microsoft Defender Secur
       - **Active remediation actions** - Users can take response actions and approve or dismiss pending remediation actions.
       - **Manage portal system settings** - Users can configure storage settings, SIEM and threat intel API settings (applies globally), advanced settings, automated file uploads, roles and machine groups.
 
-            >[!NOTE]
-            >This setting is only available in the Microsoft Defender ATP administrator (default) role. 
+        > [!NOTE]
+        > This setting is only available in the Microsoft Defender ATP administrator (default) role.
 
       - **Manage security settings** - Users can configure alert suppression settings, manage allowed/blocked lists for automation, create and manage custom detections, manage folder exclusions for automation, onboard and offboard machines, and manage email notifications.
 
-		  - **Live response capabilities** - Users can take basic or advanced live response commands. <br>
+      - **Live response capabilities** - Users can take basic or advanced live response commands.
         - Basic commands allow users to:
           - Start a live response session
           - Run read only live response commands on a remote machine