Apply suggestions from code review

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

Author: 3 people

faq/serverless-containers.mdx

@@ -39,15 +39,15 @@ This process ensures a seamless update experience, minimizing user disruption du
 
 ## Can I upgrade Serverless Container resources (vCPU and RAM) at any time?
 
-Yes, Serverless Containers ressources can be changed at any time without causing downtime, see previous question.
+Yes, Serverless Containers resources can be changed at any time without causing downtime - see the previous question for full details.
 
 ## How does scaling work in these serverless services?
 
-Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases—more requests or events—the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention.
+Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention.
 
 ## How do I integrate my serverless solutions with other Scaleway services?
 
-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.
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), 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 migrate existing applications to Serverless Containers?
 
@@ -188,26 +188,26 @@ solutions like Scaleway Object Storage.
 Currently, a new container 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/containers/concepts/#stateless), local storage is ephemeral.
+Serverless resources are by default [stateless](/serverless/containers/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
 
-* **Serverless Databases**: Go full serverless and take the complexity out of PostgreSQL database operations.
-* **Managed MySQL / PostgreSQL**: Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
-* **Managed Database for Redis®**: Fully managed Redis®* in seconds.
-* **Managed MongoDB®**: Get the best of MongoDB® and Scaleway in one database.
+* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
+* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* [Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds.
+* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
 
 ### Storage
 
-* **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.
+* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
+* [Scaleway Glacier](/storage/object/): 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.
+Explore all Scaleway products in 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.
+Further integrations are also possible even if not listed above, for example, [Secret Manager](/identity-and-access-management/secret-manager/) can help you to store information that requires versioning.
 </Message>

faq/serverless-functions.mdx

@@ -10,13 +10,13 @@ category: serverless
 productIcon: FunctionsProductIcon
 ---
 
-## 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 are the cost benefits of using serverless services like Serverless Containers and Serverless Functions?
 
@@ -26,20 +26,20 @@ With serverless, you only pay for the compute resources you actually use. There
 
 Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases—more requests or events—the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention.
 
-## Does updates of Serverless Function can cause downtime?
+## Can updates of Serverless Function cause downtime?
 
-No, when deploying a new version of your Serverless Function generates a **rolling update**. This means that a new version of the service is gradually
+No, deploying a new version of your Serverless Function generates a **rolling update**. This means that a 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 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 them.
 
-## Can I update Serverless Function ressources (vCPU and RAM) at any time?
+## Can I upgrade Serverless Function resources (vCPU and RAM) at any time?
 
-Yes, Serverless Functions ressources can be changed at any time without causing downtime, see previous question.
+Yes, Serverless Functions resources can be changed at any time without causing downtime, see the previous question for full details.
 
 ## How do I integrate my serverless solutions with other Scaleway services?