doc: typo fixes, mostly duplicated words

doc/CGROUP_DELEGATION.md

@@ -232,7 +232,7 @@ delegated.
 Let's stress one thing: delegation is available on scope and service units
 only. It's expressly not available on slice units. Why? Because slice units are
 our *inner* nodes of the cgroup trees and we freely attach service and scopes
-to them. If we'd allow delegation on slice units then this would mean that that
+to them. If we'd allow delegation on slice units then this would mean that
 both systemd and your own manager would create/delete cgroups below the slice
 unit and that conflicts with the single-writer rule.
 
@@ -359,7 +359,7 @@ optional (but of course wise).
 
 Note one particular asymmetry here though: systemd will try to take possession
 of the root cgroup you pass to it *in* *full*, i.e. it will not only
-create/remove child cgroups below it it will also attempt to manage the
+create/remove child cgroups below it, it will also attempt to manage the
 attributes of it. OTOH as mentioned above, when delegating a cgroup tree to
 somebody else it only passes the rights to create/remove sub-cgroups, but will
 insist on managing the delegated cgroup tree's top-level attributes. Or in

doc/CODE_QUALITY.md

@@ -29,7 +29,7 @@ available functionality:
    `./tools/find-tabs.sh recpatch` to fix them. (Again, grain of salt, foreign
    headers should usually be left unmodified.)
 
-6. Use `ninja -C build check-api-docs` to compare the the list of exported
+6. Use `ninja -C build check-api-docs` to compare the list of exported
    symbols of `libsystemd.so` and `libudev.so` with the list of man pages. Symbols
    lacking documentation are highlighted.
 

doc/CODING_STYLE

@@ -340,7 +340,7 @@
 - Avoid leaving long-running child processes around, i.e. fork()s that
   are not followed quickly by an execv() in the child. Resource
   management is unclear in this case, and memory CoW will result in
-  unexpected penalties in the parent much much later on.
+  unexpected penalties in the parent much, much later on.
 
 - Don't block execution for arbitrary amounts of time using usleep()
   or a similar call, unless you really know what you do. Just "giving
@@ -452,7 +452,7 @@
   setting.
 
 - When referring to a command line option in the documentation and such, please
-  allways prefix with "--" or "-" (as appropriate), to indicate that it is a
+  always prefix with "--" or "-" (as appropriate), to indicate that it is a
   command line option.
 
 - When referring to a file system path that is a directory, please always

doc/UIDS-GIDS.md

@@ -189,7 +189,7 @@ supported for the whole system, back in the days.
 assign has the lower 16bits all set to zero. That way, the upper 16bits become
 a container ID of some kind, while the lower 16bits directly encode the
 internal container UID. This is the way `systemd-nspawn` allocates UID ranges
-(see above). Following this allocation logic ensures best compability with
+(see above). Following this allocation logic ensures best compatibility with
 `systemd-nspawn` and all other container managers following the scheme, as it
 is sufficient then to check NSS for the first UID you pick regarding conflicts,
 as that's what they do, too. Moreover, it makes `chown()`ing container file