Continuing the rephrasing

[ardour-manual] / include / osc58-feedback-and-strip-types-values.html

diff --git a/include/osc58-feedback-and-strip-types-values.html b/include/osc58-feedback-and-strip-types-values.html
index a77f196d2fcc20cd0d19cb12f4a3e138fcf02a86..b6aba35b0ece02e5c9e72322853b0bace7973824 100644 (file)
--- a/include/osc58-feedback-and-strip-types-values.html
+++ b/include/osc58-feedback-and-strip-types-values.html
@@ -5,7 +5,7 @@
   to turn various kinds of feedback on or off or to determine which
   kinds of strips are currently viewed/controlled.
 </p>
-<p>Both ,<em>feedback</em> and <em>strip-types</em> use bitsets to keep
+<p>Both <em>feedback</em> and <em>strip-types</em> use bitsets to keep
   track what they are doing. Any number in a computer is made out of
   bits that are on or off, but we represent them as normal base 10
   numbers. Any one bit turned on will add a unique value to the
@@ -28,10 +28,10 @@
                2       - MidiTracks.
        </li>
        <li>
-               4       - AudioBuses.
+               4       - AudioBusses.
        </li>
        <li>
-               8       - MidiBuses.
+               8       - MidiBusses.
        </li>
        <li>
                16      - VCAs.
@@ -60,7 +60,7 @@
   to show inline with other strips.
 </p>
 <p>
-  Some handy numbers to use might be: 15 (all tracks and buses), 31
+  Some handy numbers to use might be: 15 (all tracks and busses), 31
   (add VCAs to that). Master or Monitor strips are generally not useful
   on a surface that has dedicated controls for these strips as there are
   /master* and /monitor* commands already. However, on a surface with
@@ -72,17 +72,17 @@
 <p class-"note">
   Audio Aux? say what? I am sure most people will have noticed that they
   can find no <em>Aux</em> strips in the Ardour mixer. There are none.
-  There are buses that can be used a number of ways. From analog days,
+  There are busses that can be used a number of ways. From analog days,
   in OSC, a bus is something that gets used as a sub mix before ending up
   going to Master. An auxiliary bus is used like a separate mixer and
   it's output goes outside the program or computer to be used as:
   a monitor mix, a back up recording, or what have you. In OSC where
   controller strips may be limited, it may be useful not to use up a
   strip for an aux that is not really a part of the mix. It is also
-  useful to get a list of only aux buses if the control surface is a
+  useful to get a list of only aux busses if the control surface is a
   phone used to provide talent monitor mix control on stage. Each
   performer would be able to mix their own monitor. The user is free
-  to enable both buses and auxes if they would prefer.
+  to enable both busses and auxes if they would prefer.
 </p>
 
 <h3>feedback</h3>