diff --git a/windows/manage/update-compliance-using.md b/windows/manage/update-compliance-using.md
index 00f561c820..c61b17c5fd 100644
--- a/windows/manage/update-compliance-using.md
+++ b/windows/manage/update-compliance-using.md
@@ -69,6 +69,7 @@ Update Status definitions:
 <TR><TD>Not up-to-date<TD>A device does not have the latest quality update for its servicing option.  
 </TABLE>
 
+
 ## Overall Quality Update Status
 
 **Overall Quality Update Status** is the second blade in Update Compliance. It has a donut data tile and lists the breakdown of the Up-to-date status of devices pivoted on OS version. See the following example: 
@@ -102,6 +103,7 @@ See the following definitions:
 <TR><TD>Status Unknown<TD>If a device should be, in some way, progressing toward this security update, but it’s status cannot be inferred, it will count as **Status Unknown**. Devices that are not using Windows Update are the most likely devices to fall into this category.
 </TABLE>
 
+
 ## Overall Feature Update Status
 
 Windows 10 has two main update types: Quality and Feature updates. The third blade in Update Compliance provides the most essential data about your organization’s devices for feature updates. 
@@ -175,6 +177,7 @@ See the following table for a description of last reported states for devices de
 <TR><TD>Blocked<TD>Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed.
 </TABLE>
  
+
 ### Quality Update Detailed Deployment Status
 
 
@@ -200,6 +203,7 @@ The following table provides a list of the detailed deployment states a device c
 <TR><TD>Update completed<TD>The device has completed installing, rebooting, and applying the update. 
 </TABLE>
 
+
 ## Feature Update Perspective
 
 Like Quality Updates, the Feature Update Deployment Status perspective is a breakdown of information most essential to an administrator. This information is viewed by clicking on a given build on the Feature Update Status blade and then navigating to the **Update Deployment Status** pane as displayed previously. In Update Compliance, a perspective is assigned to a query; the query used to generate the perspective can be altered to show other information, if desired.
@@ -242,6 +246,7 @@ This blade breaks down the main states a device can be in through the deployment
 <TR><TD>Blocked<TD>Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed. 
 </TABLE>
  
+
 ### Feature Update Detailed Deployment Status
 
 This blade provides more detail on the deployment process for the update in the Deployment Status blade. This blade is more of a deployment funnel for devices, enabling you to see at a more granular level how devices are progressing along in their deployment. See the following example: