Apply suggestions from code review

Co-authored-by: Benedikt Rollik <[email protected]>

Author: thomas-tacquet

serverless/containers/how-to/add-trigger-to-a-container.mdx

@@ -56,7 +56,7 @@ The configuration of the queue retention can affect the behavior of the trigger.
 When a message is pushed to the selected queues, the container will be triggered with the message content passed in the event object's body.
 
 <Message type="note">
-  **Retry Policy:** if the Container returns a status code >= 3XX it will send the message again up to 3 times.
+  **Retry Policy:** If the Container returns a status code >=3XX, sending the message will be retried up to three times.
 </Message>
 
 ## NATS triggers
@@ -74,7 +74,7 @@ When a message is pushed to the selected queues, the container will be triggered
 7. Click **Create trigger** to launch the trigger creation.
 
 <Message type="note">
-  **Retry Policy:** if the Container returns a status code >= 3XX it will send the message again up to 3 times.
+  **Retry Policy:** If the Container returns a status code >=3XX, sending the message will be retried up to three times.
 </Message>
 
 ## CRON triggers

serverless/containers/troubleshooting/502-error-when-scaling.mdx

@@ -15,21 +15,21 @@ categories:
 
 ## Problem
 
-In some cases 502 errors can occur on Serverless Containers during autoscaling process: when the system creates new instances of the Container.
+502 errors can sometimes occur on Serverless Containers during the autoscaling process when new container instances are being created.
 
 ### Cause
 
-When the new instance is created, Serverless healthcheck verification is by default done on the HTTP port. Once it's opened, the ressource is considered ready and traffic starts to be forwarded to it.
+When a new instance is created, the Serverless health check verification is performed by default on the HTTP port. Once the port is opened, the resource is considered ready, and traffic starts being forwarded to it.
 
-This is commonly due to the traffic being sent too early to the newly created Container.
+This issue typically occurs when traffic is sent too early to the newly created container before it is fully deployed.
 
 ### Possible solutions
 
-To ensure the Serverless Container is completly ready, not only the HTTP port opened but also in the software scope the solution is to use **custom healthchecks**.
+To ensure the Serverless Container is completely ready, both in terms of the HTTP port and the software scope, it is recommended to use **custom health checks**.
 
-**Custom healthchecks** are available via the API, in this case it's recommended to implement a custom http route on the Container that returns the readiness status.
+**Custom health checks** can be configured via the API; in this case, it's recommended to implement a custom HTTP route on the Container that returns its readiness status.
 
-* [Link to API documentation](https://www.scaleway.com/en/developers/api/serverless-containers/#path-containers-update-an-existing-container): look for `health_check`.
+* [API Documentation for custom health checks](https://www.scaleway.com/en/developers/api/serverless-containers/#path-containers-update-an-existing-container) - Refer to the `health_check` parameter.
 
 <Message type="tip">
   A simple health check to implement is just a simple `GET` on `/` to make sure the HTTP server is properly listening.
@@ -45,5 +45,5 @@ To ensure the Serverless Container is completly ready, not only the HTTP port op
 </Message>
 
 <Message type="note">
-    Custom healthcheck feature will be available in the Scaleway console for Q1 2025.
+    The custom health check feature will be available in the Scaleway console in Q1 2025.
 </Message>

serverless/functions/how-to/add-trigger-to-a-function.mdx

@@ -54,7 +54,7 @@ The configuration of the queue retention may affect the behavior of the trigger.
 7. Click **Create trigger** to launch trigger creation.
 
 <Message type="note">
-  **Retry Policy:** if the Function returns a status code >= 3XX it will send the message again up to 3 times.
+  **Retry Policy:** If the Function returns a status code >=3XX, sending the message will be retried up to three times.
 </Message>
 
 ## NATS triggers
@@ -72,7 +72,7 @@ Scaleway [NATS subjects](/serverless/messaging/quickstart/#quickstart-for-nats)
 7. Click **Create trigger** to launch trigger creation.
 
 <Message type="note">
-  **Retry Policy:** if the Function returns a status code >= 3XX it will send the message again up to 3 times.
+  **Retry Policy:** If the Function returns a status code >=3XX, sending the message will be retried up to three times.
 </Message>
 
 ## CRON triggers