From: Yu Watanabe <watanabe.yu+github@gmail.com>
Date: Mon, 7 Mar 2022 06:32:22 +0000 (+0900)
Subject: tree-wide: fix typo
X-Git-Tag: v251-rc1~201
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a17e54783a6c899309bd5e32f1d68e95a0db0abf;p=thirdparty%2Fsystemd.git

tree-wide: fix typo
---

diff --git a/man/sd_bus_add_object.xml b/man/sd_bus_add_object.xml
index 3249b7f98de..991f3a8064f 100644
--- a/man/sd_bus_add_object.xml
+++ b/man/sd_bus_add_object.xml
@@ -561,7 +561,7 @@
         <varlistentry>
           <term><constant>SD_BUS_VTABLE_CAPABILITY(<replaceable>capability</replaceable>)</constant></term>
 
-          <listitem><para>Access to this vtable entry will be allowed if the calling proccess has the
+          <listitem><para>Access to this vtable entry will be allowed if the calling process has the
           capability <replaceable>capability</replaceable>, as described in
           <citerefentry><refentrytitle>sd_bus_query_sender_privilege</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
           If used for <constant>SD_BUS_VTABLE_START()</constant>, provides a default for all entries in the
diff --git a/meson.build b/meson.build
index 905ed07f758..6ce7b01c0b4 100644
--- a/meson.build
+++ b/meson.build
@@ -361,7 +361,7 @@ possible_common_cc_flags = [
         '-Wno-string-plus-int',  # clang
 ]
 
-# Disable -Wmaybe-unitialized when compiling with -Os/-O1/-O3/etc. There are
+# Disable -Wmaybe-uninitialized when compiling with -Os/-O1/-O3/etc. There are
 # too many false positives with gcc >= 8. Effectively, we only test with -O0
 # and -O2; this should be enough to catch most important cases without too much
 # busywork. See https://github.com/systemd/systemd/pull/19226.
diff --git a/src/shared/watchdog.c b/src/shared/watchdog.c
index 1c0dfc99150..c4a4702a37c 100644
--- a/src/shared/watchdog.c
+++ b/src/shared/watchdog.c
@@ -230,7 +230,7 @@ static int update_pretimeout(void) {
         /* If we have a pretimeout governor, then pretimeout is supported. Without a governor
          * pretimeout does not work at all.
          * Note that this might require a kernel module that is not autoloaded, so we don't
-         * cache this, but we check everytime the configuration changes. */
+         * cache this, but we check every time the configuration changes. */
         watchdog_supports_pretimeout = true;
 
         /* Determine if the pretimeout is valid for the current watchdog timeout. */