Editorial: correct some minor wording issues

Closes #1476 and closes #1477.

fetch.bs

@@ -951,9 +951,9 @@ a <a>byte-case-insensitive</a> match for one of
  <li>`<code>Range</code>`.
 </ul>
 
-<div class="note no-backref">
+<div class=note>
  <p>These are headers that can be set by privileged APIs, and will be preserved if their associated
- request object is copied, but will be removed if the request is modified by unprivilaged APIs.
+ request object is copied, but will be removed if the request is modified by unprivileged APIs.
 
  <p>`<code>Range</code>` headers are commonly used by <a lt="download the hyperlink">downloads</a>
  and <a lt="resource fetch algorithm">media fetches</a>, although neither of these currently specify
@@ -2162,9 +2162,9 @@ string.
 <dfn for=response id=concept-response-range-requested-flag>range-requested flag</dfn>, which is
 initially unset.
 
-<p class=note>This is used to ensure to prevent a partial response from an earlier ranged request
-being provided to an API that didn't make a range request. See the flag's usage for a detailed
-description of the attack.
+<p class=note>This is used to prevent a partial response from an earlier ranged request being
+provided to an API that didn't make a range request. See the flag's usage for a detailed description
+of the attack.
 
 <p>A <a for=/>response</a> has an associated <dfn for=response>request-includes-credentials</dfn>
 (a boolean), which is initially true.
@@ -8372,6 +8372,7 @@ Jordan Stephens,
 Jörn Zaefferer,
 Joseph Pecoraro,
 Josh Matthews,
+jub0bs<!-- GitHub -->,
 Julian Krispel-Samsel,
 Julian Reschke,
 송정기 (Jungkee Song),