Apply suggestions from code review

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

Author: 3 people

serverless/containers/concepts.mdx

@@ -219,7 +219,7 @@ Refers to a system or application that does not maintain any persistent state be
 
 This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others.
 
-To store informations you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), [Scaleway Serverless Databases](/serverless/sql-databases/).
+To store data you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless/sql-databases/).
 
 ## Terraform
 

serverless/containers/reference-content/containers-limitations.mdx

@@ -54,13 +54,13 @@ In order to ensure the proper functioning of the product, we restrict the use of
 
 ### Blocked ports
 
-Due to potential abuse (spam), no outbound traffic is allowed through following ports, except from Scaleway Transactional Email SMTP servers.
+Due to potential abuse (spam), no outbound traffic is allowed through the following ports, except from Scaleway Transactional Email SMTP servers.
 
 * **25**
 * **465**
 
 ### Unavailable custom ports
-Do not make your containers listen on these ports which are used by our service.
+Do not have your containers listen on these ports, as they are used by our service.
 * 8008
 * 8012
 * 8013

serverless/functions/concepts.mdx

@@ -14,7 +14,7 @@ categories:
 
 ## Build step
 
-Before deploying a Serverless Functions it has to be built, this step occurs on deployment.
+Before deploying Serverless Functions, they have to be built. This step occurs during deployment.
 
 Once the Function is built into an image, it will be pushed to [Container Registry](#container-registry)
 
@@ -47,11 +47,11 @@ An endpoint is the URL generated to access your resource. It can be customized w
 
 ## Environment variables
 
-Environment variables are key/value pairs injected in your container. They are useful to share information such as configurations with your container. Some names are reserved. [See details about reserved names](/serverless/functions/reference-content/functions-limitations/#configuration-restrictions).
+Environment variables are key/value pairs injected in your container. They are useful for sharing information such as configurations with your container. Some names are reserved. [See details on reserved names](/serverless/functions/reference-content/functions-limitations/#configuration-restrictions).
 
 ## GB-s
 
-Unit used to measure the resource consumption of a Function. It reflects the amount of memory consumed over time.
+Unit used to measure the resource consumption of a function. It reflects the amount of memory consumed over time.
 
 ## JWT Token
 
@@ -71,15 +71,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 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: see [monitoring Serverless Functions](/serverless/functions/how-to/monitor-function/).
 
 ## 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.
 
 ## Metrics
 
-Performances of your Serverless ressources are natively available: [monitoring Serverless Functions](/serverless/functions/how-to/monitor-function/)).
+Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Functions](/serverless/functions/how-to/monitor-function/)).
 
 ## Min scale
 
@@ -111,14 +111,14 @@ The function can then process the message and perform any required actions, such
 
 ## Rolling update
 
-hen deploying a new version of a Serverless Function, 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 Function, 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 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 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.
+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.
 
 ## Runtime
 
@@ -152,9 +152,9 @@ Serverless.com (Serverless Framework) is a tool that enables the deployment of s
 
 ## 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
 
@@ -166,7 +166,7 @@ Refers to a system or application that does not maintain any persistent state be
 
 This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others.
 
-To store informations you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), [Scaleway Serverless Databases](/serverless/sql-databases/).
+To store data you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless/sql-databases/).
 
 ## Status
 

serverless/jobs/concepts.mdx

@@ -14,7 +14,7 @@ categories:
 
 ## Container Registry
 
-Container Registry is the place where your images are stored before being deployed, we recommend using Scaleway Container Registry for optimal integration. [Migration guide](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/).
+Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
 
 ## Environment variables
 
@@ -46,15 +46,15 @@ A job run is the execution of a job definition. It can be in a running, succeede
 
 ## Logging
 
-Serverless offers a built-in logging system based on cockpit to follow the activity of your ressources: [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/).
+Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/).
 
 ## Maximum duration
 
 The maximum duration option allows you to define the maximum execution time before your job is automatically killed.
 
 ## Metrics
 
-Performances of your Serverless ressources are natively available: [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/).
+Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/).
 
 ## Schedule (cron)
 
@@ -70,19 +70,19 @@ This optional field allows you to specify a custom command executed upon startin
 
 ## Status
 
-A Serverless Job Run can have the following statuses:
-* **Succeeded**: your Serverless Job Run finished in a good state.
-* **Queued**: your Serverless Job Run is waiting for ressources to run.
-* **Error**: your Serverless Job Run finished with an error or timeout. [Check our troubleshooting documentation](/serverless/jobs/troubleshooting/job-in-error-state/) to solve the issue.
-* **Canceled**: your Serverless Job Run has been canceled by the user.
+A Serverless Job run can have the following statuses:
+* **Succeeded**: your Serverless Job run finished in a successful state.
+* **Queued**: your Serverless Job run is waiting for resources to run.
+* **Error**: your Serverless Job run finished with an error or timeout. [Check our troubleshooting documentation](/serverless/jobs/troubleshooting/job-in-error-state/) to solve the issue.
+* **Canceled**: your Serverless Job run has been canceled by the user.
 
 ## Stateless
 
 Refers to a system or application that does not maintain any persistent state between executions. In a stateless environment, each request or operation is independent, and no information is retained from previous interactions.
 
 This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others.
 
-To store informations you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), [Scaleway Serverless Databases](/serverless/sql-databases/).
+To store data you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless/sql-databases/).
 
 ## vCPU-s