Editorial tweaks

source

@@ -72494,10 +72494,16 @@ END:VCARD</pre>
        <var>ineligible</var> were excluded from consideration.</p></li>
       </ol>
      </li>
-     <li><p>If <var>candidate</var> is not null, let <var>candidate</var> be the new <span
-     data-x="event-target">event target</span>.</p></li>
+     <li><p>If <var>candidate</var> is not null, then fire the event using <var>candidate</var> as
+     the revised <span data-x="event-target">event target</span>.</p></li>
      <li><p>Otherwise, do not fire the event.</p></li>
     </ol>
+
+    <p class="example">For example, consider a page that consists of just a single
+    <span>inert</span> <code>button</code> positioned in the middle of a <code>body</code>. If a
+    user clicks on the button, the <code data-x="event-click">click</code> event would cause no
+    event listeners on <code>button</code> to be run, and the event would instead be targeted at the
+    <code>body</code> element.</p>
    </li>
 
    <li><p>The user agent may ignore the node for the purposes of text search user interfaces
@@ -72509,15 +72515,11 @@ END:VCARD</pre>
   <p>User agents should allow the user to override the restrictions on search and text selection,
   however.</p>
 
-  <p class="example">For example, consider a page that consists of just a single <span>inert</span>
-  <code>button</code> positioned in the middle of a <code>body</code>. If a user clicks on the
-  button, the <code data-x="event-click">click</code> event would cause no event listeners on
-  <code>button</code> to be run, and the event would instead be targeted at the <code>body</code> element.</p>
 
   <p class="note">When a node is inert, it generally cannot be focused. Inert nodes that are <span
   data-x="concept-command">commands</span> will also get disabled.</p>
 
-  <p>User agents should show the default cursor when a user indicates an element in an inert subtree
+  <p>User agents should show the default cursor when a user indicates an <span>inert</span> element
   using a pointing device.</p>
 
   <p>While a <span>browsing context container</span> is marked as <span>inert</span>, its
@@ -72528,6 +72530,8 @@ END:VCARD</pre>
   is <dfn>expressly inert</dfn> if it is <span>inert</span> and its <span>node document</span> is
   not <span>inert</span>.</p>
 
+  <hr>
+
   <p>A <code>Document</code> <var>document</var> is <dfn>blocked by a modal dialog</dfn>
   <var>subject</var> if <var>subject</var> is the topmost <code>dialog</code> element in
   <var>document</var>'s <span>top layer</span>. While <var>document</var> is so blocked, every node
@@ -72549,7 +72553,8 @@ END:VCARD</pre>
   made <span>inert</span>.</p>
 
   <p w-nodev>When an element has an <code data-x="attr-inert">inert</code> attribute, the user agent
-  must mark that element and all its shadow-including descendants as <span>inert</span>.</p>
+  must mark that element and all its <span data-x="shadow-including descendant">shadow-including
+  descendants</span> as <span>inert</span>.</p>
 
   <p class="note">By default, there is no persistent visual indication of a subtree being inert.
   Authors are encouraged to clearly mark what parts of their document are active and which are