Skip to content

Commit 3ab0569

Browse files
committed
final acrolinx tweaks
1 parent 7e1db41 commit 3ab0569

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The following misconfigurations cause most issues with data encryption that use
2929
- You don't have permissions to access the key vault or the key doesn't exist:
3030
- The key expired or was accidentally deleted or disabled.
3131
- The managed identity of the Azure Database for MySQL instance was accidentally deleted.
32-
- Insufficient key permissions are granted to the managed identity of Azure Database for MySQL instance. For example, the permissions don't include Get, Wrap, and Unwrap.
32+
- The managed identity of the Azure Database for MySQL instance has insufficient key permissions. For example, the permissions don't include Get, Wrap, and Unwrap.
3333
- The managed identity permissions to the Azure Database for MySQL instance were revoked or deleted.
3434

3535
## Identify and resolve common errors

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 02/13/2020
1010

1111
# Troubleshoot data encryption in Azure Database for PostgreSQL - Single Server
1212

13-
This article describes how to identify and resolve common issues that can occur in the single-server deployment of Azure Database for PostgreSQL when configured with data encryption using a customer-managed key.
13+
This article helps you identify and resolve common issues that can occur in the single-server deployment of Azure Database for PostgreSQL when configured with data encryption using a customer-managed key.
1414

1515
## Introduction
1616

@@ -29,7 +29,7 @@ The following misconfigurations cause most issues with data encryption that use
2929
- You don't have permissions to access the key vault or the key doesn't exist:
3030
- The key expired or was accidentally deleted or disabled.
3131
- The managed identity of the Azure Database for PostgreSQL instance was accidentally deleted.
32-
- Insufficient key permissions are granted to the managed identity of the Azure Database for PostgreSQL instance. For example, the permissions don't include Get, Wrap, and Unwrap.
32+
- The managed identity of the Azure Database for PostgreSQL instance has insufficient key permissions. For example, the permissions don't include Get, Wrap, and Unwrap.
3333
- The managed identity permissions to the Azure Database for PostgreSQL instance were revoked or deleted.
3434

3535
## Identify and resolve common errors

0 commit comments

Comments
 (0)