fix(nav): fix navigation

Author: bene2k1

menu/navigation.json

@@ -957,7 +957,7 @@
                 "items": [
                   {
                     "label": "Bare Metal shared responsibility model",
-                    "slug": "../elastic-metal/reference-content/shared-responsibility-model"
+                    "slug": "../../elastic-metal/reference-content/shared-responsibility-model"
                   }
                 ],
                 "label": "Additional Content",
@@ -1243,7 +1243,7 @@
                 "items": [
                   {
                     "label": "Bare Metal shared responsibility model",
-                    "slug": "../elastic-metal/reference-content/shared-responsibility-model"
+                    "slug": "../../elastic-metal/reference-content/shared-responsibility-model"
                   },
                   {
                     "label": "Dedibox datasheet",

pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx

@@ -13,7 +13,7 @@ categories:
   - dedibox-servers
 ---
 
-A hardware RAID is a type of [RAID](/hardware/concepts/#raid) implementation where construction and management of the RAID is performed on dedicated hardware, independently of the operating system.
+A hardware RAID is a type of [RAID](/dedibox-hardware/concepts/#raid) implementation where construction and management of the RAID is performed on dedicated hardware, independently of the operating system.
 
 The logical disks of the RAID array are managed by a physical controller, sitting on the PCI bus, which presents only the logical volumes to the operating system. The RAID controller manages the RAID using its own CPU and RAM, without delegating tasks to the main CPU of the machine.
 

pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx

@@ -27,7 +27,7 @@ Each Elastic Metal server uses a RAID1 configuration after installation from the
 ## Removing the failed disk from the RAID configuration
 
 <Message type="tip">
-  We recommend [backing up your data](/en/docs/tutorials/restic-s3-backup/) before proceeding.
+  We recommend [backing up your data](/tutorials/restic-s3-backup/) before proceeding.
 </Message>
 
 1. Boot server in [rescue mode](/elastic-metal/how-to/use-rescue-mode/) from the Scaleway console.

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](/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](/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.