cleaning up an obsolete page, adding its useful content to another

[ardour-manual] / include / using-the-presonus-faderport.html

diff --git a/include/using-the-presonus-faderport.html b/include/using-the-presonus-faderport.html
index 2f8eb2e26e2fd549572997091263ee96b24af903..3d12ac9868964ab6ae17a362ae7624569a87b917 100644 (file)
--- a/include/using-the-presonus-faderport.html
+++ b/include/using-the-presonus-faderport.html
@@ -12,18 +12,18 @@
 <p>
   The Faderport comes with a single USB socket on the back. Connect a
   suitable USB cable from there to a USB port on your computer. As of
-  the end of 2015, you should avoid USB3 ports - these cause erratic
+  the end of 2015, you should avoid USB3 ports&mdash;these cause erratic
   behaviour with the device. This issue might get fixed by Presonus in
   the future.
 </p>
 <p class="well">
   Ardour uses the Faderport in what Presonus calls "native" mode. You
-  do not need to do anything to enable this - Ardour will set the
+  do not need to do anything to enable this&mdash;Ardour will set the
   device to be in the correct mode. In native mode, the Faderport
   sends and receives ordinary MIDI messages to/from the host, and the
   host understands the intended meaning of these messages. We note
   this detail to avoid speculation about whether Ardour supports the
-  device via the HUI protocol - it does not.
+  device via the HUI protocol&mdash;it does not.
 <p>
   The Faderport will be automatically recognized by your operating
   system, and will appear in any of the lists of possible MIDI ports
@@ -62,10 +62,10 @@
   The Faderport's controls can be divided into three groups:
   <ol>
     <li>Global controls such as the transport buttons</li>
-    
+
     <li>Controls which change the settings for particular track or
       bus</li>
-    
+
     <li>Controls which alter which track or bus is modified by the
       per-track/bus controls.</li>
   </ol>
@@ -164,7 +164,7 @@
       </p>
     </dd>
     <dt>Proj</dt>
-    <dd> 
+    <dd>
       <p>
        Possible actions include:
        <ul>
@@ -193,7 +193,7 @@
     <dd>
       Undo Causes the last operation carried out in the editor to be
       undone. When pressed in conjuction with the Shift button, it
-      causes the most recent undone operation to be re-done. 
+      causes the most recent undone operation to be re-done.
     </dd>
     <dt>Punch</dt>
     <dd>
@@ -210,7 +210,7 @@
     <dd>
       <p>
        See above. Any and all GUI-initiated actions can be driven with
-       by pressing this button on its own, or with a "long" press. 
+       by pressing this button on its own, or with a "long" press.
       </p>
       <p>
        When pressed in conjunction with the Shift button, this will move
@@ -233,7 +233,7 @@
     </dd>
   </dl>
 </p>
-  
+
 <h3>Per-track Controls</h3>
 <p>
   <dl>
@@ -260,7 +260,7 @@
       The fader controls the gain applied to the currently controlled
       track/bus. If the Faderport is powered, changing the gain in
       Ardour's GUI or via another control surface, or via automation,
-      will result in the fader moving under its own control. 
+      will result in the fader moving under its own control.
     </dd>
     <dt>Knob/Dial/Encoder</dt>
     <dd>
@@ -342,7 +342,7 @@
        Pressing the Output button causes the Faderport to control
        the fader, pan, mute and solo settings of the Master bus. If
        your session does not contain a Master bus, it does nothing.
-       This is a toggle button - pressing it again returns Faderport
+       This is a toggle button&mdash;pressing it again returns Faderport
        to controlling whichever track/bus was selected before the
        first press of the Output button.
       </p>