--- a/master/interact.html	Mon Jul 22 15:21:29 2013 -0500
+++ b/master/interact.html	Mon Jul 22 15:32:53 2013 -0500
@@ -193,12 +193,8 @@
 ideal.  How much can we remove?  SVGLoad in particular, and how it is currently
 required to fire for every element.</p>
 
-<p class="issue">DOM 2 has no keyboard events in it. The only normative spec. on this is a new <a href="https://dvcs.w3.org/hg/d4e/raw-file/default/source_respec.htm">UI events spec. that should become a public working draft soon. This is areplacement for the DOM 3 Events spec. The group needs to discuss the current limitation in using DOM 2 events. Also, DOMActivate does not appear in the UI Events Spec. Regarding the activate event, user agents treat click the same as activate. 
-</a>
-
-Having all these SVG-specific duplicates of standard DOM events isn't
-ideal.  How much can we remove?  SVGLoad in particular, and how it is currently
-required to fire for every element.</p>
+<p class="issue">DOM 2 has no keyboard events in it. The only normative spec. on this is a new <a href="https://dvcs.w3.org/hg/d4e/raw-file/default/source_respec.htm">UI events</a> specification that should become a public working draft soon. This is a replacement for the DOM 3 Events spec. The group needs to discuss the current limitation in using DOM 2 events. Also, DOMActivate does not appear in the UI Events Spec. Regarding the activate event, user agents treat click the same as activate. We should question whether we should call the table headers DOM2 name and DOM2 category. These are insufficient. Should we reference the UIEvent spec. vs. the DOM2 Event where there is overlap?
+</p>
 
     <table  class="vert event-table">
       <tr>