Acrolinx

Author: ttorble

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

@@ -45,7 +45,7 @@ To scale node pool on Azure portal, follow these steps:
    Endpoint http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&client_id=4e95dcc5-a769-4745-b2d9-
    ```
 
-**Cause**: When you enable pod-managed identity on your AKS cluster, an *AzurePodIdentityException* named *aks-addon-exception* is added to the *kube-system* namespace. An *AzurePodIdentityException* allows pods with certain labels to access the Azure Instance Metadata Service (IMDS) endpoint are are not intercepted by the NMI server.
+**Cause**: When you enable pod-managed identity on your AKS cluster, an *AzurePodIdentityException* named *aks-addon-exception* is added to the *kube-system* namespace. An *AzurePodIdentityException* allows pods with certain labels to access the Azure Instance Metadata Service (IMDS) endpoint are not intercepted by the NMI server.
 
 The extension pods aren't exempt, and require the Microsoft Entra pod identity to be enabled manually.
 
@@ -251,7 +251,7 @@ This error code can appear while you enable AKS backup to store backups in a vau
 
 **Error code**: UserErrorPVSnapshotLimitReached
 
-**Cause**: There are limited number of snapshots for a Persistent Volume that can exist at a point-in-time. For Azure Disk-based Persistent Volumes, the limit is *500 snapshots*. This error appears when snapshots for specific Persistent Volumes aren't taken due to existence of snapshots higher than the supported limits.
+**Cause**: There is a limited number of snapshots for a Persistent Volume that can exist at a point-in-time. For Azure Disk-based Persistent Volumes, the limit is *500 snapshots*. This error appears when snapshots for specific Persistent Volumes aren't taken due to existence of snapshots higher than the supported limits.
 
 **Recommended action**: Update the Backup Policy to reduce the retention duration and wait for Backup Vault to delete the older recovery points.
 

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

@@ -24,7 +24,7 @@ You can perform both *Original-Location Recovery (OLR)* (restoring in the AKS cl
 
 Initialize the variables with required details related to each resource to be used in commands:
 
-- Subscription Id of the Backup Vault
+- Subscription ID of the Backup Vault
 
     ```azurepowershell
     $vaultSubId = "xxxxxxxx-xxxx-xxxx-xxxx"
@@ -46,7 +46,7 @@ Initialize the variables with required details related to each resource to be us
     $restoreLocation = "vaultRegion" #example eastus
     ```
 
-- Id of the target AKS cluster, in case the restore will be performed to an alternate AKS cluster
+- ID of the target AKS cluster, in case the restore will be performed to an alternate AKS cluster
 
     ```azurepowershell
     $targetAKSClusterId = "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx/resourceGroups/targetrg/providers/Microsoft.ContainerService/managedClusters/PSAKSCluster2"