--- a/midi/specification.html	Tue Oct 30 20:29:48 2012 -0400
+++ b/midi/specification.html	Wed Oct 31 12:45:06 2012 -0700
@@ -494,53 +494,6 @@
 
       <p>This interface represents a MIDI input or output port.</p>
 
-      <p id="event-midiport-disconnect">
-        Whenever the MIDI port corresponding the
-        <code><a>MIDIPort</a></code> is disconnected or becomes unavailable,
-        if supported by the underlying system the UA SHOULD run the following steps:
-      </p>
-
-      <ol>
-        <li>
-          <p>
-            Fire a simple event named <code><a
-            href="#event-midiport-disconnect">disconnect</a></code>
-            at the object.
-          </p>
-        </li>
-      </ol>
-
-      <p id="event-midiport-connect">
-        Whenever the MIDI port corresponding the
-        <code><a>MIDIPort</a></code> is connected or reconnected,
-        the UA MUST run the following steps:
-      </p>
-
-      <ol>
-        <li>
-          <p>
-            Fire a simple event named <code><a
-            href="#event-midiport-connect">connect</a></code>
-            at the object.
-          </p>
-        </li>
-      </ol>
-
-      <div class="note">
-        <p>
-          The <code><a>disconnect</a></code> and
-          <code><a>connect</a></code> events may not be applicable to all
-          MIDI ports or OS APIs. For example, some system APIs do not dynamically
-          notify applications when MIDI ports become available or unavailable. 
-          Therefore the semantic here is SHOULD, rather than MUST.
-        </p>
-        <p>It is also important to note again that the MIDIPort represents an
-          input or output interface, not necessarily an endpoint MIDI device; it
-          is not possible, using this system, to be notified when a synthesizer
-          is plugged into a 5-pin DIN MIDI port on a hardware MIDI interface.
-        </p>
-      </div>
-
       <dl class="idl" title='enum MIDIPortType'>
         <dt>input</dt>
         <dd>