Skip to content

Commit c8b4155

Browse files
committed
doc/rados: standardize markup of "clean"
Standardize the markup around the status "clean" in the documentation so that readers don't mistakenly get the idea that inconsistent presentation of the word "clean" implies a never-stated difference between one instance and the other. Signed-off-by: Zac Dover <[email protected]>
1 parent f2a7ed4 commit c8b4155

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/rados/operations/health-checks.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1502,10 +1502,10 @@ This health check is raised if a certain percentage (determined by
15021502
:confval:`mon_warn_pg_not_deep_scrubbed_ratio`) of the interval has elapsed
15031503
after the time the scrub was scheduled and no scrub has been performed.
15041504

1505-
PGs will receive a deep scrub only if they are flagged as *clean* (which means
1506-
that they are to be cleaned, and not that they have been examined and found to
1507-
be clean). Misplaced or degraded PGs might not be flagged as ``clean`` (see
1508-
*PG_AVAILABILITY* and *PG_DEGRADED* above).
1505+
PGs will receive a deep scrub only if they are flagged as ``clean`` (which
1506+
means that they are to be cleaned, and not that they have been examined and
1507+
found to be clean). Misplaced or degraded PGs might not be flagged as ``clean``
1508+
(see *PG_AVAILABILITY* and *PG_DEGRADED* above).
15091509

15101510
This document offers two methods of setting the value of
15111511
:confval:`osd_deep_scrub_interval`. The first method listed here changes the

0 commit comments

Comments
 (0)