pwd: discontinous event -> newsegment event

Fix a 0.8 leftover as mentioned on bug #621121.

diff --git a/docs/pwg/advanced-clock.xml b/docs/pwg/advanced-clock.xml
index 85054400a9534de111234bf28d7a970f39612971..4f8ae39b44c4839f1b571377607a58237ed56841 100644 (file)
--- a/docs/pwg/advanced-clock.xml
+++ b/docs/pwg/advanced-clock.xml
@@ -59,7 +59,7 @@
          element will be regarded as the source element for this discussion.
        </para>
       </footnote> 
-      First, the source element sends a discontinuous event. This event carries information
+      First, the source element sends a newsegment event. This event carries information
       about the current relative time of the next sample. This relative time is
       arbitrary, but it must be consistent with the timestamp that will be
       placed in buffers. It is expected to be the relative time to the start
@@ -81,7 +81,7 @@
     <para>
       If the stream is seeked, the next samples sent will have a timestamp that
       is not adjusted with the element time. Therefore, the source element must
-      send a discontinuous event.
+      send a newsegment event.
     </para>
   </sect1>
   <sect1 id="section-clock-obligations-of-each-element" xreflabel="Obligations
@@ -101,14 +101,14 @@
        Source elements (or parsers of formats that provide notion of time, such
        as MPEG, as explained above) must place a timestamp in each buffer that
        they deliver. The origin of the time used is arbitrary, but it must
-       match the time delivered in the discontinuous event (see below).
+       match the time delivered in the newsegment event (see below).
        However, it is expected that the origin is the origin of the media
        stream.
       </para>
       <para>
        In order to initialize the element time of the rest of the pipeline, a
-       source element must send a discontinuous event before starting to play.
-       In addition, after seeking, a discontinuous event must be sent, because
+       source element must send a newsegment event before starting to play.
+       In addition, after seeking, a newsegment event must be sent, because
        the timestamp of the next element does not match the element time of the
        rest of the pipeline.
       </para>

diff --git a/docs/pwg/building-chainfn.xml b/docs/pwg/building-chainfn.xml
index 747ff6339debb57a73a470272491562969d0fcd5..a9460804fc319b2c1e6e28e192a0b179d8999b94 100644 (file)
--- a/docs/pwg/building-chainfn.xml
+++ b/docs/pwg/building-chainfn.xml
@@ -47,7 +47,7 @@ gst_my_filter_change_state (GstElement * element, GstStateChange transition)
     that buffers are not always writeable. In more advanced elements (the ones
     that do event processing), you may want to additionally specify an event
     handling function, which will be called when stream-events are sent (such
-    as end-of-stream, discontinuities, tags, etc.).
+    as end-of-stream, newsegment, tags, etc.).
   </para>
   <programlisting>
 static void