X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fgeneric-midi-learn.html;h=e03047ee17451364df87156718812d3e354ef17c;hb=e74c09802c2ca4038144d051c425a65661bde3ea;hp=f941b1bf47158bec5e26621948239d2d7acb0089;hpb=720f72d3e5375376fddb4650c41e851dc82114db;p=ardour-manual

diff --git a/include/generic-midi-learn.html b/include/generic-midi-learn.html
index f941b1b..e03047e 100644
--- 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>