From c56a42bbe39ad2cd9f84bcbb1060d8d825d227cb Mon Sep 17 00:00:00 2001
From: Greg Lindsay <greglin@microsoft.com>
Date: Thu, 1 Aug 2019 14:23:40 -0700
Subject: [PATCH] editing

---
 windows/deployment/windows-autopilot/autopilot-mbr.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/windows/deployment/windows-autopilot/autopilot-mbr.md b/windows/deployment/windows-autopilot/autopilot-mbr.md
index a5e15df930..3092a04346 100644
--- a/windows/deployment/windows-autopilot/autopilot-mbr.md
+++ b/windows/deployment/windows-autopilot/autopilot-mbr.md
@@ -208,8 +208,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>
+- Supported = **Yes**: the device can be reenabled for Autopilot
+- Supported = **No**: the device cannot be reenabled for Autopilot
+
 <table border="1">
-<th>Scenario<th>Supportability:<br>Yes = can be reenabled for Autopilot<br>No = cannot be reenabled for Autopilot<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