docs(fix): fixed broken links (scaleway#2360)

bene2k1 · web-flow · commit 2a1caabcfb18 · 2023-11-06T15:19:18.000+01:00
* docs(fix): fixed broken links

* docs(fix): fixed 404

* docs(fix): 404

* docs(fix): 404
diff --git a/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx b/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx
@@ -25,7 +25,7 @@ Learn how to configure a [flexible IP address](/bare-metal/elastic-metal/concept
 </Message>
 
 <Message typ="tip">
-  You can find information about the DNS resolver to use in each datacenter at the [network reference documentation](/dedibox-network/network/reference-content/dedibox-network-info/#dns-cache-servers).
+  You can find information about the DNS resolver to use in each datacenter at the [network reference documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers).
 </Message>
 
 ## How to configure a flexible IP on Ubuntu Linux
diff --git a/bare-metal/elastic-metal/how-to/configure-flexible-ipv6.mdx b/bare-metal/elastic-metal/how-to/configure-flexible-ipv6.mdx
@@ -22,7 +22,7 @@ The configuration of a flexible IPv6 depends on the Linux distribution running o
 </Message>
 
 <Message typ="tip">
-  You can find information about the DNS resolver to use in each datacenter at the [network reference documentation](/dedibox-network/network/reference-content/dedibox-network-info/#dns-cache-servers).
+  You can find information about the DNS resolver to use in each datacenter at the [network reference documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers).
 </Message>
 
 
diff --git a/bare-metal/elastic-metal/how-to/configure-ipv6-hypervisor.mdx b/bare-metal/elastic-metal/how-to/configure-ipv6-hypervisor.mdx
@@ -29,7 +29,7 @@ Below are some examples for the configuration of the network interfaces on diffe
 
 <Message type="tip">
   * The IPv6 gateway for your machines is learned by RA. You do not need to specify it in your configuration.
-  * The DNS cache server (nameserver) may be different depending on the physical location of your server. Refer to our [network information documentation](/dedibox-network/network/reference-content/dedibox-network-info/#dns-cache-servers) to find the IPv6 addresses to use with your machine.
+  * The DNS cache server (nameserver) may be different depending on the physical location of your server. Refer to our [network information documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) to find the IPv6 addresses to use with your machine.
 </Message>
 
 
diff --git a/changelog/instances/september2022/2022-09-06-instances-added-play2.mdx b/changelog/instances/september2022/2022-09-06-instances-added-play2.mdx
@@ -10,7 +10,7 @@ product: instances
 ---
 
 A new generation of Development Instances is now available: PLAY2.
-Scaleway’s PLAY2 Instances are designed for testing and development purposes. PLAY2 Instances are the second generation of [Development Instances](/compute/instances/concepts/#development-instance) after DEV1. They are small, agile and meet performance requirements for standard testing and development scenarios. [Learn more about PLAY2 Instances](https://www.scaleway.com/en/virtual-instances/play2) on their dedicated product page.
+Scaleway’s PLAY2 Instances are designed for testing and development purposes. PLAY2 Instances are the second generation of [Development Instances](/compute/instances/concepts/#development-instance) after DEV1. They are small, agile and meet performance requirements for standard testing and development scenarios. [Learn more about PLAY2 Instances](https://www.scaleway.com/en/cost-optimized-instances/) on their dedicated product page.
 PLAY2 Instances are currently available in:
 - fr-par-2
 - nl-ams-2
diff --git a/changelog/january2023/2023-01-18-instances-changed-ent1-range-is-extended.mdx b/changelog/january2023/2023-01-18-instances-changed-ent1-range-is-extended.mdx
@@ -9,7 +9,7 @@ category: compute
 product: instances
 ---
 
-New offers are available for Scaleway [Enterprise Instances](https://www.scaleway.com/en/virtual-instances/enterprise/). 
+New offers are available for Scaleway [Enterprise Instances](https://www.scaleway.com/en/production-optimized-instances/). 
 
 Joining the ENT1 range, **ENT1-XXS** and **ENT1-XS** are now available in all AZ. 
 
diff --git a/changelog/serverless/september2022/2022-09-07-mnq-added-sns-sqs.mdx b/changelog/serverless/september2022/2022-09-07-mnq-added-sns-sqs.mdx
@@ -9,4 +9,4 @@ category: serverless
 product: messaging-and-queuing
 ---
 
-SNS and SQS are now available for Messaging in [private beta](https://www.scaleway.com/en/betas/). You can create an SNS/SQS namespace, generate credentials and use them to connect to the system. Find out more on the SNS/SQS [documentation overview](/serverless/messaging/reference-content/snssqs-overview).
+SNS and SQS are now available for Messaging in [private beta](https://www.scaleway.com/en/betas/). You can create an SNS/SQS namespace, generate credentials and use them to connect to the system. Find out more on the SNS/SQS [documentation overview](/serverless/messaging/reference-content/).
diff --git a/compute/instances/concepts.mdx b/compute/instances/concepts.mdx
@@ -66,7 +66,7 @@ Cloud-init is a multi-distribution package that [provides boot time customizatio
 
 ## Development Instance
 
-[Development Instances](https://www.scaleway.com/en/virtual-instances/development/) are reliable and flexible Instances tuned to host your websites, applications, and development environments.
+[Development Instances](https://www.scaleway.com/en/cost-optimized-instances/) are reliable and flexible Instances tuned to host your websites, applications, and development environments.
 
 </Concept>
 
diff --git a/developer-tools/scaleway-cli/quickstart.mdx b/developer-tools/scaleway-cli/quickstart.mdx
@@ -83,7 +83,7 @@ Refer to the [Scaleway CLI repository](https://github.com/scaleway/scaleway-cli)
     Enter a valid secret-key or an email
     ```
 
-    Enter either the email address for your account (you will then be asked for your password), or your [API secret Key](/console/my-project/how-to/create-ssh-key) when prompted by the following message:
+    Enter either the email address for your account (you will then be asked for your password), or your [API secret Key](/console/project/how-to/create-ssh-key) when prompted by the following message:
 
 3. The following message displays:
 
diff --git a/developer-tools/terraform/reference-content/index.mdx b/developer-tools/terraform/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+  title: Terraform for Scaleway - Reference Content
+  description: Discover the Terraform provider for Scaleway
+content:
+  h1: Terraform for Scaleway - Reference Content
+  paragraph: Terraform for Scaleway
+---
diff --git a/faq/account.mdx b/faq/account.mdx
@@ -62,7 +62,7 @@ Your email address is now updated.
 
 ## How can I get more quotas?
 
-You can get more quotas by adding and verifying your [payment method](/console/my-account/how-to/manage-billing-information/) and [identity](/console/my-account/how-to/verify-identity/).
+You can get more quotas by adding and verifying your [payment method](/console/account/how-to/manage-billing-information/) and [identity](/console/account/how-to/verify-identity/).
 
 If you have already completed these two steps and still need an increase in quotas, contact our [support team](https://console.scaleway.com/support/tickets/create) and inform them which product you need more quotas for.
 
diff --git a/faq/messaging-and-queuing.mdx b/faq/messaging-and-queuing.mdx
@@ -30,7 +30,7 @@ We currently implement the API endpoints listed [here](/serverless/messaging/ref
 The following subscriber types are supported:
 - HTTP/S clients
 - Serverless Functions
-- SQS queues in the same [Project](/console/my-project/concepts/#project)
+- SQS queues in the same [Project](/console/project/concepts/#project)
 
 For more details on supported and unsupported SNS features, see our [dedicated page](/serverless/messaging/reference-content/sns-support/)
 
@@ -54,7 +54,7 @@ Messaging and Queuing namespaces have been removed.
 
 **SQS/SNS** namespaces and their credentials are not automatically migrated, and you must **migrate your resources yourself**. 
 - Previously these protocols were combined, and shared namespaces/credentials, but now they have been separated.
-- You must [activate](/serverless/messaging/how-to/get-started/#how-to-activate-sqs-or-sns) the SQS and/or SNS protocols on your [Scaleway Project](/console/my-project/concepts/#project)
+- You must [activate](/serverless/messaging/how-to/get-started/#how-to-activate-sqs-or-sns) the SQS and/or SNS protocols on your [Scaleway Project](/console/project/concepts/#project)
 - You must [recreate](/serverless/messaging/how-to/create-credentials/) your credentials (and any other resources e.g. queues) for the new "no-namespace" version of Messaging and Queuing.
 
 See our [migration documentation](/serverless/messaging/reference-content/migration/) for full instructions and details. The new version of Messaging and Queuing is designed to provide a better and more secure experience, as well as preparing Messaging and Queuing for further integration into the Scaleway ecosystem.
diff --git a/faq/new-object-storage-classes.mdx b/faq/new-object-storage-classes.mdx
@@ -11,7 +11,7 @@ hero: assets/objectstorage.webp
 <Concept>
 
 ## What is the difference between the Standard class in PAR and AMS, and the Standard class in WAW?
-In the Paris (PAR) and Amsterdam (AMS) [regions](storage/object/concepts/#region-and-availability-zone), Scaleway Object Storage secures your data by distributing it across three different [Availability Zones (AZ)](storage/object/concepts/#region-and-availability-zone). In the event of a complete datacenter failure in an AZ, we are still able to rebuild your data and make it accessible. This is the system we call Multi-AZ (one datacenter per AZ, three AZs per region).
+In the Paris (PAR) and Amsterdam (AMS) [regions](/storage/object/concepts/#region-and-availability-zone), Scaleway Object Storage secures your data by distributing it across three different [Availability Zones (AZ)](/storage/object/concepts/#region-and-availability-zone). In the event of a complete datacenter failure in an AZ, we are still able to rebuild your data and make it accessible. This is the system we call Multi-AZ (one datacenter per AZ, three AZs per region).
 
 The standard class in Warsaw (WAW) currently allows you to store data across only one AZ.
 
diff --git a/identity-and-access-management/secret-manager/api-cli/create-secret-folder-migrate.mdx b/identity-and-access-management/secret-manager/api-cli/create-secret-folder-migrate.mdx
@@ -18,7 +18,7 @@ This documentation allows you to create a secret called `ultra-confidential`, a
 <Macro id="iam-requirements" />
 
 <Message type="requirement">
-- You have a [Scaleway account](/console/my-account/how-to/create-an-account/)
+- You have a [Scaleway account](/console/account/how-to/create-an-account/)
 - You have configured the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#installation)
 </Message>
 
diff --git a/labs/ipfs-naming/how-to/import-key.mdx b/labs/ipfs-naming/how-to/import-key.mdx
@@ -38,7 +38,7 @@ categories:
     </Message>
 8. Enter a value for the keys.
     <Message type="note">
-      The value must be an [IPNS key](/labs/ipfs-naming/concepts/#name) or a [CID](/ipfs-naming/concepts/#content-identifier-(cid)).
+      The value must be an [IPNS key](/labs/ipfs-naming/concepts/#name) or a [CID](/labs/ipfs-naming/concepts/#content-identifier-(cid)).
     </Message>
 9. Click **Create a Name**.
 
diff --git a/labs/ipfs-naming/quickstart.mdx b/labs/ipfs-naming/quickstart.mdx
@@ -58,7 +58,7 @@ In this quickstart, we will show you how to create and import an IPNS key and up
     </Message>
 8. Enter a value for the keys.
     <Message type="note">
-      The value must be an [IPNS key](/labs/ipfs-naming/concepts/#name) or a [CID](/ipfs-naming/concepts/#content-identifier-(cid)).
+      The value must be an [IPNS key](/labs/ipfs-naming/concepts/#name) or a [CID](/labs/ipfs-naming/concepts/#content-identifier-(cid)).
     </Message>
 9. Click **Create a Name**.
 
diff --git a/serverless/messaging/reference-content/limitations.mdx b/serverless/messaging/reference-content/limitations.mdx
@@ -40,7 +40,7 @@ This section contains usage limits that apply when using Messaging and Queuing.
 | Message age / retention period (SQS)           | Max        | 14 days  | Message          |
 | Visibility timeout                             | Max        | 12 hours | SQS queue        |
 
-These limits are enforced as [Organization quotas](/console/my-account/reference-content/organization-quotas/).
+These limits are enforced as [Organization quotas](/console/account/reference-content/organization-quotas/).
 
 ## VPC
 
diff --git a/serverless/messaging/reference-content/migration.mdx b/serverless/messaging/reference-content/migration.mdx
@@ -47,7 +47,7 @@ In this previous version of the product, you created **namespaces**, setting the
 In this new version of the product, the concept of namespaces has been removed:
 
 - For **NATS** namespaces have been replaced by **accounts**. You can create one or multiple NATS accounts, and credentials for each account. Each account will have its own URL/endpoint.
-- **SQS** and **SNS** have been separated into two distinct protocols. Instead of creating a namespace, you simply **activate** each protocol. You can then create credentials for each protocol. If you previously used multiple SQS or SNS namespaces to separate resources, you should now use [Scaleway Projects](/console/my-project/concepts/#project) to separate your resources.
+- **SQS** and **SNS** have been separated into two distinct protocols. Instead of creating a namespace, you simply **activate** each protocol. You can then create credentials for each protocol. If you previously used multiple SQS or SNS namespaces to separate resources, you should now use [Scaleway Projects](/console/project/concepts/#project) to separate your resources.
 
 ## From Public Beta to General Availability: impact on billing
 
@@ -103,7 +103,7 @@ To migrate, you must **recreate your resources** (credentials and queues) in the
 
 <Message type="tip">
 
-If you previously had multiple namespaces to separate your SQS resources, we recommend that you use [Scaleway Projects](/console/my-project/concepts/#project) with the new version to handle this. By creating multiple Projects, activating SQS in each one, and then creating SQS credentials in each Project, you will be able to achieve separation of resources, and credentials scoped to the SQS broker of each Project.
+If you previously had multiple namespaces to separate your SQS resources, we recommend that you use [Scaleway Projects](/console/project/concepts/#project) with the new version to handle this. By creating multiple Projects, activating SQS in each one, and then creating SQS credentials in each Project, you will be able to achieve separation of resources, and credentials scoped to the SQS broker of each Project.
 
 </Message>
 
@@ -158,7 +158,7 @@ To migrate, you must **recreate your resources** in the new version. Remember th
 
 <Message type="tip">
 
-If you previously had multiple namespaces to separate your SNS resources, we recommend that you use [Scaleway Projects](/console/my-project/concepts/#project) with the new version to handle this. By creating multiple Projects, activating SNS in each one, and then creating SNS credentials in each Project, you will be able to achieve separation of resources, and credentials scoped to the SNS broker of each Project.
+If you previously had multiple namespaces to separate your SNS resources, we recommend that you use [Scaleway Projects](/console/project/concepts/#project) with the new version to handle this. By creating multiple Projects, activating SNS in each one, and then creating SNS credentials in each Project, you will be able to achieve separation of resources, and credentials scoped to the SNS broker of each Project.
 
 </Message>
 
diff --git a/serverless/messaging/reference-content/sns-overview.mdx b/serverless/messaging/reference-content/sns-overview.mdx
@@ -23,7 +23,7 @@ SNS (Simple Notification Service) was released in 2010. It enables users to inte
   Some SNS features are not yet available with Scaleway Messaging and Queuing. Supported subscribers are currently limited to:
     - HTTP/S clients
     - [Serverless Functions](https://www.scaleway.com/en/serverless-functions/)
-    - SQS queues in the same [Project](/console/my-project/concepts/#project)
+    - SQS queues in the same [Project](/console/project/concepts/#project)
 
   Refer to the [developers documentation](https://www.scaleway.com/en/developers/api/messaging-and-queuing/) for more information.
 </Message>
@@ -36,7 +36,7 @@ Before you can start using SNS with Scaleway Messaging and Queuing, you must fir
 
 Once you have activated SNS, the next step is to [create credentials](/serverless/messaging/how-to/create-credentials) that give your applications permission to connect to the Scaleway Messaging and Queuing service.
 
-Credentials are scoped to your SQS service at [Project](/console/my-project/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions:
+Credentials are scoped to your SQS service at [Project](/console/project/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions:
 
   - **Read**: receive messages from queues and topics.
   - **Write**: send messages to queues and publish in topics.
diff --git a/serverless/messaging/reference-content/sqs-overview.mdx b/serverless/messaging/reference-content/sqs-overview.mdx
@@ -31,7 +31,7 @@ Before you can start using SQS with Scaleway Messaging and Queuing, you must fir
 
 Once you have activated SQS, the next step is to [create credentials](/serverless/messaging/how-to/create-credentials) that give your applications permission to connect to the Scaleway Messaging and Queuing service.
 
-Credentials are scoped to your SQS service at [Project](/console/my-project/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions:
+Credentials are scoped to your SQS service at [Project](/console/project/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions:
 
   - **Read**: receive messages from queues and topics.
   - **Write**: send messages to queues and publish in topics.
diff --git a/tutorials/ark-server/index.mdx b/tutorials/ark-server/index.mdx
@@ -54,7 +54,7 @@ In this tutorial, you will learn how to create an ARK server on a [Scaleway Inst
   We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/).
 </Message>
 
-Creating an ARK server can be done in a few steps on a [Scaleway Instance](https://www.scaleway.com/en/virtual-instances/development/). If you do not have an Instance yet, start by [deploying your first Instance](/compute/instances/how-to/create-an-instance/).
+Creating an ARK server can be done in a few steps on a [Scaleway Instance](https://www.scaleway.com/en/cost-optimized-instances/). If you do not have an Instance yet, start by [deploying your first Instance](/compute/instances/how-to/create-an-instance/).
 
 <Message type="note">
   The "Ark: Survival Evolved" game server application requires at least 6 GB of RAM to start. Memory requirements increase as the number of connected players increases, as well depending on the activated mods. We recommend that you use at minimum a **DEV1-L** Instance for smooth gameplay.
diff --git a/tutorials/install-cockroachdb-scaleway-instances/index.mdx b/tutorials/install-cockroachdb-scaleway-instances/index.mdx
@@ -31,7 +31,7 @@ This article shows you how to install CockroachDB using three nodes on a regiona
 ### Requirements
 
     - You must have [CockroachDB installed](https://www.cockroachlabs.com/docs/v23.1/install-cockroachdb) locally. This is necessary for generating and managing your deployment's certificates.
-    - You must have [created an SSH key](/console/my-project/how-to/create-ssh-key/) to access the machine via SSH. This is necessary for distributing and starting CockroachDB binaries.
+    - You must have [created an SSH key](/console/project/how-to/create-ssh-key/) to access the machine via SSH. This is necessary for distributing and starting CockroachDB binaries.
     - Your network configuration must allow TCP communication on the following ports:
       - `26257` for intra-cluster and client-cluster communication
       - `8080` to expose your DB Console
diff --git a/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx b/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx
@@ -18,7 +18,7 @@ dates:
 pgLoader is an open-source database migration tool developed to simplify the process of migrating an existing database from one database engine to [PostgreSQL](https://www.postgresql.org/).  
 The tool supports migrations from several file types and database engines like [MySQL](https://www.mysql.com/), [MS SQL](https://www.microsoft.com/en-us/sql-server/sql-server-2019) and [SQLite](https://www.sqlite.org/index.html).
 
-In this tutorial you learn how to migrate an existing remote MySQL database to a [Database for PostgreSQL](https://www.scaleway.com/en/database/) using pgLoader and an intermediate [Development Instance](https://www.scaleway.com/en/virtual-instances/development/) running Ubuntu Linux.
+In this tutorial you learn how to migrate an existing remote MySQL database to a [Database for PostgreSQL](https://www.scaleway.com/en/database/) using pgLoader and an intermediate [Development Instance](https://www.scaleway.com/en/cost-optimized-instances/) running Ubuntu Linux.
 
 <Macro id="iam-requirements" />
  
diff --git a/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx b/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx
@@ -16,7 +16,7 @@ dates:
 ---
 
 
-In this tutorial, you will learn how the Private Network feature can help you to build a distributed [Rocket.Chat](/tutorials/run-messaging-platform-with-rocketchat/) application on [General Purpose](https://www.scaleway.com/en/virtual-instances/general-purpose/) and [Development](https://www.scaleway.com/en/virtual-instances/development/) Instances using a Private Network to communicate securely between them:
+In this tutorial, you will learn how the Private Network feature can help you to build a distributed [Rocket.Chat](/tutorials/run-messaging-platform-with-rocketchat/) application on [General Purpose](https://www.scaleway.com/en/cost-optimized-instances/) and [Development](https://www.scaleway.com/en/cost-optimized-instances/) Instances using a Private Network to communicate securely between them:
 
 <Lightbox src="scaleway-private_network_schema.webp" alt="" />
 
diff --git a/tutorials/overleaf/index.mdx b/tutorials/overleaf/index.mdx
diff --git a/tutorials/setup-minecraft/index.mdx b/tutorials/setup-minecraft/index.mdx
