fix(rbd): add regionalization changes to docs

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx

@@ -20,10 +20,11 @@ categories:
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the Database Instance name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-3. Go to the **Databases** tab. A list of your databases displays. The list includes the database created by default upon Database Instance creation.
-4. Click **+ Create database** to create a new one. A pop-up appears.
-5. Enter a name for your database.
-6. Click **Create database** to confirm.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the Database Instance name or <Icon name="more" /> > **More info** to access the Database Instance information page.
+4. Go to the **Databases** tab. A list of your databases displays. The list includes the database created by default upon Database Instance creation.
+5. Click **+ Create database** to create a new one. A pop-up appears.
+6. Enter a name for your database.
+7. Click **Create database** to confirm.
 
 The new database appears in the list of your databases.

pages/managed-databases-for-postgresql-and-mysql/how-to/add-users.mdx

@@ -23,14 +23,15 @@ Users can connect to a database and access its data. Each one has a different se
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-3. Go to the **Users** tab. A list of users displays. If it is the first time you create a user, your list will display the user you set up during the creation of your Database Instance.
-4. Click **+ Create user** to create a new user, if you wish to.
-5. Click <Icon name="toggle" /> to grant admin rights to the user.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
+4. Go to the **Users** tab. A list of users displays. If it is the first time you create a user, your list will display the user you set up during the creation of your Database Instance.
+5. Click **+ Create user** to create a new user, if you wish to.
+6. Click <Icon name="toggle" /> to grant admin rights to the user.
     <Message type="note">
       Admin rights allow a user to create logical databases and users. These right do not override the permissions configured for the logical databases. Logical database permissions must be set up in the Permissions tab.
     </Message>
-6. Enter a **username** and **password**.
+7. Enter a **username** and **password**.
     <Message type="note">
       Optionally, you can configure the appropriate permissions according to the user.
       Three types of permissions are available:
@@ -40,7 +41,7 @@ Users can connect to a database and access its data. Each one has a different se
       You can select the permission type in the Permissions tab.
 
     </Message>
-7. Click **Create user** to confirm.
+8. Click **Create user** to confirm.
 
     Once the user is created, it is displayed in the user list.
 

pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx

@@ -25,8 +25,9 @@ These maintenance operations are set up, run, and scheduled by Scaleway, but you
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) scheduled for maintenance
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Look for an orange info icon to identify which Database Instances are scheduled for maintenance.
-3. Click the Database Instance name or <Icon name="more" /> > **More info** to access the database information page.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Look for an orange info icon to identify which Database Instances are scheduled for maintenance.
+4. Click the Database Instance name or <Icon name="more" /> > **More info** to access the database information page.
 
     If your Database Instance is scheduled for maintenance, you will see a banner on the top of the page informing you when the scheduled maintenance will take place. You can either wait for the maintenance to be applied automatically at the expected date and time, or you can apply it immediately.
 
@@ -35,7 +36,7 @@ These maintenance operations are set up, run, and scheduled by Scaleway, but you
     </Message>
 
 
-4. Click **Apply maintenance now** to apply the maintenance immediately. You are redirected to a screen that shows you the status of the maintenance. If you want a more detailed maintenance status, you can [use the API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-apply-database-instance-maintenance).
+5. Click **Apply maintenance now** to apply the maintenance immediately. You are redirected to a screen that shows you the status of the maintenance. If you want a more detailed maintenance status, you can [use the API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-apply-database-instance-maintenance).
 
     <Message type="important">
       Your Database Instance will be unavailable during the maintenance. This might take a few minutes.

pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx

@@ -23,16 +23,17 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) with local Storage
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the name of the Database Instance you want to edit. The database's Overview page displays.
-3. Scroll down to **Volume settings**, then click **Change volume type**.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the name of the Database Instance you want to edit. The database's Overview page displays.
+4. Scroll down to **Volume settings**, then click **Change volume type**.
     <Message type="important">
       Before changing the volume type, make sure your Instance is in one of the following states:
       - `READY` (represented as "Running" in the Scaleway console)
       - `DISK_FULL`
     </Message>
     A pop-up appears.
-4. Select **Block Storage** from the drop-down menu.
-5. Click **Update volume type** to confirm.
+5. Select **Block Storage** from the drop-down menu.
+6. Click **Update volume type** to confirm.
 
     The Database Instance goes into the `Initializing` state.
 

pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx

@@ -29,17 +29,18 @@ The clone feature allows you to create a new Database Instance from an existing
 ## How to clone a Database Instance
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-3. Scroll down to the **Clone** section.
-4. Click **Clone Database Instance**. A pop-up displays.
-5. Enter a name for your database or leave the default name suggested by the Scaleway console.
-6. Select a node type. You can keep the same node type, or upgrade to a bigger one.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
+4. Scroll down to the **Clone** section.
+5. Click **Clone Database Instance**. A pop-up displays.
+6. Enter a name for your database or leave the default name suggested by the Scaleway console.
+7. Select a node type. You can keep the same node type, or upgrade to a bigger one.
     <Message type="important">
       If you have a new-generation Database Instance using a Local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first. <br /><br />
 
       Similarly, if you have a new-generation Database Instance using a [Block volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) and want to create a clone on a first-generation Instance, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy).
     </Message>
-7. Click **Clone Database Instance**.
+8. Click **Clone Database Instance**.
 
 <Message type="important">
   The source Database Instance remains available during the cloning process in **Backing up mode**. Some actions are not available during this time. <br /><br />

pages/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings.mdx

@@ -27,8 +27,9 @@ Advanced settings allow you to modify the default configuration of your database
 </Message>
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the Database Instance name or <Icon name="more" /> > **More info** to access the database information page.
-3. Click the **Advanced settings** tab.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the Database Instance name or <Icon name="more" /> > **More info** to access the database information page.
+4. Click the **Advanced settings** tab.
 
     To add advanced settings, follow these steps:
 

pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx

@@ -21,12 +21,13 @@ categories:
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-3. Retrieve the Database Instance IP and port from the Database Instance information section.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
+4. Retrieve the Database Instance IP and port from the Database Instance information section.
     <Message type="note">
     Alternatively, you can click the **copy icon** under **Connection** to retrieve the database client connection command. This already includes your database IP and port.
     </Message>
-4. Connect to your database with the database client of your engine.
+5. Connect to your database with the database client of your engine.
 
     For MySQL, run the following command:
     ```bash
@@ -37,7 +38,7 @@ categories:
     ```bash
     psql -h <ip-address> -p <port> -U <username> -d rdb
     ```
-5. Enter the password that you defined upon [Database Instance creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/).
+6. Enter the password that you defined upon [Database Instance creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/).
 
   You are now connected to your Managed Database.
 

pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx

@@ -36,13 +36,14 @@ You can create new Database Instances to attach to your Private Network, or atta
   </Message>
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-3. Scroll to the **Network** section.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
+4. Scroll to the **Network** section.
     <Message type="note">
       Alternatively, you can follow the next steps from the **Private Networks** tab. Click **+ Attach to a Private Network** to open the configuration pop-up.
     </Message>
-4. Click **Attach Private Network** next to **Private endpoint**. A pop-up appears.
-5. Choose whether to:
+5. Click **Attach Private Network** next to **Private endpoint**. A pop-up appears.
+6. Choose whether to:
     - Select and attach an existing Private Network and select the network from the drop-down list.
         <Message type="important">
           The Database Instance must be attached to a Private Network in the same region.
@@ -55,7 +56,7 @@ You can create new Database Instances to attach to your Private Network, or atta
     <Message type="note">
       Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform/OpenTofu.
     </Message>
-6. Click **Attach to Private Network** to conclude.
+7. Click **Attach to Private Network** to conclude.
 
 ## How to connect to a Database Instance through a Public Gateway
 
@@ -64,10 +65,11 @@ You can create new Database Instances to attach to your Private Network, or atta
 ## How to detach a Database Instance from a Private Network
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-3. Click the **Private Networks** tabs. The Private Network configuration displays.
-4. Click <Icon name="unlink" /> next to the static IP that you want to unlink from your Database Instance.
-5. Click **Detach resource** to remove the Instance from your Private Network.
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
+4. Click the **Private Networks** tabs. The Private Network configuration displays.
+5. Click <Icon name="unlink" /> next to the static IP that you want to unlink from your Database Instance.
+6. Click **Detach resource** to remove the Instance from your Private Network.
 
 <Message type="note">
 This action takes a few moments to complete. During this time, your Database Instance:

pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx

@@ -26,8 +26,9 @@ Compared to traditional database management, which requires customers to provide
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. If you do not have a database already created, the creation page displays.
-2. Click **Create Database Instance**. The creation wizard displays.
-3. Complete the following steps in the wizard:
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click **Create Database Instance**. The creation wizard displays.
+4. Complete the following steps in the wizard:
     - Select a database engine. **PostgreSQL** and **MySQL** are available.
     - Choose a region. This is the geographical location where your database will be deployed.
     - Select a database configuration. You can choose between:
@@ -68,4 +69,4 @@ Compared to traditional database management, which requires customers to provide
           - one number
     </Message>
     - Enter a name for your Instance.
-4. Click **Create Database Instance** to confirm your choices and launch creation.
+5. Click **Create Database Instance** to confirm your choices and launch creation.

pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx

@@ -25,15 +25,16 @@ Read Replicas allow you to scale your Database Instance for read-heavy database
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-3. Scroll down to the **Read Replica** section.
-4. Click **Create Read Replica**. A pop-up displays.
-5. Select the Availability Zone (AZ) configuration. Two configurations are available:
+2. Select the geographical region of the Instance you want to manage from the drop-down.
+3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
+4. Scroll down to the **Read Replica** section.
+5. Click **Create Read Replica**. A pop-up displays.
+6. Select the Availability Zone (AZ) configuration. Two configurations are available:
 
     - **Same AZ**: Your Read Replica is hosted in the same AZ as your main Database Instance. We recommend this option for low-latency workflows.
     - **Multi-AZ**: Your Read Replica is hosted in a different AZ, ensuring the resilience of your Replica. We recommend this option for ensuring the availability of your infrastructure, and improving your disaster recovery plan.
 
-6. Select the network type. Two types are available:
+7. Select the network type. Two types are available:
 
     - **Public network** - Resources in a public network are publicly visible by default. The default Access Control List (ACL) settings allow anybody to connect to resources in your network. You can restrict access by configuring ACLs in the Allowed IPs section.
     - **Private Networks** - Private Networks allow you to create virtual Private Networks for your Databases, enabling them to communicate in an isolated network without the need for a public IP address. If you select this option, you must select an existing Private Network to attach to your Read Replica.
@@ -45,7 +46,7 @@ Read Replicas allow you to scale your Database Instance for read-heavy database
     <Message type="important">
     If you select **Public network**, you can [attach a Private Network](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-manage-private-networks) to your Read Replica after its creation. If you choose to attach your Read Replica to a Private Network, you will not be able to add a Public Network to the same Read Replica later via the Scaleway console. You can, however, use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/) to do so via a command line or Terraform/OpenTofu.
     </Message>
-7. Click **Create Read Replica**. A list of your Read Replicas displays.
+8. Click **Create Read Replica**. A list of your Read Replicas displays.
     <Message type="important">
     Read Replicas have the same node types as the main node. For example, if your main node is of the DB-GP-S type, so is your Read Replica. The Replica also inherits the main node's configuration. The data of your main node is fully replicated in the Read Replica.
     </Message>