diff --git a/source b/source
index ded567dfbb3..252a5778987 100644
--- a/source
+++ b/source
@@ -3305,7 +3305,10 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
     <ul class="brief">
      <li><dfn data-x-href="https://w3c.github.io/touch-events/#touch-interface"><code>Touch</code></dfn> interface</li>
      <li><dfn data-x-href="https://w3c.github.io/touch-events/#dfn-touch-point">Touch point</dfn> concept</li>
+     <li><dfn data-x="event-touchstart" data-x-href="https://w3c.github.io/touch-events/#event-touchstart"><code>touchstart</code></dfn> event</li>
      <li><dfn data-x="event-touchend" data-x-href="https://w3c.github.io/touch-events/#event-touchend"><code>touchend</code></dfn> event</li>
+     <li><dfn data-x="event-touchmove" data-x-href="https://w3c.github.io/touch-events/#event-touchmove"><code>touchmove</code></dfn> event</li>
+     <li><dfn data-x="event-touchcancel" data-x-href="https://w3c.github.io/touch-events/#event-touchcancel"><code>touchcancel</code></dfn> event</li>
     </ul>
 
     <p>The following features are defined in the Pointer Events specification: <ref spec=POINTEREVENTS></p>
@@ -72476,6 +72479,10 @@ END:VCARD</pre>
      <li><p><code data-x="event-mouseout">mouseout</code></p></li>
      <li><p><code data-x="event-mouseover">mouseover</code></p></li>
      <li><p><code data-x="event-mouseup">mouseup</code></p></li>
+     <li><p><code data-x="event-touchstart">touchstart</code></p></li>
+     <li><p><code data-x="event-touchend">touchend</code></p></li>
+     <li><p><code data-x="event-touchmove">touchmove</code></p></li>
+     <li><p><code data-x="event-touchcancel">touchcancel</code></p></li>
      <li><p><code data-x="event-wheel">wheel</code></p></li>
      <li><p><code data-x="event-beforeinput">beforeinput</code></p></li>
      <li><p><code data-x="event-input">input</code></p></li>
@@ -72487,8 +72494,16 @@ END:VCARD</pre>
     </ul>
    </li>
 
+   <li><p>if one of the above events would otherwise be fired on the element
+   as a result of a user interaction, where the process for determining the
+   event target entails "hit testing", the event must instead be targeted at
+   the non-inert ancestor of the element which would be the topmost "hit
+   testing" result for the point at which the interaction occurred, if the inert
+   element, its inert ancestors, and any unrelated elements were not
+   present;</p></li>
+
    <li><p>the user agent may ignore the node for the purposes of text search user interfaces
-   (commonly known as "find in page"), and</p></li>
+   (commonly known as "find in page"); and</p></li>
 
    <li><p>the user agent may prevent the user from selecting text in that node, and may prevent
    code calling <code data-x="dom-textarea/input-setSelectionRange">setSelectionRange()</code>
@@ -72501,8 +72516,7 @@ END:VCARD</pre>
   <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 bubble up to the <code>body</code> element
-  regardless of any event listeners on the <code>button</code>.</p>
+  <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>