chore(gen): doc review MTA-6082

Author: SamyOubouaziz

pages/serverless-containers/concepts.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Key concepts of Scaleway Serverless Containers.
 tags: containers cold-start concurrency container-registry environment-variables jwt vcpu serverless scale autoscaling
 dates:
-  validation: 2024-11-14
+  validation: 2025-05-26
 categories:
   - serverless
 ---
@@ -115,15 +115,15 @@ The Serverless infrastructure manages incoming request traffic. In scenarios lik
 
 ## Logging
 
-Serverless Containers offers a built-in logging system based on Cockpit to track the activity of your resources: see [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/).
+Serverless Containers offers a built-in logging system based on Cockpit to track the activity of your resources. Refer to [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/) for more information.
 
 ## Max scale
 
-This parameter sets the maximum number of container instances. You should adjust it based on your container'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 container instances. You should adjust it based on your container'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 Containers](/serverless-containers/how-to/monitor-container/).
+Performance metrics for your Serverless resources are natively available. Refer to [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/) for more information.
 
 ## Min scale
 
@@ -165,7 +165,7 @@ Refer to the [dedicated FAQ](/serverless-containers/faq/#how-can-i-configure-acc
 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.
+The container can then process the message, and perform any required actions, such as updating a database or sending a notification.
 
 ## Registry endpoint
 
@@ -181,11 +181,10 @@ Use cases:
 
 ## Rolling update
 
-When deploying a new version of a Serverless Container, a rolling update is applied by default. This means that the new version of the service is gradually rolled out to your users without downtime.
-Here is how it works:
+When deploying a new version of a Serverless Container, a rolling update is applied by default. The new version of the service is gradually rolled out to your users without downtime, as follows:
 
 * When a new version of your container is deployed, the platform automatically starts routing traffic to it 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 it.
@@ -200,7 +199,7 @@ Refer to the [dedicated documentation](/serverless-containers/reference-content/
 
 ## Scale to zero
 
-One of the advantages of Serverless Containers is that when your container is not triggered, it does not consume any resources, which enables great savings.
+When provisioned with a [minimum scale](#min-scale) of `0`, Serverless Containers 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
 

pages/serverless-sql-databases/concepts.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Detailed explanation of concepts and architecture behind Scaleway's serverless SQL databases.
 tags: sql databases serverless
 dates:
-  validation: 2024-11-14
+  validation: 2025-05-26
 categories:
   - serverless
 ---