diff --git a/docs/random/porting-to-0.11.txt b/docs/random/porting-to-0.11.txt index bfab504500..39c08303fe 100644 --- a/docs/random/porting-to-0.11.txt +++ b/docs/random/porting-to-0.11.txt @@ -258,7 +258,7 @@ The 0.11 porting guide gst_query_parse_formats_length() -> gst_query_parse_n_formats() gst_query_parse_formats_nth() -> gst_query_parse_nth_format() - Some query utility functionsno longer use an inout parameter for the + Some query utility functions no longer use an inout parameter for the destination/query format: - gst_pad_query_position() @@ -313,7 +313,7 @@ The 0.11 porting guide gst_adapter_peek() is removed, use gst_adapter_map() and gst_adapter_unmap() to get access to raw data from the adapter. - Arguments renamed from guint to gsize. + Arguments changed from guint to gsize. * GstBitReader, GstByteReader, GstByteWriter gst_*_reader_new_from_buffer(), gst_*_reader_init_from_buffer() removed, get @@ -352,3 +352,4 @@ The 0.11 porting guide uses a GValue based API now that is similar to the 0.10 API but allows bindings to properly use GstIterator and prevents complex return value ownership issues. + diff --git a/docs/random/status-0.11-14-jun-2011.txt b/docs/random/status-0.11-14-jun-2011.txt index a6c761ce3a..b4309acc2a 100644 --- a/docs/random/status-0.11-14-jun-2011.txt +++ b/docs/random/status-0.11-14-jun-2011.txt @@ -96,7 +96,7 @@ GstCaps optimizations It doesn't look like we'll be able to implement GstCaps iterators to 0.11 so Sebastian was looking for other ways to improve caps performance. One of the -lowhanging fruits was to pass the complete GstCaps structure to the +low hanging fruits was to pass the complete GstCaps structure to the GstBaseTransform transform_caps method. This allows for better and smarter implementations of the function at the cost of marginally more complex code. diff --git a/gst/gstquery.c b/gst/gstquery.c index 12f000f239..1e5f0412f6 100644 --- a/gst/gstquery.c +++ b/gst/gstquery.c @@ -1947,7 +1947,7 @@ gst_query_new_scheduling (void) * @random_access: if random access is possible * @sequential: if sequential access is recommended * @minsize: the suggested minimum size of pull requests - * @maxsize: the suggested maximum size of pull requests: + * @maxsize: the suggested maximum size of pull requests * @align: the suggested alignment of pull requests * * Set the scheduling properties.