Meta: correct markup as per Bikeshed output

Author: nidhijaju

fetch.bs

@@ -2777,7 +2777,6 @@ functionality.
 
   <p>If this operation succeeds, return the <a for=/>set</a> of <a for=/>IP addresses</a> and any
   additional <a>implementation-defined</a> information.
- </li>
 
  <li><p>Return failure.
 </ol>
@@ -4113,7 +4112,6 @@ true, and it's always for nested navigations. Otherwise, <var>response</var> is
    <dt>"<a for="embedder policy value"><code>require-corp</code></a>"
    <dd><p>Set <var>policy</var> to `<code>same-origin</code>`.
   </dl>
- </li>
 
  <li>
   <p>Switch on <var>policy</var>:
@@ -4366,7 +4364,6 @@ the response. [[!HTTP-CACHING]]
    <a for="fetch params">preloaded response candidate</a> is null, then set <var>fetchParams</var>'s
    <a for="fetch params">preloaded response candidate</a> to "<code>pending</code>".
   </ol>
- </li>
 
  <li>
   <p>If <var>request</var>'s <a for=request>header list</a>
@@ -4883,7 +4880,6 @@ steps:
    <li><p><a>Queue a fetch task</a> to run <var>processResponseEndOfBodyTask</var> with
    <var>fetchParams</var>'s <a for="fetch params">task destination</a>.
   </ol>
- </li>
 
  <li><p>If <var>fetchParams</var>'s <a for="fetch params">process response</a> is non-null, then
  <a>queue a fetch task</a> to run <var>fetchParams</var>'s
@@ -7985,7 +7981,6 @@ constructor steps are:
    <li><p>Set <a>this</a>'s <a for=Request>headers</a>'s <a for=Headers>guard</a> to
    "<code>request-no-cors</code>".
   </ol>
- </li>
 
  <li>
   <p>If <var>init</var> <a for=map>is not empty</a>, then:
@@ -8010,7 +8005,6 @@ constructor steps are:
    <li><p>Otherwise, <a for=Headers>fill</a> <a>this</a>'s <a for=Request>headers</a> with
    <var>headers</var>.
   </ol>
- </li>
 
  <li><p>Let <var>inputBody</var> be <var>input</var>'s <a for=Request>request</a>'s
  <a for=request>body</a> if <var>input</var> is a {{Request}} object; otherwise null.
@@ -8804,7 +8798,7 @@ resource — for non-<a>CORS requests</a> as well as <a>CORS
 requests</a> — and do not use `<code>Vary</code>`.
 
 
-<h3 class=no-num id=websocket-protocol oldids=websocket-connections,websocket-opening-handshake,fail-the-websocket-connection,the-websocket-connection-is-established>WebSockets</h2>
+<h3 class=no-num id=websocket-protocol oldids=websocket-connections,websocket-opening-handshake,fail-the-websocket-connection,the-websocket-connection-is-established>WebSockets</h3>
 
 <p>As part of establishing a connection, the {{WebSocket}} object initiates a special kind of
 <a for=/>fetch</a> (using a <a for=/>request</a> whose <a for=request>mode</a> is
@@ -8968,7 +8962,7 @@ particular at what stage you would like to receive a callback:
       <li><p>Otherwise, parse <var>contents</var> considering the metadata from <var>response</var>,
       and perform your own operations on it.
      </ol>
-    </li>
+   </ol>
   </div>
  </dd>
 
@@ -9018,7 +9012,7 @@ particular at what stage you would like to receive a callback:
       <a for=response>body</a>'s <a for=body>stream</a>, and process in an appropriate way for the
       MIME type identified by <a>extracting a MIME type</a> from <var>response</var>'s <a for=response>headers list</a>.
      </ol>
-    </li>
+   </ol>
   </div>
  </dd>