Skip to content

Commit 86ef83b

Browse files
fix(gen): reviews 02/05 (#5049)
1 parent 3de2f49 commit 86ef83b

File tree

6 files changed

+26
-29
lines changed

6 files changed

+26
-29
lines changed

pages/account/troubleshooting/cannot-erase-account.mdx

Lines changed: 8 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -7,29 +7,22 @@ content:
77
paragraph: Resolve issues encountered when deleting Scaleway accounts.
88
tags: account close delete deactivate close-account
99
dates:
10-
validation: 2024-11-27
10+
validation: 2025-06-02
1111
posted: 2024-03-28
1212
categories:
1313
- console
1414
---
1515

1616
## My request to close my account and erase personal data has failed
1717

18-
### Problem
19-
When you click the **Send request** button, an error message appears. This message says that you still have active resources.
18+
### Potential problems
19+
1. When you click the **Send request** button, an error message appears. This message says that you still have active resources.
20+
2. I received an email explaining that my request to erase my account and personal data had failed.
2021

2122
### Cause
22-
You have active resources, preventing us from proceeding with your request.
23+
1. You have active resources, preventing us from proceeding with your request.
24+
2. You may have unpaid consumption, preventing us from proceeding with your request.
2325

2426
### Solution
25-
You can check all your active resources from your [Organization dashboard](https://console.scaleway.com/organization). If one or more resources are listed, they are active. You need to delete all of them manually. In this situation, you must wait for the current month's invoice to be paid before sending another request to erase your account.
26-
27-
28-
### Problem
29-
I received an email explaining that my request to erase my account and personal data had failed.
30-
31-
### Cause
32-
You may have unpaid consumption, preventing us from proceeding with your request.
33-
34-
### Solution
35-
You can check your consumption from your [Billing space](https://console.scaleway.com/billing). All invoices must be marked as paid, and your current consumption must be zero. Once these criteria are met, you can send another request to delete your account and erase personal data.
27+
1. You can check all your active resources from your [Organization dashboard](https://console.scaleway.com/organization). If one or more resources are listed, they are active. You need to delete all of them manually. In this situation, you must wait for the current month's invoice to be paid before sending another request to erase your account.
28+
2. You can check your consumption from your [Billing space](https://console.scaleway.com/billing). All invoices must be marked as paid, and your current consumption must be zero. Once these criteria are met, you can send another request to delete your account and erase personal data.

pages/account/troubleshooting/cannot-log-into-my-account.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ content:
77
paragraph: Fix issues preventing login to Scaleway accounts.
88
tags: login unrecognized-ip password 2fa
99
dates:
10-
validation: 2024-11-27
10+
validation: 2025-06-02
1111
posted: 2022-10-19
1212
categories:
1313
- console

pages/billing/how-to/redeem-voucher-code.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ content:
77
paragraph: Instructions for redeeming a voucher code in the Scaleway console.
88
tags: discount voucher billing redeem
99
dates:
10-
validation: 2024-11-26
10+
validation: 2025-06-02
1111
posted: 2024-02-15
1212
categories:
1313
- billing
@@ -41,10 +41,10 @@ Voucher codes are unique and valid only for a defined period.
4141

4242
Once the voucher is redeemed, it will appear in the list of your vouchers.
4343

44-
## Understanding voucher scope
44+
## Understanding voucher scopes
4545
Vouchers provide discounts or credits to use on our services. However, certain conditions and exclusions apply to their usage.
4646

47-
### Inclusive and Exclusive vouchers
47+
### Inclusive and exclusive vouchers
4848
- **Incl. (Inclusive)**: The voucher applies only to the products or services listed after "Incl." (e.g., "Incl. PRO2," means that the voucher only applies to PRO2 Instances).
4949

5050
- **Excl. (Exclusive)**: The voucher cannot be applied to the products or services listed after "Excl." (e.g., "Excl. Apple Silicon" means that the voucher does not apply to Apple Silicon machines).

pages/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ content:
66
h1: How to generate API keys for API and SMTP sending with IAM
77
paragraph: Learn how to generate API keys for Transactional Email using IAM.
88
dates:
9-
validation: 2024-11-26
9+
validation: 2025-06-02
1010
posted: 2022-11-07
1111
---
1212

tutorials/deploy-hasura-engine-database-postgresql/index.mdx

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,18 @@ categories:
1010
- postgresql-and-mysql
1111
hero: assets/scaleway_hasura.webp
1212
dates:
13-
validation: 2024-11-25
13+
validation: 2025-06-02
1414
posted: 2020-07-08
1515
---
1616

1717
The [Hasura GraphQL Engine](https://hasura.io) is a [GraphQL](https://graphql.org/) server and provides developers with real-time GraphQL APIs for Postgres applications. The application allows you to configure webhook triggers on database events and helps you build GraphQL apps backed by Postgres or incrementally move to GraphQL for existing applications using Postgres.
1818

1919
In this tutorial, you will learn how to get started with Hasura GraphQL Engine using a pre-built Docker container on your local computer, linked to a managed [Scaleway Database for PostgreSQL](https://www.scaleway.com/en/database/).
2020

21+
<Message type="important">
22+
Make sure you save your secret and access keys, as you will need them in the following step.
23+
</Message>
24+
2125
<Macro id="requirements" />
2226

2327
- A Scaleway account logged into the [console](https://console.scaleway.com)
@@ -49,7 +53,7 @@ Hasura provides a pre-configured [repository](https://github.com/hasura/graphql-
4953
```
5054

5155
<Message type="note">
52-
If your database password contains special characters like `@`, `!`, or `#`, ensure they are [URL-encoded](https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters). The default `dbname` is `rdb`.
56+
If your database password contains special characters like `@`, `!`, or `#`, ensure they are [URL-encoded](https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters). The default `dbname` is `rdb`.
5357
</Message>
5458

5559
3. Run the script:

tutorials/upgrade-managed-postgresql-database/index.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
meta:
33
title: Upgrading your Database for PostgreSQL to the latest version
4-
description: This page shows how to upgrade your Database for PostgreSQL to the latest version
4+
description: This page shows how to upgrade your Database for PostgreSQL to the latest version
55
content:
66
h1: Upgrading your Database for PostgreSQL to the latest version
7-
paragraph: This page shows how to upgrade your Database for PostgreSQL to the latest version
7+
paragraph: This page shows how to upgrade your Database for PostgreSQL to the latest version
88
tags: storage PostgreSQL Database rdb
99
dates:
10-
validation: 2024-11-25
10+
validation: 2025-06-02
1111
categories:
1212
- postgresql-and-mysql
1313
---
@@ -42,12 +42,12 @@ There are three steps to completing a manual migration: creating a new PostgreSQ
4242
This tutorial works with all versions of PostgreSQL. If you prefer another version than PostgreSQL 13, select your preferred version during the Instance creation.
4343
</Message>
4444

45-
1. Open the [Scaleway console](https://console.scaleway.com) in a web browser and click **Managed Databases** in the **Storage** section of the side menu. The list of your databases displays.
45+
1. Open the [Scaleway console](https://console.scaleway.com) in a web browser and click **Managed Databases** in the **Storage** section of the side menu. The list of your databases displays.
4646
2. Click **+ Create a Database Instance**. The [Database Instance creation wizard](https://console.scaleway.com/rdb/instances/create) displays.
4747
3. Select **PostgreSQL-13** from the drop-down list and fill in the [required information](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) for your new database Instance. Then click **Create an Instance**. Your database is created, and you are redirected to the database dashboard.
4848
<Message type="note">
4949
Ensure your new Database Instance is located in the same geographical region as your old one.
50-
</Message>
50+
</Message>
5151
4. Click the **Users** tab and replicate the users of your existing Database Instance.
5252

5353
### Backing up your existing database using the Scaleway API
@@ -98,7 +98,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ
9898
```
9999
<Message type="note">
100100
If you want to migrate several logical databases, repeat the command above for each of them.
101-
</Message>
101+
</Message>
102102

103103
### Restoring your backup on your new Database Instance
104104

@@ -123,7 +123,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ
123123
* `<my_database>`: The name of your PostgreSQL database, for example: `customer_data`.
124124
* `<database_instance_id>`: The ID of your **new** Database Instance, for example: `d401ff10-350d-4707-9571-c861677f0031`.
125125

126-
You will receive a [JSON formatted](https://www.json.org/json-en.html) output with information about the backup. The **status** should be `restoring`:
126+
You will receive a [JSON formatted](https://www.json.org/json-en.html) output with information about the backup. The **status** should be `restoring`:
127127

128128
```json
129129
{

0 commit comments

Comments
 (0)