From feecb973ba397059920b6e84070cfb06b0f40f74 Mon Sep 17 00:00:00 2001
From: RituDSML <102390285+RituDSML@users.noreply.github.com>
Date: Mon, 26 Jan 2026 17:05:17 +0400
Subject: [PATCH] DOC: fix write_empty_chunks default claim

---
 docs/user-guide/performance.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user-guide/performance.md b/docs/user-guide/performance.md
index a2e986a1b8..ff9fd74c2a 100644
--- a/docs/user-guide/performance.md
+++ b/docs/user-guide/performance.md
@@ -125,7 +125,7 @@ This optimization prevents storing redundant objects and can speed up reads, but
 added computation during array writes, since the contents of
 each chunk must be compared to the fill value, and these advantages are contingent on the content of the array.
 If you know that your data will form chunks that are almost always non-empty, then there is no advantage to the optimization described above.
-In this case, creating an array with `write_empty_chunks=True` (the default) will instruct Zarr to write every chunk without checking for emptiness.
+In this case, creating an array with `write_empty_chunks=True`will instruct Zarr to write every chunk without checking for emptiness.
 
 The following example illustrates the effect of the `write_empty_chunks` flag on
 the time required to write an array with different values.: