fix(gen): update

SamyOubouaziz · SamyOubouaziz · commit 8777833de322 · 2025-03-05T15:41:06.000+01:00
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
@@ -18,7 +18,7 @@ This tutorial will guide you through deploying a fully serverless Strapi headles
 
 You can either deploy your application:
   - [step by step using the Scaleway CLI](#deploy-a-strapi-headless-cms-using-the-scaleway-cli) to understand each action performed in detail and the resources required
-  - [using a Terraform/OpenTofu template](#deploy-strapi-using-scaleway-terraform-templates) to deploy your application faster and have ready-to-use Infrastructure as Code.
+  - [using a Terraform/OpenTofu template](#deploy-strapi-using-scaleway-terraformopentofu-templates) to deploy your application faster and have ready-to-use Infrastructure as Code.
 
 <Macro id="requirements" />
 
