feat(srv): update

Author: SamyOubouaziz

pages/serverless-functions/concepts.mdx

@@ -113,9 +113,21 @@ The function can then process the message and perform any required actions, such
 
 A function's privacy policy defines whether a function may be executed anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-functions/#authentication) (**private**).
 
-## Private Networks compatibility
+## Private Networks
 
-Refer to the [dedicated FAQ](/serverless-functions/faq/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Functions compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
+Scaleway Serverless Functions support Private Networks.
+
+Private Networks let you connect Scaleway resources across multiple AZs within the same region. Attached resources can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet.
+
+**D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP) is built into each Private Network, making it easy to manage the private IP addresses of your resources on the network.
+
+Read our dedicated documentation on [creating a Private Network](/vpc/how-to/create-private-network/).
+
+<Message type="note">
+Previously, Private Networks at Scaleway were zoned. Only resources from within one defined AZ could be attached to each network. Now, all Private Networks are regional, and resources from any AZ within that network's region can be attached. "Old" zoned Private Networks have all been automatically migrated to become regional.
+
+While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/vpc/reference-content/vpc-migration/) documentation for more information.
+</Message>
 
 ## Queue trigger
 

pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx

@@ -32,6 +32,7 @@ This page shows you how to create, manage, and delete a Functions namespace usin
     - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes.
     - Enter an optional **description** and **tags**.
     - Choose a **region**, which is the geographical location in which your namespace will be deployed.
+    - Tick the **Enable VPC support** if you want to create functions within this namespace that you can attach to a [Private Network](/serverless-functions/concepts/#private-networks)
     - Click **+ Add advanced options** to define any **environment variables** you want to inject into your function. For each environment variable, click **+ Add variable** and enter the key/value pair.
     - Set optional secret environment variables. **Secrets** are environment variables which are injected into your function and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**.
 4. Click **Create namespace only** to finish, or click **Create namespace and add a function** if you want to [create a function](/serverless-functions/how-to/create-a-function/) next.

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

@@ -13,7 +13,7 @@ categories:
   - serverless
 ---
 
-[Private Networks](/vpc/concepts/#private-networks) allow your Serverless Functions to communicate in an isolated and secure network without needing to be connected to the public internet. Each function can be connected to one or several Private Networks, letting you build your own network topologies.
+[Private Networks](/serverless-functions/concepts/#private-networks) allow your Serverless Functions to communicate in an isolated and secure network without needing to be connected to the public internet. Each function can be connected to one or several Private Networks, letting you build your own network topologies.
 
 For full information about Scaleway Private Networks and VPC, see our [dedicated documentation](/vpc/) and [best practice guide](/vpc/reference-content/getting-most-private-networks/).
 
@@ -28,6 +28,10 @@ The Private Networks feature can only be enabled on newly created namespaces. Ex
 - [Created a Private Network](/vpc/how-to/create-private-network/)
 
 
+## How to create a Private Network
+
+This action must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/create-private-network/).
+
 ## How to create a Private Networks-enabled namespace
 
 Before attaching a Private Network to a Serverless Function, you must create it within a namespace with the Private Networks feature enabled.