Update about-grafana-mimir-architecture (#7234)

grafana · Jan 31, 2024 · 3bb7b7f · 3bb7b7f
1 parent 57cb013
commit 3bb7b7f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/sources/mimir/get-started/about-grafana-mimir-architecture/index.md b/docs/sources/mimir/get-started/about-grafana-mimir-architecture/index.md
@@ -44,7 +44,7 @@ This gives [queriers]({{< relref "../../references/architecture/components/queri
 To effectively use the WAL, and to be able to recover the in-memory series if an ingester abruptly terminates, store the WAL to a persistent disk that can survive an ingester failure.
 For example, when running in the cloud, include an AWS EBS volume or a GCP persistent disk.
 If you are running the Grafana Mimir cluster in Kubernetes, you can use a StatefulSet with a persistent volume claim for the ingesters.
-The location on the filesystem where the WAL is stored is the same location where local TSDB blocks (compacted from head) are stored. The location of the filesystem and the location of the local TSDB blocks cannot be decoupled.
+The location on the filesystem where the WAL is stored is the same location where local TSDB blocks (compacted from head) are stored. The locations of the WAL and the local TSDB blocks cannot be decoupled.
 
 For more information, refer to [timeline of block uploads]({{< relref "../../manage/run-production-environment/production-tips#how-to-estimate--querierquery-store-after" >}}) and [Ingester]({{< relref "../../references/architecture/components/ingester" >}}).