blkparse: split off the timestamp correction code in to a separate function

[blktrace.git] / doc / btrecord.8

diff --git a/doc/btrecord.8 b/doc/btrecord.8
index b4318ae6f7c74c5c406b8ce72358486db117b511..dd92396f31a452a58b957b1cd63f875b92ced7ef 100644 (file)
--- a/doc/btrecord.8
+++ b/doc/btrecord.8
@@ -1,4 +1,4 @@
-.TH BTREPLAY 8 "December  8, 2007" "blktrace git\-20071207142532" ""
+.TH BTRECORD 8 "December  8, 2007" "blktrace git\-20071207142532" ""
 
 
 .SH NAME
@@ -105,16 +105,16 @@ Show help and exit.
 Show version number and exit.
 .RE
 
-\-m <\fInanoceconds\fR>
+\-m <\fInanoseconds\fR>
 .br
-\-\-input\-base=<\fInanoceconds\fR>
+\-\-max\-bunch\-time=<\fInanoseconds\fR>
 .RS
 The \fI\-m\fR option requires a single parameter which specifies an
 amount of time (in nanoseconds) to include in any one bunch of IOs that
 are to be processed. The smaller the value, the smaller the number of
 IOs processed at one time \(em perhaps yielding in more realistic replay.
 However, after a certain point the amount of overhead per bunch may result
-in additonal real replay time, thus yielding less accurate replay times.
+in additional real replay time, thus yielding less accurate replay times.
 .P
 The default value is 10,000,000 nanoseconds (10 milliseconds).
 .RE
@@ -167,7 +167,7 @@ sdab:3: 474773 pkts (tot), 117849 pkts (replay), 69572 bunches, 1.7 pkts/bunch
 .P
 The meaning of the columns is:
 .IP 1. 3
-  The first field contains the device name and CPU identrifer. Thus:
+  The first field contains the device name and CPU identifier. Thus:
   \fIsdab:0:\fR means the device \fIsdab\fR and traces on CPU 0. 
 .IP 2.
   The second field contains the total number of packets processed for each