addressed Acro suggestions

Author: AbhishekMallick01

articles/backup/backup-azure-database-postgresql-flex-support-matrix.md

@@ -2,7 +2,7 @@
 title: Azure Database for PostgreSQL- Flexible server support matrix
 description: Provides a summary of support settings and limitations of Azure Database for PostgreSQL- Flexible server backup.
 ms.topic: reference
-ms.date: 05/02/2025
+ms.date: 04/30/2025
 ms.custom: references_regions, ignite-2024
 ms.service: azure-backup
 author: jyothisuri
@@ -54,7 +54,7 @@ Azure Database for PostgreSQL – Flexible Server backups include the following
   - `ERROR: Only roles with the ADMIN option on role "pg_use_reserved_connections" may grant this role. permission denied to grant role "pg_use_reserved_connections"`
   - `ERROR: permission denied to grant role "pg_use_reserved_connections" SQL state: 42501 Detail: Only roles with the ADMIN option on role "pg_use_reserved_connections" may grant this role.`
 
-- In PostgreSQL **community version 16**, the requirement for superuser privileges to set the Bypass RLS attribute was removed. So, in versions 16 and higher, you can grant the Bypass RLS to azure_pg_admin allowing others to perform this. For versions lower than 16, the bypassrls attribute is granted only to the server admin and no other non-superuser roles. 
+- In PostgreSQL **community version 16**, the requirement for superuser privileges to set the Bypass Row -level security (RLS) attribute was removed. So, in versions 16 and higher, you can grant the Bypass RLS to azure_pg_admin allowing others to set the RLS. For versions lower than 16, the bypasses attribute is granted only to the server admin and no other nonsuperuser roles. 
 - If you're using Entra Admins after restoration, you might encounter the **Owner Change Issue** : As a workaround, use the **grant** option to provide ownership. 
 
 

articles/backup/restore-azure-database-postgresql-flex.md

@@ -2,7 +2,7 @@
 title: Restore Azure PostgreSQL-Flexible server as Files using Azure portal
 description: Learn about how to restore Azure PostgreSQL-Flexible server as Files.
 ms.topic: how-to
-ms.date: 05/02/2025
+ms.date: 04/30/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2024
@@ -56,7 +56,7 @@ To restore Azure PostgreSQL-Flexible database, Follow these steps:
 After the restore job is completed successfully, go to the storage account container to view the restored databases as files (`.sql` files) from your PostgreSQL – Flexible server. Azure Backup also generates the following backup files:
 
 - `Database.sql file` per database: Contains data and schema information for a particular database.  
-- `Roles.sql files` for entire instance: Contains all  role information that exists at server level (will include azure_su(superuser) azure_pg_admin, replication, local admin, Entra admins and any other custom roles on the server).
+- `Roles.sql files` for entire instance: Contains all  role information ((azure_su(superuser) azure_pg_admin, replication, local admin, Microsoft Entra admins and any other custom roles on the server)) that exists at server level.
 - `Tablespace.sql file`: Tablespace file.
 - `Schema.sql file`: Contains schema information for all the databases on the server.
 
@@ -71,7 +71,7 @@ To restore the backup files from storage container to a new or existing PostgreS
 
 1. Ensure that all required [extensions are enabled](/azure/postgresql/extensions/how-to-allow-extensions?tabs=allow-extensions-portal) on the new target Flexible server. 
 1. [Match the server parameter](/azure/postgresql/flexible-server/how-to-server-parameters-list-all?tabs=portal-list) values from the source PostgreSQL database to the Azure Database for PostgreSQL by accessing the **Server parameters** section in the Azure portal and manually updating the values accordingly. Save the parameter changes, and then restart the Azure Database for PostgreSQL - Flexible server to apply the new configuration. 
-1. If **Microsoft Entra Authentication** is required on the new server, enable it and create the relevant entra admins. 
+1. If **Microsoft Entra Authentication** is required on the new server, enable it and create the relevant Microsoft Entra admins. 
 1. Create a new database for restoration.
 
    >[!Note]
@@ -80,7 +80,7 @@ To restore the backup files from storage container to a new or existing PostgreS
    >To create the database, use the `CREATE DATABASE Database_name` command.
 
 1. Restore the database using the `database.sql file` as the target admin user.
-1.After the target database is created, restore the data in this database from the dump file using the following command from an azure storage account:
+1.After the target database is created, restore the data in this database (from the dump file) from an Azure storage account by running the following command:
 
    ```azurecli-interactive
    az storage blob download --container-name <container-name> --name <blob-name> --account-name <storage-account-name> --account-key <storage-account-key> --file - | pg_restore -h <postgres-server-url> -p <port> -U <username> -d <database-name> --no-owner -v – 
@@ -96,31 +96,31 @@ To restore the backup files from storage container to a new or existing PostgreS
 
    Alternatively, you can download the backup file and run the restore directly. 
 
-1. Restore only the required roles and privileges, and ignore the [common errors](backup-azure-database-postgresql-flex-support-matrix.md#restore-limitations). Skip this step if you are performing the restoration for compliance requirements and data retrieval, as a local admin.
+1. Restore only the required roles and privileges, and ignore the [common errors](backup-azure-database-postgresql-flex-support-matrix.md#restore-limitations). Skip this step if you're performing the restoration for compliance requirements and data retrieval, as a local admin.
 
 ## Restore roles and users for the restored databases
 
-Vaulted backups are primarily restored for compliance needs such as, testing and audits. You can sign in as a local admin and restore using the `database.sql` file; no additional roles are needed for data retrieval.
+Vaulted backups are primarily restored for compliance needs such as, testing and audits. You can sign in as a local admin and restore using the `database.sql` file; no other roles are needed for data retrieval.
 
 For other uses like accidental deletion protection or disaster recovery, ensure necessary roles are created as per your organization needs. Avoid duplications between `roles.sql` and `database.sql`.
 
 - **Restore the same Flexible server**: Role restoration might not be necessary. 
 - **Restore to a different Flexible server**: Use the `roles.sql` file to recreate the required roles. 
 
-When restoring from `roles.sql`, some roles or attributes might not be valid for the new target server.
+When you restore from `roles.sql`, some roles or attributes might not be valid for the new target server.
 
-For environments with superuser access ( on-premises or VMs), you can run all commands seamlessly.
+For environments with superuser access (on-premises or VMs), you can run all commands seamlessly.
 
 ### Key considerations for the Flexible server scenario
 
 Here are the key considerations:
 
-- **Remove Superuser-Only Attributes**: On Flexible server there's no superuser privileges. So, remove attributes such as, `NOSUPERUSER` and `NOBYPASSRLS` from the roles dump. 
-- **Exclude Service-Specific Users**: Exclude users specific to Flexible Server services (` azure_su`, `azure_pg_admin`, `replication`, `localadmin`, `Entra Admin`). These are specific service roles, and are automatically recreated when administrators are added to the new Flexible server. 
+- **Remove Superuser-Only Attributes**: On Flexible server, there's no superuser privileges. So, remove attributes, such as `NOSUPERUSER` and `NOBYPASSRLS` from the roles dump. 
+- **Exclude Service-Specific Users**: Exclude users specific to Flexible Server services (` azure_su`, `azure_pg_admin`, `replication`, `localadmin`, `Entra Admin`). These specific service roles are automatically recreated when administrators are added to the new Flexible server. 
 
-Before you restore the database objects, ensure that you have properly dumped and cleaned up the roles. To do this, download the `roles.sql`script from your storage container and create all required logins. 
+Before you restore the database objects, ensure that you properly dump and clean up the roles. To perform this action, download the `roles.sql`script from your storage container and create all required logins. 
 - **Create Non-Entra Roles**: Use a local admin account to run the role creation scripts. 
-- **Create Microsoft Entra Roles**: If you need to create roles for Entra users, use a Microsoft Entra administrator account to run the necessary scripts. 
+- **Create Microsoft Entra Roles**: If you need to create roles for Microsoft Entra users, use a Microsoft Entra administrator account to run the necessary scripts. 
 
  ## Next steps