X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmidi-overview.html;h=7de8e5013df0134afb5092445cf377d619a551c1;hb=e64d2bbf13757c538f0e8e93ee38354806184b43;hp=47358e8791200d7e04479ea944aada32ef7d9f19;hpb=6036e3f09fdf88dfa2a251202dffb4420eaf43f3;p=ardour-manual

diff --git a/include/midi-overview.html b/include/midi-overview.html
index 47358e8..7de8e50 100644
--- a/include/midi-overview.html
+++ b/include/midi-overview.html
@@ -28,13 +28,16 @@
     which allows the editing of MIDI data in a given region.
   </li>
   <li>
-    All MIDI I/O is done either by ALSA or JACK (depending on which backend was chosen when starting Ardour), for sample accurate timing and maximal efficiency when communicating with external software synthesizers.
+    All MIDI I/O is handled by the audio/MIDI backend was chosen when
+    starting Ardour. In general, all backends provide sample accurate
+    timing and maximal efficiency when communicating with external
+    software synthesizers.
   </li>
   <li>
-    Every MIDI track has its own JACK MIDI port for input; it may have an
-    arbitrary combination of audio and MIDI outputs, depending on the signal
-    processing in the track; the full flexibility of JACK connectivity is
-    present for MIDI just as it is for audio.
+    Every MIDI track has its own input port; it may have an arbitrary
+    combination of audio and MIDI outputs, depending on the signal
+    processing in the track; the full flexibility of Ardour patching
+    &amp; connectivity is present for MIDI just as it is for audio.
   </li>
   <li>
     Full automation for MIDI tracks, integrated with the handling of all MIDI