diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 9036db78b8..a5349fbf43 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -51,12 +51,12 @@ For example, a result code of **0xC1900101** with an extend code of **0x4000D**
Note: If only a single code is returned, this can be because a tool is being used that does not capture the extend code, for example the [Windows 10 Upgrade Assistant](https://support.microsoft.com/en-us/kb/3159635).
-### Result and extend codes
+### Extend codes
-The following tables display the phase corresponding to a result code, and operation assoicated with an extend code:
+The following tables display the phase and operation assoicated with an extend code:
-Result codes |
+
Extend code: phase |
Hex | Phase
0 | SP_EXECUTION_UNKNOWN
1 | SP_EXECUTION_DOWNLEVEL
@@ -67,7 +67,7 @@ The following tables display the phase corresponding to a result code, and opera
| | |
-Extend codes |
+
Extend code: operation |
Hex | Operation
@@ -114,7 +114,7 @@ The following tables display the phase corresponding to a result code, and opera
|
-For example: You can use these tables to interpret extend code of 0x**4**00**0D** as a problem during phase 4 with data migration (**4** = SP_EXECUTION_OOBE_BOOT, **0D** = SP_EXECUTION_OP_MIGRATE_DATE).
+For example: A code of 0x**4**00**0D** is a problem during **phase 4** with the **data migration** operation (**4** = SP_EXECUTION_OOBE_BOOT, **0D** = SP_EXECUTION_OP_MIGRATE_DATE).
## Log files
|