trace-cmd: Documentation - various spelling fixes.

Signed-off-by: John Kacur <jkacur@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

6 files changed, 12 insertions, 12 deletions

diff --git a/Documentation/trace-cmd-listen.txt b/Documentation/trace-cmd-listen.txt
index 981fb96..15014e6 100644
--- a/Documentation/trace-cmd-listen.txt
+++ b/Documentation/trace-cmd-listen.txt
@@ -20,7 +20,7 @@ PORT is the port that the remote host used to connect with.
 OPTIONS
 -------
 *-p* 'port'::
-    This option will specifies tha port to listen to.
+    This option will specify the port to listen to.
 
 *-D*::
     This options causes trace-cmd listen to go into a daemon mode and run in
@@ -30,7 +30,7 @@ OPTIONS
     This option specifies a directory to write the data files into.
 
 *-o* 'filename'::
-    This option overides the default 'trace' in the 'trace.HOST:PORT.dat' that
+    This option overrides the default 'trace' in the 'trace.HOST:PORT.dat' that
     is created when a remote host connects.
 
 
diff --git a/Documentation/trace-cmd-record.txt b/Documentation/trace-cmd-record.txt
index 9f43d6d..4707605 100644
--- a/Documentation/trace-cmd-record.txt
+++ b/Documentation/trace-cmd-record.txt
@@ -37,7 +37,7 @@ OPTIONS
     the Linux kernel. They are grouped by subsystem where you can enable all
     events of a given subsystem or specify specific events to be enabled. The
     'event' is of the format "subsystem:event-name". You can also just specify
-    the subsystem without the ':event-name' or the eventname without the
+    the subsystem without the ':event-name' or the event-name without the
     "subsystem:". Using "-e sched_switch" will enable the "sched_switch" event
     where as, "-e sched" will enable all events under the "sched" subsystem.
 
@@ -51,7 +51,7 @@ OPTIONS
     Specify a filter for the previous event. This must come after a *-e*. This
     will filter what events get recorded based on the content of the event.
     Filtering is passed to the kernel directly so what filtering is allowed
-    may depend on what verison of the kernel you have. Basically, it will
+    may depend on what version of the kernel you have. Basically, it will
     let you use C notation to check if an event should be processed or not.
 
 ----------------------------------------
diff --git a/Documentation/trace-cmd-report.txt b/Documentation/trace-cmd-report.txt
index 028f2ca..f3f6e88 100644
--- a/Documentation/trace-cmd-report.txt
+++ b/Documentation/trace-cmd-report.txt
@@ -17,7 +17,7 @@ created by trace-cmd record.
 OPTIONS
 -------
 *-i* 'input-file'::
-    By default, trace-cmd report willl read the file 'trace.dat'. But the *-i*
+    By default, trace-cmd report will read the file 'trace.dat'. But the *-i*
     option open up the given 'input-file' instead. Note, the input file may
     also be specified as the last item on the command line.
 
@@ -126,7 +126,7 @@ OPTIONS
     that interrupts were disabled. The 'h' means that this was called inside
     an interrupt handler. The '1' is the preemption disabled (preempt_count)
     was set to one.  The two '.'s are "need_resched" flag and kernel lock
-    counter.  If the "need_resched" flag is set, then that charater would be a
+    counter.  If the "need_resched" flag is set, then that character would be a
     'N'.
 
 *-w*::
@@ -263,7 +263,7 @@ Average wakeup latency: 110.021 usecs
 The above version will only show the wakeups and context switches of Real Time
 tasks. The 'prio' used inside the kernel starts at 0 for highest priority.
 That is 'prio' 0 is equivalent to user space real time priority 99, and
-priority 98 is quivalent to user space real time priority 1.
+priority 98 is equivalent to user space real time priority 1.
 Prios less than 100 represent Real Time tasks.
 
 
diff --git a/Documentation/trace-cmd-reset.txt b/Documentation/trace-cmd-reset.txt
index 0473e1d..d579827 100644
--- a/Documentation/trace-cmd-reset.txt
+++ b/Documentation/trace-cmd-reset.txt
@@ -16,14 +16,14 @@ bring back the performance of the system before tracing was enabled. This is
 necessary since 'trace-cmd-record(1)', 'trace-cmd-stop(1)' and
 'trace-cmd-extract(1)' do not disable the tracer, event after the data has
 been pulled from the buffers. The rational is that the user may want to
-manually enable the tracer with the Ftrace pseudo file sytem, or examine other
+manually enable the tracer with the Ftrace pseudo file system, or examine other
 parts of Ftrace to see what trace-cmd did. After the reset command happens,
 the data in the ring buffer, and the options that were used are all lost.
 
 OPTIONS
 -------
 *-b* 'buffer_size'::
-    When the kernel boots, the Ftrace ring buffer is of a miminal size (3
+    When the kernel boots, the Ftrace ring buffer is of a minimal size (3
     pages per CPU). The first time the tracer is used, the ring buffer size
     expands to what it was set for (default 1.4 Megs per CPU).
 
diff --git a/Documentation/trace-cmd-split.txt b/Documentation/trace-cmd-split.txt
index 43d6df3..d061f39 100644
--- a/Documentation/trace-cmd-split.txt
+++ b/Documentation/trace-cmd-split.txt
@@ -20,7 +20,7 @@ end-time is needed, use 0.0 as the start-time.
 
 If start-time is left out, then the split will start at the beginning of the
 file. If end-time is left out, then split will continue to the end unless it
-meets one of the reqirements specified by the options.
+meets one of the requirements specified by the options.
 
 OPTIONS
 -------
@@ -66,7 +66,7 @@ OPTIONS
 
     trace-cmd split -r -e 10000
 
-    This will break up trace.dat into serval smaller files, each with at most
+    This will break up trace.dat into several smaller files, each with at most
     10,000 events in it.
 
 *-c*::
diff --git a/Documentation/trace-cmd.txt b/Documentation/trace-cmd.txt
index 6a02cbe..9bd97c5 100644
--- a/Documentation/trace-cmd.txt
+++ b/Documentation/trace-cmd.txt
@@ -12,7 +12,7 @@ SYNOPSIS
 DESCRIPTION
 -----------
 The trace-cmd(1) command interacts with the Ftrace tracer that is built inside
-the Linux kernel. It intefaces with the Ftrace specific files found in the
+the Linux kernel. It interfaces with the Ftrace specific files found in the
 debugfs file system under the tracing directory. A 'COMMAND' must be
 specified to tell trace-cmd what to do.