fix(nw): finish routing updates

Author: RoRoJ

pages/vpc/concepts.mdx

@@ -114,9 +114,9 @@ Routing allows resources on Private Networks witin the same VPC to communicate w
 Each routed VPC has a [route table](#route-table) which is automatically populated with routes to each of its Private Networks. When you attach a Public Gateway to a Private Network, and tell it to advertise a default route to the internet, such routes are also added to the VPC's route table. You can also create your own [custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route), to route traffic towards defined destination IP ranges towards specific "next hop" resources.
 
 <Message type="note">
-If you have [updated](TODO) routing behavior on your VPC, or created a VPC since TODODATE, routing takes on the following characteristics:
+If you have [updated](/vpc/how-to/manage-routing/#how-to-update-routing-behavior) routing behavior on your VPC, or created a VPC since TODODATE, routing takes on the following characteristics:
 - Custom routes are advertised across the entire VPC, instead of only on the Private Network of the resource designated as next hop.
-- You can optionally [enable each Private Network in the VPC to receive default route advertisements](TODO) not only from their locally attached Public Gateways, but from other Public Gateways (or default custom routes) attached to different Private Networks throughout the whole VPC. 
+- You can optionally [enable each Private Network in the VPC to receive default route advertisements](/vpc/how-to/manage-routing/#how-to-manage-default-route-scope) not only from their locally attached Public Gateways, but from other Public Gateways (or default custom routes) attached to different Private Networks throughout the whole VPC. 
 </Message>
 
 Read more about how routing works in [our detailed guide](/vpc/reference-content/understanding-routing/).

pages/vpc/how-to/manage-routing.mdx

@@ -46,7 +46,7 @@ If you created your VPC before TODODATE, you must manually update its routing be
 - Advertisement of custom routes across the entire VPC as standard.
 - Option to enable each Private Network in the VPC to receive default route advertisements not only from their locally attached Public Gateways, but from other Public Gateways (or default custom routes) attached to different Private Networks throughout the whole VPC. 
 
-For more information on these new routing behaviors, see our [detailed documentation](TODO).
+For more information on these new routing behaviors, see our [detailed documentation](/vpc/reference-content/understanding-routing/#updating-routing-behavior).
 
 Updating routing behavior is irreversible: once updated, you cannot revert. However, [Network ACLs](/vpc/reference-content/undestanding-nacls) are configurable via the API to let you finely control and restrict routes within your VPC as necessary.
 
@@ -98,7 +98,7 @@ Two types of auto-generated routes exist for VPCs:
 <Message type="note">
 By default, Public Gateways remain scoped to the Private Network(s) to which they are attached. They do not, as standard, advertise the default route on other Private Networks in the VPC. 
 
-However, each Private Network can opt in to receive default route advertisements from across the entire VPC, rather than only from locally attached gateways. This allows them to find a route to the internet even if there is no Public Gateway or default custom route on their own Private Network. See our [dedicated documentation](TODO) for full details. 
+However, each Private Network can opt in to receive default route advertisements from across the entire VPC, rather than only from locally attached gateways. This allows them to find a route to the internet even if there is no Public Gateway or default custom route on their own Private Network. See our [dedicated documentation](/vpc/reference-content/understanding-routing/#default-routes) for full details. 
 </Message>
 
 You cannot delete managed routes, as their lifecycle is fully managed by Scaleway. The route will be automatically deleted for you when you delete the Private Network or Public Gateway that it concerns.

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

@@ -59,7 +59,7 @@ Bear in mind the following when activating VPC routing:
 - Once activated on a given VPC, routing cannot be deactivated on that VPC.
 - When routing is activated, all Private Networks on the VPC can communicate.
 - Network ACLs, to finely control and filter traffic within a VPC, are in Public Beta and currently available via the [VPC API](/vpc/reference-content/understanding-nacls/) only. Alternatively, users may choose to configure NACLs directly on certain resources (e.g. Instances, Elastic Metal servers) using tools such as `iptables` or `nftables`.
-- The scope of route advertisements for custom routes and default routes to Public Gateways depends on when you created your VPC, and/or whether you have updated its routing behavior to the most recent version. [Read the full documentation below](TODO) for details.
+- The scope of route advertisements for custom routes and default routes to Public Gateways depends on when you created your VPC, and/or whether you have updated its routing behavior to the most recent version. [Read the full documentation below](#updating-routing-behavior) for details.
 
 ## Best practices
 
@@ -78,7 +78,7 @@ For example, you may use one Private Network for frontend resources and another
 From TODO DATE, new routing behavior is available for VPCs.
 
 - This routing behavior will be applied automatically to VPCs created after TODO DATE, or where routing is only activated after this date. 
-- Pre-existing VPCs must be [updated](TODO) to accept this new behavior
+- Pre-existing VPCs must be [updated](/vpc/how-to/manage-routing/#how-to-update-routing-behavior) to accept this new behavior
 
 |  | Old behavior | New behavior |
 |---|---|---|
@@ -117,7 +117,7 @@ If you wish to exercise more granular control over default route advertisements,
 
 TODO: add explanation about what happens when you're receiving multiple default route announcements?
 
-See the [documentation](TODO) on how to manage default route scope for a given Private Network, once you have [updated](TODO) to new routing behavior.
+See the [documentation](/vpc/how-to/manage-routing/#how-to-manage-default-route-scope) on how to manage default route scope for a given Private Network, once you have [updated](/vpc/how-to/manage-routing/#how-to-update-routing-behavior) to new routing behavior.
 
 ### Impact on existing setup