scaleway · bene2k1 · Apr 23, 2025 · Apr 23, 2025
diff --git a/pages/guidelines.mdx b/pages/guidelines.mdx
@@ -203,7 +203,7 @@ When linking to other Scaleway Documentation pages, use relative links. Include
 
 | ✅ GOOD INTERNAL LINK                                | ❌ BAD INTERNAL LINK                                 |
 | ------------------------------------------ | ----------------------------------------------- |
-|  ````Refer to the [VPC Quickstart](/vpc/quickstart/)````  | ````Refer to the [VPC Quickstart](/vpc/quickstart/)```` <br/> <br/> ````Refer to the [VPC Quickstart](/en/docs/network/vpc/quickstart/)```` <br/> <br/> ````Refer to the [VPC Quickstart](network/vpc/quickstart)```` |
+|  ````Refer to the [VPC Quickstart](/vpc/quickstart/)````  | ````Refer to the [VPC Quickstart](/vpc/quickstart/)```` <br/> <br/> ````Refer to the [VPC Quickstart](/en/docs/vpc/quickstart/)```` <br/> <br/> ````Refer to the [VPC Quickstart](network/vpc/quickstart)```` |
 
 When linking to a Scaleway Documentation page anchor, include a leading slash, **but no trailing slash**
 

@@ -21,7 +21,7 @@ They can be of two types:
 
 - **Owner** - you are the Owner of the Organization that was created with your account.
 - **Guest** - you are a Guest when invited to an Organization of which you are not the Owner. Similarly, you can invite other users to be Guests in your Organization.
-- **Member** - you are a member when you are added to an Organization by an Owner or user with IAM Manager permissions. Members exist only within the specific Organizations in which they are added. As a member you are subject to [complying with the security requirements](/iam/how-to/how-to-comply-with-sec-requirements-member) in effect in your Organization.
+- **Member** - you are a member when you are added to an Organization by an Owner or user with IAM Manager permissions. Members exist only within the specific Organizations in which they are added. As a member you are subject to [complying with the security requirements](/iam/how-to/comply-with-sec-requirements-member/) in effect in your Organization.
 
 Within each Organization, different IAM users can have different rights (defined through policies) to perform actions on resources.
 

@@ -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 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/#hosted-interlinks).
 
 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.
 

@@ -21,7 +21,7 @@ Scaleway provides a selection of common models for deployment from the Scaleway
 
 <Macro id="requirements" />
 - A Scaleway account logged into the [console](https://console.scaleway.com).  
-- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) to perform actions in your Organization.
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) to perform actions in your Organization.
 
 1. Click **Managed Inference** in the **AI & Data** section of the side menu in the [Scaleway console](https://console.scaleway.com/) to access the dashboard.
 2. Click **Deploy a model** to launch the model deployment wizard.

@@ -38,7 +38,7 @@ After a deprecation period ending on 1 Oct 2025, the Public Gateways API v1 and
 
 - Ensure that your Public Gateway is in [IPAM mode](#ipam-mode-becomes-default). Only IPAM-mode gateways are compatible with v2.
 
-- Put any non-IPAM mode ([legacy](/network/public-gateways/concepts/#ipam)) Public Gateways in IPAM mode. You can do this in several ways:
+- Put any non-IPAM mode ([legacy](/public-gateways/concepts/#ipam)) Public Gateways in IPAM mode. You can do this in several ways:
     - Use the **Move to IPAM mode** button in the console 
     - Use the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode).
     - Use the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md)
@@ -53,13 +53,13 @@ If your Public Gateway is already in IPAM mode, and you only manage it via the c
 
 ## Background: DHCP and IPAM
 
-When Scaleway originally introduced Public Gateways, they provided DHCP functionality for resources on attached Private Networks. With the [arrival of Scaleway VPC](/network/vpc/reference-content/vpc-migration/) in 2023, DHCP was moved from Public Gateways to Private Networks themselves.
+When Scaleway originally introduced Public Gateways, they provided DHCP functionality for resources on attached Private Networks. With the [arrival of Scaleway VPC](/vpc/reference-content/vpc-migration/) in 2023, DHCP was moved from Public Gateways to Private Networks themselves.
 
-Scaleway also introduced [IPAM](/network/ipam/concepts/#ipam) to act as a single source of truth for the IP addressing of all Scaleway resources. DHCP uses IPAM to ensure consistent and reliable addressing across all Private Networks. 
+Scaleway also introduced [IPAM](/ipam/concepts/#ipam) to act as a single source of truth for the IP addressing of all Scaleway resources. DHCP uses IPAM to ensure consistent and reliable addressing across all Private Networks. 
 
-When you [create a Private Network](/network/vpc/how-to/create-private-network/), you can either automatically generate a default IPv4 CIDR block, or define a custom block. A default IPv6 block is automatically created. When you attach resources to the Private Network, they automatically receive an IPv4 address (and, if compatible, an IPv6 address) from this block. Alternatively, you can [reserve a specific IP address](/network/ipam/how-to/reserve-ip/) from the block, and [specify this address](/network/ipam/how-to/reserve-ip/#how-to-attach-a-resource-to-a-private-network-using-a-reserved-ip-address) when attaching the resource.
+When you [create a Private Network](/vpc/how-to/create-private-network/), you can either automatically generate a default IPv4 CIDR block, or define a custom block. A default IPv6 block is automatically created. When you attach resources to the Private Network, they automatically receive an IPv4 address (and, if compatible, an IPv6 address) from this block. Alternatively, you can [reserve a specific IP address](/ipam/how-to/reserve-ip/) from the block, and [specify this address](/ipam/how-to/reserve-ip/#how-to-attach-a-resource-to-a-private-network-using-a-reserved-ip-address) when attaching the resource.
 
-Whether you choose a custom or default CIDR block, automatic address assignment or use a reserved address, **the resource's private IP address does not risk changing** unless you detach the resource from the Private Network. To ensure that you can keep the same address for a resource even after detaching it, use the [reserve IP](/network/ipam/how-to/reserve-ip/) functionality.
+Whether you choose a custom or default CIDR block, automatic address assignment or use a reserved address, **the resource's private IP address does not risk changing** unless you detach the resource from the Private Network. To ensure that you can keep the same address for a resource even after detaching it, use the [reserve IP](/ipam/how-to/reserve-ip/) functionality.
 
 ## Introducing Public Gateways API v2
 
@@ -86,7 +86,7 @@ Scaleway Public Gateways are either in **Legacy mode** or **IPAM mode**. You can
 All Public Gateways created via the Scaleway console since 17 October 2023 are necessarily in IPAM mode.
 </Message>
 
-Legacy Public Gateways use a [workaround](/network/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure IPAM compatibility. IPAM-mode Public Gateways are fully integrated with Scaleway's [IPAM](/network/ipam/concepts/#ipam), which manages the coherent assignment of IP addresses to the gateway itself, and resources on attached Private Networks.
+Legacy Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure IPAM compatibility. IPAM-mode Public Gateways are fully integrated with Scaleway's [IPAM](/ipam/concepts/#ipam), which manages the coherent assignment of IP addresses to the gateway itself, and resources on attached Private Networks.
 
 Legacy mode will be deprecated going forward, and will not be compatible with v2 of the Public Gateway API. It will no longer be possible to create legacy-mode Public Gateways, all new gateways will necessarily be in IPAM mode.
 
@@ -124,7 +124,7 @@ We will automatically migrate any existing DHCP entries to IPAM for you, at the
 
 ### SSH bastion allowed IPs
 
-Allowed IPs is a new functionality of the Public Gateways API v2, that will also be available to all IPAM-mode Public Gateways via the Scaleway console. This feature allows you to specify a list of IP address ranges which should be allowed to connect to the gateway's SSH bastion and the resources behind it. All other IP addresses will be blocked from connecting. Find out more in the [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) documentation.
+Allowed IPs is a new functionality of the Public Gateways API v2, that will also be available to all IPAM-mode Public Gateways via the Scaleway console. This feature allows you to specify a list of IP address ranges which should be allowed to connect to the gateway's SSH bastion and the resources behind it. All other IP addresses will be blocked from connecting. Find out more in the [SSH bastion](/public-gateways/how-to/use-ssh-bastion/) documentation.
 
 ## Timeline and action to take
 
@@ -137,8 +137,8 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also
 
 - **8 April 2025 - 1 Oct 2025: Migration period**: You have a six month migration period to complete the following actions
 
-    - Ensure that your Public Gateway is in [IPAM mode](/network/public-gateways/concepts/#ipam). Only IPAM mode gateways are compatible with v2.
-    - Put any non-IPAM mode ([legacy](/network/public-gateways/concepts/#ipam)) Public Gateways in IPAM-mode, by using the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md).
+    - Ensure that your Public Gateway is in [IPAM mode](/public-gateways/concepts/#ipam). Only IPAM mode gateways are compatible with v2.
+    - Put any non-IPAM mode ([legacy](/public-gateways/concepts/#ipam)) Public Gateways in IPAM-mode, by using the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md).
     - Ensure that [DHCP is activated](/vpc/how-to/activate-dhcp/) on all Private Networks attached to your IPAM-mode Public Gateways.
     - Update any code or scripts you have that call version 1 of the Public Gateways API, so that they call version 2 instead. This includes removing any use of the DHCP entries, DHCP objects or address fields as mentioned above.
 
@@ -216,7 +216,7 @@ If you have any questions, get in touch with us on the `#public-gateway` channel
 The following documentation resources may be useful to you:
 
 - [Public Gateway API Documentation](https://www.scaleway.com/en/developers/api/public-gateway/)
-- [Public Gateway Main Documentation](https://www.scaleway.com/en/docs/network/public-gateways/)
+- [Public Gateway Main Documentation](https://www.scaleway.com/en/docs/public-gateways/)
 - [IPAM API Documentation](https://www.scaleway.com/en/developers/api/ipam/)
-- [IPAM Main Documentation](https://www.scaleway.com/en/docs/network/ipam/)
+- [IPAM Main Documentation](https://www.scaleway.com/en/docs/ipam/)
 - [Moving a Public Gateway from Legacy mode to IPAM mode with Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md)
@@ -150,7 +150,7 @@ The container can then process the message and perform any required actions, suc
 
 The port of a containerized application refers to the network port that the application inside the container listens on for incoming requests.
 
-Refer to the [dedicated documentation](/serverless-containers/reference-content/port-variable/) for more information and examples on the **Port** parameter of Serverless Containers. 
+Refer to the [dedicated documentation](/serverless-containers/reference-content/port-parameter-variable/) for more information and examples on the **Port** parameter of Serverless Containers. 
 
 ## Privacy policy