docs(srv): add ref content on VPC x F/CaaS MTA-6319

pages/serverless-containers/how-to/use-private-networks.mdx

@@ -87,4 +87,8 @@ Your container is redeployed and is now detached from the Private Network.
   Before deleting a Private Network, you must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources attached to it.
 </Message>
 
-This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/).
+This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/).
+
+## Private Networks and containers limitations
+
+For more information on limitations when using Private Networks with Serverless Containers, refer to the [dedicated documentation](/serverless-containers/reference-content/containers-limitations/#private-networks-and-virtual-private-cloud-vpc).

pages/serverless-containers/reference-content/containers-limitations.mdx

@@ -88,6 +88,12 @@ Do not have your containers listen on these ports, as they are used by our servi
 
 Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-containers/how-to/use-private-networks/) for more information.
 
+### Usage
+
+- Containers in the same namespace can be attached to different Private Networks.
+
+- Attaching Serverless Containers to Private Networks does not entail additional cost.
+
 ### Limitations
 
 - VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-containers/how-to/create-manage-delete-containers-namespace/#creating-a-serverless-containers-namespace), and cannot be updated afterward.

pages/serverless-functions/how-to/use-private-networks.mdx

@@ -87,4 +87,8 @@ Your function is redeployed and is now detached from the Private Network.
   Before deleting a Private Network, you must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources attached to it.
 </Message>
 
-This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/).
+This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/).
+
+## Private Networks and functions limitations
+
+For more information on limitations when using Private Networks with Serverless Functions, refer to the [dedicated documentation](/serverless-functions/reference-content/functions-limitations/#private-networks-and-virtual-private-cloud-vpc).

pages/serverless-functions/reference-content/functions-limitations.mdx

@@ -66,6 +66,12 @@ Due to potential abuse (spam), no outbound traffic is allowed through following
 
 ## Private Networks and Virtual Private Cloud (VPC)
 
+### Usage
+
+- Functions in the same namespace can be attached to different Private Networks.
+
+- Attaching Serverless Functions to Private Networks does not entail additional cost.
+
 ### Compatibility
 
 Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information.