From: Zac Dover <zac.dover@proton.me>
Date: Sun, 25 May 2025 23:05:20 +0000 (+1000)
Subject: doc/rados: s/enpty/empty/ in pgcalc doc
X-Git-Tag: v20.1.0~276^2
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=a3f022dc93a1cb29ca160c09c5240069e3a56042;p=ceph.git

doc/rados: s/enpty/empty/ in pgcalc doc

s/enpty/empty/ in doc/rados/operations/pgcalc/index.rst.

Signed-off-by: Zac Dover <zac.dover@proton.me>
(cherry picked from commit 50dc9f1a04c13faa3d5e7971ec7f0724ddf70709)
---

diff --git a/doc/rados/operations/pgcalc/index.rst b/doc/rados/operations/pgcalc/index.rst
index 1aed873914a0..b803b657a152 100644
--- a/doc/rados/operations/pgcalc/index.rst
+++ b/doc/rados/operations/pgcalc/index.rst
@@ -57,7 +57,7 @@ PG Calc
                         </ol>
                         <b>Objective</b>
                         <ul><li>The objective of this calculation and the target ranges noted in the &quot;Key&quot; section above are to ensure that there are sufficient Placement Groups for even data distribution throughout the cluster, while not going high enough on the PG per OSD ratio to cause problems during Recovery and/or Backfill operations.</li></ul>
-                        <b>Effects of enpty or non-active pools:</b>
+                        <b>Effects of empty or non-active pools:</b>
                         <ul>
                                 <li>Empty or otherwise non-active pools should not be considered helpful toward even data distribution throughout the cluster.</li>
                                 <li>However, the PGs associated with these empty / non-active pools still consume memory and CPU overhead.</li>