fix(interlink): change allowed routes wording

Author: RoRoJ

menu/navigation.json

@@ -3260,8 +3260,8 @@
                   "slug": "configure-interlink"
                 },
                 {
-                  "label": "Created an allowed routes list",
-                  "slug": "create-allowed-routes-list"
+                  "label": "Created a routing policy",
+                  "slug": "create-routing-policy"
                 },
                 {
                   "label": "Delete an InterLink",

pages/interlink/assets/scaleway-interlink-config.webp

@@ -17,14 +17,6 @@ categories:
 InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/).
 </Message>
 
-## Allowed routes list
-
-The default rule blocks any and all routes from being propagated over InterLink. Attaching an allowed routes list (aka **routing policy**) allows you to define the ranges of routes that should be whitelisted. When creating an allowed routes list, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPC, and one or many IP ranges representing the incoming route announcements to accept from the external infrastructure. 
-
-Each InterLink can have one allowed routes list attached to it, but a single allowed routes list can be attached to multiple InterLinks, if desired. When [route propagation](#route-propagation) is activated, the route ranges defined in the allowed routes list are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
-
-You may also know allowed routes lists under the terms "routing policy", or "route filters".
-
 ## Attached VPC
 
 Each InterLink can be attached to one Scaleway VPC. The InterLink and the VPC must be in the same [region](#region). You can detach the InterLink from the VPC at any time, and attach it to a different VPC in the same region, if you wish. When an InterLink is not attached to any VPC, no traffic can flow.
@@ -80,8 +72,10 @@ When creating an InterLink, you must specify a [region](/vpc/concepts/#region-an
 
 ## Route propagation
 
-Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must use an [allowed routes list](#allowed-routes-list) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
+Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must attach a [routing policy](#routing-policy) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
 
 ## Routing policy
 
-See [Allowed routes list](#allowed-routes-list).
+The default rule blocks any and all routes from being propagated over InterLink. Attaching a routing policy allows you to define the ranges of routes that should be whitelisted. When creating a routing policy, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPC, and one or many IP ranges representing the incoming route announcements to accept from the external infrastructure. 
+
+Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired. When [route propagation](#route-propagation) is activated, the route ranges defined in the routing policy are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)

pages/interlink/concepts.mdx

@@ -20,7 +20,7 @@ InterLink is Scaleway's product to let you create a secure, private connection b
 
 Currently, InterLink is available in **hosted** version only. This means that you must choose a compatible **partner** to facilitate your InterLink. The partner provides the physical connection, and this connection may be shared between several clients, each allocated a specific amount of bandwidth for their InterLink.
 
-At its simplest level, InterLink can be understood as a configurable connection between your own infrastructure, and your Scaleway VPC. You can configure details such as bandwidth, the VPC to connect to, and the routes allowed to propagate over the InterLink.
+At its simplest level, InterLink can be understood as a configurable connection between your own infrastructure, and your Scaleway VPC. You can configure details such as bandwidth, the VPC to connect to, and routing policies.
 
 ## How can I find a partner to provision my InterLink?
 

pages/interlink/faq.mdx

@@ -35,7 +35,7 @@ After ordering the InterLink from Scaleway, you **must** contact your chosen par
 
 2. Click on the InterLink that you want to finish provisioning. The InterLink's **Overview** page displays.
 
-<Lightbox src="scaleway-interlink-overview-requesting.webp" alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status." />
+<Lightbox src="scaleway-interlink-overview-requesting.webp" alt="TODO MODIFY A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status." />
 
 3. Note down the [pairing key](/interlink/concepts/#pairing-key) for your InterLink. This is a unique identification number which the partner will need in order to provision your InterLink.
 
@@ -68,7 +68,7 @@ If your InterLink does not move to `Provisioning` status, you may see one of the
 
 When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration have been completed on the partner's side, and your InterLink is ready for use.
 
-You must still configure your InterLink by attaching it to a VPC, attaching an allowed routes list, and activating route propagation, before traffic can flow over the InterLink. For help with these steps, see our documentation on [How to configure your InterLink](/interlink/reference-content/configuring/).
+You must still configure your InterLink by attaching it to a VPC, attaching a routing policy, and activating route propagation, before traffic can flow over the InterLink. For help with these steps, see our documentation on [How to configure your InterLink](/interlink/reference-content/configuring/).
 
 <Message type="important">
 If you see a `Limited connectivity` status next to your InterLink on the [listing page](https://console.scaleway.com/interlink/links), this indicates that the partner provisioned your InterLink, but either IPv4 or IPv6 connectivity is down. Similarly, a `Down` status indicates the InterLink is provisioned, but both IPv4 **and** IPv6 connectivity are down. Open a Scaleway support ticket, or contact your partner for assistance.