fix(interlink): final modifs

Author: RoRoJ

pages/interlink/assets/scaleway-hosted-interlink-ordering.webp

@@ -34,6 +34,10 @@ The type of physical connection for an InterLink. InterLink is available in both
 
 [Find out more about connection types](/interlink/reference-content/overview/#types-of-interlink).
 
+## Dedicated physical connection
+
+To create a self-hosted InterLink, you must first provision a dedicated physical connection between your router and Scaleway's router. You get sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. This connection and its bandwidth can then be used to create several InterLinks. To provision a dedicated physical connection, [contact our sales team](https://www.scaleway.com/en/contact-sales/).
+
 ## InterLink
 
 InterLink, currently in Public Beta, is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet.

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

@@ -97,7 +97,7 @@ Repeat the process to attach up to two routing policies in total (one for IPv4 a
 ## How to set up your network device (self-hosted only)
 
 <Message type="note">
-This step is necessary for [self-hosted InterLinks](TODO) only. If you have a hosted InterLink, provisioned via a partner, you do not need to set up a network device.
+This step is necessary for [self-hosted InterLinks](/interlink/reference-content/overview/#self-hosted-interlink) only. If you have a hosted InterLink, provisioned via a partner, you do not need to set up a network device.
 </Message>
 
 You must configure the real physical or software-based networking device, located on the remote network you are connecting to your Scaleway VPC via the InterLink. You will need the following information, which is available from your InterLink's **Overview** screen in the Scaleway console:
@@ -127,7 +127,7 @@ Once you have attached a VPC, attached routing policies and (for self-hosted Int
 
     Route propagation is activated, and you are returned to your InterLink's overview page. 
 
-    While route propagation remains active, traffic can flow across the InterLink along the routes allowed by the routing policy. The VPC and external infrastructure will dynamically exchange and update route information. You can deactivate route propagation at any time: if you do so, all routes are blocked and no traffic can flow.
+    While route propagation remains active, traffic can flow across the InterLink along the routes allowed by the routing policy(ies). The VPC and external infrastructure will dynamically exchange and update route information. You can deactivate route propagation at any time: if you do so, all routes are blocked and no traffic can flow.
 
 ## How to modify your InterLink configuration
 

pages/interlink/assets/scaleway-interlink-overview-up.webp

@@ -31,7 +31,7 @@ If you have a hosted InterLink, action is required on both the Scaleway side and
 
         A pop-up displays, confirming that this action will permanently delete your InterLink on the Scaleway side.
 
-5. Type **DELETE** in the box, and click **Delete InterLink**.
+5. Type **DELETE** in the box, and click **Delete InterLink**, and confirm when prompted.
 
         Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic.
 
@@ -42,3 +42,5 @@ If you have a hosted InterLink, action is required on both the Scaleway side and
     </Message>
 
     When the InterLink is fully deprovisioned on both sides, it will be deleted from the list of your InterLinks, and its Overview page will no longer be accessible.
+
+    **Self-hosted InterLinks only**: [Contact sales](https://www.scaleway.com/en/contact-sales/) if you want to deprovision your dedicated physical connection.

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

@@ -43,7 +43,7 @@ This guide takes you through the process of creating an InterLink via the Scalew
 
 3. Choose a [region](/interlink/concepts/#region) for your InterLink. This must correspond to the Scaleway VPC you want to attach later.
 
-3. Select a [physical connection type](/interlink/concepts/#connection-type)for your InterLink, either [hosted](TODO) or [self-hosted](TODO).
+3. Select a [physical connection type](/interlink/concepts/#connection-type)for your InterLink, either [hosted](/interlink/reference-content/overview/#hosted-interlinks) or [self-hosted](/interlink/reference-content/overview/#hosted-interlinks).
 
 4. Select the following options, depending on your physical connection type: 
 
@@ -56,14 +56,14 @@ This guide takes you through the process of creating an InterLink via the Scalew
         Also select the [location](/interlink/concepts/#location) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established.
 
         <TabsTab label="Self-hosted">
-        Select a [dedicated connection](TODO). The InterLink will be hosted over this connection. You must have already provisioned this connection via the Scaleway sales team. [Contact sales](TODO) if you would like to provision a dedicated connection: this cannot be done via the Scaleway console or API.
+        Select a [dedicated connection](/interlink/concepts/#dedicated-physical-connection). The InterLink will be hosted over this connection. You must have already provisioned this connection via the Scaleway sales team. [Contact sales](https://www.scaleway.com/en/contact-sales/) if you would like to provision a dedicated connection: this cannot be done via the Scaleway console or API.
 
         </TabsTab>
     </Tabs>
 
 5. Choose a [bandwidth](/interlink/concepts/#bandwidth) amount. This represents the maximum bandwidth that will be available over the InterLink.
 
-6. Attach up to two [routing policies](TODO). InterLink needs a policy for each IP traffic type it should route: all routes are blocked except those whitelisted in the policy(ies). Alternatively, skip this step and attach routing policies later.
+6. Attach up to two [routing policies](/interlink/concepts/#dedicated-physical-connection). InterLink needs a policy for each IP traffic type it should route: all routes are blocked except those whitelisted in the policy(ies). Alternatively, skip this step and attach routing policies later.
 
 7. Enter a name and optional tags for your InterLink.
 
@@ -72,7 +72,7 @@ This guide takes you through the process of creating an InterLink via the Scalew
 - **Hosted InterLink**: You must now contact your chosen partner to request they provision your InterLink from their end. Note that Scaleway starts billing you for the InterLink as soon as you create it, and your partner may charge you additional fees once provisioned on their end. For full details of the provisioning process, including how to contact your partner and what other steps you need to take, see the page [How to complete hosted InterLink provisioning](/interlink/how-to/complete-provisioning/).
     <Lightbox image={image3} alt="A four step flow chart shows the following steps: 1. User orders InterLink via Scaleway, 2. User requests InterLink from partner, 3. Partner accepts InterLink request, 4. Partner provisions InterLink." /> 
 
-- **Self-hosted InterLinks**: Your InterLink is now fully created. However, you must complete InterLink setup on the customer side by configuring your network device. For full details, see [How to complete self-hosted InterLink setup](TODO)
+- **Self-hosted InterLinks**: Your InterLink is now fully created. However, you must complete InterLink setup on the customer side by configuring your network device. For full details, see [How to complete self-hosted InterLink setup](/interlink/how-to/configure-interlink/#how-to-set-up-your-network-device-self-hosted-only)
     <Lightbox image={image4} alt="A four step flow chart shows the following steps: 1. User orders InterLink via Scaleway, 2. User requests InterLink from partner, 3. Partner accepts InterLink request, 4. Partner provisions InterLink." /> 
 
 <Message type="note">