--- a/master/interact.html	Mon Nov 18 16:01:33 2013 -0600
+++ b/master/interact.html	Mon Nov 18 16:29:40 2013 -0600
@@ -193,14 +193,14 @@
 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 class="issue">DOM 3 and UI Event both define a keyboard event where UI Event introduced a key code which appears to be necessary per the WebApps effort. UI Event is an extension to KeyboardEvent in DOM 3. The group needs to discuss whether to use the UIEvent or DOM3 Event for keyboard. Also, HTML has taken on DOM 4 events and the group needes to decide what to do with this long term. Additionally, DOMActivate does not appear in the UI Events or DOM 3 Events Specs. Regarding the activate event, user agents treat click the same as activate. 
 </p>
 
     <table  class="vert event-table">
       <tr>
         <th>Event name and description</th>
-        <th>DOM2 name</th>
-        <th>DOM2 category</th>
+        <th>DOM3 or UI Event name</th>
+        <th>Event category</th>
         <th>Event attribute name</th>
       </tr>
       <tr>