From 24428e93261070db49e5d3c11266b0d98e3303bd Mon Sep 17 00:00:00 2001 From: Felix Schwarz Date: Thu, 16 Oct 2014 10:55:36 +0200 Subject: [PATCH] docs: pwd: fix typos https://bugzilla.gnome.org/show_bug.cgi?id=738612 --- docs/pwg/advanced-allocation.xml | 4 ++-- docs/pwg/advanced-clock.xml | 2 +- docs/pwg/advanced-events.xml | 2 +- docs/pwg/advanced-qos.xml | 6 +++--- docs/pwg/advanced-tagging.xml | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/pwg/advanced-allocation.xml b/docs/pwg/advanced-allocation.xml index fde2637f91..253c60d0a6 100644 --- a/docs/pwg/advanced-allocation.xml +++ b/docs/pwg/advanced-allocation.xml @@ -117,7 +117,7 @@ The buffer contains one or more GstMemory - objects thet represent the data in the buffer. + objects that represent the data in the buffer. Metadata in the buffer consists of: @@ -398,7 +398,7 @@ my_example_meta_api_get_type (void) macro. You will also make a method to add your metadata implementation to a GstBuffer. Your my-example-meta.h header file will - need thse additions: + need these additions: Buffer running-time To calculate a buffer running-time, we need a buffer timestamp and - the SEGMENT event that preceeded the buffer. First we can convert + the SEGMENT event that preceded the buffer. First we can convert the SEGMENT event into a GstSegment object and then we can use the gst_segment_to_running_time () function to diff --git a/docs/pwg/advanced-events.xml b/docs/pwg/advanced-events.xml index 997d5b3643..5471ace1e6 100644 --- a/docs/pwg/advanced-events.xml +++ b/docs/pwg/advanced-events.xml @@ -372,7 +372,7 @@ gst_my_filter_sink_event (GstPad *pad, GstObject * parent, GstEvent * event) The flush-stop event is created with gst_event_new_flush_stop (). It has one parameter that controls if the running-time of the pipeline should - be reset to 0 or not. Normally aftera flushing seek, the + be reset to 0 or not. Normally after a flushing seek, the running_time is set back to 0. diff --git a/docs/pwg/advanced-qos.xml b/docs/pwg/advanced-qos.xml index 50edf9f531..b87bf1e812 100644 --- a/docs/pwg/advanced-qos.xml +++ b/docs/pwg/advanced-qos.xml @@ -2,7 +2,7 @@ Quality Of Service (QoS) - Quality of Service in &GStreamer; is about measuring and ajusting + Quality of Service in &GStreamer; is about measuring and adjusting the real-time performance of a pipeline. The real-time performance is always measured relative to the pipeline clock and typically happens in the sinks when they synchronize buffers against the clock. @@ -82,7 +82,7 @@ A synchronizing element also needs to measure its own performance in - order to figure out if the performace problem is upstream of itself. + order to figure out if the performance problem is upstream of itself. These measurements are used to construct a QOS event that is sent @@ -184,7 +184,7 @@ Long term corrections are a bit more difficult to perform. They rely on the value of the proportion in the QOS event. Elements should - reduce the amount of resources they comsume by the proportion + reduce the amount of resources they consume by the proportion field in the QoS message. diff --git a/docs/pwg/advanced-tagging.xml b/docs/pwg/advanced-tagging.xml index ae991d8ee5..d1e5393017 100644 --- a/docs/pwg/advanced-tagging.xml +++ b/docs/pwg/advanced-tagging.xml @@ -109,7 +109,7 @@ gst_my_filter_class_init (GstMyFilterClass *klass) TagSetter interface (which is just a layer). Pipeline tags are tags provided to the element from within the pipeline. The element receives such tags via the GST_EVENT_TAG event, which means - that tags writers should implment an event handler. The tag writer is + that tags writers should implement an event handler. The tag writer is responsible for combining all these three into one list and writing them to the output stream.