manual: no more new-decoded-pad

diff --git a/docs/manual/basics-elements.xml b/docs/manual/basics-elements.xml
index 33b805f..8f81493 100644 (file)
--- a/docs/manual/basics-elements.xml
+++ b/docs/manual/basics-elements.xml
@@ -557,7 +557,7 @@ main (int   argc,
       automatically, so it's usually only necessary to set the state of the
       top-level pipeline to start up the pipeline or shut it down. However,
       when adding elements dynamically to an already-running pipeline, e.g.
-      from within a "pad-added" or "new-decoded-pad" signal callback, you
+      from within a "pad-added" signal callback, you
       need to set it to the desired target state yourself using
       <function>gst_element_set_state ()</function> or
       <function>gst_element_sync_state_with_parent ()</function>.

diff --git a/docs/manual/basics-pads.xml b/docs/manual/basics-pads.xml
index 91c6a5a..c490a25 100644 (file)
--- a/docs/manual/basics-pads.xml
+++ b/docs/manual/basics-pads.xml
@@ -120,7 +120,7 @@ main (int   argc,
       <!-- example-end pad.c d --></programlisting>
       <para>
         It is not uncommon to add elements to the pipeline only from within
-        the "pad-added" or "new-decoded-pad" callback. If you do this, don't
+        the "pad-added" callback. If you do this, don't
         forget to set the state of the newly-added elements to the target
         state of the pipeline using
         <function>gst_element_set_state ()</function> or