--- a/src/indie-ui-events.html	Mon Aug 19 16:36:21 2013 -0700
+++ b/src/indie-ui-events.html	Wed Aug 21 17:23:52 2013 -0700
@@ -796,15 +796,15 @@
 		</section>
 		<!-- :::::::::::::::::::: END UI Request Event Interfaces :::::::::::::::::::: -->
 
-		<!-- :::::::::::::::::::: DOMImplementation.hasFeature :::::::::::::::::::: -->
+		<!-- :::::::::::::::::::: DOM Feature Detection :::::::::::::::::::: -->
 		<section id="hasFeature" class="normative">
 			<h2>Strings for DOMImplementation.hasFeature()</h2>
 			<p>User agents with <em>complete</em> support for IndieUI Events 1.0 MUST return <code>true</code> when the <code>DOMImplementation.hasFeature()</code> method is called with the feature string <code>"org.w3c.indieui.events"</code> and version <code>"1.0"</code>. User agents with partial-but-incomplete support for Indie UI 1.0 MAY return <code>true</code> when queried with the version string <code>"0.0"</code>.</p>
 			<p class="ednote">The previous RFC-2119 "may" is intended to prevent UAs from claiming full support too soon. Should we use 0.0, 0.9, or something else here? UAs should probably not return true for <code>DOMImplementation.hasFeature("org.w3c.indieui.events", "1.0")</code> until after we publish a Last Call draft.</p>
 			<p>User agents implementing specific events MUST return <code>true</code> when the <code>DOMImplementation.hasFeature()</code> method is called with a feature string matching the literal event name appended to the main IndieUI events string, such as <code>"org.w3c.indieui.events.valuechangerequest"</code>.</p>
-			<p class="ednote">Note: WHATWG has <a href="http://dom.spec.whatwg.org/#dom-domimplementation-hasfeature">deprecated hasFeature</a>, so we may need to add some additional interfaces to allow object detection of supported features.</p>
+			<p class="ednote">Note: <a href="http://www.w3.org/TR/domcore/#dom-domimplementation-hasfeature">hasFeature is deprecated</a> in DOM 4, so we may need to add some additional interfaces to allow object detection of supported features, unless we can use the similar functionality of <a href="http://www.w3.org/TR/domcore/#dom-node-issupported">Node.isSupported</a> or <a href="http://www.w3.org/TR/domcore/#dom-node-getfeature">Node.getFeature</a>.</p>
 		</section>
-		<!-- :::::::::::::::::::: END DOMImplementation.hasFeature :::::::::::::::::::: -->
+		<!-- :::::::::::::::::::: END DOM Feature Detection :::::::::::::::::::: -->
 
 		<!--
 		ReSpec: Use @data-transform to reuse a JavaScript content formatter, and @data-oninclude to transform external content before inclusion.