doc: minor formatting fixes

- Fix broken HOWTO formatting in serialize_overlap.
- Make a link to (and correct the name of) latency_target option within
  Interpreting the output, IO latency.

Signed-off-by: Sitsofe Wheeler <sitsofe@yahoo.com>

2 files changed, 3 insertions, 3 deletions

diff --git a/HOWTO b/HOWTO
index 72f972c7..83583028 100644
--- a/HOWTO
+++ b/HOWTO
@@ -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.
 
@@ -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.
 
diff --git a/fio.1 b/fio.1
index 787b596c..023d6efc 100644
--- a/fio.1
+++ b/fio.1
@@ -2916,7 +2916,7 @@ The number of \fBread/write/trim\fR requests issued, and how many of them were
 short or dropped.
 .TP
 .B IO latency
-These values are for \fBlatency-target\fR and related options. When
+These values are for \fBlatency_target\fR and related options. When
 these options are engaged, this section describes the I/O depth required
 to meet the specified latency target.
 .RE