fix(rdb): reviews 3

Author: ldecarvalho-doc

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

@@ -22,7 +22,7 @@ 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 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.
+As the service uses physical replication internally, some advanced settings and parameters must be enabled to allow the logical replication to work properly with our system, for standalone and High Availability clusters.
 
 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:
 
@@ -32,6 +32,11 @@ To enable logical replication, you must:
 - Set `hot_standby_feedback` 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.
 
+<Message type="important">
+  It is essential to set these parameters when using logical replication to ensure service availability.
+</Message>
+
+
 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.