X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmidi-on-os-x.html;fp=include%2Fmidi-on-os-x.html;h=985e5230db517012841531d1578b400f321bc596;hb=7a4c28bd8605e90876ebee619de364ab7001e405;hp=1eecc35afad0b93aa2a16774c6852fbc1ebb08b2;hpb=2a78650ae3df3a17c9c33f07aea597eb5f36da61;p=ardour-manual

diff --git a/include/midi-on-os-x.html b/include/midi-on-os-x.html
index 1eecc35..985e523 100644
--- a/include/midi-on-os-x.html
+++ b/include/midi-on-os-x.html
@@ -1,4 +1,4 @@
-  
+
 <p>
   In order for CoreMIDI to work with Jack MIDI, a CoreMIDI-to-JACK-MIDI
   <dfn>bridge</dfn>
@@ -10,8 +10,8 @@
 <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. 
+  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>