--- a/src/indie-ui-events.html	Wed May 01 00:51:01 2013 -0700
+++ b/src/indie-ui-events.html	Wed May 01 00:53:11 2013 -0700
@@ -224,7 +224,7 @@
 			<h2><abbr title="User Interface">UI</abbr> Actions</h2>
 			<p>User interface actions are declared as enumerated token attribute values on an element. Each value corresponds to a specific <a href="#RequestEvents">UI Request Event</a>, and declares the web page author's ability to receive and handle each of the request events initiated by the user agent. In order to receive each request event, authors MUST also register for the event using  <code>Element.addEventListener()</code> at this node or higher in the DOM. User agents SHOULD NOT initiate a <a href="#RequestEvents">UI Request Event</a> when the user's <a href="#def_point_of_regard">point-of-regard</a> is not inside an element with the corresponding defined action.</p>
 			
-			<section id="uiactions-dom-attribute">
+			<section id="uiactions-attribute">
 				<h2>The <code>uiactions</code> IDL Attribute</h2>
 				<p>The <code>uiactions</code> attribute of each instance of the Element interface MUST return a DOMString <a href="#def_reflected_attribute">reflecting</a> the <a href="#uiactions-content-attribute"><code>uiactions</code> content attribute</a>.</p>
 				<dl title="partial interface Element" class="idl">
@@ -236,7 +236,7 @@
 			<section id="uiactions-content-attribute">
 				<h3>The <code>uiactions</code> Content Attribute</h3>
 				<p>Every element may have a <code>uiactions</code> attribute specified, which is necessary to define the <a href="#def_request_event_receiver">receiver</a> of each type of request event. The attribute, if specified, must have a value that is a set of whitespace-separated tokens representing the various actions to which the web application responds on behalf of this element. The actions that an element has assigned to it consists of all the tokens returned when the value of the <code>uiactions</code> attribute is split on whitespace. (Duplicates are ignored.)</p>
-				<p>User agents MUST <a href="#def_reflected_attribute">reflect</a> the <code>uiactions</code> content attribute in the <a href="#uiactions-dom-attribute"><code>uiactions</code> DOM attribute</a>.</p>
+				<p>User agents MUST <a href="#def_reflected_attribute">reflect</a> the <code>uiactions</code> content attribute in the <a href="#uiactions-attribute"><code>uiactions</code> IDL attribute</a>.</p>
 				<div data-transform="listActions"><!-- dynamically generates event list --></div>
                 <!-- <p class="ednote">We could probably combine the 'manipulation' events into a single 'manipulation' action value. I don't foresee a case where an author would want to receive some, but not all of them, and even if that case exists, the author could just not listen for those specific events.</p> -->
 				<pre class="example">