add faderport dialog image

diff --git a/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html b/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
index 11338c64baadc69ba582aac5d55ade849ba10345..a07687beb56d39ab2ab1bd63a6b911ccc3de7d40 100644 (file)
--- a/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
+++ b/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
@@ -4,12 +4,13 @@ title: Using the Presonus Faderport
 menu_title: Presonus Faderport
 ---                        
 
-<img align="left" alt="A picture of a Presonus Faderport device" src="/images/faderport-ssmall.png">
 <p>
   Since version 4.5, Ardour has had full support for the Presonus
   Faderport. This is a compact control surface featuring a single
   motorized fader, a single knob (encoder) and 24 buttons with fixed
-  labels.
+  labels. It is a relatively low-cost device that functions very well
+  to control a single (selected) track or bus, along with a variety of
+  other "global" settings and conditions.
 </p>
 
 <h2>Connecting the Faderport</h2>
@@ -42,7 +43,7 @@ menu_title: Presonus Faderport
   two dropdown selectors that will allow you to identify the MIDI
   ports where your Faderport is connected.
 </p>
-<img alt="the Faderport configuration dialog" src="foo">
+<img alt="the Faderport configuration dialog" src="images/faderport_dialog.png">
 <p>
   Once you select the input and output port, Ardour will initialize
   the Faderport and it will be ready to use. You only need do this

diff --git a/source/images/faderport_dialog.png b/source/images/faderport_dialog.png
new file mode 100644 (file)
index 0000000..c36def8
Binary files /dev/null and b/source/images/faderport_dialog.png differ