chore(gen): update

Author: SamyOubouaziz

pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Create, manage, and delete namespaces in Scaleway Serverless Containers.
 tags: container namespace manage create delete environment variable secret
 dates:
-  validation: 2024-11-14
+  validation: 2025-05-27
   posted: 2021-05-26
 categories:
   - serverless
@@ -28,7 +28,7 @@ This page shows you how to create and manage a Serverless Containers namespace.
 3. Complete the following steps in the wizard:
     - Enter a **name**, and optionally a **description** for your namespace. The name must only contain alphanumeric characters and dashes.
     - Choose a **region**, which is the geographical location in which your namespace will be deployed.
-    - Enter any **environment variables** required for your namespace. Environment variables configured in a namespace will be available in all containers/apps within the same namespace. For each environment variable, click **+Add new variable** and enter the key / value pair.
+    - Enter any **environment variables** required for your namespace. Environment variables configured in a namespace will be available in all containers/apps within the same namespace. For each environment variable, click **+ Add new variable** and enter the key / value pair.
     - Set secret environment variables (optional). **Secrets** are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**.
     - Verify the **estimated cost**.
 4. Click **Create namespace only** to finish, or click **Create namespace and add container** if you want to [deploy a container](/serverless-containers/how-to/deploy-container/) next.

pages/serverless-containers/reference-content/dns-query-rate-limit.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Containers.
 tags: serverless containers dns query rate limiting limit response
 dates:
-  validation: 2024-11-12
+  validation: 2025-05-27
   posted: 2024-11-12
 categories:
   - serverless

pages/serverless-functions/concepts.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Learn the core concepts and principles behind Scaleway's Serverless Functions.
 tags: functions cold-start environment-variables gbs jwt handler serverless concept definition
 dates:
-  validation: 2024-11-14
+  validation: 2025-05-27
 categories:
   - serverless
 ---
@@ -33,19 +33,19 @@ Once the Function is built into an image, it will be pushed to [Container Regist
 Cold Start is the time a function takes to handle a request when it is called for the first time.
 
 The startup process steps are:
-* Downloading the container image (which contains the built Function) to our infrastructure
+* Downloading the container image (which contains the built function) to our infrastructure
 * Starting the container and the runtime
 * Waiting for the container to be ready.
 
-[How to reduce cold starts](/serverless-functions/faq/#how-to-reduce-cold-start-of-serverless-functions)
+Refer to the dedicated FAQ on [how to reduce cold starts](/serverless-functions/faq/#how-to-reduce-cold-start-of-serverless-functions) for more information.
 
 ## Concurrency
 
 Concurrency defines the capacity of a resource to process several requests at the same time. A single instance of a function has a concurrency of `1` as it handles requests sequentially, one by one, but a Serverless Function can have several instances running at the same time, depending on its [autoscaling](#autoscaling) configuration.
 
 ## Container Registry
 
-Container Registry is the place where the images of your Serverless Functions are stored before being deployed.
+[Container Registry](/container-registry/) is the place where the images of your Serverless Functions are stored before being deployed.
 
 ## CRON trigger
 
@@ -85,15 +85,15 @@ The Serverless infrastructure manages incoming request traffic. In scenarios lik
 
 ## Logging
 
-Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/).
+Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources. Refer to [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/) for more information.
 
 ## Max scale
 
-This parameter sets the maximum number of function instances. You should adjust it based on your function's traffic spikes, keeping in mind that you may wish to limit the max scale to manage costs effectively.
+This parameter sets the maximum number of function instances. You should adjust it based on your function's traffic spikes, keeping in mind that you may wish to limit the maximum scale to manage costs effectively.
 
 ## Metrics
 
-Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/)).
+Performance metrics for your Serverless resources are natively available. Refer to [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/) for more information.
 
 ## Min scale
 
@@ -124,7 +124,7 @@ Refer to the [dedicated FAQ](/serverless-functions/faq/#how-can-i-configure-acce
 
 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.
+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.
 
 ## Request timeout
@@ -141,7 +141,7 @@ When deploying a new version of a Serverless Function, a rolling update is appli
 Here is how it works:
 
 * When a new version of your function is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed.
-* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
+* Once the new version is successfully running, the platform gradually shifts all traffic to it, ensuring zero downtime.
 * The old version is decommissioned once the new version is fully serving traffic.
 
 This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to them.
@@ -160,7 +160,7 @@ Refer to the [dedicated documentation](/serverless-functions/reference-content/f
 
 ## Scale to zero
 
-One of the advantages of Serverless Functions is that when your function is not triggered, it does not consume any resources, which allows for significant savings.
+When provisioned with a [minimum scale](#min-scale) of `0`, Serverless Functions scale down to zero active instances as long as they are not triggered. While idling, they do not consume any resources, which allows to reduce the cost of your infrastructure.
 
 ## Secrets