fix(interlink): update info

RoRoJ · RoRoJ · commit 3484dd11e683 · 2025-10-07T11:31:43.000+02:00
diff --git a/pages/interlink/how-to/complete-provisioning.mdx b/pages/interlink/how-to/complete-provisioning.mdx
@@ -2,7 +2,7 @@
 title: How to complete hosted InterLink provisioning
 description: Learn how to complete the provisioning process for your Scaleway InterLink, to ensure your hosted connection between your on-premises infrastructure and Scaleway VPC is up and running as soon as possible.
 dates:
-  validation: 2025-09-30
+  validation: 2025-10-07
   posted: 2025-03-18
 tags: interlink direct-connect provision hosted partner contact error
 ---
@@ -41,11 +41,11 @@ Your InterLink will remain in `Requested` status until the partner responds to y
 
 ## Wait for partner to accept InterLink request
 
-Once you have requested the InterLink from your partner, you must wait for them to respond to your request. There is no further action for you to take at this point. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console.
+Once you have requested the InterLink from your partner, you must wait for them to respond to your request. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console.
 
 When the partner approves your request, the InterLink moves to `Provisioning` status. This means that the partner has agreed to facilitate your InterLink, and is now preparing the resources and configuration necessary to do so. 
 
-Your InterLink will remain in `Provisioning` status until this process has been completed.
+Your InterLink will remain in `Provisioning` status until this process has been completed. You can [configure your InterLink](/interlink/how-to/configure-interlink/) by attaching a VPC and a routing policy(ies) while the resource is in `Requested` or `Provisioning` status, if you like.
 
 <Message type="note">
 If your InterLink does not move to `Provisioning` status, you may see one of the following statuses:
@@ -58,7 +58,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 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/).
+You must still configure your InterLink (if you haven't already done so) 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="note">
 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.
diff --git a/pages/interlink/how-to/configure-interlink.mdx b/pages/interlink/how-to/configure-interlink.mdx
@@ -2,7 +2,7 @@
 title: How to configure your InterLink
 description: Learn how to configure your Scaleway InterLink, from attaching a VPC to creating a routing policy and activating route propagation. We walk you through al the steps necessary to start using your hosted connection.
 dates:
-  validation: 2025-09-30
+  validation: 2025-10-07
   posted: 2025-03-18
 tags: interlink direct-connect configure attach-vpc route-propagation allowed-routes routing-policy
 ---
@@ -14,14 +14,14 @@ import scalewayInterlinkAttachVpc from './assets/scaleway-interlink-attach-vpc.w
 import scalewayAttachRoutingPol from './assets/scaleway-attach-routing-pol.webp'
 
 
-Once you have created your InterLink (and in the case of hosted InterLinks, it has been [provisioned](/interlink/how-to/complete-provisioning/) by your chosen partner), a number of configuration steps become available to you. These steps must be carried out in order for traffic to successfully flow over your InterLink:
+Once you have created your InterLink, you must configure it. These configuration steps must be carried out in order for traffic to successfully flow over your InterLink:
 
 - Attach a VPC
 - Create and attach routing policies
 - Set up network device (self-hosted InterLinks only) 
 - Activate route propagation
 
-<Lightbox image={scalewayInterlinkConfig} alt="A five-step flow chart shows the following steps: 1. Create InterLink, 2. Attach VPC, 3. Attach routing policies, 4. set up network device (for self hosted interlinks only), 5. Activate route propagation. After these steps are complete, traffic can flow across the InterLink" />
+<Lightbox image={scalewayInterlinkConfig} alt="A five-step flow chart shows the following steps: 1. Create InterLink, 2. Attach VPC, 3. Attach routing policies, 4. Set up network device (for self hosted interlinks only), 5. Activate route propagation. After these steps are complete, traffic can flow across the InterLink" />
 
 This document explains how to complete these configuration steps with the Scaleway console.
 
diff --git a/pages/interlink/reference-content/configuring.mdx b/pages/interlink/reference-content/configuring.mdx
@@ -3,13 +3,13 @@ title: Configuring an InterLink
 description: Find out how to set up your Scaleway InterLink so that traffic can flow between your external infrastructure and your Scaleway resources. Understand how to attach a VPC, create a routing policy to whitelist route announcements, and activate route propagation across the connection.
 tags: interlink configuration attach-vpc whitelist route-range ip-prefix route-propagation
 dates:
-  validation: 2025-09-30
+  validation: 2025-10-07
   posted: 2024-10-24
 ---
 import scalewayInterlinkConfig from './assets/scaleway-interlink-config.webp'
 
 
-Once your InterLink has been created and (for hosted InterLinks) the [partner provisioning process](/interlink/reference-content/provisioning/) is complete, you must complete a number of configuration steps to enable traffic to flow across the InterLink.
+Once your InterLink has been created, you must complete a number of configuration steps to enable traffic to flow across the InterLink.
 
 This document explains the process in full, and gives tips for troubleshooting any potential issues.
 
@@ -27,7 +27,7 @@ Creating an InterLink is itself a multi-step process:
 - **Hosted InterLinks**: [Order the dedicated physical connection](/interlink/concepts/#dedicated-physical-connection) from the Scaleway sales team, then [create the InterLink](/interlink/how-to/order-interlink/) via the Scaleway console or developer tools, specifying the dedicated physical connection to use.
 - **Self hosted InterLink**: [Create the InterLink](/interlink/how-to/order-interlink/) via the Scaleway console or developer tools, then follow the multi-step process that requires action on both the Scaleway side, and on the partner side. This process is explained in full in [Provisioning an InterLink](/interlink/reference-content/provisioning/).
 
-You must wait until the InterLink has reached `Active` or `Ready` [status](/interlink/reference-content/statuses/) before you can continue with the following configuration steps.
+You can carry out the following configuration steps even while the InterLink is in in `Requested` or `Provisioning` state, although traffic will not flow across your InterLink until it is in `Active` state.
 
 ### 2. Attach VPC
 
diff --git a/pages/interlink/reference-content/overview.mdx b/pages/interlink/reference-content/overview.mdx
@@ -3,7 +3,7 @@ title: InterLink - Technical overview
 description: Dive deeper into understanding Scaleway's InterLink product, with technical diagrams, explanations and more.
 tags: interlink pop infrastructure diagram technical overview
 dates:
-  validation: 2025-09-30
+  validation: 2025-10-07
   posted: 2024-10-24
 ---
 import scalewayInterlinkDiagSimple from './assets/scaleway-interlink-diag-simple.webp'
@@ -61,7 +61,7 @@ See our dedicated page on [provisioning an InterLink](/interlink/reference-conte
 
 ## Attaching a VPC
 
-When you initially create the InterLink, it is not associated with a specific VPC, only with a given Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. You can only attach a VPC once the provisioning process is complete, and the InterLink has `Active` status. See the [configuration](/interlink/reference-content/configuring/) page for more information.
+When you initially create the InterLink, it is not associated with a specific VPC, only with a given Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. See the [configuration](/interlink/reference-content/configuring/) page for more information.
 
 While each InterLink can only be attached to a single Scaleway VPC, it is possible to attach two InterLinks to the same VPC to ensure redundancy and high availability. In this case, each InterLink must be provisioned and configured separately, and will be billed separately. Note that you can reuse the same [routing policies](#routing-policy) across multiple InterLinks.
 
