fix(rdb): dns entries and ram upgrade

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx

@@ -81,6 +81,11 @@ You can create new Database Instances to attach to your Private Network, or atta
 
     <Message type="note">
       Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform/OpenTofu.
+
+      There are also internal DNS entries that point to the allocated IP address, which can be used to connect to the database. You can use the following formats:
+          - `<rdb_instance_name>.<private_network_name>.internal`
+          - `<rdb_instance_uuid>.<private_network_name>.internal`
+          - `<rdb_instance_uuid>.<private_network_uuid>.internal`
     </Message>
 7. Click **Attach to Private Network** to conclude.
 

pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx

@@ -67,6 +67,7 @@ If you are in standalone mode, you can change the node configuration to High Ava
     <Message type="note">
       Keep in mind that:
       - Changing the node type performs a rolling upgrade of your Database Instance.
+      - Switching to a node type with less RAM than the current one incurs in an automatic reset of your configured parameters to ensure they fit the new available resources.
       - During this process, the Database Instance will be unavailable for several seconds.
       - The Instance stays in `Initializing` mode throughout the process and all console actions are unavailable.
       - If you use local storage the process can take longer than expected, but the unavailability period of the Instance will be short. This means that the Database Instance remains mostly available during the entire process, except for a few seconds.