doc: minor formatting fixes

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index e7142c57b03df0e6f500b35ad95cf712d4c20617..83583028ae70ffdd330e26f82e42860d17a72e0b 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -1815,9 +1815,9 @@ I/O engine
                        details of writing an external I/O engine.
 
                **filecreate**
-                       Simply create the files and do no IO to them.  You still need to
+                       Simply create the files and do no I/O to them.  You still need to
                        set  `filesize` so that all the accounting still occurs, but no
-                       actual IO will be done other than creating the file.
+                       actual I/O will be done other than creating the file.
 
 I/O engine specific parameters
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -2060,7 +2060,7 @@ I/O depth
        changing data and the overlapping region has a non-zero size. Setting
        ``serialize_overlap`` tells fio to avoid provoking this behavior by explicitly
        serializing in-flight I/Os that have a non-zero overlap. Note that setting
-       this option can reduce both performance and the `:option:iodepth` achieved.
+       this option can reduce both performance and the :option:`iodepth` achieved.
        Additionally this option does not work when :option:`io_submit_mode` is set to
        offload. Default: false.
 
@@ -2888,7 +2888,7 @@ Measurements and reporting
 
 .. option:: lat_percentiles=bool
 
-       Enable the reporting of percentiles of IO latencies. This is similar
+       Enable the reporting of percentiles of I/O latencies. This is similar
        to :option:`clat_percentiles`, except that this includes the
        submission latency. This option is mutually exclusive with
        :option:`clat_percentiles`.
@@ -3258,7 +3258,7 @@ writes in the example above).  In the order listed, they denote:
                short or dropped.
 
 **IO latency**
-               These values are for `--latency-target` and related options. When
+               These values are for :option:`latency_target` and related options. When
                these options are engaged, this section describes the I/O depth required
                to meet the specified latency target.