LUDOC 299 protocol: Spell-check document

[doc/protocol.git] / struct_mdt_body.txt

diff --git a/struct_mdt_body.txt b/struct_mdt_body.txt
index 2e2cff0..59c7dd8 100644 (file)
--- a/struct_mdt_body.txt
+++ b/struct_mdt_body.txt
@@ -52,8 +52,12 @@ designate that resource and 'mbo_fid2' will be cleared.
 
 include::struct_lu_fid.txt[]
 
-The 'mbo_handle' field indicates the identity of an open file related
-to the operation, if any. If there is no lock then it is just 0.
+*Returning to the 'mdt_body' structure the remaining fields are as
+follows.*
+
+The 'mbo_handle' field indicates the identity of the previously
+acquired lock for an open file, if any, that is the subject of the
+operation. If there is no lock then it is just 0.
 
 The 'mbo_valid' field identifies which of the remaining fields are
 actually in force. The flags in 'mbo_valid' are:
@@ -80,8 +84,7 @@ actually in force. The flags in 'mbo_valid' are:
 
 Which flag is associated with which field is indicated in the comments
 beside the fields in the struct definition above. The fields without
-corresponding flags in the 'mbo_valid' field should be considered
-valid, though I'm not sure how much they actually get used.
+corresponding flags in the 'mbo_valid' field are also 'valid'.
 
 Many of the fields have names and meanings that correspond directly to
 those in 'struct mdt_rec_setattr' (ex. 'atime', 'size', 'mode',
@@ -106,7 +109,7 @@ which hold such information as the resource's layout.
 The 'mbo_aclsize' field indicates the size of the POSIX access control
 lists (ACLs) in bytes.
 
-The 'mbo_max_mdsize' field indicates the maximu size of the file layout,
+The 'mbo_max_mdsize' field indicates the maximum size of the file layout,
 as described in <<struct-lov-mds-md>>
 
 The 'mbo_max_cookiesize' field is unused since Lustre 2.4.  It