Run specfmt

source

@@ -87578,9 +87578,9 @@ dictionary <dfn dictionary>DragEventInit</dfn> : <span>MouseEventInit</span> {
    been used.</p>
 
    <p>Because of these security pitfalls, this feature is in the process of being removed from the
-   web platform. It is no longer available by default, because by default
-   documents are placed in an <span>origin</span>-<span data-x="agent cluster key">keyed</span> <span>agent cluster</span>, which
-   disables the <code data-x="dom-document-domain">document.domain</code> setter.</p>
+   web platform. It is no longer available by default, because by default documents are placed in an
+   <span>origin</span>-<span data-x="agent cluster key">keyed</span> <span>agent cluster</span>,
+   which disables the <code data-x="dom-document-domain">document.domain</code> setter.</p>
 
    <p>Instead, use <code data-x="dom-window-postMessage">postMessage()</code> or
    <code>MessageChannel</code> objects to communicate across origins in a safe manner.</p>
@@ -87787,11 +87787,10 @@ dictionary <dfn dictionary>DragEventInit</dfn> : <span>MouseEventInit</span> {
    </dd>
   </dl>
 
-  <p>By default, a <code>Document</code> is placed in an
-  <span>origin</span>-<span data-x="agent cluster key">keyed</span> <span>agent
-  cluster</span>. The <dfn http-header><code>Origin-Agent-Cluster</code></dfn>`
-  HTTP response header can be used to instead request placement in a
-  <span>site</span>-<span data-x="agent cluster key">keyed</span> <span>agent
+  <p>By default, a <code>Document</code> is placed in an <span>origin</span>-<span data-x="agent
+  cluster key">keyed</span> <span>agent cluster</span>. The <dfn
+  http-header><code>Origin-Agent-Cluster</code></dfn>` HTTP response header can be used to instead
+  request placement in a <span>site</span>-<span data-x="agent cluster key">keyed</span> <span>agent
   cluster</span>. This header is a <span data-x="http-structured-header">structured header</span>
   whose value must be a <span data-x="http-structured-header-boolean">boolean</span>.
   <ref>STRUCTURED-FIELDS</ref></p>
@@ -87802,16 +87801,16 @@ dictionary <dfn dictionary>DragEventInit</dfn> : <span>MouseEventInit</span> {
   false value (i.e., `<code data-x="">?0</code>`) will be ignored.</p>
 
   <p>The consequences of using this header are that <span w-nodev>the resulting
-  <code>Document</code>'s <span>agent cluster key</span> is its <span
-  data-x="obtain a site">site</span>, instead of the <span
-  data-x="concept-document-origin">origin</span>. In terms of observable effects, this means that</span>
-  <a href="#relaxing-the-same-origin-restriction">relaxing the same-origin restriction</a> using
-  <code data-x="dom-document-domain">document.domain</code> will work, while in
-  the default case it will do nothing. Likewise, it will be possible to send
-  <code>WebAssembly.Module</code> objects to cross-origin <code>Document</code>s
-  (if they are <span>same site</span>). Behind the scenes, this choice may
-  prevent user agents from allocating implementation-specific resources corresponding to
-  <span data-x="agent cluster">agent clusters</span> more efficiently, such as processes or threads.</p>
+  <code>Document</code>'s <span>agent cluster key</span> is its <span data-x="obtain a
+  site">site</span>, instead of the <span data-x="concept-document-origin">origin</span>. In terms
+  of observable effects, this means that</span> <a
+  href="#relaxing-the-same-origin-restriction">relaxing the same-origin restriction</a> using <code
+  data-x="dom-document-domain">document.domain</code> will work, while in the default case it will
+  do nothing. Likewise, it will be possible to send <code>WebAssembly.Module</code> objects to
+  cross-origin <code>Document</code>s (if they are <span>same site</span>). Behind the scenes, this
+  choice may prevent user agents from allocating implementation-specific resources corresponding to
+  <span data-x="agent cluster">agent clusters</span> more efficiently, such as processes or
+  threads.</p>
 
   <p>Note that within a <span>browsing context group</span>, the
   `<code>Origin-Agent-Cluster</code>` header can never cause same-origin <code>Document</code>
@@ -105331,9 +105330,9 @@ location.href = '#foo';</code></pre>
      <var>navigationParams</var>'s <span data-x="navigation-params-response">response</span>'s
      <span data-x="concept-response-header-list">header list</span>.</p></li>
 
-     <li><p>Let <var>requestsOAC</var> be false if <var>oacHeader</var> is not
-     null and <var>oacHeader</var>[0] is the <span
-     data-x="http-structured-header-boolean">boolean</span> false; otherwise true.</p></li>
+     <li><p>Let <var>requestsOAC</var> be false if <var>oacHeader</var> is not null and
+     <var>oacHeader</var>[0] is the <span data-x="http-structured-header-boolean">boolean</span>
+     false; otherwise true.</p></li>
 
      <li><p>If <var>navigationParams</var>'s <span
      data-x="navigation-params-reserved-environment">reserved environment</span> is a
@@ -106898,8 +106897,8 @@ new PaymentRequest(&hellip;); // Allowed to use
 
     <p>If the encompassing <span>agent cluster</span>'s <span>is origin-keyed</span> is true, then
     all the <code>Window</code> objects will be <span>same origin</span>, can reach each other
-    directly, and <code data-x="dom-document-domain">document.domain</code> will no-op.
-    This is the default case.</p>
+    directly, and <code data-x="dom-document-domain">document.domain</code> will no-op. This is the
+    default case.</p>
 
     <p class="note">Two <code>Window</code> objects that are <span>same origin</span> can be in
     different <span data-x="similar-origin window agent">similar-origin window agents</span>, for
@@ -106998,9 +106997,9 @@ new PaymentRequest(&hellip;); // Allowed to use
   of <span data-x="similar-origin window agent">similar-origin window agents</span>.</p>
 
   <p>An <dfn>agent cluster key</dfn> is a <span>site</span> or <span
-  data-x="concept-origin-tuple">tuple origin</span>. By default these will be
-  <a href="#origin-keyed-agent-clusters">origin-keyed agent clusters</a>, but
-  with developer action they can also be <span>site</span>-<span data-x="agent cluster key">keyed</span>.</p>
+  data-x="concept-origin-tuple">tuple origin</span>. By default these will be <a
+  href="#origin-keyed-agent-clusters">origin-keyed agent clusters</a>, but with developer action
+  they can also be <span>site</span>-<span data-x="agent cluster key">keyed</span>.</p>
 
   <p class="note">An equivalent formulation is that an <span>agent cluster key</span> can be a
   <span>scheme-and-host</span> or an <span>origin</span>.</p>