mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-10-29 05:40:27 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix codespell issues

Browse source
This commit is contained in:
Björn Daase 2021-10-07 14:54:47 +02:00 • committed by Wim Taymans
parent 57eef39583
commit cf38b7bdc4
12 changed files with 25 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/doxygen-awesome.css
View file

@ -149,7 +149,7 @@ SOFTWARE.
--side-nav-foreground: var(--page-foreground-color);
--side-nav-arrow-color: var(--page-background-color);
/* height of an item in any tree / collapsable table */
/* height of an item in any tree / collapsible table */
--tree-item-height: 30px;
}

2
doc/pipewire-access.dox
View file

@ -7,7 +7,7 @@ Permissions include `R` (read), `W` (write), `X` (execute) and `M` (metadata).
- `R`: An object with permission `R` is visible to the client. The client will receive
registry events for the object and can interact with it.
- `W`: An object with permisson `W` can be modified. This is usually done
- `W`: An object with permission `W` can be modified. This is usually done
through a method that modifies the state of the object. The `W` permission
usually implies the `X` permission.
- `X`: An object with permission `X` allows invoking methods on the object.

2
doc/pipewire-session-manager.dox
View file

@ -19,7 +19,7 @@ This page describes some of the requirements for session managers in general.
## Client management
PipeWire provides a \ref page_access "permission system" to limit client's
acccess to resources but only \ref page_module_access "basic permission
access to resources but only \ref page_module_access "basic permission
handling". The session manager is expected to decide whether clients may
access specific resources.