chore(gen): fix 200s with missing anchors

SamyOubouaziz · SamyOubouaziz · commit 26737050d09e · 2024-11-29T12:18:28.000+01:00
diff --git a/compute/gpu/how-to/use-gpu-with-docker.mdx b/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.
diff --git a/compute/instances/how-to/manage-volumes.mdx b/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**.  
diff --git a/storage/block/concepts.mdx b/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/).
diff --git a/storage/block/quickstart.mdx b/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" />
 
diff --git a/storage/object/api-cli/bucket-policy.mdx b/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
diff --git a/storage/object/api-cli/bucket-website-api.mdx b/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
     ```
diff --git a/storage/object/api-cli/create-bucket-policy.mdx b/storage/object/api-cli/create-bucket-policy.mdx
@@ -58,7 +58,7 @@ To create and apply a bucket policy from the [Scaleway console](https://console/
 4. Replace the `<BUCKET_NAME>` placeholders with the name of the concerned bucket. Refer to the [resource documentation](/storage/object/api-cli/bucket-policy/#resource) for more information.
 
 <Message type="note">
-Refer to the [Bucket policies description](/storage/object/api-cli/bucket-policy/#bucket-policy-description) for more details on each string.
+Refer to the [Bucket policies description](/storage/object/api-cli/bucket-policy/#bucket-policies-description) for more details on each string.
 </Message>
 
 ## How to apply a bucket policy
diff --git a/storage/object/api-cli/lifecycle-rules-api.mdx b/storage/object/api-cli/lifecycle-rules-api.mdx
@@ -194,7 +194,7 @@ The lifecycle configuration above translates to the following effective rules:
 - `mytagvalue2` is set to expire after one day.
 
 <Message type="note">
-  To see examples of lifecycle rules API requests, refer to the Bucket Operations [documentation page](/storage/object/api-cli/bucket-operations/#put-bucket-lifecycle).
+  To see examples of lifecycle rules API requests, refer to the Bucket Operations [documentation page](/storage/object/api-cli/bucket-operations/#putbucketlifecycle).
 </Message>
 
 ## Setting rules for incomplete multipart uploads
@@ -203,7 +203,7 @@ When using the `awscli` to perform a [multipart upload](/storage/object/api-cli/
 
 You can automate the removal of incomplete multipart uploads by adding or uploading a lifecycle configuration to your bucket. The setup can be done via an API call or an [AWS-CLI](/storage/object/api-cli/object-storage-aws-cli/) command.
 
-Send a [PutBucketLifecycle](/storage/object/api-cli/bucket-operations/#get-bucket-lifecycle) request with the following XML payload:
+Send a [PutBucketLifecycle](/storage/object/api-cli/bucket-operations/#getbucketlifecycle) request with the following XML payload:
 
 ```xml no-copy
 <?xml version="1.0" encoding="UTF-8"?>
diff --git a/storage/object/api-cli/object-lock.mdx b/storage/object/api-cli/object-lock.mdx
@@ -246,7 +246,7 @@ When this mode is set, all users with [permission](/identity-and-access-manageme
 <Message type="note">
   The **Governance** mode ensures extra protection before any alterations can be completed. An object can be permanently deleted only if:
     - A retention rule is applied, the governance retention date must be anterior to the present time
-    - The object does not have a legal hold in place. If it does, the legal hold [status token](/storage/object/api-cli/object-lock/#-XML-Legal-Hold-Configuration-Token) must be set to OFF before deletion.
+    - The object does not have a legal hold in place. If it does, the legal hold [status token](/storage/object/api-cli/object-lock/#xml-legal-hold-configuration-token) must be set to OFF before deletion.
       When the above criteria are met, you will be able to use `delete-object --version-id` to permanently delete an object.
 </Message>
 
diff --git a/storage/object/api-cli/share-buckets-read-only.mdx b/storage/object/api-cli/share-buckets-read-only.mdx
@@ -60,9 +60,9 @@ Specify which resources they can access under **Resource**:
     ]
 }
 ```
-Apply the policy using the [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#put-bucket-policy) API call or run the following aws-cli command:
+Apply the policy using the [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#putbucketpolicy) API call or run the following aws-cli command:
 
 ```
 aws s3api put-bucket-policy --bucket <SOURCE_BUCKET> --profile default_project --policy file://bucket-policy.json
 ```
-You can provide the user in Organization B with the name of your bucket. If the policy is correctly applied, they will be able to see bucket A1 included in their bucket list when running `List_Buckets`. If they know the name of an object, they can view their details by running [`Get_Object`](/storage/object/api-cli/object-operations/#get-object).
+You can provide the user in Organization B with the name of your bucket. If the policy is correctly applied, they will be able to see bucket A1 included in their bucket list when running `List_Buckets`. If they know the name of an object, they can view their details by running [`Get_Object`](/storage/object/api-cli/object-operations/#getobject).
diff --git a/storage/object/api-cli/using-api-call-list.mdx b/storage/object/api-cli/using-api-call-list.mdx
@@ -61,7 +61,7 @@ Status:
 |  [HeadBucket](/storage/object/api-cli/bucket-operations/#headbucket) |  Checks if the bucket exists | ✅ |
 |  [ListObjects](/storage/object/api-cli/bucket-operations/#listobjects) |  Lists objects in the bucket | ✅ |
 |  ListObjectsV2 | Returns some or all (up to 1,000) of the objects in a bucket | ✅ |
-|  [ListObjectVersions](/storage/object/api-cli/bucket-operations/#getbucketobjectversion) |  Returns metadata about all the versions of objects in a bucket | ✅ |
+|  [ListObjectVersions](/storage/object/api-cli/bucket-operations/#listobjectversions) |  Returns metadata about all the versions of objects in a bucket | ✅ |
 |  [PutBucketAcl](/storage/object/api-cli/bucket-operations/#putbucketacl) |  Configures the Access Control List of a bucket | ✅ |
 |  [PutBucketCors](/storage/object/api-cli/bucket-operations/#putbucketcors) |  Configures [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) on a bucket | ✅ |
 |  PutBucketLifecycle |  Creates a new lifecycle configuration or replaces an existing bucket lifecycle configuration | ❗ |
diff --git a/storage/object/index.mdx b/storage/object/index.mdx
@@ -66,7 +66,7 @@ meta:
     />
     <DefaultCard
         title="Aborting Incomplete Multipart Uploads with MinIO Client"
-        url="#aborting-a-multipart-upload"
+        url="/api-cli/multipart-uploads/#aborting-a-multipart-upload"
         label="Read more"
     />
 </Grid>
diff --git a/storage/object/reference-content/optimize-object-storage-performance.mdx b/storage/object/reference-content/optimize-object-storage-performance.mdx
@@ -14,7 +14,7 @@ categories:
   - object-storage
 ---
 
-[Scaleway Object Storage](/storage/object/concepts/#object-storage) is a highly resilient and versatile service that guarantees the reliability and accessibility of your data, while being fully [Amazon S3-compatible](/storage/object/concepts/#s3) and user-friendly.
+[Scaleway Object Storage](/storage/object/concepts/#object-storage) is a highly resilient and versatile service that guarantees the reliability and accessibility of your data, while being fully [Amazon S3-compatible](/storage/object/concepts/#amazon-s3) and user-friendly.
 
 Even though it is designed to provide best-in-class latency and throughput, user infrastructure plays a predominant role in achieving optimum efficiency, as many different factors can have an impact on performance, such as your hardware, your software stack, or the way you manage your objects.
 
@@ -50,7 +50,7 @@ For example, if the most CPU-intensive operation uses 20% of your CPU, you can e
 
 ### Geographic location
 
-The physical distance to the hardware hosting your Object Storage can also have an impact on performance, especially on latency. Make sure to benchmark the different [regions](/storage/object/concepts/##region-and-availability-zone) where Object Storage is available to compare latency on your mission-critical operations.
+The physical distance to the hardware hosting your Object Storage can also have an impact on performance, especially on latency. Make sure to benchmark the different [regions](/storage/object/concepts/#region-and-availability-zone) where Object Storage is available to compare latency on your mission-critical operations.
 
 For instance, media and content distribution are often heavily affected by the physical distance between the host and the client, as objects are usually large in this scenario.
 

Original file line number	Diff line number	Diff line change
`@@ -36,4 +36,4 @@ A Storage Area Network (SAN) consists of interconnected machines, network infras`
`36`	`36`
`37`	`37`	`## Volumes`
`38`	`38`
`39`		`-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/).`
	`39`	`+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/).`
Original file line number	Diff line number	Diff line change
`@@ -60,9 +60,9 @@ Specify which resources they can access under Resource:`
`60`	`60`	`]`
`61`	`61`	`}`
`62`	`62`	```
`63`		`-Apply the policy using the [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#put-bucket-policy) API call or run the following aws-cli command:`
	`63`	`+Apply the policy using the [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#putbucketpolicy) API call or run the following aws-cli command:`
`64`	`64`
`65`	`65`	```
`66`	`66`	`aws s3api put-bucket-policy --bucket <SOURCE_BUCKET> --profile default_project --policy file://bucket-policy.json`
`67`	`67`	```
`68`		-You can provide the user in Organization B with the name of your bucket. If the policy is correctly applied, they will be able to see bucket A1 included in their bucket list when running `List_Buckets`. If they know the name of an object, they can view their details by running [`Get_Object`](/storage/object/api-cli/object-operations/#get-object).
	`68`	+You can provide the user in Organization B with the name of your bucket. If the policy is correctly applied, they will be able to see bucket A1 included in their bucket list when running `List_Buckets`. If they know the name of an object, they can view their details by running [`Get_Object`](/storage/object/api-cli/object-operations/#getobject).