Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>
Co-authored-by: Jessica <[email protected]>

Author: 3 people

faq/serverless-functions.mdx

@@ -220,11 +220,11 @@ solutions like Scaleway Object Storage.
 Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum
 scale is set to 0. This behavior is not configurable at this time.
 
-## How can I store data in my Serverless ressource?
+## How can I store data in my Serverless resource?
 
-Serverless ressources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
 
-In different use cases like saving results of analysis, exporting data etc... it can be important to save data. Serverless ressources can be connected to ressources from the Scaleway ecosystem.
+For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose:
 
 ### Databases
 
@@ -235,11 +235,11 @@ In different use cases like saving results of analysis, exporting data etc... it
 
 ### Storage
 
-* **Object storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
+* **Object Storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
 * **Scaleway Glacier**: Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
 
 <Message type="tip">
 Explore all Scaleway products on the console and select the right product for your use case.
 
-Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versionning.
+Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
 </Message>

faq/serverless-jobs.mdx

@@ -10,13 +10,13 @@ category: serverless
 productIcon: ServerlessJobsProductIcon
 ---
 
-## What is serverless computing and how does it differ from traditional cloud hosting?
+## What is serverless computing, and how does it differ from traditional cloud hosting?
 
 Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you don’t need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
 
-## Why consider using Serverless Containers, Functions or Jobs for my projects?
+## Why consider using Serverless Containers, Functions, or Jobs for my projects?
 
-These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs let you run large-scale, parallel batch processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings.
+These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs lets you run large-scale, parallel batch-processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings.
 
 ## What is Serverless Jobs, and when should I use it?
 
@@ -26,11 +26,11 @@ Serverless Jobs allows you to run large-scale batch processing and computational
 
 Integration is straightforward. Serverless Functions and Containers can be triggered by events from Queues, SQS and SNS and can easily communicate with services like Managed databases or Serverless databases. Serverless Jobs can pull data from 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.
 
-## Can I update Serverless Jobs ressources (vCPU and RAM) at any time?
+## Can I update Serverless Jobs resources (vCPU and RAM) at any time?
 
-Yes, ressources of your Job Definition can be updated at any time.
+Yes, resources of your Job Definition can be updated at any time.
 
-Ongoing Job Runs will remain using the ressources definied at the time it started.
+Ongoing Job Runs will remain using the resources definied at the time it started.
 
 ## How am I billed for Serverless Jobs?
 
@@ -143,11 +143,11 @@ To add network restrictions on your resource, consult the [list of prefixes used
 
 Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL certificates, or tokens. Serverless Jobs seamlessly integrates with [Secret Manager](/identity-and-access-management/secret-manager/), which allows you to securely reference sensitive information within your jobs. Refer to the [dedicated documentation](/serverless/jobs/how-to/reference-secret-in-job/) for more information.
 
-## How can I store data in my Serverless ressource?
+## How can I store data in my Serverless resource?
 
-Serverless ressources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
 
-In different use cases like saving results of analysis, exporting data etc... it can be important to save data. Serverless ressources can be connected to ressources from the Scaleway ecosystem.
+In different use cases, such as saving analysis results and exporting data, it can be important to save data. Serverless resources can be connected to resources from the Scaleway ecosystem.
 
 ### Databases
 
@@ -158,11 +158,11 @@ In different use cases like saving results of analysis, exporting data etc... it
 
 ### Storage
 
-* **Object storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
+* **Object Storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
 * **Scaleway Glacier**: Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
 
 <Message type="tip">
 Explore all Scaleway products on the console and select the right product for your use case.
 
-Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versionning.
+Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
 </Message>

serverless/containers/concepts.mdx

@@ -97,15 +97,15 @@ The Serverless infrastructure manages incoming request traffic. In scenarios lik
 
 ## Logging
 
-Serverless offers a built-in logging system based on cockpit to follow the activity of your ressources: [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: see [monitoring Serverless Containers](/serverless/containers/how-to/monitor-container/).
 
 ## 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.
 
 ## Metrics
 
-Performances of your Serverless ressources are natively available: [monitoring Serverless Containers](/serverless/containers/how-to/monitor-container/).
+Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Containers](/serverless/containers/how-to/monitor-container/).
 
 ## Min scale
 
@@ -174,9 +174,9 @@ Serverless.com (Serverless Framework) is a tool that allows you to deploy server
 
 ## Serverless Function
 
-A Serverless Function are serverless, fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
+Serverless Functions are serverless, fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
 
-These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable without worrying about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
+These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
 
 ## Serverless Job
 
@@ -191,11 +191,11 @@ The container can then process the message and perform any required actions, suc
 
 ## Rolling update
 
-When deploying a new version of a Serverless Container, a rolling update happens by default. This means that the new version of the service is gradually rolled out to your users without downtime.
+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 a new version of your container 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 shifts all traffic to it, ensuring zero downtime.
+* Once the new version is successfully running, we gradually shift 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 disruption to users 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