Edit pages to reflect jackd not being essential

[ardour-manual] / include / generic-midi-learn.html

diff --git a/include/generic-midi-learn.html b/include/generic-midi-learn.html
index d516bbc6cc0f6812c8d3ef6629bb45b359404b9f..e03047ee17451364df87156718812d3e354ef17c 100644 (file)
--- a/include/generic-midi-learn.html
+++ b/include/generic-midi-learn.html
@@ -6,7 +6,9 @@ controlling Ardour. There may be very legitimate reasons for different
 users to prefer quite different mappings.
 </p>
 <p>
-On every platform that Ardour runs on, there are excellent
+<kbd class="menu">Window &gt; MIDI Connections</kbd> opens the
+MIDI Connection Manager to help routing MIDI in and out.
+Along with that, 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
@@ -14,7 +16,7 @@ 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.
+QJackCtl, aconnect, Patchage, and more.
 </p>
 
 <h2>Basics</h2>
@@ -31,6 +33,14 @@ QJackctl, aconnect, Patchage, and more.
   <li>The binding is complete. Moving the hardware should control the Ardour fader etc. </li>
 </ol>
 
+<h2>Cancelling a Learned MIDI Binding</h2>
+
+<p>
+  To unlearn a learned MIDI binding, <kbd class="mod1 mouse">Middle</kbd>-click
+  on the control in the same way as you did to learn it in the first place, but
+  click on the popup to cancel it.
+</p>
+
 <h2>Avoiding work in the future</h2>
 <p>
 If you want the bindings you set up to be used automatically in every