Editorial: always pass oldParent to removing steps

dom.bs

@@ -2866,11 +2866,12 @@ within a <var>parent</var>, run these steps:
 
 <p><a lt="Other applicable specifications">Specifications</a> may define
 <dfn export id=concept-node-remove-ext>removing steps</dfn> for all or some <a for=/>nodes</a>. The
-algorithm is passed <var ignore>removedNode</var>, and optionally <var ignore>oldParent</var>, as
-indicated in the <a for=/>remove</a> algorithm below.
+algorithm is passed a <a for=/>node</a> <var ignore>removedNode</var> and a
+<a for=/>node</a>-or-null <var ignore>oldParent</var>, as indicated in the <a for=/>remove</a>
+algorithm below.
 
-<p>To <dfn export id=concept-node-remove>remove</dfn> a <var>node</var>, with an optional
-<i>suppress observers flag</i>, run these steps:
+<p>To <dfn export id=concept-node-remove>remove</dfn> a <a for=/>node</a> <var>node</var>, with an
+optional <i>suppress observers flag</i>, run these steps:
 
 <ol>
  <li><p>Let <var>parent</var> be <var>node</var>'s <a for=tree>parent</a>.
@@ -2938,7 +2939,7 @@ indicated in the <a for=/>remove</a> algorithm below.
   <a>shadow-including tree order</a>, then:
 
   <ol>
-   <li><p>Run the <a>removing steps</a> with <var>descendant</var>.
+   <li><p>Run the <a>removing steps</a> with <var>descendant</var> and null.
 
    <li><p>If <var>descendant</var> is <a for=Element>custom</a> and <var>isParentConnected</var>
    is true, then <a>enqueue a custom element callback reaction</a> with <var>descendant</var>,