tree-wide: fix typo

NEWS

@@ -7017,7 +7017,7 @@ CHANGES WITH 248:
         * When resolving host names and other records resolvectl will now
           report where the data was acquired from (i.e. the local cache, the
           network, locally synthesized, …) and whether the network traffic it
-          effected was encrypted or not. Moreover the tool acquired a number of
+          affected was encrypted or not. Moreover the tool acquired a number of
           new options --cache=, --synthesize=, --network=, --zone=,
           --trust-anchor=, --validate= that take booleans and may be used to
           tweak a lookup, i.e. whether it may be answered from cached
@@ -7151,7 +7151,7 @@ CHANGES WITH 248:
           set-property". Once a marker is set, "systemctl reload-or-restart
           --marked" may be invoked to execute the operation the units are
           marked for. This is useful for package managers that want to mark
-          units for restart/reload while updating, but effect the actual
+          units for restart/reload while updating, but affect the actual
           operations at a later step at once.
 
         * The sd_bus_message_read_strv() API call of sd-bus may now also be

docs/OSC-CONTEXT.md

@@ -198,7 +198,7 @@ contexts be discarded, not the opposite). Overly long fields should be
 discarded (or potentially truncated, depending on the field type). This
 specification does not recommend any specific stack or string limits for now.
 
-The usual terminal reset sequences should *not* effect the stack of contexts
+The usual terminal reset sequences should *not* affect the stack of contexts
 (this is a safety feature: a program down the stack should not be able to
 affect the stack further up, possibly hiding relevant information). A temporary
 TTY hangup (`vhangup()`) should result in a full reset of the stack.

man/nss-systemd.xml

@@ -100,7 +100,7 @@ lrwxrwxrwx. 1 root root   19 May 10 4711.user-privileged -> foobar.user-privileg
     <literal><replaceable>username</replaceable>:<replaceable>groupname</replaceable>.membership</literal>
     should be created, i.e. the textual UNIX user name, followed by a colon, followed by the textual UNIX
     group name, suffixed by <literal>.membership</literal>. The contents of these files are currently not
-    read, and the files should be created empty. The mere existence of these files is enough to effect a
+    read, and the files should be created empty. The mere existence of these files is enough to affect a
     user/group membership. If a program provides user and/or group record files in the searched directories,
     it should always also create such files, both for primary and auxiliary group memberships.</para>
 

man/systemd-cgtop.xml

@@ -189,7 +189,7 @@
         pressing the <keycap>r</keycap> key. Note that this setting
         only applies to process counting, i.e. when the
         <option>-P</option> or <option>-k</option> options are
-        used. It has not effect if all tasks are counted, in which
+        used. It has no effect if all tasks are counted, in which
         case the counting is always recursive.</para>
 
         <xi:include href="version-info.xml" xpointer="v226"/></listitem>

man/systemd.exec.xml

@@ -2131,7 +2131,7 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
         services need to write to these at runtime; it is hence recommended to turn this on for most services. For this
         setting the same restrictions regarding mount propagation and privileges apply as for
         <varname>ReadOnlyPaths=</varname> and related calls, see above. Defaults to off.
-        Note that this option does not prevent indirect changes to kernel tunables effected by IPC calls to
+        Note that this option does not prevent indirect changes to kernel tunables affected by IPC calls to
         other processes. However, <varname>InaccessiblePaths=</varname> may be used to make relevant IPC file system
         objects inaccessible. If <varname>ProtectKernelTunables=</varname> is set,
         <varname>MountAPIVFS=yes</varname> is implied.</para>

src/core/main.c

@@ -880,7 +880,7 @@ static void set_manager_settings(Manager *m) {
         assert(m);
 
         /* Propagates the various manager settings into the manager object, i.e. properties that
-         * effect the manager itself (as opposed to just being inherited into newly allocated
+         * affect the manager itself (as opposed to just being inherited into newly allocated
          * units, see set_manager_defaults() above). */
 
         m->confirm_spawn = arg_confirm_spawn;

src/core/unit.h

@@ -99,7 +99,7 @@ typedef enum UnitDependencyMask {
          * type) */
         UNIT_DEPENDENCY_IMPLICIT           = 1 << 1,
 
-        /* A dependency effected by DefaultDependencies=yes. Note that dependencies marked this way are conceptually
+        /* A dependency affected by DefaultDependencies=yes. Note that dependencies marked this way are conceptually
          * just a subset of UNIT_DEPENDENCY_FILE, as DefaultDependencies= is itself a unit file setting that can only
          * be set in unit files. We make this two separate bits only to help debugging how dependencies came to be. */
         UNIT_DEPENDENCY_DEFAULT            = 1 << 2,