docs(gen): fix broken links

Author: bene2k1

changelog/august2023/2023-08-31-postgresql-and-mysql-added-promote-a-read-replica.mdx

@@ -11,5 +11,5 @@ product: postgresql-and-mysql
 
 You can now promote a Read Replica node to a standalone Database Instance. This is useful for database failure recovery or sharding.
 
-For more information, refer to the [How to manage Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) documentation page.
+For more information, refer to the [How to manage Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/#how-to-promote-a-read-replica) documentation page.
 

pages/instances/reference-content/moving-instances-between-az-and-projects.mdx

@@ -15,7 +15,7 @@ You can perform these actions using the Scaleway console, CLI, or API.
 <Requirements />
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - An [Instance](/instances/how-to/create-an-instance/)
-- The [Scaleway CLI](/docs/scaleway-cli/quickstart/) installed (for CLI-based instructions)
+- The [Scaleway CLI](/scaleway-cli/quickstart/) installed (for CLI-based instructions)
 - A valid [API key](/iam/how-to/create-api-keys/) with sufficient permissions (for API-based instructions)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 

pages/managed-databases-for-postgresql-and-mysql/concepts.mdx

@@ -120,4 +120,4 @@ A database type that uses the relational model, which means that it stores and p
 
 This is the type of storage used on your Database Instances. Two types are available: [Local Storage](#local-storage) and [Block Storage](#block-storage).
 
-You can select the volume type upon Database Instance creation, and you can [change the type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) anytime.
+You can select the volume type upon Database Instance creation, and you can [change the type](/managed-databases-for-postgresql-and-mysql/how-to/manage-volumes/) anytime.

pages/managed-databases-for-postgresql-and-mysql/faq.mdx

@@ -114,7 +114,7 @@ You can use the [Read Replica feature](/managed-databases-for-postgresql-and-mys
 
 ## If my main node becomes unavailable, is my Read Replica automatically promoted to the main node?
 
-No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) procedure.
+No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/#how-to-promote-a-read-replica) procedure.
 
 ## Why is my number of active backups/snapshots exceeding the quota?
 

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

@@ -31,7 +31,7 @@ The clone feature allows you to create a new Database Instance from an existing
 6. Enter a name for your database or leave the default name suggested by the Scaleway console.
 7. Select a node type. You can keep the same node type, or upgrade to a bigger one.
     <Message type="important">
-      If you have a Database Instance using a Local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.
+      If you have a Database Instance using a Local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/manage-volumes/) to Block Storage first.
       </Message>
 8. Click **Clone Database Instance**.
 

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

@@ -19,7 +19,7 @@ You can change your Database Instance node type and enable High Availability aft
 ## How to change the node type
 
 <Message type="important">
-  If you have a Database Instance that uses a Local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.
+  If you have a Database Instance that uses a Local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/manage-volumes/) to Block Storage first.
 </Message>
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.

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

@@ -40,7 +40,7 @@ A Read Replica is a live copy of a Database Instance that behaves like an Instan
     </Message>
 
     <Message type="important">
-    If you select **Public network**, you can [attach a Private Network](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-manage-private-networks) to your Read Replica after its creation. If you choose to attach your Read Replica to a Private Network, you will not be able to add a Public Network to the same Read Replica later via the Scaleway console. You can, however, use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/) to do so via a command line or Terraform/OpenTofu.
+    If you select **Public network**, you can [attach a Private Network](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/#how-to-manage-private-networks) to your Read Replica after its creation. If you choose to attach your Read Replica to a Private Network, you will not be able to add a Public Network to the same Read Replica later via the Scaleway console. You can, however, use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/) to do so via a command line or Terraform/OpenTofu.
     </Message>
 8. Click **Create Read Replica**. A list of your Read Replicas displays.
     <Message type="important">

pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx

@@ -20,7 +20,7 @@ If your database engine is outdated, you can upgrade the version to the latest o
 <Message type="important">
 The version upgrade is only available for:
   - Database Instances using engine versions preceding the most recent version available.
-  - Database Instances using Block volumes. If your Database Instance uses a Local volume, you must first [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to a Block volume and try again.
+  - Database Instances using Block volumes. If your Database Instance uses a Local volume, you must first [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/manage-volumes/) to a Block volume and try again.
 </Message>
 
 <Requirements />
@@ -67,7 +67,7 @@ We recommend you remove the identified instances before continuing.
     <Message type="important">
       When you upgrade to a new version:
         - There is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop any write operations running on your applications during the upgrade. If you let them run during the process, the data will be stored only in the source Database Instance.
-        - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [enable HA](/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes/enable-high-availability) after the upgrade is complete. The same applies when upgrading [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas).
+        - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [enable HA](/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes/#how-to-enable-high-availability) after the upgrade is complete. The same applies when upgrading [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas).
         - Database Instance [advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) are synced as long as they are still available on the new database engine version.
     </Message>
 

pages/managed-databases-for-postgresql-and-mysql/reference-content/security-and-reliability.mdx

@@ -61,11 +61,11 @@ Creating, deleting, and promoting a Read Replica are actions triggered by you. S
     The time it takes to create the Read Replica depends on the volume of data being replicated.
   </Message>
 
-When [promoting a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) to a main node, make sure that the main node has completed all ongoing operations and that the Read Replica lag is down to zero before promoting it.
+When [promoting a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/#how-to-promote-a-read-replica) to a main node, make sure that the main node has completed all ongoing operations and that the Read Replica lag is down to zero before promoting it.
 
 If ongoing operations are not complete before the promote operation starts, some operations from the main node might not be contained in the newly promoted node.
 
-Refer to the [How to manage Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) documentation page for more information.
+Refer to the [How to manage Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/#how-to-promote-a-read-replica) documentation page for more information.
 
 
 ## Monitoring

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

@@ -23,7 +23,7 @@ You can carry out the following actions:
 
 1. [Monitor usage metrics on Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-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 [upgrade your Instance](/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database) if necessary.
+    - 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 [upgrade your Instance](/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version/) if necessary.
     - Check if there are slow queries in the Database Instance log. Huge or sub-optimized queries can slow down the instance significantly, or even fill up all the memory and trigger OOM kills.
 
 2. Try connecting to the Database Instance in a [Private Network](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/#how-to-connect-to-a-database-instance-through-a-private-network). Public endpoint traffic for Managed Databases for MySQL and PostgreSQL goes through a load balancer, which adds significant latency. Using a Private Network also ensures better security, which makes it the recommended way to connect to a Managed Database.