fix(gen): fix 404s / 200 w/o anchors (#4559)

SamyOubouaziz · bene2k1 · commit acc8a957b3dd · 2025-03-12T10:54:01.000+01:00
* fix(gen): fix 404s / 200 w/o anchors

* fix(gen): update
diff --git a/macros/developer-tools/scaleway-environment-variables.mdx b/macros/developer-tools/scaleway-environment-variables.mdx
@@ -2,7 +2,7 @@
 macro: scaleway-environment-variables
 ---
 
-# Reserved environment variables
+## Reserved environment variables
 
 The following standardized Scaleway environment variables are used for the CLI and API.
 
diff --git a/pages/billing/troubleshooting/index.mdx b/pages/billing/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+  title: &title Billing - Troubleshooting
+  description: &desc Billing Troubleshooting
+content:
+  h1: *title
+  paragraph: *desc
+---
diff --git a/pages/components/docs-editor.mdx b/pages/components/docs-editor.mdx
@@ -90,7 +90,7 @@ content:
   productLogo="cli"
   title="CLI"
   description="Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."
-  url="/foo/dd"
+  url="/#"
   label="Link"
 />
 ```
@@ -100,7 +100,7 @@ content:
   productLogo="cli"
   title="CLI"
   description="Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."
-  url="/foo/dd"
+  url="/#"
   label="Link"
 />
 
@@ -114,7 +114,7 @@ content:
 
   title="CLI"
   description="Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."
-  url="/foo/dd"
+  url="/#"
   label="Link"
 />
 ```
@@ -124,7 +124,7 @@ content:
 <ClickableBanner
   title="CLI"
   description="Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."
-  url="/foo/dd"
+  url="/#"
   label="Link"
 />
 
@@ -257,15 +257,15 @@ Example using `DefaultCard` in `Grid` wrapper.
 
 ```jsx
 <HelpBanner 
-  url="https://console.scaleway.com/support/tickets"
+  url="/#"
   title = 'Still need help?'
 />
 ``` 
 
 **Render**
 
 <HelpBanner 
-  url="https://console.scaleway.com/support/tickets"
+  url="/#"
   title = 'Still need help?'
 />
 
@@ -422,7 +422,7 @@ Props:
   productName="Instances"
   productLogo="instances"
   description="Lorem ipsum..."
-  url="/instances/quickstart"
+  url="/#"
   label="Instances quickstart"
 />
 ```
@@ -433,7 +433,7 @@ Props:
   productName="ProductHeader"
   productLogo="cli"
   description="ProductName quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat."
-  url="/instances/quickstart"
+  url="/#"
   label="Instances quickstart"
 />
 
@@ -442,7 +442,7 @@ Props:
 <ProductHeader
   productName="ProductHeader"
   description="ProductName quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat."
-  url="/instances/quickstart"
+  url="/#"
   label="Instances quickstart"
 />
 
@@ -463,7 +463,7 @@ The `icon` names are not random ones they come from Ultraviolet lib.
   icon="rocket"
   description="lorem ipsum dolor sit amet, consectetur adipiscing elit in in part of the description"
   label="Read More"
-  url="/hello/foo/"
+  url="/#"
 />
 ```
 
@@ -475,31 +475,31 @@ The `icon` names are not random ones they come from Ultraviolet lib.
   icon="rocket"
   description="Learn how to create, manage and delete a Kubernetes cluster in a few steps."
   label="Read More"
-  url="/elastic-metal/quickstart/"
+  url="/#"
 />
 
 <SummaryCard
   title="Concepts"
   icon="information-outline"
   description="Core concepts that give you a better understanding of Kubernetes Kapsule and Kosmos."
   label="Read More"
-  url="/secret-manager/concepts/"
+  url="/#"
 />
 
 <SummaryCard
   title="How-tos"
   icon="help-circle-outline"
   description="Check our guides to creating and managing Kubernetes clusters and their features."
   label="Read More"
-  url="/secret-manager/how-to/create-version/"
+  url="/#"
 />
 
 <SummaryCard
   title="Reference content"
   icon="book-open-outline"
   description="Guides to help you configuring your cluster and its advanced configuration."
   label="Read More"
-  url="/secret-manager/reference-content/data-encryption-with-secret-manager/"
+  url="/#"
 />
 </Grid>
 
diff --git a/pages/components/docs.mdx b/pages/components/docs.mdx
@@ -746,19 +746,19 @@ The above text come from a macro!
         - Choose an **Availability Zone**, which is the geographical region where your Instance will be deployed.
         - Choose an **Image** to run on your Instance. This can be an operating system, an InstantApp or a custom image. A complete list of all available Linux distributions and InstantApps can be found [here](https://www.scaleway.com/en/imagehub/).
         <Message type="note">
-          When choosing an image for an Enterprise Instance, be aware this Instance type is not compatible with bootscripts, except for [rescue mode](/instances/how-to/use-boot-modes#how-to-use-rescue-mode). InstantApps are also not available for this Instance type.
+          When choosing an image for an Enterprise Instance, be aware this Instance type is not compatible with bootscripts, except for [rescue mode](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode). InstantApps are also not available for this Instance type.
         </Message>
         - Choose an **Instance type**. Different Instance types have different prices, processing power, memory, storage options and bandwidth.
         - Add **Volumes**. Volumes are storage spaces used by your Instances.
-          - For **GP1 Instances** you can leave the default settings of a maximum local storage, or choose how much [local](/instances/concepts#local-volumes) and/or [block](/instances/concepts#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume.
+          - For **GP1 Instances** you can leave the default settings of a maximum local storage, or choose how much [local](/instances/concepts/#local-volumes) and/or [block](/instances/concepts/#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume.
           - **PRO2** and **Enterprise** Instances boot directly [on block volumes](/instances/concepts/#boot-on-block). You can add several block volumes and define how much storage you want for each.
             <Message type="important">
               Please note that:
                 - a volume with an OS image should be at least 10GB (125GB for a GPU OS).
                 - if several Block Storage volumes are connected to your Instance, the first volume will contain the OS and is required to boot the Instance. You can [change your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume) after you create the Instance.
                 - if you have two or more volumes with identical operating systems, or a volume with no operating system, choosing one of these as your boot volume may cause unpredictable boot behavior.
             </Message>
-        - Enter a **Name** for your Instance, or leave the randomly-generated name in place. Optionally, you can also add [tags](/instances/concepts#tags) to help you organize your Instance.
+        - Enter a **Name** for your Instance, or leave the randomly-generated name in place. Optionally, you can also add [tags](/instances/concepts/#tags) to help you organize your Instance.
         - Click **Advanced Options** if you want to configure a [flexible IP](/instances/concepts#flexible-ip), a local bootscript or a [cloud-init configuration](/instances/concepts#cloud-init). Otherwise, leave these options at their default values.
         - Verify the [SSH Keys](/account/concepts#ssh-key) that will give you access to your Instance.
         - Verify the **Estimated Cost** of your Instance, based on the specifications you chose.
diff --git a/pages/generative-apis/reference-content/adding-ai-to-intellij-using-continue.mdx b/pages/generative-apis/reference-content/adding-ai-to-intellij-using-continue.mdx
@@ -21,7 +21,7 @@ This guide will help you integrate AI-powered code models into JetBrain's Intell
 - A valid [API key](/iam/how-to/create-api-keys/) for API authentication
 - Installed [IntelliJ IDEA](https://www.jetbrains.com/idea/) on your local machine.
 
-## Install Continue in IntelliJ IDEA
+
 
 You can install Continue from the [JetBrains marketplace](https://plugins.jetbrains.com/plugin/22707-continue):
 
@@ -30,9 +30,9 @@ You can install Continue from the [JetBrains marketplace](https://plugins.jetbra
 3. Search for **Continue** and click **Install**.
 4. Restart IntelliJ IDEA after installation.
 
-### Configure Continue to use Scaleway’s Generative APIs
+## Configure Continue to use Scaleway’s Generative APIs
 
-#### Configure Continue through the graphical interface
+### Configure Continue through the graphical interface
 
 To link Continue with Scaleway's Generative APIs, you can use built-in menus from Continue in IntelliJ IDEA.
 
@@ -51,7 +51,7 @@ These actions will edit automatically your `config.json` file. To edit it manual
   Embeddings and autocomplete models are not yet supported through graphical interface configuration. To enable them, you need to edit the configuration manually, see [Configure Continue through configuration file](#configure-continue-through-configuration-file).
 </Message>
 
-#### Configure Continue through configuration file
+### Configure Continue through configuration file
 
 To link Continue with Scaleway’s Generative APIs, you need to configure the settings file:
 
@@ -90,7 +90,7 @@ To link Continue with Scaleway’s Generative APIs, you need to configure the se
   If you want to limit access to a specific Scaleway Project, you should add the field `"apiBase": "https://api.scaleway.ai/###PROJECT_ID###/v1/"` for each model (ie. `models`, `embeddingsProvider` and `tabAutocompleteModel`) since the default URL `https://api.scaleway.ai/v1/` can only be used with the `default` project.
 </Message>
 
-### Activate Continue in IntelliJ IDEA
+## Activate Continue in IntelliJ IDEA
 
 After configuring the API, activate Continue in IntelliJ IDEA:
 
@@ -101,7 +101,7 @@ After configuring the API, activate Continue in IntelliJ IDEA:
   Enabling tab completion **may lead to higher token consumption** as the model generates predictions for every keystroke. Be mindful of your API usage and adjust settings accordingly to avoid unexpected costs. For more information, refer to the [official Continue documentation](https://docs.continue.dev/reference#tabautocompleteoptions).
 </Message>
 
-### Going further
+## Going further
 
 You can add additional parameters to configure your model behaviour by editing `config.json`.
 For instance, you can add the following `systemMessage` value to modify LLM messages `"role":"system"` and/or `"role":"developer"` and provide less verbose answers:
diff --git a/pages/gpu/how-to/use-pipenv.mdx b/pages/gpu/how-to/use-pipenv.mdx
@@ -33,7 +33,7 @@ Pipenv is a powerful package and dependency manager for Python projects. It comb
 
 ## Accessing the preinstalled Pipenv virtual environment
 
-Refer to our [dedicated documentation](/gpu/how-to/use-preinstalled-env/#working-with-the-preinstalled-environment-on-ubuntu-focal-gpu-os-11) on how to access the Pipenv virtual environment from your Scaleway GPU Instance.
+Refer to our [dedicated documentation](/gpu/how-to/use-preinstalled-env/#working-with-the-preinstalled-environment-on-ubuntu-focal-gpu-os-12) on how to access the Pipenv virtual environment from your Scaleway GPU Instance.
 
 ## Managing packages with Pipenv
 
diff --git a/pages/gpu/how-to/use-preinstalled-env.mdx b/pages/gpu/how-to/use-preinstalled-env.mdx
@@ -19,7 +19,7 @@ GPU Instances have different types of preinstalled environments, depending on th
 |:----------------------:|:------------------:|:---------------------------------------------------------------:|------------------------------------------------|
 | Ubuntu Focal GPU OS 12 | Latest             | Nvidia drivers, Nvidia Docker environment (launch Docker container to access working environment) | Pipenv virtual environment accessed via Docker |
 
-Using the latest Ubuntu Focal GPU OS11 image gives you a minimal OS installation on which you can [launch](/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/gpu/reference-content/docker-images/). This gives you access to a preinstalled Python environment managed with pipenv. A number of useful AI core packages and tools are installed, including `scipy`, `numpy`, `scikit-learn`, `jupyter`, `tensorflow`, and the Scaleway SDK. Depending on the [Docker image you choose](/gpu/reference-content/docker-images/), other packages and tools will also be preinstalled, providing a convenient framework environment for you so that you can begin work immediately.
+Using the latest Ubuntu Focal GPU OS12 image gives you a minimal OS installation on which you can [launch](/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/gpu/reference-content/docker-images/). This gives you access to a preinstalled Python environment managed with pipenv. A number of useful AI core packages and tools are installed, including `scipy`, `numpy`, `scikit-learn`, `jupyter`, `tensorflow`, and the Scaleway SDK. Depending on the [Docker image you choose](/gpu/reference-content/docker-images/), other packages and tools will also be preinstalled, providing a convenient framework environment for you so that you can begin work immediately.
 
 <Macro id="requirements" />
 
diff --git a/pages/managed-databases-for-postgresql-and-mysql/reference-content/pg-version-updates.mdx b/pages/managed-databases-for-postgresql-and-mysql/reference-content/pg-version-updates.mdx
@@ -88,5 +88,5 @@ Refer to the official [Error reporting and logging](https://www.postgresql.org/d
 - `pg_stat_statements.track`
 - `pg_stat_statements.track_utility`
 
-Refer to the official [PG stats parameters](ttps://www.postgresql.org/docs/16/pgstatstatements.html#PGSTATSTATEMENTS-CONFIG-PARAMS) PostgreSQL documentation for more information.
+Refer to the official [PG stats parameters](https://www.postgresql.org/docs/16/pgstatstatements.html#PGSTATSTATEMENTS-CONFIG-PARAMS) PostgreSQL documentation for more information.
 
diff --git a/pages/serverless-containers/how-to/deploy-container.mdx b/pages/serverless-containers/how-to/deploy-container.mdx
@@ -58,7 +58,7 @@ You can deploy a container from the [Scaleway Container Registry](/container-reg
       - Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
     </TabsTab>
     <TabsTab label="Requests">
-    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
+    - Set a custom [timeout](/serverless-containers/concepts/#request-timeout) for the duration of the requests received by your container.
     - Tick the box under [HTTP protocol](/serverless-containers/concepts/#protocol) to listen to HTTP/2 requests if it is required by your application. Otherwise, we recommend you use HTTP/1.
     </TabsTab>
     <TabsTab label="Performances">
@@ -121,7 +121,7 @@ Private external container registries are currently not supported.
       - Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
     </TabsTab>
     <TabsTab label="Requests">
-    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
+    - Set a custom [timeout](/serverless-containers/concepts/#request-timeout) for the duration of the requests received by your container.
     - Tick the box under [HTTP protocol](/serverless-containers/concepts/#protocol) to listen to HTTP/2 requests if it is required by your application. Otherwise, we recommend you use HTTP/1.
     </TabsTab>
     <TabsTab label="Performances">
diff --git a/pages/serverless-containers/how-to/manage-a-container.mdx b/pages/serverless-containers/how-to/manage-a-container.mdx
@@ -49,7 +49,7 @@ This page shows you how to manage a container, in order to verify or edit its de
       - Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
     </TabsTab>
     <TabsTab label="Requests">
-    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
+    - Set a custom [timeout](/serverless-containers/concepts/#request-timeout) for the duration of the requests received by your container.
     - Tick the box under [HTTP protocol](/serverless-containers/concepts/#protocol) to listen to HTTP/2 requests if it is required by your application. Otherwise, we recommend you use HTTP/1.
     </TabsTab>
     <TabsTab label="Performances">
@@ -94,7 +94,7 @@ This page shows you how to manage a container, in order to verify or edit its de
       - Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
     </TabsTab>
     <TabsTab label="Requests">
-    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
+    - Set a custom [timeout](/serverless-containers/concepts/#request-timeout) for the duration of the requests received by your container.
     - Tick the box under [HTTP protocol](/serverless-containers/concepts/#protocol) to listen to HTTP/2 requests if it is required by your application. Otherwise, we recommend you use HTTP/1.
     </TabsTab>
     <TabsTab label="Performances">
diff --git a/pages/serverless-functions/how-to/create-a-function.mdx b/pages/serverless-functions/how-to/create-a-function.mdx
@@ -13,7 +13,7 @@ categories:
   - serverless
 ---
 
-This page shows you how to deploy a [function](/serverless-functions/concepts/#function) using the Scaleway console.
+This page shows you how to deploy a [function](/serverless-functions/concepts/#serverless-functions) using the Scaleway console.
 
 <Macro id="requirements" />
 
diff --git a/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx b/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx
@@ -15,7 +15,7 @@ categories:
 
 This page shows you how to create, manage, and delete a Functions namespace using the Scaleway console.
 
-[Namespaces](/serverless-functions/concepts/#namespace) allow you to group your [functions](/serverless-functions/concepts/#function) and share environment variables, secrets and tokens between them.
+[Namespaces](/serverless-functions/concepts/#namespace) allow you to group your [functions](/serverless-functions/concepts/#serverless-functions) and share environment variables, secrets and tokens between them.
 
 <Macro id="requirements" />
 
diff --git a/pages/serverless-functions/quickstart.mdx b/pages/serverless-functions/quickstart.mdx
@@ -13,7 +13,7 @@ categories:
   - serverless
 ---
 
-Scaleway Serverless Functions makes your [functions](/serverless-functions/concepts/#function) available, executes them on demand and manages resource allocation for you.
+Scaleway Serverless Functions makes your [functions](/serverless-functions/concepts/#serverless-functions) available, executes them on demand and manages resource allocation for you.
 
 Functions are designed for lightweight and short-lived workloads, and are limited to [a selection of runtimes](/serverless-functions/reference-content/functions-runtimes/#available-runtimes) for optimum performance.
 
diff --git a/pages/vpc/reference-content/use-case-basic.mdx b/pages/vpc/reference-content/use-case-basic.mdx
@@ -35,7 +35,7 @@ This is a basic infrastructure to leverage VPC isolation:
 - Administrators can access the Instances via the [Public Gateway](/public-gateways/concepts/#public-gateway).
 - External services are accessed by the Instances via the Public Gateway.
 
-Full [Terraform/OpenTofu templates](#terraform) are available for this infrastructure.
+Full [Terraform/OpenTofu templates](##terraformopentofu) are available for this infrastructure.
 
 ## Detail
 
diff --git a/tutorials/create-serverless-scraping/index.mdx b/tutorials/create-serverless-scraping/index.mdx
@@ -45,7 +45,7 @@ We start by creating the scraper program, or the "data producer".
 3. Create a subdirectory `handlers` within the `scraper` directory, and add a `scrape_hn.py` file inside it.
 4. Complete the `scrape_hn.py` file by adding the function code [as shown in the repository](https://github.com/scaleway/serverless-examples/blob/main/mnq/serverless-scraping/scraper/handlers/scrape_hn.py). The main code blocks are briefly explained as follows:
 
-    Queue credentials and URL are read by the function from environment variables. Those variables are set by Terraform/OpenTofu as explained in [one of the next sections](#create-a-terraform-file-to-provision-the-necessary-scaleway-resources). *If you choose another deployment method, such as the [console](https://console.scaleway.com/), do not forget to set them.*
+    Queue credentials and URL are read by the function from environment variables. Those variables are set by Terraform/OpenTofu as explained in [one of the next sections](#create-a-terraformopentofu-file-to-provision-the-necessary-scaleway-resources). *If you choose another deployment method, such as the [console](https://console.scaleway.com/), do not forget to set them.*
     ```python
     queue_url = os.getenv('QUEUE_URL')
     sqs_access_key = os.getenv('SQS_ACCESS_KEY')
diff --git a/tutorials/strapi-app-serverless-containers-sqldb/index.mdx b/tutorials/strapi-app-serverless-containers-sqldb/index.mdx
