diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx
index 70bc344c34..c7311aefe0 100644
--- a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx
+++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx
@@ -80,7 +80,8 @@ You can create new Database Instances to attach to your Private Network, or atta
         </Message>
 
     <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.
+      - 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.
+      - You can also use internal DNS entries that point to the allocated IP address, which can be used to connect to the database. Refer to the [DNS resolution details](/vpc/reference-content/dns/#dns-resolution-details) section of the **Understanding Scaleway DNS for VPC and Private Networks** documentation page for a list of the formats resolved by the DNS service.
     </Message>
 7. Click **Attach to Private Network** to conclude.
 
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx
index 10a159a050..ec0f5024be 100644
--- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx
+++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx
@@ -31,6 +31,7 @@ You can change your Database Instance node type and enable High Availability aft
     <Message type="important">
     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 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.
       - If you use local storage: