diff --git a/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx b/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx
index 648af340e2..664092f49b 100644
--- a/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx
+++ b/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx
@@ -27,21 +27,6 @@ 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**.
 
-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.
-
-  Example (incomplete) settings:
-  ```
-  health_check: {
-    http: {
-        path: "/"
-    }
-  }
-  ```
-</Message>
-
-<Message type="note">
-    Custom healthcheck feature will be available in the Scaleway console for Q1 2025.
-</Message>
\ No newline at end of file
+Custom health checks allow you to define a specific endpoint that the Serverless Container must respond to before it is considered ready to receive traffic. This ensures that the container is fully initialized and ready to handle requests.
+
+Update your Serverless Container to use custom health checks by following the instructions in the [Serverless Containers documentation](/serverless-containers/how-to/manage-a-container/#how-to-manage-a-container-deployment).