updates recommended by Diana Richards

Author: rajats22

articles/backup/aks-backup-faq.yml

@@ -37,7 +37,7 @@ sections:
         answer: | 
           The pods associated with the AKS Backup Extension are deployed on the NodePools of the AKS cluster. To successfully deploy these pods and prevent them from interfering with your application resources, ensure the following:
           - The AKS cluster must have the agent node pool with the `Linux` operating system including both Azure Linux and Ubuntu.
-          - The agent node pool must have VMSS SKUs based on non-ARM64 based architecture.
+          - The agent node pool must have Azure Virtual Machine Scale Sets SKUs based on non-ARM64 based architecture.
           - The agent node pool must have the taint `CriticalAddOnOnly` associated with it. This taint is automatically added to the node pool when the AKS Cluster is created via Portal. It ensures that only critical add-on pods, such as the AKS Backup Extension pods, are scheduled on the node pool. This prevents interference with your application workloads and ensures that backup operations are isolated from other workloads in the cluster. In case the taint isn't present, you can add it manually before installing the AKS Backup Extension.
 
       - question: |
@@ -70,10 +70,10 @@ sections:
           As part of the Backup Extension installation, a User Identity also gets created in the Node Resource Group of the cluster. This identity is used by the AKS Backup Extension to access the Azure resources required for backup operations. The User Identity is assigned `Storage Blob Data Contributor` role over the storage account to enable access for the Extension. Whenever extension is uninstalled from the AKS cluster, the identity also gets deleted.
 
       - question: |
-          Why should Velero shouldn't be used in the cluster alongside of AKS Backup Extension?
+          Why Velero shouldn't be used in the cluster alongside of AKS Backup Extension?
         answer: | 
           Velero is a third-party backup solution for Kubernetes that can conflict with the AKS Backup Extension. It's recommended to use only the AKS Backup Extension for backup operations in a cluster, but not both simultaneously. 
-          AKS Backup Extension also deploys Velero CRDs in the cluster. In case standalone Velero is installed in the AKS cluster along with Backup Extension and the versions used by each installation differ at any point in time can lead to failures due to contract mismatches. Additionally, custom Velero configurations created by the you—such as a VolumeSnapshotClass for Velero CSI-based snapshotting—might interfere with the AKS Backup snapshotting setup. Velero annotations containing `velero.io` applied to various resources in the cluster can also impact the behavior of AKS Backup in unsupported ways.
+          AKS Backup Extension also deploys Velero CRDs in the cluster. In case standalone Velero is installed in the AKS cluster along with Backup Extension and the versions used by each installation differ at any point in time can lead to failures due to contract mismatches. Additionally, custom Velero configurations created by you such as a VolumeSnapshotClass for Velero CSI-based snapshotting—might interfere with the AKS Backup snapshotting setup. Velero annotations containing `velero.io` applied to various resources in the cluster can also impact the behavior of AKS Backup in unsupported ways.
           
       - question: |
            What is a snapshot resource group?

articles/backup/azure-kubernetes-service-backup-overview.md

@@ -454,7 +454,7 @@ You incur charges for:
 
 * **Snapshot fee**: Azure Backup for AKS protects disk- and file-based Persistent Volumes by creating snapshots. For Azure Disks, snapshots are stored in a resource group in your subscription; for Azure Files, they’re stored alongside the file share in your subscription. These snapshots incur standard snapshot storage charges. Because the snapshots aren’t copied to the Backup vault, vault storage charges don’t apply. Although if vault tier is enabled, snapshot charges will still remain applicable. For more information on snapshot pricing, see [Managed Disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/) and [Azure Files pricing](https://azure.microsoft.com/pricing/details/storage/files/).
 
-* **Backup storage fee**: Azure Backup for AKS also supports storing backups in the Vault Tier. You can store backups in the Vault Tier by defining retention rules for vault standard in the backup policy, with one restore point per day eligible to be moved into the vault. Restore points stored in the Vault Tier are charged a separate fee (called a Backup storage fee) according to the total data stored (in gigabytes) and redundancy type enable on the Backup vault.
+* **Backup storage fee**: Azure Backup for AKS also supports storing backups in the Vault Tier. You can store backups in the Vault Tier by defining retention rules for vault standard in the backup policy, with one restore point per day elligible to be moved into the vault. Restore points stored in the Vault Tier are charged a separate fee (called a Backup storage fee) according to the total data stored (in gigabytes) and redundancy type enable on the Backup vault.
 
 ## Related content
 

articles/backup/azure-kubernetes-service-cluster-backup-support-matrix.md

@@ -37,7 +37,7 @@ China East 2, China East 3, China North 2, China North 3, US GOV Arizona, US GOV
 - Azure Backup for AKS supports only CSI driver-based persistent volumes. In-tree volume plugins aren't supported. Ensure that the CSI driver and snapshot are enabled for your cluster. If they're disabled, [enable these settings](/azure/aks/csi-storage-drivers#enable-csi-storage-drivers-on-an-existing-cluster). Also, if your workloads use in-tree volumes, [migrate them to CSI-based volumes to enable backup support](/azure/aks/csi-migrate-in-tree-volumes).
 
 - Azure Backup for AKS supports the following persistent volume types provisioned using the CSI driver:
-  - **Azure Disk-based persistent volumes**: Supported disk SKUs include Standard HDD, Standard SSD, Premium SSD, Premium SSD v2, and Ultra Disks. While snapshot and restore operations are supported across all these SKUs, both operations for Premium SSD v2 and Ultra Disks may take longer. This is because the both processes involves copying data from the volume to a snapshot and back. As a result, the snapshot may appear available and the volume may be mounted before the underlying data copy operation is fully completed, causing a delay before the restored data becomes visible.
+  - **Azure Disk-based persistent volumes**: Supported disk SKUs include Standard HDD, Standard SSD, Premium SSD, Premium SSD v2, and Ultra Disks. While snapshot and restore operations are supported across all these SKUs, both operations for Premium SSD v2 and Ultra Disks may take longer. This is because both processes involves copying data from the volume to a snapshot and back. As a result, the snapshot may appear available and the volume may be mounted before the underlying data copy operation is fully completed, causing a delay before the restored data becomes visible.
   - **Azure Files-based persistent volumes (SMB protocol only)**: Both Standard and Premium file shares are supported. The CSI driver version must be 1.32 or higher. Azure Files using NFS protocol isn't supported. 
 
 - Both dynamically and statically provisioned volumes are supported; however, for static volumes, the *storage class* must be explicitly defined in the **YAML** specification—otherwise, the volume is skipped during backup. 
@@ -60,7 +60,7 @@ China East 2, China East 3, China North 2, China North 3, US GOV Arizona, US GOV
 
 - To enable Azure Backup for AKS using Terraform, use version 3.99.0 or later.
 
-- Azure Backup for AKS requires a backup extension to be installed. This extension requires a storage account and preferably an empty blob container inside it as input while installing. Don't use a blob container with non backup related files.
+- Azure Backup for AKS requires a backup extension to be installed. This extension requires a storage account and preferably an empty blob container inside it as input while installing. Do not use a blob container with non backup related files.
 
 - The storage account specified during the installation of the backup extension must be in the same region as the AKS cluster. Only General-purpose v2 storage accounts are supported; Premium storage accounts aren't supported.
 
@@ -76,7 +76,7 @@ China East 2, China East 3, China North 2, China North 3, US GOV Arizona, US GOV
 
 - Azure Backup for AKS supports [Enhanced Soft Delete](backup-azure-enhanced-soft-delete-about.md) for backups stored in the Vault Tier, providing protection against accidental or malicious deletion. For backups stored in the Operational Tier, the underlying snapshots aren't protected by soft delete and can be permanently deleted.
 
-- Azure Backup for AKS supports [Multi-user authorization (MUA)](multi-user-authorization-concept.md) allowing you to add an another layer of protection to critical operations on your Backup vaults where backups are configured.
+- Azure Backup for AKS supports [Multi-user authorization (MUA)](multi-user-authorization-concept.md) allowing you to add another layer of protection to critical operations on your Backup vaults where backups are configured.
 
 - Azure Backup for AKS supports the [Immutable vault](backup-azure-immutable-vault-concept.md), which helps protect your backup data by preventing operations that could result in the loss of recovery points. However, WORM (Write Once, Read Many) storage for backups isn't currently supported.
 
@@ -130,13 +130,13 @@ China East 2, China East 3, China North 2, China North 3, US GOV Arizona, US GOV
 
 - **Mixed Workloads**: You can back up both Azure Disk and Azure Files volumes in the same backup instance. However, if you need different backup targets (Vault Tier for Disks and Operational Tier for Files), you must create separate backup instances—one for each resource type.
 
-- **CLI Support**: Currently, ability to backup AFS based Persistent Volumes is only available by Azure Portal. Powershell, Azure CLI, Terraform  and other programmatic tools are currently not supported. 
+- **CLI Support**: Currently, ability to backup AFS based Persistent Volumes is only available by Azure portal. Powershell, Azure CLI, Terraform  and other programmatic tools are currently not supported. 
 
 - **File Size limits**: Only Fileshares with ≤ 25,000 files are supported. Larger fileshares may result in failures during restoration.
 
 - **NFS File Support**: Fileshares using SMB protocol are only supported with NFS protocol based Files are skipped while creating a backup.
 
-- **Retention Duration**: Backup policies used for File-based Persistent Volumes support a maximum retention of 30 days. This limit is imposed due the maximum of 200 snapshots that can exist concurrently for an Azure File Share.
+- **Retention Duration**: Backup policies used for File-based Persistent Volumes support a maximum retention of 30 days. This limit is imposed due to the maximum of 200 snapshots that can exist concurrently for an Azure File Share.
 
 
 ### Supported Scenarios and limitations specific for Vaulted backup and Cross Region Restore

articles/backup/azure-kubernetes-service-cluster-manage-backups.md

@@ -133,7 +133,7 @@ To ensure successful backup and restore operations, manually update the resource
 
     ![Screenshot shows how to select Extensions + Applications.](./media/azure-kubernetes-service-cluster-manage-backups/aks-cluster-extension-applications.png)
 
-1. Click on the extension titled "azure-aks-backup".
+1. Select on the extension titled "azure-aks-backup".
 
     ![Screenshot shows how to open Backup extension settings.](./media/azure-kubernetes-service-cluster-manage-backups/aks-cluster-extension-azure-aks-backup.png)
 
@@ -150,7 +150,7 @@ To ensure successful backup and restore operations, manually update the resource
 
 #### Verifying the Changes
 
-After applying the changes, either wait for a scheduled backup to run or initiate an on-demand backup. If you still experience an OOMKilled failure, repeat the steps above and gradually increase memory limits and if it still persists increase `resources.limits.cpu` parameter also.
+Once changes are applied, either wait for a scheduled backup to run or initiate an on-demand backup. If you still experience an OOMKilled failure, repeat the steps above and gradually increase memory limits and if it still persists increase `resources.limits.cpu` parameter also.
 
 ### Monitor a backup operation
 
@@ -253,19 +253,19 @@ AKS Backup now allows you to modify the configuration of an existing backup inst
 
 1. Find your AKS cluster backup instance, open it and click on **Edit backup instance** on top.
 
-    :::image type="content" source="./media/quick-backup-aks/start-edit-backup-instance.png" alt-text="Screenshot showing how to open edit backup instance experience" lightbox="./media/quick-backup-aks/start-edit-backup-instance.png":::
+    :::image type="content" source="./media/quick-backup-aks/start-edit-backup-instance.png" alt-text="Screenshot showing how to open the edit backup instance experience." lightbox="./media/quick-backup-aks/start-edit-backup-instance.png":::
 
-1. On the new screen, options are available to modify the backup policy, managed identity being used by backup vault and the backup instance configuration. Click on **Select** in the **Modify backup instace** section
+1. On the new screen, options are available to modify the backup policy, managed identity being used by backup vault and the backup instance configuration. Select on **Select** in the **Modify backup instance** section.
 
     :::image type="content" source="./media/quick-backup-aks/modify-backup-instance.png" alt-text="Screenshot showing how to initiate editing backup configuration." lightbox="./media/quick-backup-aks/modify-backup-instance.png":::
 
-1. On the right hand side pane, to include Files based volumes to backup, open the dropdown **Select Volume Types** and select the checkbox for **Azure SMB Fileshares**. Additionally select the checkbox **Include Secrets**. You can use this pane, to update any other exisiting backup configurations including labels. Then click on **Select**.
+1. On the right hand side pane, to include Files based volumes to backup, open the dropdown **Select Volume Types** and select the checkbox for **Azure SMB Fileshares**. Additionally select the checkbox **Include Secrets**. You can use this pane, to update any other existing backup configurations including labels. Then click on **Select**.
 
     :::image type="content" source="./media/quick-backup-aks/select-backup-instance.png" alt-text="Screenshot showing how to select resources including Azure Files volumes." lightbox="./media/quick-backup-aks/select-backup-instance.png":::
 
 1. After updating the backup configuration, click **Validate** to ensure all prerequisites for using Azure Files are met. If required roles are missing for the Backup vault identity, a role assignment error will appear. If you have the necessary permissions on the relevant resources, you can resolve this by clicking **Grant Permissions**.
 
-1. Click on **Apply** to finish off the modification of backup instance configuration. 
+1. Select on **Apply** to finish off the modification of backup instance configuration. 
 
 
 #### Stop Protection and Retain Data

articles/backup/azure-kubernetes-service-cluster-restore.md

@@ -1,5 +1,5 @@
 ---
-title: Restore Azure Kubernetes Service (AKS) using Azure Backup
+title: Restore Azure Kubernetes Service (AKS) using Azure Backup.
 description: This article explains how to restore backed-up Azure Kubernetes Service (AKS) using Azure Backup.
 ms.topic: how-to
 ms.service: azure-backup

articles/backup/media/quick-backup-aks/modify-backup-instance.png

@@ -78,7 +78,7 @@ If you haven't already installed the Backup extension, follow these steps:
 1. Select **Create** and wait for the extension installation to complete.
 
 > [!NOTE]
-> If you already have the Backup extension installed, verify it's version v0.0.03004.544 or later. If needed, enable auto-upgrade to update to the latest version.
+> If you already have the Backup extension installed, verify its version v0.0.03004.544 or later. If needed, enable auto-upgrade to update to the latest version.
 
 ### Configure backup for AKS cluster with Azure Files
 
@@ -108,7 +108,7 @@ If you haven't already installed the Backup extension, follow these steps:
     - **Persistent Volumes**: Select **Azure Files** to back up Azure Files-based volumes.
     - **Secrets**: Enable **Backup Secrets** if you're using Kubernetes secrets to store storage account keys (required for restore operations).
 
-    :::image type="content" source="./media/quick-backup-aks/resources-to-backup.png" alt-text="Screenshot showing how to select resources including Azure Files volumes." lightbox="./media/quick-backup-aks/resources-to-backup-afs.png":::
+    :::image type="content" source="./media/quick-backup-aks/resources-to-backup.png" alt-text="Screenshot showing how to select resources including Azure Files volumes." lightbox="./media/quick-backup-aks/resources-to-backup-azure-files.png":::
 
 1. For **Snapshot resource group**, select the resource group to store Azure Disk snapshots (required even if you're only backing up Azure Files volumes). Then select **Validate**.
 
@@ -129,9 +129,9 @@ To create an immediate backup:
 1. Track the backup progress in **Backup Jobs**.
 
 1. Once the backup completes, verify the Azure Files snapshot:
-    - Go to the storage account containing your file share.
-    - Navigate to the file share used by your persistent volume.
-    - Select **Snapshots** to view the backup snapshot created by Azure Backup.
+    1. Go to the storage account containing your file share.
+    1. Navigate to the file share used by your persistent volume.
+    1. Select **Snapshots** to view the backup snapshot created by Azure Backup.
 
 ### Verify backup configuration
 
@@ -157,7 +157,7 @@ This section explains how you can modify an existing backup instance and start b
 
 1. Find your AKS cluster backup instance, open it and click on **Edit backup instance** on top.
 
-    :::image type="content" source="./media/quick-backup-aks/start-edit-backup-instance.png" alt-text="Screenshot showing how to open edit backup instance experience" lightbox="./media/quick-backup-aks/start-edit-backup-instance.png":::
+    :::image type="content" source="./media/quick-backup-aks/start-edit-backup-instance.png" alt-text="Screenshot showing how to open edit backup instance experience." lightbox="./media/quick-backup-aks/start-edit-backup-instance.png":::
 
 1. On the new screen, options are available to modify the backup policy, managed identity being used by backup vault and the backup instance configuration. Click on **Select** in the **Modify backup instance** section