mirror of
https://gitlab.freedesktop.org/pipewire/pipewire
synced 2024-10-14 20:02:38 +00:00
doc: fix a typo
This commit is contained in:
parent
3234037a71
commit
68080ec531
|
@ -31,7 +31,7 @@ a user-space daemon is needed to make this possible:
|
|||
from clients
|
||||
* For Pro audio, we use JACK to manage the graph of nodes.
|
||||
|
||||
None of these solutions (except perhaps to some extend Wayland), however,
|
||||
None of these solutions (except perhaps to some extent Wayland), however,
|
||||
were designed to support the security features that are required when
|
||||
dealing with flatpaks or other containerized applications. PipeWire
|
||||
aims to solve this problem and provides a unified framework to run both
|
||||
|
|
|
@ -11,7 +11,7 @@ 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. The POD start is always aligned to 8 bytes.
|
||||
POD types. The POD start is always aligned to 8 bytes.
|
||||
|
||||
PODs can be efficiently constructed and parsed in real-time threads without
|
||||
requiring memory allocations.
|
||||
|
|
Loading…
Reference in a new issue