Fix HTML validation errors.

index.html

@@ -55,12 +55,12 @@ <h2>Terminology</h2>
     <p>
       The following terms are defined in
       <a href="https://webrtc.org/experiments/rtp-hdrext/abs-capture-time"><dfn>RTP Header Extension for Absolute Capture Time</dfn></a>:
-      <ul>
-        <li><a href="https://webrtc.org/experiments/rtp-hdrext/abs-capture-time#absolute-capture-timestamp"><dfn>absolute capture timestamp</dfn></a>
-        <li><a href="https://webrtc.org/experiments/rtp-hdrext/abs-capture-time#timestamp-interpolation"><dfn>timestamp interpolation</dfn></a>
-        <li><a href="https://webrtc.org/experiments/rtp-hdrext/abs-capture-time#estimated-capture-clock-offset"><dfn>estimated capture clock offset</dfn></a>
-      </ul>
     </p>
+    <ul>
+      <li><a href="https://webrtc.org/experiments/rtp-hdrext/abs-capture-time#absolute-capture-timestamp"><dfn>absolute capture timestamp</dfn></a></li>
+      <li><a href="https://webrtc.org/experiments/rtp-hdrext/abs-capture-time#timestamp-interpolation"><dfn>timestamp interpolation</dfn></a></li>
+      <li><a href="https://webrtc.org/experiments/rtp-hdrext/abs-capture-time#estimated-capture-clock-offset"><dfn>estimated capture clock offset</dfn></a></li>
+    </ul>
     <p>The process of <dfn>chaining</dfn> an operation to an <dfn>operations chain</dfn> is defined in [[WEBRTC]] Section 4.4.1.2.</p>
     <p>
       The {{EventHandler}} interface, representing a callback used for event handlers, is defined in [[!HTML]].
@@ -914,7 +914,6 @@ <h2>Dictionary {{RTCRtpContributingSource}} Members</h2>
             {{RTCRtpContributingSource.timestamp}} -
             <var>receiverCaptureTimestamp</var>.
           </p>
-          </p>
         </dd>
       </dl>
     </section>
@@ -928,7 +927,7 @@ <h3>
        Transferable Data Channels
      </h3>
      <p>This section extends {{RTCDataChannel}} by making it <a data-cite="!HTML/#transferable-objects">transferable</a>.</p>
-      This allows sending and receiving messages outside the context the connection was created, for instance in workers or third-party iframes.</p>
+      <p>This allows sending and receiving messages outside the context the connection was created, for instance in workers or third-party iframes.</p>
       <div>
       <p>The WebIDL changes are the following:
       <pre class="idl">
@@ -1049,7 +1048,6 @@ <h3>
           the transceiver is sending enrypted RTP header extensions as defined in
           [[CRYPTEX]].
         </p>
-        <div>
   <pre class="idl">
   partial interface RTCRtpTransceiver {
     readonly attribute boolean rtpHeaderEncryptionNegotiated;