Fixed errors

Author: v-miegge

articles/virtual-machines/troubleshooting/troubleshooting-guide-critical-process-died.md

@@ -37,15 +37,15 @@ Usually, this is due to a critical system process failing during boot. You can r
 
 1. Create and Access a Repair VM.
 2. Fix any OS Corruption.
-3. Recommended: Before you rebuild the VM, enable serial console and memory dump collection.
+3. **Recommended**: Before you rebuild the VM, enable serial console and memory dump collection.
 4. Rebuild the VM.
 
 > [!NOTE]
 > When encountering this boot error, the Guest OS is not operational. You will be troubleshooting in Offline mode to resolve this issue.
 
 ### Create and Access a Repair VM
 
-1. Use steps 1-3 of the VM Repair Commands to prepare a Repair VM.
+1. Use [steps 1-3 of the VM Repair Commands](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands) to prepare a Repair VM.
 2. Using Remote Desktop Connection connect to the Repair VM.
 
 ### Fix any OS Corruption
@@ -55,9 +55,9 @@ Usually, this is due to a critical system process failing during boot. You can r
 
    `sfc /scannow /offbootdir=<BOOT DISK DRIVE>:\ /offwindir=<BROKEN DISK DRIVE>:\windows`
 
-   * Where *<BOOT DISK DRIVE>* is the boot volume of the Repair VM typically C: and <BROKEN DISK DRIVE> will be the drive letter for the attached disk from the broken VM.
+   * Where < BOOT DISK DRIVE > is the boot volume of the Repair VM (typically "C:") and < BROKEN DISK DRIVE > will be the drive letter for the attached disk from the broken VM. Replace the greater than / less than symbols as well as the text contained within them, e.g. "< text here >", with the appropriate letter.
 
-3. Next, use step 5 of the VM Repair Commands to reassemble the VM and see if it boots.
+3. Next, use [step 5 of the VM Repair Commands](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands#repair-process-example) to reassemble the VM and see if it boots.
 4. If the VM is still not booting, then continue to collect the memory dump file.
 
 ### Collect the Memory Dump File
@@ -66,13 +66,13 @@ If the issue persists after running SFC, analysis of a memory dump file will be
 
 ### Attach the OS disk to a new Repair VM
 
-1. Use steps 1-3 of the VM Repair Commands to prepare a new Repair VM.
+1. Use [steps 1-3 of the VM Repair Commands](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands) to prepare a new Repair VM.
 2. Using Remote Desktop Connection connect to the Repair VM.
 
 ### Locate the dump file and submit a support ticket
 
 3. On the repair VM, go to windows folder in the attached OS disk. If the driver letter that is assigned to the attached OS disk is *F*, you need to go to *F:\Windows*.
-4. Locate the *memory.dmp* file, and then submit a support ticket with the memory dump file.
+4. Locate the *memory.dmp* file, and then [submit a support ticket](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade) with the memory dump file.
 
    > [!NOTE]
    > If you cannot find the dump file, complete the below steps to enable memory dump collection and Serial Console, then return to this section and repeat the steps in the task above to collect the memory dump file.
@@ -90,6 +90,8 @@ To enable memory dump collection and Serial Console, run the following script:
 
    `bcdedit /store <VOLUME LETTER WHERE THE BCD FOLDER IS>:\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200`
 
+   Replace any greater than or less than symbols as well as the text within them, e.g. "< text here >".
+
 3. Verify that the free space on the OS disk is as much as the memory size (RAM) on the VM.
 
 If there's not enough space on the OS disk, you should change the location where the memory dump file will be created and refer that to any data disk attached to the VM that has enough free space. To change the location, replace "%SystemRoot%" with the drive letter (for example, "F:") of the data disk in the below commands.

articles/virtual-machines/troubleshooting/troubleshooting-guide-windows-boot-manager-menu.md

@@ -45,7 +45,7 @@ Process Overview:
 4. **Recommended**: Before you rebuild the VM, enable serial console and memory dump collection.
 5. Rebuild the VM.
 
-## Configure for Faster Boot Time using Serial Console
+### Configure for Faster Boot Time using Serial Console
 
 If you have access to serial console, there are two ways you can achieve faster boot times. Either decrease the *displaybootmenu* wait time, or remove the flag altogether.
 
@@ -71,12 +71,12 @@ If you have access to serial console, there are two ways you can achieve faster
       > [!NOTE]
       > If you were unable to use serial console to configure a faster boot time in the steps above, you can instead continue with the following steps. You'll now be troubleshooting in offline mode to resolve this issue.
 
-## Create and Access a Repair VM
+### Create and Access a Repair VM
 
 1. Use [steps 1-3 of the VM Repair Commands](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands) to prepare a Repair VM.
-2 Use Remote Desktop Connection connect to the Repair VM.
+2. Use Remote Desktop Connection connect to the Repair VM.
 
-## Configure for Faster Boot Time on a Repair VM
+### Configure for Faster Boot Time on a Repair VM
 
 1. Open an elevated command prompt.
 2. Enter the following to enable DisplayBootMenu:
@@ -89,6 +89,8 @@ If you have access to serial console, there are two ways you can achieve faster
 
    `bcdedit /store <VOLUME LETTER OF EFI SYSTEM PARTITION>:EFI\Microsoft\boot\bcd /set {bootmgr} displaybootmenu yes`
 
+   Replace any greater than or less than symbols as well as the text within them, e.g. "< text here >".
+
 3. Change the timeout value to 5 seconds:
 
    Use this command for **Generation 1 VMs**:
@@ -99,6 +101,8 @@ If you have access to serial console, there are two ways you can achieve faster
 
    `bcdedit /store <VOLUME LETTER OF EFI SYSTEM PARTITION>:EFI\Microsoft\boot\bcd /set {bootmgr} timeout 5`
 
+   Replace any greater than or less than symbols as well as the text within them, e.g. "< text here >".
+
 ### Recommended: Before you rebuild the VM, enable serial console and memory dump collection
 
 To enable memory dump collection and Serial Console, run the following script:
@@ -112,6 +116,8 @@ To enable memory dump collection and Serial Console, run the following script:
 
    `bcdedit /store <VOLUME LETTER WHERE THE BCD FOLDER IS>:\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200`
 
+   Replace any greater than or less than symbols as well as the text within them, e.g. "< text here >".
+
 3. Verify that the free space on the OS disk is as much as the memory size (RAM) on the VM.
 
    If there's not enough space on the OS disk, you should change the location where the memory dump file will be created and refer that to any data disk attached to the VM that has enough free space. To change the location, replace "%SystemRoot%" with the drive letter (for example, "F:") of the data disk in the below commands.