chore(gen): update

Author: SamyOubouaziz

faq/serverless-functions.mdx

@@ -6,7 +6,7 @@ content:
   h1: Serverless Functions
 hero: assets/faas.webp
 dates:
-  validation: 2024-03-25
+  validation: 2024-10-03
 category: serverless
 ---
 
@@ -16,21 +16,21 @@ category: serverless
 
 Serverless Functions is billed on a pay-as-you-go basis. Three components are taken into account:
 
-* **Monthly Request number:** each time your function is invoked we increase a counter.
+* **Monthly request number:** each time your function is invoked we increase a counter.
 
 * **Resource consumption:** this component is obtained by multiplying the memory tiers chosen by the duration of each function invocation.
 
-* **Resources provision:** in order to mitigate cold start, users can choose to keep some function Instances warm (by filing the min scale value). We then charge for the provisioned resources similarly to the Resources consumption component.
+* **Resources provision:** in order to mitigate cold start, users can choose to keep some function instances warm (by filing the minimum scale value). We then charge for the provisioned resources similarly to the Resources consumption component.
 
 The scheme below illustrates our billing model:
 
 <Lightbox src={["scaleway-Billing-FaaS-1-DEF.webp", "scaleway-Billing-FaaS-2-DEF.webp"]} size={"medium"}  alt={["Functions Billing", "Functions Billing"]} />
 
 ### Pricing
 
-* **Monthly requests:** **€0.15 per million requests** and we offer **1M free requests** per account per month.
+* **Monthly requests:** **€0.15 per million requests**, and we offer **1M free requests** per account per month.
 
-* **Resources consumption:**  **€1.20 per 100 000 GB-s** and we provide **400 000 GB-s free tiers** per account and per month.
+* **Resources consumption:** **€1.20 per 100 000 GB-s**, and we provide **400 000 GB-s free tiers** per account and per month.
 
 | Memory provisioned  | Cost per second |
 |---------------------|-----------------|
@@ -157,7 +157,7 @@ Serverless Functions use cases are wide so [several ways to deploy functions](/s
 
 ## How can I test my functions locally?
 
-Local development is useful for debugging, profiling, testing etc... so we provide libraries to do this: [local testing doc](/serverless/functions/reference-content/local-testing/).
+ Scaleway provide libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless/functions/reference-content/local-testing/) for more information.
 
 ## Where can I find some advanced code examples for functions?
 
@@ -166,10 +166,14 @@ Check out our [serverless-examples repository](https://github.com/scaleway/serve
 ## How to migrate runtimes?
 
 There are no constraints when changing a function runtime, you simply need to choose the runtime version you want.
+<<<<<<< HEAD
 Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. See the [functions runtimes lifecycle documentation](/serverless/functions/reference-content/functions-lifecycle/) for more information.
 
 ## How do I configure access to a Private Network?
 
 Scaleway Serverless Functions does not currently support Scaleway VPC or Private Networks, though this feature is under development.
 
 To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Note that Serverless resources do not have dedicated or predictable IP addresses.
+=======
+Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. Refer to the [functions runtimes lifecycle documentation](/serverless/functions/reference-content/functions-lifecycle/) for more information.
+>>>>>>> 231926b2c (chore(gen): update)