Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

Author: RoRoJ

pages/vpc/concepts.mdx

@@ -68,7 +68,7 @@ When an IPv6-compatible resource is attached to a Private Network, it has a priv
 NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console.
 </Message>
 
-A VPC's Network **A**ccess **C**ontrol **L**ist is composed of stateless rules to control the flow of traffic between Private Networks. By default, the list contains no rules and therefore traffic is allowed to flow unrestrictedly between the VPC's Private Networks. Add rules to the list to start creating restrictions. [Take a deeper diver into NACLs](/vpc/reference-content/understanding-nacls/).
+A VPC's Network **A**ccess **C**ontrol **L**ist is composed of stateless rules to control the flow of traffic between Private Networks. By default, the list contains no rules, and therefore traffic is allowed to flow unrestrictedly between the VPC's Private Networks. Add rules to the list to start creating restrictions. [Take a deeper dive into NACLs](/vpc/reference-content/understanding-nacls/).
 
 ## Private IP address
 

pages/vpc/faq.mdx

@@ -48,7 +48,7 @@ Managed Databases do not currently support VPC routing - see our [dedicated docu
 
 ### Can I control traffic flow between my VPC's Private Networks?
 
-Yes, use the [Network ACL feature](/vpc/how-to/manage-nacl) to filter packets flowing between the different Private Networks of your VPC. By default all traffic is allowed to pass, until you start to add rules to the VPC's NACL.
+Yes, use the [Network ACL feature](/vpc/how-to/manage-nacl) to filter packets flowing between the different Private Networks of your VPC. By default, all traffic is allowed to pass, until you start to add rules to the VPC's NACL.
 
 <Message type="important">
 NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console.

pages/vpc/index.mdx

@@ -8,7 +8,7 @@ meta:
   sentiment="info"
   title="Network Access Control List"
 >
-  Network Access Control Lists (NACLs) are now in Public Beta, allowing you to control routing between the Private Networks of your VPC. Currently, NACLs are configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console..
+  Network Access Control Lists (NACLs) are now in Public Beta, allowing you to control routing between the Private Networks of your VPC. Currently, NACLs are configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console.
 
 </Alert>
 

pages/vpc/reference-content/understanding-nacls.mdx

@@ -1,10 +1,10 @@
 ---
 meta:
   title: Understanding Network ACLs
-  description: Learn how to Network Access Control Lists (NACL) filter inbound and outbound traffic bewteen the different Private Networks of your VPC. Understand concepts, best practices, and key use cases.
+  description: Learn how to Network Access Control Lists (NACL) filter inbound and outbound traffic between the different Private Networks of your VPC. Understand concepts, best practices, and key use cases.
 content:
   h1: Understanding Network ACLs
-  paragraph: Learn how to Network Access Control Lists (NACL) filter inbound and outbound traffic bewteen the different Private Networks of your VPC. Understand concepts, best practices, and key use cases.
+  paragraph: Learn how to Network Access Control Lists (NACL) filter inbound and outbound traffic between the different Private Networks of your VPC. Understand concepts, best practices, and key use cases.
 tags: vpc nacl network-access-control-list default-rule stateless inbound outbound port
 dates:
   validation: 2025-03-26
@@ -17,7 +17,7 @@ categories:
 NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console.
 </Message>
 
-Every VPC has a Network **A**ccess **C**ontrol **L**ist (NACL). This list is composed of stateless rules to control the flow of traffic between the Private Networks of the VPC. By default, at first the list contains no rules and therefore traffic is allowed to flow unrestrictedly. You can add rules to restrict traffic flow  according to your requirements.
+Every VPC has a Network **A**ccess **C**ontrol **L**ist (NACL). This list is composed of stateless rules to control the flow of traffic between the Private Networks of the VPC. By default, at first, the list contains no rules, and therefore traffic is allowed to flow unrestrictedly. You can add rules to restrict traffic flow according to your requirements.
 
 This document sets out general information and best practices about Scaleway VPC NACLs.
 
@@ -35,7 +35,7 @@ NACLs only control traffic as it enters or exits the Private Network(s) of a VPC
 - Filter traffic between resources attached to the same Private Network
 - Filter traffic from/to the public internet (for this, use [security groups](/instances/how-to/use-security-groups/) for Instances, or equivalent features for [other resource types](/ipam/reference-content/)).
 
-The diagram below shows how a NACL allows an Instance on Private Network A to send a packet to an Instance on Private Network 
+The diagram below shows how a NACL allows an Instance on Private Network A to send a packet to an Instance on Private Network.
 
 However, an Instance on Private Network B is blocked from sending a packet to an Instance on Private Network A, because no specific rules allow it to do so, and the default rule is set to `Deny`.
 
@@ -47,7 +47,7 @@ When defining an NACL rule, you must enter the following settings:
 
 - **IP version**: Either IPv4 or IPv6. The rule will apply only to traffic matching this IP version, meaning that in effect, each VPC has two NACLs: one for IPv4 and one for IPv6. If you want to create an equivalent rule for the other IP version, you must do so separately.
 
-- **Protocol**: Either `TCP`, `UDP` or `ICMP`. The rule will apply only to traffic matching this protocol. Alternatively, you can choose to apply it to traffic matching any protocol.
+- **Protocol**: Either `TCP`, `UDP`, or `ICMP`. The rule will apply only to traffic matching this protocol. Alternatively, you can choose to apply it to traffic matching any protocol.
 
 - **Source** and **destination**: The rule will apply to traffic originating from this source and being sent to this destination. For both, enter an IP range range in [CIDR format](/vpc/concepts/#cidr-block), and a port or port range. Alternatively, you can opt for the rule to apply to all IPs and/or all ports.
 
@@ -67,7 +67,7 @@ Therefore, if you create a rule to allow traffic in one direction, you may also
 
 Each NACL must have a default rule, which applies its action to all traffic that did not match any other rules in the list.
 
-Best practice is to set your default rule to **Deny**, and for all other rules to use the **Allow** action. In this way, you have fine-grained control over the traffic that is allowed to flow, and all other traffic is blocked by default.
+Best practice is to set your default rule to **Deny**, and use the **Allow** action for all other rules. This way, you have fine-grained control over the traffic allowed to flow, and all other traffic is blocked by default.
 
 Nonetheless, you can choose to set your default rule to **Allow** if you wish. In this case, all other rules in the list should use the **Deny** action, to filter out the specific traffic you want to block. All other traffic will be permitted by the default rule.
 
@@ -77,7 +77,7 @@ The table below shows an example of an NACL for IPv4 traffic:
 
 <Lightbox src="scaleway-nacl-example.webp" alt="A table shows a number of NACL rules" />
 
-- A number of TCP rules allow connections to the specific ports necessary for SSH, HTTP and HTTPS traffic. These rules allow all IPv4 sources within the VPC to connect to these ports, for all IPv4 destinations. 
+- A number of TCP rules allow connections to the specific ports necessary for SSH, HTTP, and HTTPS traffic. These rules allow all IPv4 sources within the VPC to connect to these ports, for all IPv4 destinations. 
 
 - An ICMP rule allows all ICMP traffic from/to all IPv4 addresses on all ports, effectively permitting all ping requests within the VPC to function.