docs(srv): add new entries to FAQ MTA-5829

pages/serverless-containers/faq.mdx

@@ -139,6 +139,12 @@ Ensure that your code avoids heavy computations or long-running initialization a
 
 * **Use sandbox v2**: We recommend you use sandbox v2 (advanced settings) to reduce cold starts.
 
+### Which Linux syscalls are supported?
+
+- [Sandbox](/serverless-containers/concepts/#sandbox) v1 guarantees full compatibility with Linux syscalls.
+
+- [Sandbox](/serverless-containers/concepts/#sandbox) v2 relies on [gVisor](https://gvisor.dev/), which implements a selection of syscalls. Refer to the [official gVisor documentation](https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/) for a comprehensive list of supported syscalls.
+
 ### What are the limitations of Serverless Containers?
 
 Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless-containers/reference-content/containers-limitations/) for more information.
@@ -171,17 +177,31 @@ 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 do I know if my application is compatible with Serverless Containers ?
+
+Your application is compatible with Serverless Containers if it meets the following criteria:
+
+- It must handle requests delivered via HTTP, HTTP/2, WebSockets, or gRPC.
+- It must not require a persistent local storage due to [ephemeral storage](/serverless-containers/concepts/#ephemeral-storage), and must use shared file storage systems like [Object Storage](https://www.scaleway.com/en/docs/object-storage/)
+- 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
 
+### Can I redirect all HTTP traffic to HTTPS?
+
+Yes, you can [redirect every inbound HTTP connections to HTTPS](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) by enabling **HTTPS connections only** in the **Security** tab of the **Advanced options** of your container.
+
 ### Can I whitelist the IPs of my containers?
 
 Serverless Containers does not yet support Private Networks. However, you can use the Scaleway IP ranges defined at [https://www.scaleway.com/en/peering/](https://www.scaleway.com/en/peering/) on Managed Databases and other products that allow IP filtering.
 
 ### Which protocols are supported by Serverless Containers?
 
-Serverless Containers use the **http1** protocol by default, but some services (e.g., gRPC) only support `http2`.
+Serverless Containers support **http1** and **http2**. **http1** is enabled by default, but some services (e.g., gRPC) only support **http2**.
 
-Protocol switching is available in the Console under the `Advanced options` section in the `Deployment` tab.
+You can [modify the protocol](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) used by your container from the **Requests tab** of the **Advanced options**.
 
 ### Why does my gRPC container not respond?
 
@@ -193,6 +213,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, you cannot use your own TLS certificates.
+
 ### 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.