From: eggfly Date: Tue, 23 Aug 2022 08:09:59 +0000 (+0800) Subject: fix typos X-Git-Tag: v252-rc1~371 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=6b5e82408dbaf67bf86f81432be02ae02d30c182;p=thirdparty%2Fsystemd.git fix typos --- diff --git a/NEWS b/NEWS index f2747b6acab..685a894d3a0 100644 --- a/NEWS +++ b/NEWS @@ -2488,7 +2488,7 @@ CHANGES WITH 248: units. systemd-oomd is now considered fully supported (the usual - backwards-compatiblity promises apply). Swap is not required for + backwards-compatibility promises apply). Swap is not required for operation, but it is still recommended. * systemd-timesyncd gained a new ConnectionRetrySec= setting which diff --git a/man/org.freedesktop.resolve1.xml b/man/org.freedesktop.resolve1.xml index 1dc6dcbd739..54f0a18418e 100644 --- a/man/org.freedesktop.resolve1.xml +++ b/man/org.freedesktop.resolve1.xml @@ -606,7 +606,7 @@ node /org/freedesktop/resolve1 { The DNSSECStatistics property contains information about the DNSSEC validations executed so far. It contains four 64-bit counters: the number of secure, insecure, bogus, and indeterminate DNSSEC validations so far. The counters are increased for each validated RRset, and - each non-existance proof. The secure counter is increased for each operation that successfully verified + each non-existence proof. The secure counter is increased for each operation that successfully verified a signed reply, the insecure counter is increased for each operation that successfully verified that an unsigned reply is rightfully unsigned. The bogus counter is increased for each operation where the validation did not check out and the data is likely to have been tempered with. Finally the diff --git a/src/resolve/resolved-dns-cache.c b/src/resolve/resolved-dns-cache.c index 594984685bc..4c004c4a48c 100644 --- a/src/resolve/resolved-dns-cache.c +++ b/src/resolve/resolved-dns-cache.c @@ -58,7 +58,7 @@ struct DnsCacheItem { /* Returns true if this is a cache item created as result of an explicit lookup, or created as "side-effect" * of another request. "Primary" entries will carry the full answer data (with NSEC, …) that can aso prove - * wildcard expansion, non-existance and such, while entries that were created as "side-effect" just contain + * wildcard expansion, non-existence and such, while entries that were created as "side-effect" just contain * immediate RR data for the specified RR key, but nothing else. */ #define DNS_CACHE_ITEM_IS_PRIMARY(item) (!!(item)->answer) diff --git a/src/udev/dmi_memory_id/dmi_memory_id.c b/src/udev/dmi_memory_id/dmi_memory_id.c index bae05b8ecdd..338cbc72c0b 100644 --- a/src/udev/dmi_memory_id/dmi_memory_id.c +++ b/src/udev/dmi_memory_id/dmi_memory_id.c @@ -86,7 +86,7 @@ static bool verify_checksum(const uint8_t *buf, size_t len) { } /* - * Type-independant Stuff + * Type-independent Stuff */ static const char *dmi_string(const struct dmi_header *dm, uint8_t s) { diff --git a/test/units/testsuite-62-4.service b/test/units/testsuite-62-4.service index 94c7b534683..053e6d205f4 100644 --- a/test/units/testsuite-62-4.service +++ b/test/units/testsuite-62-4.service @@ -1,6 +1,6 @@ # SPDX-License-Identifier: LGPL-2.1-or-later [Unit] -Description=TEST-62-RESTRICT-IFACES-empty-assigment +Description=TEST-62-RESTRICT-IFACES-empty-assignment [Service] ExecStart=/bin/sh -c 'ping -c 1 -W 0.2 192.168.113.1' ExecStart=/bin/sh -c 'ping -c 1 -W 0.2 192.168.113.5' diff --git a/test/units/testsuite-62-5.service b/test/units/testsuite-62-5.service index 38664da4938..a8f268d1d81 100644 --- a/test/units/testsuite-62-5.service +++ b/test/units/testsuite-62-5.service @@ -1,6 +1,6 @@ # SPDX-License-Identifier: LGPL-2.1-or-later [Unit] -Description=TEST-62-RESTRICT-IFACES-invert-assigment +Description=TEST-62-RESTRICT-IFACES-invert-assignment [Service] ExecStart=/bin/sh -c '! ping -c 1 -W 0.2 192.168.113.1' ExecStart=/bin/sh -c 'ping -c 1 -W 0.2 192.168.113.5'