Delete "Follow these setps:"

Lines 54 and 79 to avoid formatting inconsistencies. 
Delete preceding space line 43.

Author: Angela Fleischmann

windows-365/enterprise/known-issues-enterprise.md

@@ -40,7 +40,7 @@ A [resize](resize-cloud-pc.md) of a Cloud PC eliminates all existing [restore](r
 
 ## Windows doesn’t scan for software updates until the first time a user signs in<!--38212344-->
 
- While a Windows PC (physical or Cloud PC) sits idle before the first user signs in, Windows Update doesn’t scan for or install monthly quality patches. This means that the PC might miss important security updates. Without the latest security updates, the device is exposed to security vulnerabilities.
+While a Windows PC (physical or Cloud PC) sits idle before the first user signs in, Windows Update doesn’t scan for or install monthly quality patches. This means that the PC might miss important security updates. Without the latest security updates, the device is exposed to security vulnerabilities.
 
  **Troubleshooting steps**: Make sure that a user signs in to new Cloud PCs as soon as possible.
 
@@ -51,7 +51,7 @@ Windows 365 provisioning failures may occur because both:
 - the Desired State Configuration (DSC) extension isn't signed and
 - the PowerShell Execution policy is set to Allsigned in the Group Policy Object (GPO)
 
-**Troubleshooting steps**: Follow these steps:
+**Troubleshooting steps**: 
 
 1. Did the on-premises network connection (OPNC) fail with the following error: `"An internal error occurred. The virtual machine deployment timed out."`?
 2. If yes, review the related GPO. Is PowerShell Execution set to AllSigned?
@@ -76,7 +76,7 @@ The following device compliance settings report as **Not Compliant** when being
 - **Require BitLocker**
 - **Require Secure Boot to be enabled on the device.**
 
-**Troubleshooting steps**: Follow these steps:
+**Troubleshooting steps**: 
 
 1. [Create a filter for all Cloud PCs](create-filter.md#create-a-filter-for-all-cloud-pcs).
 2. For any existing device compliance policies that both evaluate to a Cloud PC and contain either of the **Not Compliant** settings, use this new filter to exclude Cloud PCs from the policy assignment.