Removed link to MIDI on Linux page in Mackie Control setup page.

[ardour-manual] / include / audiomidi-busses-mixer-strips.html

diff --git a/include/audiomidi-busses-mixer-strips.html b/include/audiomidi-busses-mixer-strips.html
index 226fea859fb7c77cd5c436cc1df5157f2a78ce36..6a9712b0f52a9b5c4475a2e04a8dbca9b1b3894b 100644 (file)
--- a/include/audiomidi-busses-mixer-strips.html
+++ b/include/audiomidi-busses-mixer-strips.html
@@ -1,15 +1,18 @@
 
 <figure class="right">
     <img src="/images/bus-mixer-strip.png" alt="A bus mixer strip">
+     <figcaption>
+      A bus mixer strip
+    </figcaption>
 </figure>
 
 <p>
   An Ardour bus can be considered a virtual track, as in a track that doesn't
   have a playlist (so, no regions). Its use is to "group" some audio signals to
   be treated the same way. One simple use case is to group all the audio tracks
-  containing the different drums of a drumkit. Routing all the drums tracks
+  containing the different drums of a drum kit. Routing all the drum tracks'
   outputs to a bus allows, once the different levels amongst the drums have been
-  set, to adjust the global level of the drumkit in the mix.
+  set, to adjust the global level of the drum kit in the mix.
 </p>
 <p>
   Bus usage goes way beyond this simple example though: busses, as tracks, can
@@ -33,7 +36,7 @@
   <li>as for tracks, the MIDI bus doesn't have a trim knob or invert phase button(s).</li>
 </ul>
 <p>
-  MIDI busses provide a particularly efficient workflow for virtual drumkits where
+  MIDI busses provide a particularly efficient workflow for virtual drum kits where
   the arrangement uses different MIDI tracks. Moreover, busses with both Audio and
   MIDI inputs are well suited for vocoders and similar plugins, where a MIDI
   signal controls an audio one.
@@ -48,7 +51,7 @@
   all of their controls</a>. The differences are:
 </p>
 <ul>
-  <li>as the busses dont have a playlist (and cannot host any media), they can't be recorded on. The recording controls are not present</li>
+  <li>as the busses don't have a playlist (and cannot host any media), they can't be recorded on. The recording controls are not present</li>
   <li>an <kbd class="menu">Aux</kbd> button replaces these controls.</li>
 </ul>
 <p>
@@ -76,13 +79,19 @@
 
 <h3>Connecting a track to a bus via its outputs</h3>
 
-<img class="left" src="/images/connecting_bus_output.png" alt="Connecting a bus through a track's outputs">
+<figure class="left">
+    <img src="/images/connecting_bus_output.png" alt="Connecting a bus through a track's outputs">
+    <figcaption>
+      Connecting a bus through a track's outputs
+    </figcaption>
+</figure>
+
 <p>
        Connecting the output(s) of a track to the input(s) of the bus sends
        <em>all</em> the audio/MIDI to the bus. In the mixer strip, select (at the
        bottom) the OUTPUT button (often, by default, "Master"), and in the list,
        choose the input of a bus. Note that only the bus able to receive this output
-       will show up, e.g. a mono bus wont be able to be connected to the output of a
+       will show up, e.g. a mono bus won't be able to be connected to the output of a
        stereo track).
 </p>
 <p>
@@ -97,7 +106,13 @@
 
 <h3>Connecting a track to a bus via Sends</h3>
 
-<img class="left" src="/images/connecting_bus_send.png" alt="Connecting a bus through a send">
+<figure class="left">
+    <img src="/images/connecting_bus_send.png" alt="Connecting a bus through a send">
+    <figcaption>
+      Connecting a bus through a send
+    </figcaption>
+</figure>
+
 <p>
        This allows not to interrupt the natural flow of the signal, i.e. the track will
   still output to what its connected to (e.g. Master). The signal is "tapped" at