doc/crimson/seastore: make code snippets in a text block

Signed-off-by: chunmei liu <chunmei.liu@ibm.com>

diff --git a/doc/dev/crimson/seastore.rst b/doc/dev/crimson/seastore.rst
index 91b29624cca399b7ebaf1669e90e38d7071f2004..c1dc9691f952a649bc4530dc6143ab5c21ec4dcc 100644 (file)
--- a/doc/dev/crimson/seastore.rst
+++ b/doc/dev/crimson/seastore.rst
@@ -707,7 +707,7 @@ With MultiShardStores, the number of OSD shards could be changed also after mkfs
 Each reactor thread can host multiple store shards. Alternatively, few reactors threads could now share the same store shard. Store shards can forward their I/O requests to another store shard running on a different reactor thread.
 
 For example, for an OSD that had 3 reactor threads (seastar::smp::count: 3) set during mkfs.
-After changing the reactor thread count to 5 and restarting the cluster, the mounted store shards will look like:
+After changing the reactor thread count to 5 and restarting the cluster, the mounted store shards will look like::
 
   Reactors thread 0 -> Store Shard: 0
   Reactors thread 1 -> Store Shard: 1
@@ -715,12 +715,14 @@ After changing the reactor thread count to 5 and restarting the cluster, the mou
   Reactors thread 3 -> Store Shard: 0 (forwarded)
   Reactors thread 4 -> Store Shard: 1 (forwarded)
 
-When changing to seastar::smp::count: 2:
+When changing to seastar::smp::count: 2::
+
   Reactors thread 0 -> Store Shard: 0, 2
   Reactors thread 1 -> Store Shard: 1
 
 using ./bin/ceph daemon osd.0 dump_store_shards to check store assignment.
 See the following example outputs from running dump_store_shards with the above scenarios:
+
 **first start with 3 reactors**::
 
   ./bin/ceph daemon osd.0 dump_store_shards