Update disk-backup-support-matrix.md

Author: rajats22

articles/backup/disk-backup-support-matrix.md

@@ -26,7 +26,7 @@ Azure Disk Backup is available in all public cloud and Sovereign cloud regions.
   >- For Azure Disks belonging to Premium V2 and Ultra Disk SKUs, you can define the backup schedule with *Hourly* frequency of only 12 hours and *Daily* frequency.
 
 >[!Note]
->- If the target disk is attached as a Persistent Volume to an AKS cluster, choose [Azure Backup for AKS](/backup/azure-kubernetes-service-backup-overview.md) over the standalone Disk Backup solution. It enables backing up the disk as snapshots along with the containerized application in a Kubernetes-aware manner, all as a single unit.  Additionally, you get Cross Region Restore and ransomware protection capabilities with AKS Backup.
+>- If the target disk is attached as a Persistent Volume to an AKS cluster, choose [Azure Backup for AKS](azure-kubernetes-service-backup-overview) over the standalone Disk Backup solution. It enables backing up the disk as snapshots along with the containerized application in a Kubernetes-aware manner, all as a single unit.  Additionally, you get Cross Region Restore and ransomware protection capabilities with AKS Backup.
 
 - Azure Disk Backup supports backup of Write Accelerator disk. However, during restore the disk would be restored as a normal disk. Write Accelerated cache can be enabled on the disk after mounting it to a VM.
 
@@ -50,21 +50,21 @@ Azure Disk Backup is available in all public cloud and Sovereign cloud regions.
 
 - ADE encrypted disks can't be protected.
 
-- Disks encrypted with platform-managed keys or customer-managed keys are supported. However, the restore will fail for the restore points of a disk that is encrypted using customer-managed keys (CMK) if the Disk Encryption Set KeyVault key is disabled or deleted.
+- Disks encrypted with platform-managed keys or customer-managed keys are supported. However, the restore fails for the restore points of a disk that is encrypted using customer-managed keys (CMK) if the Disk Encryption Set KeyVault key is disabled or deleted.
 
-- Currently, the Backup policy can't be modified, and the Snapshot Resource group that is assigned to a backup instance when you  configure the backup of a disk can't be changed.
+- The Snapshot Resource group that is assigned to a backup instance when you  configure the backup of a disk can't be changed.
 
 - When you configure backup, the disk selected to be backed up and the snapshot resource group where the snapshots are to be stored must be part of the same subscription. You can't create an incremental snapshot for a particular disk outside of that disk's subscription. Learn more about [incremental snapshots](/azure/virtual-machines/disks-incremental-snapshots#restrictions) for managed disk. For more information on how to choose a snapshot resource group, see  [Configure backup](backup-managed-disks.md#configure-backup).
 
 - For successful backup and restore operations, role assignments are required by the Backup vault’s managed identity. Use only the role definitions provided in the documentation. Use of other roles like owner, contributor, and so on, isn't supported. You may face permission issues, if you start configuring backup or restore operations soon after assigning roles. This is because the role     assignments take a few minutes to take effect.
 
-- Managed disks allow changing the performance tier at deployment or afterwards without changing size of the disk. The Azure Disk Backup solution supports the performance tier changes to the source disk that is being backed up. During restore, the performance tier of the restored disk will be the same as that of the source disk at the time of backup. Follow the documentation [here](/azure/virtual-machines/disks-performance-tiers-portal) to change your disk’s performance tier after restore operation.
+- Managed disks allow changing the performance tier at deployment or afterwards without changing size of the disk. The Azure Disk Backup solution supports the performance tier changes to the source disk that is being backed up. During restore, the performance tier of the restored disk is the same as that of the source disk at the time of backup. Follow the documentation [here](/azure/virtual-machines/disks-performance-tiers-portal) to change your disk’s performance tier after restore operation.
 
 - [Private Links](/azure/virtual-machines/disks-enable-private-links-for-import-export-portal) support for managed disks allows you to restrict the export and import of managed disks so that it only occurs within your Azure virtual network. Azure Disk Backup supports backup of disks that have private endpoints enabled. This doesn't include the backup data or snapshots to be accessible through the private endpoint.
 
 - You can stop backup and retain backup data. This allows you to *retain backup data* forever or as per the backup policy. You can also delete a backup instance, which stops the backup and deletes all backup data. 
 
-- Backup Vault does not support Azure Lighthouse. Thus, cross tenant management experiences cannot be enabled by Lighthouse for Azure Disk Backup and you cannot backup/restore Azure Disks across tenant.
+- Backup Vault doesn't support Azure Lighthouse. Thus, cross tenant management experiences can't be enabled by Lighthouse for Azure Disk Backup and you can't backup/restore Azure Disks across tenant.
 
 - Azure Disk Backup limits are: