Editorial: move owner set manipulation into discarding a document

Fixes #2533.

source

@@ -78688,11 +78688,11 @@ callback <dfn>FrameRequestCallback</dfn> = void (<span>DOMHighResTimeStamp</span
    <li><p>Lose the strong reference from the <code>Document</code>'s <span
    data-x="concept-document-bc">browsing context</span> to the <code>Document</code>.</p></li>
 
-  </ol>
+   <li><p><span data-x="list remove">Remove</span> the <code>Document</code> object from the
+   <span>owner set</span> of each <code>WorkerGlobalScope</code> object whose set <span
+   data-x="list contains">contains</span> that <code>Document</code> object.</p></li>
 
-  <p class="note">Whenever a <code>Document</code> object is <span data-x="discard a
-  Document">discarded</span>, it is also removed from the <span>owner set</span> of each worker
-  whose set contains that <code>Document</code>.</p>
+  </ol>
 
   <p>When <dfn data-export="">a <em>browsing context</em> is discarded</dfn>, the strong reference
   from the user agent itself to the <span>browsing context</span> must be severed, and all the
@@ -97070,11 +97070,6 @@ interface <dfn>SharedWorkerGlobalScope</dfn> : <span>WorkerGlobalScope</span> {
   <var>worker global scope</var>. This list includes the implicit <code>MessagePort</code> in the
   case of <span data-x="DedicatedWorkerGlobalScope">dedicated workers</span>.</p>
 
-  <p>Whenever a <code>Document</code> object is <span data-x="discard a Document">discarded</span>,
-  it must be <span data-x="list remove">removed</span> from the <span>owner set</span> of each
-  <code>WorkerGlobalScope</code> object whose set <span data-x="list contains">contains</span> that
-  <code>Document</code> object.</p>
-
   <p id="list-of-relevant-document-objects-to-add">Given an <span>environment settings object</span>
   <var>o</var> when creating or obtaining a worker, the <dfn>relevant owner to add</dfn> depends on
   the type of <span data-x="concept-settings-object-global">global object</span> specified by