feat(interlink): private beta doc

Author: RoRoJ

network/interlink/index.mdx

@@ -9,15 +9,15 @@ meta:
   sentiment="info"
   title="InterLink is now in Private Beta"
 >
-  InterLink is currently available in [Private Beta](https://www.scaleway.com/en/betas/) only, for selected testers.
+  InterLink is currently available in [Private Beta](https://www.scaleway.com/en/betas/) only, for selected testers. Watch this space for more information on public availability.
 </Alert>
 
 <ProductHeader 
    productName="InterLink"
    productLogo="interlink"
    description="InterLink lets you create a secure, private connection between your external infrastructure, and your Scaleway VPC."
-   url="https://www.scaleway.com/en/developers/api/api/interlink/#quickstart"
-   label="InterLink Quickstart"
+   url="/network/interlink/reference-content/overview/"
+   label="InterLink Overview"
 />
 
 ## Getting Started

network/interlink/reference-content/configuring.mdx

@@ -40,7 +40,7 @@ You must wait until the InterLink has reached `Active` [status](/network/interli
 ### 2. Attach VPC
 
 Attaching an InterLink to a VPC allows you to complete the connection from your external infrastructure, across the InterLink, to the Scaleway resources in the selected VPC.
-z
+
 The VPC must be in the same region region as the InterLink. An InterLink can only be attached to one VPC at a time, but you are free to detach the VPC and attach a different one whenever you like.
 
 You can use the [Attach a VPC](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-vpc) endpoint to attach a VPC to a given InterLink.

network/interlink/reference-content/overview.mdx

@@ -71,11 +71,11 @@ When both BGP sessions are up, the InterLink has `Active` status. If one BGP ses
 
 ### Allowed routes list
 
-By default, **all route announcements from both sides are blocked** by InterLink. This is part of a safety-net mechanism to allow customers to efficiently and safely control traffic flow across the link. You must create and attach an [allowed routes list](/network/interlink/concepts/#allowed-routes-list) (aka routing policy), to specify the IP prefix announcements to whitelist from each sid. This is step one of two in allowing traffic to flow across the InterLink. See the [configuration](/network/interlink/reference-content/configuring/) page for more information on allowed routes lists. 
+By default, **all route announcements from both sides are blocked** by InterLink. This is part of a safety-net mechanism to allow customers to efficiently and safely control traffic flow across the link. You must create and attach an [allowed routes list](/network/interlink/concepts/#allowed-routes-list) (aka routing policy), to specify the IP prefix announcements to whitelist from each side. This is step one of two in allowing traffic to flow across the InterLink. See the [configuration](/network/interlink/reference-content/configuring/) page for more information on allowed routes lists. 
 
 ### Route propagation
 
-Even after attaching an allowed route list, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. When it is deactivated, no traffic can flow across the InterLink. See the [configuration](/network/interlink/reference-content/configuring/) page for more information on route propagation. 
+Even after attaching an allowed route list, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/network/interlink/reference-content/configuring/) page for more information on route propagation. 
 
 
 

network/interlink/reference-content/provisioning.mdx

@@ -21,9 +21,7 @@ InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), an
 
 The process of ordering an InterLink has multiple stages: action is required both from Scaleway, the user, and from the selected [partner](/network/interlink/concepts/#partner). When preparing your InterLink order, you must choose appropriate location (aka **P**oint **o**f **P**resence), partner and region settings to ensure compatibility with your external and Scaleway infrastructure.
 
-<Lightbox src="scaleway-interlink-diag-tech.webp" alt="TODO" />
-
-TODO change telco to partner?
+<Lightbox src="scaleway-interlink-diag-tech.webp" alt="Diagram of Scaleway’s network architecture for connecting customer infrastructure via a partner using a hosted InterLink. On the left, Scaleway’s PAR region includes a VPC with an InterLink and vRouter connected to the PAR backbone. This links to a Point of Presence (PoP) in Paris (TH2), where both Scaleway and partner routers are located. The partner’s infrastructure connects the Paris PoP to a customer or partner PoP, such as in Marseille. The customer PoP has a partner router and a customer router connected through an MMR (Meet-Me Room). The setup supports either on-premises customer infrastructure via last-mile connection or hosted customer infrastructure in the partner’s data center" />
 
 This document explains the provisioning process in full, so you know what to expect when ordering an InterLink, what action is required from all parties, and how to deal with any potential errors.
 
@@ -64,8 +62,6 @@ After ordering the InterLink from Scaleway, you **must** contact your chosen par
 
 Use the [Get a partner](https://www.scaleway.com/en/developers/api/interlink/#path-partners-get-a-partner) endpoint to get information about your selected partner. Each partner provides either a contact email address, and/or the URL of their online portal. You should make contact with your partner via one of these channels.
 
-TODO INFO ABOUT PAIRING KEY
-
 Your InterLink will remain in `Requested` status until the partner responds to your request.
 
 ### 3. Partner accepts InterLink request