fix: MD006/ul-start-left

Consider starting bulleted lists at the beginning of the line

windows/security/identity-protection/hello-for-business/hello-how-it-works-technology.md

@@ -71,7 +71,7 @@ Azure AD Join is intended for organizations that desire to be cloud-first or clo
 [Join Type](#join-type), [Hybrid Azure AD Joined](#hybrid-azure-ad-joined)
 
 ### More information
- - [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction).
+- [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction).
 
 [Return to Top](hello-how-it-works-technology.md)
 ## Azure AD Registered

windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-base.md

@@ -309,13 +309,13 @@ Sign-in a workstation with access equivalent to a _domain user_.
 ![Intune Windows Hello for Business policy settings](images/aadj/IntuneWHFBPolicy-01.png)
 
 11. Select the appropriate configuration for the following settings.
-   * **Lowercase letters in PIN**
-   * **Uppercase letters in PIN**
-   * **Special characters in PIN**
-   * **PIN expiration (days)**
-   * **Remember PIN history**
-     > [!NOTE]
-     > The Windows Hello for Business PIN is not a symmetric key (a password).  A copy of the current PIN is not stored locally or on a server like in the case of passwords.  Making the PIN as complex and changed frequently as a password increases the likelihood of forgotten PINs.  Additionally, enabling PIN history is the only scenario that requires Windows 10 to store older PIN combinations (protected to the current PIN). Windows Hello for Business combined with a TPM provides anti-hammering functionality that prevents brute force attacks of the user's PIN.  If you are concerned with user-to-user shoulder surfacing, rather that forcing complex PIN that change frequently, consider using the [Multifactor Unlock](feature-multifactor-unlock.md) feature.
+    * **Lowercase letters in PIN**
+    * **Uppercase letters in PIN**
+    * **Special characters in PIN**
+    * **PIN expiration (days)**
+    * **Remember PIN history**
+    > [!NOTE]
+    > The Windows Hello for Business PIN is not a symmetric key (a password).  A copy of the current PIN is not stored locally or on a server like in the case of passwords.  Making the PIN as complex and changed frequently as a password increases the likelihood of forgotten PINs.  Additionally, enabling PIN history is the only scenario that requires Windows 10 to store older PIN combinations (protected to the current PIN). Windows Hello for Business combined with a TPM provides anti-hammering functionality that prevents brute force attacks of the user's PIN.  If you are concerned with user-to-user shoulder surfacing, rather that forcing complex PIN that change frequently, consider using the [Multifactor Unlock](feature-multifactor-unlock.md) feature.
 
 12. Select **Yes** next to **Allow biometric authentication** if you want to allow users to use biometrics (fingerprint and/or facial recognition) to unlock the device.  To further secure the use of biometrics, select **Yes** to **Use enhanced anti-spoofing, when available**.
 13. Select **No** to **Allow phone sign-in**.  This feature has been deprecated.

windows/security/identity-protection/hello-for-business/passwordless-strategy.md

@@ -34,9 +34,9 @@ With Windows Hello for Business and passwords coexisting in your environment, th
 
 ### 3. Transition into a passwordless deployment
 Once the user-visible password surface has been eliminated, your organization can begin to transition those users into a passwordless world. A world where:
-  - the users never type their password
-  - the users never change their password
-  - the users do not know their password
+- the users never type their password
+- the users never change their password
+- the users do not know their password
 
 In this world, the user signs in to Windows 10 using Windows Hello for Business and enjoys single sign-on to Azure and Active Directory resources. If the user is forced to authenticate, their authentication uses Windows Hello for Business.