Update headings for clarity in chroot guide

Author: genlin

support/azure/virtual-machines/linux/chroot-environment-linux.md

@@ -94,7 +94,7 @@ This article describes how to troubleshoot the chroot environment on a rescue vi
 1. Detach the disk from the rescue VM, and then perform a disk swap with the original VM.
 1. Start the original VM, and check its connectivity.
 
-## RHEL/Centos/Oracle 6._x_ && Oracle 8._x_ && RHEL/Centos 7._x_ with RAW partitions
+## RHEL/Centos/Oracle 6._x_ , Oracle 8._x_ and RHEL/Centos 7._x_ with RAW partitions
 
 1. Stop or deallocate the affected VM.
 1. Create a rescue VM image of the same OS version in the same resource group (RSG) and location by using a managed disk.
@@ -158,7 +158,7 @@ This article describes how to troubleshoot the chroot environment on a rescue vi
 1. Detach the disk from the rescue VM, and then perform a disk swap with the original VM.
 1. Start the original VM, and check its connectivity.
 
-## RHEL/Centos 7._x_ & 8._x_ with LVM
+## RHEL/Centos 7._x_ and 8._x_ with LVM
 
 > [!NOTE]
 > If your original VM includes Logical Volume Manager (LVM) on the OS Disk, create the rescue VM by using the image with raw partitions on the OS Disk.
@@ -690,7 +690,7 @@ The following commands are to be run on the recovery (rescue) VM that's temporar
 1. Detach the disk from the rescue VM, and then perform a disk swap with the original VM.
 1. Start the original VM, and check its connectivity.
 
-## SUSE-SLES 12 SP4, SUSE-SLES 12 SP4 For SAP, SUSE-SLES 15 SP1, SUSE-SLES 15 SP1 For SAP
+## SUSE-SLES 12 SP4, SUSE-SLES 12 SP4 For SAP, SUSE-SLES 15 SP1 and SUSE-SLES 15 SP1 For SAP
 
 1. Stop or deallocate the affected VM.
 1. Create a rescue VM image of the same OS version in the same resource group (RSG) and location by using a managed disk.