mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-12-14 08:56:37 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: fix some typos

Browse source
This commit is contained in:
Wim Taymans 2020-11-27 17:35:25 +01:00
parent aa63077eea
commit 77791bd427
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/spa/pod.md
View file

@ -56,7 +56,7 @@ also possible to dynamically grow the memory as needed.
The most common way to construct a POD is on the stack. This does The most common way to construct a POD is on the stack. This does
not require any memory allocations. The size of the POD can be not require any memory allocations. The size of the POD can be
estimated pretty easily and it the buffer is not large enough, an estimated pretty easily and if the buffer is not large enough, an
appropriate error will be generated. appropriate error will be generated.
The code fragment below initializes a pod builder to write into The code fragment below initializes a pod builder to write into
@ -325,8 +325,8 @@ prop = spa_pod_find_prop(obj, prop, SPA_FORMAT_AUDIO_rate);
Similar to the builder, there is a parser object as well. Similar to the builder, there is a parser object as well.
It the fields in a struct are known, it is much easier to use the If the fields in a struct are known, it is much easier to use the
parser. Similarly, if the object type (and thus its) keys are known, parser. Similarly, if the object type (and thus its keys) are known,
the parser is easier. the parser is easier.
First initialize a `struct spa_pod_parser`: First initialize a `struct spa_pod_parser`: