Correct location URL algorithm fragment handling

a876e5d made a typo and did not account for it potentially not being a URL.

Also remove a dangling reference to the removed body's transmitted bytes concept.

fetch.bs

@@ -2044,8 +2044,8 @@ or a <a for=/>URL</a>.
   only parse successfully if it is an <a>absolute-URL-with-fragment string</a>.
 
  <li>
-  <p>If <var>locationURL</var>'s <a for=url>fragment</a> is null, then set <var>locationURL</var>'s
-  <a for=url>fragment</a> to <var>requestFragment</var>.
+  <p>If <var>location</var> is a <a for=/>URL</a> whose <a for=url>fragment</a> is null, then set
+  <var>location</var>'s <a for=url>fragment</a> to <var>requestFragment</var>.
 
   <p class=note>This ensures that synthetic (indeed, all) responses follow the processing model for
   redirects defined by HTTP. [[HTTP-SEMANTICS]]
@@ -4821,9 +4821,6 @@ these steps:
         <ol>
          <li><p>Let <var>bytes</var> be the transmitted bytes.
 
-         <li><p>Increase <var>response</var>'s <a for=response>body</a>'s <a for=body>transmitted
-         bytes</a> with <var>bytes</var>' length.
-
          <li><p>Let <var>codings</var> be the result of <a>extracting header list values</a> given
          `<code>Content-Encoding</code>` and <var>response</var>'s <a for=response>header list</a>.
 
@@ -7358,6 +7355,7 @@ Tiancheng "Timothy" Gu,
 Tobie Langel,
 Tom Schuster,
 Tomás Aparicio,
+triple-underscore<!-- GitHub -->,
 保呂毅 (Tsuyoshi Horo),
 Tyler Close,
 Ujjwal Sharma,