Apply suggestions from code review

Co-authored-by: Néda <[email protected]>

Author: RoRoJ

pages/interlink/how-to/create-routing-policy.mdx

@@ -45,9 +45,9 @@ Learn more about routing across an InterLink in our [detailed overview](/interli
 
 7. Whitelist the incoming routes to allow, in the same way you did for outgoing routes. Outgoing routes concern announcements to accept from the external infrastructure. Traffic can be routed via InterLink from your Scaleway VPC to your external infrastructure along these routes.
 
-4. Enter a name for the policy, or leave the randomly-generated name in place. Optionally, you can also add tags.
+8. Enter a name for the policy, or leave the randomly-generated name in place. Optionally, you can also add tags.
 
-8. Click **Create routing policy**.
+9. Click **Create routing policy**.
 
 The policy is created, and you are returned to the listing of your routing policies.
 
@@ -71,6 +71,6 @@ See our dedicated documentation on using [BGP communities](/interlink/reference-
 
         A warning displays, to remind you that modifications will immediately be propagated on InterLinks using this policy.
 
-5. Click **Save**.
+6. Click **Save**.
 
 The policy is modified and modifications are immediately applied.

pages/interlink/how-to/order-interlink.mdx

@@ -43,9 +43,9 @@ 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).
+4. 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: 
+5. Select the following options, depending on your physical connection type: 
 
    <Tabs id="interlink-create">
 
@@ -61,13 +61,13 @@ This guide takes you through the process of creating an InterLink via the Scalew
         </TabsTab>
     </Tabs>
 
-5. Choose a [bandwidth](/interlink/concepts/#bandwidth) amount. This represents the maximum bandwidth that will be available over the InterLink.
+6. 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](/interlink/concepts/#routing-policy). 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. Attach up to two [routing policies](/interlink/concepts/#routing-policy). 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.
+8. Enter a name and optional tags for your InterLink.
 
-8. Click **Create InterLink**.
+9. Click **Create InterLink**.
 
 - **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={scalewayHostedInterlinkOrdering} 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." /> 

pages/interlink/reference-content/statuses.mdx

@@ -23,7 +23,7 @@ This document explains the different statuses possible for an InterLink, and how
 | **Provisioning**      | The partner has accepted the hosted 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 hosted 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 hosted 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.  |
-| **Ready**           | The self-hosted InterLink has been created and is ready to connect.. <br/><br/> The tunnel(s) cannot be established because the customer network device is not yet successfully configured.  |
+| **Ready**           | The self-hosted InterLink has been created and is ready to connect. <br/><br/> The tunnel(s) cannot be established because the customer network device is not yet successfully configured.  |
 | **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 (for hosted InterLinks) 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). |
 | **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 and configured 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. |