fix(gen): update links

Author: bene2k1

pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx

@@ -40,5 +40,5 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an
       - When switching from a Local volume to a Block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage.
       - Disk size cannot be reduced, so when switching from Local to Block, the volume size remains the same by default.
       - When switching from a Block to a Local volume, make sure to select a node with a Local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a Local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance.
-      - When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
+      - When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/managed-databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
     </Message>

pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx

@@ -35,7 +35,7 @@ Backups are used when your Database Instance's storage option is a Local volume.
   <br />
   By default, the Database Instance creation date is used as the base timestamp for the automated backups. When you change the schedule configuration, the moment you validated the new configuration becomes the new base timestamp. For example, if at 8 a.m. on a Thursday you update the autobackup frequency to 24h, your next autobackup will be created at 8 a.m. on a Friday.
   <br />
-  When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
+  When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/managed-databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
 </Message>
 
 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays.

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

@@ -147,7 +147,7 @@ Two types of engine version upgrades are available for your databases:
 
 ### Database extensions
 
-For security reasons, we support a defined set of [databases extensions for PostgreSQL](/databases-for-postgresql-and-mysql/faq/#which-postgresql-extensions-are-available).
+For security reasons, we support a defined set of [databases extensions for PostgreSQL](/managed-databases-for-postgresql-and-mysql/faq/#which-postgresql-extensions-are-available).
 
 For security and reliability reasons, we only support a specific version of each extension for each PostgreSQL major version.
 

pages/managed-databases-for-redis/reference-content/ensuring-data-persistence.mdx

@@ -21,7 +21,7 @@ To avoid this, Redis™<sup>*</sup> natively supports persistence by performing
 
 This feature is supported and managed by Scaleway with Managed Databases for Redis™.
 
-Furthermore, you can leverage the [cluster mode](/databases-for-redis/faq/#what-is-the-logic-behind-the-cluster-mode) to ensure the durability of your data.
+Furthermore, you can leverage the [cluster mode](/managed-databases-for-redis/faq/#what-is-the-logic-behind-the-cluster-mode) to ensure the durability of your data.
 
 <Message type="important">
   Scaleway Managed Database for Redis™ is currently best suited for caching use cases. The data persistence mechanism presented on this page do not guarantee data recovery in case of incident.
@@ -43,7 +43,7 @@ When you create a new Redis™ Database Instance, a Redis™ snapshot is also au
 
 ## Cluster mode
 
-If you want to benefit from fault-tolerant architecture in some use cases, we recommend you deploy Redis™ in [cluster mode](/databases-for-redis/faq/#what-is-the-logic-behind-the-cluster-mode), where each primary node is deployed with a replica node.
+If you want to benefit from fault-tolerant architecture in some use cases, we recommend you deploy Redis™ in [cluster mode](/managed-databases-for-redis/faq/#what-is-the-logic-behind-the-cluster-mode), where each primary node is deployed with a replica node.
 
 A Redis cluster contains a minimum of three nodes and up to six nodes. Each node contains a source and a replica. The cluster nodes use hash partitioning to split the keyspace into key slots. Each replica copies the data of a specific source and can be reassigned to replicate another source or be elected as a source node if needed. This is recommended for scaling as the operation is spread across multiple nodes instead of having a single entry point.
 

pages/vpc/reference-content/getting-most-private-networks.mdx

@@ -127,6 +127,6 @@ Different types of Scaleway resources may have different requirements and possib
 | Compatible with private IPv6 | No               | No                          | No              | No            |
 | Compatible with reserved IPs | No               | No                          | Yes             | Yes           |
 | Additional information       | Must have at least one of <br/> private and/or public endpoint | Must have at least one of <br/> private and/or public endpoint | -- | Private LBs must have a PN |
-| Documentation | [Go](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/databases-for-redis/faq/#what-is-the-private-networks-feature-for-redistm-database-instances) | [Go](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/load-balancer/how-to/use-with-private-network/)
+| Documentation | [Go](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/managed-databases-for-redis/faq/#what-is-the-private-networks-feature-for-redistm-database-instances) | [Go](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/load-balancer/how-to/use-with-private-network/)