docs(srv): update

Author: SamyOubouaziz

pages/serverless-containers/faq.mdx

@@ -171,6 +171,11 @@ 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 Google Cloud Run ?
+
+You can make your application compatible with Cloud Run using **http2¨¨** and gRPC.
+## Features
+
 ## Network and storage
 
 ### Can I redirect all HTTP traffic to HTTPS?
@@ -197,6 +202,10 @@ Scaleway Serverless Containers does not currently support Scaleway VPC or Privat
 
 To add network restrictions on your resource, refer to the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses.
 
+### Can I use my own TLS certificates?
+
+No.
+
 ### Can I connect to my container using SSH?
 
 No, it is not possible to connect to Serverless Containers using SSH. Serverless Containers is a fully managed, and stateless compute environment that does not provide direct access to the underlying infrastructure due to several features, such as autoscaling.