doc/internals/osd_internals: fix indentation errors

Signed-off-by: Samuel Just <sam.just@inktank.com>

diff --git a/doc/internals/osd_internals/map_message_handling.rst b/doc/internals/osd_internals/map_message_handling.rst
index 60ffd0df38baebfa179401ca936f3475f15d91d3..16e045ff0e7bd5a735030854e1138ad6183bbb5a 100644 (file)
--- a/doc/internals/osd_internals/map_message_handling.rst
+++ b/doc/internals/osd_internals/map_message_handling.rst
@@ -60,8 +60,8 @@ messages.  That is, messages from different PGs may be reordered.
 
 MOSDPGOps follow the following process:
   1. OSD::handle_op: validates permissions and crush mapping.
-          See OSDService::handle_misdirected_op
-          See OSD::op_has_sufficient_caps
+     See OSDService::handle_misdirected_op
+     See OSD::op_has_sufficient_caps
            See OSD::require_same_or_newer_map
   2. OSD::enqueue_op
 
@@ -82,12 +82,12 @@ In summary, the possible ways that an op may wait or be discarded in are:
      OSD::handle_*.
   2. Discarded in OSD::can_discard_op at enqueue_op.
   3. Wait in PG::op_waiters due to PG::must_delay_request in PG::do_request.
-       4. Wait in PG::waiting_for_active in due_request due to !flushed.
+  4. Wait in PG::waiting_for_active in due_request due to !flushed.
   5. Wait in PG::waiting_for_active due to !active() in do_op/do_sub_op.
   6. Wait in PG::waiting_for_(degraded|missing) in do_op.
   7. Wait in PG::waiting_for_active due to scrub_block_writes in do_op
 
-TODO: The above is not a complete list.        
+TODO: The above is not a complete list.
 
 Peering Messages
 ----------------

diff --git a/doc/internals/osd_internals/osd_overview.rst b/doc/internals/osd_internals/osd_overview.rst
index 5eb5fd71b78014cd238cd801186866997768e392..8df946118eba67e3d6e090e73f68b88a74bb124b 100644 (file)
--- a/doc/internals/osd_internals/osd_overview.rst
+++ b/doc/internals/osd_internals/osd_overview.rst
@@ -8,10 +8,10 @@ Concepts
 *Messenger*
    See src/msg/Messenger.h
 
-        Handles sending and receipt of messages on behalf of the OSD.  The OSD uses
-        two messengers: 
-          1. cluster_messenger - handles traffic to other OSDs, monitors
-           2. client_messenger - handles client traffic
+   Handles sending and receipt of messages on behalf of the OSD.  The OSD uses
+   two messengers: 
+     1. cluster_messenger - handles traffic to other OSDs, monitors
+     2. client_messenger - handles client traffic
 
         This division allows the OSD to be configured with different interfaces for
         client and cluster traffic.