From c58e7ad0f238ea7810052b187326d5da21a76e2f Mon Sep 17 00:00:00 2001
From: Greg Lindsay <greglin@microsoft.com>
Date: Wed, 5 Oct 2016 17:13:36 -0700
Subject: [PATCH] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index a44acae79c..ac4cb550b8 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -223,15 +223,20 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.
 A setupact.log or setuperr.log entry includes the following elements:
 
 <OL>
-<LI>The date and time. For example: 2016-09-08 09:20:05.
-<LI>The log level: Info, Warning, Error, Fatal Error.
-<LI>The logging component: CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS.
+<LI><B>The date and time</B> - 2016-09-08 09:20:05.
+<LI><B>The log level</B> - Info, Warning, Error, Fatal Error.
+<LI><B>The logging component</B> - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS.
 <UL>
 <LI>The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are particularly useful for troubleshooting Windows Setup errors.
 </UL>
-<LI>The message. For example: Operation completed successfully.
+<LI><B>The message</B> - Operation completed successfully.
 </OL>
 
+An example log entry is shown below:
+<PRE>
+2016-09-08 09:23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
+</PRE>
+
 ### Analyze log files
 
 To analyze Windows Setup log files: