Apply suggestions from code review

Co-authored-by: Benedikt Rollik <[email protected]>

Author: RoRoJ

network/interlink/reference-content/configuring.mdx

@@ -60,7 +60,7 @@ Only one allowed routes list (routing policy) can be attached to an InterLink at
 Once you have attached a VPC and defined the routing policy/allowed routes, you must [activate route propagation](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your allowed routes list / routing policy to be announced in the BGP session, so that traffic can flow along these routes. 
 
 <Message type="important">
-Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka allowed routes list) to the InterLink to allow traffic to flow.
+Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka [allowed routes list](/network/interlink/concepts/#allowed-routes-list) to the InterLink to allow traffic to flow.
 </Message>
 
 You can deactivate route propagation via the dedicated endpoint at any time. When you do this, all routes are blocked and removed from the VPC's route table. No traffic can flow across the InterLink until route propagation is reactivated.

network/interlink/reference-content/overview.mdx

@@ -1,10 +1,10 @@
 ---
 meta:
-  title: InterLink - technical overview
+  title: InterLink - Technical overview
   description: Dive deeper into understanding Scaleway's InterLink product, with technical diagrams, explanations and more.
   noindex: true
 content:
-  h1: InterLink - technical overview
+  h1: InterLink - Technical overview
   paragraph: Dive deeper into understanding Scaleway's InterLink product, with technical diagrams, explanations and more.
   noindex: true
 tags: interlink pop infrastructure diagram technical overview