Editorial: relocate "stopped parsing" step for non-DOM documents

As pointed out in #125 (comment), it was quite hard to discover how the load event fired on iframes containing error documents or other "inline content that doesn't have a DOM". This was because the step that did this was, for some reason, located outside of the main list of algorithm steps. Update to follow the same pattern as used for media documents, of locating the step inline.

Author: domenic

source

@@ -111825,6 +111825,9 @@ new PaymentRequest(…); // Allowed to use
    the normal <code>Document</code> rendering rules, or mutate <var>document</var> until it
    represents the content the user agent wants to render.</p></li>
 
+   <li><p>Act as if the user agent had <span data-x="stop parsing">stopped parsing</span>
+   <var>document</var>.</p></li>
+
    <li><p>Return <var>document</var>.</p></li>
   </ol>
 
@@ -111839,11 +111842,6 @@ new PaymentRequest(&hellip;); // Allowed to use
   algorithm</span> from getting confused, and so are set to default values.</p>
   </div>
 
-  <div algorithm>
-  <p>Once the page has been set up, the user agent must act as if it had <span data-x="stop
-  parsing">stopped parsing</span>.</p>
-  </div>
-
 
   <h4 id="loading-documents">Finishing the loading process</h4>