fix codespell issues

NEWS

@@ -91,7 +91,7 @@ with previous 0.3.x releases.
   - Parse channel_map arguments in module-loopback. (#1486)
 
 ## JACK
-  - Delay emiting the samplerate and buffersize callbacks until the
+  - Delay emitting the samplerate and buffersize callbacks until the
     client is active. This fixes some crashes with Carla and other
     JACK apps.
 
@@ -110,7 +110,7 @@ with previous 0.3.x releases.
     a lot better now.
   - Virtual sinks and sources should now always show up immediately.
   - JACK processing is now delayed until buffersize and samplerate
-    are emited. This should improve stability of many JACK apps.
+    are emitted. This should improve stability of many JACK apps.
   - JACK transport sync is now implemented correctly so that preroll
     in bitwig works.
 
@@ -231,7 +231,7 @@ with previous 0.3.x releases.
     But, this will also disable compatibility with JACK applications.
 
 ## Bluetooth
-  - Bluetooth codecs are now compiled into sperate plugins which are
+  - Bluetooth codecs are now compiled into separate plugins which are
     dynamically loaded. This makes it possible to change the plugin
     implementation or ship plugins separately without having to recompile
     the bluetooth module.
@@ -400,7 +400,7 @@ with previous 0.3.x releases.
     of a property so that producers can negotiate more
     efficiently. This is used to negotiate DMA-BUF modifiers,
     which should make more efficient use of the GPU. (#1084)
-  - Add support for multipe sample rates. The graph can switch
+  - Add support for multiple sample rates. The graph can switch
     when IDLE to one of the supported rates. Add an option to
     lock the rate as well. This is not enabled by default yet
     because of driver bugs that need to be worked around first.
@@ -498,7 +498,7 @@ with previous 0.3.x releases.
     default-route module. (#1403)
 
 ## ALSA
-  - Make sure tha alibpref is not part of the device node name because
+  - Make sure that alibpref is not part of the device node name because
     it is random. (#1362)
   - Fixed an off-by-one that could cause midi events to end up with a
     wrong timestamp and thus being discarded by some apps. (#1395)
@@ -616,7 +616,7 @@ with previous 0.3.x releases.
     actually changed.
 
 ## JACK
-  - The locking was reviewed. All callbacks are now emited
+  - The locking was reviewed. All callbacks are now emitted
     from the PipeWire thread with the lock released and
     the process function will be disabled for the duration
     of the callback. This ensures that no two callbacks are
@@ -692,7 +692,7 @@ with previous 0.3.x releases.
 
 ## PipeWire
   - A new module-rt was added to acquire real-time scheduling
-    priviledges without using RTKit.
+    privileges without using RTKit.
   - Documentation fixes and updates. Docs are now using a
     custom theme.
   - There is now a MANDATORY flag on properties that influence
@@ -700,7 +700,7 @@ with previous 0.3.x releases.
   - Filter-chain now parses the LADSPA_PATH correctly when it
     contains a colon separated list.
   - Move `#pipewire` IRC channel to oftc.net.
-  - Fix an error where param changes were not emited in all
+  - Fix an error where param changes were not emitted in all
     cases.
   - Implement Latency reporting. Latency values are propagated
     through the graph so that each node knows the latency to
@@ -819,7 +819,7 @@ with previous 0.3.x releases.
     include the webrtc echo-canceler.
   - State files don't have the X permission anymore.
   - Move i18n core into a private header file.
-  - Stream can now advertize properties and receive property
+  - Stream can now advertise properties and receive property
     updates.
   - Fix an issue where the wrong index was used to address a port.
     It caused Bluetooth devices to stop working.
@@ -846,7 +846,7 @@ with previous 0.3.x releases.
     result. This fixes some volume update issues.
 
 - GStreamer plugins
-  - GStreamer plugins now advertize handling DMABUF explicitly. This
+  - GStreamer plugins now advertise handling DMABUF explicitly. This
     is currently the only way to avoid a memcpy for v4l2 devices.
 
 - Device support

doc/doxygen-awesome.css

@@ -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;
 }
 

doc/pipewire-access.dox

@@ -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.

doc/pipewire-session-manager.dox

@@ -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.
 

include/valgrind/valgrind.h

@@ -1075,7 +1075,7 @@ typedef
 
 /* Use these to write the name of your wrapper.  NOTE: duplicates
    VG_WRAP_FUNCTION_Z{U,Z} in pub_tool_redir.h.  NOTE also: inserts
-   the default behaviour equivalance class tag "0000" into the name.
+   the default behaviour equivalence class tag "0000" into the name.
    See pub_tool_redir.h for details -- normally you don't need to
    think about this, though. */
 
@@ -1673,7 +1673,7 @@ typedef
 /* NB 9 Sept 07.  There is a nasty kludge here in all these CALL_FN_
    macros.  In order not to trash the stack redzone, we need to drop
    %rsp by 128 before the hidden call, and restore afterwards.  The
-   nastyness is that it is only by luck that the stack still appears
+   nastiness is that it is only by luck that the stack still appears
    to be unwindable during the hidden call - since then the behaviour
    of any routine using this macro does not match what the CFI data
    says.  Sigh.

spa/include/spa/param/audio/dsd.h

@@ -42,7 +42,7 @@ extern "C" {
 /** Extra DSD audio flags */
 #define SPA_AUDIO_DSD_FLAG_NONE		(0)		/*< no valid flag */
 
-/* DSD bits are transfered in a buffer grouped in bytes with the bitorder
+/* DSD bits are transferred in a buffer grouped in bytes with the bitorder
  * defined by \a bitorder.
  *
  * Channels are placed in separate planes (interleave = 0) or interleaved

src/media-session/alsa-monitor.c

@@ -111,9 +111,9 @@
  *
  * ## Module-specific properties:
  *
- * Ths modules supports the following entries in the `properties` dictionary:
+ * This modules supports the following entries in the `properties` dictionary:
  * - `alsa.reserve = false`: disable device reservation (default: enabled)
- * - `alsa.jack-device = true`: createa a JACK device (default: disabled), see
+ * - `alsa.jack-device = true`: create a JACK device (default: disabled), see
  *   the comment in the example configuration file.
  *
  * See the `alsa-monitor.conf` provided by your installation for details on

src/modules/module-filter-chain/biquad.h

@@ -15,7 +15,7 @@ extern "C" {
  * are stored in x1 and x2, and the previous two outputs are stored in y1 and
  * y2.
  *
- * We use double during the coefficients calculation for better accurary, but
+ * We use double during the coefficients calculation for better accuracy, but
  * float is used during the actual filtering for faster computation.
  */
 struct biquad {

src/modules/module-filter-chain/pffft.c

@@ -85,7 +85,7 @@
 #endif
 
 /*
-   vector support macros: the rest of the code is independant of
+   vector support macros: the rest of the code is independent of
    SSE/Altivec/NEON -- adding support for other platforms with 4-element
    vectors should be limited to these macros
 */

src/modules/module-filter-chain/pffft.h

@@ -170,7 +170,7 @@ extern "C" {
   void *pffft_aligned_malloc(size_t nb_bytes);
   void pffft_aligned_free(void *);
 
-  /* return 4 or 1 wether support SSE/Altivec instructions was enable when building pffft.c */
+  /* return 4 or 1 weather support SSE/Altivec instructions was enable when building pffft.c */
   int pffft_simd_size();
 
   void pffft_select_cpu(int flags);

src/modules/module-protocol-pulse/modules/module-combine-sink.c

@@ -55,7 +55,7 @@ static const struct spa_dict_item module_combine_sink_info[] = {
 struct module_combine_sink_data;
 
 /* This goes to the stream event listener to be able to identify the stream on
- * which the event occured and to have a link to the module data */
+ * which the event occurred and to have a link to the module data */
 struct combine_stream {
 	struct pw_stream *stream;
 	struct spa_hook stream_listener;

test/pwtest.h

@@ -60,7 +60,7 @@ extern "C" {
  * - \ref PWTEST_FAIL for a test case failure. Usually you should not return this
  *   value but rely on the `pwtest` macros to handle this case.
  * - \ref PWTEST_SKIP to skip the current test
- * - \ref PWTEST_SYSTEM_ERROR in case of an error that would cause the test to not run propertly. This is not a test case failure but some required precondition not being met.
+ * - \ref PWTEST_SYSTEM_ERROR in case of an error that would cause the test to not run properly. This is not a test case failure but some required precondition not being met.
  *
  * ```c
  * #include "pwtest.h"
@@ -85,7 +85,7 @@ extern "C" {
  * ...
  * ```
  *
- * `pwtest` provides comparision macros for most basic data types with the `lt`,
+ * `pwtest` provides comparison macros for most basic data types with the `lt`,
  * `le`, `eq`, `gt`, `ge` suffixes (`<, <=, ==, >, >=`). Tests usually should not
  * return `PWTEST_FAIL` directly, use the `pwtest_fail()` macros if .
  *
@@ -167,7 +167,7 @@ enum pwtest_result {
 					     Use the pwtest_ macros instead */
 	PWTEST_SKIP = 77,		/**< test was skipped */
 	PWTEST_TIMEOUT = 78,		/**< test aborted after timeout */
-	PWTEST_SYSTEM_ERROR = 79,	/**< unrelated error occured */
+	PWTEST_SYSTEM_ERROR = 79,	/**< unrelated error occurred */
 };
 
 /**