Editorial changes in the mode definition.

Author: bvandersloot-mozilla

fetch.bs

@@ -41,6 +41,10 @@ urlPrefix:https://tc39.es/ecma262/#;type:dfn;spec:ecma-262
     url:sec-list-and-record-specification-type;text:Record
 </pre>
 
+<pre class=link-defaults>
+  spec:infra; type:dfn; text:user agent
+</pre>
+
 <pre class=biblio>
 {
     "HTTP": {
@@ -1799,13 +1803,18 @@ Unless stated otherwise, it is "<code>no-cors</code>".
   <dd>This is a special mode used only when <a>navigating</a> between documents.
 
   <dt>"<code>unsafe-no-cors</code>"
-  <dd>This is a special mode for the <a>host environment</a> to use internally to wittingly make
+  <dd>This is a special mode for the [=user agent=] to use internally to wittingly make
   requests that are unsafe. It restricts requests to using <a>CORS-safelisted methods</a> and
-  <a>CORS-safelisted request-headers</a>. However, the request will not be required to pass a
-  <a>cross-origin resource policy check</a> or to test if
-  <a>Cross-Origin-Embedder-Policy allows credentials</a>. Additionally, upon success a fetch will
-  return a <a>cors filtered response</a>. However, a request with this mode cannot
-  use <a>service-workers mode</a> "<code>all</code>".
+  <a>CORS-safelisted request-headers</a> and a request with this mode cannot use
+  <a>service-workers mode</a> "<code>all</code>". However, the request will not be required to
+  pass a <a>cross-origin resource policy check</a> or to test if
+  <a>Cross-Origin-Embedder-Policy allows credentials</a>. Upon success a fetch will
+  return a <a>cors filtered response</a>.
+
+  <p class=warning> Using <a for=/>request</a> <a for=request>mode</a> "<code>unsafe-no-cors</code>"
+  is even more discouraged and unsafe than "<code>no-cors</code>". Any use of this mode must be in an
+  <a>agent cluster</a> associated with the <a>host environment</a> itself to isolate its results from
+  misuse. This <a for=request>mode</a> is deliberately not exposed in the {{RequestMode}}.
 
   <dt>"<code>websocket</code>"
   <dd>This is a special mode used only when
@@ -1815,10 +1824,7 @@ Unless stated otherwise, it is "<code>no-cors</code>".
  <p>Even though the default <a for=/>request</a> <a for=request>mode</a> is "<code>no-cors</code>",
  standards are highly discouraged from using it for new features. It is rather unsafe.
 
- <p class=warning> Using <a for=/>request</a> <a for=request>mode</a> "<code>unsafe-no-cors</code>"
- is even more discouraged and unsafe than "<code>no-cors</code>". Any use of this mode must be in an
- <a>agent cluster</a> associated with the <a>host environment</a> itself to isolate its results from
- misuse. This <a for=request>mode</a> is deliberately not exposed in the {{RequestMode}}.
+
 </div>
 
 <p>A <a for=/>request</a> has an associated