diff --git a/pages/serverless-containers/how-to/test-a-container.mdx b/pages/serverless-containers/how-to/test-a-container.mdx
index 9a1136f7de..6796d2d156 100644
--- a/pages/serverless-containers/how-to/test-a-container.mdx
+++ b/pages/serverless-containers/how-to/test-a-container.mdx
@@ -16,7 +16,7 @@ categories:
This page shows you how to execute Serverless Containers from the [Scaleway console](https://console.scaleway.com). The **Test** feature of a container allows you to run your code using a selection of methods to make sure it behaves as expected.
-Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless-functions/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function.
+Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless-containers/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function.
diff --git a/pages/serverless-functions/how-to/add-trigger-to-a-function.mdx b/pages/serverless-functions/how-to/add-trigger-to-a-function.mdx
index dd933ef2b2..33bc873da6 100644
--- a/pages/serverless-functions/how-to/add-trigger-to-a-function.mdx
+++ b/pages/serverless-functions/how-to/add-trigger-to-a-function.mdx
@@ -39,7 +39,7 @@ You can create triggers on private functions, but to update the privacy of a fun
## Queue triggers
-[Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a function using events stored in a [queue](/messaging/concepts/#queue).
+[Queue triggers](/serverless-functions/concepts/#queue-trigger) allow you to automatically invoke a function using events stored in a [queue](/messaging/concepts/#queue).
Only queues created with the Scaleway Queues product are compatible with Serverless Functions.
diff --git a/pages/serverless-functions/reference-content/deploy-function.mdx b/pages/serverless-functions/reference-content/deploy-function.mdx
index 867e943127..598d348883 100644
--- a/pages/serverless-functions/reference-content/deploy-function.mdx
+++ b/pages/serverless-functions/reference-content/deploy-function.mdx
@@ -42,7 +42,7 @@ Many of the examples found in our [Serverless Examples repository](https://githu
## Terraform
-Serverless Functions integrate easily with your infrastructure as code, via our [Terraform provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/container).
+Serverless Functions integrate easily with your infrastructure as code, via our [Terraform provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/function).
Examples using Terraform can be found in our [Serverless Examples repository](https://github.com/scaleway/serverless-examples), such as our [example using Terraform with Python](https://github.com/scaleway/serverless-examples/tree/main/functions/terraform-python-example).
diff --git a/pages/serverless-jobs/concepts.mdx b/pages/serverless-jobs/concepts.mdx
index 5cdef37512..3f8a1ad6d8 100644
--- a/pages/serverless-jobs/concepts.mdx
+++ b/pages/serverless-jobs/concepts.mdx
@@ -14,7 +14,7 @@ categories:
## Container Registry
-Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
+Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless-jobs/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
## Environment variables
@@ -100,6 +100,12 @@ This means that each request is treated as a new and isolated event, and there i
To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/).
+## Terraform
+
+Terraform is an infrastructure-as-code tool, owned by Hashicorp. Serverless Jobs integrate easily with your infrastructure as code, via our [Terraform provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/job_definition).
+
+Examples using Terraform can be found in our [Serverless Examples repository](https://github.com/scaleway/serverless-examples), such as our [example using Terraform with Serverless Jobs](https://github.com/scaleway/serverless-examples/blob/main/jobs/terraform-hello-world).
+
## vCPU-s
Unit used to measure the resource consumption of a container. It reflects the amount of vCPU used over time.
\ No newline at end of file
diff --git a/pages/serverless-jobs/quickstart.mdx b/pages/serverless-jobs/quickstart.mdx
index 4332565eb4..742b6056f4 100644
--- a/pages/serverless-jobs/quickstart.mdx
+++ b/pages/serverless-jobs/quickstart.mdx
@@ -18,7 +18,7 @@ Scaleway Serverless Jobs allows you to run recurring tasks in the cloud. A [Job]
Jobs are designed for autonomous and recurring tasks, and therefore do not offer automatic scaling or a web interface.
-Refer to the [differences between Jobs, Containers, and Functions](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products.
+Refer to the [differences between Jobs, Containers, and Functions](/serverless-jobs/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products.
This page explains how to create a job definition with the latest Alpine Linux image, how to execute it, and delete it.