aboutsummaryrefslogtreecommitdiffstats
path: root/doc/editcap.pod
diff options
context:
space:
mode:
authorChris Maynard <Christopher.Maynard@GTECH.COM>2010-11-09 03:20:15 +0000
committerChris Maynard <Christopher.Maynard@GTECH.COM>2010-11-09 03:20:15 +0000
commit86db02c22e6565c1691f1823ab04ab3978f1592c (patch)
tree0cd30534df1fd5ca7a5216b0251841ff1f120a9f /doc/editcap.pod
parentfae0f7d74ae6cc42c68f184850dd399294b40a42 (diff)
Fixed typos.
svn path=/trunk/; revision=34816
Diffstat (limited to 'doc/editcap.pod')
-rw-r--r--doc/editcap.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/editcap.pod b/doc/editcap.pod
index f2cb2f7e34..7dd5886592 100644
--- a/doc/editcap.pod
+++ b/doc/editcap.pod
@@ -105,7 +105,7 @@ to standard out. This verbose output (specifically the MD5 hash strings)
can be useful in scripts to identify duplicate packets across trace
files.
-The <dup window> is specifed as an integer value between 0 and 1000000 (inclusive).
+The <dup window> is specified as an integer value between 0 and 1000000 (inclusive).
NOTE: Specifying large <dup window> values with large tracefiles can
result in very long processing times for B<editcap>.
@@ -119,7 +119,7 @@ and the packet length and MD5 hash of the current packet are the same then
the packet to skipped. The duplicate comparison test stops when
the current packet's relative arrival time is greater than <dup time window>.
-The <dup time window> is specifed as I<seconds>[I<.fractional seconds>].
+The <dup time window> is specified as I<seconds>[I<.fractional seconds>].
The [.fractional seconds] component can be specified to nine (9) decimal
places (billionths of a second) but most typical trace files have resolution
@@ -134,7 +134,7 @@ removal option may not identify some duplicates.
=item -E E<lt>error probabilityE<gt>
-Sets the probabilty that bytes in the output file are randomly changed.
+Sets the probability that bytes in the output file are randomly changed.
B<Editcap> uses that probability (between 0.0 and 1.0 inclusive)
to apply errors to each data byte in the file. For instance, a
probability of 0.02 means that each byte has a 2% chance of having an error.