Apply suggestions from code review

Co-authored-by: nerda-codes <[email protected]>

Author: RoRoJ

network/interlink/concepts.mdx

@@ -50,7 +50,7 @@ A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location wh
 
 ## 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 ley ensures that the correct endpoints are securely connected.
+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.
 
 ## Partner
 

network/interlink/reference-content/configuring.mdx

@@ -41,7 +41,7 @@ You must wait until the InterLink has reached `Active` [status](/network/interli
 
 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.
 
-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.
+The VPC must be in the same 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

@@ -49,7 +49,7 @@ A dedicated InterLink is provisioned, where the customer gets sole use of a sing
 
 ## Provisioning an InterLink
 
-Provisioning an InterLink is a multi-step process. As only hosted InterLinks (via partners) are currently available, specific action is required from both from Scaleway, the customer, and from the selected partner in order to successfully complete the provisioning process. See our dedicated page on [provisioning an InterLink](/network/interlink/reference-content/provisioning/) for full details.
+Provisioning an InterLink is a multi-step process. As only hosted InterLinks (via partners) are currently available, specific action is required from Scaleway, the customer, and the selected partner in order to successfully complete the provisioning process. See our dedicated page on [provisioning an InterLink](/network/interlink/reference-content/provisioning/) for full details.
 
 ## Attaching a VPC
 

network/interlink/reference-content/statuses.mdx

@@ -26,13 +26,13 @@ This document explains the different statuses possible for an InterLink, and how
 | **Status**            | **Description**                     | 
 |-------------------|-----------------------------------------|
 | **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 the request may time out. |
+| **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. |
 | **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 allowed routes lists, route propagation, and an attached VPC are correctly configured). |
-| **Limited Connectivity** | The InterLink is provisioned, but IP connectivity is limited. <br/><br/> This may be the case if either, but not both of, the BGP IPv4 or IPv6 sessions are down. |
+| **Limited Connectivity** | The InterLink is provisioned, but IP connectivity is limited. <br/><br/> This may be the case if either, but not both of, the BGP, IPv4, or IPv6 sessions are down. |
 | **Down / All down**  | The InterLink is provisioned, but there is no IP connectivity. <br/><br/> The InterLink has been provisioned successfully on both sides, but both BGP sessions (IPv4 and IPv6) are down and traffic cannot flow. Open a support ticket with Scaleway, or contact your partner. |
 | **Locked** | The InterLink has been locked by the Trust and Safety team <br/><br/> You cannot carry out any actions on the InterLink. Open a support ticket. |
 | **Deprovisioning** | Deletion of the InterLink has been initiated on either the partner side or the Scaleway side, but has not been finalized. <br/><br/> An InterLink must be deleted by both Scaleway and the partner in order to move to `Deleted` status. If you have deleted an InterLink on the Scaleway side, ensure you contact the partner separately to request that they delete the resource on their side. If you have deleted an InterLink on the partner side, ensure that you delete the resource on the Scaleway side. |