fix(rdb): review axel

Author: ldecarvalho-doc

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 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.
       - If you use local storage:
@@ -67,7 +68,6 @@ 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.