fix(red): HA

faq/databases-for-redis.mdx

@@ -90,15 +90,15 @@ Refer to the image below to see which node types belong to which node class.
 
 ## What's the difference between High Availability (HA) and Cluster mode?
 
-A Redis cluster contains a minimum of 3 nodes and up to 6 nodes. Each node contains a source and a replica.
+A Redis™ cluster contains a minimum of 3 nodes and up to 6 nodes. Each node contains a source and a replica.
 The cluster nodes use hash partitioning to split the keyspace into key slots. Each replica copies the data of a specific source and can be reassigned to replicate another source or be elected as a source node if needed.
 This is much better for scaling as the operation is spread across multiple nodes instead of having a single entry point.
 
 <Lightbox src="scaleway-redis-cluster.webp" alt="" />
 
-A two-node architecture for Redis™ with a primary node being duplicated in a standby node might increase the durability of the data but does not prevent the service from failing as automatic failover is not available for Redis databases.
-This means that the primary node will be a Single Point Of failure.
-Scaleway does not provide two nodes HA Redis™ Database Instances but offers a state-of-the-art Redis Cluster Architecture, which can scale vertically and horizontally with built-in High Availability.
+Two-node High Availability configurations are available with Redis™ Database Instances. This configuration type allows you to create a standby node, with an up-to-date replica of the database. If the main node fails for any reason, the standby can take over requests, reducing downtime.
+
+The HA standby node is linked to the main node, using asynchronous replication. Asynchronous replication allows you to maintain good performance.
 
 ## Can I change the username and password of my Database Instance's default user?
 

managed-databases/redis/concepts.mdx

@@ -35,7 +35,9 @@ A Database Instance is made up of multiple (at least 1) dedicated compute nodes,
 
 ## High availability
 
-High Availability is handled through the Redis™ clustering feature. This is a 3-node multi-master architecture. In case of downtime on a node in the cluster, a new node is able to take over the requests with minimal downtime.
+High Availability is a Database Instance configuration that allows you to create a standby node, with an up-to-date replica of the database. If the main node fails for any reason, the standby can take over requests, reducing downtime.
+
+The HA standby node is linked to the main node, using asynchronous replication. Asynchronous replication allows you to maintain good performance.
 
 ## Horizontal scaling
 

managed-databases/redis/how-to/create-a-database-for-redis.mdx

@@ -33,6 +33,7 @@ Managed Database for Redis™<sup>*</sup> is a low-latency caching solution base
     - Select the version of Redis™ you wish to use on your Instance.
     - Select a database configuration. You can choose between:
         - **Cluster mode**: creates the database as a Cluster composed of three or more nodes. The cluster uses partitioning to split the keyspace. Each partition is replicated and can be reassigned or elected as the primary when necessary.
+        - **High Availability**: creates a secondary node with an up-to-date replica of the Database Instance. If the primary node fails, the secondary one will take over requests, reducing downtime.
         - **Standalone**: creates a standalone database provisioned on a single node.
     - Select a node type.
 4. Configure your Network. You can select either:

managed-databases/redis/quickstart.mdx

@@ -35,6 +35,7 @@ Managed Database for Redis™ is a low-latency caching solution based on in-memo
     - Select the version of Redis™ you wish to use on your Instance.
     - Select a database configuration. You can choose between:
         - **Cluster mode**: creates the database as a cluster composed of three or more nodes. The cluster uses partitioning to split the keyspace. Each partition is replicated and can be reassigned or elected as the primary when necessary.
+        - **High Availability**: creates a secondary node with an up-to-date replica of the Database Instance. If the primary node fails, the secondary one will take over requests, reducing downtime.
         - **Standalone**: creates a standalone database provisioned on a single node.
     - Select a node type.
 4. Configure your network. You can select either:

managed-databases/redis/reference-content/ensuring-data-persistence.mdx

@@ -49,11 +49,9 @@ A Redis cluster contains a minimum of three nodes and up to six nodes. Each node
 
 ## High Availability
 
-The Scaleway Managed Databases team is currently working on a High Availability configuration that will allow standalone nodes to be deployed with a replica node.
+High Availability is a Database Instance configuration that allows you to create a standby node, with an up-to-date replica of the database. If the main node fails for any reason, the standby can take over requests, reducing downtime.
 
-This feature is expected in October 2023.
-
-Follow our [changelog](/changelog/) to remain up-to-date with the latest improvements in Managed Databases for Redis™.
+The HA standby node is linked to the main node, using asynchronous replication. Asynchronous replication allows to keep good performances.
 
 <br/>
-<sup>*</sup> <small>Redis is a trademark of Redis Labs Ltd. Any rights therein are reserved to Redis Labs Ltd. Any use by Scaleway is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Scaleway. </small>
+<sup>*</sup> <small>Redis is a trademark of Redis Labs Ltd. Any rights therein are reserved to Redis Labs Ltd. Any use by Scaleway is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Scaleway. </small>