From: Zac Dover <zac.dover@proton.me>
Date: Tue, 13 Jun 2023 16:11:53 +0000 (+1000)
Subject: doc/rados: fix list in crush-map.rst
X-Git-Tag: v18.1.2~34^2
X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=dfa565e7f77b18aec74b6599f17a530dae0c69f8;p=ceph-ci.git

doc/rados: fix list in crush-map.rst

Correct the numbering and formatting of an ordered list in
doc/rados/operations/crush-map.rst.

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

diff --git a/doc/rados/operations/crush-map.rst b/doc/rados/operations/crush-map.rst
index 1f23fe9d992..083ac3d9493 100644
--- a/doc/rados/operations/crush-map.rst
+++ b/doc/rados/operations/crush-map.rst
@@ -292,22 +292,22 @@ pools) to achieve a balanced distribution.
 
 Ceph supports two types of weight sets:
 
- #. A **compat** weight set is a single alternative set of weights for each
-     device and each node in the cluster. Compat weight sets cannot be expected
-     to correct all anomalies (for example, PGs for different pools might be of
-     different sizes and have different load levels, but are mostly treated
-     alike by the balancer).  However, they have the major advantage of being
-     *backward compatible* with previous versions of Ceph. This means that even
-     though weight sets were first introduced in Luminous v12.2.z, older
-     clients (for example, Firefly) can still connect to the cluster when a
-     compat weight set is being used to balance data.
-
-  #. A **per-pool** weight set is more flexible in that it allows placement to
-     be optimized for each data pool. Additionally, weights can be adjusted
-     for each position of placement, allowing the optimizer to correct for a
-     subtle skew of data toward devices with small weights relative to their
-     peers (an effect that is usually apparent only in very large clusters
-     but that can cause balancing problems).
+#. A **compat** weight set is a single alternative set of weights for each
+   device and each node in the cluster. Compat weight sets cannot be expected
+   to correct all anomalies (for example, PGs for different pools might be of
+   different sizes and have different load levels, but are mostly treated alike
+   by the balancer).  However, they have the major advantage of being *backward
+   compatible* with previous versions of Ceph. This means that even though
+   weight sets were first introduced in Luminous v12.2.z, older clients (for
+   example, Firefly) can still connect to the cluster when a compat weight set
+   is being used to balance data.
+
+#. A **per-pool** weight set is more flexible in that it allows placement to
+   be optimized for each data pool. Additionally, weights can be adjusted
+   for each position of placement, allowing the optimizer to correct for a
+   subtle skew of data toward devices with small weights relative to their
+   peers (an effect that is usually apparent only in very large clusters
+   but that can cause balancing problems).
 
 When weight sets are in use, the weights associated with each node in the
 hierarchy are visible in a separate column (labeled either as ``(compat)`` or