fix(vpc): finished first draft

Author: RoRoJ

pages/vpc/how-to/assets/scaleway-nacl-empty.webp

@@ -35,20 +35,22 @@ You cannot use NACLs to restrict traffic flow over resources' public network int
 
     - If you have already added rules to the list, then traffic flow is controlled according to the rules' restrictions:
 
-    <Lightbox src="scaleway-nacl-list.webp" alt="A screenshot of the NACL tab in the Scaleway console shows three rules: two with a DENY action, and then the final default rule for ALLOW." />
+    <Lightbox src="scaleway-nacl-screen.webp" alt="A screenshot of the NACL tab in the Scaleway console shows a list of rules." />
 
 ## How to read and interpret a NACL
 
-The following guidance applies when reading a VPC's NACL.
+The following guidance applies when reading a VPC's NACL. For more detailed information and examples, see our [in-depth guide to understanding NACLs](/vpc/reference-content/understanding-nacls/).
 
 ### IPv4 and IPv6 
 
+TODO REDO FOR LIST ABOVE ONCE CONSOLE AVAILABLE
 <Lightbox src="scaleway-nacl-list-ip.webp" alt="A screenshot of the NACL tab in the Scaleway console highlights the IPv4-IPv6 toggle" />
 
 IPv4 and IPv6 traffic is filtered separately. Each VPC has two distinct NACLs: one for IPv4 and one for IPv6. Use the toggle to switch between these lists. You must manage and create rules for each list separately.
 
 ### Rule priority and application 
 
+TODO REDO FOR LIST ABOVE ONCE CONSOLE AVAILABLE
 <Lightbox src="scaleway-nacl-list-prio.webp" alt="A screenshot of the NACL tab in the Scaleway console indicates that the topmost rule in the list has the highest priority" />
 
 **Read the list from from top to bottom**. Rules closer to the top of the list are applied first. If traffic matches an NACL rule for an **Allow** or **Deny** action, the action is applied immediately. That traffic is not then subject to any further filtering or any further actions by any rules that follow. 
@@ -59,16 +61,23 @@ IPv4 and IPv6 traffic is filtered separately. Each VPC has two distinct NACLs: o
 
 This means that if you create a rule to allow traffic in one direction, you may also need a separate rule to allow the response in the opposite direction. There is a functionality to auto-generate matching inverse rules for this purpose when creating a new rule.
 
+TODO IMAGE WITH INVERSE RULE FOR POSTGRESQL (USE EXAMPLE ABOVE AND CREATE INVERSE) 
+
 ### NACL default rule
 
 <Lightbox src="scaleway-nacl-list-default.webp" alt="A screenshot of the NACL tab in the Scaleway console highlights the default rule at the bottom of the list" />
+TODO REDO FOR LIST ABOVE ONCE CONSOLE AVAILABLE
 
 **A default rule is auto-generated at the end of the list** This rule is generated at the moment you first start to edit your NACL. It carries out its action on all traffic that did not match any other rule in the list.
 
-If you wish, you can modify the default rule to change its action from `DENY` to `ALLOW` (as in the screenshot above). In this case, it allows all traffic that did not match any other rule in the list, to pass.
+If you wish, you can modify the default rule to change its action from `DENY` to `ALLOW`, to allow all traffic that did not match any other rule in the list, to pass. However, this is not considered best practice. It is recommended to leave the default rule of `DENY` and use specific `ALLOW` rules higher up the list.cd 
 
 ## How to add rules to a NACL
 
+<Message type="tip">
+The steps below explain the mechanics of creating an NACL rule in the console. For help with constructing a meaningful and effective NACL, see our [in-depth guide to understanding NACLs](/vpc/reference-content/understanding-nacls/) for best practices and examples.
+</Message>
+
 1. Click **VPC** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. The list of your VPCs displays.
 
 2. Click the VPC whose NACL you want to view, then click the **Network ACL** tab.

pages/vpc/how-to/assets/scaleway-nacl-screen.webp

@@ -6,9 +6,9 @@ meta:
 
 <Alert
   sentiment="info"
-  title="VPC Basic Use Case"
+  title="Secure your VPC with Network ACL rules"
 >
-  Read our [Basic VPC use case](/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates.
+  You can now filter and control traffic flow across the Private Networks of your VPC with our new [Network ACL](/vpc/reference-content/understanding-nacls/) feature.
 
 </Alert>