remove reference to ardour 2.x

diff --git a/_manual/22_using-control-surfaces/04_midi-learn.html b/_manual/22_using-control-surfaces/04_midi-learn.html
index 15fdb088816f72dea8cb435f66e4e20e05059a3a..1d7b9aaa34b22414cf9ffc2a30cd5daaafd7b1c1 100644 (file)
--- a/_manual/22_using-control-surfaces/04_midi-learn.html
+++ b/_manual/22_using-control-surfaces/04_midi-learn.html
@@ -12,7 +12,15 @@ with any pre-defined mapping - we believe that users know what is best
 for them.
 </p>
 <p>
-On every platform that Ardour runs on, there are excellent free-of-charge tools for making connections between MIDI hardware and "virtual" MIDI ports like the ones that Ardour creates and uses. Rather than waste precious developer time replicating these connection/patch managers, we prefer to leverage their existence by having users rely on them to actually connect Ardour to other MIDI devices and software. On OS X, we recommend Pete Yandell's MIDI Patchbay. On Linux, a wide variety of tools are available including QJackctl, aconnect, Patchage, and more. So, you will not find a MIDI connection dialog in Ardour 2.X.
+On every platform that Ardour runs on, there are excellent
+free-of-charge tools for making connections between MIDI hardware and
+"virtual" MIDI ports like the ones that Ardour creates and
+uses. Rather than waste precious developer time replicating these
+connection/patch managers, we prefer to leverage their existence by
+having users rely on them to actually connect Ardour to other MIDI
+devices and software. On OS X, we recommend Pete Yandell's MIDI
+Patchbay. On Linux, a wide variety of tools are available including
+QJackctl, aconnect, Patchage, and more. 
 </p>
 
 <h3>Basics<h3>