fix(docs): doc review

Author: SamyOubouaziz

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

@@ -27,7 +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**.
 
-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.
+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.