spelling fix

2 files changed, 6 insertions, 6 deletions

diff --git a/doc/tracing.html b/doc/tracing.html
index 55d0085..4c15c20 100644
--- a/doc/tracing.html
+++ b/doc/tracing.html
@@ -158,11 +158,11 @@ Used to measure the time spent to enqueue a newly-released job in a ready queue.
 
 <h2>Recording and Post-Processing Scheduling Traces</h2>
 
-<p>Scheduling traces are also recorded using Feather-Trace. However, a different binary format is being used. The definition and an explanation of the format can be found in the file <code>include/litmus/sched_trace.h</code> (in the kernel directory).</p>
+<p>Scheduling traces are also recorded using Feather-Trace. However, a different binary format is used. The definition and an explanation of the format can be found in the file <code>include/litmus/sched_trace.h</code> (in the kernel directory).</p>
 
 <p>Since <code>sched_trace</code> uses per-processor buffers several <code>ftcat</code> instances have to be launched. The <code>ft_tools</code> package includes a wrapper script called <code>st_trace</code> that automates this setup procedure. Note that one may have to modify <code>st_trace</code> to change the default location of the <code>sched_trace</code> device files. <code>st_trace</code> accepts a tag as the only argument. The tag is used to assign a unique name to the trace files.</p>
 
-<p>The following example illustrates how a <code>st_trace</code> is used with the tag <code>global-exp</code>.</p>
+<p>The following example illustrates how <code>st_trace</code> is used with the tag <code>global-exp</code>.</p>
 
 <pre><code>$ st_trace global-exp
 CPU 0: 8204 &gt; st-global-exp-0.bin [0]
@@ -181,7 +181,7 @@ Disabling 9 events.
 /home/litmus/log3: 1234 bytes read.
 </code></pre>
 
-<p>Note that <code>st_trace</code> may have to modified to change the default <code>sched_trace</code> device locations.</p>
+<p>Note that <code>st_trace</code> may have to be modified to change the default <code>sched_trace</code> device locations.</p>
 
 <p><strong>Hint</strong>: The dummy real-time task <code>rtspin</code> (distributed as part of the <code>liblitmus</code> package) may be useful when studying/testing the behavior of a scheduler plugin.</p>
 
diff --git a/doc/tracing.text b/doc/tracing.text
index f31cb39..0e3c7b9 100644
--- a/doc/tracing.text
+++ b/doc/tracing.text
@@ -145,11 +145,11 @@ Once the recorded overheads have been exported to CSV files they can be easily a
 Recording and Post-Processing Scheduling Traces
 -----------------------------------------------
 
-Scheduling traces are also recorded using Feather-Trace. However, a different binary format is being used. The definition and an explanation of the format can be found in the file `include/litmus/sched_trace.h` (in the kernel directory).
+Scheduling traces are also recorded using Feather-Trace. However, a different binary format is used. The definition and an explanation of the format can be found in the file `include/litmus/sched_trace.h` (in the kernel directory).
 
 Since `sched_trace` uses per-processor buffers several `ftcat` instances have to be launched. The `ft_tools` package includes a wrapper script called `st_trace` that automates this setup procedure. Note that one may have to modify `st_trace` to change the default location of the `sched_trace` device files. `st_trace` accepts a tag as the only argument. The tag is used to assign a unique name to the trace files.
 
-The following example illustrates how a `st_trace` is used with the tag `global-exp`.
+The following example illustrates how `st_trace` is used with the tag `global-exp`.
 
         $ st_trace global-exp
         CPU 0: 8204 > st-global-exp-0.bin [0]
@@ -167,7 +167,7 @@ The following example illustrates how a `st_trace` is used with the tag `global-
         /home/litmus/log2: 1234 bytes read.
         /home/litmus/log3: 1234 bytes read.
 
-Note that `st_trace` may have to modified to change the default `sched_trace` device locations.
+Note that `st_trace` may have to be modified to change the default `sched_trace` device locations.
 
 **Hint**: The dummy real-time task `rtspin` (distributed as part of the `liblitmus` package) may be useful when studying/testing the behavior of a scheduler plugin.