fix(interlink): meta

RoRoJ · RoRoJ · commit c7f97265ed41 · 2025-08-12T11:39:42.000+02:00
diff --git a/pages/interlink/concepts.mdx b/pages/interlink/concepts.mdx
@@ -38,6 +38,10 @@ The type of physical connection for an InterLink. InterLink is available in both
 
 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/).
 
+## Hosted InterLink
+
+See [connection type](#connection-type).
+
 ## 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.
@@ -76,4 +80,8 @@ Route propagation can be activated or deactivated at any given time on an InterL
 
 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. 
 
-IPv4 and IPv6 routes must be whitelisted in separate routing policies. An InterLink must therefore have a **minimum of one** and a **maximum of two** attached routing policies, one for each IP traffic type to be routed (IPv4 and/or IPv6). When [route propagation](#route-propagation) is activated, the route ranges defined in the attached routing polic(ies) 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)
+IPv4 and IPv6 routes must be whitelisted in separate routing policies. An InterLink must therefore have a **minimum of one** and a **maximum of two** attached routing policies, one for each IP traffic type to be routed (IPv4 and/or IPv6). When [route propagation](#route-propagation) is activated, the route ranges defined in the attached routing polic(ies) 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).
+
+## Self-hosted InterLink
+
+See [connection type](#connection-type).
diff --git a/pages/interlink/faq.mdx b/pages/interlink/faq.mdx
@@ -1,8 +1,15 @@
 ---
+<<<<<<< HEAD
 title: InterLink FAQ
 description: Discover Scaleway InterLink and find answers to your most common questions.
 dates:
   validation: 2025-03-18
+=======
+title: InterLink
+description: Discover Scaleway InterLink and find answers to your most common questions.
+dates:
+  validation: 2025-07-09
+>>>>>>> d1722557a (fix(interlink): meta)
 productIcon: InterlinkProductIcon
 ---
 
@@ -26,7 +33,7 @@ You can see available partners in the Scaleway console by opening the [InterLink
 
 ## I want to create a dedicated InterLink without a partner, how can I do this?
 
-You can create a **self-hosted** InterLinks available soon, whereby a single client can provision their own physical connection without a partner, getting sole use of a single InterLink port on Scaleway's router. The bandwidth of this connection can then be used by the client to create several InterLinks just for them.
+You can create a **self-hosted** InterLink, provisioning your own physical connection without a partner, getting sole use of a single InterLink port on Scaleway's router. You can then use the bandwidth of this connection to create several InterLinks just for you.
 
 [Contact a sales representative](https://www.scaleway.com/en/contact-sales/) to register your interest in a self-hosted InterLink. The process of provisioning the dedicated physical connection must be done via our sales team, and cannot be achieved via the Scaleway console or developer tools.
 
diff --git a/pages/interlink/how-to/complete-provisioning.mdx b/pages/interlink/how-to/complete-provisioning.mdx
@@ -1,5 +1,9 @@
 ---
+<<<<<<< HEAD
 title: How to complete InterLink provisioning
+=======
+title: How to complete hosted InterLink provisioning
+>>>>>>> d1722557a (fix(interlink): meta)
 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-07-09
diff --git a/pages/interlink/how-to/configure-interlink.mdx b/pages/interlink/how-to/configure-interlink.mdx
@@ -6,6 +6,7 @@ dates:
   posted: 2025-03-18
 tags: interlink direct-connect configure attach-vpc route-propagation allowed-routes routing-policy
 ---
+
 import Requirements from '@macros/iam/requirements.mdx'
 
 import image from './assets/scaleway-interlink-config.webp'
diff --git a/pages/interlink/how-to/order-interlink.mdx b/pages/interlink/how-to/order-interlink.mdx
@@ -1,5 +1,9 @@
 ---
+<<<<<<< HEAD
 title: How to order an InterLink
+=======
+title: How to create an InterLink
+>>>>>>> d1722557a (fix(interlink): meta)
 description: Learn how to create an InterLink to connect your external infrastructure to your Scaleway cloud, either hosted by a partner or self-hosted with your own physical connection. Step-by-step guide included.
 dates:
   validation: 2025-07-09
@@ -43,7 +47,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](/interlink/reference-content/overview/#hosted-interlinks) or [self-hosted](/interlink/reference-content/overview/#hosted-interlinks).
+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: 
 
diff --git a/pages/interlink/index.mdx b/pages/interlink/index.mdx
@@ -5,8 +5,8 @@ description: Dive into Scaleway InterLink with our quickstart guides, how-tos, t
 
 <Message
   type="note"
-  title="InterLink is now in Public Beta">
-  InterLink is now available in [Public Beta](https://www.scaleway.com/en/betas/). Check it out on the [Scaleway console](https://console.scaleway.com/interlink/) or [API](https://www.scaleway.com/en/developers/api/interlink/), and order your InterLink today.
+  title="Self-hosted InterLink now available">
+  You can now create self-hosted InterLinks without a partner, by provisioning your own dedicated physical connection to Scaleway's router. Find out more in our [dedicated documentation](/interlink/reference-content/overview/#self-hosted-interlink).
 </Message>
 
 <ProductHeader
diff --git a/pages/interlink/quickstart.mdx b/pages/interlink/quickstart.mdx
@@ -43,7 +43,7 @@ InterLink is Scaleway's product to let you create a secure, private connection b
 
 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](/interlink/reference-content/overview/#hosted-interlinks) or [self-hosted](/interlink/reference-content/overview/#self-hosted-interlink).
+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/#self-hosted-interlink).
 
 4. Select the following options, depending on your physical connection type: 
 
@@ -77,7 +77,9 @@ InterLink is Scaleway's product to let you create a secure, private connection b
 
 ## How to complete hosted InterLink provisioning.
 
+<Message type="note">
 **These steps apply to hosted InterLink's (via partners) only.** For self-hosted InterLinks, continue to [how to configure your InterLink](#how-to-configure-your-interlink)
+</Message>
 
 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays.
 
diff --git a/pages/interlink/reference-content/configuring.mdx b/pages/interlink/reference-content/configuring.mdx
@@ -1,6 +1,10 @@
 ---
 title: Configuring an InterLink
+<<<<<<< HEAD
 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.
+=======
+ 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.
+>>>>>>> d1722557a (fix(interlink): meta)
 tags: interlink configuration attach-vpc whitelist route-range ip-prefix route-propagation
 dates:
   validation: 2025-07-10
diff --git a/pages/interlink/reference-content/provisioning.mdx b/pages/interlink/reference-content/provisioning.mdx
@@ -1,5 +1,5 @@
 ---
-title: Provisioning an InterLink
+title: Provisioning a hosted InterLink
 description: Get help with understanding all the different stages of ordering and provisioning a hosted Scaleway InterLink, from placing the initial order, to dealing with error messages, and deleting the resource if no longer needed.
 tags: interlink provision order steps partner process error
 dates:
