[[mgs-connect-rpc]]
The general behavior of MGS_CONNECT RPCs closely resembles that of
-OST_CONNECT RPCs (See <<ost-connect-rpc>>) and MDS_CONNECt RPCs. The
+OST_CONNECT RPCs (See <<ost-connect-rpc>>) and MDS_CONNECT RPCs. The
actual RPC's 'pb_opc' value will be different as are the names of the
targets and the specific values in the 'obd_connect_data' structure.
'client_uuid'::
A string with the client's own UUID. This is also a
<<struct-obd-uuid>>. The target sets the 'exp_client_uuid' field of
-its 'eport' structure to this value.
+its 'export' structure to this value.
'lustre_handle'::
See <<struct-lustre-handle>>. This 'lustre_handle' is distinct from
the 'pb_handle' field in the 'ptlrpc_body'. This 'lustre_handle'
-provied a unique 'cookie' to identify this client for this connection
+provides a unique 'cookie' to identify this client for this connection
attempt. After a disconnect, a subsequent connect RPC will have a
different value. The target preserves this cookie in the 'exp_handle'
field of its 'obd_export' structure for this client. In that way it