updated documentation

Author: naman-msft

scenarios/KernelBootIssuesRepairVM/kernel-related-boot-issues-repairvm.md

@@ -32,7 +32,7 @@ export MY_VM_NAME="myVM89f292"
 
 Make sure the [serial console](serial-console-linux.md) is enabled and functional in the Linux VM.
 
-## <a id="missing-initramfs"></a>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
+## Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
 
 This error occurs because of a recent system update (kernel). It's most commonly seen in RHEL-based distributions.
 You can [identify this issue from the Azure serial console](#identify-kernel-boot-issue). You'll see any of the following error messages:
@@ -64,7 +64,7 @@ You can [identify this issue from the Azure serial console](#identify-kernel-boo
 
 This kind of error indicates that the initramfs file isn't generated, the GRUB configuration file has the initrd entry missing after a patching process, or a GRUB manual misconfiguration.
 
-### <a id="missing-initramfs-alar"></a>Regenerate missing initramfs by using Azure Repair VM ALAR scripts
+### Regenerate missing initramfs by using Azure Repair VM ALAR scripts
 
 1. Create a repair VM by running the following Bash command line with [Azure Cloud Shell](/azure/cloud-shell/overview). For more information, see [Use Azure Linux Auto Repair (ALAR) to fix a Linux VM - initrd option](repair-linux-vm-using-ALAR.md#initrd). This command will regenerate the initrd/initramfs image, regenerate the GRUB configuration file if it has the initrd entry missing, and swap the OS disk
 

scenarios/TroubleshootVMGrubError/troubleshoot-vm-grub-error-repairvm.md

@@ -35,7 +35,7 @@ This article discusses multiple conditions that cause GRUB rescue issues and pro
 
 During the boot process, the boot loader tries to locate the Linux kernel and hand off the boot control. If this handoff can't be performed, the virtual machine (VM) enters a GRUB rescue console. The GRUB rescue console prompt isn't shown in the Azure serial console log, but it can be shown in the [Azure boot diagnostics screenshot](/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view).
 
-## <a id="identify-grub-rescue-issue"></a>Identify GRUB rescue issue
+## Identify GRUB rescue issue
 
 [View a boot diagnostics screenshot](/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) in the VM **Boot diagnostics** page of the Azure portal. This screenshot helps diagnose the GRUB rescue issue and determine if a boot error causes the issue.
 
@@ -47,7 +47,7 @@ Entering rescue mode...
 grub rescue>
 ```
 
-## <a id="offline-troubleshooting"></a>Troubleshoot GRUB rescue issue offline
+## Troubleshoot GRUB rescue issue offline
 
 1. To troubleshoot a GRUB rescue issue, a rescue/repair VM is required. Use [vm repair commands](repair-linux-vm-using-azure-virtual-machine-repair-commands.md) to create a repair VM that has a copy of the affected VM's OS disk attached. Mount the copy of the OS file systems in the repair VM by using [chroot](chroot-environment-linux.md).
 
@@ -78,7 +78,7 @@ 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="offline-troubleshooting"></a> Reinstall GRUB and regenerate GRUB configuration file using Auto Repair (ALAR)
+### Reinstall GRUB and regenerate GRUB configuration file using Auto Repair (ALAR)
 
 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.