From f904af10fcdf9d5c4aa132ea1c77afc39da0f97b Mon Sep 17 00:00:00 2001
From: Greg Lindsay <greglin@microsoft.com>
Date: Fri, 2 Aug 2019 13:19:13 -0700
Subject: [PATCH] tweak

---
 windows/deployment/windows-autopilot/autopilot-mbr.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/deployment/windows-autopilot/autopilot-mbr.md b/windows/deployment/windows-autopilot/autopilot-mbr.md
index cafb23c91d..d83600279e 100644
--- a/windows/deployment/windows-autopilot/autopilot-mbr.md
+++ b/windows/deployment/windows-autopilot/autopilot-mbr.md
@@ -212,12 +212,12 @@ NOTES ON TEST RESULTS:
 - In the cases where a repair facility does not have the ability to write device info into the BIOS of the repaired device, new processes need to be created to successfully enable Autopilot.
 - Repaired device should have the Product Key (DPK) preinjected in the BIOS before capturing the new 4K HH (device ID)
 
-See the following table:<br>
+In the following table:<br>
 - Supported = **Yes**: the device can be reenabled for Autopilot
 - Supported = **No**: the device cannot be reenabled for Autopilot
 
 <table border="1">
-<th>Scenario<th>Supported*<th>Microsoft Recommendation
+<th>Scenario<th>Supported<th>Microsoft Recommendation
 <tr><td>Motherboard Replacement (MBR) in general<td>Yes<td>The recommended course of action for MBR scenarios is:
 
 1. Autopilot device is deregistered from the Autopilot program