fix(rdb): review hugo

Co-authored-by: Hugo DUBOIS <[email protected]>

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-publisher.mdx

@@ -1,7 +1,7 @@
 ---
 title: Setting up logical replication as a publisher in PostgreSQL
 description: Learn how to set up and use logical replication as a publisher in PostgreSQL
-tags: postgresql logical replication publisher migration database
+tags: postgresql logical replication publisher publication database 
 dates:
   validation: 2025-08-25
   posted: 2025-02-20
@@ -40,8 +40,8 @@ Follow the steps in the [How to manage users](/managed-databases-for-postgresql-
 
 To create publications and replication slots, the `replication_user` must:
 
-- Either be an admin user (`rdb_admin`)
-- Or be granted the following rights from an `rdb_admin`:
+- Either be an member of admin user role (`_rdb_admin`)
+- Or be granted the following rights from a role member of the`_rdb_admin` role:
     - `ALTER replication_user with REPLICATION`
     - `GRANT CREATE ON DATABASE my_database TO my_replication_user;`
 
@@ -117,8 +117,8 @@ We use an example scenario to show how logical replication can be set up.
     ```
     </Message>
 
-- If a logical replication is not active but still consumed by a subscription or other tool, PostgreSQL WAL files will accumulate in the primary node, filling up storage. In the worst case scenario, your database can be set to read only mode (check disk full section).
+- If a logical replication is not active (not consumed by a subscription or other tool), PostgreSQL WAL files will accumulate in the primary node, filling up storage. In the worst case scenario, your database can be set to read only mode (check disk full section) or unavailable.
     <Message type="tip">
-      - We recommend you delete any replications that are no longer used.
+      - We recommend you delete any replication slots that are no longer used.
       - If a logical replication is inactive for 24h, it will be automatically removed.
     </Message>