fix(rdb): reviews

Co-authored-by: Bastien Wirtz <[email protected]>

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx

@@ -49,13 +49,13 @@ I cannot connect to my Database Instance through a Private Network.
 
 - Client network issue
 - You have reached the maximum number of connections
-- You have a high memory usage
+- The Database Instance is experiencing instabilities due to a high load
 
 ### Solution
 
 You can carry out the following actions:
 
-1. Check if you are you able to connect to the Database Instance from the public endpoint, if one is available.
+1. Try to connect to the Database Instance from the public endpoint, if one is available, to identify the possible origin (network or instance). This information can help you or the support team to identify the issue.
 2. [Use Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to check database logs and look for any activity or behavior that could explain the issue.
 3. Create a support ticket if the first two steps do not help troubleshoot the issue. In the body of the ticket, make sure you provide:
 

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx

@@ -31,4 +31,4 @@ You can monitor your Database Instance activity to be able to quickly identify a
 
     - Check if the usage is regular. Database Instance can be impacted by high data loads or unexpected high traffic from an app or website, for example
     - Check if there are slow queries in the Database Instance log. Huge or sub-optimized queries can fill up all the memory and trigger OOM kills
-    - Check Database Instance logs and look for anything else that could explain the issue
+    - Check the Database Instance logs for any unusual or suspicious activity