chore(gen): fix 200s with missing anchors

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

@@ -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

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

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/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>