fix(vpc): routing

Author: RoRoJ

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

@@ -82,7 +82,7 @@ From TODO DATE, new routing behavior is available for VPCs.
 
 |  | Old behavior | New behavior |
 |---|---|---|
-| Custom routes | Custom route advertisements are scoped only to the Private Network(s) to which the “next hop” resource is directly attached. | Custom route advertisements are scoped to the entire Private Network as standard. |
+| Custom routes | Custom route advertisements are scoped only to the Private Network(s) to which the “next hop” resource is directly attached. | Custom route advertisements are scoped to the entire VPC as standard. |
 | Default routes | Public Gateways' default route advertisements are scoped only to the Private Network(s) to which the gateway is attached.<br/><br/>Private Networks cannot receive default route advertisements from Public Gateways they are not directly attached to. | Standard behavior remains unchanged, but now each Private Network can opt in to receive default route advertisements from across the entire VPC. |
 
 ### Custom routes
@@ -129,7 +129,7 @@ Your existing setup may be impacted by the new behavior if you want your custom
 
 ### Example use of NACLs to mitigate impact
 
-TODO CHECK THIS EXAMPLE
+The example below shows how to achieve desired routing behavior for a custom route which is now advertised across the whole VPC.
 
 #### Scenario