--- a/editing.html	Tue Oct 11 11:48:10 2011 -0600
+++ b/editing.html	Tue Oct 11 11:53:26 2011 -0600
@@ -1173,9 +1173,16 @@
 subsequent calls must return the same object if nothing has removed the
 <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#context-object>context object</a>'s <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-range title=concept-range>range</a> in the meantime.)
 
-<p class=comments>IE9 and Firefox 4.0 act as described here.  Chrome 12 dev and
+<div class=comments>
+<p>IE9 and Firefox 4.0 store a reference, as described here.  Chrome 12 dev and
 Opera 11.10 appear to store a copy, so changes don't affect the selection.
 
+<p>Chrome 15 dev seems to ignore addRange() if there's already a range.  IE9
+replaces the existing range.  Firefox 9.0a2, of course, just gives you a
+multi-range selection.  IE is likely to behave closest to Firefox, and is also
+more useful than silent failure, so the spec goes with that.
+</div>
+
 <p>The <dfn id=dom-selection-addrange title=dom-Selection-addRange><code>addRange(<var title="">range</var>)</code></dfn>
 method must <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-throw title=concept-throw>throw</a> an "InvalidNodeTypeError" exception if <var title="">range</var>'s
 <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-range-start-node title=concept-range-start-node>start node</a> or <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-range-end-node title=concept-range-end-node>end node</a> is not a <code class=external data-anolis-spec=dom><a href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#text>Text</a></code> or <code class=external data-anolis-spec=dom><a href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#element>Element</a></code> node.  Otherwise,
@@ -1188,12 +1195,6 @@
 it is added must be reflected in the <a href=#concept-selection title=concept-selection>selection</a>, until something else
 removes or replaces the <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#context-object>context object</a>'s <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-range title=concept-range>range</a>.
 
-<p class=comments>Firefox 9.0a2 allows multiple Ranges per Selection, as noted
-elsewhere, so of course this isn't how it behaves.  Chrome 15 dev seems to
-ignore addRange() if there's already a range.  The spec matches IE9, which
-replaces the existing range.  This is likely to behave closest to Firefox, and
-is also more useful than silent failure.
-
 <p>The <dfn id=dom-selection-removerange title=dom-Selection-removeRange><code>removeRange(<var title="">range</var>)</code></dfn>
 method must set the <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#context-object>context object</a>'s <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-range title=concept-range>range</a> to null if its <a class=external data-anolis-spec=dom href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-range title=concept-range>range</a> is
 currently <var title="">range</var>, otherwise do nothing.

--- a/source.html	Tue Oct 11 11:48:10 2011 -0600
+++ b/source.html	Tue Oct 11 11:53:26 2011 -0600
@@ -1123,9 +1123,16 @@
 subsequent calls must return the same object if nothing has removed the
 [[contextobject]]'s [[range]] in the meantime.)
 
-<p class=comments>IE9 and Firefox 4.0 act as described here.  Chrome 12 dev and
+<div class=comments>
+<p>IE9 and Firefox 4.0 store a reference, as described here.  Chrome 12 dev and
 Opera 11.10 appear to store a copy, so changes don't affect the selection.
 
+<p>Chrome 15 dev seems to ignore addRange() if there's already a range.  IE9
+replaces the existing range.  Firefox 9.0a2, of course, just gives you a
+multi-range selection.  IE is likely to behave closest to Firefox, and is also
+more useful than silent failure, so the spec goes with that.
+</div>
+
 <p>The <dfn
 title=dom-Selection-addRange><code>addRange(<var>range</var>)</code></dfn>
 method must [[throw]] an "InvalidNodeTypeError" exception if <var>range</var>'s
@@ -1139,12 +1146,6 @@
 it is added must be reflected in the [[selection]], until something else
 removes or replaces the [[contextobject]]'s [[range]].
 
-<p class=comments>Firefox 9.0a2 allows multiple Ranges per Selection, as noted
-elsewhere, so of course this isn't how it behaves.  Chrome 15 dev seems to
-ignore addRange() if there's already a range.  The spec matches IE9, which
-replaces the existing range.  This is likely to behave closest to Firefox, and
-is also more useful than silent failure.
-
 <p>The <dfn
 title=dom-Selection-removeRange><code>removeRange(<var>range</var>)</code></dfn>
 method must set the [[contextobject]]'s [[range]] to null if its [[range]] is