[PATCH] HOWTO: typo: write_log_log -> write_lat_log + use suffix

[Lucian Adrian Grijincu <lucian@xxxxxx>]

- I guess 'write_log_log' was a copy-pasta typo.

- You used 'suffix' everywhere except for two places where you said
  'postfix'.
---
 HOWTO |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/HOWTO b/HOWTO
index 73e8265..92ce05d 100644
--- a/HOWTO
+++ b/HOWTO
@@ -320,7 +320,7 @@ rw=str		Type of io pattern. Accepted values are:
 		one by appending a ':<nr>' to the end of the string given.
 		For a random read, it would look like 'rw=randread:8' for
 		passing in an offset modifier with a value of 8. If the
-		postfix is used with a sequential IO pattern, then the value
+		suffix is used with a sequential IO pattern, then the value
 		specified will be added to the generated offset for each IO.
 		For instance, using rw=write:4k will skip 4k for every
 		write. It turns sequential IO into sequential IO with holes.
@@ -1107,8 +1107,8 @@ write_bw_log=str If given, write a bandwidth log of the jobs in this job
 		file. Can be used to store data of the bandwidth of the
 		jobs in their lifetime. The included fio_generate_plots
 		script uses gnuplot to turn these text files into nice
-		graphs. See write_log_log for behaviour of given
-		filename. For this option, the postfix is _bw.log.
+		graphs. See write_lat_log for behaviour of given
+		filename. For this option, the suffix is _bw.log.
 
 write_lat_log=str Same as write_bw_log, except that this option stores io
 		submission, completion, and total latencies instead. If no
-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html