Updates from editor

Author: v-phoebh

support/azure/virtual-machines/linux/troubleshoot-vm-boot-error.md

@@ -61,18 +61,18 @@ grub rescue>
 
     3. Check whether the VM can start by taking a look at the Azure serial console or by trying to connect to the VM.
 
-4. If the entire /boot partition or other important contents are missing and can't be recovered, we recommend restoring the VM from a backup. For more information, see [How to restore Azure VM data in Azure portal](/azure/backup/backup-azure-arm-restore-vms).
+4. If the entire `/boot` partition or other important contents are missing and can't be recovered, we recommend restoring the VM from a backup. For more information, see [How to restore Azure VM data in Azure portal](/azure/backup/backup-azure-arm-restore-vms).
 
 See the following sections for detailed errors, possible causes, and solutions.
 
 > [!NOTE]
 > In the commands mentioned in the following sections, replace `/dev/sdX` with the corresponding Operating System (OS) disk device.
 
-### <a id="reinstall-grub-regenerate-grub-configuration-file-repairvm"></a> Reinstall GRUB and regenerate GRUB configuration file using Azure Linux Auto Repair
+### <a id="reinstall-grub-regenerate-grub-configuration-file-repairvm"></a> Reinstall GRUB and regenerate the GRUB configuration file using Azure Linux Auto Repair
 
 Azure Linux Auto Repair (ALAR) scripts are part of the VM repair extension described in [Use Azure Linux Auto Repair (ALAR) to fix a Linux VM](./repair-linux-vm-using-alar.md). ALAR covers the automation of multiple repair scenarios, including GRUB rescue issues.
 
-The ALAR scripts use the repair extension `repair-button` to fix GRUB issues by specifying `--button-command grubfix` for Generation 1 VMs, or `--button-command efifix` for Generation 2 VMs. This parameter triggers the automated recovery. Implement the following commands to automate the fix of common GRUB errors by reinstalling GRUB and regenerating the corresponding configuration file:
+The ALAR scripts use the repair extension `repair-button` to fix GRUB issues by specifying `--button-command grubfix` for Generation 1 VMs or `--button-command efifix` for Generation 2 VMs. This parameter triggers the automated recovery. Implement the following commands to automate the fix of common GRUB errors by reinstalling GRUB and regenerating the corresponding configuration file:
 
 * **Linux VMs without UEFI (BIOS based - Gen1):**
 
@@ -93,9 +93,9 @@ The ALAR scripts use the repair extension `repair-button` to fix GRUB issues by
 > [!IMPORTANT]
 > Replace the resource group name `$RGNAME` and VM name `$VMNAME` accordingly.
 
-The repair VM script, in conjunction with the ALAR script, temporarily creates a resource group, a repair VM, and a copy of the affected VM's OS disk. It reinstalls GRUB and regenerates the corresponding GRUB configuration file and then it swaps the OS disk of the broken VM with the copied fixed disk. Finally, the `repair-button` script will automatically delete the resource group containing the temporary repair VM.
+The repair VM script, in conjunction with the ALAR script, temporarily creates a resource group, a repair VM, and a copy of the affected VM's OS disk. It reinstalls GRUB, regenerates the corresponding GRUB configuration file, and then swaps the broken VM's OS disk with the copied fixed disk. Finally, the `repair-button` script automatically deletes the resource group containing the temporary repair VM.
 
-### <a id="reinstall-grub-regenerate-grub-configuration-file"></a>Reinstall GRUB and regenerate GRUB configuration file manually
+### <a id="reinstall-grub-regenerate-grub-configuration-file"></a>Reinstall GRUB and regenerate the GRUB configuration file manually
 
 1. Check whether a rescue/repair VM was created. If it wasn't created, follow step 1 in [Troubleshoot GRUB rescue issue offline](#offline-troubleshooting) to create the VM. Mount all the required file systems, including `/` and `/boot` in the rescue/repair VM, and then enter the [chroot](chroot-environment-linux.md) environment.
 
@@ -151,9 +151,9 @@ This error might be associated with one of the following issues:
 
 * GRUB boot loader points to an invalid disk or partition.
 
-  To resolve this issue, [reinstall GRUB and regenerate GRUB configuration file](#reinstall-grub-regenerate-grub-configuration-file).
+  To resolve this issue, [reinstall GRUB and regenerate the GRUB configuration file-manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually).
 
-* OS disk partition table issues caused by human errors.
+* OS disk partition table issues caused by human error.
 
   To resolve such issues, follow the steps in [Error: No such partition](#no-such-partition) to re-create the `/boot` partition if missing or created incorrectly.
 
@@ -179,7 +179,7 @@ To resolve this issue, follow these steps:
 
 2. Inspect the `/boot` file system contents and determine what's missing.
 
-3. If the GRUB configuration file is missing, [reinstall GRUB and regenerate GRUB configuration file](#reinstall-grub-regenerate-grub-configuration-file).
+3. If the GRUB configuration file is missing, [reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually).
 
 4. Verify that the file permissions in the `/boot` file system are OK. You can compare the permissions by using another VM that's running the same Linux version.
 
@@ -193,7 +193,7 @@ The following screenshot shows the error message:
 
 :::image type="content" source="./media/troubleshoot-vm-boot-error/grub-normal-file-not-found.png" alt-text="Screenshot of grub error normal.mod not found.":::
 
-1. Check whether a rescue/repair VM was created. If it wasn't created, follow step 1 in [Troubleshoot GRUB rescue issue offline](#offline-troubleshooting) to create one. Mount all the required file systems, including / and /boot in the rescue/repair VM, and then enter the [chroot](chroot-environment-linux.md) environment.
+1. Check whether a rescue/repair VM was created. If it wasn't created, follow step 1 in [Troubleshoot GRUB rescue issue offline](#offline-troubleshooting) to create one. Mount all the required file systems, including `/` and `/boot` in the rescue/repair VM, and then enter the [chroot](chroot-environment-linux.md) environment.
 
 2. If you're unable to mount the `/boot` file system due to a corruption error, [fix /boot file system corruption](#fix-boot-file-system-corruption).
 
@@ -265,19 +265,19 @@ If the `/boot` partition is missing, re-create it by following these steps:
 
 3. If the partition table has **dos** as the partition table type, [re-create /boot partition in dos systems](#re-create-boot-partition-in-dos-systems). If the partition table has **GPT** as the partition table type, [re-create /boot partition in GPT systems](#re-create-boot-partition-in-gpt-systems).
 
-4. Make sure that the GRUB boot loader is installed by using the proper disk. You can follow the steps in [Reinstall GRUB and regenerate GRUB configuration file](#reinstall-grub-regenerate-grub-configuration-file) to get it installed and configured.
+4. Make sure that the GRUB boot loader is installed by using the proper disk. You can follow the steps in [Reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually) to get it installed and configured.
 
 5. Proceed with step 3 in [Troubleshoot GRUB rescue issue offline](#offline-troubleshooting) to swap the OS disk.
 
 #### <a id="re-create-boot-partition-in-dos-systems"></a>Re-create /boot partition in dos systems
 
-1. Re-create the /boot partition from a rescue/repair VM by using the following command:
+1. Re-create the `/boot` partition from a rescue/repair VM by using the following command:
 
     ```bash
     sudo fdisk /dev/sdX
     ```
 
-    Use the default values in the **First** and **Last** sectors, and **partition type** (83). Make sure the /boot partition table is marked as bootable by using the `a` option in the `fdisk` tool, as shown in the following output:
+    Use the default values in the **First** and **Last** sectors, and **partition type** (83). Make sure the `/boot` partition table is marked as bootable by using the `a` option in the `fdisk` tool, as shown in the following output:
 
     ```output
     sudo fdisk /dev/sdc
@@ -344,7 +344,7 @@ If the `/boot` partition is missing, re-create it by following these steps:
 
 #### <a id="re-create-boot-partition-in-gpt-systems"></a>Re-create /boot partition in GPT systems
 
-1. Re-create the /boot partition by using the following command, from a rescue/repair VM:
+1. Re-create the `/boot` partition from a rescue/repair VM by using the following command:
 
     ```bash
     sudo gdisk /dev/sdX
@@ -402,7 +402,7 @@ If the `/boot` partition is missing, re-create it by following these steps:
     The operation has completed successfully.
     ```
 
-2. Check whether the /boot file system is detected by the system by using the following command:
+2. Check whether the `/boot` file system is detected by the system by using the following command:
 
     ```bash
     sudo blkid /dev/sdX1
@@ -415,7 +415,7 @@ If the `/boot` partition is missing, re-create it by following these steps:
     /dev/sdc1: UUID="<UUID>" BLOCK_SIZE="4096" TYPE="xfs" PARTLABEL="Linux filesystem" PARTUUID="<PARTUUID>"
     ```
 
-3. If the /boot file system isn't visible after you re-create the partition, this means that the /boot data no longer exists. You have to re-create the /boot file system (by using the same UUID that's in the `/etc/fstab` `/boot` entry), and then [restore its contents from a backup](/azure/backup/backup-azure-arm-restore-vms).
+3. If the `/boot` file system isn't visible after you re-create the partition, this means that the `/boot` data no longer exists. You have to re-create the `/boot` file system (by using the same UUID that's in the `/etc/fstab` `/boot` entry), and then [restore its contents from a backup](/azure/backup/backup-azure-arm-restore-vms).
 
 ## <a id="grub_efi_get_secure_boot"></a>Error: symbol 'grub_efi_get_secure_boot' not found
 
@@ -429,7 +429,7 @@ Linux kernel version 4.12.14 (that's used in SLES 12 SP5) doesn't support the [S
 
 To resolve the boot error, follow these steps:  
 
-1. Check whether a rescue/repair VM was created. If it wasn't created, follow step 1 in [Troubleshoot GRUB rescue issue offline](#offline-troubleshooting) to create the VM. Mount all the required file systems, including / and /boot, and then enter the [chroot](chroot-environment-linux.md) environment.
+1. Check whether a rescue/repair VM was created. If it wasn't created, follow step 1 in [Troubleshoot GRUB rescue issue offline](#offline-troubleshooting) to create the VM. Mount all the required file systems, including `/` and `/boot`, and then enter the [chroot](chroot-environment-linux.md) environment.
 
 2. Run the following [YaST](https://yast.opensuse.org) command in the chroot environment:  
 
@@ -453,7 +453,7 @@ This kind of error is triggered in one of the following scenarios:
 
 * The GRUB configuration file is missing.
 * The wrong GRUB configuration is used.
-* The /boot partition or its contents are missing.
+* The `/boot` partition or its contents are missing.
 
 To resolve this error, follow these steps:
 
@@ -467,7 +467,7 @@ To resolve this error, follow these steps:
     * [GRUB access in SUSE SLES](serial-console-grub-single-user-mode.md#grub-access-in-suse-sles)
     * [GRUB access in Oracle Linux](serial-console-grub-single-user-mode.md#grub-access-in-oracle-linux)
 
-3. [Reinstall GRUB and regenerate GRUB configuration file](#reinstall-grub-regenerate-grub-configuration-file).
+3. [Reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually).
 
     > [!NOTE]
     > If the missing file is `/boot/grub/menu.lst`, this error is for older OS versions (RHEL 6.x, Centos 6.x and Ubuntu 14.04). The commands will differ because GRUB version 1 is used in those systems instead. GRUB version 1 isn't covered in this article.