From 86c1d709b599345871d8b654d57ce50438e5c61d Mon Sep 17 00:00:00 2001
From: Domenic Denicola <d@domenic.me>
Date: Wed, 14 Aug 2019 13:02:48 -0400
Subject: [PATCH] Editorial tweaks

---
 source | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/source b/source
index 9f3792c5dad..88a4f2135ef 100644
--- a/source
+++ b/source
@@ -78164,6 +78164,7 @@ dictionary <dfn>DragEventInit</dfn> : <span>MouseEventInit</span> {
   <ol>
    <li><p>Let <var>browsingContext</var> be the result of <span>creating a new browsing
    context</span> with <var>element</var>'s <span>node document</span>, and <var>element</var>'s
+   <span>node document</span>'s <span data-x="concept-document-bc">browsing context</span>'s
    <span>top-level browsing context</span>'s <span data-x="tlbc group">group</span>.</p></li>
 
    <li><p>Set <var>element</var>'s <span>nested browsing context</span> to
@@ -90318,9 +90319,9 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
   data-x="concept-global-object-realm">realms</span> that can synchronously access each other, and
   thus needs to run in a single execution thread.</p>
 
-  <p class="note">Two <code>Window</code> objects that have the same <span>agent</span> does not
+  <p class="note">Two <code>Window</code> objects having the same <span>agent</span> does not
   indicate they can directly access all objects created in each other's realms. They would have to
-  be in <span>same origin-domain</span>, see <span>IsPlatformObjectSameOrigin</span>.</p>
+  be <span>same origin-domain</span>; see <span>IsPlatformObjectSameOrigin</span>.</p>
 
   <p>Until such a time that this standard has a better handle on lifetimes, it defines four types of
   <span data-x="agent">agents</span> that user agents must allocate at the appropriate time.</p>
@@ -90374,6 +90375,13 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
   in particular among which <span data-x="agent">agents</span> the backing data of
   <code>SharedArrayBuffer</code> objects can be shared.</p>
 
+  <p class="note">Conceptually, the <span>agent cluster</span> concept is an
+  architecture-independent, idealized "process boundary" that groups together multiple "threads"
+  (<span data-x="agent">agents</span>). The <span data-x="agent cluster">agent clusters</span>
+  defined by the specification are generally more restrictive than the actual process boundaries
+  implemented in user agents. By enforcing these idealized divisions at the specification level, we
+  ensure that web developers see interoperable behavior with regard to shared memory, even in the
+  face of varying and changing user agent process models.</p>
   <p>A <dfn data-export="">scheme-and-site</dfn> is a <span>tuple</span> of a <span
   data-x="concept-url-scheme">scheme</span> and a <span data-x="concept-domain">domain</span>.</p>
 
@@ -90414,8 +90422,8 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
   <p>A <dfn data-export="">similar-origin window agent</dfn> is an <span>agent</span> whose
   [[CanBlock]] is false. </p>
 
-  <p class="note">All global objects that use this agent all have the a similar <span>origin</span>
-  and are allocated via the <span data-x="obtain-similar-origin-window-agent">obtain similar-origin
+  <p class="note">All global objects that use this agent all have a similar <span>origin</span> and
+  are allocated via the <span data-x="obtain-similar-origin-window-agent">obtain similar-origin
   window agent</span> algorithm.</p>
 
   <p>To <dfn data-x="obtain-browsing-agent-cluster">obtain a browsing context agent cluster</dfn>,
@@ -90438,13 +90446,6 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
    <li><p>Return <var>group</var>'s <span>agent cluster map</span>[<var>key</var>].</p></li>
   </ol>
 
-  <p class="note">Conceptually, the <span>agent cluster</span> concept is an
-  architecture-independent, idealized "process boundary" that groups together multiple "threads"
-  (<span data-x="agent">agents</span>). The <span data-x="agent cluster">agent clusters</span>
-  defined by the specification are generally more restrictive than the actual process boundaries
-  implemented in user agents. By enforcing these idealized divisions at the specification level, we
-  ensure that web developers see interoperable behavior with regard to shared memory, even in the
-  face of varying and changing user agent process models.</p>
 
   <p>A <span>similar-origin window agent</span>, <span>dedicated worker agent</span>, <span>shared
   worker agent</span>, or <span>service worker agent</span>, <var>agent</var>, <span>can share