types of layouts for different files, either 'lov_mds_md_v1' or
'lov_mds_md_v3' as of Lustre 2.7, though they are very similar in
structure. In an intent request (as opposed to a reply and as yet
-unimplemanted) it will modify the layout. It will not be included
+unimplemented) it will modify the layout. It will not be included
(zero length) in requests in current releases.
[source,c]
that there is a hole (missing object) within the layout, which is normally
caused by corruption or loss of the file layout that had to be rebuilt
by LFSCK. LOV_PATTERN_F_RELEASED is used by HSM to indicate that the
-file data is not resident in the filesystem, but rather in an external
+file data is not resident in the file system, but rather in an external
archive, so the layout is only a stub that describes the layout to use
when the file is restored.
The 'lmm_stripe_count' field gives how many OST objects the file is striped
over.
-The 'lmm_layout_gen' field is updated as the layout of the obeject is
+The 'lmm_layout_gen' field is updated as the layout of the Object is
updated. If the 'lmm_layout_gen' is modified, then clients can detect
the layout has changed when refreshing the layout after having lost the
layout lock.