LUDOC-296 protocol: Reorganize the document ot be top-down

[doc/protocol.git] / statfs.txt

diff --git a/statfs.txt b/statfs.txt
index 3d86ac8..a11f231 100644 (file)
--- a/statfs.txt
+++ b/statfs.txt
@@ -73,7 +73,7 @@ Step Client         MDT          OST
 4             <------OST_STATFS
 //////////////////////////////////////////////////////////////////////
 
-1 - The client issues an MDS_STATFS request to each MDT.
+*1 - The client issues an MDS_STATFS request to each MDT.*
 
 The MDS_STATFS request is a so-called 'empty' RPC in that it consists
 only of the 'ptlrpc_body' (Lustre RPC descriptor) with the opcode set to
@@ -94,7 +94,7 @@ messages.
 !===================
 |====
 
-2 - The MDS_STATFS reply returns 'statfs' info
+*2 - The MDS_STATFS reply returns 'statfs' info*
 
 In addition to the 'ptlrpc_body' (Lustre RPC descriptor), the
 MDS_STATFS reply to the client has the 'obd_statfs' structure. For a
@@ -114,7 +114,7 @@ detailed discussion of the fields in the 'obd_statfs' refer to
 !===================
 |====
 
-3 - The client issues an OST_STATFS request to each OST.
+*3 - The client issues an OST_STATFS request to each OST.*
 
 The OST_STATFS RPC looks just like the MDS_STATFS, except the opcode
 is 13 instead of 41 and the target of the RPC is an OST instead of an
@@ -134,7 +134,7 @@ MDT.
 |====
 
 
-4 - The OST_STATFS reply returns 'statfs' info
+*4 - The OST_STATFS reply returns 'statfs' info*
 
 In addition to the 'ptlrpc_body' (Lustre RPC descriptor), the OST_STATFS
 reply to the client has the 'obd_statfs' structure. For a detailed