fix(rdb): review hugo estelle

Author: ldecarvalho-doc

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

@@ -101,5 +101,5 @@ You can create new Database Instances to attach to your Private Network, or atta
 This action takes a few moments to complete. During this time, your Database Instance:
   - remains available,
   - goes into **Configuring** mode, and
-  - network configuration actions become unavailable
+  - all Database Instance configuration becomes unavailable
 </Message>

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

@@ -29,11 +29,15 @@ You can change your Database Instance the node type and enable High Availability
 5. Choose the specifications of the new Database Instance from the drop-down list.
 6. Click **Update node type** to confirm your choices.
     <Message type="important">
-      Make sure that the Database Instance you choose provides sufficient disk space for your database. Otherwise, an error message will be displayed, and the database will not be upgraded.
+    Keep in mind that:
+      - Changing the node type performs a rolling upgrade of your Database Instance.
+      - 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:
+          - Make sure that the Database Instance you choose provides sufficient disk space for your database. Otherwise, an error message will be displayed, and the database will not be upgraded.
+          - The process can take longer than expected, but the unavailability period of the Instance will be short. This means that though the Database Instance mostly remains available during the entire process, bar a few seconds.
     </Message>
 
-Changing the node type performs a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several seconds.
-
 ## How to enable High Availability
 
 You define your Database Instance's node configuration upon its [creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database). Two node configuration modes are available with PostgreSQL or MySQL Database Instances.
@@ -61,5 +65,9 @@ If you are in standalone mode, you can change the node configuration to High Ava
 6. Click **Activate**.
 
     <Message type="note">
-Changing the node type performs a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several seconds.
+      Keep in mind that:
+      - Changing the node type performs a rolling upgrade of your Database Instance.
+      - 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 though the Database Instance mostly remains available during the entire process, bar a few seconds.
     </Message>

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

@@ -40,9 +40,9 @@ Users can connect to a database and access its data. Each one has a different se
     </Message>
 
     <Message type="important">
-      Permissions are applied to existing items **at the moment the configuration is set**. They cannot be applied to any items created afterward.
-      When you modify your Database configuration, your configured permissions are automatically set to **Custom**. The **Custom** setting ensures that your permissions are still valid for items created before you reconfigured your Database.
-      Any items created after you change your configuration will not have permissions applied to them, you must set new permissions.
+      PostgreSQL Permissions are applied to existing items **at the moment the configuration is set**. They cannot be applied to any items created afterward.
+      When you add database objects like tables or sequences, your configured permissions are automatically set to **Custom**. The **Custom** setting ensures that your permissions are still valid for items created before you reconfigured your Database.
+      You can use [PostgreSQL default privileges](https://www.postgresql.org/docs/current/sql-alterdefaultprivileges.html) to set default privileges for future objects.
     </Message>
 8. Click **Create user** to confirm.
 
@@ -64,7 +64,7 @@ Permissions define the actions a user can perform on a logical database. A datab
       Three types of permissions are available:
         - **None:** No access to the database
         - **Read:** Allow users to read tables and fields in a database
-        - **Write:** Allow users to write content in databases
-
+        - **Read/Write:** Allow users to read/write content in databases
+        - **All:** Allows the creation of schemas and tables.
     </Message>
 7. Click **Update user** to confirm.

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

@@ -41,7 +41,7 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an
 5. Select **Block Storage** from the drop-down menu.
 6. Click **Update volume type** to confirm.
 
-    The Database Instance goes into the `Initializing` state.
+    The Database Instance goes into the `Initializing` state and remains available during the process. The time it takes to complete the process may vary, depending on the size of the volume.
 
 ### The volume changing process