Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>
Co-authored-by: Thomas TACQUET <[email protected]>

Author: 3 people

pages/serverless-containers/faq.mdx

@@ -141,7 +141,7 @@ Ensure that your code avoids heavy computations or long-running initialization a
 
 ### Which Linux syscalls are supported?
 
-- [Sandbox](/serverless-containers/concepts/#sandbox) v1 guarantees a full compatibility with Linux syscalls.
+- [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.
 
@@ -182,7 +182,7 @@ For now, the `HEALTHCHECK` Docker directive has no impact on container readiness
 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, but either a local [ephemeral storage](/serverless-containers/concepts/#ephemeral-storage), or a network file system.
+- 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.