diff options
| author | Wim Taymans <wtaymans@redhat.com> | 2020-06-09 15:28:26 +0200 |
|---|---|---|
| committer | Wim Taymans <wtaymans@redhat.com> | 2020-06-09 15:28:26 +0200 |
| commit | 9fd642831411ebeb1aacd92124fbd2fb2d6623e8 (patch) | |
| tree | e65b3d31b507e9a3c22b9c5d8595a36f3ab11e7b | |
| parent | 014e48c1f1c47404653f597e500314cbf021056d (diff) | |
docs: fix some typos
| -rw-r--r-- | doc/spa/pod.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/spa/pod.md b/doc/spa/pod.md index c8e280dc..7cfd525a 100644 --- a/doc/spa/pod.md +++ b/doc/spa/pod.md @@ -1,17 +1,17 @@ # POD POD (plan old data) is a sort of data container. It is comparable to -DBus Variant of LV2 Atom. +DBus Variant or LV2 Atom. A POD can express nested structures of Objects (with properties), Vectors, Arrays, sequences and various primitives types. All information in the POD -is layed out sequenctially in memory and can be written directly do +is layed out sequentially in memory and can be written directly to storage or exchanged between processes or threads without additional marshalling.. Each POD is made of a 32 bits size followed by a 32 bits type field, followed by the pod contents. This makes it possible to skip over unknown -POD type. +POD type. The POD start is always aligned to 8 bytes. PODs can be efficiently constructed and parsed in real-time threads without requiring memory allocations. @@ -285,7 +285,7 @@ an object of the expected type. ## Struct fields -To iterate over the fields of a struct use: +To iterate over the fields of a Struct use: ``` struct spa_pod *pod, *obj; @@ -470,7 +470,7 @@ Given 2 pod objects of the same type (Object, Struct, ..) one can run a filter and generate a new pod that only contains values that are compatibe with both input pods. -This is, for example, used to find a compatible format between to ports. +This is, for example, used to find a compatible format between two ports. As an example we can run a filter on two simple PODs: |