fix(docs): doc review

Author: SamyOubouaziz

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, sending the message will be retried up to three times.
+  **Retry Policy:** If the Container returns a status code superior or equal to 300, 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, sending the message will be retried up to three times.
+  **Retry Policy:** If the Container returns a status code superior or equal to 300, sending the message will be retried up to three times.
 </Message>
 
 ## CRON triggers

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

@@ -1,10 +1,10 @@
 ---
 meta:
   title: Error code 502
-  description: Troubleshoot 502 issues while sending requests to Serverless Containers.
+  description: Troubleshoot 502 error codes while sending requests to Serverless Containers.
 content:
   h1: Error code 502
-  paragraph: Troubleshoot 502 issues while sending requests to Serverless Containers.
+  paragraph: Troubleshoot 502 error codes while sending requests to Serverless Containers.
 tags: serverless Containers troubleshooting issue error 502
 dates:
   validation: 2025-01-03
@@ -27,9 +27,7 @@ This issue typically occurs when traffic is sent too early to the newly created
 
 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 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.
-
-* [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.
+You can configure [Custom health checks via the Scaleway API]@(https://www.scaleway.com/en/developers/api/serverless-containers/#path-containers-update-an-existing-container) with the `health_check` parameter. In this case, we recommend you implement a custom HTTP route on the Container that returns its readiness status.
 
 <Message type="tip">
   A simple health check to implement is just a simple `GET` on `/` to make sure the HTTP server is properly listening.
@@ -43,7 +41,3 @@ To ensure the Serverless Container is completely ready, both in terms of the HTT
     }
   ```
 </Message>
-
-<Message type="note">
-    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, sending the message will be retried up to three times.
+  **Retry Policy:** If the Function returns a status code superior or equal to 300, 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, sending the message will be retried up to three times.
+  **Retry Policy:** If the Function returns a status code superior or equal to 300, sending the message will be retried up to three times.
 </Message>
 
 ## CRON triggers