Adding new troubleshooting document

Author: kummanish

articles/mysql/howto-data-encryption-troubleshoot.md

@@ -29,7 +29,7 @@ No permissions to access the key vault or the key doesn't exist
 
 * The key was accidentally deleted, disabled or the key expired.
 * The Azure Database for MySQL instance-managed identity was accidentally deleted.
-* Permissions granted to the Azure Database for  MySQL server’s managed identity for the keys aren't sufficient (they don't include Get, Wrap, and Unwrap).
+* Permissions granted to the Azure Database for MySQL server managed identity for the keys aren't sufficient (they don't include Get, Wrap, and Unwrap).
 * Permissions for the Azure Database for MySQL server instance-managed identity were revoked.
 
 ## Identify and resolve common errors
@@ -50,4 +50,4 @@ No permissions to access the key vault or the key doesn't exist
 
 
 ## Next steps
-Learn how to [set up data encryption with a customer-managed key for your Azure database for MySQL by using the Azure portal](howto-data-encryption-portal.md).
+[Set up data encryption with a customer-managed key for your Azure database for MySQL by using the Azure portal](howto-data-encryption-portal.md).

articles/postgresql/howto-data-encryption-troubleshoot.md

@@ -1,20 +1,20 @@
 ---
-title: Data encryption for Azure Database for PostgreSQL Single server troubleshooting
-description: Learn how to troubleshoot the data encryption for your Azure Database for PostgreSQL Single server
+title: Data encryption for Azure Database for PostgreSQL - Single server troubleshooting
+description: Learn how to troubleshoot the data encryption for your Azure Database for PostgreSQL - Single server
 author: kummanish
 ms.author: manishku
 ms.service: postgresql
 ms.topic: conceptual
 ms.date: 02/13/2020
 ---
 
-# Troubleshooting data encryption with customer-managed keys in Azure Database for PostgreSQL Single server
-This article describes how to identify and resolve common issues/errors that occur on an Azure Database for PostgreSQL Single server configured with Data Encryption using customer-managed key.
+# Troubleshooting data encryption with customer-managed keys in Azure Database for PostgreSQL - Single server
+This article describes how to identify and resolve common issues/errors that occur on an Azure Database for PostgreSQL - Single server configured with Data Encryption using customer-managed key.
 
 ## Introduction
 When data encryption is configured to use a customer-managed key in Azure Key Vault, continuous access to this key is required for the server to stay available. If the server loses access to the customer-managed key in Azure Key Vault, the server will start denying all connections with the appropriate error message and change its state to ***Inaccessible*** in the Azure portal.
 
-If an inaccessible Azure Database for PostgreSQL Single server is no longer needed, it can be deleted immediately to stop incurring costs. All other actions on the server are not permitted until access to the Azure key vault has been restored and the server is back available. Changing the data encryption option from ‘Yes’(customer-managed) to ‘No’ (service-managed) on an inaccessible the server is also not possible while a server is encrypted with customer-managed. You must revalidate the key manually to make the server back available. This is necessary to protect the data from unauthorized access while permissions to the customer-managed key have been revoked.
+If an inaccessible Azure Database for PostgreSQL - Single server is no longer needed, it can be deleted immediately to stop incurring costs. All other actions on the server are not permitted until access to the Azure key vault has been restored and the server is back available. Changing the data encryption option from ‘Yes’(customer-managed) to ‘No’ (service-managed) on an inaccessible the server is also not possible while a server is encrypted with customer-managed. You must revalidate the key manually to make the server back available. This is necessary to protect the data from unauthorized access while permissions to the customer-managed key have been revoked.
 
 ## Common errors causing server to become inaccessible
 
@@ -28,8 +28,8 @@ The key vault is unavailable or doesn't exist
 No permissions to access the key vault or the key doesn't exist
 
 * The key was accidentally deleted, disabled or the key expired.
-* The Azure Database for PostgreSQL Single server instance-managed identity was accidentally deleted.
-* Permissions granted to the Azure Database for  PostgreSQL Single server’s managed identity for the keys aren't sufficient (they don't include Get, Wrap, and Unwrap).
+* The Azure Database for PostgreSQL - Single server instance-managed identity was accidentally deleted.
+* Permissions granted to the Azure Database for PostgreSQL managed identity for the keys aren't sufficient (they don't include Get, Wrap, and Unwrap).
 * Permissions for the Azure Database for PostgreSQL Single server instance-managed identity were revoked or deleted.
 
 ## Identify and resolve common errors
@@ -50,4 +50,4 @@ No permissions to access the key vault or the key doesn't exist
 
 
 ## Next steps
-Learn how to [set up data encryption with a customer-managed key for your Azure database for PostgreSQL by using the Azure portal](howto-data-encryption-portal.md).
+[Set up data encryption with a customer-managed key for your Azure database for PostgreSQL by using the Azure portal](howto-data-encryption-portal.md).