chore(gen): fix 200s with missing anchors (#4058)

* chore(gen): fix 200s with missing anchors

* chore(gen): fix 200s with missing anchors

* chore(gen): fix 200s with missing anchors

Author: SamyOubouaziz

compute/gpu/how-to/use-gpu-with-docker.mdx

@@ -75,7 +75,7 @@ In the above example, everything in the `/root/mydata` directory on the Instance
 
 ### How to map Block Storage volumes
 
-You can also map [Block Storage](https://www.scaleway.com/en/block-storage/) volumes into your containers. Block Storage is fully backed by SSDs. These three-time replicated, high-speed drives allow up to 5,000 IOPS. Once [attached](/storage/block/how-to/attach-a-volume/) and [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-volume) in the host OS of the GPU Instance, you can map the volume like a local volume, as we did above.
+You can also map [Block Storage](https://www.scaleway.com/en/block-storage/) volumes into your containers. Block Storage is fully backed by SSDs. These three-time replicated, high-speed drives allow up to 5,000 IOPS. Once [attached](/storage/block/how-to/attach-a-volume/) and [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) in the host OS of the GPU Instance, you can map the volume like a local volume, as we did above.
 
 <Message type="tip">
   [Block Storage](/storage/block/quickstart/) volumes are independent of your GPU Instance and provide three-time replicated storage. It is recommended to use Block Storage for storing your datasets, training logs, model source code, etc.

compute/instances/how-to/manage-volumes.mdx

@@ -32,7 +32,7 @@ categories:
 5. Click **Attach volume to Instance**.
 
     <Message type="tip">
-      Find out [how to mount a Block Storage volume to your Instance](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-volume).
+      Find out [how to mount a Block Storage volume to your Instance](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume).
     </Message>
     <Message type="note">
       To use **[Block Storage Low Latency](/storage/block/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.  
@@ -52,7 +52,7 @@ categories:
     </Message>
 
     <Message type="tip">
-      Refer to our [dedicated documentation](/storage/block/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume) to find out how to increase the partition size of your volume.
+      Refer to our [dedicated documentation](/storage/block/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase the partition size of your volume.
     </Message>
 
 ## How to detach a volume

containers/kubernetes/quickstart.mdx

@@ -35,19 +35,19 @@ Scaleway Kubernetes [Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsul
     </tr>
     <tr>
         <td>[<sup>4</sup> Introduction video to Kubernetes](/containers/kubernetes/videos/#introduction-to-kubernetes)</td>
-        <td>[<sup>11</sup> How does containerizing two simple applications with Docker sound](/containers/kubernetes/videos/#getting-started-with-kubernetes:-part-1-containers-and-docker)</td>
+        <td>[<sup>11</sup> How does containerizing two simple applications with Docker sound](/containers/kubernetes/videos/#getting-started-with-kubernetes-part-1-containers-and-docker)</td>
     </tr>
     <tr>
         <td>[<sup>5</sup> Scaleway Instances](/compute/instances/reference-content/choosing-instance-type/)</td>
         <td>[<sup>12</sup> Docker concepts](/containers/container-registry/concepts/#docker)</td>
     </tr>
     <tr>
         <td>[<sup>6</sup> How to connect to a cluster with kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/)</td>
-        <td>[<sup>13</sup> How to deploy a containerized application with Kubernetes Kapsule](/containers/kubernetes/videos/#getting-started-with-kubernetes:-part-2-deloying-an-app-with-kapsule)</td>
+        <td>[<sup>13</sup> How to deploy a containerized application with Kubernetes Kapsule](/containers/kubernetes/videos/#getting-started-with-kubernetes-part-2-deloying-an-app-with-kapsule)</td>
     </tr>
     <tr>
         <td>[<sup>7</sup> kubectl definition](/containers/kubernetes/concepts/#kubectl)</td>
-        <td>[<sup>14</sup> How to add a load balancer service to your Scaleway Kubernetes Kapsule](/containers/kubernetes/videos/#getting-started-with-kubernetes:-part-3-load-balancers)</td>
+        <td>[<sup>14</sup> How to add a load balancer service to your Scaleway Kubernetes Kapsule](/containers/kubernetes/videos/#getting-started-with-kubernetes-part-3-load-balancers)</td>
     </tr>
 </table>
 </font>

dedibox-network/dns/how-to/configure-secondary-dns.mdx

@@ -31,7 +31,7 @@ This how-to assumes that you want to manage your domains exclusively with BIND.
 ## How to configure BIND
 
 1. If you use a management panel for your server, add the domain in your panel.
-2. Log in to your server as root [via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#how-to-connect-via-ssh).
+2. Log in to your server as root [via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh).
 3. Use your favorite text editor to edit the general BIND configuration file, located at `/etc/bind/named.conf`. The configuration of your domain should be as follows (replace `domain.fr` with your domain):
     ```
     zone "domain.fr" { 

dedibox/dedicated-servers/how-to/get-started-with-server.mdx

@@ -28,7 +28,7 @@ Dedibox servers do not come with a graphical interface by default. Instead, all
 - Create, edit, and delete files and directories
 - Configure server settings
 
-You can [connect to the shell via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#how-to-connect-via-ssh). For essential commands, refer to our [basic Linux commands guide](/dedibox/dedicated-servers/reference-content/basic-linux-commands/).
+You can [connect to the shell via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). For essential commands, refer to our [basic Linux commands guide](/dedibox/dedicated-servers/reference-content/basic-linux-commands/).
 
 ## Using a graphical desktop
 

dedibox/dedicated-servers/how-to/use-rescue-mode.mdx

@@ -46,7 +46,7 @@ We offer three types of rescue modes:
 
 To access your server in Linux/FreeBSD rescue mode:
 
-1. [Connect to your server via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#how-to-connect-via-ssh).
+1. [Connect to your server via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh).
 2. Use the login credentials provided on the server’s status page in the console. Note that it may take approximately two minutes for rescue mode to fully initialize.
 
    Once connected, you can operate rescue mode like a standard distribution, installing tools such as text editors or FTP clients as needed. Keep in mind that the size of the ramdisk is limited.

environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx

@@ -69,7 +69,7 @@ All calculations will use the following variables:
     The acronyms used below are based on the French phrases for these terms.
 </Message>
 
-- [dU](/environmental-footprint/environmental-footprint/concepts/##du-duration-of-use): duration of use of the equipment included in the study
+- [dU](/environmental-footprint/environmental-footprint/concepts/#du-duration-of-use): duration of use of the equipment included in the study
 - [DDV](/environmental-footprint/environmental-footprint/concepts/#ddvdc-data-center-lifespan): lifespan
 - [PuissEqt](/environmental-footprint/environmental-footprint/concepts/#puisseqt-rated-power): rated power of the equipment
 - [PuissCommDC](/environmental-footprint/environmental-footprint/concepts/#puisscommdc): proportion of the data center's installed power reserved by customers

faq/objectstorage.mdx

@@ -222,7 +222,7 @@ An object stored in Glacier class is listed but cannot be downloaded instantly.
 We recommend that you use Glacier to archive data that you may need only once or twice within a decade.
 
 <Message type="important">
-  The time it takes to restore an object depends on the size of the object and if [multipart](/storage/object/concepts/#multipart-uploads) is configured. It can take anywhere from a few minutes to 24 hours for restore to start (for objects larger than 1 MB). 
+  The time it takes to restore an object depends on the size of the object and if [multipart](/storage/object/concepts/#multipart-uploads-uploads) is configured. It can take anywhere from a few minutes to 24 hours for restore to start (for objects larger than 1 MB). 
   Unfortunately, we are unable to provide estimates of how long data retrieval takes for each use case.
 
   To facilitate restoration and ensure the fast restitution of your data, we recommend you use average-sized files (larger than 1 MB).

managed-services/iot-hub/quickstart.mdx

@@ -13,7 +13,7 @@ categories:
   - managed-services
 ---
 
-[Scaleway IoT Hub](/managed-services/iot-hub/concepts/#iot-hub) is a resilient and multi-protocol message broker with export capabilities. Devices can connect to the hub to exchange messages, by which they get access to cloud services. Hub Routes also allow devices to push messages to other, non MQTT, services.
+[Scaleway IoT Hub](/managed-services/iot-hub/quickstart/) is a resilient and multi-protocol message broker with export capabilities. Devices can connect to the hub to exchange messages, by which they get access to cloud services. Hub Routes also allow devices to push messages to other, non MQTT, services.
 
 In this Quickstart, we show you how to create your first IoT Hub to connect objects, Scaleway services and applications.
 

serverless/containers/api-cli/migrate-external-image-to-scaleway-registry.mdx

@@ -17,7 +17,7 @@ Serverless Containers rely on images that can be stored in the Scaleway Containe
 
 <Macro id="container-registry-note" />
 
-This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/containers/container-registry/#container-registry).
+This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/containers/container-registry/concepts/#container-registry).
 
 <Macro id="requirements" />
 

serverless/containers/troubleshooting/cannot-deploy-image.mdx

@@ -25,7 +25,7 @@ I am unable to deploy my image using Serverless Containers.
 
 - Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU.
 
-- Make sure you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation for more information.
+- Make sure you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/containers/reference-content/containers-limitations/#architecture) documentation for more information.
 
 - Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/).
 

serverless/functions/api-cli/deploy-function-api.mdx

@@ -81,7 +81,7 @@ Refer to the [Scaleway Developers website](https://www.scaleway.com/en/developer
       ```
     </Message>
 
-4. Upload your zip file [using the Scaleway console](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-upload-your-zip-file-to-the-scaleway-console) or [using the Scaleway API](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-upload-your-zip-file-using-the-scaleway-api).
+4. Upload your zip file [using the Scaleway console](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-upload-your-zip-file-to-the-scaleway-console) or [using the Scaleway API](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-upload-your-zip-file).
 
 5. Run the following command to deploy your function:
 

serverless/functions/how-to/package-function-dependencies-in-zip.mdx

@@ -46,7 +46,7 @@ The example above will create a `.zip` archive that contains the myFunction fold
 <Tabs id="tab1">
   <TabsTab label="Scaleway Console">
 
-    1. Package your dependencies on your local computer, as explained in the [Configure your package](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-zip-your-function) section.
+    1. Package your dependencies on your local computer, as explained in the [Configure your package](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-package-a-function-into-zip-file) section.
     2. Create a **ZIP** archive containing the files and folders you need.
     3. Go to the [Functions](https://console.scaleway.com/functions/namespaces) section of the Scaleway console and click on the functions namespace you want to configure.
     4. Click **+ Create function**. The function creation page displays.

serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry.mdx

@@ -17,7 +17,7 @@ Serverless Jobs rely on container images. These images can be stored in the Scal
 
 <Macro id="container-registry-note" />
 
-This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/containers/container-registry/#container-registry).
+This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/containers/container-registry/concepts/#container-registry).
 
 <Macro id="requirements" />
 

serverless/jobs/troubleshooting/job-in-error-state.mdx

@@ -19,6 +19,6 @@ My job run is in an error state.
 
 ## Possible solutions
 
-- Make sure that you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation for more information.
+- Make sure that you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/jobs/reference-content/jobs-limitations/#architecture) documentation for more information.
 
 - Make sure that your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/).

serverless/messaging/quickstart.mdx

@@ -336,7 +336,7 @@ Credentials for NATS accounts are not granular: they necessarily give full read
 
 ### How to create and manage queues, messages and streams
 
-All further actions related to publishing, processing and managing messages, subjects, queues and streams can be done via a supported CLI or SDK. See our documentation on [NATS CLI and SDKs](/serverless/messaging/reference-content/nats-overview#further-actions:-nats-cli-and-nats-sdk) for more information. You can also check out our tutorial on [creating a serverless architecture for handling large messages](/tutorials/large-messages/) with Scaleway Messaging and Queuing NATS.
+All further actions related to publishing, processing and managing messages, subjects, queues and streams can be done via a supported CLI or SDK. See our documentation on [NATS CLI and SDKs](/serverless/messaging/reference-content/nats-overview/#further-actions-nats-cli-and-nats-sdk) for more information. You can also check out our tutorial on [creating a serverless architecture for handling large messages](/tutorials/large-messages/) with Scaleway Messaging and Queuing NATS.
 
 ### How to delete a NATS account
 

serverless/messaging/reference-content/sns-overview.mdx

@@ -18,7 +18,7 @@ validation_frequency: 8
 
 SNS is a managed messaging service developed by AWS and supported by Scaleway Messaging and Queuing. It is often coupled to work with [SQS](/serverless/messaging/reference-content/sqs-overview/).
 
-SNS (Simple Notification Service) was released in 2010. It enables users to interconnect their applications and systems using a [publish/subscribe](/serverless/messaging/concepts#publishsubscribe) pattern. Many publishers can send messages to [topics](/serverless/messaging/concepts#topicexchange), while consumers, e.g. applications, can subscribe to topics to receive all (or a subset) of messages sent to this topic. Scaleway Messaging and Queuing makes it easy to migrate your SNS-connected applications by providing a dedicated protocol gateway.
+SNS (Simple Notification Service) was released in 2010. It enables users to interconnect their applications and systems using a [publish/subscribe](/serverless/messaging/concepts#publishsubscribe) pattern. Many publishers can send messages to [topics](/serverless/messaging/concepts#topic), while consumers, e.g. applications, can subscribe to topics to receive all (or a subset) of messages sent to this topic. Scaleway Messaging and Queuing makes it easy to migrate your SNS-connected applications by providing a dedicated protocol gateway.
 
 <Message type="note">
   Some SNS features are not yet available with Scaleway Messaging and Queuing. Supported subscribers are currently limited to:

storage/block/concepts.mdx

@@ -36,4 +36,4 @@ A Storage Area Network (SAN) consists of interconnected machines, network infras
 
 ## Volumes
 
-A volume is a storage space used by your Instances. Several volumes can be [attached to an Instance](/storage/block/how-to/attach-a-volume/). In addition, they can be [snapshotted](/storage/block/how-to/create-a-snapshot/), [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-volume) or [unmounted](/storage/block/api-cli/unmounting-a-volume/).
+A volume is a storage space used by your Instances. Several volumes can be [attached to an Instance](/storage/block/how-to/attach-a-volume/). In addition, they can be [snapshotted](/storage/block/how-to/create-a-snapshot/), [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) or [unmounted](/storage/block/api-cli/unmounting-a-volume/).

storage/block/how-to/increase-block-volume.mdx

@@ -30,7 +30,7 @@ categories:
     </Message>
 
     <Message type="tip">
-      Refer to our [dedicated documentation](/storage/block/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume) to find out how to increase your volume's partition size.
+      Refer to our [dedicated documentation](/storage/block/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase your volume's partition size.
     </Message>
 
 

storage/block/quickstart.mdx

@@ -16,7 +16,7 @@ categories:
 
 Scaleway [Block Storage](/storage/block/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/compute/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local Storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/compute/instances/concepts/#availability-zone).
 
-From the user's point of view, once [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-volume), the block device behaves like a regular disk.
+From the user's point of view, once [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume), the block device behaves like a regular disk.
 
 <Macro id="requirements" />
 

storage/object/api-cli/bucket-policy.mdx

@@ -76,7 +76,7 @@ Bucket policies use a JSON-based access policy language and are composed of stri
 ```
 
 <Message type="note">
-    Refer to the [documentation on bucket policy versions](/storage/object/api-cli/combining-iam-and-object-storage/#note-on-bucket-policy-versions) for more information.
+    Refer to the [documentation on bucket policy versions](/storage/object/api-cli/bucket-policy/#bucket-policies-versions) for more information.
 </Message>
 
 ### Id

storage/object/api-cli/bucket-website-api.mdx

@@ -172,7 +172,7 @@ If you want your website to be accessible, you need to set up a bucket policy.
 
     - `"<BUCKET_NAME>/*"` - Grants access to all objects inside a bucket, but not to the bucket itself.
     - `"<BUCKET_NAME>/<PREFIX>/*"` - Grants access only to objects with the specified prefix inside a bucket, but not to the bucket itself. For example, if you apply a bucket policy that specifies `"my_files/movie/*"` under **Resource**, you would grant access to all objects with the `movie/` prefix, but not to other objects in `my_files/` bucket.
-3. Use [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#put-bucket-policy) or run the following command to implement the policy via the AWS-CLI:
+3. Use [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#putbucketpolicy) or run the following command to implement the policy via the AWS-CLI:
     ```
     aws s3api put-bucket-policy --bucket <BUCKET_NAME> --policy file://bucket-policy.json
     ```