Skip to content

Commit 816b651

Browse files
fix(rdb): review jessi
Co-authored-by: Jessica <[email protected]>
1 parent 7d1ba1e commit 816b651

File tree

4 files changed

+8
-12
lines changed

4 files changed

+8
-12
lines changed

pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Yes, they are. Since July 2023, the automatic allocation of IP addresses via IPA
7373

7474
For any new Private Networks you create and attach to Managed Databases after July 2023, your private IP addresses are automatically allocated.
7575

76-
If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old private network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/#how-to-connect-to-a-database-instance-through-a-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API.
76+
If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old Private Network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/#how-to-connect-to-a-database-instance-through-a-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API.
7777

7878
In the example below, we show you how to do so via the API. We specify the automated configuration of your Private Network via IPAM using `"ipam_config": {},`.
7979

pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,16 +32,16 @@ You can change your Database Instance the node type and enable High Availability
3232
Make sure that the Database Instance you choose provides sufficient disk space for your database. Otherwise, an error message will be displayed, and the database will not be upgraded.
3333
</Message>
3434

35-
The action of changing the node type will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds.
35+
Changing the node type performs a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several seconds.
3636

37-
## Enable High Availability
37+
## How to enable High Availability
3838

3939
You define your Database Instance's node configuration upon its [creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database). Two node configuration modes are available with PostgreSQL or MySQL Database Instances.
4040

4141
- **High Availability**: creates a secondary Instance with an up-to-date replica of the database. If the primary Instance fails, the secondary takes over requests.
4242
- **Standalone**: a standalone database provisioned on a single node.
4343

44-
If you are standalone mode, you can change the node configuration to High Availability in the console anytime.
44+
If you are in standalone mode, you can change the node configuration to High Availability in the console at any time.
4545

4646
<Message type="important">
4747
Once you upgrade to the High Availability mode, you cannot revert to standalone.
@@ -61,5 +61,5 @@ If you are standalone mode, you can change the node configuration to High Availa
6161
6. Click **Activate**.
6262

6363
<Message type="note">
64-
The action of changing the node configuration will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds.
64+
Changing the node type performs a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several seconds.
6565
</Message>

pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ When you set up [autobackups](/managed-databases-for-postgresql-and-mysql/how-to
1616
You can create new Database Instances from a snapshot.
1717

1818
<Message type="important">
19-
Refer to the [How to create a Database Instance from a snapshot]() procedure for more information.
19+
Refer to the [How to create a Database Instance from a snapshot](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database#how-to-create-a-database-instance-from-a-snapshot) procedure for more information.
2020
</Message>
2121

2222
You can have up to 100 snapshots per Instance and Project (depending on quotas).

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

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Users can connect to a database and access its data. Each one has a different se
4040
</Message>
4141

4242
<Message type="important">
43-
Permissions are applied on existing items **at the moment the configuration is set**, and not applied to any items created afterward.
43+
Permissions are applied to existing items **at the moment the configuration is set**. They cannot be applied to any items created afterward.
4444
When you modify your Database configuration, your configured permissions are automatically set to **Custom**. The **Custom** setting ensures that your permissions are still valid for items created before you reconfigured your Database.
4545
Any items created after you change your configuration will not have permissions applied to them, you must set new permissions.
4646
</Message>
@@ -52,7 +52,7 @@ To update the password, the permissions or delete the user, click <Icon name="mo
5252

5353
## Set permissions for an existing user
5454

55-
Permissions define the actions a user can perform on a logical database. A database user is generated automatically when you create your Database Instance and this user is attributed all permissions. However, newly created users have no permissions by default.
55+
Permissions define the actions a user can perform on a logical database. A database user is automatically generated when you create your Database Instance, to whom the permissions are attributed. However, newly created users have no permissions by default.
5656

5757
1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
5858
2. Select the geographical region of the Instance you want to manage from the drop-down.
@@ -68,7 +68,3 @@ Permissions define the actions a user can perform on a logical database. A datab
6868

6969
</Message>
7070
7. Click **Update user** to confirm.
71-
72-
73-
74-

0 commit comments

Comments
 (0)