Update pages/serverless-containers/concepts.mdx

Co-authored-by: Jessica <[email protected]>

Author: SamyOubouaziz

pages/serverless-containers/concepts.mdx

@@ -96,7 +96,7 @@ To determine the status of a container, the default health check automatically c
     - 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 **interval** corresponds to the duration in seconds between every check. 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/) or set a [specific endpoint via the Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-containers-create-a-new-container).