We are currently experiencing downtime impacting viewing & cloning the Mesa repo, and some GitLab pages returning 503. Please see #freedesktop on IRC for more updates.

Commit 53ae1b2c authored by Sebastian Rasmussen's avatar Sebastian Rasmussen Committed by Tim-Philipp Müller

docs: Fix typos in function/object descriptions

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=720029
parent e8ecf3c4
......@@ -214,7 +214,7 @@ videotestsrc ! xvimagesink
- sink pushes RECONFIGURE event upstream
- src receives the RECONFIGURE event and marks renegotiation
- On the next buffer push, the source renegotiates the caps and the
bufferpool. The sink will put the new new prefered format high in the list
bufferpool. The sink will put the new new preferred format high in the list
of caps it returns from its caps query.
videotestsrc ! queue ! xvimagesink
......
......@@ -212,7 +212,7 @@ the buffer (see part-negotiation.txt).
When an element pad receives a CAPS event, it has to check if it understand the
media type. The element must refuse following buffers if the media type
preceeding it was not accepted.
preceding it was not accepted.
Both gst_pad_push() and gst_pad_pull_range() have a return value indicating whether
the operation succeeded. An error code means that no more data should be sent
......
......@@ -38,15 +38,15 @@ The main reason for adding these extra progress notifications is twofold:
have at least DNS resolving and server connections and requests be well
defined.
2) To make the state changes non-blocking and cancelable.
2) To make the state changes non-blocking and cancellable.
Currently state changes such as going to the READY or PAUSED state often do
blocking calls such as resolving DNS or connecting to a remote server. These
operations often block the main thread and are often not cancelable, causing
operations often block the main thread and are often not cancellable, causing
application lockups.
We would like to make the state change function, instead, start a separate
thread that performs the blocking operations in a cancelable way. When going
thread that performs the blocking operations in a cancellable way. When going
back to the NULL state, all pending operations would be canceled immediately.
For downward state changes, we want to let the application implement its own
......@@ -143,7 +143,7 @@ Messages
- "code", G_TYPE_STRING
A generic extensible string that can be used to programatically determine the
A generic extensible string that can be used to programmatically determine the
action that is in progress. Some standard predefined codes will be
defined.
......@@ -176,7 +176,7 @@ Implementation
Elements should not do blocking operations from the state change function.
Instead, elements should post an appropriate progress message with the right
code and of type GST_PROGRESS_TYPE_START and then start a thread to perform
the blocking calls in a cancelable manner.
the blocking calls in a cancellable manner.
It is highly recommended to only start async operations from the READY to PAUSED
state and onwards and not from the NULL to READY state. The reason for this is
......
......@@ -73,7 +73,7 @@ This value is monotonically increasing at the rate of the clock.
Timestamps
~~~~~~~~~~
The GstBuffer timestamps and the preceeding SEGMENT event (See
The GstBuffer timestamps and the preceding SEGMENT event (See
part-streams.txt) define a transformation of the buffer timestamps to
running_time as follows:
......@@ -82,7 +82,7 @@ The following notation is used:
B: GstBuffer
- B.timestamp = buffer timestamp (GST_BUFFER_PTS or GST_BUFFER_DTS)
S: SEGMENT event preceeding the buffers.
S: SEGMENT event preceding the buffers.
- S.start: start field in the SEGMENT event. This is the lowest allowed
timestamp.
- S.stop: stop field in the SEGMENT event. This is the highers allowed
......@@ -130,7 +130,7 @@ As we have seen, we can get a running_time:
C.running_time = absolute_time - base_time
- using the buffer timestamp and the preceeding SEGMENT event as (assuming
- using the buffer timestamp and the preceding SEGMENT event as (assuming
positive playback rate):
B.running_time = (B.timestamp - (S.start + S.offset)) / ABS (S.rate) + S.base
......@@ -187,7 +187,7 @@ Additional fields in the SEGMENT are used:
- S.time: time field in the SEGMENT event. This the stream-time of S.start
- S.applied_rate: The rate already applied to the stream.
Stream time is calculated using the buffer times and the preceeding SEGMENT
Stream time is calculated using the buffer times and the preceding SEGMENT
event as follows:
stream_time = (B.timestamp - S.start) * ABS (S.applied_rate) + S.time
......
......@@ -152,7 +152,7 @@ information.
When the SKIP flag is set, frames can be dropped in the elements. If S is the
speedup factor, a good algorithm for implementing frame skipping is to send audio in
chunks of Nms (usualy 300ms is good) and then skip ((S-1) * Nns) of audio data.
chunks of Nms (usually 300ms is good) and then skip ((S-1) * Nns) of audio data.
For the video we send only the keyframes in the (S * Nns) interval. In this
case, the demuxer would scale the timestamps and would set an applied rate of S.
......
......@@ -207,7 +207,7 @@
the file on the server.
</para>
<para>
In this case, buffering messages will be emited as usual when the
In this case, buffering messages will be emitted as usual when the
requested range is not within the downloaded area + buffersize. The
buffering message will also contain an indication that incremental
download is being performed. This flag can be used to let the application
......@@ -233,7 +233,7 @@
</para>
<para>
This mode is suitable for all live streams. As with the incremental
download mode, buffering messages are emited along with an indication
download mode, buffering messages are emitted along with an indication
that timeshifting download is in progress.
</para>
</sect1>
......@@ -246,7 +246,7 @@
a queue (such as a jitterbuffer) or by other means (in the audiosink).
</para>
<para>
Buffering messages can be emited in those live pipelines as well and
Buffering messages can be emitted in those live pipelines as well and
serve as an indication to the user of the latency buffering. The
application usually does not react to these buffering messages with a
state change.
......
......@@ -131,7 +131,7 @@
<title>Buffer stream-time</title>
<para>
The buffer stream-time, also known as the position in the stream,
is calculated from the buffer timestamps and the preceeding SEGMENT
is calculated from the buffer timestamps and the preceding SEGMENT
event. It represents the time inside the media as a value between
0 and the total duration of the media.
</para>
......
......@@ -76,7 +76,7 @@ Plugin development
loop based
buffers
metadata
subbufers
subbuffers
adding pads
libraries
plugin registry
......
......@@ -125,7 +125,7 @@
<sect2>
<title>Parser/Decoder/Encoder elements </title>
<para>
Parser/Decoder elements must use the incomming timestamps and transfer
Parser/Decoder elements must use the incoming timestamps and transfer
those to the resulting output buffers. They are allowed to interpolate
or reconstruct timestamps on missing input buffers when they can.
</para>
......@@ -137,7 +137,7 @@
Demuxer elements can usually set the timestamps stored inside the media
file onto the outgoing buffers. They need to make sure that outgoing
buffers that are to be played at the same time have the same
running-time. Demuxers also need to take into account the incomming
running-time. Demuxers also need to take into account the incoming
timestamps on buffers and use that to calculate an offset on the outgoing
buffer timestamps.
</para>
......@@ -146,8 +146,8 @@
<sect2>
<title>Muxer elements</title>
<para>
Muxer elements should use the incomming buffer running-time to mux the
different streams together. They should copy the incomming running-time
Muxer elements should use the incoming buffer running-time to mux the
different streams together. They should copy the incoming running-time
to the outgoing buffers.
</para>
</sect2>
......
......@@ -463,7 +463,7 @@ gst_my_filter_chain (GstPad *pad,
to reconfigure its caps by doing a new query for the allowed caps and then
choosing a new caps. The element that sends out the RECONFIGURE event
would influence the selection of the new caps by returning the new
prefered caps from its GST_QUERY_CAPS query function. The RECONFIGURE
preferred caps from its GST_QUERY_CAPS query function. The RECONFIGURE
event will set the GST_PAD_FLAG_NEED_RECONFIGURE on all pads that it
travels over.
</para>
......@@ -477,7 +477,7 @@ gst_my_filter_chain (GstPad *pad,
Elements that want to propose a new format upstream need to first
check if the new caps are acceptable upstream with an ACCEPT_CAPS
query. Then they would send a RECONFIGURE event and be prepared to
answer the CAPS query with the new prefered format. It should be
answer the CAPS query with the new preferred format. It should be
noted that when there is no upstream element that can (or wants)
to renegotiate, the element needs to deal with the currently
configured format.
......
......@@ -34,7 +34,7 @@ G_BEGIN_DECLS
*
* Opaque atomic data queue.
*
* Use the acessor functions to get the stored values.
* Use the accessor functions to get the stored values.
*/
typedef struct _GstAtomicQueue GstAtomicQueue;
......
......@@ -408,7 +408,7 @@ gst_bin_class_init (GstBinClass * klass)
* @bin: the #GstBin
*
* Will be emitted when the bin needs to perform latency calculations. This
* signal is only emited for toplevel bins or when async-handling is
* signal is only emitted for toplevel bins or when async-handling is
* enabled.
*
* Only one signal handler is invoked. If no signals are connected, the
......
......@@ -71,7 +71,7 @@
* produced so far. For compressed data, it could be the byte offset in a
* source or destination file. Likewise, the end offset will be the offset of
* the end of the buffer. These can only be meaningfully interpreted if you
* know the media type of the buffer (the preceeding CAPS event). Either or both
* know the media type of the buffer (the preceding CAPS event). Either or both
* can be set to #GST_BUFFER_OFFSET_NONE.
*
* gst_buffer_ref() is used to increase the refcount of a buffer. This must be
......@@ -1281,7 +1281,7 @@ gst_buffer_get_sizes_range (GstBuffer * buffer, guint idx, gint length,
/**
* gst_buffer_resize:
* @buffer: a #GstBuffer.
* @offset: the offset adjustement
* @offset: the offset adjustment
* @size: the new size or -1 to just adjust the offset
*
* Set the offset and total size of the memory blocks in @buffer.
......@@ -1310,7 +1310,7 @@ gst_buffer_set_size (GstBuffer * buffer, gssize size)
* @buffer: a #GstBuffer.
* @idx: an index
* @length: a length
* @offset: the offset adjustement
* @offset: the offset adjustment
* @size: the new size or -1 to just adjust the offset
*
* Set the total size of the @length memory blocks starting at @idx in
......@@ -1997,7 +1997,7 @@ gst_buffer_remove_meta (GstBuffer * buffer, GstMeta * meta)
* Retrieve the next #GstMeta after @current. If @state points
* to %NULL, the first metadata is returned.
*
* @state will be updated with an opage state pointer
* @state will be updated with an opaque state pointer
*
* Returns: (transfer none): The next #GstMeta or %NULL when there are
* no more items.
......
......@@ -319,7 +319,7 @@ void gst_buffer_extract_dup (GstBuffer *buffer, gsize offset,
*
* Increases the refcount of the given buffer by one.
*
* Note that the refcount affects the writeability
* Note that the refcount affects the writability
* of @buf and its metadata, see gst_buffer_is_writable().
* It is important to note that keeping additional references to
* GstBuffer instances can potentially increase the number
......
......@@ -66,7 +66,7 @@ typedef gboolean (*GstBufferListFunc) (GstBuffer **buffer, guint idx,
*
* Increases the refcount of the given buffer list by one.
*
* Note that the refcount affects the writeability of @list and its data, see
* Note that the refcount affects the writability of @list and its data, see
* gst_buffer_list_make_writable(). It is important to note that keeping
* additional references to GstBufferList instances can potentially increase
* the number of memcpy operations in a pipeline.
......
......@@ -650,7 +650,7 @@ gst_caps_append_structure_full (GstCaps * caps, GstStructure * structure,
* @caps: the #GstCaps to remove from
* @idx: Index of the structure to remove
*
* removes the stucture with the given index from the list of structures
* removes the structure with the given index from the list of structures
* contained in @caps.
*/
void
......
......@@ -411,7 +411,7 @@ gst_caps_features_free (GstCapsFeatures * features)
* |[
* GST_LOG ("features is %" GST_PTR_FORMAT, features);
* ]|
* This prints the features in human readble form.
* This prints the features in human readable form.
*
* Free-function: g_free
*
......
......@@ -100,7 +100,7 @@ gst_child_proxy_default_get_child_by_name (GstChildProxy * parent,
/**
* gst_child_proxy_get_child_by_name:
* @parent: the parent object to get the child from
* @name: the childs name
* @name: the child's name
*
* Looks up a child element by the given name.
*
......@@ -125,7 +125,7 @@ gst_child_proxy_get_child_by_name (GstChildProxy * parent, const gchar * name)
/**
* gst_child_proxy_get_child_by_index:
* @parent: the parent object to get the child from
* @index: the childs position in the child list
* @index: the child's position in the child list
*
* Fetches a child by its number.
*
......
......@@ -33,7 +33,7 @@
* If a subsystem is disabled, most of this changes are done in an API
* compatible way, so you don't need to adapt your code in most cases. It is
* never done in an ABI compatible way though. So if you want to disable a
* suybsystem, you have to rebuild all programs depending on GStreamer, too.
* subsystem, you have to rebuild all programs depending on GStreamer, too.
*
* If a subsystem is disabled in GStreamer, a value is defined in
* &lt;gst/gst.h&gt;. You can check this if you do subsystem-specific stuff.
......@@ -81,14 +81,14 @@
/**
* GST_DISABLE_PARSE:
*
* Configures the inclusion of the gst-lauch parser
* Configures the inclusion of the gst-launch parser
*/
@GST_DISABLE_PARSE_DEFINE@
/**
* GST_DISABLE_TRACE:
*
* Configures the inclusion of a resource tracing facillity
* Configures the inclusion of a resource tracing facility
* (seems to be unused)
*/
@GST_DISABLE_TRACE_DEFINE@
......
......@@ -587,7 +587,7 @@ __gst_date_time_compare (const GstDateTime * dt1, const GstDateTime * dt2)
*
* Note that @tzoffset is a float and was chosen so for being able to handle
* some fractional timezones, while it still keeps the readability of
* represeting it in hours for most timezones.
* representing it in hours for most timezones.
*
* If value is -1 then all over value will be ignored. For example
* if @month == -1, then #GstDateTime will created only for @year. If
......
......@@ -32,7 +32,7 @@ G_BEGIN_DECLS
* information. It currently supports ranges from 0001-01-01 to
* 9999-12-31 in the Gregorian proleptic calendar.
*
* Use the acessor functions to get the stored values.
* Use the accessor functions to get the stored values.
*/
typedef struct _GstDateTime GstDateTime;
......
......@@ -72,7 +72,7 @@
* #GST_ELEMENT_FLAG_REQUIRE_CLOCK() flag is set, a clock should be set on the
* element with gst_element_set_clock().
*
* Note that clock slection and distribution is normally handled by the
* Note that clock selection and distribution is normally handled by the
* toplevel #GstPipeline so the clock functions are only to be used in very
* specific situations.
*
......@@ -1535,7 +1535,7 @@ gst_element_default_send_event (GstElement * element, GstEvent * event)
* event handler, the event will be pushed on a random linked sink pad for
* upstream events or a random linked source pad for downstream events.
*
* This function takes owership of the provided event so you should
* This function takes ownership of the provided event so you should
* gst_event_ref() it if you want to reuse the event after this call.
*
* MT safe.
......
......@@ -212,7 +212,7 @@ typedef enum {
* </para></listitem>
* <listitem><para>
* The pipeline selects a #GstClock and distributes this to all the children
* before setting them to PLAYING. This means that it is only alowed to
* before setting them to PLAYING. This means that it is only allowed to
* synchronize on the #GstClock in the PLAYING state.
* </para></listitem>
* <listitem><para>
......
......@@ -27,7 +27,7 @@
* @see_also: #GstElement, #GstPlugin, #GstPluginFeature, #GstPadTemplate.
*
* #GstElementFactory is used to create instances of elements. A
* GstElementfactory can be added to a #GstPlugin as it is also a
* GstElementFactory can be added to a #GstPlugin as it is also a
* #GstPluginFeature.
*
* Use the gst_element_factory_find() and gst_element_factory_create()
......@@ -818,7 +818,7 @@ gst_element_factory_list_get_elements (GstElementFactoryListType type,
* whose pad templates caps can intersect with @caps will be returned.
*
* Returns: (transfer full) (element-type Gst.ElementFactory): a #GList of
* #GstElementFactory elements that match the given requisits.
* #GstElementFactory elements that match the given requisites.
* Use #gst_plugin_feature_list_free after usage.
*/
GList *
......
......@@ -23,7 +23,7 @@
* @see_also: #GstMessage
*
* GStreamer elements can throw non-fatal warnings and fatal errors.
* Higher-level elements and applications can programatically filter
* Higher-level elements and applications can programmatically filter
* the ones they are interested in or can recover from,
* and have a default handler handle the rest of them.
*
......
......@@ -481,7 +481,7 @@ gst_event_new_flush_start (void)
* pads accept data again.
*
* Elements can process this event synchronized with the dataflow since
* the preceeding FLUSH_START event stopped the dataflow.
* the preceding FLUSH_START event stopped the dataflow.
*
* This event is typically generated to complete a seek and to resume
* dataflow.
......@@ -934,7 +934,7 @@ gst_event_parse_buffer_size (GstEvent * event, GstFormat * format,
* increasing value.
*
* The upstream element can use the @diff and @timestamp values to decide
* whether to process more buffers. For possitive @diff, all buffers with
* whether to process more buffers. For positive @diff, all buffers with
* timestamp <= @timestamp + @diff will certainly arrive late in the sink
* as well. A (negative) @diff value so that @timestamp + @diff would yield a
* result smaller than 0 is not allowed.
......@@ -1097,9 +1097,9 @@ gst_event_new_seek (gdouble rate, GstFormat format, GstSeekFlags flags,
* @format: (out): result location for the stream format
* @flags: (out): result location for the #GstSeekFlags
* @start_type: (out): result location for the #GstSeekType of the start position
* @start: (out): result location for the start postion expressed in @format
* @start: (out): result location for the start position expressed in @format
* @stop_type: (out): result location for the #GstSeekType of the stop position
* @stop: (out): result location for the stop postion expressed in @format
* @stop: (out): result location for the stop position expressed in @format
*
* Parses a seek @event and stores the results in the given result locations.
*/
......@@ -1298,7 +1298,7 @@ gst_event_parse_step (GstEvent * event, GstFormat * format, guint64 * amount,
/**
* gst_event_new_reconfigure:
* Create a new reconfigure event. The purpose of the reconfingure event is
* Create a new reconfigure event. The purpose of the reconfigure event is
* to travel upstream and make elements renegotiate their caps or reconfigure
* their buffer pools. This is useful when changing properties on elements
* or changing the topology of the pipeline.
......
......@@ -34,10 +34,10 @@ G_BEGIN_DECLS
* GstDebugLevel:
* @GST_LEVEL_NONE: No debugging level specified or desired. Used to deactivate
* debugging output.
* @GST_LEVEL_ERROR: Error messages are to be used only when an error occured
* @GST_LEVEL_ERROR: Error messages are to be used only when an error occurred
* that stops the application from keeping working correctly.
* An examples is gst_element_error, which outputs a message with this priority.
* It does not mean that the application is terminating as with g_errror.
* It does not mean that the application is terminating as with g_error.
* @GST_LEVEL_WARNING: Warning messages are to inform about abnormal behaviour
* that could lead to problems or weird behaviour later on. An example of this
* would be clocking issues ("your computer is pretty slow") or broken input
......
......@@ -34,7 +34,7 @@
*
* In general, whenever calling a GstIterator function results in your code
* receiving a refcounted object, the refcount for that object will have been
* increased. Your code is responsible for unrefing that object after use.
* increased. Your code is responsible for unreffing that object after use.
*
* The basic use pattern of an iterator is as follows:
*
......
......@@ -384,7 +384,7 @@ gst_message_new_eos (GstObject * src)
*
* Create a new error message. The message will copy @error and
* @debug. This message is posted by element when a fatal event
* occured. The pipeline will probably (partially) stop. The application
* occurred. The pipeline will probably (partially) stop. The application
* receiving this message should stop the pipeline.
*
* Returns: (transfer full): the new error message.
......@@ -649,7 +649,7 @@ gst_message_new_clock_lost (GstObject * src, GstClock * clock)
* @clock: (transfer none): the new selected clock
*
* Create a new clock message. This message is posted whenever the
* pipeline selectes a new clock for the pipeline.
* pipeline selects a new clock for the pipeline.
*
* Returns: (transfer full): The new new clock message.
*
......@@ -912,7 +912,7 @@ gst_message_new_latency (GstObject * src)
* changed. A typical use case would be an audio server that wants to pause the
* pipeline because a higher priority stream is being played.
*
* Returns: (transfer full): the new requst state message.
* Returns: (transfer full): the new request state message.
*
* MT safe.
*/
......@@ -1684,7 +1684,7 @@ gst_message_parse_step_done (GstMessage * message, GstFormat * format,
*
* @active is set to TRUE when the element has activated the step operation and
* is now ready to start executing the step in the streaming thread. After this
* message is emited, the application can queue a new step operation in the
* message is emitted, the application can queue a new step operation in the
* element.
*
* Returns: (transfer full): The new step_start message.
......@@ -2064,7 +2064,7 @@ gst_message_new_toc (GstObject * src, GstToc * toc, gboolean updated)
* @toc: (out) (transfer full): return location for the TOC.
* @updated: (out): return location for the updated flag.
*
* Extract thef TOC from the #GstMessage. The TOC returned in the
* Extract the TOC from the #GstMessage. The TOC returned in the
* output argument is a copy; the caller must free it with
* gst_toc_unref() when done.
*
......
......@@ -33,11 +33,11 @@ typedef struct _GstMessage GstMessage;
* only receive this message in the PLAYING state and every time it sets a
* pipeline to PLAYING that is in the EOS state. The application can perform a
* flushing seek in the pipeline, which will undo the EOS state again.
* @GST_MESSAGE_ERROR: an error occured. When the application receives an error
* @GST_MESSAGE_ERROR: an error occurred. When the application receives an error
* message it should stop playback of the pipeline and not assume that more
* data will be played.
* @GST_MESSAGE_WARNING: a warning occured.
* @GST_MESSAGE_INFO: an info message occured
* @GST_MESSAGE_WARNING: a warning occurred.
* @GST_MESSAGE_INFO: an info message occurred
* @GST_MESSAGE_TAG: a tag was found.
* @GST_MESSAGE_BUFFERING: the pipeline is buffering. When the application
* receives a buffering message in the PLAYING state for a non-live pipeline it
......@@ -260,7 +260,7 @@ typedef enum {
* posted on the bus.
*
* The type of a %GST_MESSAGE_PROGRESS. The progress messages inform the
* application of the status of assynchronous tasks.
* application of the status of asynchronous tasks.
*/
typedef enum {
GST_PROGRESS_TYPE_START = 0,
......
......@@ -175,8 +175,8 @@ typedef gboolean (*GstMetaTransformFunction) (GstBuffer *transbuf,
/**
* GstMetaInfo:
* @api: tag indentifying the metadata structure and api
* @type: type indentifying the implementor of the api
* @api: tag identifying the metadata structure and api
* @type: type identifying the implementor of the api
* @size: size of the metadata
* @init_func: function for initializing the metadata
* @free_func: function for freeing the metadata
......
......@@ -336,7 +336,7 @@ gst_mini_object_make_writable (GstMiniObject * mini_object)
*
* Increase the reference count of the mini-object.
*
* Note that the refcount affects the writeability
* Note that the refcount affects the writability
* of @mini-object, see gst_mini_object_is_writable(). It is
* important to note that keeping additional references to
* GstMiniObject instances can potentially increase the number
......@@ -645,7 +645,7 @@ gst_mini_object_weak_unref (GstMiniObject * object,
* needs to be freed
*
* This sets an opaque, named pointer on a miniobject.
* The name is specified through a #GQuark (retrived e.g. via
* The name is specified through a #GQuark (retrieved e.g. via
* g_quark_from_static_string()), and the pointer
* can be gotten back from the @object with gst_mini_object_get_qdata()
* until the @object is disposed.
......
......@@ -62,7 +62,7 @@ typedef gboolean (*GstMiniObjectDisposeFunction) (GstMiniObject *obj);
* GstMiniObjectFreeFunction:
* @obj: MiniObject to free
*
* Virtual function prototype for methods to free ressources used by
* Virtual function prototype for methods to free resources used by
* mini-objects.
*/
typedef void (*GstMiniObjectFreeFunction) (GstMiniObject *obj);
......@@ -114,7 +114,7 @@ typedef void (*GstMiniObjectNotify) (gpointer user_data, GstMiniObject * obj);
* @obj: MiniObject to unset flag in.
* @flag: Flag to set, must be a single bit in guint32.
*
* This macro usets the given bits.
* This macro unsets the given bits.
*/
#define GST_MINI_OBJECT_FLAG_UNSET(obj,flag) (GST_MINI_OBJECT_FLAGS (obj) &= ~(flag))
......
......@@ -813,7 +813,7 @@ gst_object_has_ancestor (GstObject * object, GstObject * ancestor)
* does not do any locking of any kind. You might want to protect the
* provided list with the lock of the owner of the list. This function
* will lock each #GstObject in the list to compare the name, so be
* carefull when passing a list with a locked object.
* careful when passing a list with a locked object.
*
* Returns: TRUE if a #GstObject named @name does not appear in @list,
* FALSE if it does.
......
......@@ -145,7 +145,7 @@ typedef enum
* @obj: a #GstObject
* @flag: Flag to set
*
* This macro usets the given bits.
* This macro unsets the given bits.
*/
#define GST_OBJECT_FLAG_UNSET(obj,flag) (GST_OBJECT_FLAGS (obj) &= ~(flag))
......
......@@ -3813,7 +3813,7 @@ no_function:
* The function returns #GST_FLOW_FLUSHING if the pad was flushing.
*
* If the buffer type is not acceptable for @pad (as negotiated with a
* preceeding GST_EVENT_CAPS event), this function returns
* preceding GST_EVENT_CAPS event), this function returns
* #GST_FLOW_NOT_NEGOTIATED.
*
* The function proceeds calling the chain function installed on @pad (see
......@@ -4278,7 +4278,7 @@ get_range_failed:
* When this function returns any other result value than #GST_FLOW_OK, @buffer
* will be unchanged.
*
* This is a lowlevel function. Usualy gst_pad_pull_range() is used.
* This is a lowlevel function. Usually gst_pad_pull_range() is used.
*
* Returns: a #GstFlowReturn from the pad.
*
......@@ -4764,7 +4764,7 @@ idle_probe_stopped:
* mainly used by elements to send events to their peer
* elements.
*
* This function takes owership of the provided event so you should
* This function takes ownership of the provided event so you should
* gst_event_ref() it if you want to reuse the event after this call.
*
* Returns: TRUE if the event was handled.
......@@ -5132,7 +5132,7 @@ precheck_failed:
* plugin doesn't need to bother itself with this information; the core handles
* all necessary locks and checks.
*
* This function takes owership of the provided event so you should
* This function takes ownership of the provided event so you should
* gst_event_ref() it if you want to reuse the event after this call.
*
* Returns: TRUE if the event was handled.
......
......@@ -133,7 +133,7 @@ typedef enum {
* @GST_FLOW_FLUSHING: Pad is flushing.
* @GST_FLOW_EOS: Pad is EOS.
* @GST_FLOW_NOT_NEGOTIATED: Pad is not negotiated.
* @GST_FLOW_ERROR: Some (fatal) error occured. Element generating
* @GST_FLOW_ERROR: Some (fatal) error occurred. Element generating
* this error should post an error message with more
* details.
* @GST_FLOW_NOT_SUPPORTED: This operation is not supported.
......
......@@ -204,7 +204,7 @@ _gst_parse_escape (const gchar * str)
* @error: pointer to a #GError
*
* Create a new element based on command line syntax.
* @error will contain an error message if an erroneuos pipeline is specified.
* @error will contain an error message if an erroneous pipeline is specified.
* An error does not mean that the pipeline could not be constructed.
*