From: Zbigniew Jędrzejewski-Szmek Date: Wed, 25 Mar 2026 00:43:29 +0000 (+0100) Subject: various: fix typos X-Git-Tag: v261-rc1~744^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F41302%2Fhead;p=thirdparty%2Fsystemd.git various: fix typos --- diff --git a/NEWS b/NEWS index 85cc7ac2d1d..cdf3c3a0ad9 100644 --- a/NEWS +++ b/NEWS @@ -14264,7 +14264,7 @@ CHANGES WITH 235: the "utmp" group already, and it appears to be generally understood that members of "utmp" can modify/flush the utmp/wtmp/lastlog/btmp databases. Previously this was implemented correctly for all these - databases excepts btmp, which has been opened up like this now + databases except btmp, which has been opened up like this now too. Note that while the other databases are world-readable (i.e. 0644), btmp is not and remains more restrictive. diff --git a/src/growfs/growfs.c b/src/growfs/growfs.c index d991b82d67c..8481257ab71 100644 --- a/src/growfs/growfs.c +++ b/src/growfs/growfs.c @@ -189,7 +189,7 @@ static int parse_argv(int argc, char *argv[]) { if (optind + 1 != argc) return log_error_errno(SYNTHETIC_ERRNO(EINVAL), - "%s excepts exactly one argument (the mount point).", + "%s expects exactly one argument (the mount point).", program_invocation_short_name); arg_target = argv[optind]; diff --git a/test/test-network/conf/25-routing-policy-rule-test1.network b/test/test-network/conf/25-routing-policy-rule-test1.network index 66ea59d3a99..4c83fd5fb78 100644 --- a/test/test-network/conf/25-routing-policy-rule-test1.network +++ b/test/test-network/conf/25-routing-policy-rule-test1.network @@ -67,7 +67,7 @@ Priority=202 Table=22 # The four routing policy rules below intentionally have the same config -# excepts for their To= addresses. See issue #35874. +# except for their To= addresses. See issue #35874. [RoutingPolicyRule] To=192.0.2.0/26 Table=1001