LUDOC 299 protocol: Spell-check document

[doc/protocol.git] / struct_obd_statfs.txt

diff --git a/struct_obd_statfs.txt b/struct_obd_statfs.txt
index 13f9945..2282668 100644 (file)
--- a/struct_obd_statfs.txt
+++ b/struct_obd_statfs.txt
@@ -52,9 +52,9 @@ units of os_bsize.
 The 'os_bfree' field is the number of blocks not currently in use.
 
 The 'os_bavail' is the number of blocks available to be allocated to
-new files.  The number of available blocks is typically lower than
-the number of free blocks due to <<grant>> and blocks reserved for
-target internal usage such as metadata.
+new files.  The number of available blocks is typically lower than the
+number of free blocks due to outstanding "grants" (see <<grant>>) and
+blocks reserved for target internal usage such as metadata.
 
 The 'os_files' field is the total number of files on the target, both
 allocated and free.  For some OSD types this is a static number, and
@@ -97,10 +97,9 @@ In normal operation the 'os_state' value is returned as 0x0.  If the
 OSD has a RAID configuration that is degraded or
 rebuilding the state is returned with the OS_STATE_DEGRADED (0x1) flag
 set. If the file system has been set to read-only, either manually at
-mount or automatcially due to detected corruption of the underlying
-target filesystem, then 'os_state' is returned with OS_STATE_READONLY (0x2)
-set, for example if it was explicitly mounted read-only, or
-corruption has been detected at runtime in the backing filesystem.
+mount or automatically due to detected corruption of the underlying
+target file system, then 'os_state' is returned with OS_STATE_READONLY (0x2)
+set.
 
 The 'os_fprecreated' field counts the number of pre-created objects
 available on an OST. The 'os_fprecreated' value counts as "used"