feat(acc): reviews 15/07

ldecarvalho-doc · ldecarvalho-doc · commit 5360e4b1a3e1 · 2025-07-15T11:30:53.000+02:00
diff --git a/pages/account/how-to/report-abuse.mdx b/pages/account/how-to/report-abuse.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Report abuse incidents related to Scaleway accounts.
 tags: report incident abuse
 dates:
-  validation: 2025-01-07
+  validation: 2025-07-15
   posted: 2024-02-19
 categories:
   - account
@@ -22,22 +22,22 @@ import Requirements from '@macros/iam/requirements.mdx'
 ## How to report an abuse
 
 1. Go to the [Report Abuse](https://console.scaleway.com/support/abuses/create/) page. A form displays.
-2. Enter the IP address, domain name, or URL of the source you want to report.
-3. Enter the date of publication of the illegal content or the start date of the illegal behavior.
-4. Enter the time of the publication of the illegal content or the time the illegal behavior started.
-5. Select the type of abuse you wish to report in the drop-down box
+2. Select the type of abuse you wish to report in the drop-down box.
     <Message type="tip">
     The different types of content or illegal behavior that can be reported are described in Scaleway’s [Abuse notice](https://www.scaleway.com/en/abuse-notice/).
     </Message>
     <Message type="important">
     Falsely reporting content or activity as illegal only to obtain its removal or to stop its distribution, is punishable by one year imprisonment and a €15,000 fine.
     </Message>
-6. Enter your email address and name if required.
-7. Describe what you have observed in as much detail as possible. Provide information such as logs, time zones, headers, the precise location and, if applicable, the email addresses to which the content is made accessible.
+3. Describe what you have observed in as much detail as possible. Provide information such as logs, time zones, headers, the precise location and, if applicable, the email addresses to which the content is made accessible.
     <Message type="important">
     This description will be directly forwarded to our customer. Therefore, refrain from including any confidential or personal information which you do not want them to have access to.
     Scaleway denies all responsibility for the use that could be made by third parties of any information that you provide in this field.
     </Message>
+4. Enter the IP address, domain name, or URL of the source you want to report.
+5. Enter the date of publication of the illegal content or the start date of the illegal behavior.
+6. Enter the time of the publication of the illegal content or the time the illegal behavior started.
+7. Enter your email address and name if required.
 8. Check the box confirming that you are submitting this report in good faith.
 9. Once you have entered the information mentioned above, check the CAPTCHA form and click **Submit abuse report**.
     <Message type="note">
diff --git a/pages/account/how-to/switch-account-to-corporate.mdx b/pages/account/how-to/switch-account-to-corporate.mdx
@@ -7,7 +7,7 @@ content:
  paragraph: Convert your Scaleway account to a corporate account.
 tags: account personal corporate business
 dates:
- validation: 2025-01-04
+ validation: 2025-07-15
  posted: 2023-09-03
 categories:
  - console
@@ -18,17 +18,30 @@ import image from './assets/scaleway-billing-personal-info.webp'
 import image2 from './assets/scaleway-billing-corporate-info.webp'
 
 
-The [Scaleway console](https://console.scaleway.com) allows you to choose between two types of accounts, Personal and Corporate. All users are given the possibility to select one or the other option when first signing up for a Scaleway account. If you signed up for a personal account and need to convert to a corporate one, follow these instructions.
+The [Scaleway console](https://console.scaleway.com) allows you to choose between four account use cases:
+
+- **Corporate**
+- **Startup**
+- **Consultant or Freelancer**
+- **Personal Project**.
+
+All users are given the possibility to select one or the other option when first signing up for a Scaleway account.
+
+When you select either **Corporate**, **Startup** or **Consultant or Freelancer**, your account is considered of the **Corporate** type.
+
+When you select **Personal Project**, your account is considered of the **Personal** type.
+
+If you signed up for a personal account and need to convert to a corporate one, follow these instructions.
 
 <Message type="important">
- Switching to a corporate account is permanent. You will not be able to switch back to a personal account once the conversion to corporate is completed.
+  Switching to a corporate account is permanent. You will not be able to switch back to a personal account once the conversion to corporate is completed.
 </Message>
 
 <Requirements />
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 
 1. Click **Billing** in the top right drop-down menu. The **Billing** dashboard displays.
-2. Click the **Payment and billing tab**.
+2. Click the **Payment and billing** tab.
 3. Scroll down to billing information, then click <Icon name="edit" /> **Edit**. A pop-up with your billing information displays.
     <Lightbox image={image} alt="" />
 4. Check the box at the top to confirm you wish to have a corporate account. A new form displays.
diff --git a/pages/account/how-to/use-the-search-bar.mdx b/pages/account/how-to/use-the-search-bar.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Efficiently search for features and settings in the Scaleway console.
 tags: account search-bar resource
 dates:
-  validation: 2025-01-03
+  validation: 2025-07-15
   posted: 2024-03-14
 categories:
   - account
diff --git a/pages/managed-databases-for-postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx b/pages/managed-databases-for-postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to import or migrate your data into Managed Databases for PostgreSQL from another database or backup files
 tags: managed database postgresql mysql import migrate backup
 dates:
-  validation: 2025-01-02
+  validation: 2025-07-15
   posted: 2024-06-24
 ---
 import Requirements from '@macros/iam/requirements.mdx'
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to change the volume type of your Database
 tags: managed-database database volume-type
 dates:
-  validation: 2025-04-23
+  validation: 2025-07-15
   posted: 2021-03-10
 categories:
   - managed-databases
@@ -24,6 +24,18 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) with local Storage
 
+## Important information
+
+Since there are different types of volumes for Database Instances, make sure you are aware of the following information before changing the volume type:
+
+- When autobackup is enabled for your local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/managed-databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
+- When switching from a local volume to a Block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage.
+- Disk size cannot be reduced. Therefore, when switching from local to Block, the volume size remains the same by default.
+- When switching from a Block to a local volume, make sure to select a node with a local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance.
+
+
+## How to change the volume type
+
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
 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.
@@ -39,9 +51,23 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an
 
     The Database Instance goes into the `Initializing` state.
 
-    <Message type="important">
-      - When switching from a local volume to a Block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage.
-      - Disk size cannot be reduced, so when switching from local to Block, the volume size remains the same by default.
-      - When switching from a Block to a local volume, make sure to select a node with a local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance.
-      - When autobackup is enabled for your local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/managed-databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
-    </Message>
+
+## The volume changing process
+
+During the process:
+
+- The Database Instance will display the `initializing` status, but remains available available.
+- Changing the volume type can take a while, depending on the amount of data and the node type of the Database Instance. Data is synchronized between nodes in live, which means you can continue performing write operations.
+    <Message type="tip">
+      - Avoid performing too many write operations during the data synchronization.
+      - Delay batch or scheduled scripts if possible.
+    </Message>
+- When all the data is synchronized, a switchover is performed between nodes of the cluster. This means that the database will be unavailable few dozen of seconds during at this time.
+
+
+
+
+
+
+
+
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Step-by-step guide to cloning a PostgreSQL or MySQL Database Instance.
 tags: managed-database database database-instance
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2019-10-20
 categories:
   - managed-databases
@@ -38,13 +38,11 @@ The clone feature allows you to create a new Database Instance from an existing
 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>
+      If you have a 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.
+      </Message>
 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 />
-  The time it takes to clone a Database Instance with Local Storage depends on the size of the database. For Database Instances with Block Storage the cloning process is slightly faster.
+  - The source Database Instance remains available during the cloning process in **Backing up mode**. Some actions are not available during this time.
+  - The time it takes to clone a Database Instance with Local Storage depends on the size of the database. For Database Instances with Block Storage the cloning process is slightly faster.
 </Message>
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Guide to configuring advanced settings for your PostgreSQL and MySQL databases.
 tags: managed-database postgresql mysql database-instance advanced-settings
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2019-05-11
 categories:
   - managed-databases
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Instructions for connecting your Database Instance over a Private Network.
 tags: managed-database postgresql mysql private-network database-instance
 dates:
-  validation: 2025-01-04
+  validation: 2025-07-15
   posted: 2019-11-15
 categories:
   - managed-databases
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to create Read Replicas for PostgreSQL and MySQL databases.
 tags: managed-database read-replica read replicas
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2022-09-01
 categories:
   - managed-databases
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Instructions for deleting a PostgreSQL or MySQL Database Instance on Scaleway.
 tags: managed-database postgresql mysql database-instance
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2019-05-11
 categories:
   - managed-databases
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx
@@ -7,15 +7,14 @@ content:
   paragraph:  Instructions for enabling Autobackup for PostgreSQL and MySQL databases.
 tags: managed-dabatase autobackup database
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2019-05-11
 categories:
   - managed-databases
   - postgresql-and-mysql
 ---
 import Requirements from '@macros/iam/requirements.mdx'
 
-
 With the autobackup feature, the creation and management of your Database Instance backups is automated according to your backup schedule configuration.
 
 Two types of autobackups are available at Scaleway: [backups](/managed-databases-for-postgresql-and-mysql/concepts/#database-backup) and [snapshots](/managed-databases-for-postgresql-and-mysql/concepts/#database-snapshot).
@@ -33,11 +32,9 @@ Backups are used when your Database Instance's storage option is a Local volume.
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
 
 <Message type="note">
-  The autobackup feature is enabled by default upon the creation of an Instance. Simultaneously, a schedule policy is created. The default autobackup frequency is of 1 per day with a retention period of 7 days. You can change this in the Database Instance information page after Instance creation.
-  <br />
-  By default, the Database Instance creation date is used as the base timestamp for the automated backups. When you change the schedule configuration, the moment you validated the new configuration becomes the new base timestamp. For example, if at 8 a.m. on a Thursday you update the autobackup frequency to 24h, your next autobackup will be created at 8 a.m. on a Friday.
-  <br />
-  When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/managed-databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
+  - The autobackup feature is enabled by default upon the creation of an Instance. Simultaneously, a schedule policy is created. The default autobackup frequency is of 1 per day with a retention period of 7 days. You can change this in the Database Instance information page after Instance creation.
+  - By default, the Database Instance creation date is used as the base timestamp for the automated backups. When you change the schedule configuration, the moment you validated the new configuration becomes the new base timestamp. For example, if at 8 a.m. on a Thursday you update the autobackup frequency to 24h, your next autobackup will be created at 8 a.m. on a Friday.
+  - When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/managed-databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
 </Message>
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Guide to managing allowed IP addresses for your Database Instances.
 tags: managed-database ip-address database
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2019-05-11
 categories:
   - managed-databases
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Step-by-step guide to managing manual backups for PostgreSQL and MySQL databases.
 tags: managed-database database instance backup
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2021-03-10
 categories:
   - managed-databases
@@ -40,7 +40,9 @@ You can create manual backups for Database Instances with Block Storage if the D
 
 1. Click the **Backups** tab on your selected Database Instance's information page.
 2. Click <Icon name="more" /> > **Restore** next to the name of the backup you want to restore. A pop-up displays.
-4. Select the Database Instance and the database to which you wish to restore the backup.
+4. Select the Database Instance and the database to which you wish to restore the backup. Two options are available:
+    - Restoring to the original database. This will restore the backup to the same database.
+    - Restoring to a new database. If you select this option, you must set a name for your new database.
 5. Click **Restore backup**.
     <Message type="note">
       Large database backups can take up to several hours to restore.
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Instructions for managing snapshots of PostgreSQL and MySQL databases.
 tags: managed-database database database-snapshot
 dates:
-  validation: 2025-01-06
+  validation: 2025-07-15
   posted: 2021-03-10
 categories:
   - managed-databases
@@ -38,7 +38,7 @@ You can have up to 100 snapshots per Instance and Project (depending on quotas).
     A pop-up displays.
 3. Enter a name for your snapshot and set up the expiration date and time.
     <Message type="note">
-      The default retention period for snapshots is 365 days.
+      The default retention period for snapshots is 7 days.
     </Message>
 4. Click **Create snapshot** to confirm.
 
@@ -49,7 +49,7 @@ You can restore the data contained in a snapshot to a Database Instance. When yo
 1. Go to the **Snapshots** tab of your Database Instance of choice.
 2. Click the <Icon name="more" /> next to the name of the snapshot.
 3. Click **Create Database Instance from snapshot**. A pop-up appears.
-4. Enter a name for your new Instance.
+4. Enter a name for your new Instance or leave the name suggested by Scaleway.
 5. Choose a node type and configuration.
     <Message type="important">
       It is possible to select a different (larger or smaller) node type for your new Instance. However, the Block volume size will be the same as the size of the restored snapshot. All Instance settings will be restored if you chose a node type with the same or more memory size than the initial Instance. Settings will be reset to the default if your node type has less memory.
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to remove the public endpoint of your Database Instance or Read Replica
 tags: managed-database postgresql mysql endpoints database-instance
 dates:
-  validation: 2025-01-04
+  validation: 2025-07-15
   posted: 2024-03-22
 categories:
   - managed-databases
diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx
diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/disk-full.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/disk-full.mdx
