fix p as children of ol, please check semantics

index.html

@@ -425,26 +425,26 @@ <h2>Attributes</h2>
                   <p>Update the underlying system about the new <var>target</var>,
                   or that there is no application preference if <var>target</var> is
                   <code>null</code>.</p>
-                </li>
-                <p>
-                  If <var>track</var> is synchronized with another
-                  {{RTCRtpReceiver}}'s track for
-                  <a data-cite="RFC5888#section-7">audio/video synchronization</a>,
-                  then the <a>user agent</a> SHOULD use the larger of the two receivers'
-                  {{RTCRtpReceiver/[[JitterBufferTarget]]}} for both receivers.
-                </p>
-                <p>
-                  When the underlying system is applying a jitter buffer target, it will
-                  continuously make sure that the actual jitter buffer target is clamped
-                  within the <a>minimum allowed target</a> and <a>maximum allowed
-                  target</a>.
-                  <p class="note">
-                    If the <a>user agent</a> ends up using a target different from the
-                    requested one (e.g. due to network conditions or physical memory
-                    constraints), this is not reflected in the
-                    {{RTCRtpReceiver/[[JitterBufferTarget]]}} internal slot.
+                  <p>
+                    If <var>track</var> is synchronized with another
+                    {{RTCRtpReceiver}}'s track for
+                    <a data-cite="RFC5888#section-7">audio/video synchronization</a>,
+                    then the <a>user agent</a> SHOULD use the larger of the two receivers'
+                    {{RTCRtpReceiver/[[JitterBufferTarget]]}} for both receivers.
                   </p>
-                </p>
+                  <p>
+                    When the underlying system is applying a jitter buffer target, it will
+                    continuously make sure that the actual jitter buffer target is clamped
+                    within the <a>minimum allowed target</a> and <a>maximum allowed
+                    target</a>.
+                    <p class="note">
+                      If the <a>user agent</a> ends up using a target different from the
+                      requested one (e.g. due to network conditions or physical memory
+                      constraints), this is not reflected in the
+                      {{RTCRtpReceiver/[[JitterBufferTarget]]}} internal slot.
+                    </p>
+                  </p>
+                </li>
                 <li>
                   <p>Modifying the jitter buffer target of the underlying system SHOULD
                   affect the internal audio or video buffering gradually in order not