tree-wide: fix spelling errors

Based on a report from Fossies.org using Codespell.

Followup to #15436

5 files changed, 5 insertions, 5 deletions

diff --git a/docs/BOOT_LOADER_SPECIFICATION.md b/docs/BOOT_LOADER_SPECIFICATION.md
index 514b8cd11a..6bb72e0faa 100644
--- a/docs/BOOT_LOADER_SPECIFICATION.md
+++ b/docs/BOOT_LOADER_SPECIFICATION.md
@@ -95,7 +95,7 @@ Note that the `$BOOT` partition is not supposed to be exclusive territory of
 this specification. This specification only defines semantics of the `/loader/`
 directory inside the file system (see below), but it doesn't intend to define
 ownership of the whole file system exclusively. Boot loaders, firmware, and
-other software implementating this specification may choose to place other
+other software implementing this specification may choose to place other
 files and directories in the same file system. For example, boot loaders that
 implement this specification might install their own boot code into the `$BOOT`
 partition. On systems where `$BOOT` is the ESP this is a particularly common
diff --git a/docs/DESKTOP_ENVIRONMENTS.md b/docs/DESKTOP_ENVIRONMENTS.md
index 1c8c7aec6e..6dbbbb10f2 100644
--- a/docs/DESKTOP_ENVIRONMENTS.md
+++ b/docs/DESKTOP_ENVIRONMENTS.md
@@ -39,7 +39,7 @@ The purpose of this grouping is to assign different priorities to the
 applications.
 This could e.g. mean reserving memory to session processes,
 preferentially killing background tasks in out-of-memory situations
-or assinging different memory/CPU/IO priorities to ensure that the session
+or assigning different memory/CPU/IO priorities to ensure that the session
 runs smoothly under load.
 
 TODO: Will there be a default to place units into e.g. `apps.slice` by default
diff --git a/docs/HOME_DIRECTORY.md b/docs/HOME_DIRECTORY.md
index 34400b3ba4..c517cf573c 100644
--- a/docs/HOME_DIRECTORY.md
+++ b/docs/HOME_DIRECTORY.md
@@ -147,7 +147,7 @@ directory-based storage mechanisms (`directory`, `subvolume` and `fscrypt`)
 this is a bind mount, in case of `cifs` this is a CIFS network mount, and in
 case of the LUKS2 backend a regular block device mount of the file system
 contained in the LUKS2 image. By requiring a mount for all cases (even for
-those that already are a directory) a clear logic is defined to distuingish
+those that already are a directory) a clear logic is defined to distinguish
 active and inactive home directories, so that the directories become
 inaccessible under their regular path the instant they are
 deactivated. Moreover, the `nosuid`, `nodev` and `noexec` flags configured in
diff --git a/docs/USER_GROUP_API.md b/docs/USER_GROUP_API.md
index 3530f00d0d..8ec1823149 100644
--- a/docs/USER_GROUP_API.md
+++ b/docs/USER_GROUP_API.md
@@ -95,7 +95,7 @@ services are listening there, that have special relevance:
 2. `io.systemd.Multiplexer` → This service multiplexes client queries to all
    other running services. It's supposed to simplify client development: in
    order to look up or enumerate user/group records it's sufficient to talk to
-   one service instead of all of them in parallel. Note that it is not availabe
+   one service instead of all of them in parallel. Note that it is not available
    during earliest boot and final shutdown phases, hence for programs running
    in that context it is preferable to implement the parallel lookup
    themselves.
diff --git a/docs/USER_NAMES.md b/docs/USER_NAMES.md
index a56984b044..50ac835521 100644
--- a/docs/USER_NAMES.md
+++ b/docs/USER_NAMES.md
@@ -157,7 +157,7 @@ it creates ambiguity in traditional `chown` syntax (which is still accepted
 today) that uses it to separate user and group names in the command's
 parameter: without consulting the user/group databases it is not possible to
 determine if a `chown` invocation would change just the owning user or both the
-owning user and group. It also allows embeddeding `@` (which is confusing to
+owning user and group. It also allows embedding `@` (which is confusing to
 MTAs).
 
 ## Common Core