Fix typo in high availability docs (elastic#126788)

shainaraskas · web-flow · commit 7f4769b97f76 · 2025-04-14T13:12:46.000-04:00
diff --git a/docs/reference/high-availability.asciidoc b/docs/reference/high-availability.asciidoc
@@ -18,7 +18,7 @@ To effectively distribute read and write operations across nodes, the nodes in a
 +
 Co-locating nodes in a single location exposes you to the risk of a single outage taking your entire cluster offline. To maintain high availability, you can prepare a second cluster that can take over in case of disaster by implementing {ccr} (CCR).
 +
-CCR provides a way to automatically synchronize indices from a leader cluster to a follower cluster. This cluster could be in a different data center or even a different content from the leader cluster. If the primary cluster fails, the secondary cluster can take over.
+CCR provides a way to automatically synchronize indices from a leader cluster to a follower cluster. This cluster could be in a different data center or even a different continent from the leader cluster. If the primary cluster fails, the secondary cluster can take over.
 +
 TIP: You can also use CCR to create secondary clusters to serve read requests in geo-proximity to your users.
 

Original file line number	Diff line number	Diff line change
`@@ -18,7 +18,7 @@ To effectively distribute read and write operations across nodes, the nodes in a`
`18`	`18`	`+`
`19`	`19`	`Co-locating nodes in a single location exposes you to the risk of a single outage taking your entire cluster offline. To maintain high availability, you can prepare a second cluster that can take over in case of disaster by implementing {ccr} (CCR).`
`20`	`20`	`+`
`21`		`-CCR provides a way to automatically synchronize indices from a leader cluster to a follower cluster. This cluster could be in a different data center or even a different content from the leader cluster. If the primary cluster fails, the secondary cluster can take over.`
	`21`	`+CCR provides a way to automatically synchronize indices from a leader cluster to a follower cluster. This cluster could be in a different data center or even a different continent from the leader cluster. If the primary cluster fails, the secondary cluster can take over.`
`22`	`22`	`+`
`23`	`23`	`TIP: You can also use CCR to create secondary clusters to serve read requests in geo-proximity to your users.`
`24`	`24`