wording edits

[ardour-manual-diverged] / _manual / 22_using-control-surfaces / 05_Presonus_FaderPort.html

diff --git a/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html b/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
index eec502d90e25577d0dc1fd9f8b318461506655a6..c0da405f1a9d9059c7d69c236199af08eb4870e1 100644 (file)
--- a/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
+++ b/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
@@ -21,7 +21,7 @@ menu_title: Presonus Faderport
   behaviour with the device. This issue might get fixed by Presonus in
   the future.
 </p>
-<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
   device to be in the correct mode. In native mode, the Faderport
@@ -117,13 +117,13 @@ menu_title: Presonus Faderport
 
 <h3>Other Global Controls</h3>
 <p>
-  The Mix, Proj, Trns buttons have no "obvious" functionality
-  that they correspond to in Ardour. We have therefore allowed users
-  to choose from a carefully curated set of possible actions that seem
-  related to the button labels in some clear way. This can be done via
-  the Faderport configuration dialog accessed via <code>Preferences
-  &gt; Control Surfaces</code>. Each button has 3 possible actions
-  associated with it:
+  The Mix, Proj, Trns buttons do not obviously correspond any
+  particular functions or operations in Ardour. We have therefore
+  allowed users to choose from a carefully curated set of possible
+  actions that seem related to the button labels in some clear
+  way. This can be done via the Faderport configuration dialog
+  accessed via <code>Preferences &gt; Control Surfaces</code>. Each
+  button has 3 possible actions associated with it:
   <ul>
     <li>Plain Press: action to be taken when the button is pressed on
       its own.</li>