chore(gen): update

Author: SamyOubouaziz

pages/serverless-containers/how-to/secure-a-container.mdx

@@ -119,5 +119,3 @@ Refer to our [dedicated repository](https://github.com/scaleway/serverless-scale
 Using Scaleway [Observability Cockpit](/cockpit/quickstart/), a managed Grafana solution to which all your containers are connected, you can:
 * Monitor your containers using the default dashboard or create custom ones.
 * Set up notifications to be alerted in case of unexpected behavior.
-
-

pages/serverless-containers/quickstart.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Quickstart guide for Scaleway Serverless Containers.
 tags: containers serverless namespace
 dates:
-  validation: 2024-08-13
+  validation: 2025-02-27
   posted: 2021-05-26
 categories:
   - serverless

pages/serverless-functions/how-to/secure-a-function.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: How to secure your Scaleway Serverless Functions effectively.
 tags: functions secure private
 dates:
-  validation: 2024-08-13
+  validation: 2025-02-27  
   posted: 2023-02-01
 categories:
   - serverless

pages/serverless-functions/reference-content/code-examples.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Explore code examples for creating and deploying Serverless Functions in Scaleway.
 tags: functions serverless serverless-functions
 dates:
-  validation: 2024-07-22
+  validation: 2025-02-27
   posted: 2021-10-18
 categories:
   - serverless
@@ -31,7 +31,7 @@ This page shows examples of functions in [Python](#python), [Node](#node), [Gola
 
 ### Returning a function result in Python
 
-There are several ways to return a response from a handler function:
+There are several ways to return a response from a handler function.
 
 **Response object with HTTP information:**
 

pages/serverless-sql-databases/quickstart.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Quickstart guide for setting up Scaleway serverless SQL databases.
 tags: sql-databases serverless database connect create delete serverless-sql-database serverless-db postgresql 
 dates:
-  validation: 2024-08-12
+  validation: 2025-02-27
   posted: 2023-08-11
 categories:
   - serverless

pages/serverless-sql-databases/reference-content/serverless-sql-databases-overview.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Overview of Scaleway's serverless SQL databases, including autoscaling and technical specifications.
 tags: database serverless-sql-database serverless overview specs
 dates:
-  validation: 2024-08-13
+  validation: 2025-02-27
   posted: 2023-08-04
 categories:
   - serverless
@@ -48,7 +48,7 @@ Autoscaling is triggered automatically, based on your database vCPU consumption:
   - **Scaling down**: after using less than 70% of the currently allocated vCPU for 10 seconds, the vCPU and RAM allocated to your database will decrease by 25% (rounded down to the nearest vCPU integer value), down to a minimum of 1 vCPU and 4 GB RAM while your database is active.
 
 <Message type="note">
-  Scaling (up or down) operations happens at most once every minute. Moreover, for low vCPU values, scale-down operations happen only if the current workload can be absorbed by the nearest vCPU integer value rounded down. For instance, a database with 2 vCPUs consuming only 1.2 vCPU on average (60% of provisioned vCPU) will not scale down to 1 vCPU as the current load could not be absorbed.
+  Scaling (up or down) operations happen at most once every minute. Moreover, for low vCPU values, scale-down operations happen only if the current workload can be absorbed by the nearest vCPU integer value rounded down. For instance, a database with 2 vCPUs consuming only 1.2 vCPU on average (60% of provisioned vCPU) will not scale down to 1 vCPU as the current load could not be absorbed.
 </Message>
 
 Automatic scaling operations may need to happen **between** atomic transactions. For example, a long-running transaction (such as updating millions of rows) taking one minute may delay the next scaling operation by one minute. The next transaction performed will, however, benefit from the upscaled/downscaled database performance. For optimal autoscaling reactivity and performance, we recommend you limit each transaction duration to a few seconds at most.
@@ -92,4 +92,3 @@ The following actions must be performed by you directly:
 - SQL request size is limited to 512 KB. A single SQL query sent to a Serverless SQL Database cannot exceed 512 KB, but the response to the query is not limited and results tables can exceed 512 KB.
 
 - The total size of prepared statements is limited to 512 KB per client connection. Refer to the [official PostgreSQ documentation](https://www.postgresql.org/docs/current/sql-prepare.html) for more information on prepared statements.
-