Updating the existing content for Data encryption

Author: kummanish

articles/mysql/concepts-data-encryption-mysql.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Database for MySQL Data Encryption with customer-managed key
-description: Azure Database for MySQL data encryption with customer-managed key enables you to Bring Your Own Key (BYOK) for data protection at rest, and allows organizations to implement separation of duties in the management of keys and data.
+description: Azure Database for MySQL ata encryption with customer-managed key enables you to Bring Your Own Key (BYOK) for data protection at rest, and allows organizations to implement separation of duties in the management of keys and data.
 author: kummanish
 ms.author: manishku
 ms.service: mysql
@@ -36,7 +36,7 @@ Data encryption for Azure Database for MySQL provides the following benefits:
 
 **Key Encryption Key (KEK)** - An encryption key used to encrypt the data encryption Keys. Use of a Key Encryption Key that never leaves Key Vault, allows the data encryption keys themselves to be encrypted and controlled. The entity that has access to the KEK may be different than the entity that requires the DEK. Since the KEK is required to decrypt the DEKs, the KEK is effectively a single point by which DEKs can be effectively deleted by deletion of the KEK.
 
-The Data encryption Key (DEK), encrypted with the Key Encryption Keys, are stored separately and only an entity with access to the Key Encryption Key can decrypt these data encryption Keys. For more information, see [security in encryption at rest](../security/fundamentals/encryption-atrest.md).
+The Data encryption Keys (DEK), encrypted with the Key Encryption Keys, are stored separately and only an entity with access to the Key Encryption Key can decrypt these data encryption Keys. For more information, see [security in encryption at rest](../security/fundamentals/encryption-atrest.md).
 
 ## How data encryption with customer-managed key works
 

articles/postgresql/concepts-data-encryption-postgresql.md

@@ -36,7 +36,7 @@ Data encryption for Azure Database for PostgreSQL Single server provides the fol
 
 **Key Encryption Key (KEK)** - An encryption key used to encrypt the data encryption Keys. Use of a Key Encryption Key that never leaves Key Vault, allows the data encryption keys themselves to be encrypted and controlled. The entity that has access to the KEK may be different than the entity that requires the DEK. Since the KEK is required to decrypt the DEKs, the KEK is effectively a single point by which DEKs can be effectively deleted by deletion of the KEK.
 
-The Data Encryption Key (DEK), encrypted with the Key Encryption Keys, are stored separately and only an entity with access to the Key Encryption Key can decrypt these data encryption Keys. For more information, see [security in encryption at rest](../security/fundamentals/encryption-atrest.md).
+The Data Encryption Keys (DEK), encrypted with the Key Encryption Keys, are stored separately and only an entity with access to the Key Encryption Key can decrypt these data encryption Keys. For more information, see [security in encryption at rest](../security/fundamentals/encryption-atrest.md).
 
 ## How data encryption with customer-managed key works