fix(rdb): reviews final

Author: ldecarvalho-doc

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

@@ -33,7 +33,7 @@ To enable logical replication, you must:
 - 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.
 
 <Message type="important">
-  It is essential to set these parameters when using logical replication to ensure service availability.
+  As the service uses physical replication to provide High Availability, the `hot_standby_feedback` and `sync_replication_slots` 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 settings are enabled as even a Database Instance in standalone mode can be replaced with temporary replicas.
 </Message>
 
 To use replication, users must also have the corresponding rights.
@@ -109,7 +109,7 @@ We use an example scenario to show how logical replication can be set up.
 - 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).
-      - Exceeding this limit may cause the Instance's internal replication to fail.
+      - Exceeding this limit may cause the Instance's internal replication to fail. High Availability and cluster operations may also become degraded or not functional. In extreme cases, service availability may be affected.
     </Message>
 
     <Message type="tip">