LUDOC 299 protocol: Spell-check document

[doc/protocol.git] / struct_ptlrpc_body.txt

diff --git a/struct_ptlrpc_body.txt b/struct_ptlrpc_body.txt
index eecb189..cc73ee9 100644 (file)
--- a/struct_ptlrpc_body.txt
+++ b/struct_ptlrpc_body.txt
@@ -54,7 +54,7 @@ will use that 'lustre_handle' (the 'pb_handle' field will be set to
 that value) to to gain access to their shared state. In subsequent RPC
 reply messages (after the *_CONNECT reply) the 'pb_handle' field is
 0. The 'lustre_handle' is persistent across client reconnects to the
-same instance of the server, but if the client unmounts the filesystem
+same instance of the server, but if the client unmounts the file system
 or is evicted then it must re-connect as a new client, with a new
 'lustre_handle'.
 
@@ -266,7 +266,7 @@ and the value for each operation.
 | UPDATE_OBJ                             | 1000
 |====
 
-The 'pb_status' field was already mentioned above in conjuction with
+The 'pb_status' field was already mentioned above in conjunction with
 the 'pb_type' field in replies.  In a request message 'pb_status' is
 set to the 'pid' of the process making the request. In a reply
 message, a zero indicates that the service successfully initiated the
@@ -294,7 +294,7 @@ to operations that do modify the file system it is the target-unique,
 server-assigned transaction number for the client request.  See
 <<transno>>. Upon receipt of the reply, the client copies this
 transaction number from 'pb_transno' of the reply to 'pb_transno' of
-the saved request.  If 'pb_transno' is larger than 'pb_last_commited'
+the saved request.  If 'pb_transno' is larger than 'pb_last_committed'
 (above) then the request has been processed at the target but is not
 yet committed to stable storage.  The client must save the request for
 later resend to the server in case the target fails before the