diff --git a/docs/manual/advanced-autoplugging.xml b/docs/manual/advanced-autoplugging.xml
index 5703a7922a..58889da771 100644
--- a/docs/manual/advanced-autoplugging.xml
+++ b/docs/manual/advanced-autoplugging.xml
@@ -29,7 +29,7 @@
- MIME-types as a way to identity streams
+ MIME-types as a way to identify streams
We have previously introduced the concept of capabilities as a way
for elements (or, rather, pads) to agree on a media type when
@@ -513,7 +513,7 @@ cb_typefound (GstElement *typefind,
By doing all this, we will be able to make a simple autoplugger that
can automatically setup a pipeline for any media type. In the example
- below, we will do this for audio only. However, we can also do this
+ above, we did this for audio only. However, we can also do this
for video to create a player that plays both audio and video.
-
+
Most plugins provide additional properties to provide more information
- about their configuration or to configure the element.
+ about their configuration or to configure the element.
gst-inspect is a useful tool to query the properties
of a particular element, it will also use property introspection to give
a short explanation about the function of the property and about the
- parameter types and ranges it supports. See the appendix for details
- about gst-inspect.
-
-
+ parameter types and ranges it supports. See
+
+ in the appendix for details about gst-inspect.
+
+
For more information about GObject
properties we recommend you read the .
- A
+ A
GstElement also provides various
GObject signals that can be used as a flexible
callback mechanism. Here, too, you can use gst-inspect
diff --git a/docs/manual/basics-pads.xml b/docs/manual/basics-pads.xml
index ee34f939ee..bdd7c18e30 100644
--- a/docs/manual/basics-pads.xml
+++ b/docs/manual/basics-pads.xml
@@ -216,7 +216,7 @@ link_to_multiplexer (GstPad *tolink_pad,
Dissecting capabilities
- A pads capabilities are described in a GstCaps
+ A pad's capabilities are described in a GstCaps
object. Internally, a GstCaps
will contain one or more audio/x-vorbis. The source pad will be used
to send raw (decoded) audio samples to the next element, with
- a raw audio mime-type (in this case,
- audio/x-raw-int
) The source pad will also
+ a raw audio mime-type (in this case,
+ audio/x-raw-float
). The source pad will also
contain properties for the audio samplerate and the amount of
channels, plus some more that you don't need to worry about
for now.
@@ -539,7 +539,7 @@ link_elements_with_filter (GstElement *element1, GstElement *element2)
This will force the data flow between those two elements to
a certain video format, width, height and framerate (or the linking
- will fail if that cannot be achieved in the context of the elments
+ will fail if that cannot be achieved in the context of the elements
involved). Keep in mind that when you use
gst_element_link_filtered () it will automatically create
a capsfilter element for you and insert it into
@@ -585,8 +585,10 @@ link_elements_with_filter (GstElement *element1, GstElement *element2)
See the API references for the full API of
- GstStructure and
- GstCaps.
+ GstStructure
+ and GstCaps.
diff --git a/docs/manual/intro-basics.xml b/docs/manual/intro-basics.xml
index 82ce35a935..b0c2806133 100644
--- a/docs/manual/intro-basics.xml
+++ b/docs/manual/intro-basics.xml
@@ -59,9 +59,9 @@
through one or more sink pads. Source and sink
elements have only source and sink pads, respectively. Data usually
means buffers (described by the GstBuffer
+ url="&URLAPI;gstreamer-GstBuffer.html">GstBuffer
object) and events (described by the
+ type="http" url="&URLAPI;gstreamer-GstEvent.html">
GstEvent object).
diff --git a/docs/manual/manual.xml b/docs/manual/manual.xml
index 0f336fa38b..af6466e6b8 100644
--- a/docs/manual/manual.xml
+++ b/docs/manual/manual.xml
@@ -158,14 +158,14 @@
Some parts of this part will serve mostly as an explanation of
how &GStreamer; works internally; they are not actually needed for
- actual application development. This includes chapter such as the
+ actual application development. This includes chapters such as the
ones covering scheduling, autoplugging and synchronization. Other
chapters, however, discuss more advanced ways of
pipeline-application interaction, and can turn out to be very useful
for certain applications. This includes the chapters on metadata,
querying and events, interfaces, dynamic parameters and pipeline
data manipulation.
-
+
&QUERYEVENTS;