diff --git a/source b/source
index 9eb28e333a5..c8caba5038e 100644
--- a/source
+++ b/source
@@ -48199,11 +48199,12 @@ interface <dfn interface>HTMLInputElement</dfn> : <span>HTMLElement</span> {
   being <i data-x="concept-fe-mutable">mutable</i>.</p>
 
   <p>The <code>input</code> element can <dfn data-x="input-support-picker">support a picker</dfn>. A
-  picker is a popup that allows the end user to choose a value. Whether an <code>input</code>
-  element supports a picker depends on the <code data-x="attr-input-type">type</code> attribute
-  state and <span>implementation-defined</span> behavior. An <code>input</code> element must support
-  a picker when its <code data-x="attr-input-type">type</code> attribute is in the <span
-  data-x="attr-input-type-file">File Upload</span> state.</p>
+  picker is a user interface element that allows the end user to choose a value. Whether an
+  <code>input</code> element supports a picker depends on the <code
+  data-x="attr-input-type">type</code> attribute state and <span>implementation-defined</span>
+  behavior. An <code>input</code> element must support a picker when its <code
+  data-x="attr-input-type">type</code> attribute is in the <span data-x="attr-input-type-file">File
+  Upload</span> state.</p>
 
   <div class="note">
    <p>As of the time of this writing, typical browser implementations show such picker UI for:</p>
@@ -48220,16 +48221,10 @@ interface <dfn interface>HTMLInputElement</dfn> : <span>HTMLElement</span> {
     data-x="concept-input-list">suggestions source element</span>;</p></li>
 
     <li><p><code>input</code> elements whose <code data-x="attr-input-type">type</code> attribute
-    is in the <span data-x="attr-input-type-file">File Upload</span> state (although those are
-    handled via the special case above, instead of by this step); and</p></li>
+    is in the <span data-x="attr-input-type-file">File Upload</span> state; and</p></li>
 
     <li><p><code>select</code> elements.</p></li>
    </ul>
-
-   <p>However, the intent of this step is to trigger <em>any</em> picker UI implementation. So
-   for example, if a user agent implemented a password picker UI for the <span
-   data-x="attr-input-type-password">Password</span> state, then this method would be expected to
-   show that picker UI when called on a password input.</p>
   </div>
 
   <p>The <span data-x="concept-node-clone-ext">cloning steps</span> for <code>input</code> elements
@@ -52861,11 +52856,11 @@ You cannot submit this form when the field is incorrect.</samp></pre>
    <dt><code data-x=""><var>input</var>.<span subdfn data-x="dom-input-showPicker">showPicker</span>()</code></dt>
 
    <dd>
+    <p>Shows any applicable picker UI for <var>input</var>, so that the user can select a value.</p>
+
     <p>If <var>input</var> does not <span data-x="input-support-picker">support a picker</span>,
     this method does nothing.</p>
 
-    <p>Shows any applicable picker UI for <var>input</var>, so that the user can select a value.</p>
-
     <p>Throws an <span>"<code>InvalidStateError</code>"</span> <code>DOMException</code> if
     <var>input</var> is not <span data-x="concept-fe-mutable">mutable</span>.</p>
 
@@ -75083,10 +75078,10 @@ Demos:
 
    <dt><dfn selector><code data-x="selector-open">:open</code></dfn></dt>
    <dd>
-    <p>An <code>Element</code> matches the <code data-x="selector-open">:open</code>
-    <span>pseudo-class</span> if it matches one of the following:</p>
+    <p>The <code data-x="selector-open">:open</code> <span>pseudo-class</span> must any
+    <code>Element</code> falling into one of the following categories:</p>
 
-    <ol>
+    <ul>
      <li><p>A <code>details</code> element which has the <code
      data-x="attr-details-open">open</code> attribute.</p></li>
 
@@ -75098,7 +75093,7 @@ Demos:
 
      <li><p>An <code>input</code> element which <span data-x="input-support-picker">supports a
      picker</span> and whose picker is open.</p></li>
-    </ol>
+    </ul>
    </dd>
   </dl>