doc/dev/osd_internals: fix sphinx warnings

silences errors like

erasure_coding/proposals.rst:236: ERROR: Unexpected indentation.

Signed-off-by: Kefu Chai <kchai@redhat.com>

diff --git a/doc/dev/osd_internals/erasure_coding/proposals.rst b/doc/dev/osd_internals/erasure_coding/proposals.rst
index d557cc8a4da7c40d0045d8e3757d136981caff12..e068f0d2d1dd9b2691183c2378db79057959c36f 100644 (file)
--- a/doc/dev/osd_internals/erasure_coding/proposals.rst
+++ b/doc/dev/osd_internals/erasure_coding/proposals.rst
@@ -232,17 +232,16 @@ new object_info and log_entry.
 A truly terrifying option would be to eliminate version and
 prior_version entirely from the object_info_t.  There are a few
 specific purposes it serves:
-(1) On OSD startup, we prime the missing set by scanning backwards
-               from last_update to last_complete comparing the stored object's
-               object_info_t to the version of most recent log entry.
-(2) During backfill, we compare versions between primary and target
-               to avoid some pushes.
-
-We use it elsewhere as well
-(3) While pushing and pulling objects, we verify the version.
-(4) We return it on reads and writes and allow the librados user to
-               assert it atomically on writesto allow the user to deal with write
-               races (used extensively by rbd).
+
+#. On OSD startup, we prime the missing set by scanning backwards
+   from last_update to last_complete comparing the stored object's
+   object_info_t to the version of most recent log entry.
+#. During backfill, we compare versions between primary and target
+   to avoid some pushes. We use it elsewhere as well
+#. While pushing and pulling objects, we verify the version.
+#. We return it on reads and writes and allow the librados user to
+   assert it atomically on writesto allow the user to deal with write
+   races (used extensively by rbd).
 
 Case (3) isn't actually essential, just convenient.  Oh well.  (4)
 is more annoying. Writes are easy since we know the version.  Reads