fix(rdb): review neda

Co-authored-by: Néda <[email protected]>

Author: ldecarvalho-doc

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

@@ -67,7 +67,7 @@ To be able to create a subscription, you must have the privileges of the `pg_cre
     SELECT * FROM pg_subscription;
     ```
     <Message type="tip">
-      Refer to the official PostgreSQL documentation for more information on the `pg_subscription` catalog.
+      Refer to the official [PostgreSQL documentation](https://www.postgresql.org/docs/current/catalog-pg-subscription.html) for more information on the `pg_subscription` catalog.
     </Message>
 
 
@@ -76,7 +76,7 @@ To be able to create a subscription, you must have the privileges of the `pg_cre
 When creating a subscription from a Scaleway Database Instance to a public IP, the public interface of the Database Instance node is used to connect to the publisher. This might incur in the following consequences:
 
 - If you only have a private endpoint, your Database Instance will still have a public management IP address. The ports are all closed, stopping all connections except the one with the publisher database. All outgoing data is securely encrypted. 
-- If your Database Instance set-up is composed of more than one node, your IP address is subject to change. In case of failover, for example, the IP address connecting to the publisher database will change. We cannot predict the new IP your nodes might take one. However, you can use [Scaleway's Autonomous System](https://ipinfo.io/AS12876) to check the number (ASN) of your primary node's IP address, look up the IP address allocation for the ASN. This can help you predict the IP address of your failover nodes.
+- If your Database Instance set-up is composed of more than one node, your IP address is subject to change. In case of failover, for example, the IP address connecting to the publisher database will change. We cannot predict the new IP your nodes might take. However, you can use [Scaleway's Autonomous System](https://ipinfo.io/AS12876) to check the number (ASN) of your primary node's IP address, and look up the IP address allocation for the ASN. This can help you predict the IP address of your failover nodes.
 - There is a limit to the number of subscriptions that can be created per Database Instance offer. You can find the table of maximum number of subscriptions per node type below.
 
 | Node Type | Maximum subscriptions |

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

@@ -44,7 +44,7 @@ The `RDB` admin role can now assign the following predefined roles:
 New features are available with PostgreSQL 16:
 
 - The logical replication of databases as a subscriber is now supported. Refer to the [Setting up logical replication as a subscriber in PostgreSQL](/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber) documentation page for more information.
-- Passwords are now encrypted using the `SCRAM-SHA-256` setting. If you upgrade your engine and are currently using MD5, you have also to migrate to SCRAM-SHA-256. Refer to the official [Password Authentication](https://www.postgresql.org/docs/current/auth-password.html#AUTH-PASSWORD) PostgreSQL documentation to learn how to do so.
+- Passwords are now encrypted using the `SCRAM-SHA-256` setting. If you upgrade your engine and are currently using MD5, you also have to migrate to SCRAM-SHA-256. Refer to the official [Password Authentication](https://www.postgresql.org/docs/current/auth-password.html#AUTH-PASSWORD) PostgreSQL documentation to learn how to do so.
 - Support of the Timescale [pre-restore](https://docs.timescale.com/api/latest/administration/#timescaledb_pre_restore) and [post-restore](https://docs.timescale.com/api/latest/administration/#timescaledb_post_restore) features. They allow you to restore the database using `pg_restore`.
 
 ## Extensions