AUTO: Sync ScalarDB docs in English to docs site repo

Author: josh-wong

docs/scalardb-cluster/remote-replication.mdx

@@ -5,17 +5,19 @@ tags:
 displayed_sidebar: docsEnglish
 ---
 
-# Replicate Data for Disaster Recovery
+# Replicate Data for High Availability
 
-ScalarDB Cluster can replicate its managed data to a remote site for disaster recovery. The remote replication feature provides near-real-time replication of write operations from a primary site to one or more backup sites. This feature ensures business continuity by enabling failover to a backup site when disasters or other critical failures affect the primary site.
+ScalarDB Cluster can replicate its managed data to remote sites for high availability and workload distribution. The remote replication feature provides near-real-time replication of write operations from a primary site to one or more backup sites.
+
+This feature ensures business continuity by enabling failover to a backup site in the event of disasters or critical failures affecting the primary site. Additionally, the backup sites can function as read replicas, helping to offload analytical queries, reporting, and business intelligence workloads.
 
 ## What is remote replication in ScalarDB?
 
 Remote replication in ScalarDB uses a hybrid approach, combining synchronous and asynchronous replication. This ensures zero data loss (a recovery point objective, or RPO, of zero) while minimizing performance impact at the primary site. The recovery time objective (RTO) can be flexibly adjusted by controlling the amount of computing resources. This feature is built on top of ScalarDB Cluster, making it cloud-agnostic and database-agnostic. This allows replication from one database in one cloud vendor to another, possibly different kind of database in a different cloud vendor.
 
 ## Key benefits
 
-Remote replication provides several key advantages for disaster recovery and business continuity:
+Remote replication provides several key advantages:
 
 - Guarantees zero data loss (RPO of 0) for all committed transactions.
 - Minimizes performance impact through the combination of synchronous and asynchronous processing.