fix(interlink): remove connection mentions

RoRoJ · RoRoJ · commit d5ca02501ca0 · 2025-03-27T11:04:57.000+01:00
diff --git a/menu/navigation.json b/menu/navigation.json
@@ -3298,6 +3298,10 @@
               {
                 "label": "InterLink statuses",
                 "slug": "statuses"
+              },
+              {
+                "label": "Using BGP communities",
+                "slug": "bgp-communities"
               }
             ],
             "label": "Additional Content",
diff --git a/pages/interlink/concepts.mdx b/pages/interlink/concepts.mdx
@@ -23,7 +23,7 @@ Each InterLink can be attached to one Scaleway VPC. The InterLink and the VPC mu
 
 ## Bandwidth
 
-Every InterLink has a defined bandwidth, representing the maximum data transfer rate possible over the connection. Measured in megabits per second (Mbps) or gigabits per second (Gbps), it shows how much data can be transmitted over InterLink per second.
+Every InterLink has a defined bandwidth, representing the maximum data transfer rate possible over the link. Measured in megabits per second (Mbps) or gigabits per second (Gbps), it shows how much data can be transmitted over InterLink per second.
 
 ## Border Gateway Protocol (BGP)
 
@@ -34,7 +34,7 @@ Every InterLink has a defined bandwidth, representing the maximum data transfer
 The type of physical connection for an InterLink. In the long term, InterLink will be available in both **hosted** and **self-hosted** connection types. For now, only **hosted** connections (facilitated via a partner) are available:
 
 - **Hosted InterLink**:  The customer provisions an InterLink via a [partner](#partner). The available bandwidth of the partner's physical connection is shared between multiple customers: each gets a specified amount when creating their InterLink.
-- **Self-hosted InterLink**: The customer gets sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. The customer can use available bandwidth of this dedicated physical connection to provision several InterLinks for themselves.
+- **Self-hosted InterLink**: The customer gets sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. They create their own dedicated physical connection, and can use its available bandwidth to provision several InterLinks for themselves.
 
 [Find out more about connection types](/interlink/reference-content/overview/#types-of-interlink).
 
@@ -50,17 +50,17 @@ For more information on how InterLink works, see our [detailed overview](/interl
 
 ## Location
 
-A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location where you can establish an InterLink connection between your on-premises infrastructure and the Scaleway network. Locations are facilitated by partners.
+A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location where you can establish an InterLink between your on-premises infrastructure and the Scaleway network. Locations are facilitated by partners.
 
 ## Pairing key
 
-A pairing key is a unique identifier used to establish and authenticate an InterLink connection. It is provided by Scaleway once an InterLink order is made. You must then share this key with your selected partner to facilitate the setup of the physical link. The pairing key ensures that the correct endpoints are securely connected.
+A pairing key is a unique identifier used to establish and authenticate an InterLink via a partner. It is provided by Scaleway once an InterLink order is made. You must then share this key with your selected partner to facilitate the setup of the physical link. The pairing key ensures that the correct endpoints are securely connected.
 
 ## Partner
 
-A partner is a third party service provider that facilitates a hosted InterLink connection between a client's on-premises infrastructure, and their Scaleway infrastructure. Current partners include [Free Pro](https://pro.free.fr/), with more coming soon.
+A partner is a third party service provider that facilitates a hosted InterLink between a client's on-premises infrastructure, and their Scaleway infrastructure. Current partners include [Free Pro](https://pro.free.fr/), with more coming soon.
 
-Partners are generally companies specialized in data transit, with their own fibers at data connection points. To establish an InterLink connection via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. See our information on [hosted InterLinks](/interlink/reference-content/overview/#hosted-interlinks) for more information.
+Partners are generally companies specialized in data transit, with their own fibers at data connection points. To establish an InterLink via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. See our information on [hosted InterLinks](/interlink/reference-content/overview/#hosted-interlinks) for more information.
 
 ## PoP
 
diff --git a/pages/interlink/faq.mdx b/pages/interlink/faq.mdx
@@ -24,7 +24,7 @@ At its simplest level, InterLink can be understood as a configurable connection
 
 ## How can I find a partner to provision my InterLink?
 
-To establish a hosted InterLink connection via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their data center, or on your own premises using the partner as a network provider. For more details, see our [information on choosing a partner](/interlink/reference-content/overview/how-to-choose-a-partner).
+To establish a hosted InterLink via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their data center, or on your own premises using the partner as a network provider. For more details, see our [information on choosing a partner](/interlink/reference-content/overview/how-to-choose-a-partner).
 
 You can see available partners in the Scaleway console by opening the [InterLink order form](https://console.scaleway.com/interlink/links/order). More partners will be added to Scaleway InterLink as time goes on.
 
diff --git a/pages/interlink/how-to/complete-provisioning.mdx b/pages/interlink/how-to/complete-provisioning.mdx
@@ -53,7 +53,7 @@ Once you have requested the InterLink from your partner, you must wait for them
 
 <Lightbox src="scaleway-interlink-listing.webp" alt="A screen in the Scaleway console shows a listing of InterLinks, with the following information: name, status, partner, location, region and bandwidth." />
 
-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 establish the physical connection. 
+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.
 
diff --git a/pages/interlink/how-to/create-routing-policy.mdx b/pages/interlink/how-to/create-routing-policy.mdx
@@ -53,4 +53,8 @@ Learn more about routing across an InterLink in our [detailed overview](/interli
 8. Click **Create routing policy**.
 The policy is created, and you are returned to the listing of your routing policies.
 
-Remember to [attach the policy to an InterLink](/interlink/how-to/configure-interlink/#how-to-attach-a-routing-policy) for it to take effect.  Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired.
+Remember to [attach the policy to an InterLink](/interlink/how-to/configure-interlink/#how-to-attach-a-routing-policy) for it to take effect.  Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired.
+
+<Message type="tip">
+See our dedicated documentation on using [BGP communities](/interlink/reference-content/bgp-communities/) to influence route priority for InterLink traffic.
+</Message>
diff --git a/pages/interlink/quickstart.mdx b/pages/interlink/quickstart.mdx
@@ -48,7 +48,7 @@ InterLink is Scaleway's product to let you create a secure, private connection b
 
 8. Enter a name and optional tags for your InterLink.
 
-9. Check the estimated cost for your InterLink. Note that Scaleway will start billing you for the InterLInk as soon as you order it. You must then wait for your partner to provision the connection, who may charge you additional fees.
+9. Check the estimated cost for your InterLink. Note that Scaleway will start billing you for the InterLInk as soon as you order it. You must then wait for your partner to provision the InterLink, who may charge you additional fees.
 
 10. Click **Order InterLink**.
 
@@ -74,7 +74,7 @@ Your InterLink will remain in `Requested` status until the partner responds to y
 
 <Lightbox src="scaleway-interlink-listing.webp" alt="A screen in the Scaleway console shows a listing of InterLinks, with the following information: name, status, partner, location, region and bandwidth." />
 
-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 establish the physical connection. 
+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. 
 
 When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration has been completed on the partner's side, and your InterLink is ready for use.
 
diff --git a/pages/interlink/reference-content/bgp-communities.mdx b/pages/interlink/reference-content/bgp-communities.mdx
@@ -1,10 +1,10 @@
 ---
 meta:
-  title: Using BGP community tags with InterLink
-  description: Learn how to use BGP community tags to set local preference for incoming traffic via Scaleway InterLink.
+  title: Using BGP communities with InterLink
+  description: Learn how to use BGP communities to set local preference for incoming traffic via Scaleway InterLink.
 content:
-  h1: Using BGP community tags with InterLink
-  paragraph: Learn how to use BGP community tags to set local preference for incoming traffic via Scaleway InterLink.
+  h1: Using BGP communities with InterLink
+  paragraph: Learn how to use BGP communities to set local preference for incoming traffic via Scaleway InterLink.
 tags: interlink configuration border-gateway-protocol bgp-tags local-preference local-pref
 categories: 
   - interlink
@@ -14,18 +14,18 @@ dates:
   posted: 2025-03-26
 ---
 
-You can use **B**order **G**ateway **P**rotocol (BGP) communities on outgoing routes (advertized by Scaleway VPC) and incoming routes (advertized by your external router). TODO CHECK? 
+A **B**order **G**ateway **P**rotocol (BGP) community is a group of IP prefixes that share a common attribute.
 
-A BGP community is a group of IP prefixes that share a common attribute.
+Scaleway recognizes three BGP communities, and applies routing priorities based on the community applied. This lets you influence routing between the various Interlinks in a VPC, for traffic flowing from Scaleway to your external network.
 
-Scaleway makes available three tags for the **Local Preference** attribute. This attribute lets you influence load balancing and route preference for traffic. For each prefix that you advertize over a BGP session, you can apply one of the following local preference community tags to indicate the priority of the associated path for returning traffic:
+For each prefix that you advertise from your external/on-premises router over a BGP session, you can apply one of the following community tags to indicate the priority of the associated path for returning traffic:
 
 - `12876:42050` — Low preference
 - `12876:42100` — Medium preference
 - `12876:42200` — High preference
 
-Local preference BGP community tags are evaluated in order from lowest to highest preference, where the highest preference is preferred.
+These BGP communities are evaluated in order from lowest to highest preference, where the highest preference is preferred. They are mutually exclusive, meaning you can only apply one of them per prefix.
 
-These tags are mutually exclusive, meaning you can only apply one of them per prefix.
+To apply these communities, you must configure your BGP router or software to add the appropriate community to the routes you advertise.
 
-To apply these community tags, you must configure your BGP router or software to add the appropriate community to the routes you advertise.
+You cannot add communities to prefixes advertised by your Scaleway VPC towards your external/on-premises router.
diff --git a/pages/interlink/reference-content/configuring.mdx b/pages/interlink/reference-content/configuring.mdx
@@ -50,7 +50,9 @@ InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wi
 
 Follow the instructions and tips for [creating a routing policy](/interlink/how-to/create-routing-policy/), via the console. Alternatively, you can [create](https://www.scaleway.com/en/developers/api/interlink/#path-routing-policies-create-a-routing-policy) and [attach](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-routing-policy) routing policies via the API.
 
-### 4. Activate route propagation.
+See our dedicated documentation on using [BGP communities](/interlink/reference-content/bgp-communities/) to influence route priority for InterLink traffic.
+
+### 4. Activate route propagation
 
 Once you have attached a VPC and defined the routing policy, you must activate route propagation to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your routing policy to be announced in the BGP session, so that traffic can flow along these routes.  See the documentation for activating route propagation via the [API](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) or the [console](/interlink/how-to/configure-interlink/#how-to-activate-route-propagation)
 
diff --git a/pages/interlink/reference-content/provisioning.mdx b/pages/interlink/reference-content/provisioning.mdx
@@ -59,7 +59,7 @@ Your InterLink will remain in `Requested` status until the partner responds to y
 
 ### 3. Partner accepts InterLink request
 
-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 establish the physical connection. 
+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. See the [statuses documentation](/interlink/reference-content/statuses/) for help with resolving any error statuses.
 
@@ -71,7 +71,7 @@ You must still configure your InterLink by attaching it to a VPC, attaching a ro
 
 ## Deprovisioning overview
 
-When you no longer want your InterLink connection, you can delete it. The process is as follows:
+When you no longer want your InterLink, you can delete it. The process is as follows:
 
 1. Deactivate route propagation.
 2. [Delete your InterLink on the Scaleway side](/interlink/how-to/delete-interlink/). InterLink status moves to `Deprovisioning`.
diff --git a/pages/interlink/reference-content/statuses.mdx b/pages/interlink/reference-content/statuses.mdx
@@ -27,7 +27,7 @@ This document explains the different statuses possible for an InterLink, and how
 | **Configuring**       | InterLink is configuring and is in a transient state. No user actions can be carried out. <br/><br/> This status could occur immediately after creating your InterLink order, while Scaleway processes the order and configures the InterLink, or at any time when a new configuration is being applied. |
 | **Requesting**        | InterLink has been created successfully on the Scaleway side, provisioning must now be requested from the chosen partner. <br/><br/> You must contact your partner to request that they provision your InterLink. Either a contact email address, or a link to the partner’s portal is provided via the Scaleway API. Scaleway does not make the request to the partner, this is the responsibility of the user.<br/><br/> The InterLink will remain in `Requesting` status until the partner accepts the request, at which point it moves into `Provisioning` status. Alternatively, the partner may refuse the request, or the request may time out. |
 | **Failed**          | Scaleway was unable to create the InterLink. <br/><br/> This usually occurs when there is a configuration error on the Scaleway side while attempting to create the InterLink. Our technical team is automatically made aware of such a problem, and will intervene to resolve it. When the problem is resolved, the InterLink should move to `Requesting` status. Wait for technical intervention, or open a support ticket if you require further help.
-| **Provisioning**      | The partner has accepted the InterLink request, and is now provisioning the connection at their end. <br/><br/> The InterLink is not yet operational: traffic cannot yet flow. You must wait for the partner to finish provisioning the connection. When provisioning is complete, the InterLink should move to `Active` status. |
+| **Provisioning**      | The partner has accepted the InterLink request, and is now provisioning it at their end. <br/><br/> The InterLink is not yet operational: traffic cannot yet flow. You must wait for the partner to finish provisioning. When provisioning is complete, the InterLink should move to `Active` status. |
 | **Expired**           | No response was received from the selected partner in the 10 days following the creation of the InterLink on the Scaleway side. <br/><br/> If Scaleway does not receive a response from the selected partner after 10 days, the InterLink moves to `Expired` status. It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again. |
 | **Refused**           | The partner refused the request to provision the InterLink. <br/><br/> It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again with a different partner or configuration.  |
 | **Active**            | The InterLink is in a ready state, and traffic can flow. <br/><br/> The InterLink has been provisioned on both the Scaleway side and the partner side, and is now in an active state. Traffic can flow across the InterLink (presuming that routing policies, route propagation, and an attached VPC are correctly configured). |

Original file line number	Diff line number	Diff line change
`@@ -3298,6 +3298,10 @@`
`3298`	`3298`	`{`
`3299`	`3299`	`"label": "InterLink statuses",`
`3300`	`3300`	`"slug": "statuses"`
	`3301`	`+ },`
	`3302`	`+ {`
	`3303`	`+ "label": "Using BGP communities",`
	`3304`	`+ "slug": "bgp-communities"`
`3301`	`3305`	`}`
`3302`	`3306`	`],`
`3303`	`3307`	`"label": "Additional Content",`