fix(red): links

Author: ldecarvalho-doc

pages/managed-databases-for-redis/how-to/monitor-redis-databases-cockpit.mdx

@@ -27,7 +27,7 @@ This page explains how to get started with Scaleway Cockpit for viewing your Man
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
-- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
+- A [Redis™ Database Instance](/managed-databases-for-redis/quickstart/)
 
 ## How to activate your Cockpit
 
@@ -72,7 +72,7 @@ Metrics are refreshed every minute, and report on the following data:
 At the top of the dashboard, you can configure the following parameters, that control which metrics are displayed:
 
 - **Resource name** - Select a specific Database Instance to monitor.
-- **Node** - Choose a specific node (main, replica, or Read Replica). In a High Availability (HA) cluster, both nodes might switch from main to replica and vice versa. So you might see two versions of the same node, as main and as replica. If you select main for a specific node, you will only see the node's activity when it was the main, and vice-versa.
+- **Node** - Choose a specific node (main or replica). In a High Availability (HA) cluster, both nodes might switch from main to replica and vice versa. You might see two versions of the same node, as main and as replica. If you select main for a specific node, you will only see the node's activity when it was the main, and vice-versa. In Cluster mode, all nodes are considered primary and each have a data subset.
 - **Timeframe** - Get metrics from the last five minutes up to 31 days (free plan) and 365 days (premium plan).
 
 ### Viewing logs

pages/managed-databases-for-redis/troubleshooting/database-instance-connectivity-issues.mdx

@@ -34,7 +34,7 @@ You can check the following points to identify and act on what might be causing
 1. If TLS is enabled on the Database Instance, make sure the certificate is up to date and that your client application is properly configured.
 2. Make sure your [ACLs](/managed-databases-for-redis/concepts/#allowed-ips) are [properly configured](/managed-databases-for-redis/how-to/manage-allowed-ip-addresses-redis).
 3. Make sure your Database Instance has not reached the maximum number of connections stipulated in the advanced settings of the Database Instance. You can monitor the number of connections on Cockpit. You can also [adjust the advanced settings](/managed-databases-for-redis/how-to/configure-advanced-settings-redis) to accept a higher number of connections.
-4. [Monitor other usage metrics on Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to:
+4. [Monitor other usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-redis-databases-cockpit) to:
 
     - Check if the memory usage is nominal. High memory usage could trigger OOM Kills and cause disconnection
     - Check Database Instance logs and look for anything else that could explain the issue
@@ -57,7 +57,7 @@ I cannot connect to my Database Instance through a Private Network.
 You can carry out the following actions:
 
 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-redis/how-to/monitor-databases-cockpit) to check database logs and look for any activity or behavior that could explain the issue.
+2. [Use Cockpit](/managed-databases-for-redis/how-to/monitor-redis-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:
 
     - The resource ID of resource from which the connection was attempted

pages/managed-databases-for-redis/troubleshooting/database-instance-performance-issues.mdx

@@ -26,6 +26,6 @@ My Database Instance is not performing as expected.
 
 ## Solution
 
-You can [Monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-databases-cockpit) to check if the usage is nominal.
+You can [Monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-redis-databases-cockpit) to check if the usage is nominal.
 
 The Database Instance can be impacted by high data loads or unexpected high traffic from an app or website, for example. You can [scale up your Instance](/managed-databases-for-redis/how-to/scale-up-a-database-for-redis) if necessary.

pages/managed-databases-for-redis/troubleshooting/database-instance-unavailable.mdx

@@ -27,7 +27,7 @@ My Database Instance is unavailable.
 
 You can monitor your Database Instance activity to be able to quickly identify and act on irregular activities that might be causing the instability/unavailability.
 
-[Monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-databases-cockpit) to:
+[Monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-redis-databases-cockpit) to:
 
     - 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 the Database Instance logs for any unusual or suspicious activity