fix(mdb): menu

Author: ldecarvalho-doc

managed-databases/mongodb/how-to/add-a-database.mdx

@@ -15,18 +15,20 @@ categories:
 
 <Macro id="requirements" />
 
-<Message type="requirement">
-- You have an account and are logged into the [Scaleway console](https://console.scaleway.com)
-- You have a [MongoDB™ Database Instance](/managed-databases/mongodb/quickstart)
-</Message>
+
+- 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) allowing you to perform actions in the intended Organization
+- A [MongoDB™ Database Instance](/managed-databases/mongodb/quickstart)
+- Installed either [mongosh](https://www.mongodb.com/docs/mongodb-shell/), or the [pymongo](https://pymongo.readthedocs.io/en/stable/) distribution for Python, or the Node.js [mongodb module](https://www.npmjs.com/package/mongodb) or the [mongo driver for Go](https://github.com/mongodb/mongo-go-driver), or [Mongoose](https://mongoosejs.com/) on your local machine
+
 
 ## How to connect via database client
 
 1. Click **MongoDB™** under **Managed 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 <Icon name="download" /> next to the **TLS certificate** to download it.
 4. Transfer the file to where you will execute the connection command.
-5. Return to the console and click **Connect** in the **Connect Database Instance** section.
+5. Return to the console and click **Connect** in the **Connect Database Instance** section. A pop-up appears.
 6. Select a connection mode. The following modes are available: `mongosh`, `Python`, `Go`, `Node.js` and `Mongoose`.
 7. Replace the variables in the commands with your information.
 
@@ -38,35 +40,34 @@ To connect to a public endpoint using the MongoDB™ shell:
 
 1. Replace the following variables in the command as described:
     ```sh
-    mongosh "mongodb+srv://{instance_id}.mgdb.{region}.scw.cloud" --tlsCAFile {your_certificate.pem} -u {username}
+    mongosh "mongodb+srv://{instance_id}.mgdb.{region}.scw.cloud" --tlsCAFile {your_certificate.pem} -u {username
     ```
 
-  - `{your-certificate.pem}` - the TLS certificate downloaded on **step 3**.
-  - `{username}` -  the username you defined upon Database Instance creation.
-  - `{db-instance-id}` - the UUID of your Database Instance.
-  - `{region}` - the database name you entered upon Database Instance creation. The default is called `rdb`.
+    - `{your-certificate.pem}` - the TLS certificate downloaded on **step 3**.
+    - `{username}` -  the username you defined upon Database Instance creation.
+    - `{db-instance-id}` - the UUID of your Database Instance.
+    - `{region}` - the database name you entered upon Database Instance creation. The default is called `rdb`.
 
-  ```
 2. Run the command.
 3. Enter your password when prompted.
 
 If the connection is successful, you should see the following message display on your console, and be able to write queries:
-  ```sh
-  The server generated these startup warnings when booting
-  Powered by MongoDB™ v0.9.0 and PostgreSQL 14.6.
-  ```
+    ```sh
+    The server generated these startup warnings when booting
+    Powered by MongoDB™ v0.9.0 and PostgreSQL 14.6.
+    ```
 
-Follow the same procedure to connect to a private endpoint for one node, replacing `{privateNetorkName}` with the name of your Private Netowrk:
+Follow the same procedure to connect to a private endpoint for one node, replacing `{privateNetorkName}` with the name of your Private Network:
 
-  ```sh
-  mongosh "mongodb://{instance_id}-0.{privateNetworkName}" -u {username}
-  ```
+    ```sh
+    mongosh "mongodb://{instance_id}-0.{privateNetworkName}" -u {username}
+    ```
 
 For multiple nodes, replace `{db-instance-id}` with the Database Instance UUID of each respective Instance, and `{privateNetworkName}` with the names of your Private Network:
 
-  ```sh
-  "mongodb://{instance_id}-0.{privateNetworkName},{instance_id}-1.{privateNetworkName},{instance_id}-2.{privateNetworkName}" -u {username}
-  ```
+    ```sh
+    "mongodb://{instance_id}-0.{privateNetworkName},{instance_id}-1.{privateNetworkName},{instance_id}-2.{privateNetworkName}" -u {username}
+    ```
 
 ### Python
 

managed-databases/mongodb/how-to/add-users.mdx

@@ -7,8 +7,8 @@ content:
   paragraph: This page explains how to create a MongoDB™ Database Instance
 tags: postgresql mongodb mongodb database-instance managed-database database
 dates:
-  validation: 2024-02-08
-  posted: 2023-08-01
+  validation: 2024-10-01
+  posted: 2024-10-01
 categories:
   - managed-databases
 ---
@@ -28,9 +28,9 @@ Document databases enable users to store and retrieve data in a document format,
 1. Click **MongoDB™** under **Managed Databases** on the side menu, if you do not have a Database Instance already created, the creation page displays.
 2. Click **Create a Database Instance**. The creation wizard displays.
 3. Complete the following steps in the wizard:
-    - Select ** MongoDB™** as a database engine.
+    - Select **MongoDB™** as a database engine.
     - Choose a region. This is the geographical location where your database will be deployed.
-    - Select a database configuration. You can choose between:
+    - Select a replica set configuration. You can choose between:
         - **Replica-set 1-node** - an instance of MongoDB™ that runs as a single server and does not provide redundancy or high availability.
         - **Replica-set 3-nodes** - a group of 3 MongoDB™ servers (1 primary and 2 standby nodes) that maintain the same data set. Replica sets provide redundancy and high availability and are the basis for all production deployments. If the main node fails for any reason, one of the remaining standby nodes is assigned and can take over requests, reducing downtime.
     - Select a node type.
@@ -46,4 +46,4 @@ Document databases enable users to store and retrieve data in a document format,
     - Enter a name for your Database Instance.
 4. Click **Create a Database Instance** to confirm your choices and launch creation.
 
-    You are taken to the **Overview** tab for your Database Instance, where you can see information including the **Endpoint** to enable you to connect to it.
+     You are taken to the **Overview** tab for your Database Instance.

managed-databases/mongodb/how-to/configure-advanced-settings.mdx

@@ -7,23 +7,23 @@ content:
   paragraph: This page explains how to delete a Database
 tags: managed-database postgresql mongodb mongodb document database-instance
 dates:
-  validation: 2024-02-08
-  posted: 2023-08-01
+  validation: 2024-10-01
+  posted: 2024-10-01
 categories:
   - managed-databases
 ---
 
 
 <Macro id="requirements" />
 
-<Message type="requirement">
-  - You have an account and are logged into the [Scaleway console](https://console.scaleway.com)
-  - You have a [MongoDB™ Database Instance](/managed-databases/mongodb/quickstart)
-</Message>
+- 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) allowing you to perform actions in the intended Organization
+- A [MongoDB™ Database Instance](/managed-databases/mongodb/quickstart)
+
 
 1. Click **MongoDB™** under **Managed 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 the page to the **Delete Instance** section and click **Delete Instance**. A pop-up appears to inform you that:
+3. Click the **Settings** tab, scroll down to the **Delete Database Instance** section and click **Delete Instance**. A pop-up appears to inform you that:
     <Message type="important">
       This will permanently destroy your Instance, and all your data will be lost. This action is irreversible.
     </Message>

managed-databases/mongodb/how-to/connect-database-instance.mdx

@@ -0,0 +1,35 @@
+---
+meta:
+  title: How to increase the storage of a Managed Database for MongoDB™
+  description: Guide to increasing the block volume of your MongoDB™ Database Instance at Scaleway.
+content:
+  h1: How to increase the storage of a Managed Database for MongoDB™
+  paragraph: Guide to increasing the block volume of your MongoDB™ Database Instance at Scaleway.
+tags: managed-database postgresql mysql upgrade
+dates:
+  validation: 2024-10-01
+  posted: 2024-10-01
+categories:
+  - managed-databases
+---
+
+You can increase the Block Storage volume of your MongoDB™ Database Instance in the Scaleway console anytime.
+
+<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) allowing you to perform actions in the intended Organization
+- A [MongoDB™ Database Instance](/managed-databases/mongodb/quickstart)
+
+
+## How to increase a Block Storage volume
+
+1. Click **MongoDB™** under **Managed Databases** on the side menu. A list of your Database Instances displays.
+2. Click the name of the Database Instance you want to configure. The Database Instance overview page displays.
+3. Scroll down to **Volume settings**.
+4. Specify your volume capacity (in GB). The amount you define will be your new volume capacity.
+    <Message type="important">
+      - You can increase your Block Storage volume to up to 10 TB.
+      - Block volume sizes cannot be decreased.
+    </Message>
+5. Click **Increase volume size** to confirm.