LUDOC-298 protocl: Editorial pass through the document.

[doc/protocol.git] / struct_lu_fid.txt

diff --git a/struct_lu_fid.txt b/struct_lu_fid.txt
index c4c7b3e..2b3a3d9 100644 (file)
--- a/struct_lu_fid.txt
+++ b/struct_lu_fid.txt
@@ -14,16 +14,16 @@ struct lu_fid {
 A file identifier ('FID') is a 128-bit number that uniquely identifies a
 resource on an MDT or OST. The FID for the resource on an MDT
 identifies the file as a whole. The FID for a resource on an OST
-identifiess the fragment of a file assigned to that OST.
+identifies the fragment of a file assigned to that OST.
 
-The 'f_seq' field holds the sequence number, or SEQ, and is used in
-conjunction with the 'FID location database' (FLDB) to
-determine on which target the resource is located.  All resources with the
-same 'f_seq' value will be on the same target. A target can have more
-than one 'f_seq' value assigned to it.
+The 'f_seq' field holds the sequence number, or SEQ (see below), and
+is used in conjunction with the 'FID location database' (FLDB) to
+determine on which target the resource is located.  All resources with
+the same 'f_seq' value will be on the same target. A target can have
+more than one 'f_seq' value assigned to it.
 
-The 'f_oid' field holds the unique 'object identifier' (OID) within the
-sequence to identify a particular object.
+The 'f_oid' field holds the unique 'object identifier' (OID) to
+identify a particular object.
 
 The 'f_ver' value identifies which version of a resource is being
 identified in the event that the resource is being updated, and
@@ -63,9 +63,10 @@ enum fid_seq {
 ----
 
 ****
-There are several reserved ranges of FID sequence values, to allow for
-interoperability with older Lustre filesystems, to identify "well known"
-objects for internal or external use, as well as for future expansion.
+There are several reserved ranges of FID sequence values
+(summarized in the list above), to allow for interoperability with
+older Lustre filesystems, to identify "well known" objects for
+internal or external use, as well as for future expansion.
 
 The 'FID_SEQ_OST_MDT0' (0x0) range is reserved for OST objects created
 by MDT0 in non-DNE filesystems.  Since all such OST objects used an
@@ -83,8 +84,8 @@ testing purposes such as obdfiler-survey.
 The 'FID_SEQ_LLOG_NAME' (0x10) range is used for named llog files such
 as configuration logs and the ChangeLog.
 
-The 'FID_SEQ_IGIF' (0xb-0xffffffff) range is reserved for 'inode and
-generation in FID' (IGIF) inodes allocated by MDSes before Lustre 2.0.
+The 'FID_SEQ_IGIF' (0xb-0xffffffff) range is reserved for 'inode
+generation in FID' (IGIF) inodes allocated by MDSs before Lustre 2.0.
 This corresponds to the 4 billion maximum inode number that could be
 allocated for such filesystems.  The 'f_oid' field for IGIF FIDs
 contains the inode version number, and as such there is normally only