addressed peer-review inputs

Author: AbhishekMallick-MS

articles/backup/backup-azure-database-postgresql-flex-use-rest-api-create-update-policy.md

@@ -2,7 +2,7 @@
 title: Create backup policies for Azure database for PostgreSQL - Flexible server using data protection REST API in Azure Backup
 description: Learn how to create the backup policy to protect Azure PostgreSQL flexible servers using REST API.
 ms.topic: conceptual
-ms.date: 04/30/2024
+ms.date: 05/13/2024
 ms.assetid: 759ee63f-148b-464c-bfc4-c9e640b7da6b
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
@@ -14,7 +14,7 @@ This article describes how to create the backup policy to protect Azure PostgreS
 
 A backup policy governs the retention and schedule of your backups. Azure PostgreSQL flexible servers Backup offers long-term retention and supports a backup per day. 
 
-You can reuse an existing backup policy to configure backup for PostgreSQL flexible servers to a vault, or [create a backup policy for an Azure Recovery Services vault using REST API](/rest/api/dataprotection/backup-policies/create-or-update)
+You can reuse an existing backup policy to configure backup for PostgreSQL flexible servers to a vault, or [create a backup policy for an Azure Recovery Services vault using REST API](/rest/api/dataprotection/backup-policies/create-or-update).
 
 ## Understanding PostgreSQL backup policy
 
@@ -30,7 +30,7 @@ Before you start creating the backup policy, learn about the backup policy objec
     - Default Tagging Criteria (A default 'tag' for all the scheduled backups. This tag links the backups to the retention rule)
   - Default Retention Rule (A rule that will be applied to all backups, by default, on the initial datastore)
 
-This object defines the type of backups that are triggered, the way they are triggered (via a schedule), the tags marked for the backup operation, the path where the backups are stored (a datastore), and the lifecycle of the backup data in a datastore. The default PowerShell object for PostgreSQL - Flexible servers trigger a full backup every week, and stores the backups in the vault, and retains them for three months.
+This object defines the type of backups that are triggered, the way they are triggered (via a schedule), the tags marked for the backup operation, the path where the backups are stored (a datastore), and the lifecycle of the backup data in a datastore. The default PowerShell object for PostgreSQL - Flexible servers triggers a full backup every week, and stores the backups in the vault, and retains them for three months.
 
 ## Create a backup policy
 
@@ -47,7 +47,7 @@ The `{policyName}` and `{vaultName}` are provided in the URI. Additional informa
 
 ## Create the request body
 
-For example, to create a policy for PostgreSQL - Flexible servers backup, the request body needs the following components:
+For example, to create a policy for Azure Database for PostgreSQL - Flexible servers backup, the request body needs the following components:
 
 | Name | Required | Type | Description |
 | --- | --- | --- | --- |
@@ -57,9 +57,9 @@ For the complete list of definitions in the request body, see the [backup policy
 
 ### Example request body
 
-The policy explains:
+The policy says that:
 
-- Scheduled trigger for a weekly backup and choose the starting time (Time + P1W).
+- It's scheduled to triggrr weekly backup and choose the start time (Time + P1W).
 - Datastore is vault store, as the backups are directly transferred to the vault.
 - The backups are retained in the vault for three months (P3M).
 
@@ -131,7 +131,7 @@ The policy explains:
 
 Let's update the above JSON template with one change - Backups on multiple days of the week.
 
-The following example modifies the weekly backup to back up occurring on every Sunday, Wednesday, and Friday of every week. The schedule date array mentions the dates, and dates of the week are taken as days of the week. You also need to specify that these schedules should repeat every week. So, the schedule interval is *1* and the interval type is *Weekly*.
+The following example modifies the weekly backup to back up on every Sunday, Wednesday, and Friday of every week. The schedule date array mentions the dates, and the dates of the week are taken as days of the week. You also need to specify that these schedules should repeat every week. So, the schedule interval is *1* and the interval type is *Weekly*.
 
 **Scheduled trigger**:
 
@@ -151,7 +151,7 @@ The following example modifies the weekly backup to back up occurring on every S
 
 If you want to add another retention rule, then modify the *policy JSON* as follows:
 
-The above JSON has a lifecycle for the initial datastore under the default retention rule. In this scenario, the rule mentions deleting the backup data after three months. You can add a new retention rule that defines a longer retention duration of 6 months for first backups taken at start of every month - let's name this new rule as *Monthly*.
+The above JSON has a lifecycle for the initial datastore under the default retention rule. In this scenario, the rule mentions deleting the backup data after three months. You can add a new retention rule that defines a longer retention duration of 6 months for the first backups taken at the start of every month. Let's name this new rule as *Monthly*.
 
 **Retention lifecycle**:
 
@@ -195,7 +195,7 @@ The above JSON has a lifecycle for the initial datastore under the default reten
 
 ```
 
-Every time you add a retention rule, you need to add a corresponding tag in *Trigger* property of the policy. The following example creates a new tag along with the criteria (the first successful backup of the month) with the exact same name as the corresponding retention rule to be applied.
+Every time you add a retention rule, you need to add a corresponding tag in the *Trigger* property of the policy. The following example creates a new tag along with the criteria (the first successful backup of the month) with the exact same name as the corresponding retention rule to be applied.
 
 In this example, the tag criteria should be named *Monthly*.
 
@@ -324,7 +324,7 @@ For more details about policy creation, see the [PostGreSQL database Backup poli
 
 ### Responses
 
-The backup policy creation or update is a synchronous operation and returns &OK* once the operation is successful.
+The backup policy creation or update is a synchronous operation and returns *OK* once the operation is successful.
 
 | Name | Type | Description |
 | --- | --- | --- |
@@ -440,7 +440,7 @@ Once the operation completes, it returns 200 (OK) with the policy content in the
 
 [Enable protection for Azure Database for PostgreSQL - Flexible server](backup-azure-database-postgresql-flex-use-rest-api.md).
 
-For more information on the Azure Backup REST APIs, see the following articles:
+For more information on Azure Backup REST APIs, see the following articles:
 
 - [Azure Data Protection REST API](/rest/api/dataprotection)
 - [Get started with Azure REST API](/rest/api/azure)

articles/backup/backup-azure-database-postgresql-flex-use-rest-api-restore.md

@@ -2,15 +2,15 @@
 title: Restore Azure Database for PostgreSQL - Flexible servers using in Azure Backup
 description: Learn how to restore Azure Database for PostgreSQL - Flexible servers using REST API.
 ms.topic: conceptual
-ms.date: 04/30/2024
+ms.date: 05/13/2024
 ms.assetid: 759ee63f-148b-464c-bfc4-c9e640b7da6b
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
 
 # Restore Azure Database for PostgreSQL - Flexible servers using REST API (preview)
 
-This article describes how to restore an Azure PostgreSQL flexible server backed-up by Azure Backup.
+This article describes how to restore an Azure Database for PostgreSQL - Flexible server backed up by Azure Backup.
 
 ## Prerequisites
 
@@ -27,7 +27,7 @@ Let's use an existing Backup vault `TestBkpVault`, under the resource group `tes
 ### Set up permissions
 
 Backup vault uses Managed Identity to access other Azure resources. To restore from backup, Backup vault’s managed identity requires a set of permissions on the target to be restored to.
-To restore the recovery point as files to a storage account, Backup vault's system assigned managed identity needs access on the target storage account as [mentioned here](restore-azure-database-postgresql.md#restore-permissions-on-the-target-storage-account).
+To restore the recovery point as files to a storage account, Backup vault's system assigned managed identity needs access on the target storage account as mentioned [here](restore-azure-database-postgresql.md#restore-permissions-on-the-target-storage-account).
 
 ### Fetch the relevant recovery point
 
@@ -43,7 +43,7 @@ For example, this API translates to:
 GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/TestBkpVaultRG/providers/Microsoft.DataProtection/backupVaults/testBkpVault/backupInstances/pgflextestserver-857d23b1-c679-4c94-ade6-c4d34635e149/recoveryPoints?api-version=2021-07-01
 ```
 
-**Responses for list of recovery points**:
+**Responses for the list of recovery points**:
 
 Once you submit the *GET* request, it returns response as *200* (OK), and the list of all discrete recovery points with all the relevant details.
 
@@ -106,7 +106,7 @@ Select the relevant recovery points from the above list and proceed to prepare t
 
 ### Restore as files
 
-Fetch the URI of the container, within the storage account to which permissions were assigned as [detailed above](#set-up-permissions). For example, a container named `testcontainerrestore` under a storage account `testossstorageaccount` with a different subscription.
+Fetch the URI of the container, within the storage account to which permissions were assigned as detailed [above](#set-up-permissions). For example, a container named `testcontainerrestore` under a storage account `testossstorageaccount` with a different subscription.
 
 ```HTTP
 "https://testossstorageaccount.blob.core.windows.net/testcontainerrestore"
@@ -254,7 +254,7 @@ It returns two responses: 202 (Accepted) when another operation is created. Then
 
 Example response to trigger restore request:
 
-Once the *POST* operation is submitted, it will return the initial response as *202* (Accepted) with an *Azure-asyncOperation* header.
+Once the *POST* operation is submitted, it will return the initial response as *202* (Accepted) with an `Azure-asyncOperation` header.
 
 ```HTTP
 HTTP/1.1 202 Accepted
@@ -276,7 +276,7 @@ X-Powered-By: ASP.NET
 
 ```
 
-Track the `Azure-AsyncOperation` header with a simple *GET* request. When the request is successful, it will return 200 (OK) with a job ID that should be further tracked for completion of restore request.
+Track the `Azure-AsyncOperation` header with a simple *GET* request. When the request is successful, it will return 200 (OK) with a job ID that should be further tracked for completion of the restore request.
 
 ```HTTP
 GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/providers/Microsoft.DataProtection/locations/westus/operationStatus/ZmMzNDFmYWMtZWJlMS00NGJhLWE4YTgtMDNjYjI4Y2M5OTExO2Q1NDIzY2VjLTczYjYtNDY5ZC1hYmRjLTc1N2Q0ZTJmOGM5OQ==?api-version=2021-07-01

articles/backup/backup-azure-database-postgresql-flex-use-rest-api.md

@@ -2,7 +2,7 @@
 title: Back up Azure Database for PostgreSQL - Flexible servers using in Azure Backup
 description: Learn how to back up Azure Database for PostgreSQL - Flexible servers using REST API.
 ms.topic: conceptual
-ms.date: 04/30/2024
+ms.date: 05/13/2024
 ms.assetid: 759ee63f-148b-464c-bfc4-c9e640b7da6b
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
@@ -39,7 +39,7 @@ Once the vault and policy are created, there're three critical points to conside
 
    Backup vault has to connect and access the PostgreSQL flexible server. Access is granted to the Backup vault's Managed Service Identity (MSI).
 
-   You need to grant permissions to back up vault's MSI on the PostgreSQL. Learn more.
+   You need to grant permissions to back up vault's MSI on the PostgreSQL. [Learn more](backup-azure-database-postgresql-overview.md#set-of-permissions-needed-for-azure-postgresql-database-backup).
 
 ### Prepare the request to configure backup
 
@@ -80,10 +80,9 @@ After you set the relevant permissions to the vault and PostgreSQL flexible serv
 
 To validate if the backup configuration request will be successful, use the *validate for backup* API. You can use the response to perform the required prerequisites, and then submit the configuration for the backup request.
 
-**Validate for backup request is a POST operation and the Uniform Resource Identifier (URI)**
+*Validate for backup request* is a *POST* operation and the Uniform Resource Identifier (URI) contains `{subscriptionId}`, `{vaultName}`, `{vaultresourceGroupName}` parameters.
 
 ```HTTP
-contains {subscriptionId}, {vaultName}, {vaultresourceGroupName} parameters.
 POST https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{vaultresourceGroupname}/providers/Microsoft.DataProtection/backupVaults/{backupVaultName}/validateForBackup?api-version=2021-01-01
 
 ```
@@ -145,7 +144,7 @@ It returns two responses: 202 (Accepted) when another operation is created, and
 
 *Error response*
 
-If the given server is already protected, it returns the response as HTTP 400 (Bad request) and states that the given server is already protected in a backup vault along with details.
+If the given server is already protected, it returns the response as HTTP 400 (Bad request) and states that the given server is already protected in a backup vault along with the details.
 
 ```HTTP
 HTTP/1.1 400 BadRequest
@@ -233,7 +232,7 @@ GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
 
 ```
 
-It returns 200 (OK) once it completes and the response body lists further requirements to be fulfilled, such as permissions.
+It returns 200 (OK) once it completes and the response body lists more requirements to be fulfilled, such as permissions.
 
 ```HTTP
 GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/providers/Microsoft.DataProtection/locations/westus/operationStatus/ZmMzNDFmYWMtZWJlMS00NGJhLWE4YTgtMDNjYjI4Y2M5OTExOzM2NDdhZDNjLTFiNGEtNDU4YS05MGJkLTQ4NThiYjRhMWFkYg==?api-version=2021-01-01
@@ -276,7 +275,7 @@ GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
 
 ```
 
-If you grant all permissions, then resubmit the validation request, track the resulting operation. It'll return the success response as 200 (OK) if all the conditions are met.
+If you grant all permissions, then resubmit the validation request, and track the resulting operation. It'll return the success response as 200 (OK) if all the conditions are met.
 
 ```HTTP
 GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/providers/Microsoft.DataProtection/locations/westus/operationStatus/ZmMzNDFmYWMtZWJlMS00NGJhLWE4YTgtMDNjYjI4Y2M5OTExOzlhMjk2YWM2LWRjNDMtNGRjZS1iZTU2LTRkZDNiMDhjZDlkOA==?api-version=2021-01-01
@@ -295,7 +294,7 @@ GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
 
 Once the request is validated, you can submit the same to the [create backup instance API](/rest/api/dataprotection/backup-instances/create-or-update). One of the Azure Backup data protection services protects the Backup instance within the Backup vault. Here, the Azure PostgreSQL flexible server is the backup instance. Use the above-validated request body with minor additions.
 
-Use a unique name for the backup instance. So, we recommend you use a combination of the resource name and a unique identifier. For example, in the following operation, we'll use *pgflextestserver-857d23b1-c679-4c94-ade6-c4d34635e149* and mark it as the backup instance name.
+Use a unique name for the backup instance. We recommend you to use a combination of the resource name and a unique identifier. For example, in the following operation, we'll use *pgflextestserver-857d23b1-c679-4c94-ade6-c4d34635e149* and mark it as the backup instance name.
 
 To create or update the backup instance, use the following *PUT* operation:
 
@@ -358,7 +357,7 @@ We'll use the [same request body that we used to validate the backup request](ba
 ### Responses to configure backup request
 
 Create backup instance request is an [asynchronous operation](../azure-resource-manager/management/async-operations.md). So, this operation creates another operation that needs to be tracked separately.
-It returns two responses: 201 (Created) when backup instance is created and the protection is configured. 200 (OK) when that configuration completes.
+It returns two responses: *201* (Created) when the backup instance is created and the protection is configured. 200 (OK) when that configuration completes.
 
 | Name | Type | Description |
 | --- | --- | --- |