Merge pull request #125018 from ArieHein/Spelling-Wave-13

Spelling Fixes - Wave 13

Author: v-dirichards

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

@@ -72,7 +72,7 @@ Azure Backup for AKS currently supports the following two options when doing a r
 2. **Patch**: This option allows the patching mutable variable in the backed-up resource on the resource in the target cluster. If you want to update the number of replicas in the target cluster, you can opt for patching as an operation. 
 
 >[!Note]
->AKS backup currently doesn't delete and recreate resources in the target cluster if they already exist. If you attempt to restore Persistent Volumess in the original location, delete the existing Persistent Volumes, and then do the restore operation.
+>AKS backup currently doesn't delete and recreate resources in the target cluster if they already exist. If you attempt to restore Persistent Volumes in the original location, delete the existing Persistent Volumes, and then do the restore operation.
 
 ## Use custom hooks for backup and restore
 

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

@@ -66,7 +66,7 @@ You can use [Azure Backup](./backup-overview.md) to help protect Azure Kubernete
 
 - Backup vault doesn't support Azure Lighthouse. Thus, cross tenant management can't be enabled by Lighthouse for Azure Backup for AKS and you cannot backup/restore AKS Clusters across tenant.
 
-- The following namespaces are skipped from Backup Configuration and not cofigured for backups: `kube-system`, `kube-node-lease`, `kube-public`.
+- The following namespaces are skipped from Backup Configuration and not configured for backups: `kube-system`, `kube-node-lease`, `kube-public`.
 
 - Here are the AKS backup limits:
 

articles/backup/azure-kubernetes-service-cluster-backup-using-cli.md

@@ -254,7 +254,7 @@ The configuration of backup is performed in two steps:
     "snapshot_volumes": true
    }
    ```
-The following namespaces are skipped from backup configuration and not cofigured for backups: kube-system, kube-node-lease, kube-public.
+The following namespaces are skipped from backup configuration and not configured for backups: kube-system, kube-node-lease, kube-public.
 
 2. Prepare the relevant request using the relevant vault, policy, AKS cluster, backup configuration, and snapshot resource group using the `az dataprotection backup-instance initialize` command.
 

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

@@ -161,7 +161,7 @@ With the created Backup vault and backup policy, and the AKS cluster in *ready-t
 
 The configuration of backup is performed in two steps:
 
-1. Prepare backup configuration to define which cluster resources are to be backed up using the `New-AzDataProtectionBackupConfigurationClientObject` cmdlet. In the following example, the configuration is defined as all cluster resources under current, and future namespaces will be backed up  with the label as `key-value pair x=y`. Also, all the cluster scoped resources and persistent volumes are backed up. The following namespaces are skipped from backup configuration and not cofigured for backups: kube-system, kube-node-lease, kube-public.
+1. Prepare backup configuration to define which cluster resources are to be backed up using the `New-AzDataProtectionBackupConfigurationClientObject` cmdlet. In the following example, the configuration is defined as all cluster resources under current, and future namespaces will be backed up  with the label as `key-value pair x=y`. Also, all the cluster scoped resources and persistent volumes are backed up. The following namespaces are skipped from backup configuration and not configured for backups: kube-system, kube-node-lease, kube-public.
 
    ```azurepowershell
    $backupConfig = New-AzDataProtectionBackupConfigurationClientObject -SnapshotVolume $true -IncludeClusterScopeResource $true -DatasourceType AzureKubernetesService -LabelSelector "env=prod"

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

@@ -121,7 +121,7 @@ Azure Backup for AKS currently supports the following two options when doing a r
 - **Patch**: This option allows the patching mutable variable in the backed-up resource on the resource in the target cluster. If you want to update the number of replicas in the target cluster, you can opt for patching as an operation. 
 
 >[!Note]
->AKS backup currently doesn't delete and recreate resources in the target cluster if they already exist. If you attempt to restore Persistent Volumess in the original location, delete the existing Persistent Volumes, and then do the restore operation.
+>AKS backup currently doesn't delete and recreate resources in the target cluster if they already exist. If you attempt to restore Persistent Volumes in the original location, delete the existing Persistent Volumes, and then do the restore operation.
 
 ## Restore in secondary region
 

articles/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.md

@@ -157,7 +157,7 @@ When you can recover a backed up virtual machine, you use the Recovery wizard to
 1. In the MABS Administrator console, type the name of the VM, or expand the list of protected items, navigate to **All Protected HyperV Data**, and select the VM you want to recover.
 
    >[!Note]
-   >- All the Clustered HA VMs are recoverd by selecting these Virtual machines under the cluster.
+   >- All the Clustered HA VMs are recovered by selecting these Virtual machines under the cluster.
    >- Both Hyper-V and Clustered VMs are restored as Hyper-V Virtual Machines.
 
 2. In the **Recovery points for** pane, on the calendar, select any date to see the recovery points available. Then in the **Path** pane, select the recovery point you want to use in the Recovery wizard.

articles/backup/backup-azure-about-mars.md

@@ -61,7 +61,7 @@ To back up files, folders, and the volume or system state from an on-premises co
 
 The following diagram shows the backup flow:
 
-![Diagra shows the bacup flow of Azure Backup agent.](./media/backup-try-azure-backup-in-10-mins/backup-process.png)
+![Diagram shows the backup flow of Azure Backup agent.](./media/backup-try-azure-backup-in-10-mins/backup-process.png)
 
 ### Additional information
 

articles/backup/backup-azure-dataprotection-use-rest-api-restore-disks.md

@@ -417,7 +417,7 @@ Use the *GET* command to track the _JobId_ present in the [trigger restore respo
     "errorDetails": null,
     "extendedInfo": {
       "backupInstanceState": null,
-      "dataTransferedInBytes": null,
+      "dataTransferredInBytes": null,
       "targetRecoverPoint": null,
       "sourceRecoverPoint": {
         "recoveryPointID": "3a512290ec6b43d6b9a644869f4a3b38",

articles/backup/backup-azure-diagnostic-events.md

@@ -69,7 +69,7 @@ To send your vault diagnostics data to Log Analytics:
 After data flows into the Log Analytics workspace, dedicated tables for each of these events are created in your workspace. You can query any of these tables directly. You can also perform joins or unions between these tables if necessary.
 
 > [!IMPORTANT]
-> *Addon Azure Backup Alerts* refers to the alerts being generated by the classic alerts solution. As classic alerts solution is on deprecation path in favour of Azure Monitor-based alers, we recommend you not to select the event *Addon Azure Backup Alerts* when configuring diagnostics settings. To send the fired Azure Monitor-based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
+> *Addon Azure Backup Alerts* refers to the alerts being generated by the classic alerts solution. As classic alerts solution is on deprecation path in favour of Azure Monitor-based alerts, we recommend you not to select the event *Addon Azure Backup Alerts* when configuring diagnostics settings. To send the fired Azure Monitor-based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
 >
 > For Recovery Services vault, the six events- *Core Azure Backup*, *Addon Azure Backup Jobs*, *Addon Azure Backup Policy*, *Addon Azure Backup Storage*, *Azure Backup Operations*, and *Addon Azure Backup Protected Instance* are supported *only* in the *resource-specific* mode for Recovery Services in Backup reports. If you try to send data for these events in the Azure diagnostics mode, no data will appear in Backup reports.
 >
@@ -88,7 +88,7 @@ Currently, we continue to support the *Azure Backup Reporting Data* event for Re
 *The legacy event in Azure diagnostics mode will eventually be deprecated. Choosing the new events can help you avoid complex migrations later*. Our Log Analytics-based [reporting solution](./configure-reports.md) will also cease support for data from the legacy event. 
 
 > [!NOTE]
-> For Backup vaults, all diagnostics events are sent to the resource-specific tables only; so, you don't need to do any migration for Backup vaults. The preceeding section is specific to Recovery services vaults.
+> For Backup vaults, all diagnostics events are sent to the resource-specific tables only; so, you don't need to do any migration for Backup vaults. The preceding section is specific to Recovery services vaults.
 
 ### Steps to move to new diagnostics settings for a Log Analytics workspace
 

articles/backup/backup-azure-files.md

@@ -207,7 +207,7 @@ To run an on-demand backup, follow these steps:
 
 # [File share blade](#tab/file-share-pane)
 
-To run an on-demamd backup, follow these steps:
+To run an on-demand backup, follow these steps:
 
 1. Open the file share’s **Overview** blade for which you want to take an on-demand backup.