diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index ac5d5cb4c9..39bb4cd654 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -245,16 +245,12 @@ A setupact.log or setuperr.log entry includes the following elements:
 
 See the following example:
 
-<P><TABLE BORDER=1>
-<TR><TD style='padding:0in 4pt 0in 4pt'> <span style='font-size:9.0pt'>2016-09-08 09:23:50</TD>
-<TD style='padding:0in 4pt 0in 4pt'><span style='font-size:9.0pt'>Warning</TD>
-<TD style='padding:0in 4pt 0in 4pt'><span style='font-size:9.0pt'>MIG</TD>
-<TD style='padding:0in 4pt 0in 4pt'><span style='font-size:9.0pt'>Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.</TD></TR>
-</TABLE>
+```
+2016-09-08 09:23:50,  Warning          MIG     Could not replace object C:\Users\name\Cookies. Target Object cannot be removed.
+```
 
 ### Analyze log files
 
-
 <P>To analyze Windows Setup log files:
 
 <OL>
@@ -336,13 +332,10 @@ Therefore, Windows Setup failed because it was not able to migrate the corrupt f
 
 <P>This analysis indicates that the Windows upgrade error can be resolved by deleting the C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\[CN] file. Note: In this example, the full, unshortened file name is  C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\be8228fb2d3cb6c6b0ccd9ad51b320b4_a43d512c-69f2-42de-aef9-7a88fabdaa3f. 
 
-
 ## Resolution procedures
 
-
 ### 0xC1900101
 
-
 A frequently observed result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the downlevel phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as:<BR>
 
 - The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp,