[html5] r8442 - [e] (0) typo in the media section Fixing https://www.w3.org/Bugs/Public/show_bug [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2014-01-29 18:36:53 -0800 (Wed, 29 Jan 2014)
New Revision: 8442

Modified:
   complete.html
   index
   source
Log:
[e] (0) typo in the media section
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=24435
Affected topics: Video Text Tracks

Modified: complete.html
===================================================================
--- complete.html	2014-01-30 02:35:28 UTC (rev 8441)
+++ complete.html	2014-01-30 02:36:53 UTC (rev 8442)
@@ -30711,7 +30711,7 @@
   particular, using the <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> event would be less
   appropriate as it would require doing work even when the cues haven't changed, and, more
   importantly, would introduce a higher latency between when the metatata cues become active and
-  when the display is updated, this <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> events
+  when the display is updated, since <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> events
   are rate-limited.)</p>
 
 

Modified: index
===================================================================
--- index	2014-01-30 02:35:28 UTC (rev 8441)
+++ index	2014-01-30 02:36:53 UTC (rev 8442)
@@ -30711,7 +30711,7 @@
   particular, using the <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> event would be less
   appropriate as it would require doing work even when the cues haven't changed, and, more
   importantly, would introduce a higher latency between when the metatata cues become active and
-  when the display is updated, this <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> events
+  when the display is updated, since <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> events
   are rate-limited.)</p>
 
 

Modified: source
===================================================================
--- source	2014-01-30 02:35:28 UTC (rev 8441)
+++ source	2014-01-30 02:36:53 UTC (rev 8442)
@@ -33100,7 +33100,7 @@
   particular, using the <code data-x="event-media-timeupdate">timeupdate</code> event would be less
   appropriate as it would require doing work even when the cues haven't changed, and, more
   importantly, would introduce a higher latency between when the metatata cues become active and
-  when the display is updated, this <code data-x="event-media-timeupdate">timeupdate</code> events
+  when the display is updated, since <code data-x="event-media-timeupdate">timeupdate</code> events
   are rate-limited.)</p>