Merge pull request #126125 from changeworld/patch-176

Fix typo

Author: Court72

articles/backup/backup-postgresql-ps.md

@@ -231,7 +231,7 @@ Fetch the Azure Resource Manager ID (ARM ID) of PostgreSQL to be protected. This
 $ossId = "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx/resourcegroups/ossrg/providers/Microsoft.DBforPostgreSQL/servers/archive-postgresql-ccy/databases/empdb11"
 ```
 
-#### Azure key vault
+#### Azure Key Vault
 
 Azure Backup service doesn't store the username and password to connect to the PostgreSQL database. Instead, the backup admin seeds the *keys* into the key vault, and then the backup service will access the key vault, read the keys, and access the database. Note the secret identifier of the relevant key.
 
@@ -243,7 +243,7 @@ $keyURI = "https://testkeyvaulteus.vault.azure.net/secrets/ossdbkey"
 
 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.
+[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 Azure Key Vault, where the keys to the database are stored.
 
 ### Prepare the request