Merge pull request #167156 from v-amallick/July-28-2021-Blob

blobs and CMK minor changes

Author: PRMerger12

articles/backup/backup-overview.md

@@ -20,7 +20,7 @@ The Azure Backup service provides simple, secure, and cost-effective solutions t
 - **SQL Server in Azure VMs** -  [Back up SQL Server databases running on Azure VMs](backup-azure-sql-database.md)
 - **SAP HANA databases in Azure VMs** - [Backup SAP HANA databases running on Azure VMs](backup-azure-sap-hana-database.md)
 - **Azure Database for PostgreSQL servers (preview)** -  [Back up Azure PostgreSQL databases and retain the backups for up to 10 years](backup-azure-database-postgresql.md)
-- **Azure Blobs (preview)** - [Overview of operational backup for Azure Blobs (in preview)](blob-backup-overview.md)
+- **Azure Blobs** - [Overview of operational backup for Azure Blobs](blob-backup-overview.md)
 
 ![Azure Backup Overview](./media/backup-overview/azure-backup-overview.png)
 

articles/backup/encryption-at-rest-with-cmk.md

@@ -281,11 +281,11 @@ Before proceeding to configure protection, we strongly recommend you ensure the
 >[!IMPORTANT]
 > Before proceeding to configure protection, you must have **successfully** completed the following steps:
 >
->1. Created your Backup vault
+>1. Created your Recovery Services vault
 >1. Enabled the Recovery Services vault's system-assigned managed identity or assigned a user-assigned managed identity to the vault
->1. Assigned permissions to your Backup Vault (or the user-assigned managed identity) to access encryption keys from your Key Vault
+>1. Assigned permissions to your Recovery Services vault (or the user-assigned managed identity) to access encryption keys from your Key Vault
 >1. Enabled soft delete and purge protection for your Key Vault
->1. Assigned a valid encryption key for your Backup vault
+>1. Assigned a valid encryption key for your Recovery Services vault
 >
 >If all the above steps have been confirmed, only then proceed with configuring backup.