Apply suggestions from code review

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

Author: 2 people

pages/serverless-containers/concepts.mdx

@@ -206,32 +206,14 @@ It automatically handles infrastructure management, scaling, and load balancing,
 
 ## Serverless Functions
 
-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.
+Serverless Functions are 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, 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 Jobs
 
 Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-containers/reference-content/difference-jobs-functions-containers) for more information.
 
-## Queue trigger
-
-A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue.
-
-For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter.
-The container can then process the message and perform any required actions, such as updating a database or sending a notification.
-
-## Rolling update
-
-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 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 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 it
-
 ## 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.

pages/serverless-jobs/concepts.mdx

@@ -68,13 +68,17 @@ It automatically handles infrastructure management, scaling, and load balancing,
 
 ## Serverless Functions
 
-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.
+Serverless Functions are 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, 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 Jobs
 
+<<<<<<< HEAD:pages/serverless-jobs/concepts.mdx
 Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-jobs/reference-content/difference-jobs-functions-containers) for more information.
+=======
+Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless/jobs/reference-content/difference-jobs-functions-containers) for more information.
+>>>>>>> b19395d4f (Apply suggestions from code review):serverless/jobs/concepts.mdx
 
 ## Secrets reference