two minor word tweaks to the tracing doc

2 files changed, 4 insertions, 4 deletions

diff --git a/doc/tracing.html b/doc/tracing.html
index fae0bd2..8640d3f 100644
--- a/doc/tracing.html
+++ b/doc/tracing.html
@@ -88,7 +88,7 @@ done
 <pre><code>sort -n my_debug_log &gt; my_sorted_debug_log
 </code></pre>
 
-<p><strong>Hint</strong>: One can use <code>netcat(1)</code> to send the debug messages to another machine via UDP to avoid filesystem activity.</p>
+<p><strong>Hint</strong>: One can use <code>netcat(1)</code> to send the debug messages to another host to avoid filesystem activity.</p>
 
 <h2>Recording  Overhead Traces</h2>
 
@@ -117,7 +117,7 @@ Used to measure the overhead incurred at the beginning of a scheduling quantum.<
 <li><code>PLUGIN_TICK_START</code>, <code>PLUGIN_TICK_END</code>: <br />
 Like [<code>TICK_START</code>, <code>TICK_END</code>], but only measures the time spent by the active scheduling plugin.</li>
 <li><code>PLUGIN_SCHED_START</code>, <code>PLUGIN_SCHED_END</code>: <br />
-Like [<code>SCHED_START</code>, <code>SCHED_END</code>], but only measures the time spent by the active scheduling plugin. There is no equivalent <code>SCHED2</code> counterpart because the scheduling plugins do not directly compute to the <code>SCHED2</code> overhead.</li>
+Like [<code>SCHED_START</code>, <code>SCHED_END</code>], but only measures the time spent by the active scheduling plugin. There is no equivalent <code>SCHED2</code> counterpart because the scheduling plugins do not directly contribute to the <code>SCHED2</code> overhead.</li>
 <li><code>RELEASE_START</code>, <code>RELEASE_END</code>: <br />
 Used to measure the time spent to enqueue a newly-released job in a ready queue.</li>
 </ul>
diff --git a/doc/tracing.txt b/doc/tracing.txt
index 2e44e10..7efcffd 100644
--- a/doc/tracing.txt
+++ b/doc/tracing.txt
@@ -78,7 +78,7 @@ Example:
 
         sort -n my_debug_log > my_sorted_debug_log
 
-**Hint**: One can use `netcat(1)` to send the debug messages to another machine via UDP to avoid filesystem activity.
+**Hint**: One can use `netcat(1)` to send the debug messages to another host to avoid filesystem activity.
 
 Recording  Overhead Traces
 --------------------------
@@ -106,7 +106,7 @@ Used to measure the overhead incurred at the beginning of a scheduling quantum.
 - `PLUGIN_TICK_START`, `PLUGIN_TICK_END`:  
 Like [`TICK_START`, `TICK_END`], but only measures the time spent by the active scheduling plugin.
 - `PLUGIN_SCHED_START`, `PLUGIN_SCHED_END`:  
-Like [`SCHED_START`, `SCHED_END`], but only measures the time spent by the active scheduling plugin. There is no equivalent `SCHED2` counterpart because the scheduling plugins do not directly compute to the `SCHED2` overhead.
+Like [`SCHED_START`, `SCHED_END`], but only measures the time spent by the active scheduling plugin. There is no equivalent `SCHED2` counterpart because the scheduling plugins do not directly contribute to the `SCHED2` overhead.
 - `RELEASE_START`, `RELEASE_END`:  
 Used to measure the time spent to enqueue a newly-released job in a ready queue.