docs(srv): update

Author: SamyOubouaziz

pages/serverless-containers/concepts.mdx

@@ -91,7 +91,13 @@ gRPC is supported on Serverless Containers, as long as you have enabled http2 (`
 
 ## Health check
 
-To determine the status of a container, the default health check automatically checks if basic requirements are met, to define the status as `ready`.
+To determine the status of a container, the default health check automatically checks if basic requirements are met, to define the status as `ready`. You can customize the following elements to better fit your use case:
+- The **probe type** defines the type of check to perform to define if your container is ready:
+    - The **TCP** probe will check if the TCP connection of your Serverless Container is opened on the specified port
+    - THe **HTTP** probe allows you to define a custom path to your Serverless Container to get the readiness status. It can be useful to check if all requirements are met, such as the connection to database, etc. 
+- The **failure threshold** corresponds to the maximum number of checks that can fail before declaring the Serverless Container in error. Defaults to 30.
+- The **interval** corresponds to the duration in seconds between every checks. Defaults to 10 seconds.
+- The **path** (HTTP probe type only) corresponds to the endpoint to call you Serverless Container (example: `/health`).
 
 You can define custom health check rules via the [Scaleway console](/serverless-containers/how-to/manage-a-container/) [specific endpoint via the Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-containers-create-a-new-container).