Merge pull request #125302 from ArieHein/Spelling-Wave-50

Spelling Fixes

Author: Court72

articles/backup/backup-azure-afs-automation.md

@@ -197,7 +197,7 @@ To create a backup policy that configures multiple backups a day, follow these s
    $schPol.ScheduleRunTimeZone=$timeZone.Id
    ```
 
-   To reate a policy with daily schedule, run the following cmdlet:
+   To create a policy with daily schedule, run the following cmdlet:
 
    ```azurepowershell
    $UtcTime = Get-Date -Date "2019-03-20 01:30:00Z"

articles/backup/backup-azure-monitoring-alerts.md

@@ -200,7 +200,7 @@ The following example helps you to enable built-in Azure Monitor alerts for job
 az backup vault backup-properties set \
 	--name testVault \
 	--resource-group testRG \
-    --clasic-alerts  Disable \
+    --classic-alerts  Disable \
     --alerts-for-job-failures Enable
 ```
 

articles/backup/backup-azure-reports-data-model.md

@@ -94,7 +94,7 @@ This table provides information about core backup entities, such as vaults and b
 This table provides details about alert related fields.
 
 > [!NOTE]
-> AddonAzureBackupAlerts 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 this event AddonAzureBackupAlerts 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.
+> AddonAzureBackupAlerts 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 this event AddonAzureBackupAlerts 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.
 
 | **Field**                      | **Data Type** | **Applicable Resource Types** | **Description**                                              |
 | ----------------------------- | -------------  | ------------------------------ | ------------------------------ |
@@ -187,7 +187,7 @@ This table provides details about job-related fields.
 | VaultUniqueId                  | Text          | Recovery Services vault, Backup vault | Unique identifier of the protected vault associated with the job |
 | SourceSystem                   | Text          | Recovery Services vault, Backup vault | Source system of the current data - Azure                    |
 | DatasourceSetFriendlyName      | Text          | Backup vault | Friendly name of the datasource being backed up                    |
-| DatasouceSetResourceId         | Text          | Backup vault | Azure Resource Manager (ARM) ID of the parent resource of the datasource (wherever applicable). For example, for an Azure PostgreSQL database, this field will contain the ARM ID of the PostgreSQL server                    |
+| DatasourceSetResourceId         | Text          | Backup vault | Azure Resource Manager (ARM) ID of the parent resource of the datasource (wherever applicable). For example, for an Azure PostgreSQL database, this field will contain the ARM ID of the PostgreSQL server                    |
 | DatasourceSetType              | Text          | Backup vault | Type of the datasource being backed up, for example, Microsoft.DBforPostgreSQL/servers/databases                    |
 | DatasourceResourceId           | Text          | Backup vault | Azure Resource Manager (ARM) ID of the datasource being backed up                    |
 | DatasourceType                 | Text          | Backup vault | Type of the datasource being backed up, for example, Microsoft.DBforPostgreSQL/servers/databases                    |

articles/backup/backup-azure-vms-troubleshoot.md

@@ -435,33 +435,33 @@ To resolve this issue:
 >- With a different name than the original one, **or**
 >- In a different resource group with the same name.
 
-#### UserErrorCrossSubscriptionRestoreNotSuppportedForOLR  
+#### UserErrorCrossSubscriptionRestoreNotSupportedForOLR  
 
-**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForOLR 
+**Error code**: UserErrorCrossSubscriptionRestoreNotSupportedForOLR 
 
 **Error message**: Operation failed as Cross Subscription Restore is not supported for Original Location Recovery.
 
 **Resolution**: Ensure that you [select Create New/ Restore Disk](backup-azure-arm-restore-vms.md#restore-disks) for restore operation.
 
-#### UserErrorCrossSubscriptionRestoreNotSuppportedForUnManagedAzureVM   
+#### UserErrorCrossSubscriptionRestoreNotSupportedForUnManagedAzureVM   
 
-**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForUnManagedAzureVM  
+**Error code**: UserErrorCrossSubscriptionRestoreNotSupportedForUnManagedAzureVM  
 
 **Error message**: Operation failed as Cross Subscription Restore is not supported for Azure VMs with Unmanaged Disks.
 
 **Resolution**: Perform standard restores within the same subscription instead.
 
-#### UserErrorCrossSubscriptionRestoreNotSuppportedForCRR
+#### UserErrorCrossSubscriptionRestoreNotSupportedForCRR
 
-**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForCRR  
+**Error code**: UserErrorCrossSubscriptionRestoreNotSupportedForCRR  
 
 **Error message**: Operation failed as Cross Subscription Restore is not supported along-with Cross Region Restore.
 
 **Resolution**: Use either Cross Subscription Restore' or Cross Region Restore.  
   
-#### UserErrorCrossSubscriptionRestoreNotSuppportedFromSnapshot  
+#### UserErrorCrossSubscriptionRestoreNotSupportedFromSnapshot  
 
-**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedFromSnapshot 
+**Error code**: UserErrorCrossSubscriptionRestoreNotSupportedFromSnapshot 
 
 **Error message**: Operation failed as Cross Subscription Restore is not supported when restoring from a Snapshot recovery point.
 
@@ -483,17 +483,17 @@ To resolve this issue:
 
 **Resolution**:  Ensure the target subscription is registered to the Recovery Services Resource Provider before you attempt a cross subscription restore. Creating a vault in the target Subscription should register the Subscription to Recovery Services Resource Provider.
 
-#### UserErrorCrossSubscriptionRestoreNotSuppportedForEncryptedAzureVM 
+#### UserErrorCrossSubscriptionRestoreNotSupportedForEncryptedAzureVM 
 
-**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForEncryptedAzureVM
+**Error code**: UserErrorCrossSubscriptionRestoreNotSupportedForEncryptedAzureVM
 
 **Error message**: Operation failed as Cross Subscription Restore is not supported for Encrypted Azure VMs.
 
 **Resolution**: Use the same subscription for Restore of Encrypted AzureVMs. 
 
-#### UserErrorCrossSubscriptionRestoreNotSuppportedForTrustedLaunchAzureVM 
+#### UserErrorCrossSubscriptionRestoreNotSupportedForTrustedLaunchAzureVM 
 
-**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForTrustedLaunchAzureVM
+**Error code**: UserErrorCrossSubscriptionRestoreNotSupportedForTrustedLaunchAzureVM
 
 **Error message**: Operation failed as Cross Subscription Restore is not supported for Trusted Launch Azure VMs (TVMs).
 

articles/backup/backup-postgresql-ps.md

@@ -29,7 +29,7 @@ For information on the Azure PostgreSQL databases supported scenarios and limita
 
 Backup vault is a storage entity in Azure that stores the backup data for various new workloads that Azure Backup supports, such as Azure Database for PostgreSQL servers, Azure Disks, and Azure Blobs. Backup vaults help to organize your backup data, while minimizing management overhead. Backup vaults are based on the Azure Resource Manager model of Azure, which provides enhanced capabilities to help secure backup data.
 
-Before you creat a Backup vault, choose the storage redundancy of the data within the vault. Then proceed to create the backup vault with that storage redundancy and the location.
+Before you create a Backup vault, choose the storage redundancy of the data within the vault. Then proceed to create the backup vault with that storage redundancy and the location.
 
 In this article, we'll create a Backup vault *TestBkpVault*, in *westus* region, under the resource group *testBkpVaultRG*. Use the [New-AzDataProtectionBackupVault](/powershell/module/az.dataprotection/new-azdataprotectionbackupvault) command to create a Backup vault. Learn more about [creating a Backup vault](./create-manage-backup-vault.md#create-a-backup-vault).
 
@@ -241,7 +241,7 @@ $keyURI = "https://testkeyvaulteus.vault.azure.net/secrets/ossdbkey"
 
 #### Backup vault
 
-You need to connect the Backup vault to the PostgreSQL server, and then access the database via the keys present in the key vault. So, it requires access to the PostgGreSQL server and the key vault. Access is granted to the Backup vault's MSI.
+You need to connect the Backup vault to the PostgreSQL server, and then access the database via the keys present in the key vault. So, it requires access to the PostgreSQL server and the key vault. Access is granted to the Backup vault's MSI.
 
 [Read about the appropriate permissions](./backup-azure-database-postgresql-overview.md#set-of-permissions-needed-for-azure-postgresql-database-backup) that you should grant to the Backup vault's MSI on the PostgreSQL server and the Azure key vault, where the keys to the database are stored.
 

articles/backup/offline-backup-server-previous-versions.md

@@ -196,7 +196,7 @@ The *AzureOfflineBackupDiskPrep* utility is used to prepare the SATA drives that
 
     When you run the command, the utility requests the selection of the Azure import job that corresponds to the drives that need to be prepared. If only a single import job is associated with the provided staging location, you see a page like this one.
 
-    ![Screenshot shows how to add xthe Azure disk preparation tool input.](./media/offline-backup-dpm-mabs-previous-versions/azure-disk-preparation-tool-drive-input.png) <br/>
+    ![Screenshot shows how to add the Azure disk preparation tool input.](./media/offline-backup-dpm-mabs-previous-versions/azure-disk-preparation-tool-drive-input.png) <br/>
 
 1. Enter the drive letter without the trailing colon for the mounted disk that you want to prepare for transfer to Azure. When prompted, provide confirmation for the formatting of the drive.
 

articles/backup/restore-afs.md

@@ -124,7 +124,7 @@ To perform item-level restore for Azure File share to the original location, fol
 
 ### Restore to an alternate location (item-level recovery)
 
-To perform iten-level restore for Azure File share to an alternate location, follow these steps:
+To perform item-level restore for Azure File share to an alternate location, follow these steps:
 
 1. Select **Alternate Location** as the **Recovery Destination**.
 1. Select the destination storage account where you want to restore the backed-up content from the **Storage Account** drop-down list.

articles/backup/sap-hana-backup-support-matrix.md

@@ -36,7 +36,7 @@ Azure Backup supports the backup of SAP HANA databases to Azure. This article su
 | **Special configurations** |                                                              | SAP HANA + Dynamic Tiering <br>  Cloning through LaMa        |
 | **Compression** | You can enable HANA Native compression via the Backup policy. [See the SAP HANA document](https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/86943e9f8d5343c59577755edff8296b.html). |       |
 | **Multi-streaming backup** | You can increase your streaming backup throughput from *420 MBps* to *1.5 GBps*. [Learn more](#support-for-multistreaming-data-backups). |      |
-| **File System types** | File Systems `ext3` and `xfs` are supported for SAP HANA database instance snapshots backup. | Other File Sustems aren't supported. |
+| **File System types** | File Systems `ext3` and `xfs` are supported for SAP HANA database instance snapshots backup. | Other File Systems aren't supported. |
 
 ------
 

articles/backup/sap-hana-database-with-hana-system-replication-backup.md

@@ -86,11 +86,11 @@ When a failover occurs, the users are replicated to the new primary, but *hdbuse
    >
    >**Diagram shows the creation of the custom backup key using local host/IP.**
    >
-   >    :::image type="content" source="./media/sap-hana-database-with-hana-system-replication-backup/pass-custom-backup-user-key-to-script-as-parameter-architecture.png" alt-text="Disgram explains the flow to pass the custom backup user key to the script as a parameter." lightbox="./media/sap-hana-database-with-hana-system-replication-backup/pass-custom-backup-user-key-to-script-as-parameter-architecture.png":::
+   >    :::image type="content" source="./media/sap-hana-database-with-hana-system-replication-backup/pass-custom-backup-user-key-to-script-as-parameter-architecture.png" alt-text="Diagram explains the flow to pass the custom backup user key to the script as a parameter." lightbox="./media/sap-hana-database-with-hana-system-replication-backup/pass-custom-backup-user-key-to-script-as-parameter-architecture.png":::
    >
    >**Diagram shows the creation of the custom backup key using Virtual IP (Load Balancer Frontend IP/Host).**
    >
-   >    :::image type="content" source="./media/sap-hana-database-with-hana-system-replication-backup/create-custom-backup-key-using-virtual-ip.png" alt-text="Disgram explains the flow to create the custom backup key using Virtual IP." lightbox="./media/sap-hana-database-with-hana-system-replication-backup/create-custom-backup-key-using-virtual-ip.png":::
+   >    :::image type="content" source="./media/sap-hana-database-with-hana-system-replication-backup/create-custom-backup-key-using-virtual-ip.png" alt-text="Diagram explains the flow to create the custom backup key using Virtual IP." lightbox="./media/sap-hana-database-with-hana-system-replication-backup/create-custom-backup-key-using-virtual-ip.png":::
 
 1. Create the same *Custom backup user* (with the same password) and key (in *hdbuserstore*) on both VMs/nodes.
 
@@ -120,7 +120,7 @@ When a failover occurs, the users are replicated to the new primary, but *hdbuse
    - SDC: ./script.sh -sk SYSTEMKEY -bk USRBKP -hn HSRlab001 -p 39015
    ```
 
-1. If your HANA setup uses private endpoints, run the preregistration script with the `-sn` or `--skip-network-checks` parameter. Ater the preregistration script has run successfully, proceed to the next steps.
+1. If your HANA setup uses private endpoints, run the preregistration script with the `-sn` or `--skip-network-checks` parameter. After the preregistration script has run successfully, proceed to the next steps.
 
 1. Run the SAP HANA backup configuration script (preregistration script) in the VMs where HANA is installed as the root user. This script sets up the HANA system for backup. For more information about the script actions, see the [What the preregistration script does](tutorial-backup-sap-hana-db.md#what-the-pre-registration-script-does) section.
 

articles/cloud-services-extended-support/deploy-template.md

@@ -307,7 +307,7 @@ To deploy Cloud Services (extended support) by using a template:
           "type": "string",
           "defaultValue": "[concat(parameters('cloudServiceName'), 'VNet')]",
           "metadata": {
-            "description": "Name of vitual network"
+            "description": "Name of virtual network"
           }
         },
         "publicIPName": {