Issue #181 - redefine section 3.1 in terms of Fetch

Author: miketaylr

index.html

@@ -12,7 +12,7 @@
     github: "https://github.com/w3c/network-error-logging/",
     shortname: "network-error-logging",
     specStatus: "ED",
-    xref: ["network-reporting", "fetch", "hr-time", "html", "referrer-policy", "reporting", "resource-timing", "secure-contexts", "url"],
+    xref: ["network-reporting", "fetch", "hr-time", "html", "mixed-content", "referrer-policy", "reporting", "resource-timing", "secure-contexts", "url"],
     editors: [{
       name: "Douglas Creager",
       url: "https://dcreager.net/",
@@ -117,38 +117,30 @@ <h2>Network requests</h2>
 
       <p>
       A <dfn data-lt="network requests">network request</dfn> occurs when the
-      user agent must use the network to service a single
-      <dfn data-cite="RFC9110#core.semantics">request</dfn>.
+      user agent must use the network to service a single [=request=].
       </p>
 
       <p>
-      If the user agent can service a <a>request</a> out of a local
-        cache, that <a>request</a> MUST NOT result in a <a>network
-        request</a>.
+      If the user agent can service a [=request=] out of a local cache, that
+      [=request=] MUST NOT result in a <a>network request</a>.
       </p>
 
       <p>
-      If the user agent follows [=redirect status|redirects=] as part of a [=navigate|navigation=],
-      there MUST be separate <a>network requests</a> for each <a>request</a> in
-      the redirect chain.
+      If the user agent follows [=redirect status|redirects=] as part of a
+      [=navigate|navigation=], there MUST be separate <a>network requests</a>
+      for each <a>request</a> in the redirect chain.
       </p>
 
       <p>
-      A <a>request</a> MUST NOT result in a <a>network request</a> if the user
-      agent is known to be offline (i.e., when <code>navigator.</code>{{NavigatorOnLine/onLine}} returns
-      <code>false</code>).
+      A [=request=] MUST NOT result in a <a>network request</a> if the user
+      agent is known to be offline (i.e., when <code>navigator.</code>
+      {{NavigatorOnLine/onLine}} returns <code>false</code>).
       </p>
 
       <p>
-      A <a>request</a> MUST NOT result in a <a>network request</a> if it is
-      blocked due to mixed content or CORS failures.  Any <a>CORS-preflight
-        request</a> MUST result in its own <a>network request</a>.
-      </p>
-
-      <p class="note">
-      For user agents that service <a>requests</a> according to the [[FETCH]]
-      standard, a <a>network request</a> corresponds to one execution of the
-      <a data-cite="FETCH#http-network-fetch">HTTP-network fetch</a> algorithm.
+      A [=request=] MUST NOT result in a <a>network request</a> if it is
+      blocked due to [=mixed content=] or [=CORS protocol|CORS=] failures. Any
+      [=CORS-preflight request=] MUST result in its own <a>network request</a>.
       </p>
 
       <p>
@@ -160,9 +152,9 @@ <h2>Network requests</h2>
       <ol>
         <li>
           <dfn>DNS resolution</dfn>: The user agent uses the Domain Name System
-          [[RFC1034]] to resolve a domain name into an IP address of a
+          [[RFC1034]] to resolve a domain name into an [=IP address=] of a
           <dfn data-cite="RFC9110#core.semantics">server</dfn> can that service
-          HTTP requests to that domain.
+          HTTP [=requests=] to that domain.
         </li>
 
         <li>
@@ -173,8 +165,8 @@ <h2>Network requests</h2>
 
         <li>
           <dfn>Transmission of request and response</dfn>: Once the secure
-          channel is established, the user agent can transmit the HTTP request,
-          and receive the response from the <a>server</a>.
+          channel is established, the user agent can transmit the HTTP
+          [=request=], and receive the [=response=] from the <a>server</a>.
         </li>
       </ol>
 
@@ -186,8 +178,8 @@ <h2>Network requests</h2>
       to the same domain. Similarly, HTTP
       <a data-cite="RFC9112#persistent.connections">persistent connections</a>
       allow open connections to be shared for multiple requests to the same
-      <a>origin</a>. However, if multiple <a>phases</a> occur, they will occur
-      in the above order.
+      [=network partition key=]. However, if multiple <a>phases</a> occur, they
+      will occur in the above order.
       </p>
 
       <p class="ednote">