Apply suggestions from code review

Co-authored-by: Néda <[email protected]>

Author: SamyOubouaziz

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

@@ -2,8 +2,8 @@
 title: Serverless Containers and Private Networks integration
 description: This page contains details on how Serverless Containers interacts with Virtual Private Cloud and Private Networks
 dates:
-  - posted: 2025-07-29
-  - validation: 2025-07-29
+  posted: 2025-07-29
+  validation: 2025-07-29
 ---
 
 ## Compatibility
@@ -14,8 +14,8 @@ Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and
 
 - Containers in the same namespace can be attached to different Private Networks.
 - Both [sandbox](/serverless-containers/concepts/#sandbox) environments (`V1` and `V2`) are compatible with Private Networks.
-- Attaching Serverless Containers to Private Networks **does not entail additional cost**.
-- **Egress** (outbound private traffic from a container to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be through the public endpoint of the container.
+- Attaching Serverless Containers to Private Networks **does not incur additional cost**.
+- **Egress** (outbound private traffic from a container to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be routed through the public endpoint of the container.
 - All DNS resolution is done through the Private Network (using the VPC DNS server `169.254.169.254`), which allows to resolve `*.internal` records.
 
 ## Quotas

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

@@ -14,8 +14,8 @@ Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and c
 
 - Functions in the same namespace can be attached to different Private Networks.
 - Both [sandbox](/serverless-functions/concepts/#sandbox) environments (`V1` and `V2`) are compatible with Private Networks.
-- Attaching Serverless Functions to Private Networks **does not entail additional cost**.
-- **Egress** (outbound private traffic from a function to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be through the public endpoint of the function.
+- Attaching Serverless Functions to Private Networks **does not incur additional cost**.
+- **Egress** (outbound private traffic from a function to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be routed through the public endpoint of the function.
 - All DNS resolution is done through the Private Network (using the VPC DNS server `169.254.169.254`), which allows to resolve `*.internal` records.
 
 ## Quotas