Fix typos

found them with codespell.

Signed-off-by: Diego Viola <diego.viola@gmail.com>

doc/dox/api/spa-pod.dox

@@ -1018,9 +1018,9 @@ A choice contains an array of possible values.
     - Step (2)   : child1 is a default value, options are between
                    child2 and child3, in steps of child4 in the value array.
     - Enum (3)   : child1 is a default value, options are any value from
-                   the value array, prefered values come first.
+                   the value array, preferred values come first.
     - Flags (4)  : child1 is a default value, options are any value from
-                   the value array, prefered values come first.
+                   the value array, preferred values come first.
 - flags: must be 0
 
 ## Pod (20)

doc/dox/config/pipewire-client.conf.5.md

@@ -287,7 +287,7 @@ deprecated, the target.object property should be used instead, which uses the mo
 a possible target.
 
 @PAR@ client.conf  target.object = <node.name|object.serial>
-Where the node should link to ths can be a node.name or an object.serial.
+Where the node should link to, this can be a node.name or an object.serial.
 
 @PAR@ client.conf  node.dont-reconnect = false
 \parblock
@@ -437,7 +437,7 @@ This option is only active when the up-mix is enabled.
 @PAR@ client.conf  channelmix.rear-delay = 12.0
 \parblock
 Apply a delay in milliseconds when up-mixing the rear channels. This improves
-spacialization of the sound. A typical delay of 12 milliseconds is the default.
+specialization of the sound. A typical delay of 12 milliseconds is the default.
 
 This is only active when the `psd` up-mix method is used.
 \endparblock
@@ -452,7 +452,7 @@ This is only active when up-mix is enabled and a Front Center channel is mixed.
 
 @PAR@ client.conf  channelmix.hilbert-taps = 0
 \parblock
-This option will apply a 90 degree phase shift to the rear channels to improve spacialization.
+This option will apply a 90 degree phase shift to the rear channels to improve specialization.
 Taps needs to be between 15 and 255 with more accurate results (and more CPU consumption)
 for higher values.
 
@@ -489,7 +489,7 @@ disabled otherwise.
 ## Debug Parameters
 
 @PAR@ client.conf  debug.wav-path = ""
-Make the stream to also write the raw samples to a WAV file for debugging puposes.
+Make the stream to also write the raw samples to a WAV file for debugging purposes.
 
 ## Format Properties
 

doc/dox/config/pipewire-devices.7.md

@@ -100,7 +100,7 @@ The priority for selecting this device as the default device.
 \parblock
 The name of the clock. This name is auto generated from the card index and stream direction. Devices with the same clock name will not use a resampler to align the clocks. This can be used to link devices together with a shared word clock.
 
-In Pro Audio mode, nodes from the same device are assumed to have the same clock and no resampling will happen when linked togther. So, linking a capture port to a playback port will not use any adaptive resampling in Pro Audio mode.
+In Pro Audio mode, nodes from the same device are assumed to have the same clock and no resampling will happen when linked together. So, linking a capture port to a playback port will not use any adaptive resampling in Pro Audio mode.
 
 In Non Pro Audio profile, no such assumption is made and adaptive resampling is done in all cases by default. This can also be disabled by setting the same clock.name on the nodes.
 \endparblock
@@ -293,7 +293,7 @@ Ignore the ALSA batch flag. If the batch flag is set, ALSA will need an extra pe
 Use the driver provided channel map. Default is true when using UCM, false otherwise because many driver don't report this correctly.
 
 @PAR@ device-param  api.alsa.multi-rate    # boolean
-Allow devices from the same card to be opened in multiple sample rates. Default is true. Some older drivers did not properly advertize the capabilities of the device and only really supported opening the device in one rate.
+Allow devices from the same card to be opened in multiple sample rates. Default is true. Some older drivers did not properly advertise the capabilities of the device and only really supported opening the device in one rate.
 
 @PAR@ device-param  api.alsa.htimestamp = false    # boolean
 Use ALSA htimestamps in scheduling, instead of the system clock.

doc/dox/config/pipewire.conf.5.md

@@ -286,7 +286,7 @@ it. Disable this if you want to globally disable DBus support in the process.
 @PAR@ pipewire.conf  vm.overrides = { default.clock.min-quantum = 1024 }
 Any property in the vm.overrides property object will override the property
 in the context.properties when PipeWire detects it is running in a VM. This
-is deprected, use the context.properties.rules instead.
+is deprecated, use the context.properties.rules instead.
 
 @PAR@ pipewire.conf  context.modules.allow-empty = false
 By default, a warning is logged when there are no context.modules loaded because this

doc/dox/internals/daemon.dox

@@ -139,7 +139,7 @@ more debugging. This variable supports the following format:
   shell globs to match on log topics and the levels are the respective
   log level to set for that topic. Globs are applied in order and a matching
   glob overrides an earlier glob for that category. A level without a glob
-  prefix will set the global log level and is a more preformant version of
+  prefix will set the global log level and is a more performant version of
   `*:<level>`.  For example, `PIPEWIRE_DEBUG=E,mod.*:D,mod.foo:X` enables global error messages,
   debugging on all modules but no messages on the foo module.
 - `<level>` specifies the log level:

doc/dox/internals/library.dox

@@ -56,7 +56,7 @@ for state changes.
 # Versioning
 
 All interfaces have a version number. The maximum supported version
-number of an interface is advertized in the registry global event.
+number of an interface is advertised in the registry global event.
 
 A client asks for a specific version of an interface when it binds
 to them. It is the task of the server to adapt to the version of the

doc/dox/internals/protocol.dox

@@ -157,7 +157,7 @@ The id and seq should be copied from the Ping event.
 
 ### Core::Error (Opcode 4)
 
-An error occured in an object on the client.
+An error occurred in an object on the client.
 
 ```
    Struct(
@@ -274,11 +274,11 @@ Destroy an object.
 
 ## Core Events
 
-Core events are emited by the server.
+Core events are emitted by the server.
 
 ### Core::Info (Opcode 0)
 
-Emited by the server upon connection with the more information about the
+Emitted by the server upon connection with the more information about the
 server.
 
 ```
@@ -309,7 +309,7 @@ server.
 
 ### Core::Done (Opcode 1)
 
-Emited as a result of a client Sync method.
+Emitted as a result of a client Sync method.
 
 ```
    Struct(
@@ -322,7 +322,7 @@ id and seq are passed from the client Sync request.
 
 ### Core::Ping (Opcode 2)
 
-Emited by the server when it wants to check if a client is alive or ensure
+Emitted by the server when it wants to check if a client is alive or ensure
 that it has processed the previous events.
 
 ```
@@ -1236,7 +1236,7 @@ about the the newly allocated buffer memory.
 - type: the plane memory type
 - memfd: the plane memfd
 - mapoffset: the start offset of where the buffer memory starts
-- maxsize: the maxiumum size of the memory.
+- maxsize: the maximum size of the memory.
 
 ## ClientNode events
 

doc/dox/internals/scheduling.dox

@@ -188,7 +188,7 @@ The driver calculates some stats about cpu time etc.
 
 # Remote nodes.
 
-For remote nodes, the eventfd and the activation is transfered from the server
+For remote nodes, the eventfd and the activation is transferred from the server
 to the client.
 
 This means that writing to the remote client eventfd will wake the client directly

doc/dox/overview.dox

@@ -21,7 +21,7 @@ For example
 - a stereo ALSA PCM playback device can appear as a sink with two input ports: front-left and front-right or
 - a virtual ALSA device, to which clients which attempt to use ALSA directly connect, can appear as a source with two output ports: front-left and front right.
 
-Similar mechanisms exist to interface with and accomodate applications which use JACK or Pulseaudio.
+Similar mechanisms exist to interface with and accommodate applications which use JACK or Pulseaudio.
 
 NOTE: `pw-jack` modifies the `LD_LIBRARY_PATH` environment variable so that applications will load PipeWire’s reimplementation of the JACK client libraries instead of JACK’s own libraries. This results in JACK clients being redirected to PipeWire.
 

doc/dox/programs/pw-container.1.md

@@ -43,7 +43,7 @@ Show version information.
 
 # EXIT STATUS
 
-If the security context was successfuly created, **pw-container** does
+If the security context was successfully created, **pw-container** does
 not exit until terminated with a signal. It exits with status 0 if terminated by
 SIGINT or SIGTERM in this case.