X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmidi-on-os-x.html;h=47442131bec7b04dc50733a3c3931efe46e7af7f;hb=53168d99209b770d9894692b820f06393a63abb5;hp=d1323fbdaa77b6667cdc9d0c685f6fa4da05598b;hpb=2098e011e638b5c86c56e68df7757975fc4d728f;p=ardour-manual

diff --git a/include/midi-on-os-x.html b/include/midi-on-os-x.html
index d1323fb..4744213 100644
--- a/include/midi-on-os-x.html
+++ b/include/midi-on-os-x.html
@@ -1,30 +1,31 @@
-  
+
 <p>
   In order for CoreMIDI to work with Jack MIDI, a CoreMIDI-to-JACK-MIDI
-  <dfn>bridge</dfn>
-  is required. This feature is available on versions equal to or great than
-  version 0.89 of JackOSX.
+  <dfn>bridge</dfn> is required. This feature is available on versions equal to
+  or greater than version 0.89 of JackOSX.
 </p>
 
 <h2>Routing MIDI</h2>
+
 <h3>Inside Ardour</h3>
+
 <p>
-  MIDI ports show up in Ardour's MIDI connection matrix in multiple
-  locations. Bridged CoreMIDI ports as well as JACK MIDI ports that have 
-  been created by other software clients will show up under the "Other" tab. 
-  Bridged CoreMIDI hardware ports show up under the "Hardware" tab.
+  MIDI ports show up in Ardour's MIDI connection matrix in multiple locations.
+  Bridged CoreMIDI ports as well as JACK MIDI ports that have been created by
+  other software clients will show up under the "Other" tab. Bridged CoreMIDI
+  hardware ports show up under the "Hardware" tab.
 </p>
 
 <h3>External Applications</h3>
+
 <p>
   There are multiple options for connecting MIDI ports outside of Ardour.
 </p>
+
 <ul>
   <li><a href="http://www.snoize.com/MIDIMonitor/">MIDI Monitor</a> is a handy
   tool for doing various MIDI-related tasks.</li>
-  <li><a href="http://notahat.com/midi_patchbay/">MIDI Patchbay</a> lets you
-  connect ports and filters MIDI data.</li>
+  <li><a href="http://notahat.com/midi_patchbay/">MIDI Patchbay</a> allows
+  connection of ports and filters MIDI data.</li>
 </ul>
 
-  
-