diff --git a/docs/Scaling horizontally, HA.md b/docs/Higher Availability and Disaster Recovery.md
similarity index 99%
rename from docs/Scaling horizontally, HA.md
rename to docs/Higher Availability and Disaster Recovery.md
index 2452cdf3..8f8f31db 100644
--- a/docs/Scaling horizontally, HA.md	
+++ b/docs/Higher Availability and Disaster Recovery.md	
@@ -1,4 +1,4 @@
-# HA, Horizontal Scaling and DR
+# Higher Availability and Disaster Recovery
 
 !!! Note
     SkySQL, unlike hyperscalers, deploy replicas in a active-active configuration. When primary crashes our intelligent proxy allows us to failover near instantly to an alternate replica. Or, failback when the original primary recovers. Ensuring data consistency even when replicas have a replication lag through “causal reads”, or transaction replay. Our underlying k8s based operator has smarts to rebuild replicas that lag a lot using cloud native snapshots.
@@ -65,4 +65,4 @@ One effective strategy to mitigate such risks is to replicate data to a data cen
 
 SkySQL empowers users to configure “external” replicas that can run anywhere, offering flexibility and resilience.
 
-To facilitate this, SkySQL provides several built-in stored procedures for configuring both “outbound” and “inbound” replication to any compatible MariaDB or MySQL server environment. This flexibility allows users to tailor their disaster recovery strategy based on their specific needs, whether replicating across regions, cloud providers, or maintaining self-managed standby environments.
\ No newline at end of file
+To facilitate this, SkySQL provides several built-in stored procedures for configuring both “outbound” and “inbound” replication to any compatible MariaDB or MySQL server environment. This flexibility allows users to tailor their disaster recovery strategy based on their specific needs, whether replicating across regions, cloud providers, or maintaining self-managed standby environments.