docs(srv): update

Author: SamyOubouaziz

pages/serverless-containers/faq.mdx

@@ -177,12 +177,15 @@ You can copy an image from an external registry using the Docker CLI, or open so
 A Serverless Container is set to `ready` once the specified port is correctly bound to the container, and will start receiving traffic. If your application needs to perform some tasks before receiving traffic (e.g. connect to a database), it is important to run them before binding to the port (starting the webserver).
 For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the health check will be customizable for your applications.
 
-### How can I make my application compatible with Serverless Containers ?
+### How do I know if my application is compatible with Serverless Containers ?
 
-You can make your application compatible with Serverless Containers by:
+Your application is compatible with Serverless Containers if it meets the following criteria:
 
-- listening on port 0.0.0.0
-- responding to HTTP or gRPC requests.
+- It must handle requests delivered via HTTP, HTTP/2, WebSockets, or gRPC.
+- It must not require a persistent local storage, but either a local [ephemeral storage](/serverless-containers/concepts/#ephemeral-storage), or a network file system.
+- It must be able to handle multiple instances of the app running simultaneously.
+- It must fit the [Serverless Containers limitations](/serverless-containers/reference-content/containers-limitations/)
+- It must expose a webserver port to be accessible.
 
 ## Network and storage