diff --git a/windows/deployment/upgrade/windows-error-reporting.md b/windows/deployment/upgrade/windows-error-reporting.md
index 1b021674ca..aa0ab353aa 100644
--- a/windows/deployment/upgrade/windows-error-reporting.md
+++ b/windows/deployment/upgrade/windows-error-reporting.md
@@ -18,15 +18,15 @@ ms.topic: article
- Windows 10
>[!NOTE]
->This is a 300 level topic (moderately advanced).
->See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
+> This is a 300 level topic (moderately advanced).
+> See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
When Windows Setup fails, the result and extend code are recorded as an informational event in the Application log by Windows Error Reporting as event 1001. The event name is **WinSetupDiag02**. You can use Event Viewer to review this event, or you can use Windows PowerShell.
To use Windows PowerShell, type the following commands from an elevated Windows PowerShell prompt:
-```
+```Powershell
$events = Get-WinEvent -FilterHashtable @{LogName="Application";ID="1001";Data="WinSetupDiag02"}
$event = [xml]$events[0].ToXml()
$event.Event.EventData.Data
@@ -40,19 +40,20 @@ To use Event Viewer:
Note: For legacy operating systems, the Event Name was WinSetupDiag01.
Ten parameters are listed in the event:
-
-
P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool) |
P2: Setup Mode (x=default,1=Downlevel,5=Rollback) |
P3: New OS Architecture (x=default,0=X86,9=AMD64) |
P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked) |
P5: Result Error Code (Ex: 0xc1900101) |
P6: Extend Error Code (Ex: 0x20017) |
P7: Source OS build (Ex: 9600) |
P8: Source OS branch (not typically available) |
P9: New OS build (Ex: 16299} |
P10: New OS branch (Ex: rs3_release} |