From 42dd5e2612ceae8f01e6bacb8e6ac5d32a9c9407 Mon Sep 17 00:00:00 2001
From: "I. Elisa Pasaoglu" <72536009+ilmiye@users.noreply.github.com>
Date: Thu, 3 Oct 2024 19:09:44 +0100
Subject: [PATCH] Fix doc about max number of failing zone (#9512)

* Fix doc about max number of failing zone

* Update docs/sources/mimir/configure/configure-zone-aware-replication.md

Co-authored-by: Nick Pillitteri <56quarters@users.noreply.github.com>

---------

Co-authored-by: Nick Pillitteri <56quarters@users.noreply.github.com>
---
 .../sources/mimir/configure/configure-zone-aware-replication.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/mimir/configure/configure-zone-aware-replication.md b/docs/sources/mimir/configure/configure-zone-aware-replication.md
index f847ef75369..7f86231c40d 100644
--- a/docs/sources/mimir/configure/configure-zone-aware-replication.md
+++ b/docs/sources/mimir/configure/configure-zone-aware-replication.md
@@ -71,7 +71,7 @@ With a replication factor of 3, which is the default, deploy the Grafana Mimir c
 Deploying Grafana Mimir clusters to more zones than the configured replication factor does not have a negative impact.
 Deploying Grafana Mimir clusters to fewer zones than the configured replication factor can cause writes to the replica to be missed, or can cause writes to fail completely.
 
-If there are fewer than `floor(replication factor / 2)` zones with failing replicas, reads and writes can withstand zone failures.
+A Grafana Mimir deployment should have at least `floor(replication factor / 2) + 1` healthy zones to operate.
 
 ## Unbalanced zones