eta: ensure we include terminating 0 space in je->run_str[]

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index b823eaed24a5b84b30bbf2d19ab5f4ef9f089ae0..b61a638907334bdc7d8f84e77d2a23d979d69c54 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -198,7 +198,7 @@ sections.
 -------------------------
 
 fio also supports environment variable expansion in job files. Any
 -------------------------
 
 fio also supports environment variable expansion in job files. Any

-substring of the form "${VARNAME}" as part of an option value (in other
+sub-string of the form "${VARNAME}" as part of an option value (in other

 words, on the right of the `='), will be expanded to the value of the
 environment variable called VARNAME.  If no such environment variable
 is defined, or VARNAME is the empty string, the empty string will be
 words, on the right of the `='), will be expanded to the value of the
 environment variable called VARNAME.  If no such environment variable
 is defined, or VARNAME is the empty string, the empty string will be


@@ -875,8 +875,8 @@ fsync=int   If writing to a file, issue a sync of the dirty data
 
 fdatasync=int  Like fsync= but uses fdatasync() to only sync data and not
                metadata blocks.
 
 fdatasync=int  Like fsync= but uses fdatasync() to only sync data and not
                metadata blocks.

-               In FreeBSD and Windows there is no fdatasync(), this falls back to
-               using fsync()
+               In FreeBSD and Windows there is no fdatasync(), this falls back
+               to using fsync()

 
 sync_file_range=str:val        Use sync_file_range() for every 'val' number of
                write operations. Fio will track range of writes that
 
 sync_file_range=str:val        Use sync_file_range() for every 'val' number of
                write operations. Fio will track range of writes that