--- a/src/include/terms.html	Thu Mar 28 16:38:05 2013 -0700
+++ b/src/include/terms.html	Tue Apr 30 19:32:56 2013 -0700
@@ -24,13 +24,13 @@
 	
 	<dt id="def_request_event_receiver">Request Event Receiver</dt>
 	<dd>
-		<p>The closest DOM ancestor to the user's <a href="#def_point_of_regard">point-of-regard</a> that declares the current event type via the @ui-actions content attribute or uiActions DOM attribute. The Request Event Receiver is referenced in the Event object's <code>receiver</code> property.</p>
+		<p>The closest DOM ancestor to the user's <a href="#def_point_of_regard">point-of-regard</a> that declares the current event type via the <code>uiactions</code> content attribute or <code>uiactions</code> DOM attribute. The Request Event Receiver is referenced in the Event object's <code>receiver</code> property.</p>
 		<p>UI Request Events are not initiated by the user agent unless the following are true:</p>
 		<ol>
-			<li>The user's point of regard is on the current or descendant node of an element that declares the event receiver via <code>@ui-actions</code></li>
+			<li>The user's point of regard is on the current or descendant node of an element that declares the event receiver via <code>@uiactions</code></li>
 			<li>The event receiver node (or any ancestor node of the receiver) also registered as the event listener via <code>element.addEventListener()</code></li>
 		</ol>
-		<p class="ednote">Some of this definition will need to be massaged and move into the normative sections above defining @ui-actions.</p>
+		<p class="ednote">Some of this definition will need to be massaged and move into the normative sections above defining @uiactions.</p>
 	</dd>
 	
 	<dt id="def_user_agent">User Agent</dt>

--- a/src/indie-ui-events.html	Thu Mar 28 16:38:05 2013 -0700
+++ b/src/indie-ui-events.html	Tue Apr 30 19:32:56 2013 -0700
@@ -140,7 +140,7 @@
 					<pre class="example">
 						<span class="markup" data-transform="syntaxMarkup">
 						&lt;!-- Declare which IndieUI event(s) this element receives. --&gt;
-						&lt;dialog <strong>ui-actions="dismiss"</strong> id="myDialog"&gt;
+						&lt;dialog <strong>uiactions="dismiss"</strong> id="myDialog"&gt;
 						  ...
 						&lt;/dialog&gt;
 						
@@ -177,7 +177,7 @@
 					<pre class="example">
 						<span class="markup" data-transform="syntaxMarkup">
 						&lt;!-- Declare which IndieUI event(s) this element receives. --&gt;
-						&lt;canvas <strong>ui-actions="valuechange"</strong> id="slider" role="slider" aria-valuemin="0" aria-valuemax="100" aria-valuenow="42"&gt;&lt;/canvas&gt;
+						&lt;canvas <strong>uiactions="valuechange"</strong> id="slider" role="slider" aria-valuemin="0" aria-valuemax="100" aria-valuenow="42"&gt;&lt;/canvas&gt;
 						
 						&lt;script type="text/javascript"&gt;</span><!--
 						--><span class="javascript" data-transform="syntaxJavaScript">
@@ -224,32 +224,31 @@
 			<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">
-				<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="#ui-actions"><code>ui-actions</code></a> content attribute.</p>
+			<section id="uiactions-dom-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">
-					<dt>attribute DOMString uiActions</dt>
-					<dd>A attribute whose string value <a href="#def_reflected_attribute">reflects</a> the value of the <a href="#ui-actions"><code>ui-actions</code></a> content attribute.</dd>
+					<dt>reflected attribute DOMString receives</dt>
+					<dd>A attribute whose string value <a href="#def_reflected_attribute">reflects</a> the value of the <a href="#uiactions-content-attribute"><code>uiactions</code> content attribute</a>.</dd>
 				</dl>
-				<p class="ednote">It may be more appropriate to name this receives/@receives than uiActions/@ui-actions.</p>
 			</section>
 			
-			<section id="ui-actions">
-				<h3>The <code>ui-actions</code> Content Attribute</h3>
-				<p>Every element may have a <code>ui-actions</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>ui-actions</code> attribute is split on whitespace. (Duplicates are ignored.)</p>
-				<p>User agents MUST <a href="#def_reflected_attribute">reflect</a> the <code>ui-actions</code> content attribute in the <a href="#uiActions"><code>uiActions</code></a> IDL attribute.</p>
+			<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>
 				<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">
 					<span class="markup" data-transform="syntaxMarkup">
 					&lt;!-- body element is event listener for all events, but event receiver only for 'undo' actions. --&gt;
-					&lt;body <strong>ui-actions="undo"</strong>&gt;
+					&lt;body <strong>uiactions="undo"</strong>&gt;
 					
 					  &lt;!-- Element container for custom 'mapview' is the event receiver for 'pan' and 'zoom' actions. --&gt;
-					  &lt;div id="mapview" <strong>ui-actions="pan zoom"</strong>&gt; ... &lt;/div&gt;
+					  &lt;div id="mapview" <strong>uiactions="pan zoom"</strong>&gt; ... &lt;/div&gt;
 					
 					  &lt;!-- This Dialog is the event receiver for 'dismiss' actions initiated on any lower-level event target. --&gt;
-					  &lt;dialog <strong>ui-actions="dismiss"</strong>&gt; ... &lt;/dialog&gt;
+					  &lt;dialog <strong>uiactions="dismiss"</strong>&gt; ... &lt;/dialog&gt;
 					
 					&lt;/body&gt;
 					
@@ -282,10 +281,10 @@
 			<!-- :::::::::::::::::::: UIRequestEvent :::::::::::::::::::: -->
 			<section id="UIRequestEvent" class="normative">
 				<h3>Interface UIRequestEvent</h3>
-				<p class="ednote">Separate interface from UIEvent because the @ui-actions attribute will 1) affect when and where these events are fired, and 2) adds the distinction of an event <a href="#def_request_event_receiver">receiver</a> element (element declaring the ui-actions attribute) in addition to the "target" element where the event initiates and the "listener" element where the event is registered for and handled.</p>
+				<p class="ednote">Separate interface from UIEvent because the @uiactions attribute will 1) affect when and where these events are fired, and 2) adds the distinction of an event <a href="#def_request_event_receiver">receiver</a> element (element declaring the uiactions attribute) in addition to the "target" element where the event initiates and the "listener" element where the event is registered for and handled.</p>
 				<dl title="[Constructor(DOMString typeArg, optional UIRequestEventInit dictUIRequestEventInit)] interface UIRequestEvent : UIEvent" class="idl">
 					<dt>readonly attribute EventTarget receiver</dt>
-					<dd>In addition to the target and currentTarget, each UI Request Event has a receiver element, which is declared via the <a href="#ui-actions"><code>ui-actions</code></a> content attribute on an ancestor node of the event target. <p class="ednote">Note: This may need to be defined as a partial interface on AbstractView, rather than in this interface.</p></dd>
+					<dd>In addition to the target and currentTarget, each UI Request Event has a receiver element, which is declared via the <a href="#uiactions-content-attribute"><code>uiactions</code></a> content attribute on an ancestor node of the event target. <p class="ednote">Note: This may need to be defined as a partial interface on AbstractView, rather than in this interface.</p></dd>
 				</dl>
 				
 				<div class="ednote">
@@ -591,6 +590,12 @@
 			<h2>Events List (alphabetical)</h2>
 			<div data-transform="listEvents"><!-- dynamically generates event list --></div>
 		</section>
+		<section id="changelist" class="appendix">
+			<h2>Normative changes since the last public working draft</h2>
+			<ul>
+				<li>The reflected attribute uiActions/@ui-actions is now uiactions/@uiactions.</li>
+			</ul>
+		</section>
 		<section id="terms" class="appendix" data-include="./include/terms.html"></section>
 		<section id="acknowledgements" class="appendix" data-include="./include/ack.html"></section>