fix(nav): fix navigation

Author: bene2k1

menu/navigation.json

@@ -2281,7 +2281,7 @@
               }
             ],
             "label": "PostgreSQL and MySQL",
-            "slug": "postgresql-and-mysql"
+            "slug": "managed-databases-for-postgresql-and-mysql"
           },
           {
             "items": [

pages/elastic-metal/reference-content/shared-responsibility-model.mdx

@@ -37,7 +37,7 @@ Bare Metal Products target the following power supplies and connectivity SLOs:
 The detailed SLAs measurements and guarantees can be found at [Service Level Agreement for Bare Metal Services](https://www.scaleway.com/en/bare-metal/sla/).
 
 Once the resource is in your hands, we have no access to the machine and therefore no way to monitor its operation.
-In case of any operational issues, we invite you to consult our [documentation](/bare-metal/) or [create a ticket](https://console.scaleway.com/support/tickets/create) with our support team. We will then do our utmost to ensure that you regain access to your resources as quickly as possible.
+In case of any operational issues, we invite you to consult our documentation or [create a ticket](https://console.scaleway.com/support/tickets/create) with our support team. We will then do our utmost to ensure that you regain access to your resources as quickly as possible.
 
 ### Backups and snapshots
 

pages/generative-apis/api-cli/using-generative-apis.mdx

@@ -63,7 +63,7 @@ Querying AI models hosted by Scaleway Generative APIs will require any of the fo
 
 ## Projects
 
-You can scope your Generative APIs consumption to a [Project](identity-and-access-management/iam/concepts/#project). This is helpful to restrict IAM users’ access to only the Project they are working on, or to isolate your bills between Projects.
+You can scope your Generative APIs consumption to a [Project](/iam/concepts/#project). This is helpful to restrict IAM users’ access to only the Project they are working on, or to isolate your bills between Projects.
 
 1. Find your Project ID in your [Project settings](https://console.scaleway.com/project/settings)
 2. Insert your Project ID in the Generative APIs service URL, for example:

pages/transactional-email/how-to/create-webhooks.mdx

@@ -46,7 +46,7 @@ You can create only one webhook per domain.
     </Message>
     - Select an existing topic. Existing topics are displayed based on the region you select.
     <Message type="tip">
-    If you do not have a topic, you can [create one](serverless/messaging/how-to/create-manage-topics/) with Scaleway Topics and Events from the console.
+    If you do not have a topic, you can [create one](/serverless-messaging/how-to/create-manage-topics/) with Scaleway Topics and Events from the console.
     </Message>
     - Choose the email events that will trigger the webhook and send information to your selected topic.
     <Message type="note">

pages/vpc/reference-content/use-case-basic.mdx

@@ -85,7 +85,7 @@ Follow the steps below to create this infrastructure using the [Scaleway console
     <Message type="tip">
     If you are creating several Instances with the exact same configuration running the exact same template, consider creating just one Instance, configuring and installing it to communicate with the other resources inside and outside the VPC as required, then [creating an image](/instances/how-to/create-a-backup/) of this Instance and creating the remaining Instances [using this image](/instances/how-to/create-a-backup/#how-to-create-or-restore-an-instance-from-an-image).
     </Message>
-9. [Attach each Instance to the Private Network](/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) you created at step 2. Either let Scaleway automatically choose an IP from the Private Network's subnet for each Instance, or use [reserved IPs](s/network/ipam/how-to/reserve-ip/) to specify the IP for each Instance on the network.
+9. [Attach each Instance to the Private Network](/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) you created at step 2. Either let Scaleway automatically choose an IP from the Private Network's subnet for each Instance, or use [reserved IPs](/network/ipam/how-to/reserve-ip/) to specify the IP for each Instance on the network.
 10. [Create a Load Balancer](/load-balancer/how-to/create-load-balancer/), ensuring you assign a public (flexible) IP address. Do not yet create the frontends and backends.
 11. [Attach the Load Balancer to the Private Network](/load-balancer/how-to/use-with-private-network/#how-to-attach-a-private-network-to-your-load-balancer). As before, you can use an auto-selected IP, or a specific reserved IP from the subnet.
 12. [Create a frontend and backend for the Load Balancer](/load-balancer/how-to/create-frontends-backends/). Choose the most appropriate configuration for your purpose and application, following advice and tips in the linked documentation. When configuring the Load Balancer's backend servers, enter the private IP addresses of the Instances on the Private Network.