fix(links): update links

Author: RoRoJ

pages/faq/index.mdx

@@ -180,9 +180,19 @@ content:
   />
 
   <ProductCardIllustration
+    productLogo="nats"
+    url="/nats/faq/"
+    label="NATS"
+  />
+    <ProductCardIllustration
+    productLogo="sqs"
+    url="/queues/faq/"
+    label="Queues"
+  />
+    <ProductCardIllustration
     productLogo="sns"
-    url="/messaging/faq/"
-    label="Messaging and Queuing"
+    url="/topics-and-events/faq/"
+    label="Topics and Events"
   />
 
   <ProductCardIllustration

pages/organizations-and-projects/additional-content/organization-quotas.mdx

@@ -336,7 +336,7 @@ For example, if you choose to create a container with 512 MB of memory and a max
 
 Scaleway NATS is a message broker tool based on the NATS protocol, that allows you to transfer messages between different microservices and platforms.
 
-The following usage limits are enforced as Organization quotas when using Scaleway [NATS](/messaging/concepts/#nats):
+The following usage limits are enforced as Organization quotas when using Scaleway [NATS](/nats/concepts/#nats):
 
 **NATS**
 
@@ -354,8 +354,8 @@ Note that in memory stream are not supported, please create your NATS stream usi
 
 ## Queues
 
-Scaleway Queues is a product for creating managed messaging queues based on the [SQS](/messaging/concepts/#sqs) protocol.
-Limits that apply to regular queues also apply to [dead letter queues](/messaging/concepts/#dead-letter-queue).
+Scaleway Queues is a product for creating managed messaging queues based on the [SQS](/queues/concepts/#sqs) protocol.
+Limits that apply to regular queues also apply to [dead letter queues](/queues/concepts/#dead-letter-queue).
 The following usage limits are enforced as Organization quotas when using Scaleway Queues:
 
 
@@ -371,7 +371,7 @@ The following usage limits are enforced as Organization quotas when using Scalew
 
 ## Topics and Events
 
-Topics and Events is a product for creating managed messaging topics based on the [SNS](/messaging/concepts/#sns) protocol. The following usage limits are enforced as Organization quotas when using Scaleway Topics and Events:
+Topics and Events is a product for creating managed messaging topics based on the [SNS](/topics-and-events/concepts/#sns) protocol. The following usage limits are enforced as Organization quotas when using Scaleway Topics and Events:
 
 | Resource                                       | Criteria   | Limits   | Scope            |
 |------------------------------------------------|------------|----------|------------------|

pages/scaleway-cli/reference-content/cli-reference.mdx

@@ -22,7 +22,7 @@ The [Scaleway command line interface (CLI)](https://github.com/scaleway/scaleway
 | Instances                       | [Creating and managing an Instance with the CLI (v2)](/instances/api-cli/creating-managing-instances-with-cliv2/) |
 | Instances                       | [Managing Instance snapshots with the CLI (v2)](/instances/api-cli/managing-instance-snapshot-via-cli/) |
 | Elastic Metal                   | [Creating and Managing Elastic Metal servers with the CLI](/elastic-metal/api-cli/elastic-metal-with-cli/) |
-| NATS                            | [Using the NATS CLI](/messaging/api-cli/nats-cli/) |
+| NATS                            | [Using the NATS CLI](/nats/api-cli/nats-cli/) |
 | Kubernetes                      | [Creating and managing a Kubernetes Kapsule with the CLI (v2)](/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2/) |
 | Iot Hub                         | [Getting started with the IoT Hub CLI](/iot-hub/api-cli/getting-started-with-iot-hub-cli/) |
 

pages/serverless-containers/concepts.mdx

@@ -141,7 +141,7 @@ Containers in the same namespace can share environment variables, secrets, and a
 
 ## NATS trigger
 
-A NATS trigger is a mechanism that connects a container to a [NATS](/messaging/concepts/#nats) subject and invokes the container automatically whenever a message is published to the subject.
+A NATS trigger is a mechanism that connects a container to a [NATS](/nats/concepts/#nats) subject and invokes the container automatically whenever a message is published to the subject.
 
 For each message that is sent to a NATS subject, the NATS trigger reads the message and invokes the associated container with the message as the input parameter.
 The container can then process the message and perform any required actions, such as updating a database or sending a notification.
@@ -162,7 +162,7 @@ Refer to the [dedicated FAQ](/serverless-containers/faq/#how-can-i-configure-acc
 
 ## Queue trigger
 
-A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue.
+A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/queues/concepts/#scaleway-queues), and invokes the container automatically whenever a message is added to the queue.
 
 For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter.
 The container can then process the message and perform any required actions, such as updating a database or sending a notification.

pages/serverless-containers/faq.mdx

@@ -165,7 +165,7 @@ There are several ways to deploy containers. Refer to the [dedicated documentati
 
 ### How do I integrate my serverless solutions with other Scaleway services?
 
-Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/queues/concepts/#scaleway-queues) and [Topics and Events](/topics-and-events/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
 
 ### Where should I host my container images for deployment ?
 

pages/serverless-containers/how-to/add-trigger-to-a-container.mdx

@@ -25,8 +25,8 @@ A trigger can be an HTTP request, a message from a queue or stream, a CRON sched
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - Deployed a container from [Scaleway Container Registry](/serverless-containers/how-to/deploy-container/) or an [external registry](/serverless-containers/how-to/deploy-container/)
-- [Created credentials](/messaging/how-to/create-credentials/) for Scaleway Queues
-- [Created a queue](/messaging/how-to/create-manage-queues/)
+- [Created credentials](/queues/how-to/create-credentials/) for Scaleway Queues
+- [Created a queue](/queues/how-to/create-manage-queues/)
 
 <Message type="important">
 You can create triggers on private containers, but to update the privacy of a container from **public** to **private**, you must recreate the existing **Scaleway Queues** and **Scaleway NATS** triggers after the privacy change. We are actively working to make this operation as seamless as possible.
@@ -44,7 +44,7 @@ You must have at least the `MessagingAndQueuingReadOnly` permission in the Proje
 Refer to the [permissions sets documentation](/iam/reference-content/permission-sets/) for more information.
 </Message>
 
-[Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a container using events stored in a [Scaleway queue](/messaging/concepts/#queues).
+[Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a container using events stored in a [Scaleway queue](/queues/concepts/#scaleway-queues).
 
 Only queues created with the Scaleway Queues product are compatible with Serverless Containers.
 
@@ -72,9 +72,9 @@ You must have at least the `MessagingAndQueuingReadOnly` permission in the Proje
 Refer to the [permissions sets documentation](/iam/reference-content/permission-sets/) for more information.
 </Message>
 
-[NATS triggers](/serverless-containers/concepts/#nats-trigger) allow you to automatically invoke a container using messages sent in a [NATS](/messaging/concepts/#nats) subject.
+[NATS triggers](/serverless-containers/concepts/#nats-trigger) allow you to automatically invoke a container using messages sent in a [NATS](/nats/concepts/#nats) subject.
 
-[Scaleway NATS subjects](/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Containers.
+[Scaleway NATS subjects](/nats/quickstart/) are compatible with Serverless Containers.
 
 1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays.
 2. Click the relevant containers namespace.

pages/serverless-functions/concepts.mdx

@@ -107,7 +107,7 @@ Functions in the same namespace can share environment variables and access token
 
 ## NATS trigger
 
-A NATS trigger is a mechanism that connects a function to a [NATS](/messaging/concepts/#nats) subject and invokes the function automatically whenever a message is published to the subject.
+A NATS trigger is a mechanism that connects a function to a [NATS](/nats/concepts/#nats) subject and invokes the function automatically whenever a message is published to the subject.
 
 For each message that is sent to a NATS subject, the NATS trigger reads the message and invokes the associated function with the message as the input parameter.
 The function can then process the message and perform any required actions, such as updating a database or sending a notification.
@@ -122,7 +122,7 @@ Refer to the [dedicated FAQ](/serverless-functions/faq/#how-can-i-configure-acce
 
 ## Queue trigger
 
-A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the function automatically whenever a message is added to the queue.
+A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/queues/concepts/#scaleway-queues), and invokes the function automatically whenever a message is added to the queue.
 
 For each message that is sent to a queue, the trigger reads the message and invokes the associated function with the message as the input parameter.
 The function can then process the message and perform any required actions, such as updating a database or sending a notification.

pages/serverless-functions/faq.mdx

@@ -188,7 +188,7 @@ There are [several ways to deploy Serverless Functions](/serverless-functions/re
 
 ### How do I integrate my serverless solutions with other Scaleway services?
 
-Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/queues/concepts/#queues) and [Topics and Events](/topics-and-events/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
 
 ### How do Serverless Functions namespaces and Container Registry namespaces interact?
 

pages/serverless-functions/how-to/add-trigger-to-a-function.mdx

@@ -26,8 +26,8 @@ A trigger can be an HTTP request, a message from a queue or stream, a CRON sched
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - Created a [functions namespace](/serverless-functions/how-to/create-manage-delete-functions-namespace/)
 - Created a [function](/serverless-functions/how-to/create-a-function/)
-- [Created credentials](/messaging/how-to/create-credentials/) for Scaleway Queues
-- [Created a queue](/messaging/how-to/create-manage-queues/)
+- [Created credentials](/queues/how-to/create-credentials/) for Scaleway Queues
+- [Created a queue](/queues/how-to/create-manage-queues/)
 
 <Message type="important">
 You can create triggers on private functions, but to update the privacy of a function from **public** to **private**, you must recreate the existing **Queues** and **NATS** triggers after the privacy change. We are actively working to make this operation as seamless as possible.
@@ -45,7 +45,7 @@ You must have at least the `MessagingAndQueuingReadOnly` permission in the Proje
 Refer to the [permissions sets documentation](/iam/reference-content/permission-sets/) for more information.
 </Message>
 
-[Queue triggers](/serverless-functions/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](/queues/concepts/#queue).
 
 Only queues created with the Scaleway Queues product are compatible with Serverless Functions.
 
@@ -72,9 +72,9 @@ Refer to the [permissions sets documentation](/iam/reference-content/permission-
 </Message>
 
 
-[NATS triggers](/serverless-functions/concepts/#nats-trigger) allow you to automatically invoke a function using messages sent in a [NATS](/messaging/concepts/#nats) subject.
+[NATS triggers](/serverless-functions/concepts/#nats-trigger) allow you to automatically invoke a function using messages sent in a [NATS](/nats/concepts/#nats) subject.
 
-Scaleway [NATS subjects](/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Functions.
+Scaleway [NATS subjects](/nats/quickstart/) are compatible with Serverless Functions.
 
 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays.
 2. Click the relevant functions namespace.

pages/serverless-functions/reference-content/configure-trigger-inputs.mdx

@@ -18,7 +18,7 @@ categories:
   This feature only allows a maximum of 10 in-flight requests. Functions that are configured with more than 10 replicas will not be used at full capacity. This limitation will be removed in the future.
 </Message>
 
-Triggers get events from an input, such as a [Scaleway queue](/messaging/concepts/#queues), and forward them to a function, which will scale up according to its settings to accommodate the workload. This process uses back pressure, so that no new events are read if the function instances have not yet finished processing the previous ones.
+Triggers get events from an input, such as a [Scaleway queue](/queues/concepts/#queue), and forward them to a function, which will scale up according to its settings to accommodate the workload. This process uses back pressure, so that no new events are read if the function instances have not yet finished processing the previous ones.
 
 <Message type="note">
   Triggers only keep a buffer of the messages that are in-flight, they do not drain all the messages of the input in advance.