fix(rdb): reviews

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 publication database 
+tags: postgresql logical replication publisher publication database
 dates:
   validation: 2025-08-25
   posted: 2025-02-20
@@ -22,19 +22,17 @@ Replication slots can be created with the `failover` flag, which ensures that re
 
 ## Configuring advanced settings and user rights
 
-As the service uses physical replication to provide High Availability, some parameters must be enabled to allow the logical replication to remain active after the promotion of a secondary node, without disturbing the HA setup. It is essential to ensure these setting are enabled as even Database Instances with in standalone mode can be replaced with temporary replicas.
-
-The [replication slot](https://www.postgresql.org/docs/17/logicaldecoding-explanation.html#LOGICALDECODING-REPLICATION-SLOTS) is an important part of the logical replication. Each subscription receives changes via one replication slot created on the "publishing" node. You have one replication slot available per logical database.
-
-To use replication, users must also have the corresponding rights.
+As the service uses physical replication to provide High Availability, some advanced settings must be enabled to allow the logical replication to remain active after the promotion of a secondary node, without disturbing the HA setup. It is essential to ensure these settings are enabled as even Database Instances with in standalone mode can be replaced with temporary replicas.
 
 Follow the steps in the [How to configure advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) documentation page to configure the following settings:
 
 To enable logical replication, you must:
 
 - Enable the `rdb.enable_logical_replication` setting. This automatically changes the `wal_level` settings to `logical`.
 - Set `hot_standby_feedback` to `ON`
-- Set `sync_replication_slots` to `ON`
+- Set `sync_replication_slots` to `ON`- [replication slots](https://www.postgresql.org/docs/17/logicaldecoding-explanation.html#LOGICALDECODING-REPLICATION-SLOTS) is an important part of the logical replication. Each subscription receives changes via one replication slot created on the "publishing" node. You have one replication slot available per logical database.
+
+To use replication, users must also have the corresponding rights.
 
 Follow the steps in the [How to manage users](/managed-databases-for-postgresql-and-mysql/how-to/manage-users) documentation page to attribute user rights.
 
@@ -86,7 +84,7 @@ We use an example scenario to show how logical replication can be set up.
         CREATE SUBSCRIPTION sub CONNECTION 'host=myhost port=myport user=myuser dbname=mydb password=mypassword' PUBLICATION pub WITH (enabled=true, create_slot=false, slot_name='sub');
         ```
         <Message type="note">
-          Refer to the [PostgreSQL documentation](https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-REPLICATION) for more information about `pg_create_logical_replication_slot()`.
+          Refer to the official [PostgreSQL documentation](https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-REPLICATION) for more information about `pg_create_logical_replication_slot()`.
         </Message>
       </TabsTab>
     </Tabs>
@@ -96,14 +94,18 @@ We use an example scenario to show how logical replication can be set up.
     SELECT * FROM mytable;
     ```
 
+<Message type="note">
+  Refer to the official [PostgreSQL documentation](https://www.postgresql.org/docs/current/logical-replication.html) for more information about logical replication.
+</Message>
+
 ## Limitations
 
 - 100 replication slots are available for each Database Instance.
 - 25 out of the 100 slots are reserved for Scaleway's internal systems.
 - During the synchronization phase, 2 or more slots might be needed for a subscription.
     <Message type="important">
       - If you need more than 50 replication slots, [create a support ticket](https://console.scaleway.com/support).
-      - If the limit is exceeded, your Managed Database service may become compromised.
+      - Exceeding this limit may cause the Instance's internal replication to fail.
     </Message>
 
     <Message type="tip">

pages/managed-databases-for-postgresql-and-mysql/reference-content/pg-version-updates.mdx

@@ -29,7 +29,7 @@ New features are available with PostgreSQL 17:
 ### Extensions
 
 - **PostGIS** - [3.5](https://postgis.net/tags/3.5/)
-- **Timescale** - [2.2](https://github.com/timescale/timescaledb/releases/tag/2.21.4)
+- **Timescale** - [2.2](https://github.com/timescale/timescaledb/releases/tag/2.22.1)
 - **pgRouting** - [3.7.3](https://github.com/pgRouting/pgrouting/releases/tag/v3.7.3)
 - **pgvector** - [0.8.1](https://github.com/pgvector/pgvector/releases/tag/v0.8.1)
 - **H3 PG** - [4.2.3](https://github.com/zachasme/h3-pg/releases/tag/v4.2.3)
@@ -38,7 +38,8 @@ New features are available with PostgreSQL 17:
 
 These are the new advanced settings available with PostgreSQL 17:
 
-- `allow_alter_system`
+- `rdb.enable_logical_replication`
+- `sync_replication_slots`
 
 Refer to the official [Server configuration](https://www.postgresql.org/docs/17/runtime-config-compatible.html) PostgreSQL documentation for more information.