Update pages/serverless-containers/reference-content/containers-private-networks.mdx

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

Author: SamyOubouaziz

pages/serverless-containers/reference-content/containers-private-networks.mdx

@@ -25,7 +25,7 @@ Refer to the [dedicated documentation](/organizations-and-projects/additional-co
 ## 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.
-- Only one Private Network can be attached to a container.
+- Only one Private Network can be attached to a Serverless Container.
 - **VPC routing** (custom routes and cross-PN automatic routing) is not supported yet.
 - **Ingress** (inbound private traffic from resources to a container within the same Private Network) is not supported yet.
 - Each [container instance](/serverless-containers/concepts/#instance) has a unique IP automatically assigned by Scaleway in the Private Network. This implies the following: