fixs w3c#753 change playout delay to jitterbuffertarget

webrtc-stats.html

@@ -1470,13 +1470,13 @@ <h2>
                 <p>
                   There are various reasons why the jitter buffer delay might be increased to a higher value, such as
                   to achieve AV synchronization or because a
-                  <a href="https://w3c.github.io/webrtc-extensions/#dom-rtcrtpreceiver-playoutdelay">playoutDelay</a>
+                  <a href="https://w3c.github.io/webrtc-extensions/#rtcrtpreceiver-jitterbuffertarget">jitterbuffertarget</a>
                   was set on a RTCRtpReceiver. When using one of these mechanisms, it can be useful to keep track of
                   the minimal jitter buffer delay that could have been achieved, so WebRTC clients can track the amount
                   of additional delay that is being added.
                 </p><p>
                   This metric works the same way as {{jitterBufferTargetDelay}}, except that it is not affected by
-                  external mechanisms that increase the jitter buffer target delay, such as playoutDelay (see link above),
+                  external mechanisms that increase the jitter buffer target delay, such as jitterbuffertarget (see link above),
                   AV sync, or any other mechanisms. This metric is purely based on the network characteristics such
                   as jitter and packet loss, and can be seen as the minimum obtainable jitter buffer delay if no
                   external factors would affect it. The metric is updated every time {{jitterBufferEmittedCount}} is updated.