Merge pull request #4629 from nschonni/fix--MD019/no-multiple-space-atx

fix: MD019/no-multiple-space-atx

windows/client-management/mdm/win32compatibilityappraiser-csp.md

@@ -11,7 +11,7 @@ ms.reviewer:
 manager: dansimp
 ---
 
-#  Win32CompatibilityAppraiser CSP 
+# Win32CompatibilityAppraiser CSP 
 
 > [!WARNING]
 > Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

windows/client-management/reset-a-windows-10-mobile-device.md

@@ -66,7 +66,7 @@ To perform a "wipe and persist" reset, preserving the provisioning applied to th
 </SyncML>
 ```
 
-##  Reset using the UI
+## Reset using the UI
 
 
 1.  On your mobile device, go to **Settings** > **System** > **About** > **Reset your Phone**

windows/client-management/troubleshoot-inaccessible-boot-device.md

@@ -17,7 +17,7 @@ manager: dansimp
 
 This article provides steps to troubleshoot **Stop error 7B: Inaccessible_Boot_Device**. This error may occur after some changes are made to the computer, or immediately after you deploy Windows on the computer.
 
-##  Causes of the  Inaccessible_Boot_Device  Stop error
+## Causes of the  Inaccessible_Boot_Device  Stop error
 
 Any one of the following factors may cause the stop error:
 
@@ -37,7 +37,7 @@ Any one of the following factors may cause the stop error:
 
 *	Corrupted files in the **Boot**  partition (for example, corruption in the volume that is labeled **SYSTEM**  when you run the `diskpart`  > `list vol`  command)
 
-##  Troubleshoot this error
+## Troubleshoot this error
 
 Start the computer in [Windows Recovery Mode (WinRE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre). To do this, follow these steps.
 
@@ -47,9 +47,9 @@ Start the computer in [Windows Recovery Mode (WinRE)](https://docs.microsoft.com
 
 3. On the **System Recovery Options**  screen, select **Next**  > **Command Prompt** .
 
-###  Verify that the boot disk is connected and accessible
+### Verify that the boot disk is connected and accessible
 
-####  Step 1
+#### Step 1
 
  At the WinRE Command prompt, run `diskpart`, and then run `list disk`.
 
@@ -67,7 +67,7 @@ If the computer uses a Unified Extensible Firmware Interface (UEFI) startup inte
 
 If the computer uses a basic input/output system (BIOS) interface, there will not be an asterisk in the **Dyn**  column.
 
-####  Step 2
+#### Step 2
 
 If the `list disk` command lists the OS disks correctly, run the `list vol` command in `diskpart`.
 
@@ -88,7 +88,7 @@ If the `list disk` command lists the OS disks correctly, run the `list vol` comm
 >[!NOTE]
 >If the disk that contains the OS is not listed in the output, you will have to engage the OEM or virtualization manufacturer.
 
-###  Verify the integrity of Boot Configuration Database
+### Verify the integrity of Boot Configuration Database
 
 Check whether the Boot Configuration Database (BCD) has all the correct entries. To do this, run `bcdedit` at the WinRE command prompt.
 
@@ -163,7 +163,7 @@ If you do not have a Windows 10 ISO, you must format the partition and copy **bo
 
 4. Right-click the partition, and then format it.
 
-###  Troubleshooting if this issue occurs after a Windows Update installation
+### Troubleshooting if this issue occurs after a Windows Update installation
 
 Run the following command to verify the Windows update installation and dates:
 
@@ -203,9 +203,9 @@ After you run this command, you will see the **Install pending** and **Uninstall
 
 11.	 Expand **Control\Session Manager**. Check whether the **PendingFileRenameOperations** key exists. If it does, back up the **SessionManager** key, and then delete the **PendingFileRenameOperations** key.
 
-###  Verifying boot critical drivers and services
+### Verifying boot critical drivers and services
 
-####  Check services	
+#### Check services	
 
 1.	 Follow steps 1-10 in the "Troubleshooting if this issue occurs after an Windows Update installation" section. (Step 11 does not apply to this procedure.)
 
@@ -235,7 +235,7 @@ ren SYSTEM SYSTEM.old
 copy OSdrive:\Windows\System32\config\RegBack\SYSTEM OSdrive:\Windows\System32\config\
 ```
 
-####  Check upper and lower filter drivers
+#### Check upper and lower filter drivers
 
 Check whether there are any non-Microsoft upper and lower filter drivers on the computer and that they do not exist on another, similar working computer. if they do exist, remove the upper and lower filter drivers:
 
@@ -268,7 +268,7 @@ The reason that these entries may affect us is because there may be an entry in
 >[!NOTE]
 >If there actually is a service that is set to **0** or **1** that corresponds to an **UpperFilters** or **LowerFilters** entry, setting the service to disabled in the **Services** registry (as discussed in steps 2 and 3 of the Check services section) without removing the **Filter Driver** entry causes the computer to crash and generate a 0x7b Stop error.
 
-###  Running SFC and Chkdsk
+### Running SFC and Chkdsk
 
  If the computer still does not start, you can try to run a **chkdisk**  process on the system drive, and also run System File Checker. To do this, run the following commands at a WinRE command prompt:
 

windows/configuration/kiosk-xml.md

@@ -16,7 +16,7 @@ ms.author: dansimp
 ms.topic: article
 ---
 
-#  Assigned Access configuration (kiosk) XML reference
+# Assigned Access configuration (kiosk) XML reference
 
 
 **Applies to**

windows/privacy/gdpr-it-guidance.md

@@ -159,7 +159,7 @@ The following table lists in what GDPR mode – controller or processor – Wind
 
 */*Depending on which application/feature this is referring to.*
 
-##  Windows diagnostic data and Windows 10
+## Windows diagnostic data and Windows 10
 
 
 ### Recommended Windows 10 settings

windows/security/identity-protection/credential-guard/credential-guard-known-issues.md

@@ -16,7 +16,7 @@ ms.date: 08/17/2017
 ms.reviewer: 
 ---
 
-#  Windows Defender Credential Guard: Known issues 
+# Windows Defender Credential Guard: Known issues 
 
 **Applies to**
 -   Windows 10

windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md

@@ -38,7 +38,7 @@ A new Active Directory Federation Services farm should have a minimum of two fed
 
 Prepare the Active Directory Federation Services deployment by installing and updating two Windows Server 2016 Servers.  Ensure the update listed below is applied to each server before continuing.    
 
-##  Update Windows Server 2016
+## Update Windows Server 2016
 
 Sign-in the federation server with _local admin_ equivalent credentials.
 1. Ensure Windows Server 2016 is current by running **Windows Update** from **Settings**. Continue this process until no further updates are needed. If you’re not using Windows Update for updates, please advise the [Windows Server 2016 update history page](https://support.microsoft.com/help/4000825/windows-10-windows-server-2016-update-history) to make sure you have the latest updates available installed.

windows/security/identity-protection/hello-for-business/hello-key-trust-adfs.md

@@ -38,7 +38,7 @@ A new Active Directory Federation Services farm should have a minimum of two fed
 
 Prepare the Active Directory Federation Services deployment by installing and updating two Windows Server 2016 Servers.  Ensure the update listed below is applied to each server before continuing.    
 
-##  Update Windows Server 2016
+## Update Windows Server 2016
 
 Sign-in the federation server with _local admin_ equivalent credentials.
 1. Ensure Windows Server 2016 is current by running **Windows Update** from **Settings**. Continue this process until no further updates are needed. If you’re not using Windows Update for updates, please review the [Windows Server 2016 update history page](https://support.microsoft.com/help/4000825/windows-10-windows-server-2016-update-history) to make sure you have the latest updates available installed.

windows/security/identity-protection/remote-credential-guard.md

@@ -15,7 +15,7 @@ ms.localizationpriority: medium
 ms.date: 01/12/2018
 ms.reviewer: 
 ---
-#  Protect Remote Desktop credentials with Windows Defender Remote Credential Guard
+# Protect Remote Desktop credentials with Windows Defender Remote Credential Guard
 
 **Applies to**
 -   Windows 10

windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md

@@ -48,7 +48,7 @@ This is applicable to Azure Hybrid AD as well.
 For Windows PCs and Windows Phones that enroll using **Connect to work or school account**, BitLocker Device Encryption is managed over MDM, the same as devices joined to Azure AD.
 
 
-##  Managing servers
+## Managing servers
 
 Servers are often installed, configured, and deployed using PowerShell, so the recommendation is to also use [PowerShell to enable BitLocker on a server](bitlocker-use-bitlocker-drive-encryption-tools-to-manage-bitlocker.md#bitlocker-cmdlets-for-windows-powershell), ideally as part of the initial setup. BitLocker is an Optional Component (OC) in Windows Server, so follow the directions in [BitLocker: How to deploy on Windows Server 2012 and later](bitlocker-how-to-deploy-on-windows-server.md) to add the BitLocker OC. 
 

windows/security/threat-protection/TOC.md

@@ -133,7 +133,7 @@
 
 #### [Integrations]()
 ##### [Microsoft Defender ATP integrations](microsoft-defender-atp/threat-protection-integration.md)
-#####  [Protect users, data, and devices with conditional access](microsoft-defender-atp/conditional-access.md)
+##### [Protect users, data, and devices with conditional access](microsoft-defender-atp/conditional-access.md)
 ##### [Microsoft Cloud App Security integration overview](microsoft-defender-atp/microsoft-cloud-app-security-integration.md)
 
 #### [Information protection in Windows overview]()
@@ -1049,7 +1049,7 @@
 ###### [Network access: Remotely accessible registry paths](security-policy-settings/network-access-remotely-accessible-registry-paths.md)
 ###### [Network access: Remotely accessible registry paths and subpaths](security-policy-settings/network-access-remotely-accessible-registry-paths-and-subpaths.md)
 ###### [Network access: Restrict anonymous access to Named Pipes and Shares](security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares.md)
-######  [Network access: Restrict clients allowed to make remote calls to SAM](security-policy-settings/network-access-restrict-clients-allowed-to-make-remote-sam-calls.md)
+###### [Network access: Restrict clients allowed to make remote calls to SAM](security-policy-settings/network-access-restrict-clients-allowed-to-make-remote-sam-calls.md)
 ###### [Network access: Shares that can be accessed anonymously](security-policy-settings/network-access-shares-that-can-be-accessed-anonymously.md)
 ###### [Network access: Sharing and security model for local accounts](security-policy-settings/network-access-sharing-and-security-model-for-local-accounts.md)
 ###### [Network security: Allow Local System to use computer identity for NTLM](security-policy-settings/network-security-allow-local-system-to-use-computer-identity-for-ntlm.md)

windows/security/threat-protection/microsoft-defender-atp/alerts-queue.md

@@ -38,7 +38,7 @@ On the top navigation you can:
 
 ![Image of alerts queue](images/alerts-queue-list.png)
 
-##  Sort, filter, and group the alerts queue
+## Sort, filter, and group the alerts queue
 You can apply the following filters to limit the list of alerts and get a more focused view the alerts.
 
 ### Severity

windows/security/threat-protection/microsoft-defender-atp/api-portal-mapping.md

@@ -28,7 +28,7 @@ ms.date: 10/16/2017
 
 Understand what data fields are exposed as part of the alerts API and how they map to Microsoft Defender Security Center.
 
-##  Alert API fields and portal mapping
+## Alert API fields and portal mapping
 The following table lists the available fields exposed in the alerts API payload. It shows examples for the populated values and a reference on how data is reflected on the portal.
 
 The ArcSight field column contains the default mapping between the Microsoft Defender ATP fields and the built-in fields in ArcSight. You can download the mapping file from the portal when you enable the SIEM integration feature and you can modify it to match the  needs of your organization. For more information, see [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md).

windows/security/threat-protection/microsoft-defender-atp/configure-mssp-support.md

@@ -108,7 +108,7 @@ It is recommended that groups are created for MSSPs to make authorization access
 As a MSSP customer, you can always remove or modify the permissions granted to the MSSP by updating the Azure AD user groups. 
 
  
-##  Access the Windows Defender Security Center MSSP customer portal
+## Access the Windows Defender Security Center MSSP customer portal
 
 >[!NOTE] 
 >These set of steps are directed towards the MSSP. 

windows/security/threat-protection/microsoft-defender-atp/run-detection-test.md

@@ -17,7 +17,7 @@ ms.collection: M365-security-compliance
 ms.topic: article
 ---
 
-#  Run a detection test on a newly onboarded Microsoft Defender ATP machine 
+# Run a detection test on a newly onboarded Microsoft Defender ATP machine 
 
 **Applies to:**
 - Supported Windows 10 versions

windows/security/threat-protection/microsoft-defender-atp/troubleshoot-overview.md

@@ -17,7 +17,7 @@ ms.collection: M365-security-compliance
 ms.topic: troubleshooting
 ---
 
-#  Troubleshoot Microsoft Defender Advanced Threat Protection 
+# Troubleshoot Microsoft Defender Advanced Threat Protection 
 
 Troubleshoot issues that might arise as you use Microsoft Defender ATP capabilities.
 

windows/security/threat-protection/security-policy-settings/network-security-minimum-session-security-for-ntlm-ssp-based-including-secure-rpc-servers.md

@@ -65,7 +65,7 @@ This section describes features and tools that are available to help you manage
 
 None. Changes to this policy become effective without a device restart when they are saved locally or distributed through Group Policy.
 
-###  Policy dependencies
+### Policy dependencies
 
 The settings for this security policy are dependent on the [Network security: LAN Manager authentication level](network-security-lan-manager-authentication-level.md) setting value.
 

windows/security/threat-protection/wannacrypt-ransomware-worm-targets-out-of-date-systems-wdsi.md

@@ -15,7 +15,7 @@ manager: dansimp
 ms.author: dolmont
 ---
 
-#   WannaCrypt ransomware worm targets out-of-date systems
+# WannaCrypt ransomware worm targets out-of-date systems
 
 
 On May 12, 2017 we detected a new ransomware that spreads like a worm by leveraging vulnerabilities that have been previously fixed. While security updates are automatically applied in most computers, some users and enterprises may delay deployment of patches. Unfortunately, the ransomware, known as [WannaCrypt](https://www.microsoft.com/security/portal/threat/encyclopedia/Entry.aspx?Name=Ransom:Win32/WannaCrypt), appears to have affected computers that have not applied the patch for these vulnerabilities. While the attack is unfolding, we remind users to install [MS17-010](https://technet.microsoft.com/library/security/ms17-010.aspx) if they have not already done so.

windows/whats-new/whats-new-windows-10-version-1809.md

@@ -67,7 +67,7 @@ This is an update to the [BitLocker CSP](https://docs.microsoft.com/windows/clie
 
 This feature will soon be enabled on Olympia Corp as an optional feature.
 
-####  Delivering BitLocker policy to AutoPilot devices during OOBE 
+#### Delivering BitLocker policy to AutoPilot devices during OOBE 
 
 You can choose which encryption algorithm to apply to BitLocker encryption capable devices, rather than automatically having those devices encrypt themselves with the default algorithm. This allows the encryption algorithm (and other BitLocker policies that must be applied prior to encryption), to be delivered before BitLocker encryption begins.