tree-wide: fix typos reported by Fossies Codespell report

src/shared/async.c

@@ -128,7 +128,7 @@ int asynchronous_rm_rf(const char *p, RemoveFlags flags) {
         r = rm_rf(p, flags);
         if (r < 0) {
                 log_debug_errno(r, "Failed to rm -rf '%s', ignoring: %m", p);
-                _exit(EXIT_FAILURE); /* This is a detached process, hence noone really cares, but who knows
+                _exit(EXIT_FAILURE); /* This is a detached process, hence no one really cares, but who knows
                                       * maybe it's good for debugging/tracing to return an exit code
                                       * indicative of our failure here. */
         }

src/shared/cgroup-setup.c

@@ -263,7 +263,7 @@ int cg_trim(const char *controller, const char *path, bool delete_root) {
         else if (r < 0)
                 log_debug_errno(r, "Failed to iterate through cgroup %s: %m", path);
 
-        /* If we shall delete the top-level cgroup, then propagate the faiure to do so (except if it is
+        /* If we shall delete the top-level cgroup, then propagate the failure to do so (except if it is
          * already gone anyway). Also, let's debug log about this failure, except if the error code is an
          * expected one. */
         if (delete_root && !empty_or_root(path) &&

src/shared/creds-util.c

@@ -140,7 +140,7 @@ int read_credential_with_decryption(const char *name, void **ret, size_t *ret_si
          * yet.
          *
          * Note that read_credential_harder_and_warn() logs on its own, while read_credential() does not!
-         * (It's a lot more complex and error prone given its TPM2 connectivty, and is generally called from
+         * (It's a lot more complex and error prone given its TPM2 connectivity, and is generally called from
          * generators only where logging is OK).
          *
          * Error handling is also a bit different: if we can't find a credential we'll return 0 and NULL

src/shared/tpm2-util.c

@@ -210,7 +210,7 @@ static int tpm2_cache_capabilities(Tpm2Context *c) {
          * by the SetAlgorithmSet() command. Unfortunately, the spec doesn't require a TPM reinitialization
          * after changing the algorithm set (unless the PCR algorithms are changed). However, the spec also
          * indicates the TPM behavior after SetAlgorithmSet() is "vendor-dependent", giving the example of
-         * flushing sessions and objects, erasing policies, etc. So, if the algorithm set is programatically
+         * flushing sessions and objects, erasing policies, etc. So, if the algorithm set is programmatically
          * changed while we are performing some operation, it's reasonable to assume it will break us even if
          * we don't cache the algorithms, thus they should be "safe" to cache. */
         TPM2_ALG_ID current_alg = TPM2_ALG_FIRST;
@@ -245,7 +245,7 @@ static int tpm2_cache_capabilities(Tpm2Context *c) {
         }
 
         /* Cache the command capabilities. The spec isn't actually clear if commands can be added/removed
-         * while running, but that would be crazy, so let's hope it is not possbile. */
+         * while running, but that would be crazy, so let's hope it is not possible. */
         TPM2_CC current_cc = TPM2_CC_FIRST;
         for (;;) {
                 r = tpm2_get_capability(