docs(serverless): add entries in serverless FAQ (#3858)

Author: Bemilie

faq/serverless-containers.mdx

@@ -126,3 +126,13 @@ Scaleway Serverless Containers does not currently support Scaleway VPC or Privat
 
 To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses.
 
+## How can I attach Block Storage to a Serverless Container?
+
+Scaleway Serverless Containers do not currently support attaching block storage. These containers are designed to be
+stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external
+solutions like Scaleway Object Storage.
+
+# Why does my container have an instance running after deployment, even with min-scale 0?
+
+Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum
+scale is set to 0. This behavior is not configurable at this time.

faq/serverless-functions.mdx

@@ -173,3 +173,14 @@ Upgrading a runtime is highly recommended in case of deprecation, and for runtim
 Scaleway Serverless Functions does not currently support Scaleway VPC or Private Networks, though this feature is under development.
 
 To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Note that Serverless resources do not have dedicated or predictable IP addresses.
+
+## How can I attach Block Storage to a Serverless Function?
+
+Scaleway Serverless Functions do not currently support attaching block storage. These functions are designed to be
+stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external
+solutions like Scaleway Object Storage.
+
+# Why does my function have an instance running after deployment, even with min-scale 0?
+
+Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum
+scale is set to 0. This behavior is not configurable at this time.