Skip to content

Commit f3906b4

Browse files
RoRoJnerda-codes
andcommitted
Apply suggestions from code review
Co-authored-by: nerda-codes <[email protected]>
1 parent e3faa67 commit f3906b4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

network/interlink/reference-content/overview.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Provisioning an InterLink is a multi-step process. As only hosted InterLinks (vi
5353

5454
## Attaching a VPC
5555

56-
When you initially create the InterLink, it is not associated with a specific VPC, only with given a Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. You can only attach a VPC once the provisioning process is complete, and the InterLink has `Active` status. See the [configuration](/network/interlink/reference-content/configuring/) page for more information.
56+
When you initially create the InterLink, it is not associated with a specific VPC, only with a given Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. You can only attach a VPC once the provisioning process is complete, and the InterLink has `Active` status. See the [configuration](/network/interlink/reference-content/configuring/) page for more information.
5757

5858
While each InterLink can only be attached to a single Scaleway VPC, it is possible to attach two InterLinks to the same VPC to ensure redundancy and high availability. In this case, each InterLink must be provisioned and configured separately, and will be billed separately. Note that you can reuse the same [allowed routes lists](#allowed-routes-list) across multiple InterLinks.
5959

0 commit comments

Comments
 (0)