Merge cfc9161087 into 37c2be73e7

Force-pushed as usual, now HEAD is v257.1.

.packit.yml

@@ -57,8 +57,7 @@ jobs:
 
 - job: tests
   trigger: pull_request
-  fmf_url: https://src.fedoraproject.org/tests/systemd
-  fmf_ref: main
+  fmf_path: test/fmf
   tmt_plan: ci
   targets:
   - fedora-rawhide-x86_64

docs/CREDENTIALS.md

@@ -378,7 +378,7 @@ Various services shipped with `systemd` consume credentials for tweaking behavio
   Note that in case the hypervisor does not support `SOCK_DGRAM` over `AF_VSOCK`,
   `SOCK_SEQPACKET` will be tried instead.
   The credential payload should be in the form: `vsock:<CID>:<PORT>`.
-  Also note that this requires support for VHOST to be built-in both the guest and the host kernels, and the kernel modules to be loaded.
+  Also note that this requires support for VSOCK to be built in both the guest and the host kernels, and the kernel modules to be loaded.
 
 * [`systemd-sysusers(8)`](https://www.freedesktop.org/software/systemd/man/systemd-sysusers.html)
   will look for the credentials `passwd.hashed-password.<username>`,

man/90-rearrange-path.py

@@ -35,7 +35,7 @@ def rearrange_bin_sbin(path):
 
 if __name__ == '__main__':
     path = os.environ['PATH'] # This should be always set.
-                              # If it's not, we'll just crash, which is OK too.
+                              # If it is not, we will just crash, which is OK too.
     new = rearrange_bin_sbin(path)
     if new != path:
         print('PATH={}'.format(new))

man/bootctl.xml

@@ -406,7 +406,7 @@
 
       <varlistentry>
         <term><option>--random-seed=yes|no</option></term>
-        <listitem><para>By default the <command>install</command> command initializes a random seed file in
+        <listitem><para>By default, the <command>install</command> command initializes a random seed file in
         the ESP. When creating an image it may be desirable to disable that in order to avoid having the
         same seed in all instances.</para>
 
@@ -468,8 +468,8 @@
         <filename>os-release</filename> (e.g. <literal>vendorx-cashier-system</literal>).</para>
 
         <para>If set to <option>auto</option> (the default), the <filename>/etc/kernel/entry-token</filename>
-        file will be read if it exists, and the stored value used.  Otherwise if the local machine ID is
-        initialized it is used. Otherwise <varname>IMAGE_ID=</varname> from <filename>os-release</filename>
+        file will be read if it exists, and the stored value used. Otherwise, if the local machine ID is
+        initialized it is used. Otherwise, <varname>IMAGE_ID=</varname> from <filename>os-release</filename>
         will be used, if set.  Otherwise, <varname>ID=</varname> from <filename>os-release</filename> will be
         used, if set.</para>
 
@@ -509,7 +509,7 @@
         <para>Using the default entry name <literal>Linux Boot Manager</literal> is generally preferable as only
         one bootloader installed to a single ESP partition should be used to boot any number of OS installations
         found on the various disks installed in the system. Specifically distributions should not use this flag
-        to install a branded entry in the boot option list. However in situations with multiple disks, each with
+        to install a branded entry in the boot option list. However, in situations with multiple disks, each with
         their own ESP partition, it can be beneficial to make it easier to identify the bootloader being used in
         the firmware's boot option menu.</para>
 

man/bootup.xml

@@ -339,7 +339,7 @@ systemd-reboot.service     |               |               |               |
     remaining file systems, kill any remaining processes and release any other remaining resources, in a simple and
     robust fashion, without taking any service or unit concept into account anymore. At that point, regular
     applications and resources are generally terminated and released already, the second phase hence operates only as
-    safety net for everything that couldn't be stopped or released for some reason during the primary, unit-based
+    safety net for everything that could not be stopped or released for some reason during the primary, unit-based
     shutdown phase described above.</para>
   </refsect1>
 

man/crypttab.xml

@@ -104,7 +104,7 @@
       see above and below.</para></listitem>
 
       <listitem><para>The key may be acquired via a PKCS#11 compatible hardware security token or
-      smartcard. In this case a saved key used in unlock process is stored on disk/removable media, acquired via
+      smartcard. In this case, a saved key used in unlock process is stored on disk/removable media, acquired via
       <constant>AF_UNIX</constant>, or stored in the LUKS2 JSON token metadata header. For RSA, the saved key
       is an encrypted volume key. The encrypted volume key is then decrypted by the PKCS#11 token with an RSA
       private key stored on it, and used to unlock the encrypted volume. For elliptic-curve (EC) cryptography,
@@ -114,14 +114,14 @@
       </para></listitem>
 
       <listitem><para>Similarly, the key may be acquired via a FIDO2 compatible hardware security token
-      (which must implement the "hmac-secret" extension). In this case a key generated randomly during
+      (which must implement the "hmac-secret" extension). In this case, a key generated randomly during
       enrollment is stored on disk/removable media, acquired via <constant>AF_UNIX</constant>, or stored in
       the LUKS2 JSON token metadata header. The random key is hashed via a keyed hash function (HMAC) on the
       FIDO2 token, using a secret key stored on the token that never leaves it. The resulting hash value is
       then used as key to unlock the encrypted volume. Use the <option>fido2-device=</option> option
       described below to use this mechanism.</para></listitem>
 
-      <listitem><para>Similarly, the key may be acquired via a TPM2 security chip. In this case a (during
+      <listitem><para>Similarly, the key may be acquired via a TPM2 security chip. In this case, a (during
       enrollment) randomly generated key — encrypted by an asymmetric key derived from the TPM2 chip's seed
       key — is stored on disk/removable media, acquired via <constant>AF_UNIX</constant>, or stored in the
       LUKS2 JSON token metadata header. Use the <option>tpm2-device=</option> option described below to use
@@ -713,7 +713,7 @@
 
         <para>The specified URI can refer directly to a private key stored on a token or alternatively
         just to a slot or token, in which case a search for a suitable private key will be performed.  In
-        this case if multiple suitable objects are found the token is refused. The keyfile configured
+        this case, if multiple suitable objects are found, the token is refused. The keyfile configured
         in the third column of the line is used as is (i.e. in binary form, unprocessed). The resulting
         decrypted key (for RSA) or derived shared secret (for ECC) is then Base64 encoded before it is used
         to unlock the LUKS volume.</para>
@@ -783,7 +783,7 @@
         <term><option>fido2-rp=</option></term>
 
         <listitem><para>Takes a string, configuring the FIDO2 Relying Party (rp) for the FIDO2 unlock
-        operation. If not specified <literal>io.systemd.cryptsetup</literal> is used, except if the LUKS2
+        operation. If not specified, <literal>io.systemd.cryptsetup</literal> is used, except if the LUKS2
         JSON token header contains a different value. It should normally not be necessary to override
         this.</para>
 
@@ -891,7 +891,7 @@
         public key specified at key enrollment time can be provided. See
         <citerefentry><refentrytitle>systemd-cryptenroll</refentrytitle><manvolnum>1</manvolnum></citerefentry>
         for details on enrolling TPM2 PCR public keys. If this option is not specified but it is attempted to
-        unlock a LUKS2 volume with a signed TPM2 PCR enrollment a suitable signature file
+        unlock a LUKS2 volume with a signed TPM2 PCR enrollment, a suitable signature file
         <filename>tpm2-pcr-signature.json</filename> is searched for in <filename>/etc/systemd/</filename>,
         <filename>/run/systemd/</filename>, <filename>/usr/lib/systemd/</filename> (in this
         order).</para>
@@ -908,7 +908,7 @@
         variants. See
         <citerefentry><refentrytitle>systemd-cryptenroll</refentrytitle><manvolnum>1</manvolnum></citerefentry>
         for details on enrolling TPM2 pcrlock policies. If this option is not specified but it is attempted
-        to unlock a LUKS2 volume with a TPM2 pcrlock enrollment a suitable signature file
+        to unlock a LUKS2 volume with a TPM2 pcrlock enrollment, a suitable signature file
         <filename>pcrlock.json</filename> is searched for in <filename>/run/systemd/</filename> and
         <filename>/var/lib/systemd/</filename> (in this order).</para>
 
@@ -934,7 +934,7 @@
 
         <listitem><para>Selects one or more TPM2 PCR banks to measure the volume key into, as configured with
         <option>tpm2-measure-pcr=</option> above. Multiple banks may be specified, separated by a colon
-        character. If not specified automatically determines available and used banks. Expects a message
+        character. If not specified, automatically determines available and used banks. Expects a message
         digest name (e.g. <literal>sha1</literal>, <literal>sha256</literal>, …) as argument, to identify the
         bank.</para>
 
@@ -984,10 +984,10 @@
         <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
         units marked with <option>x-initrd.mount</option>.</para>
 
-        <para>Although it's not necessary to mark the mount entry for the root file system with
+        <para>Although it is not necessary to mark the mount entry for the root file system with
         <option>x-initrd.mount</option>, <option>x-initrd.attach</option> is still recommended with
         the encrypted block device containing the root file system as otherwise systemd will
-        attempt to detach the device during the regular system shutdown while it's still in
+        attempt to detach the device during the regular system shutdown while it is still in
         use. With this option the device will still be detached but later after the root file
         system is unmounted.</para>
 

man/directives-template.xml

@@ -163,7 +163,7 @@
   <refsect1>
     <title>Miscellaneous options and directives</title>
 
-    <para>Other configuration elements which don't fit in any of the above groups.</para>
+    <para>Other configuration elements which do not fit in any of the above groups.</para>
 
     <variablelist id='miscellaneous' />
   </refsect1>

man/fido2-crypttab.sh

@@ -8,7 +8,7 @@ sudo systemd-cryptenroll --fido2-device=auto /dev/sdXn
 sudo systemd-cryptsetup attach mytest /dev/sdXn - fido2-device=auto
 
 # If that worked, let's now add the same line persistently to /etc/crypttab,
-# for the future. We don't want to use the (unstable) /dev/sdX name, so let's
+# for the future. We do not want to use the (unstable) /dev/sdX name, so let's
 # figure out a stable link:
 udevadm info -q symlink -r /dev/sdXn
 

man/file-hierarchy.xml

@@ -72,7 +72,7 @@
         <listitem><para>If the boot partition <filename>/boot/</filename> is maintained separately from the
         EFI System Partition (ESP), the latter is mounted here. Tools that need to operate on the EFI system
         partition should look for it at this mount point first, and fall back to <filename>/boot/</filename>
-        — if the former doesn't qualify (for example if it is not a mount point or does not have the correct
+        — if the former does not qualify (for example if it is not a mount point or does not have the correct
         file system type <constant>MSDOS_SUPER_MAGIC</constant>).</para></listitem>
       </varlistentry>
 
@@ -534,7 +534,7 @@
       possible to mount them <option>noexec</option>, because various programs use those directories for
       dynamically generated or optimized code, and with that flag those use cases would break. Using this
       flag is OK on special-purpose installations or systems where all software that may be installed is
-      known and doesn't require such functionality. See the discussion of
+      known and does not require such functionality. See the discussion of
       <option>nosuid</option>/<option>nodev</option>/<option>noexec</option> in <citerefentry
       project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> and
       <constant>PROT_EXEC</constant> in <citerefentry

man/homectl.xml

@@ -261,7 +261,7 @@
 
         <listitem><para>Takes a path to use as home directory for the user. Note that this is the directory
         the user's home directory is mounted to while the user is logged in. This is not where the user's
-        data is actually stored, see <option>--image-path=</option> for that. If not specified defaults to
+        data is actually stored, see <option>--image-path=</option> for that. If not specified, defaults to
         <filename>/home/$USER</filename>.</para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
@@ -329,7 +329,7 @@
 
         <listitem><para>Takes a file system path to a directory. Specifies the skeleton directory to
         initialize the home directory with. All files and directories in the specified path are copied into
-        any newly create home directory. If not specified defaults to <filename>/etc/skel/</filename>.
+        any newly create home directory. If not specified, defaults to <filename>/etc/skel/</filename>.
         </para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
@@ -339,7 +339,7 @@
         <term><option>--shell=<replaceable>SHELL</replaceable></option></term>
 
         <listitem><para>Takes a file system path. Specifies the shell binary to execute on terminal
-        logins. If not specified defaults to <filename>/bin/bash</filename>.</para>
+        logins. If not specified, defaults to <filename>/bin/bash</filename>.</para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
       </varlistentry>
@@ -633,7 +633,7 @@
         After this time passes logging in may only proceed after the password is changed.
         <option>--password-change-warn=</option> specifies how much earlier than then the time configured
         with <option>--password-change-max=</option> the user is warned at login to change their password as
-        it will expire soon. Finally <option>--password-change-inactive=</option> configures the time which
+        it will expire soon. Finally, <option>--password-change-inactive=</option> configures the time which
         has to pass after the password as expired until the user is not permitted to log in or change the
         password anymore. Note that these options only apply to password authentication, and do not apply to
         other forms of authentication, for example PKCS#11-based security token
@@ -896,7 +896,7 @@
         loopback file system instead of immediately from a common pool like the other backends do it). In
         regular intervals free disk space in the active home areas and their backing storage is redistributed
         among them, taking the weight value configured here into account. Expects an integer in the range
-        1…10000, or the special string <literal>off</literal>. If not specified defaults to 100. The weight
+        1…10000, or the special string <literal>off</literal>. If not specified, defaults to 100. The weight
         is used to scale free space made available to the home areas: a home area with a weight of 200 will
         get twice the free space as one with a weight of 100; a home area with a weight of 50 will get half
         of that. The backing file system will be assigned space for a weight of 20. If set to
@@ -914,7 +914,7 @@
         <term><option>--noexec=<replaceable>BOOL</replaceable></option></term>
 
         <listitem><para>Configures the <literal>nosuid</literal>, <literal>nodev</literal> and
-        <literal>noexec</literal> mount options for the home directories. By default <literal>nodev</literal>
+        <literal>noexec</literal> mount options for the home directories. By default, <literal>nodev</literal>
         and <literal>nosuid</literal> are on, while <literal>noexec</literal> is off. For details about these
         mount options see <citerefentry
         project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
@@ -932,7 +932,7 @@
         directory/user account, as well as the file share ("service") to mount as directory. The latter is
         used when <literal>cifs</literal> storage is selected. The file share should be specified in format
         <literal>//<replaceable>host</replaceable>/<replaceable>share</replaceable>/<replaceable>directory/…</replaceable></literal>. The
-        directory part is optional — if not specified the home directory will be placed in the top-level
+        directory part is optional — if not specified, the home directory will be placed in the top-level
         directory of the share. The <option>--cifs-extra-mount-options=</option> setting allows specifying
         additional mount options when mounting the share, see <citerefentry
         project='man-pages'><refentrytitle>mount.cifs</refentrytitle><manvolnum>8</manvolnum></citerefentry>
@@ -948,7 +948,7 @@
         sessions of the user ended. The default is configured in
         <citerefentry><refentrytitle>logind.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> (for
         home directories of LUKS2 storage located on removable media this defaults to 0 though). A longer
-        time makes sure quick, repetitive logins are more efficient as the user's service manager doesn't
+        time makes sure quick, repetitive logins are more efficient as the user's service manager does not
         have to be started every time.</para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
@@ -1310,7 +1310,7 @@ ykman piv generate-key -a RSA2048 9d pubkey.pem
 # Create a self-signed certificate from this public key, and store it on the device.
 ykman piv generate-certificate --subject "Knobelei" 9d pubkey.pem
 
-# We don't need the public key on disk anymore
+# We do not need the public key on disk anymore
 rm pubkey.pem
 
 # Allow the security token to unlock the account of user 'lafcadio'.

man/homed.conf.xml

@@ -60,7 +60,7 @@
         <citerefentry><refentrytitle>homectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>. If not
         configured or assigned the empty string, the default storage is automatically determined: if not
         running in a container environment and <filename>/home/</filename> is not itself encrypted, defaults
-        to <literal>luks</literal>. Otherwise defaults to <literal>subvolume</literal> if
+        to <literal>luks</literal>. Otherwise, defaults to <literal>subvolume</literal> if
         <filename>/home/</filename> is on a btrfs file system, and <literal>directory</literal>
         otherwise. Note that the storage selected on the <command>homectl</command> command line always takes
         precedence.</para>
@@ -72,7 +72,7 @@
         <term><varname>DefaultFileSystemType=</varname></term>
         <listitem><para>When using <literal>luks</literal> as storage (see above), selects the default file
         system to use inside the user's LUKS volume. Takes one of <literal>btrfs</literal>,
-        <literal>ext4</literal> or <literal>xfs</literal>. If not specified defaults to
+        <literal>ext4</literal> or <literal>xfs</literal>. If not specified, defaults to
         <literal>btrfs</literal>. This setting has no effect if a different storage mechanism is used. The
         file system type selected on the <command>homectl</command> command line always takes
         precedence.</para>

man/journalctl.xml

@@ -206,8 +206,8 @@
       <varlistentry>
         <term><option>--namespace=<replaceable>NAMESPACE</replaceable></option></term>
 
-        <listitem><para>Takes a journal namespace identifier string as argument. If not specified the data
-        collected by the default namespace is shown. If specified shows the log data of the specified
+        <listitem><para>Takes a journal namespace identifier string as argument. If not specified, the data
+        collected by the default namespace is shown. If specified, shows the log data of the specified
         namespace instead. If the namespace is specified as <literal>*</literal> data from all namespaces is
         shown, interleaved. If the namespace identifier is prefixed with <literal>+</literal> data from the
         specified namespace and the default namespace is shown, interleaved, but no other. For details about
@@ -272,7 +272,7 @@
         <term><option>--cursor-file=<replaceable>FILE</replaceable></option></term>
 
         <listitem><para>If <replaceable>FILE</replaceable> exists and contains a cursor, start showing
-        entries <emphasis>after</emphasis> this location.  Otherwise show entries according to the other
+        entries <emphasis>after</emphasis> this location. Otherwise, show entries according to the other
         given options. At the end, write the cursor of the last entry to
         <replaceable>FILE</replaceable>. Use this option to continually read the journal by sequentially
         calling <command>journalctl</command>.</para>
@@ -737,7 +737,7 @@
       <varlistentry>
         <term><option>--no-hostname</option></term>
 
-        <listitem><para>Don't show the hostname field of log messages originating from the local host. This
+        <listitem><para>Do not show the hostname field of log messages originating from the local host. This
         switch has an effect only on the <option>short</option> family of output modes (see above).</para>
 
         <para>Note: this option does not remove occurrences of the hostname from log entries themselves, so

man/journald.conf.xml

@@ -422,7 +422,7 @@
         where the console is often a slow, virtual serial port.
         Since journald is implemented as a conventional single-process daemon, forwarding to a completely
         hung console will block journald. This can have a cascading effect resulting in any services synchronously
-        logging to the blocked journal also becoming blocked.  Unless actively debugging/developing something, it's
+        logging to the blocked journal also becoming blocked.  Unless actively debugging/developing something, it is
         generally preferable to setup a <command>journalctl --follow</command> style service redirected to the
         console, instead of ForwardToConsole=yes, for production use.</para>
         </listitem>
@@ -487,7 +487,7 @@
         <para>Note that this option does not control whether <command>systemd-journald</command> collects
         generated audit records, it just controls whether it tells the kernel to generate them. If you need
         to prevent <command>systemd-journald</command> from collecting the generated messages, the socket
-        unit <literal>systemd-journald-audit.socket</literal> can be disabled and in this case this setting
+        unit <literal>systemd-journald-audit.socket</literal> can be disabled and, in this case, this setting
         is without effect.</para>
 
         <xi:include href="version-info.xml" xpointer="v246"/>

man/kernel-command-line.xml

@@ -168,7 +168,7 @@
           the special value <literal>state</literal>. If false (the default), normal boot mode is selected, the root
           directory and <filename>/var/</filename> are mounted as specified on the kernel command line or
           <filename>/etc/fstab</filename>, or otherwise configured. If true, full state-less boot mode is selected. In
-          this case the root directory is mounted as volatile memory file system (<literal>tmpfs</literal>), and only
+          this case, the root directory is mounted as volatile memory file system (<literal>tmpfs</literal>), and only
           <filename>/usr/</filename> is mounted from the file system configured as root device, in read-only mode. This
           enables fully state-less boots were the vendor-supplied OS is used as shipped, with only default
           configuration and no stored state in effect, as <filename>/etc/</filename> and <filename>/var/</filename> (as
@@ -403,7 +403,7 @@
           <para>If <varname>root=</varname> is not set (or set to <literal>gpt-auto</literal>) the automatic
           root partition discovery implemented by
           <citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-          will be in effect. In this case <varname>rootfstype=</varname>, <varname>rootflags=</varname>,
+          will be in effect. In this case, <varname>rootfstype=</varname>, <varname>rootflags=</varname>,
           <varname>ro</varname>, <varname>rw</varname> will be interpreted by
           <command>systemd-gpt-auto-generator</command>.</para>
 
@@ -688,7 +688,7 @@
 
         <programlisting>dd if=/dev/urandom bs=512 count=1 status=none | base64 -w 0</programlisting>
 
-        <para>Again: do not use this option outside of testing environments, it's a security risk elsewhere,
+        <para>Again: do not use this option outside of testing environments, it is a security risk elsewhere,
         as secret key material derived from the entropy pool can possibly be reconstructed by unprivileged
         programs.</para>
 

man/kernel-install.xml

@@ -308,9 +308,9 @@
           <para>If set to <option>auto</option> (the default), the
           <filename>/etc/kernel/entry-token</filename> (or
           <filename>$KERNEL_INSTALL_CONF_ROOT/entry-token</filename>) file will be read if it exists, and the
-          stored value used. Otherwise if the local machine ID is initialized it is used. Otherwise
+          stored value used. Otherwise, if the local machine ID is initialized, it is used. Otherwise,
           <varname>IMAGE_ID=</varname> from <filename>os-release</filename> will be used, if set. Otherwise,
-          <varname>ID=</varname> from <filename>os-release</filename> will be used, if set. Otherwise a
+          <varname>ID=</varname> from <filename>os-release</filename> will be used, if set. Otherwise, a
           randomly generated machine ID is used.</para>
 
           <para>Using the machine ID for naming the entries is generally preferable, however there are cases
@@ -413,7 +413,7 @@
       </variablelist>
 
       <para><varname>$KERNEL_INSTALL_MACHINE_ID</varname> is set for the plugins to the desired machine-id to
-      use. It's always a 128-bit ID. Normally it's read from <filename>/etc/machine-id</filename>, but it can
+      use. It's always a 128-bit ID. Normally it is read from <filename>/etc/machine-id</filename>, but it can
       also be overridden via <varname>$MACHINE_ID</varname> (see below). If not specified via these methods,
       a fallback value will generated by <command>kernel-install</command> and used only for a single
       invocation.</para>
@@ -429,7 +429,7 @@
       <para>Note that while <varname>$KERNEL_INSTALL_ENTRY_TOKEN</varname> and
       <varname>$KERNEL_INSTALL_MACHINE_ID</varname> are often set to the same value, the latter is guaranteed
       to be a valid 32 character ID in lowercase hexadecimals while the former can be any short string. The
-      entry token to use is read from <filename>/etc/kernel/entry-token</filename>, if it exists. Otherwise a
+      entry token to use is read from <filename>/etc/kernel/entry-token</filename>, if it exists. Otherwise, a
       few possible candidates below <varname>$BOOT</varname> are checked for Boot Loader Specification Type 1
       entry directories, and if found the entry token is derived from that. If that is not successful,
       <varname>$KERNEL_INSTALL_MACHINE_ID</varname> is used as fallback.</para>
@@ -442,7 +442,7 @@
 
       <para><varname>$KERNEL_INSTALL_LAYOUT=auto|bls|uki|other|...</varname> is set for the plugins to specify the
       installation layout. Additional layout names may be defined by convention. If a plugin uses a special layout,
-      it's encouraged to declare its own layout name and configure <varname>layout=</varname> in
+      it is encouraged to declare its own layout name and configure <varname>layout=</varname> in
       <filename>install.conf</filename> upon initial installation. The following values are currently
       understood:</para>
 

man/logcontrol-example.c

@@ -220,7 +220,7 @@ int main(int argc, char **argv) {
   if (r < 0)
     return log_error(o.log_level, r, "sd_bus_add_object_vtable()");
 
-  /* By default the service is assigned an ephemeral name. Also add a fixed
+  /* By default, the service is assigned an ephemeral name. Also add a fixed
    * one, so that clients know whom to call.
    * https://www.freedesktop.org/software/systemd/man/sd_bus_request_name.html
    */

man/logind.conf.xml

@@ -386,7 +386,7 @@
 
         <listitem><para>Specifies a timeout in seconds, or a time span value after which
         <filename>systemd-logind</filename> checks the idle state of all sessions. Every session that is idle
-        for longer than the timeout will be stopped. Note that this option doesn't apply to
+        for longer than the timeout will be stopped. Note that this option does not apply to
         <literal>greeter</literal> or <literal>lock-screen</literal> sessions. Defaults to
         <literal>infinity</literal> (<filename>systemd-logind</filename> is not checking the idle state
         of sessions). For details about the syntax of time spans, see

man/machinectl.xml

@@ -422,7 +422,7 @@
         <listitem><para>Edit the settings file of the specified machines. For the format of the settings
         file, refer to
         <citerefentry project='man-pages'><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
-        If an existing settings file of the given machine can't be found, <command>edit</command>
+        If an existing settings file of the given machine cannot be found, <command>edit</command>
         automatically create a new settings file from scratch under
         <filename>/etc/systemd/nspawn/</filename>.
         </para>

man/networkctl.xml

@@ -156,7 +156,7 @@
                 <term>pending</term>
                 <listitem>
                   <para><citerefentry><refentrytitle>systemd-udevd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-                  is still processing the link, we don't yet know if we will manage it.</para>
+                  is still processing the link, we do not yet know if we will manage it.</para>
 
                   <xi:include href="version-info.xml" xpointer="v240"/>
                 </listitem>
@@ -165,7 +165,7 @@
                 <term>initialized</term>
                 <listitem>
                   <para><citerefentry><refentrytitle>systemd-udevd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-                  has processed the link, but we don't yet know if we will manage it.</para>
+                  has processed the link, but we do not yet know if we will manage it.</para>
 
                   <xi:include href="version-info.xml" xpointer="v251"/>
                 </listitem>
@@ -296,7 +296,7 @@
         <listitem>
           <para>Show discovered LLDP (Link Layer Discovery Protocol) neighbors. If one or more
           <replaceable>PATTERN</replaceable>s are specified only neighbors on those interfaces are shown.
-          Otherwise shows discovered neighbors on all interfaces. Note that for this feature to work,
+          Otherwise, shows discovered neighbors on all interfaces. Note that for this feature to work,
           <varname>LLDP=</varname> must be turned on for the specific interface, see
           <citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
           details.</para>
@@ -632,7 +632,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
           drop-in directories are created and populated in one go.</para>
 
           <para>Multiple drop-ins may be "edited" in this mode with <option>--drop-in=</option>, and
-          the same contents will be written to all of them. Otherwise exactly one main configuration file
+          the same contents will be written to all of them. Otherwise, exactly one main configuration file
           is expected.</para>
 
           <xi:include href="version-info.xml" xpointer="v257"/>

man/nss-systemd.xml

@@ -39,7 +39,7 @@
     <citerefentry><refentrytitle>systemd-homed.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>, or <citerefentry><refentrytitle>systemd-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
 
     <para>This module also ensures that the root and nobody users and groups (i.e. the users/groups with the UIDs/GIDs
-    0 and 65534) remain resolvable at all times, even if they aren't listed in <filename>/etc/passwd</filename> or
+    0 and 65534) remain resolvable at all times, even if they are not listed in <filename>/etc/passwd</filename> or
     <filename>/etc/group</filename>, or if these files are missing.</para>
 
     <para>This module preferably utilizes

man/org.freedesktop.home1.xml

@@ -568,7 +568,7 @@ node /org/freedesktop/home1/home {
       operate like their matching counterparts on the <classname>org.freedesktop.home1.Manager</classname>
       interface (see above). The main difference is that they are methods of the home directory objects, and
       hence carry no additional user name parameter. Which of the two flavors of methods to call depends on
-      the handles to the user known on the client side: if only the user name is known, it's preferable to use
+      the handles to the user known on the client side: if only the user name is known, it is preferable to use
       the methods on the manager object since they operate with user names only. Clients can also easily operate
       on their own home area by using the methods on the manager object with an empty string as the user name.
       If the client has the home's object path already acquired in some way, however, it is preferable to operate

man/org.freedesktop.login1.xml

@@ -1420,7 +1420,7 @@ node /org/freedesktop/login1/session/1 {
       only works on devices that are attached to the seat of the given session. A process is not required to
       have direct access to the device node. <filename>systemd-logind</filename> only requires you to be the
       active session controller (see <function>TakeControl()</function>). Also note that any device can only
-      be requested once. As long as you don't release it, further <function>TakeDevice()</function> calls
+      be requested once. As long as you do not release it, further <function>TakeDevice()</function> calls
       will fail.</para>
 
       <para><function>ReleaseDevice()</function> releases a device again (see
@@ -1465,7 +1465,7 @@ node /org/freedesktop/login1/session/1 {
       notification. <function>pause</function> means <filename>systemd-logind</filename> grants you a limited amount of time to pause the device. You must respond to this via
       <function>PauseDeviceComplete()</function>. This synchronous pausing mechanism is used for
       backwards-compatibility to VTs and <filename>systemd-logind</filename> is free to not make use of
-      it. It is also free to send a forced <function>PauseDevice()</function> if you don't respond in a timely
+      it. It is also free to send a forced <function>PauseDevice()</function> if you do not respond in a timely
       manner (or for any other reason). <function>gone</function> means the device was unplugged from the
       system and you will no longer get any notifications about it. There is no need to call
       <function>ReleaseDevice()</function>. You may call <function>TakeDevice()</function> again if a new

man/org.freedesktop.resolve1.xml

@@ -500,7 +500,7 @@ node /org/freedesktop/resolve1 {
         hence where the data was found.</para>
 
         <para>The primary use cases for these five flags are follow-up look-ups based on DNS data retrieved
-        earlier. In this case it is often a good idea to limit the follow-up look-up to the protocol that was
+        earlier. In this case, it is often a good idea to limit the follow-up look-up to the protocol that was
         used to discover the first DNS result.</para>
 
         <para>The NO_CNAME flag controls whether CNAME/DNAME resource records shall be followed during the
@@ -625,7 +625,7 @@ node /org/freedesktop/resolve1 {
       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
+      validation did not check out and the data is likely to have been tempered with. Finally, the
       indeterminate counter is increased for each operation which did not complete because the necessary keys
       could not be acquired or the cryptographic algorithms were unknown.</para>
 

man/org.freedesktop.systemd1.xml

@@ -1283,7 +1283,7 @@ node /org/freedesktop/systemd1 {
       its dependencies, possibly replacing already queued jobs that conflict with it. If
       <literal>fail</literal>, the method will start the unit and its dependencies, but will fail if this would
       change an already queued job. If <literal>isolate</literal>, the method will start the unit in question
-      and terminate all units that aren't dependencies of it. If <literal>ignore-dependencies</literal>, it
+      and terminate all units that are not dependencies of it. If <literal>ignore-dependencies</literal>, it
       will start a unit but ignore all its dependencies. If <literal>ignore-requirements</literal>, it will
       start a unit but only ignore the requirement dependencies. It is not recommended to make use of the
       latter two options. On reply, if successful, this method returns the newly created job object
@@ -1309,8 +1309,8 @@ node /org/freedesktop/systemd1 {
       <function>TryRestartUnit()</function>, <function>ReloadOrRestartUnit()</function>, or
       <function>ReloadOrTryRestartUnit()</function> may be used to restart and/or reload a unit. These methods take
       similar arguments as <function>StartUnit()</function>. Reloading is done only if the unit is already
-      running and fails otherwise. If a service is restarted that isn't running, it will be started unless
-      the "Try" flavor is used in which case a service that isn't running is not affected by the restart. The
+      running and fails otherwise. If a service is restarted that is not running, it will be started unless
+      the "Try" flavor is used in which case a service that is not running is not affected by the restart. The
       "ReloadOrRestart" flavors attempt a reload if the unit supports it and use a restart otherwise.</para>
 
       <para><function>EnqueueMarkedJobs()</function> creates reload/restart jobs for units which have been
@@ -1619,12 +1619,12 @@ node /org/freedesktop/systemd1 {
       <literal>failed</literal>, <literal>dependency</literal>, or
       <literal>skipped</literal>. <literal>done</literal> indicates successful execution of a
       job. <literal>canceled</literal> indicates that a job has been canceled (via
-      <function>CancelJob()</function> above) before it finished execution (this doesn't necessarily mean
+      <function>CancelJob()</function> above) before it finished execution (this does not necessarily mean
       though that the job operation is actually cancelled too, see above). <literal>timeout</literal>
       indicates that the job timeout was reached. <literal>failed</literal> indicates that the job
       failed. <literal>dependency</literal> indicates that a job this job depended on failed and the job hence
       was removed as well. <literal>skipped</literal> indicates that a job was skipped because
-      it didn't apply to the unit's current state.</para>
+      it did not apply to the unit's current state.</para>
 
       <para><function>StartupFinished()</function> is sent out when startup finishes. It carries six
       microsecond timespan values, each indicating how much boot time has been spent in the firmware (if
@@ -2575,7 +2575,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       reboot). <literal>masked</literal> indicates that the unit file is masked permanently.
       <literal>masked-runtime</literal> indicates that it is masked in <filename>/run/</filename> temporarily
       (until the next reboot). <literal>static</literal> indicates that the unit is statically enabled, i.e.
-      always enabled and doesn't need to be enabled explicitly. <literal>invalid</literal> indicates that it
+      always enabled and does not need to be enabled explicitly. <literal>invalid</literal> indicates that it
       could not be determined whether the unit file is enabled.</para>
 
       <para><varname>InactiveExitTimestamp</varname>, <varname>InactiveExitTimestampMonotonic</varname>,
@@ -2636,7 +2636,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       five fields are given: condition type (e.g. <varname>ConditionPathExists</varname>), whether the
       condition is a trigger condition, whether the condition is reversed, the right hand side of the
       condition (e.g. the path in case of <varname>ConditionPathExists</varname>), and the status. The status
-      can be 0, in which case the condition hasn't been checked yet, a positive value, in which case the
+      can be 0, in which case the condition has not been checked yet, a positive value, in which case the
       condition passed, or a negative value, in which case the condition is not met. Currently only 0, +1, and -1
       are used, but additional values may be used in the future, retaining the meaning of
       zero/positive/negative values.</para>
@@ -4767,7 +4767,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       with runtime data.</para>
 
       <para><varname>LimitCPU</varname> (and related properties) map more or less directly to the
-      corresponding settings in the service unit files except that if they aren't set, their value is
+      corresponding settings in the service unit files except that if they are not set their value is
       18446744073709551615 (i.e. -1).</para>
 
       <para><varname>Capabilities</varname> contains the configured capabilities, as formatted with
@@ -4813,7 +4813,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       <para><varname>Result</varname> encodes the execution result of the last run of the service. It is
       useful to determine the reason a service failed if it is in the <literal>failed</literal> state (see
       <varname>ActiveState</varname> above). The following values are currently known:
-      <literal>success</literal> is set if the unit didn't fail. <literal>resources</literal> indicates that
+      <literal>success</literal> is set if the unit did not fail. <literal>resources</literal> indicates that
       not enough resources were available to fork off and execute the service
       processes. <literal>timeout</literal> indicates that a timeout occurred while executing a service
       operation. <literal>exit-code</literal> indicates that a service process exited with an unclean exit
@@ -6890,8 +6890,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2esocket {
 
     <!--End of Autogenerated section-->
 
-    <para><varname>PollLimitIntervalUSec</varname>/<varname>PollLimitBurst</varname> properties configure the
-    polling limit for the socket unit. Expects a time in µs, resp. an unsigned integer. If either is set to
+    <para>The <varname>PollLimitIntervalUSec</varname> and <varname>PollLimitBurst</varname> properties configure the
+    polling limit for the socket unit. Expects a time in µs and unsigned integer, respectively. If either is set to
     zero the limiting feature is turned off.</para>
 
     <refsect2>

man/org.freedesktop.sysupdate1.xml

@@ -284,7 +284,7 @@ node /org/freedesktop/sysupdate1/target/host {
       software center to correctly associate the catalogs with this target.</para>
 
       <para><function>GetVersion()</function> returns the current version of this target, if any. The current
-      version is the newest version that is installed. Note that this isn't necessarily the same thing as the
+      version is the newest version that is installed. Note that this is not necessarily the same thing as the
       booted or currently-in-use version of the target.  For example, on the host system the booted version
       is the current version most of the time, but if an update is installed and pending a reboot it will
       become the current version instead.  You can query the booted version of the host system via

man/os-release.xml

@@ -120,7 +120,7 @@
 
       <para>In the <filename>extension-release.<replaceable>IMAGE</replaceable></filename> filename, the
       <replaceable>IMAGE</replaceable> part must exactly match the file name of the containing image with the
-      suffix removed. In case it is not possible to guarantee that an image file name is stable and doesn't
+      suffix removed. In case it is not possible to guarantee that an image file name is stable and does not
       change between the build and the deployment phases, it is possible to relax this check: if exactly one
       file whose name matches <literal><filename>extension-release.*</filename></literal> is present in this
       directory, and the file is tagged with a <varname>user.extension-release.strict</varname>

man/pam_systemd.xml

@@ -192,7 +192,7 @@
         for details on the capabilities concept. If not specified, the default bounding set is left as is
         (i.e. usually contains the full set of capabilities). The default ambient set is set to
         <constant>CAP_WAKE_ALARM</constant> for regular users if the PAM session is associated with a local
-        seat or if it is invoked for the <literal>systemd-user</literal> service. Otherwise defaults to the
+        seat or if it is invoked for the <literal>systemd-user</literal> service. Otherwise, defaults to the
         empty set.</para>
 
         <xi:include href="version-info.xml" xpointer="v254"/></listitem>

man/pam_systemd_home.xml

@@ -65,8 +65,8 @@
         user concurrently uses graphical login sessions that implement the required re-authentication
         mechanism and console logins that do not, the home directory is not locked during suspend, due to the
         logic explained above. That said, it is possible to set this field for TTY logins too, ignoring the
-        fact that TTY logins actually don't support the re-authentication mechanism. In that case the TTY
-        sessions will appear hung until the user logs in on another virtual terminal (regardless if via
+        fact that TTY logins actually do not support the re-authentication mechanism. In that case the TTY
+        sessions will appear hung until the user logs in on another virtual terminal (regardless of whether via
         another TTY session or graphically) which will resume the home directory and unblock the original TTY
         session. (Do note that lack of screen locking on TTY sessions means even though the TTY session
         appears hung, keypresses can still be queued into it, and the existing screen contents be read

man/portablectl.xml

@@ -119,7 +119,7 @@
           <filename>/run/portables/</filename>, to make sure it is included in it.</para></listitem>
         </orderedlist>
 
-        <para>By default all unit files whose names start with a prefix generated from the image's file name are copied
+        <para>By default, all unit files whose names start with a prefix generated from the image's file name are copied
         out. Specifically, the prefix is determined from the image file name with any suffix such as
         <filename>.raw</filename> removed, truncated at the first occurrence of an underscore character
         (<literal>_</literal>), if there is one. The underscore logic is supposed to be used to versioning so that the
@@ -170,7 +170,7 @@
         <listitem><para>Detaches an existing portable service image from the host, and immediately attaches it again.
         This is useful in case the image was replaced. Running units are not stopped during the process. Partial matching,
         to allow for different versions in the image name, is allowed: only the part before the first <literal>_</literal>
-        character has to match. If the new image doesn't exist, the existing one will not be detached. The parameters
+        character has to match. If the new image does not exist, the existing one will not be detached. The parameters
         follow the same syntax as the <command>attach</command> command.</para>
 
         <para>If <option>--now</option> and/or <option>--enable</option> are passed, the portable services are
@@ -186,7 +186,7 @@
         <listitem><para>Extracts various metadata from a portable service image and presents it to the
         caller. Specifically, the
         <citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry> file of the
-        image is retrieved as well as all matching unit files. By default a short summary showing the most relevant
+        image is retrieved as well as all matching unit files. By default, a short summary showing the most relevant
         metadata in combination with a list of matching unit files is shown (that is the unit files
         <command>attach</command> would install to the host system). If combined with <option>--cat</option> (see
         above), the <filename>os-release</filename> data and the units files' contents is displayed unprocessed. This
@@ -314,7 +314,7 @@
         <term><option>-p</option> <replaceable>PROFILE</replaceable></term>
         <term><option>--profile=<replaceable>PROFILE</replaceable></option></term>
 
-        <listitem><para>When attaching an image, select the profile to use. By default the <literal>default</literal>
+        <listitem><para>When attaching an image, select the profile to use. By default, the <literal>default</literal>
         profile is used. For details about profiles, see below.</para>
 
         <xi:include href="version-info.xml" xpointer="v239"/></listitem>
@@ -350,7 +350,7 @@
       <varlistentry>
         <term><option>--no-reload</option></term>
 
-        <listitem><para>Don't reload the service manager after attaching or detaching a portable service
+        <listitem><para>Do not reload the service manager after attaching or detaching a portable service
         image. Normally the service manager is reloaded to ensure it is aware of added or removed unit
         files.</para>
 
@@ -388,7 +388,7 @@
       <varlistentry>
         <term><option>--no-block</option></term>
 
-        <listitem><para>Don't block waiting for attach --now to complete.</para>
+        <listitem><para>Do not block waiting for attach --now to complete.</para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
       </varlistentry>

man/poweroff.xml

@@ -129,7 +129,7 @@
         <term><option>-n</option></term>
         <term><option>--no-sync</option></term>
 
-        <listitem><para>Don't sync hard disks/storage media before power-off, reboot, or halt.
+        <listitem><para>Do not sync hard disks/storage media before power-off, reboot, or halt.
         </para>
 
         <xi:include href="version-info.xml" xpointer="v253"/></listitem>

man/repart.d.xml

@@ -60,7 +60,7 @@
     no matching partition file are left as they are.</para>
 
     <para>Note that these definitions may only be used to create and initialize new partitions or to grow
-    existing ones. In the latter case it will not grow the contained files systems however; separate
+    existing ones. In the latter case, it will not grow the contained files systems however; separate
     mechanisms, such as
     <citerefentry><refentrytitle>systemd-growfs</refentrytitle><manvolnum>8</manvolnum></citerefentry> may be
     used to grow the file systems inside of these partitions. Partitions may also be marked for automatic
@@ -250,7 +250,7 @@
         <listitem><para>The textual label to assign to the partition if none is assigned yet. Note that this
         setting is not used for matching. It is also not used when a label is already set for an existing
         partition. It is thus only used when a partition is newly created or when an existing one had a no
-        label set (that is: an empty label). If not specified a label derived from the partition type is
+        label set (that is: an empty label). If not specified, a label derived from the partition type is
         automatically used. Simple specifier expansion is supported, see below.</para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
@@ -338,7 +338,7 @@
         <varname>SizeMaxBytes=</varname>) otherwise. If the backing device does not provide enough space to
         fulfill the constraints placing the partition will fail. For partitions that shall be created,
         depending on the setting of <varname>Priority=</varname> (see above) the partition might be dropped
-        and the placing algorithm restarted. By default a minimum size constraint of 10M and no maximum size
+        and the placing algorithm restarted. By default, a minimum size constraint of 10M and no maximum size
         constraint is set.</para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
@@ -351,7 +351,7 @@
         <listitem><para>Specifies minimum and maximum size constraints in bytes for the free space after the
         partition (the "padding"). Semantics are similar to <varname>SizeMinBytes=</varname> and
         <varname>SizeMaxBytes=</varname>, except that unlike partition sizes free space can be shrunk and can
-        be as small as zero. By default no size constraints on padding are set, so that only
+        be as small as zero. By default, no size constraints on padding are set, so that only
         <varname>PaddingWeight=</varname> determines the size of the padding applied.</para>
 
         <xi:include href="version-info.xml" xpointer="v245"/></listitem>
@@ -391,7 +391,7 @@
         <para>This option has no effect if the partition it is declared for already exists, i.e. existing
         data is never overwritten. Note that the data is copied in before the partition table is updated,
         i.e. before the partition actually is persistently created. This provides robustness: it is
-        guaranteed that the partition either doesn't exist or exists fully populated; it is not possible that
+        guaranteed that the partition either does not exist or exists fully populated; it is not possible that
         the partition exists but is not or only partially populated.</para>
 
         <para>This option cannot be combined with <varname>Format=</varname> or
@@ -445,7 +445,7 @@
         <para>The copy operation is executed before the file system is registered in the partition table,
         thus ensuring that a file system populated this way only ever exists fully initialized.</para>
 
-        <para>Note that <varname>CopyFiles=</varname> will skip copying files that aren't supported by the
+        <para>Note that <varname>CopyFiles=</varname> will skip copying files that are not supported by the
         target filesystem (e.g symlinks, fifos, sockets and devices on vfat). When an unsupported file type
         is encountered, <command>systemd-repart</command> will skip copying this file and write a log message
         about it.</para>
@@ -718,7 +718,7 @@
         <term><varname>Flags=</varname></term>
 
         <listitem><para>Configures the 64-bit GPT partition flags field to set for the partition when creating
-        it. This option has no effect if the partition already exists. If not specified the flags values is
+        it. This option has no effect if the partition already exists. If not specified, the flags value is
         set to all zeroes, except for the three bits that can also be configured via
         <varname>NoAuto=</varname>, <varname>ReadOnly=</varname> and <varname>GrowFileSystem=</varname>; see
         below for details on the defaults for these three flags. Specify the flags value in hexadecimal (by

man/resolvectl.xml

@@ -43,7 +43,7 @@
 
     <para>The program's output contains information about the protocol used for the look-up and on which network
     interface the data was discovered. It also contains information on whether the information could be
-    authenticated. All data for which local DNSSEC validation succeeds is considered authenticated. Moreover all data
+    authenticated. All data for which local DNSSEC validation succeeds is considered authenticated. Moreover, all data
     originating from local, trusted sources is also reported authenticated, including resolution of the local host
     name, the <literal>localhost</literal> hostname or all data from <filename>/etc/hosts</filename>.</para>
   </refsect1>
@@ -84,10 +84,10 @@
         <ulink url="https://tools.ietf.org/html/rfc2782">RFC 2782 SRV</ulink> services, depending on the
         specified list of parameters. If three parameters are passed the first is assumed to be the DNS-SD
         service name, the second the <constant class='dns'>SRV</constant> service type, and the third the
-        domain to search in. In this case a full DNS-SD style <constant class='dns'>SRV</constant> and
+        domain to search in. In this case, a full DNS-SD style <constant class='dns'>SRV</constant> and
         <constant class='dns'>TXT</constant> lookup is executed. If only two parameters are specified, the
         first is assumed to be the <constant class='dns'>SRV</constant> service type, and the second the
-        domain to look in. In this case no <constant class='dns'>TXT</constant> resource record is requested.
+        domain to look in. In this case, no <constant class='dns'>TXT</constant> resource record is requested.
         Finally, if only one parameter is specified, it is assumed to be a domain name, that is already
         prefixed with an <constant class='dns'>SRV</constant> type, and an <constant
         class='dns'>SRV</constant> lookup is done (no <constant class='dns'>TXT</constant>).</para>
@@ -298,7 +298,7 @@
         <literal>llmnr-ipv4</literal>, <literal>llmnr-ipv6</literal> (LLMNR via the indicated underlying IP
         protocols), <literal>mdns</literal> (<ulink url="https://www.ietf.org/rfc/rfc6762.txt">Multicast DNS</ulink>),
         <literal>mdns-ipv4</literal>, <literal>mdns-ipv6</literal> (MDNS via the indicated underlying IP protocols).
-        By default the lookup is done via all protocols suitable for the lookup. If used, limits the set of
+        By default, the lookup is done via all protocols suitable for the lookup. If used, limits the set of
         protocols that may be used. Use this option multiple times to enable resolving via multiple protocols at the
         same time. The setting <literal>llmnr</literal> is identical to specifying this switch once with
         <literal>llmnr-ipv4</literal> and once via <literal>llmnr-ipv6</literal>. Note that this option does not force
@@ -399,7 +399,7 @@
 
         <listitem><para>Takes a boolean parameter; used in conjunction with <command>query</command>. If true
         (the default), lookups use the local DNS resource record cache. If false, lookups are routed to the
-        network instead, regardless if already available in the local cache.</para>
+        network instead, regardless of whether already available in the local cache.</para>
 
         <xi:include href="version-info.xml" xpointer="v248"/></listitem>
       </varlistentry>

man/resolved.conf.xml

@@ -201,7 +201,7 @@
         returned data could not be verified (either because the data
         was found unsigned in the DNS, or the DNS server did not
         support DNSSEC or no appropriate trust anchors were known). In
-        the latter case it is assumed that client programs employ a
+        the latter case, it is assumed that client programs employ a
         secondary scheme to validate the returned DNS data, should
         this be required.</para>
 
@@ -294,7 +294,7 @@
       <varlistentry>
         <term><varname>CacheFromLocalhost=</varname></term>
         <listitem><para>Takes a boolean as argument. If <literal>no</literal> (the default), and response cames from
-        host-local IP address (such as 127.0.0.1 or ::1), the result wouldn't be cached in order to avoid
+        host-local IP address (such as 127.0.0.1 or ::1), the result would not be cached in order to avoid
         potential duplicate local caching.</para>
 
         <xi:include href="version-info.xml" xpointer="v248"/>
@@ -382,7 +382,7 @@ DNSStubListenerExtra=udp:[2001:db8:0:f102::13]:9953</programlisting>
         <para>This is useful when a DNS server failure occurs or becomes unreachable. In such cases,
         <citerefentry><refentrytitle>systemd-resolved</refentrytitle><manvolnum>8</manvolnum></citerefentry>
         continues to use the stale records to answer DNS queries, particularly when no valid response can be
-        obtained from the upstream DNS servers. However, this doesn't apply to NXDOMAIN responses, as those
+        obtained from the upstream DNS servers. However, this does not apply to NXDOMAIN responses, as those
         are still perfectly valid responses. This feature enhances resilience against DNS infrastructure
         failures and outages.</para>
 

man/run0.xml

@@ -215,7 +215,7 @@
 
         <listitem><para>Set a shell prompt prefix string. This ultimately controls the
         <varname>$SHELL_PROMPT_PREFIX</varname> environment variable for the invoked program, which is
-        typically imported into the shell prompt. By default – if emojis are supported – a superhero emoji is
+        typically imported into the shell prompt. By default – if emojis are supported –, a superhero emoji is
         shown (🦸). This default may also be changed (or turned off) by passing the
         <varname>$SYSTEMD_RUN_SHELL_PROMPT_PREFIX</varname> environment variable to <varname>run0</varname>,
         see below. Set to an empty string to disable shell prompt prefixing.</para>
@@ -291,7 +291,7 @@
 
       <varlistentry>
         <term><varname>$SHELL_PROMPT_PREFIX</varname></term>
-        <listitem><para>By default set to the superhero emoji (if supported), but may be overridden with the
+        <listitem><para>By default, set to the superhero emoji (if supported), but may be overridden with the
         <varname>$SYSTEMD_RUN_SHELL_PROMPT_PREFIX</varname> environment variable (see below), or the
         <option>--shell-prompt-prefix=</option> switch (see above).</para>
 

man/sd-json.xml

@@ -40,7 +40,7 @@
 
     <para>The API's central data structure is <type>JsonVariant</type> which encapsulates a JSON object,
     array, string, boolean, number or null value. These data structures are mostly considered immutable after
-    construction (i.e. their contents won't change, but some meta-data might, such as reference counters).</para>
+    construction (i.e. their contents will not change, but some meta-data might, such as reference counters).</para>
 
     <para>The APIs broadly fall into five categories:</para>
 

man/sd_bus_add_match.xml

@@ -134,7 +134,7 @@
 
     <para>If an error occurs during the callback invocation, the callback should return a negative error number
     (optionally, a more precise error may be returned in <parameter>ret_error</parameter>, as well). If it wants other
-    callbacks that match the same rule to be called, it should return 0. Otherwise it should return a positive integer.
+    callbacks that match the same rule to be called, it should return 0. Otherwise, it should return a positive integer.
     </para>
 
     <para>If the <parameter>bus</parameter> refers to a direct connection (i.e. not a bus connection, as set with

man/sd_bus_attach_event.xml

@@ -58,7 +58,7 @@
     will be automatically read and processed, and outgoing messages written, whenever the event loop is run. When the
     event loop is about to terminate, the bus connection is automatically flushed and closed (see
     <citerefentry><refentrytitle>sd_bus_set_close_on_exit</refentrytitle><manvolnum>3</manvolnum></citerefentry> for
-    details on this). By default bus connection objects are not attached to any event loop. When a bus connection
+    details on this). By default, bus connection objects are not attached to any event loop. When a bus connection
     object is attached to one it is not necessary to invoke
     <citerefentry><refentrytitle>sd_bus_wait</refentrytitle><manvolnum>3</manvolnum></citerefentry> or
     <citerefentry><refentrytitle>sd_bus_process</refentrytitle><manvolnum>3</manvolnum></citerefentry> as this

man/sd_bus_get_fd.xml

@@ -77,7 +77,7 @@
     <constant>CLOCK_MONOTONIC</constant> and specified in microseconds. When converting this value in order
     to pass it as third argument to <function>poll()</function> (which expects relative milliseconds), care
     should be taken to convert to a relative time and use a division that rounds up to ensure the I/O polling
-    operation doesn't sleep for shorter than necessary, which might result in unintended busy looping
+    operation does not sleep for shorter than necessary, which might result in unintended busy looping
     (alternatively, use <citerefentry
     project='man-pages'><refentrytitle>ppoll</refentrytitle><manvolnum>2</manvolnum></citerefentry> instead
     of plain <function>poll()</function>, which understands timeouts with nano-second granularity).</para>

man/sd_bus_message_read.xml

@@ -209,7 +209,7 @@ sd_bus_message_read(m, "x", &amp;x);</programlisting>
     <para>Read a boolean value:</para>
 
     <programlisting>sd_bus_message *m;
-int x; /* Do not use C99 'bool' type here, it's typically smaller
+int x; /* Do not use C99 "bool" type here, it is typically smaller
           in memory and would cause memory corruption */
 
 sd_bus_message_read(m, "b", &amp;x);</programlisting>

man/sd_bus_message_seal.xml

@@ -45,7 +45,7 @@
     corresponding request. <parameter>timeout_usec</parameter> specifies the maximum time in
     microseconds to wait for a reply to arrive.</para>
 
-    <para>Note that in most scenarios, it's not necessary to call this function directly.
+    <para>Note that in most scenarios, it is not necessary to call this function directly.
     <citerefentry><refentrytitle>sd_bus_call</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
     <citerefentry><refentrytitle>sd_bus_call_async</refentrytitle><manvolnum>3</manvolnum></citerefentry> and
     <citerefentry><refentrytitle>sd_bus_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>

man/sd_bus_message_sensitive.xml

@@ -39,7 +39,7 @@
     sensitive data. This ensures that the message data is carefully removed from memory (specifically,
     overwritten with zero bytes) when released. It is recommended to mark all incoming and outgoing messages
     like this that contain security credentials and similar data that should be dealt with carefully. Note
-    that it is not possible to unmark messages like this, it's a one way operation. If a message is already
+    that it is not possible to unmark messages like this, it is a one way operation. If a message is already
     marked sensitive and then marked sensitive a second time the message remains marked so and no further
     operation is executed.</para>
 

man/sd_bus_message_set_destination.xml

@@ -81,7 +81,7 @@
     <function>sd_bus_message_get_member()</function> return the destination, path, interface, and
     member fields from <parameter>message</parameter> header. The return value will be
     <constant>NULL</constant> is <parameter>message</parameter> is <constant>NULL</constant> or the
-    message is of a type that doesn't use those fields or the message doesn't have them set. See
+    message is of a type that does not use those fields or the message does not have them set. See
     <citerefentry><refentrytitle>sd_bus_message_new_method_call</refentrytitle><manvolnum>3</manvolnum></citerefentry> and
     <citerefentry><refentrytitle>sd_bus_message_set_destination</refentrytitle><manvolnum>3</manvolnum></citerefentry>
     for more discussion of those values.</para>
@@ -96,7 +96,7 @@
 
     <para>When a string is returned, it is a pointer to internal storage, and may not be modified or
     freed. It is only valid as long as the <parameter>message</parameter> remains referenced and
-    this field hasn't been changed by a different call.</para>
+    this field has not been changed by a different call.</para>
   </refsect1>
 
   <refsect1>

man/sd_bus_query_sender_creds.xml

@@ -52,7 +52,7 @@
     for a list of possible flags. First, this message checks if the requested credentials are attached to the
     message itself. If not, but the message contains the pid of the sender and the caller specified the
     <constant index='false'>SD_BUS_CREDS_AUGMENT</constant> flag, this function tries to figure out
-    the missing credentials via other means (starting from the pid). If the pid isn't available but the
+    the missing credentials via other means (starting from the pid). If the PID is not available but the
     message has a sender, this function calls
     <citerefentry><refentrytitle>sd_bus_get_name_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>
     to get the requested credentials. If the message has no sender (when a direct connection is used), this

man/sd_bus_send.xml

@@ -56,11 +56,11 @@
     <para><function>sd_bus_send()</function> queues the bus message object <parameter>m</parameter> for
     transfer. If <parameter>bus</parameter> is <constant>NULL</constant>, the bus that
     <parameter>m</parameter> is attached to is used. <parameter>bus</parameter> only needs to be set when the
-    message is sent to a different bus than the one it's attached to, for example when forwarding messages.
+    message is sent to a different bus than the one it is attached to, for example when forwarding messages.
     If the output parameter <parameter>cookie</parameter> is not <constant>NULL</constant>, it is set to the
     message identifier. This value can later be used to match incoming replies to their corresponding
     messages. If <parameter>cookie</parameter> is set to <constant>NULL</constant> and the message is not
-    sealed, <function>sd_bus_send()</function> assumes the message <parameter>m</parameter> doesn't expect a
+    sealed, <function>sd_bus_send()</function> assumes the message <parameter>m</parameter> does not expect a
     reply and adds the necessary headers to indicate this.</para>
 
     <para>Note that in most scenarios, <function>sd_bus_send()</function> should not be called

man/sd_bus_service_reconnect.c

@@ -181,7 +181,7 @@ static int setup(object *o) {
                                o);
   if (r < 0)
     return log_error(r, "sd_bus_add_object_vtable()");
-  /* By default the service is only assigned an ephemeral name. Also add a
+  /* By default, the service is only assigned an ephemeral name. Also add a
    * well-known one, so that clients know whom to call. This needs to be
    * asynchronous, as D-Bus might not be yet available. The callback will check
    * whether the error is expected or not, in case it fails.
@@ -242,7 +242,7 @@ int main(int argc, char **argv) {
   if (r < 0)
     return log_error(r, "sd_event_default()");
 
-  /* By default the event loop will terminate when all sources have disappeared,
+  /* By default, the event loop will terminate when all sources have disappeared,
    * so we have to keep it 'occupied'. Register signal handling to do so.
    * https://www.freedesktop.org/software/systemd/man/sd_event_add_signal.html
    */

man/sd_bus_set_close_on_exit.xml

@@ -55,7 +55,7 @@
     <citerefentry><refentrytitle>sd-event</refentrytitle><manvolnum>3</manvolnum></citerefentry>
     event loop, see
     <citerefentry><refentrytitle>sd_bus_attach_event</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
-    By default this mechanism is enabled and makes sure that any pending messages that have not been
+    By default, this mechanism is enabled and makes sure that any pending messages that have not been
     written to the bus connection are written out when the event loop is shutting down. In some
     cases this behaviour is not desirable, for example when the bus connection shall remain usable
     until after the event loop exited. If <parameter>b</parameter> is true, the feature is enabled

man/sd_bus_set_sender.xml

@@ -50,7 +50,7 @@
     that are sent on the connection and have no sender set yet, for example through
     <citerefentry><refentrytitle>sd_bus_message_set_sender</refentrytitle><manvolnum>3</manvolnum></citerefentry>. Note
     that this function is only supported on direct connections, i.e. not on connections to a bus broker as the broker
-    will fill in the sender service name automatically anyway. By default no sender name is configured, and hence
+    will fill in the sender service name automatically anyway. By default, no sender name is configured, and hence
     messages are sent without sender field set. If the <parameter>name</parameter> parameter is specified as
     <constant>NULL</constant> the default sender service name is cleared, returning to the default state if a default
     sender service name was set before. If passed as non-<constant>NULL</constant> the specified name must be a valid

man/sd_bus_set_watch_bind.xml

@@ -61,7 +61,7 @@
     <citerefentry><refentrytitle>sd_bus_call</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
     <citerefentry><refentrytitle>sd_bus_add_match</refentrytitle><manvolnum>3</manvolnum></citerefentry> or
     <citerefentry><refentrytitle>sd_bus_request_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>),
-    that is used on a connection with this feature enabled that hasn't been established yet, might block
+    that is used on a connection with this feature enabled that has not been established yet, might block
     forever if the socket is never created. However, asynchronous remote operations (such as
     <citerefentry><refentrytitle>sd_bus_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
     <citerefentry><refentrytitle>sd_bus_call_async</refentrytitle><manvolnum>3</manvolnum></citerefentry>,

man/sd_bus_track_add_name.xml

@@ -126,7 +126,7 @@
     <para><function>sd_bus_track_count()</function> returns the number of names currently being tracked by the
     specified bus peer tracking object. Note that this function always returns the actual number of names tracked, and
     hence if <function>sd_bus_track_add_name()</function> has been invoked multiple times for the same name it is only
-    counted as one, regardless if recursive mode is used or not.</para>
+    counted as one, regardless of whether recursive mode is used or not.</para>
 
     <para><function>sd_bus_track_count_name()</function> returns the current per-name counter for the specified
     name. If non-recursive mode is used this returns either 1 or 0, depending on whether the specified name has been
@@ -159,7 +159,7 @@
 
     <para>On success, <function>sd_bus_track_add_name()</function> and <function>sd_bus_track_add_sender()</function>
     return 0 if the specified name has already been added to the bus peer tracking object before and positive if it
-    hasn't. On failure, they return a negative errno-style error code.</para>
+    has not. On failure, they return a negative errno-style error code.</para>
 
     <para><function>sd_bus_track_remove_name()</function> and <function>sd_bus_track_remove_sender()</function> return
     positive if the specified name was previously tracked by the bus peer tracking object and has now been removed. In

man/sd_bus_track_new.xml

@@ -137,7 +137,7 @@
     irrelevant and the tracking of the specific peer is immediately
     removed. <function>sd_bus_track_get_recursive()</function> may be used to determine whether the bus peer tracking
     object is operating in recursive mode. <function>sd_bus_track_set_recursive()</function> may be used to enable or
-    disable recursive mode. By default a bus peer tracking object operates in non-recursive mode, and
+    disable recursive mode. By default, a bus peer tracking object operates in non-recursive mode, and
     <function>sd_bus_track_get_recursive()</function> for a newly allocated object hence returns a value equal to
     zero. Use <function>sd_bus_track_set_recursive()</function> to enable recursive mode, right after allocation. It
     takes a boolean argument to enable or disable recursive mode. Note that tracking objects for which

man/sd_event_add_child.xml

@@ -155,7 +155,7 @@
     project='man-pages'><refentrytitle>pthread_sigmask</refentrytitle><manvolnum>3</manvolnum></citerefentry>).</para>
 
     <para>If the second parameter of <function>sd_event_add_child()</function> is passed as
-    <constant>NULL</constant> no reference to the event source object is returned. In this case the event
+    <constant>NULL</constant> no reference to the event source object is returned. In this case, the event
     source is considered "floating", and will be destroyed implicitly when the event loop itself is
     destroyed.</para>
 
@@ -202,7 +202,7 @@
 
     <para><function>sd_event_source_get_child_pidfd()</function> retrieves the file descriptor referencing
     the watched process ("pidfd") if this functionality is available. On kernels that support the concept the
-    event loop will make use of pidfds to watch child processes, regardless if the individual event sources
+    event loop will make use of pidfds to watch child processes, regardless of whether the individual event sources
     are allocated via <function>sd_event_add_child()</function> or
     <function>sd_event_add_child_pidfd()</function>. If the latter call was used to allocate the event
     source, this function returns the file descriptor used for allocation. On kernels that do not support the
@@ -212,7 +212,7 @@
 
     <para><function>sd_event_source_get_child_pidfd_own()</function> may be used to query whether the pidfd
     the event source encapsulates shall be closed when the event source is freed. This function returns zero
-    if the pidfd shall be left open, and positive if it shall be closed automatically. By default this
+    if the pidfd shall be left open, and positive if it shall be closed automatically. By default, this
     setting defaults to on if the event source was allocated via <function>sd_event_add_child()</function>
     and off if it was allocated via <function>sd_event_add_child_pidfd()</function>. The
     <function>sd_event_source_set_child_pidfd_own()</function> function may be used to change the setting and
@@ -221,7 +221,7 @@
     <para><function>sd_event_source_get_child_process_own()</function> may be used to query whether the
     process the event source watches shall be killed (with <constant>SIGKILL</constant>) and reaped when the
     event source is freed. This function returns zero if the process shell be left running, and positive if
-    it shall be killed and reaped automatically. By default this setting defaults to off. The
+    it shall be killed and reaped automatically. By default, this setting defaults to off. The
     <function>sd_event_source_set_child_process_own()</function> function may be used to change the setting
     and takes a boolean parameter with the new setting. Note that currently if the calling process is
     terminated abnormally the watched process might survive even thought the event source ceases to

man/sd_event_add_defer.xml

@@ -122,7 +122,7 @@
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
     <para>If the second parameter of these functions is passed as <constant>NULL</constant> no reference to
-    the event source object is returned. In this case the event source is considered "floating", and will be
+    the event source object is returned. In this case, the event source is considered "floating", and will be
     destroyed implicitly when the event loop itself is destroyed.</para>
 
     <para>If the <parameter>handler</parameter> parameter to <function>sd_event_add_defer()</function> or

man/sd_event_add_inotify.xml

@@ -126,7 +126,7 @@
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
     <para>If the second parameter of <function>sd_event_add_inotify()</function> is passed as
-    <constant>NULL</constant> no reference to the event source object is returned. In this case the event
+    <constant>NULL</constant> no reference to the event source object is returned. In this case, the event
     source is considered "floating", and will be destroyed implicitly when the event loop itself is
     destroyed.</para>
 

man/sd_event_add_io.xml

@@ -137,7 +137,7 @@
     read from or written to the file descriptor to reset the mask of events seen.</para>
 
     <para>Setting the I/O event mask to watch for to 0 does not mean
-    that the event source won't be triggered anymore, as
+    that the event source will not be triggered anymore, as
     <constant>EPOLLHUP</constant> and <constant>EPOLLERR</constant>
     may be triggered even with a zero event mask. To temporarily
     disable an I/O event source use
@@ -156,7 +156,7 @@
     <para>If the second parameter of
     <function>sd_event_add_io()</function> is
     <constant>NULL</constant> no reference to the event source object
-    is returned. In this case the event source is considered
+    is returned. In this case, the event source is considered
     "floating", and will be destroyed implicitly when the event loop
     itself is destroyed.</para>
 
@@ -227,7 +227,7 @@
     event source shall take ownership of the file descriptor. Takes a boolean parameter
     <parameter>b</parameter>. When true (nonzero), the file descriptor will be closed automatically when the
     event source is freed or when the file descriptor is replaced by
-    <function>sd_event_source_set_io_fd()</function>. By default the descriptor is not owned by the event
+    <function>sd_event_source_set_io_fd()</function>. By default, the descriptor is not owned by the event
     source, and the application has to do close it on its own if needed.</para>
 
     <para><function>sd_event_source_get_io_fd_own()</function> may be used to query the current setting of the file

man/sd_event_add_memory_pressure.xml

@@ -84,7 +84,7 @@
     with <constant>SD_EVENT_OFF</constant>.</para>
 
     <para>If the second parameter of <function>sd_event_add_memory_pressure()</function> is
-    <constant>NULL</constant> no reference to the event source object is returned. In this case the event
+    <constant>NULL</constant> no reference to the event source object is returned. In this case, the event
     source is considered "floating", and will be destroyed implicitly when the event loop itself is
     destroyed.</para>
 
@@ -138,7 +138,7 @@
 
     <para>This event source typically fires on memory pressure stalls, i.e. when operational latency above a
     configured threshold already has been seen. This should be taken into consideration when discussing
-    whether later latency to re-aquire any released resources is acceptable: it's usually more important to
+    whether later latency to re-aquire any released resources is acceptable: it is usually more important to
     think of the latencies that already happened than those coming up in future.</para>
 
     <para>The <function>sd_event_source_set_memory_pressure_type()</function> and

man/sd_event_add_signal.xml

@@ -107,7 +107,7 @@
     <para>If the second parameter of
     <function>sd_event_add_signal()</function> is
     <constant>NULL</constant> no reference to the event source object
-    is returned. In this case the event source is considered
+    is returned. In this case, the event source is considered
     "floating", and will be destroyed implicitly when the event loop
     itself is destroyed.</para>
 

man/sd_event_add_time.xml

@@ -164,7 +164,7 @@
     <para>If the second parameter of
     <function>sd_event_add_time()</function> is
     <constant>NULL</constant> no reference to the event source object
-    is returned. In this case the event source is considered
+    is returned. In this case, the event source is considered
     "floating", and will be destroyed implicitly when the event loop
     itself is destroyed.</para>
 
@@ -197,7 +197,7 @@
     base the <parameter>usec</parameter> parameter passed to the timer
     callback, or the timestamp returned by
     <function>sd_event_now()</function>. In the former case timer
-    events will be regular, while in the latter case the scheduling
+    events will be regular, while in the latter case, the scheduling
     latency will keep accumulating on the timer.</para>
 
     <para><function>sd_event_source_get_time()</function> retrieves the configured time value of an event

man/sd_event_set_signal_exit.xml

@@ -48,10 +48,10 @@
     <para>If the parameter <parameter>b</parameter> is specified as true, the event loop will terminate on
     <constant>SIGINT</constant> and <constant>SIGTERM</constant>. If specified as false, it will no
     longer. When this functionality is turned off the calling thread's signal mask is restored to match the
-    state before it was turned on, for the two signals. By default the two signals are not handled by the
+    state before it was turned on, for the two signals. By default, the two signals are not handled by the
     event loop, and Linux' default signal handling for them is in effect.</para>
 
-    <para>It's customary for UNIX programs to exit on either of these two signals, hence it's typically a
+    <para>It is customary for UNIX programs to exit on either of these two signals, hence it is typically a
     good idea to enable this functionality for the main event loop of a program.</para>
   </refsect1>
 

man/sd_event_source_set_ratelimit.xml

@@ -74,10 +74,10 @@
     dispatched more often than the specified burst within the specified interval it is placed in a mode
     similar to being disabled with
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-    and the <constant>SD_EVENT_OFF</constant> parameter. However it is disabled only temporarily – once the
+    and the <constant>SD_EVENT_OFF</constant> parameter. However, it is disabled only temporarily – once the
     specified interval is over regular operation resumes. It is again disabled temporarily once the specified rate
     limiting is hit the next time. If either the interval or the burst value are specified as zero, rate
-    limiting is turned off. By default event sources do not have rate limiting enabled. Note that rate
+    limiting is turned off. By default, event sources do not have rate limiting enabled. Note that rate
     limiting and disabling via <function>sd_event_source_set_enabled()</function> are independent of each
     other, and an event source will only effect event loop wake-ups and is dispatched while it both is
     enabled and rate limiting is not in effect.</para>
@@ -111,7 +111,7 @@
     return a negative errno-style error code. <function>sd_event_source_is_ratelimited()</function> returns
     zero if rate limiting is currently not in effect and greater than zero if it is in effect; it returns a
     negative errno-style error code on failure. <function>sd_event_source_leave_ratelimit()</function>
-    returns zero if rate limiting wasn't in effect on the specified event source, and positive if it was and
+    returns zero if rate limiting was not in effect on the specified event source, and positive if it was and
     rate limiting is now turned off again; it returns a negative errno-style error code on failure.</para>
 
     <refsect2>
@@ -151,7 +151,7 @@
           <term><constant>-ENOEXEC</constant></term>
 
           <listitem><para><function>sd_event_source_get_ratelimit()</function> was called on an event source
-          that doesn't have rate limiting configured.</para>
+          that does not have rate limiting configured.</para>
 
           <xi:include href="version-info.xml" xpointer="v248"/></listitem>
         </varlistentry>

man/sd_journal_get_catalog.xml

@@ -85,9 +85,9 @@
     <title>Notes</title>
 
     <para>Function <function>sd_journal_get_catalog()</function> is thread-agnostic and only
-    a single specific thread may operate on a given object during its entire lifetime. It's safe to allocate multiple
-    independent objects and use each from a specific thread in parallel. However, it's not safe to allocate such an
-    object in one thread, and operate or free it from any other, even if locking is used to ensure these threads don't
+    a single specific thread may operate on a given object during its entire lifetime. It is safe to allocate multiple
+    independent objects and use each from a specific thread in parallel. However, it is not safe to allocate such an
+    object in one thread, and operate or free it from any other, even if locking is used to ensure these threads do not
     operate on it at the very same time.</para>
 
     <para>Function <function>sd_journal_get_catalog_for_message_id()</function> is are thread-safe and may be called in

man/sd_journal_get_data.xml

@@ -148,7 +148,7 @@
     code. <function>sd_journal_enumerate_data()</function> and
     <function>sd_journal_enumerate_available_data()</function> return a positive integer if the next field
     has been read, 0 when no more fields remain, or a negative errno-style error code.
-    <function>sd_journal_restart_data()</function> doesn't return anything.
+    <function>sd_journal_restart_data()</function> does not return anything.
     <function>sd_journal_set_data_threshold()</function> and <function>sd_journal_get_threshold()</function>
     return 0 on success or a negative errno-style error code.</para>
 

man/sd_journal_get_fd.xml

@@ -192,7 +192,7 @@ else {
       invocation.</para></listitem>
 
       <listitem><para>If <constant>SD_JOURNAL_APPEND</constant> is returned, new entries have been appended to the end
-      of the journal. In this case it is sufficient to simply continue reading at the previous end location of the
+      of the journal. In this case, it is sufficient to simply continue reading at the previous end location of the
       journal, to read the newly added entries.</para></listitem>
 
       <listitem><para>If <constant>SD_JOURNAL_INVALIDATE</constant>, journal files were added to or removed from the

man/sd_journal_has_runtime_files.xml

@@ -46,11 +46,11 @@
 
     <para><function>sd_journal_has_runtime_files()</function> returns a positive value
     if runtime journal files (present in /run/systemd/journal/) have been found.
-    Otherwise returns 0.</para>
+    Otherwise, returns 0.</para>
 
     <para><function>sd_journal_has_persistent_files()</function> returns a positive value
     if persistent journal files (present in /var/log/journal/) have been found.
-    Otherwise returns 0.</para>
+    Otherwise, returns 0.</para>
   </refsect1>
 
   <refsect1>

man/sd_journal_query_unique.xml

@@ -119,7 +119,7 @@
     code. <function>sd_journal_enumerate_unique()</function> and
     <function>sd_journal_query_available_unique()</function> return a positive integer if the next field data
     has been read, 0 when no more fields remain, or a negative errno-style error code.
-    <function>sd_journal_restart_unique()</function> doesn't return anything.</para>
+    <function>sd_journal_restart_unique()</function> does not return anything.</para>
 
     <refsect2>
       <title>Errors</title>

man/sd_listen_fds.xml

@@ -52,13 +52,13 @@
     (i.e. <constant>SD_LISTEN_FDS_START</constant>), the remaining descriptors follow at 4, 5, 6, …, if
     any.</para>
 
-    <para>The file descriptors passed this way may be closed at will by the processes receiving them: it's up
+    <para>The file descriptors passed this way may be closed at will by the processes receiving them: it is up
     to the processes themselves to close them after use or whether to leave them open until the process exits
     (in which case the kernel closes them automatically). Note that the file descriptors received by daemons
     are duplicates of the file descriptors the service manager originally allocated and bound and of which it
     continuously keeps a copy (except if <varname>Accept=yes</varname> is used). This means any socket option
     changes and other changes made to the sockets will be visible to the service manager too. Most
-    importantly this means it's generally not a good idea to invoke <citerefentry
+    importantly this means it is generally not a good idea to invoke <citerefentry
     project='man-pages'><refentrytitle>shutdown</refentrytitle><manvolnum>2</manvolnum></citerefentry> on
     such sockets, since it will shut down communication on the file descriptor the service manager holds for
     the same socket too. Also note that if a daemon is restarted (and its associated sockets are not) it will

man/sd_notify.xml

@@ -292,7 +292,7 @@
         <term>MAINPID=…</term>
 
         <listitem><para>Change the main process ID (PID) of the service. This is especially useful in the case
-        where the real main process isn't directly forked off by the service manager.
+        where the real main process is not directly forked off by the service manager.
         Example: <literal>MAINPID=4711</literal>.</para>
 
         <xi:include href="version-info.xml" xpointer="v233"/></listitem>
@@ -362,7 +362,7 @@
 
         <listitem><para>Tells the service manager to extend the startup, runtime or shutdown service timeout
         corresponding the current state. The value specified is a time in microseconds during which the
-        service must send a new message. A service timeout will occur if the message isn't received, but only
+        service must send a new message. A service timeout will occur if the message is not received, but only
         if the runtime of the current state is beyond the original maximum times of
         <varname>TimeoutStartSec=</varname>, <varname>RuntimeMaxSec=</varname>, and
         <varname>TimeoutStopSec=</varname>.  See

man/standard-conf.xml

@@ -61,7 +61,7 @@
     <filename>/usr/lib/systemd/</filename>.
     The vendor version of the file contains commented out entries showing the defaults as a guide to the
     administrator. Local overrides can also be created by creating drop-ins, as described below. The main
-    configuration file can also be edited for this purpose (or a copy in <filename>/etc/</filename> if it's
+    configuration file can also be edited for this purpose (or a copy in <filename>/etc/</filename> if it is
     shipped under <filename>/usr/</filename>), however using drop-ins for local configuration is recommended
     over modifications to the main configuration file.</para>
 

man/standard-options.xml

@@ -110,7 +110,7 @@
     <listitem><para>Takes an image policy string as argument, as per
     <citerefentry><refentrytitle>systemd.image-policy</refentrytitle><manvolnum>7</manvolnum></citerefentry>. The
     policy is enforced when operating on the disk image specified via <option>--image=</option>, see
-    above. If not specified defaults to the <literal>*</literal> policy, i.e. all recognized file systems
+    above. If not specified, defaults to the <literal>*</literal> policy, i.e. all recognized file systems
     in the image are used.</para></listitem>
   </varlistentry>
 

man/sysctl.d.xml

@@ -174,7 +174,7 @@ net.ipv4.conf.hub0.rp_filter = 1
       <filename>net.ipv4.conf.default.rp_filter</filename> first, so any interfaces which are added
       <emphasis>later</emphasis> will get this value (this also covers any interfaces detected while we're
       running). The glob matches any interfaces which were detected <emphasis>earlier</emphasis>. The glob
-      will also match <filename>net.ipv4.conf.all.rp_filter</filename>, which we don't want to set at all, so
+      will also match <filename>net.ipv4.conf.all.rp_filter</filename>, which we do not want to set at all, so
       it is explicitly excluded. And "hub0" is excluded from the glob because it has an explicit setting.
       </para>
     </example>

man/systemctl.xml

@@ -59,14 +59,14 @@
           <listitem>
             <para>List units that <command>systemd</command> currently has in memory. This includes units that are
             either referenced directly or through a dependency, units that are pinned by applications programmatically,
-            or units that were active in the past and have failed. By default only units which are active, have pending
+            or units that were active in the past and have failed. By default, only units which are active, have pending
             jobs, or have failed are shown; this can be changed with option <option>--all</option>. If one or more
             <replaceable>PATTERN</replaceable>s are specified, only units matching one of them are shown. The units
             that are shown are additionally filtered by <option>--type=</option> and <option>--state=</option> if those
             options are specified.</para>
 
             <para>Note that this command does not show unit templates, but only instances of unit
-            templates. Units templates that aren't instantiated are not runnable, and will thus never show up
+            templates. Units templates that are not instantiated are not runnable, and will thus never show up
             in the output of this command. Specifically this means that <filename>foo@.service</filename>
             will never be shown in this list — unless instantiated, e.g. as
             <filename>foo@bar.service</filename>. Use <command>list-unit-files</command> (see below) for
@@ -357,7 +357,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             on disk, which might not match the system manager's
             understanding of these units if any unit files were
             updated on disk and the <command>daemon-reload</command>
-            command wasn't issued since.</para>
+            command was not issued since.</para>
 
             <xi:include href="version-info.xml" xpointer="v209"/>
           </listitem>
@@ -391,7 +391,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             <filename>default.target</filename> is implied.</para>
 
             <para>The units that are shown are additionally filtered by <option>--type=</option> and
-            <option>--state=</option> if those options are specified. Note that we won't be able to
+            <option>--state=</option> if those options are specified. Note that we will not be able to
             use a tree structure in this case, so <option>--plain</option> is implied.</para>
 
             <para>By default, only target units are recursively
@@ -405,7 +405,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
 
             <para>Note that this command only lists units currently loaded into memory by the service manager. In
             particular, this command is not suitable to get a comprehensive list at all reverse dependencies on a
-            specific unit, as it won't list the dependencies declared by units currently not loaded.</para>
+            specific unit, as it will not list the dependencies declared by units currently not loaded.</para>
 
             <xi:include href="version-info.xml" xpointer="v198"/>
           </listitem>
@@ -496,8 +496,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             <para>Stop and then start one or more units specified on the
             command line if the units are running. This does nothing
             if units are not running.</para>
-            <!-- Note that we don't document condrestart here, as that is just compatibility support, and we generally
-                 don't document that. -->
+            <!-- Note that we do not document condrestart here, as that is just compatibility support, and we generally
+                 do not document that. -->
           </listitem>
         </varlistentry>
         <varlistentry>
@@ -514,8 +514,8 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
           <listitem>
             <para>Reload one or more units if they support it. If not, stop and then start them instead. This does
             nothing if the units are not running.</para>
-            <!-- Note that we don't document force-reload here, as that is just compatibility support, and we generally
-                 don't document that. -->
+            <!-- Note that we do not document force-reload here, as that is just compatibility support, and we generally
+                 do not document that. -->
 
             <xi:include href="version-info.xml" xpointer="v229"/>
           </listitem>
@@ -629,7 +629,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             command line using cgroup freezer</para>
 
             <para>Freezing the unit will cause all processes contained within the cgroup corresponding to the unit
-            to be suspended. Being suspended means that unit's processes won't be scheduled to run on CPU until thawed.
+            to be suspended. Being suspended means that unit's processes will not be scheduled to run on CPU until thawed.
             Note that this command is supported only on systems that use unified cgroup hierarchy. Unit is automatically
             thawed just before we execute a job against the unit, e.g. before the unit is stopped.</para>
 
@@ -1108,12 +1108,12 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
                   </row>
                   <row>
                     <entry><literal>bad</literal></entry>
-                    <entry>The unit file is invalid or another error occurred. Note that <command>is-enabled</command> will not actually return this state, but print an error message instead. However the unit file listing printed by <command>list-unit-files</command> might show it.</entry>
+                    <entry>The unit file is invalid or another error occurred. Note that <command>is-enabled</command> will not actually return this state, but print an error message instead. However, the unit file listing printed by <command>list-unit-files</command> might show it.</entry>
                     <entry>&gt; 0</entry>
                   </row>
                   <row>
                     <entry><literal>not-found</literal></entry>
-                    <entry>The unit file doesn't exist.</entry>
+                    <entry>The unit file does not exist.</entry>
                     <entry>4</entry>
                   </row>
                 </tbody>
@@ -1142,7 +1142,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             specified). If a matching unit file already exists under these directories this operation will
             hence fail. This means that the operation is primarily useful to mask units shipped by the vendor
             (as those are shipped in <filename>/usr/lib/systemd/system/</filename> and not the aforementioned
-            two directories), but typically doesn't work for units created locally (as those are typically
+            two directories), but typically does not work for units created locally (as those are typically
             placed precisely in the two aforementioned directories). Similar restrictions apply for
             <option>--user</option> mode, in which case the directories are below the user's home directory
             however.</para>
@@ -1740,7 +1740,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
 
           <listitem>
             <para>Shut down and reboot the system via <command>kexec</command>. This command will load a
-            kexec kernel if one wasn't loaded yet or fail. A kernel may be loaded earlier by a separate step,
+            kexec kernel if one was not loaded yet or fail. A kernel may be loaded earlier by a separate step,
             this is particularly useful if a custom initrd or additional kernel command line options are
             desired. The <option>--force</option> can be used to continue without a kexec kernel, i.e. to
             perform a normal reboot. The final reboot step is equivalent to
@@ -1939,7 +1939,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
       units currently in memory, and patterns which do not match anything
       are silently skipped. For example:
       <programlisting># systemctl stop "sshd@*.service"</programlisting>
-      will stop all <filename>sshd@.service</filename> instances. Note that alias names of units, and units that aren't
+      will stop all <filename>sshd@.service</filename> instances. Note that alias names of units, and units that are not
       in memory are not considered for glob expansion.
       </para>
 
@@ -2350,7 +2350,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
         <term><option>--no-warn</option></term>
 
         <listitem>
-          <para>Don't generate the warnings shown by default in the following cases:
+          <para>Do not generate the warnings shown by default in the following cases:
           <itemizedlist>
             <listitem>
               <para>when <command>systemctl</command> is invoked without procfs mounted on
@@ -2358,7 +2358,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             </listitem>
             <listitem>
               <para>when using <command>enable</command> or <command>disable</command> on units without
-              install information (i.e. don't have or have an empty [Install] section),</para>
+              install information (i.e. do not have or have an empty [Install] section),</para>
             </listitem>
             <listitem>
               <para>when using <command>disable</command> combined with <option>--user</option> on units

man/systemd-ac-power.xml

@@ -31,7 +31,7 @@
     <title>Description</title>
 
     <para><command>systemd-ac-power</command> may be used to check whether the system
-    is running on AC power or not. By default it will simply return success (if we
+    is running on AC power or not. By default, it will simply return success (if we
     can detect that we are running on AC power) or failure, with no output.
     This can be useful for example to debug <varname>ConditionACPower=</varname> (see
     <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>).</para>
@@ -55,7 +55,7 @@
       <varlistentry>
         <term><option>--low</option></term>
 
-        <listitem><para>Instead of showing AC power state, show low battery state. In this case will return
+        <listitem><para>Instead of showing AC power state, show low battery state. In this case, will return
         zero if all batteries are currently discharging and below 5% of maximum charge. Returns non-zero
         otherwise.</para>
 

man/systemd-analyze.xml

@@ -255,7 +255,7 @@ multi-user.target reached after 47.820s in userspace
       <para>This command prints a list of all running units, ordered by the time they took to initialize.
       This information may be used to optimize boot-up times. Note that the output might be misleading as the
       initialization of one service might be slow simply because it waits for the initialization of another
-      service to complete.  Also note: <command>systemd-analyze blame</command> doesn't display results for
+      service to complete.  Also note: <command>systemd-analyze blame</command> does not display results for
       services with <varname>Type=simple</varname>, because systemd considers such services to be started
       immediately, hence no measurement of the initialization delays can be done. Also note that this command
       only shows the time units took for starting up, it does not show how long unit jobs spent in the
@@ -291,7 +291,7 @@ multi-user.target reached after 47.820s in userspace
       <command>blame</command> command, this only takes into account the time units spent in
       <literal>activating</literal> state, and hence does not cover units that never went through an
       <literal>activating</literal> state (such as device units that transition directly from
-      <literal>inactive</literal> to <literal>active</literal>). Moreover it does not show information on
+      <literal>inactive</literal> to <literal>active</literal>). Moreover, it does not show information on
       jobs (and in particular not jobs that timed out).</para>
 
       <example>
@@ -371,8 +371,8 @@ $ eog bootup.svg&amp;
 
       <para>Note that this plot is based on the most recent per-unit timing data of loaded units. This means
       that if a unit gets started, then stopped and then started again the information shown will cover the
-      most recent start cycle, not the first one. Thus it's recommended to consult this information only
-      shortly after boot, so that this distinction doesn't matter. Moreover, units that are not referenced by
+      most recent start cycle, not the first one. Thus it is recommended to consult this information only
+      shortly after boot, so that this distinction does not matter. Moreover, units that are not referenced by
       any other unit through a dependency might be unloaded by the service manager once they terminate (and
       did not fail). Such units will not show up in the plot.</para>
     </refsect2>
@@ -688,7 +688,7 @@ NAutoVTs=8
       <para>This command has two distinct modes of operation, depending on whether the operator
       <replaceable>OP</replaceable> is specified.</para>
 
-      <para>In the first mode — when <replaceable>OP</replaceable> is not specified — it will compare the two
+      <para>In the first mode — when <replaceable>OP</replaceable> is not specified —, it will compare the two
       version strings and print either <literal><replaceable>VERSION1</replaceable> &lt;
       <replaceable>VERSION2</replaceable></literal>, or <literal><replaceable>VERSION1</replaceable> ==
       <replaceable>VERSION2</replaceable></literal>, or <literal><replaceable>VERSION1</replaceable> &gt;
@@ -964,7 +964,7 @@ default         ignore      -         -</programlisting>
       <para>Reports whether the system is equipped with a usable TPM2 device. If a TPM2 device has been
       discovered, is supported, and is being used by firmware, by the OS kernel drivers and by userspace
       (i.e. systemd) this prints <literal>yes</literal> and exits with exit status zero. If no such device is
-      discovered/supported/used, prints <literal>no</literal>. Otherwise prints
+      discovered/supported/used, prints <literal>no</literal>. Otherwise, prints
       <literal>partial</literal>. In either of these two cases exits with non-zero exit status. It also shows
       five lines indicating separately whether firmware, drivers, the system, the kernel and libraries
       discovered/support/use TPM2. Currently, required libraries are <filename>libtss2-esys.so.0</filename>,
@@ -1630,7 +1630,7 @@ LEGEND: M → sys_vendor (LENOVO) ┄ F → product_family (ThinkPad X1 Carbon G
         <term><option>--base-time=<replaceable>TIMESTAMP</replaceable></option></term>
 
         <listitem><para>When used with the <command>calendar</command> command, show next iterations relative
-        to the specified point in time. If not specified defaults to the current time.</para>
+        to the specified point in time. If not specified, defaults to the current time.</para>
 
         <xi:include href="version-info.xml" xpointer="v244"/></listitem>
       </varlistentry>
@@ -1730,7 +1730,7 @@ LEGEND: M → sys_vendor (LENOVO) ┄ F → product_family (ThinkPad X1 Carbon G
     <constant>0</constant> or <constant>1</constant> if the condition is respectively true or false.</para>
 
     <para>In case of the <command>has-tpm2</command> command returns 0 if a TPM2 device is discovered,
-    supported and used by firmware, driver, and userspace (i.e. systemd). Otherwise returns the OR
+    supported and used by firmware, driver, and userspace (i.e. systemd). Otherwise, returns the OR
     combination of the value 1 (in case firmware support is missing), 2 (in case driver support is missing)
     and 4 (in case userspace support is missing). If no TPM2 support is available at all, value 7 is hence
     returned.</para>

man/systemd-bless-boot.service.xml

@@ -41,7 +41,7 @@
     OS. It contains a file system path (relative to the EFI system partition) of the <ulink
     url="https://uapi-group.org/specifications/specs/boot_loader_specification">Boot Loader Specification</ulink> compliant boot loader entry
     file or unified kernel image file that was used to boot up the
-    system. <command>systemd-bless-boot.service</command> removes the two 'tries done' and 'tries left' numeric boot
+    system. <command>systemd-bless-boot.service</command> removes the two "tries done" and "tries left" numeric boot
     counters from the filename, which indicates to future invocations of the boot loader that the entry has completed
     booting successfully at least once. (This service will hence rename the boot loader entry file or unified kernel
     image file on the first successful boot.)</para>
@@ -84,8 +84,8 @@
       <varlistentry>
         <term><option>bad</option></term>
 
-        <listitem><para>When called the 'tries left' counter in the boot loader entry file name or unified kernel image
-        file name is set to zero, marking the boot loader entry or kernel image as "bad", so that the boot loader won't
+        <listitem><para>When called the "tries left" counter in the boot loader entry file name or unified kernel image
+        file name is set to zero, marking the boot loader entry or kernel image as "bad", so that the boot loader will not
         consider it anymore on future boots (at least as long as there are other entries available that are not marked
         "bad" yet). This command is normally not executed, but can be used to instantly put an end to the boot counting
         logic if a problem is detected and persistently mark the boot entry as bad.</para>

man/systemd-boot-random-seed.service.xml

@@ -43,12 +43,12 @@
     the random seed stored in the ESP is refreshed on <emphasis>every</emphasis> reboot ensuring that
     multiple subsequent boots will boot with different seeds. On the other hand, the system token is
     generated randomly <emphasis>once</emphasis>, and then persistently stored in the system's EFI variable
-    storage, ensuring the same disk image won't result in the same series of boot loader seed values if used
+    storage, ensuring the same disk image will not result in the same series of boot loader seed values if used
     on multiple systems in parallel.</para>
 
     <para>The <filename>systemd-boot-random-seed.service</filename> unit invokes the <command>bootctl
     random-seed</command> command, which updates the random seed in the ESP, and initializes the system
-    token if it's not initialized yet. The service is conditionalized so that it is run only when a boot
+    token if it is not initialized yet. The service is conditionalized so that it is run only when a boot
     loader is used that implements the <ulink url="https://systemd.io/BOOT_LOADER_INTERFACE">Boot Loader
     Interface</ulink>.</para> <para>For further details see
     <citerefentry><refentrytitle>bootctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, regarding

man/systemd-boot.xml

@@ -602,7 +602,7 @@
 
     <orderedlist>
       <listitem><para>If the 'tries left' counter of an entry is greater than zero the entry is considered to be in
-      'indeterminate' state. This means the entry has not completed booting successfully yet, but also hasn't been
+      'indeterminate' state. This means the entry has not completed booting successfully yet, but also has not been
       determined not to work.</para></listitem>
 
       <listitem><para>If the 'tries left' counter of an entry is zero it is considered to be in 'bad' state. This means

man/systemd-bsod.service.xml

@@ -52,7 +52,7 @@
         <term><option>--continuous</option></term>
 
         <listitem><para>When specified, <command>systemd-bsod</command> waits continuously for changes in the
-        journal if it doesn't find any emergency messages on the initial attempt.</para>
+        journal if it does not find any emergency messages on the initial attempt.</para>
 
          <xi:include href="version-info.xml" xpointer="v255"/></listitem>
       </varlistentry>
@@ -60,7 +60,7 @@
       <varlistentry>
         <term><option>--tty=<replaceable></replaceable></option></term>
 
-        <listitem><para>Specify the TTY to output to. By default <command>systemd-bsod</command> will
+        <listitem><para>Specify the TTY to output to. By default, <command>systemd-bsod</command> will
         automatically find a free VT to display the message on. If this option is specified a TTY may be
         selected explicitly. Use <option>--tty=/dev/tty</option> to direct output to the terminal the command
         is invoked on.</para>

man/systemd-creds.xml

@@ -88,7 +88,7 @@
 
         <listitem><para>Generates a host encryption key for credentials, if one has not been generated
         already. This ensures the <filename>/var/lib/systemd/credential.secret</filename> file is initialized
-        with a random secret key if it doesn't exist yet. This secret key is used when encrypting/decrypting
+        with a random secret key if it does not exist yet. This secret key is used when encrypting/decrypting
         credentials with <command>encrypt</command> or <command>decrypt</command>, and is only accessible to
         the root user. Note that there's typically no need to invoke this command explicitly as it is
         implicitly called when <command>encrypt</command> is invoked, and credential host key encryption
@@ -247,7 +247,7 @@
         <term><option>--newline=</option></term>
 
         <listitem><para>When specified with <command>cat</command> or <command>decrypt</command> controls
-        whether to add a trailing newline character to the end of the output if it doesn't end in one,
+        whether to add a trailing newline character to the end of the output if it does not end in one,
         anyway. Takes one of <literal>auto</literal>, <literal>yes</literal> or <literal>no</literal>. The
         default mode of <literal>auto</literal> will suffix the output with a single newline character only
         when writing credential data to a TTY.</para>
@@ -271,20 +271,20 @@
         <term><option>--name=<replaceable>name</replaceable></option></term>
 
         <listitem><para>When specified with the <command>encrypt</command> command controls the credential
-        name to embed in the encrypted credential data. If not specified the name is chosen automatically
+        name to embed in the encrypted credential data. If not specified, the name is chosen automatically
         from the filename component of the specified output path. If specified as empty string no
         credential name is embedded in the encrypted credential, and no verification of credential name is
         done when the credential is decrypted.</para>
 
         <para>When specified with the <command>decrypt</command> command control the credential name to
-        validate the credential name embedded in the encrypted credential with. If not specified the name is
+        validate the credential name embedded in the encrypted credential with. If not specified, the name is
         chosen automatically from the filename component of the specified input path. If no credential name
         is embedded in the encrypted credential file (i.e. the <option>--name=</option> with an empty string
         was used when encrypted) the specified name has no effect as no credential name validation is
         done.</para>
 
         <para>Embedding the credential name in the encrypted credential is done in order to protect against
-        reuse of credentials for purposes they weren't originally intended for, under the assumption the
+        reuse of credentials for purposes they were not originally intended for, under the assumption the
         credential name is chosen carefully to encode its intended purpose.</para>
 
         <xi:include href="version-info.xml" xpointer="v250"/></listitem>
@@ -300,7 +300,7 @@
 
         <para>When specified with the <command>decrypt</command> command controls the timestamp to use to
         validate the "not-after" timestamp that was configured with <option>--not-after=</option> during
-        encryption. If not specified defaults to the current system time.</para>
+        encryption. If not specified, defaults to the current system time.</para>
 
         <xi:include href="version-info.xml" xpointer="v250"/></listitem>
       </varlistentry>
@@ -311,7 +311,7 @@
         <listitem><para>When specified with the <command>encrypt</command> command controls the time when the
         credential shall not be used anymore. This embeds the specified timestamp in the encrypted
         credential. During decryption the timestamp is checked against the current system clock, and if the
-        timestamp is in the past the decryption will fail. By default no such timestamp is set. Takes a
+        timestamp is in the past the decryption will fail. By default, no such timestamp is set. Takes a
         timestamp specification in the format described in
         <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
 
@@ -392,7 +392,7 @@
         <filename>/etc/systemd/</filename>, <filename>/run/systemd/</filename>,
         <filename>/usr/lib/systemd/</filename> (searched in this order), it is automatically used. The
         <option>--tpm2-public-key-pcrs=</option> option takes a list of TPM2 PCR indexes to bind to (same
-        syntax as <option>--tpm2-pcrs=</option> described above). If not specified defaults to 11 (i.e. this
+        syntax as <option>--tpm2-pcrs=</option> described above). If not specified, defaults to 11 (i.e. this
         binds the policy to any unified kernel image for which a PCR signature can be provided).</para>
 
         <para>Note the difference between <option>--tpm2-pcrs=</option> and

man/systemd-cryptenroll.xml

@@ -229,7 +229,7 @@
     <para>Note that currently when enrolling a new key of one of the five supported types listed above, it is
     required to first provide a passphrase, a recovery key, a FIDO2 token, or a TPM2 key. It's currently not
     supported to unlock a device with a PKCS#11 key in order to enroll a new PKCS#11 key. Thus, if in future
-    key roll-over is desired it's generally recommended to ensure a passphrase, a recovery key, a FIDO2
+    key roll-over is desired it is generally recommended to ensure a passphrase, a recovery key, a FIDO2
     token, or a TPM2 key is always enrolled.</para>
 
     <para>Also note that support for enrolling multiple FIDO2 tokens is currently limited. When multiple FIDO2
@@ -398,7 +398,7 @@
         is unsupported if <option>--unlock-fido2-device=</option> option is also specified. The special value
         <literal>list</literal> may be used to enumerate all suitable FIDO2 tokens currently plugged in. Note
         that many hardware security tokens that implement FIDO2 also implement the older PKCS#11
-        standard. Typically FIDO2 is preferable, given it's simpler to use and more modern.</para>
+        standard. Typically FIDO2 is preferable, given it is simpler to use and more modern.</para>
 
         <para>In order to unlock a LUKS2 volume with an enrolled FIDO2 security token, specify the
         <option>fido2-device=</option> option in the respective <filename>/etc/crypttab</filename> line:</para>
@@ -628,7 +628,7 @@
         <filename>/etc/systemd/</filename>, <filename>/run/systemd/</filename>,
         <filename>/usr/lib/systemd/</filename> (searched in this order), it is automatically used. The
         <option>--tpm2-public-key-pcrs=</option> option takes a list of TPM2 PCR indexes to bind to (same
-        syntax as <option>--tpm2-pcrs=</option> described above). If not specified defaults to 11 (i.e. this
+        syntax as <option>--tpm2-pcrs=</option> described above). If not specified, defaults to 11 (i.e. this
         binds the policy to any unified kernel image for which a PCR signature can be provided).</para>
 
         <para>Note the difference between <option>--tpm2-pcrs=</option> and

man/systemd-dissect.xml

@@ -152,7 +152,7 @@
         unmounted.</para>
 
         <para>The OS image may either be specified as path to an OS image stored in a regular file or may
-        refer to block device node (in the latter case the block device must be the "whole" device, i.e. not
+        refer to block device node (in the latter case, the block device must be the "whole" device, i.e. not
         a partition device). (The other supported commands described here support this, too.)</para>
 
         <para>All mounted file systems are checked with the appropriate <citerefentry
@@ -215,7 +215,7 @@
 
         <listitem><para>Detach the specified disk image from a loopback block device. This undoes the effect
         of <option>--attach</option> above. This expects either a path to a loopback block device as an
-        argument, or the path to the backing image file. In the latter case it will automatically determine
+        argument, or the path to the backing image file. In the latter case, it will automatically determine
         the right device to detach.</para>
 
         <xi:include href="version-info.xml" xpointer="v254"/></listitem>
@@ -277,9 +277,9 @@
         the current working directory, or an absolute path, both outside of the image). If the destination
         path is omitted or specified as dash (<literal>-</literal>), the specified file is written to
         standard output. If the source path in the image file system refers to a regular file it is copied to
-        the destination path. In this case access mode, extended attributes and timestamps are copied as
+        the destination path. In this case, access mode, extended attributes and timestamps are copied as
         well, but file ownership is not. If the source path in the image refers to a directory, it is copied
-        to the destination path, recursively with all containing files and directories. In this case the file
+        to the destination path, recursively with all containing files and directories. In this case, the file
         ownership is copied too.</para>
 
         <xi:include href="version-info.xml" xpointer="v247"/></listitem>
@@ -295,9 +295,9 @@
         image) and a destination path (relative to the image's root directory). If the source path is omitted
         or specified as dash (<literal>-</literal>), the data to write is read from standard input. If the
         source path in the host file system refers to a regular file, it is copied to the destination path.
-        In this case access mode, extended attributes and timestamps are copied as well, but file ownership
+        In this case, access mode, extended attributes and timestamps are copied as well, but file ownership
         is not. If the source path in the host file system refers to a directory it is copied to the
-        destination path, recursively with all containing files and directories. In this case the file
+        destination path, recursively with all containing files and directories. In this case, the file
         ownership is copied too.</para>
 
         <para>As with <option>--mount</option> file system checks are implicitly run before the copy
@@ -344,7 +344,7 @@
         dissection policy into account. Since this operation does not mount file systems, this command –
         unlike all other commands implemented by this tool – requires no privileges other than the ability to
         access the specified file. Prints "OK" and returns zero if the image appears to be in order and
-        matches the specified image dissection policy. Otherwise prints an error message and returns
+        matches the specified image dissection policy. Otherwise, prints an error message and returns
         non-zero.</para>
 
         <xi:include href="version-info.xml" xpointer="v254"/></listitem>
@@ -366,7 +366,7 @@
         <term><option>--read-only</option></term>
         <term><option>-r</option></term>
 
-        <listitem><para>Operate in read-only mode. By default <option>--mount</option> will establish
+        <listitem><para>Operate in read-only mode. By default, <option>--mount</option> will establish
         writable mount points. If this option is specified they are established in read-only mode
         instead.</para>
 
@@ -376,7 +376,7 @@
       <varlistentry>
         <term><option>--fsck=no</option></term>
 
-        <listitem><para>Turn off automatic file system checking. By default when an image is accessed for
+        <listitem><para>Turn off automatic file system checking. By default, when an image is accessed for
         writing (by <option>--mount</option> or <option>--copy-to</option>) the file systems contained in the
         OS image are automatically checked using the appropriate <citerefentry
         project='man-pages'><refentrytitle>fsck</refentrytitle><manvolnum>8</manvolnum></citerefentry>
@@ -390,7 +390,7 @@
         <term><option>--growfs=no</option></term>
 
         <listitem><para>Turn off automatic growing of accessed file systems to their partition size, if
-        marked for that in the GPT partition table. By default when an image is accessed for writing (by
+        marked for that in the GPT partition table. By default, when an image is accessed for writing (by
         <option>--mount</option> or <option>--copy-to</option>) the file systems contained in the OS image
         are automatically grown to their partition sizes, if bit 59 in the GPT partition flags is set for
         partition types that are defined by the <ulink

man/systemd-firstboot.xml

@@ -304,7 +304,7 @@
         <term><option>--force</option></term>
 
         <listitem><para>Write configuration even if the relevant files already exist. Without this option,
-        <command>systemd-firstboot</command> doesn't modify or replace existing files. Note that when
+        <command>systemd-firstboot</command> does not modify or replace existing files. Note that when
         configuring the root account, even with this option, <command>systemd-firstboot</command> only
         modifies the entry of the <literal>root</literal> user, leaving other entries in
         <filename>/etc/passwd</filename> and <filename>/etc/shadow</filename> intact.</para>
@@ -337,7 +337,7 @@
       <varlistentry>
         <term><option>--welcome=</option></term>
 
-        <listitem><para>Takes a boolean argument. By default when prompting the user for configuration
+        <listitem><para>Takes a boolean argument. By default, when prompting the user for configuration
         options a brief welcome text is shown before the first question is asked. Pass false to this option
         to turn off the welcome text.</para>
 
@@ -445,7 +445,7 @@
         <term><varname>systemd.firstboot=</varname></term>
 
         <listitem><para>Takes a boolean argument, defaults to on. If off, <filename>systemd-firstboot.service</filename>
-        won't interactively query the user for basic settings at first boot, even if those settings are not
+        will not interactively query the user for basic settings at first boot, even if those settings are not
         initialized yet.</para>
 
         <xi:include href="version-info.xml" xpointer="v233"/></listitem>

man/systemd-import-generator.xml

@@ -130,7 +130,7 @@
         completing the download successfully, or unsuccessfully. See
         <varname>SuccessAction=</varname>/<varname>FailureAction=</varname> on
         <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
-        details about the available actions. If not specified no action is taken, and the system will
+        details about the available actions. If not specified, no action is taken, and the system will
         continue to boot normally.</para>
 
         <xi:include href="version-info.xml" xpointer="v257"/></listitem>

man/systemd-journal-remote.service.xml

@@ -49,7 +49,7 @@
     <para><filename>systemd-journal-remote.service</filename> is a system service that uses
     <command>systemd-journal-remote</command> to listen for connections.
     <filename>systemd-journal-remote.socket</filename> configures the network address that
-    <filename>systemd-journal-remote.service</filename> listens on. By default this is port 19532.
+    <filename>systemd-journal-remote.service</filename> listens on. By default, this is port 19532.
     What connections are accepted and how the received data is stored can be configured through the
     <citerefentry><refentrytitle>journal-remote.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
     configuration file.</para>

man/systemd-journald.service.xml

@@ -77,7 +77,7 @@
     necessary. Individual fields making up a log record stored in the journal may be up to 2⁶⁴-1 bytes in size.</para>
 
     <para>The journal service stores log data either persistently below <filename>/var/log/journal</filename> or in a
-    volatile way below <filename>/run/log/journal/</filename> (in the latter case it is lost at reboot). By default, log
+    volatile way below <filename>/run/log/journal/</filename> (in the latter case, it is lost at reboot). By default, log
     data is stored persistently if <filename>/var/log/journal/</filename> exists during boot, with an implicit fallback
     to volatile storage otherwise. Use <varname>Storage=</varname> in
     <citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> to configure
@@ -112,7 +112,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
 
     <para>If <filename>systemd-journald.service</filename> is stopped, the stream connections associated with all
     services are terminated. Further writes to those streams by the service will result in <constant>EPIPE</constant>
-    errors. In order to react gracefully in this case it is recommended that programs logging to standard output/error
+    errors. In order to react gracefully in this case, it is recommended that programs logging to standard output/error
     ignore such errors. If the <constant>SIGPIPE</constant> UNIX signal handler is not blocked or turned off, such
     write attempts will also result in such process signals being generated, see
     <citerefentry project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
@@ -152,7 +152,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
     consisting of one or more services from the rest of the system and a mechanism for improving
     performance. Multiple journal namespaces may exist simultaneously, each defining its own, independent log
     stream managed by its own instance of <command>systemd-journald</command>. Namespaces are independent of
-    each other, both in the data store and in the IPC interface. By default only a single 'default' namespace
+    each other, both in the data store and in the IPC interface. By default, only a single "default namespace
     exists, managed by <filename>systemd-journald.service</filename> (and its associated socket
     units). Additional namespaces are created by starting an instance of the
     <filename>systemd-journald@.service</filename> service template. The instance name is the namespace
@@ -169,7 +169,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
     the native logging protocol of the journal and via stdout/stderr; the logging from all three transports
     is associated with the namespace.</para>
 
-    <para>By default only the default namespace will collect kernel and audit log messages.</para>
+    <para>By default, only the default namespace will collect kernel and audit log messages.</para>
 
     <para>The <command>systemd-journald</command> instance of the default namespace is configured through
     <filename>/etc/systemd/journald.conf</filename> (see below), while the other instances are configured

man/systemd-measure.xml

@@ -46,7 +46,7 @@
     The result may optionally be signed cryptographically, to allow TPM2 policies that can only be unlocked
     if a certain set of kernels is booted, for which such a PCR signature can be provided.</para>
 
-    <para>It usually doesn't make sense to call this tool directly when constructing a UKI. Instead,
+    <para>It usually does not make sense to call this tool directly when constructing a UKI. Instead,
     <citerefentry><refentrytitle>ukify</refentrytitle><manvolnum>1</manvolnum></citerefentry> should be used;
     it will invoke <command>systemd-measure</command> and take care of embedding the resulting measurements
     into the UKI.</para>
@@ -178,7 +178,7 @@
         same PEM key should be supplied in both cases.</para>
 
         <para>If the <option>--public-key=</option> is not specified but <option>--private-key=</option> is
-        specified the public key is automatically derived from the private key.</para>
+        specified, the public key is automatically derived from the private key.</para>
 
         <para><option>--certificate=</option> can be used to specify an X.509 certificate as an alternative
         to <option>--public-key=</option> since v256.</para>
@@ -234,7 +234,7 @@
         <literal>enter-initrd:leave-initrd:sysinit:ready</literal>, i.e. calculates expected PCR values for
         the boot phase in the initrd, during early boot, during later boot, and during system runtime, but
         excluding the phases before the initrd or when shutting down. This setting is honoured both by
-        <command>calculate</command> and <command>sign</command>. When used with the latter it's particularly
+        <command>calculate</command> and <command>sign</command>. When used with the latter it is particularly
         useful for generating PCR signatures that can only be used for unlocking resources during specific
         parts of the boot process.</para>
 

man/systemd-mount.xml

@@ -77,7 +77,7 @@
     <para>If two arguments are specified, the first indicates the mount source (the
     <replaceable>WHAT</replaceable>) and the second indicates the path to mount it on (the
     <replaceable>WHERE</replaceable>). In this mode no probing of the source is attempted, and a backing
-    device node doesn't have to exist. However, if this mode is combined with <option>--discover</option>,
+    device node does not have to exist. However, if this mode is combined with <option>--discover</option>,
     device node probing for additional metadata is enabled, and – much like in the single-argument case
     discussed above – the specified device has to exist at the time of invocation of the command.</para>
 
@@ -138,7 +138,7 @@
         <listitem><para>Enable probing of the mount source. This switch is implied if a single argument is specified on
         the command line. If passed, additional metadata is read from the device to enhance the unit to create. For
         example, a descriptive string for the transient units is generated from the file system label and device
-        model. Moreover if a removable block device (e.g. USB stick) is detected an automount unit instead of a regular
+        model. Moreover, if a removable block device (e.g. USB stick) is detected an automount unit instead of a regular
         mount unit is created, with a short idle timeout, in order to ensure the file-system is placed in a clean
         state quickly after each access.</para>
 
@@ -218,7 +218,7 @@
         accessed. In automount mode the <option>--timeout-idle-sec=</option> switch (see below) may be used to ensure
         the mount point is unmounted automatically after the last access and an idle period passed.</para>
 
-        <para>If this switch is not specified it defaults to false. If not specified and <option>--discover</option> is
+        <para>If this switch is not specified, it defaults to false. If not specified and <option>--discover</option> is
         used (or only a single argument passed, which implies <option>--discover</option>, see above), and the file
         system block device is detected to be removable, it is set to true, in order to increase the chance that the
         file system is in a fully clean state if the device is unplugged abruptly.</para>
@@ -238,7 +238,7 @@
         <term><option>--timeout-idle-sec=</option></term>
 
         <listitem><para>Takes a time value that controls the idle timeout in automount mode. If set to
-        <literal>infinity</literal> (the default) no automatic unmounts are done. Otherwise the file system backing the
+        <literal>infinity</literal> (the default) no automatic unmounts are done. Otherwise, the file system backing the
         automount point is detached after the last access and the idle timeout passed. See
         <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry> for details on
         the time syntax supported. This option has no effect if only a regular mount is established, and automounting
@@ -265,7 +265,7 @@
 
         <listitem><para>This option only has an effect in automount mode,
         and controls whether the automount unit shall be bound to the backing device's lifetime. If set, the
-        automount unit will be stopped automatically when the backing device vanishes. By default the automount unit
+        automount unit will be stopped automatically when the backing device vanishes. By default, the automount unit
         stays around, and subsequent accesses will block until backing device is replugged. This option has no effect
         in case of non-device mounts, such as network or virtual file system mounts.</para>
 
@@ -310,7 +310,7 @@
         all mount units that mount and failed are kept in memory until the user explicitly resets their failure state with
         <command>systemctl reset-failed</command> or an equivalent command. On the other hand, units that stopped
         successfully are unloaded immediately. If this option is turned on the "garbage collection" of units is more
-        aggressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for
+        aggressive, and unloads units regardless of whether they exited successfully or failed. This option is a shortcut for
         <command>--property=CollectMode=inactive-or-failed</command>, see the explanation for
         <varname>CollectMode=</varname> in
         <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for further

man/systemd-network-generator.service.xml

@@ -142,7 +142,7 @@
         credential <filename>network.link.50-foobar</filename> will be copied into a configuration file
         <filename>50-foobar.link</filename>.</para>
 
-        <para>Note that the resulting files are created world-readable, it's hence recommended to not include
+        <para>Note that the resulting files are created world-readable, it is hence recommended to not include
         secrets in these credentials, but supply them via separate credentials directly to
         <filename>systemd-networkd.service</filename>.</para>
 

man/systemd-nspawn.xml

@@ -351,7 +351,7 @@
         <listitem><para>Takes an image policy string as argument, as per
         <citerefentry><refentrytitle>systemd.image-policy</refentrytitle><manvolnum>7</manvolnum></citerefentry>. The
         policy is enforced when operating on the disk image specified via <option>--image=</option>, see
-        above. If not specified defaults to
+        above. If not specified, defaults to
         <literal>root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent:home=encrypted+unprotected+absent:srv=encrypted+unprotected+absent:esp=unprotected+absent:xbootldr=unprotected+absent:tmp=encrypted+unprotected+absent:var=encrypted+unprotected+absent</literal>,
         i.e. all recognized file systems in the image are used, but not the swap partition.</para>
 
@@ -363,7 +363,7 @@
 
         <listitem><para>Takes the path to an OCI runtime bundle to invoke, as specified in the <ulink
         url="https://github.com/opencontainers/runtime-spec/blob/master/spec.md">OCI Runtime Specification</ulink>. In
-        this case no <filename>.nspawn</filename> file is loaded, and the root directory and various settings are read
+        this case, no <filename>.nspawn</filename> file is loaded, and the root directory and various settings are read
         from the OCI runtime JSON data (but data passed on the command line takes precedence).</para>
 
         <xi:include href="version-info.xml" xpointer="v242"/></listitem>
@@ -375,7 +375,7 @@
         <listitem><para>Mount the container's root file system (and any other file systems contained in the container
         image) read-only. This has no effect on additional mounts made with <option>--bind=</option>,
         <option>--tmpfs=</option> and similar options. This mode is implied if the container image file or directory is
-        marked read-only itself. It is also implied if <option>--volatile=</option> is used. In this case the container
+        marked read-only itself. It is also implied if <option>--volatile=</option> is used. In this case, the container
         image on disk is strictly read-only, while changes are permitted but kept non-persistently in memory only. For
         further details, see below.</para></listitem>
       </varlistentry>
@@ -400,7 +400,7 @@
 
         <para>Note that if one of the volatile modes is chosen, its effect is limited to the root file system
         (or <filename>/var/</filename> in case of <option>state</option>), and any other mounts placed in the
-        hierarchy are unaffected — regardless if they are established automatically (e.g. the EFI system
+        hierarchy are unaffected — regardless of whether they are established automatically (e.g. the EFI system
         partition that might be mounted to <filename>/efi/</filename> or <filename>/boot/</filename>) or
         explicitly (e.g. through an additional command line option such as <option>--bind=</option>, see
         below). This means, even if <option>--volatile=overlay</option> is used changes to
@@ -626,7 +626,7 @@
         <constant>SIGTERM</constant>, in order to trigger an orderly shutdown of the container. Defaults to
         <constant>SIGRTMIN+3</constant> if <option>--boot</option> is used (on systemd-compatible init systems
         <constant>SIGRTMIN+3</constant> triggers an orderly shutdown). If <option>--boot</option> is not used and this
-        option is not specified the container's processes are terminated abruptly via <constant>SIGKILL</constant>. For
+        option is not specified, the container's processes are terminated abruptly via <constant>SIGKILL</constant>. For
         a list of valid signals, see <citerefentry
         project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
 
@@ -733,7 +733,7 @@
 
         <listitem><para>Make the container part of the specified slice, instead of the default
         <filename>machine.slice</filename>. This applies only if the machine is run in its own scope unit, i.e. if
-        <option>--keep-unit</option> isn't used.</para>
+        <option>--keep-unit</option> is not used.</para>
 
         <xi:include href="version-info.xml" xpointer="v206"/>
         </listitem>
@@ -743,7 +743,7 @@
         <term><option>--property=</option></term>
 
         <listitem><para>Set a unit property on the scope unit to register for the machine. This applies only if the
-        machine is run in its own scope unit, i.e. if <option>--keep-unit</option> isn't used. Takes unit property
+        machine is run in its own scope unit, i.e. if <option>--keep-unit</option> is not used. Takes unit property
         assignments in the same format as <command>systemctl set-property</command>. This is useful to set memory
         limits and similar for the container.</para>
 
@@ -1416,7 +1416,7 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
 
         <para>It's recommended to use <literal>copy-…</literal> or <literal>replace-…</literal> if the
         container shall be able to make changes to the DNS configuration on its own, deviating from the
-        host's settings. Otherwise <literal>bind</literal> is preferable, as it means direct changes to
+        host's settings. Otherwise, <literal>bind</literal> is preferable, as it means direct changes to
         <filename>/etc/resolv.conf</filename> in the container are not allowed, as it is a read-only bind
         mount (but note that if the container has enough privileges, it might simply go ahead and unmount the
         bind mount anyway). Note that both if the file is bind mounted and if it is copied no further
@@ -1601,7 +1601,7 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
 
         <para>Note that the user record propagated from the host into the container will contain the UNIX
         password hash of the user, so that seamless logins in the container are possible. If the container is
-        less trusted than the host it's hence important to use a strong UNIX password hash function
+        less trusted than the host it is hence important to use a strong UNIX password hash function
         (e.g. yescrypt or similar, with the <literal>$y$</literal> hash prefix).</para>
 
         <para>When binding a user from the host into the container checks are executed to ensure that the

man/systemd-pcrlock.xml

@@ -453,7 +453,7 @@
         <term><option>--nv-index=</option></term>
 
         <listitem><para>Specifies the NV index to store the policy in. Honoured by
-        <command>make-policy</command>. If not specified the command will automatically pick a free NV
+        <command>make-policy</command>. If not specified, the command will automatically pick a free NV
         index.</para>
 
         <xi:include href="version-info.xml" xpointer="v255"/></listitem>
@@ -464,7 +464,7 @@
 
         <listitem><para>Takes a path to read <filename>*.pcrlock</filename> and
         <filename>*.pcrlock.d/*.pcrlock</filename> files from. May be used more than once to specify multiple
-        such directories. If not specified defaults to <filename>/etc/pcrlock.d/</filename>,
+        such directories. If not specified, defaults to <filename>/etc/pcrlock.d/</filename>,
         <filename>/run/pcrlock.d/</filename>, <filename>/var/lib/pcrlock.d/</filename>,
         <filename>/usr/local/pcrlock.d/</filename>, <filename>/usr/lib/pcrlock.d/</filename>.</para>
 
@@ -534,7 +534,7 @@
         <term><option>--policy=</option></term>
 
         <listitem><para>Takes a file system path as argument. If specified, configures where to write pcrlock
-        policy metadata to. If not specified defaults to
+        policy metadata to. If not specified, defaults to
         <filename>/var/lib/systemd/pcrlock.json</filename>.</para>
 
         <xi:include href="version-info.xml" xpointer="v255"/></listitem>

man/systemd-pcrphase.service.xml

@@ -141,7 +141,7 @@
       <varlistentry>
         <term><option>--bank=</option></term>
 
-        <listitem><para>Takes the PCR banks to extend the specified word into. If not specified the tool
+        <listitem><para>Takes the PCR banks to extend the specified word into. If not specified, the tool
         automatically determines all enabled PCR banks and measures the word into all of
         them.</para>
 
@@ -173,7 +173,7 @@
         <term><option>--graceful</option></term>
 
         <listitem><para>If no TPM2 firmware, kernel subsystem, kernel driver or device support is found, exit
-        with exit status 0 (i.e. indicate success). If this is not specified any attempt to measure without a
+        with exit status 0 (i.e. indicate success). If this is not specified, any attempt to measure without a
         TPM2 device will cause the invocation to fail.</para>
 
         <xi:include href="version-info.xml" xpointer="v253"/></listitem>

man/systemd-repart.xml

@@ -168,7 +168,7 @@
       <varlistentry>
         <term><option>--dry-run=</option></term>
 
-        <listitem><para>Takes a boolean. If this switch is not specified <option>--dry-run=yes</option> is
+        <listitem><para>Takes a boolean. If this switch is not specified, <option>--dry-run=yes</option> is
         the implied default. Controls whether <filename>systemd-repart</filename> executes the requested
         re-partition operations or whether it should only show what it would do. Unless
         <option>--dry-run=no</option> is specified <filename>systemd-repart</filename> will not actually
@@ -183,7 +183,7 @@
         <listitem><para>Takes one of <literal>refuse</literal>, <literal>allow</literal>,
         <literal>require</literal>, <literal>force</literal> or <literal>create</literal>. Controls how to
         operate on block devices that are entirely empty, i.e. carry no partition table/disk label yet. If
-        this switch is not specified the implied default is <literal>refuse</literal>.</para>
+        this switch is not specified, the implied default is <literal>refuse</literal>.</para>
 
         <para>If <literal>refuse</literal> <command>systemd-repart</command> requires that the block device
         it shall operate on already carries a partition table and refuses operation if none is found. If
@@ -202,9 +202,9 @@
       <varlistentry>
         <term><option>--discard=</option></term>
 
-        <listitem><para>Takes a boolean. If this switch is not specified <option>--discard=yes</option> is
+        <listitem><para>Takes a boolean. If this switch is not specified ,<option>--discard=yes</option> is
         the implied default. Controls whether to issue the <constant>BLKDISCARD</constant> I/O control
-        command on the space taken up by any added partitions or on the space in between them. Usually, it's
+        command on the space taken up by any added partitions or on the space in between them. Usually, it is
         a good idea to issue this request since it tells the underlying hardware that the covered blocks
         shall be considered empty, improving performance. If operating on a regular file instead of a block
         device node, a sparse file is generated.</para>
@@ -242,7 +242,7 @@
       <varlistentry>
         <term><option>--factory-reset=</option></term>
 
-        <listitem><para>Takes boolean. If this switch is not specified <option>--factory=reset=no</option> is
+        <listitem><para>Takes boolean. If this switch is not specified, <option>--factory=reset=no</option> is
         the implied default. Controls whether to operate in "factory reset" mode, see above. If set to true
         this will remove all existing partitions marked with <varname>FactoryReset=</varname> set to yes
         early while executing the re-partitioning algorithm. Use with care, this is a great way to lose all
@@ -299,7 +299,7 @@
 
         <listitem><para>Takes a UUID as argument or the special value <constant>random</constant>. If a UUID
         is specified the UUIDs to assign to partitions and the partition table itself are derived via
-        cryptographic hashing from it. If not specified it is attempted to read the machine ID from the host
+        cryptographic hashing from it. If not specified, it is attempted to read the machine ID from the host
         (or more precisely, the root directory configured via <option>--root=</option>) and use it as seed
         instead, falling back to a randomized seed otherwise. Use <option>--seed=random</option> to force a
         randomized seed. Explicitly specifying the seed may be used to generated strictly reproducible
@@ -337,8 +337,8 @@
         <listitem><para>Takes a file system path. Configures the encryption key to use when setting up LUKS2
         volumes configured with the <varname>Encrypt=key-file</varname> setting in partition files. Should
         refer to a regular file containing the key, or an <constant>AF_UNIX</constant> stream socket in the
-        file system. In the latter case a connection is made to it and the key read from it. If this switch
-        is not specified the empty key (i.e. zero length key) is used. This behaviour is useful for setting
+        file system. In the latter case, a connection is made to it and the key read from it. If this switch
+        is not specified, the empty key (i.e. zero length key) is used. This behaviour is useful for setting
         up encrypted partitions during early first boot that receive their user-supplied password only in a
         later setup step.</para>
 
@@ -455,7 +455,7 @@
         <term><option>--exclude-partitions=<replaceable>PARTITIONS</replaceable></option></term>
 
         <listitem><para>These options specify which partition types <command>systemd-repart</command> should
-        operate on. If <option>--include-partitions=</option> is used, all partitions that aren't specified
+        operate on. If <option>--include-partitions=</option> is used, all partitions that are not specified
         are excluded. If <option>--exclude-partitions=</option> is used, all partitions that are specified
         are excluded. Both options take a comma separated list of GPT partition type UUIDs or identifiers
         (see <varname>Type=</varname> in
@@ -470,7 +470,7 @@
 
         <listitem><para>This option specifies for which partition types <command>systemd-repart</command>
         should defer. All partitions that are deferred using this option are still taken into account when
-        calculating the sizes and offsets of other partitions, but aren't actually written to the disk image.
+        calculating the sizes and offsets of other partitions, but are not actually written to the disk image.
         The net effect of this option is that if you run <command>systemd-repart</command> again without this
         option, the missing partitions will be added as if they had not been deferred the first time
         <command>systemd-repart</command> was executed.</para>

man/systemd-resolved.service.xml

@@ -178,7 +178,7 @@
       DNS servers, unless the domain is specified explicitly as routing or search domain for the DNS server
       and interface. This means that on networks where the <literal>.local</literal> domain is defined in a
       site-specific DNS server, explicit search or routing domains need to be configured to make lookups work
-      within this DNS domain. Note that these days, it's generally recommended to avoid defining
+      within this DNS domain. Note that these days, it is generally recommended to avoid defining
       <literal>.local</literal> in a DNS server, as <ulink
       url="https://tools.ietf.org/html/rfc6762">RFC6762</ulink> reserves this domain for exclusive
       MulticastDNS use.</para></listitem>
@@ -213,7 +213,7 @@
 
       <para>In case of single-label names, when search domains are defined, the same logic applies, except
       that the name is first suffixed by each of the search domains in turn. Note that this search logic
-      doesn't apply to any names with at least one dot. Also see the discussion about compatibility with
+      does not apply to any names with at least one dot. Also see the discussion about compatibility with
       the traditional glibc resolver below.</para></listitem>
 
       <listitem><para>If a query does not match any configured routing domain (either per-link or global), it
@@ -224,7 +224,7 @@
       and no global DNS server configured, one of the compiled-in fallback DNS servers is used.</para>
       </listitem>
 
-      <listitem><para>Otherwise the unicast DNS query fails, as no suitable DNS servers can be determined.
+      <listitem><para>Otherwise, the unicast DNS query fails, as no suitable DNS servers can be determined.
       </para></listitem>
     </itemizedlist>
 

man/systemd-run.xml

@@ -314,7 +314,7 @@
 
         <para>This option will result in <command>systemd-run</command> synchronously waiting for
         the transient service to terminate, similar to specifying <option>--wait</option>. If specified
-        along with <option>--wait</option>, <command>systemd-run</command> won't exit when manually disconnecting
+        along with <option>--wait</option>, <command>systemd-run</command> will not exit when manually disconnecting
         from the pseudo TTY device.</para>
 
         <para>Note that
@@ -475,7 +475,7 @@
         all units that ran and failed are kept in memory until the user explicitly resets their failure state with
         <command>systemctl reset-failed</command> or an equivalent command. On the other hand, units that ran
         successfully are unloaded immediately. If this option is turned on the "garbage collection" of units is more
-        aggressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for
+        aggressive, and unloads units regardless of whether they exited successfully or failed. This option is a shortcut for
         <command>--property=CollectMode=inactive-or-failed</command>, see the explanation for
         <varname>CollectMode=</varname> in
         <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for further
@@ -652,7 +652,7 @@ There is a screen on:
       <literal>&lt;></literal>, <literal>&lt;${INVOCATION_ID}></literal>] as the argument array, and then
       <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
       generates <varname>${INVOCATION_ID}</varname> and substitutes it in the command-line. This substitution
-      could not be done on the client side, because the target ID that will be set for the service isn't
+      could not be done on the client side, because the target ID that will be set for the service is not
       known before the call is made.</para>
     </example>
 
@@ -675,7 +675,7 @@ There is a screen on:
       <citerefentry project='man-pages'><refentrytitle>bash</refentrytitle><manvolnum>1</manvolnum></citerefentry>
       shell which is started by the service unit. The shell expands <literal>$SHELL</literal> to the path of
       the shell, and <literal>$$</literal> to its process number, and then those strings are passed to the
-      <command>echo</command> built-in and printed to standard output (which in this case is connected to the
+      <command>echo</command> built-in and printed to standard output (which, in this case, is connected to the
       calling terminal).</para>
     </example>
 

man/systemd-sbsign.xml

@@ -43,7 +43,7 @@
 
         <listitem><para>Signs the given PE binary for EFI Secure Boot. Takes a path to a PE binary as its
         argument. If the PE binary already has a certificate table, the new signature will be added to it.
-        Otherwise a new certificate table will be created. The signed PE binary will be written to the path
+        Otherwise, a new certificate table will be created. The signed PE binary will be written to the path
         specified with <option>--output=</option>.</para>
 
         <xi:include href="version-info.xml" xpointer="v257"/>

man/systemd-sleep.conf.xml

@@ -139,7 +139,7 @@
         <term><varname>AllowHybridSleep=</varname></term>
         <term><varname>AllowSuspendThenHibernate=</varname></term>
 
-        <listitem><para>By default any power-saving mode is advertised if possible (i.e.
+        <listitem><para>By default, any power-saving mode is advertised if possible (i.e.
         the kernel supports that mode, the necessary resources are available). Those
         switches can be used to disable specific modes.</para>
 

man/systemd-soft-reboot.service.xml

@@ -58,7 +58,7 @@
       <listitem><para>The initrd initialization.</para></listitem>
     </itemizedlist>
 
-    <para>However this form of reboot comes with drawbacks as well:</para>
+    <para>However, this form of reboot comes with drawbacks as well:</para>
 
     <itemizedlist>
       <listitem><para>The OS update remains incomplete, as the kernel is not reset and continues
@@ -149,7 +149,7 @@ DefaultDependencies=no</programlisting>
     <para>Even though passing resources from one soft reboot cycle to the next is possible this way, we
     strongly suggest to use this functionality sparingly only, as it creates a more fragile system as
     resources from different versions of the OS and applications might be mixed with unforeseen
-    consequences. In particular it's recommended to <emphasis>avoid</emphasis> allowing processes to survive
+    consequences. In particular it is recommended to <emphasis>avoid</emphasis> allowing processes to survive
     the soft reboot operation, as this means code updates will necessarily be incomplete, and processes
     typically pin various other resources (such as the file system they are backed by), thus increasing
     memory usage (as two versions of the OS/application/file system might be kept in memory). Leaving

man/systemd-ssh-proxy.xml

@@ -65,13 +65,13 @@ Host .host
     must be of type <constant>SOCK_STREAM</constant>. Similar, SSH connections to <literal>vsock/</literal>
     followed by an <constant>AF_VSOCK</constant> CID will result in an SSH connection made to that
     CID. <literal>vsock-mux/</literal> followed by an absolute <constant>AF_UNIX</constant> file system
-    path to a socket is similar but for cloud-hypervisor/firecracker which don't allow
+    path to a socket is similar but for cloud-hypervisor/firecracker which do not allow
     direct <constant>AF_VSOCK</constant> communication between the host and guests, and provide their own
     multiplexer over <constant>AF_UNIX</constant> sockets. See
     <ulink url="https://github.com/cloud-hypervisor/cloud-hypervisor/blob/main/docs/vsock.md">cloud-hypervisor VSOCK support</ulink>
     and <ulink url="https://github.com/firecracker-microvm/firecracker/blob/main/docs/vsock.md">Using the Firecracker Virtio-vsock Device</ulink>.</para>
 
-    <para>Moreover connecting to <literal>.host</literal> will connect to the local host via SSH, without
+    <para>Moreover, connecting to <literal>.host</literal> will connect to the local host via SSH, without
     involving networking.</para>
 
     <para>This tool is supposed to be used together with

man/systemd-storagetm.service.xml

@@ -70,7 +70,7 @@
         url="https://nvmexpress.org/wp-content/uploads/NVM-Express-Base-Specification-2.0c-2022.10.04-Ratified.pdf">NVM
         Express Base Specification 2.0c</ulink>, section 4.5 "NVMe Qualified Names". Note that the NQN
         specified here will be suffixed with a dot and the block device name before it is exposed on the
-        NVMe target. If not specified defaults to
+        NVMe target. If not specified, defaults to
         <literal>nqn.2023-10.io.systemd:storagetm.<replaceable>ID</replaceable></literal>, where ID is
         replaced by a 128bit ID derived from
         <citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>

man/systemd-stub.xml

@@ -127,7 +127,7 @@
     multi-profile UKIs, see below.</para> <para>If UEFI SecureBoot is enabled and the
     <literal>.cmdline</literal> section is present in the executed image, any attempts to override the kernel
     command line by passing one as invocation parameters to the EFI binary are ignored. Thus, in order to
-    allow overriding the kernel command line, either disable UEFI SecureBoot, or don't include a kernel
+    allow overriding the kernel command line, either disable UEFI SecureBoot, or do not include a kernel
     command line PE section in the kernel image file. If a command line is accepted via EFI invocation
     parameters to the EFI binary it is measured into TPM PCR 12 (if a TPM is present).</para> <para>If a
     DeviceTree is embedded in the <literal>.dtb</literal> section, it replaces an existing DeviceTree in the
@@ -345,12 +345,12 @@
     </table>
 
     <para>The section list above would define three profiles. The first four sections make up the base
-    profile. A <literal>.profile</literal> section then introduces profile @0. It doesn't override any
+    profile. A <literal>.profile</literal> section then introduces profile @0. It does not override any
     sections (or add any) from the base section, hence it is immediately followed by another
     <literal>.profile</literal> section that then introduces section @1. This profile overrides the kernel
     command line. Finally, the last two sections define section @2, again overriding the command line. (Note
     that in this example the first <literal>.cmdline</literal> could also moved behind the first
-    <literal>.profile</literal> with equivalent effect. To keep things nicely extensible, it's probably a
+    <literal>.profile</literal> with equivalent effect. To keep things nicely extensible, it is probably a
     good idea to keep the generic command line in the base section instead of profile 0, in case later added
     profiles might want to reuse it.)</para>
 
@@ -526,7 +526,7 @@
 
         <listitem><para>Similar to <varname>LoaderDevicePartUUID</varname> and
         <varname>StubImageIdentifier</varname>, but indicates the location of the unified kernel image EFI
-        binary rather than the location of the boot loader binary, regardless if booted via a boot loader
+        binary rather than the location of the boot loader binary, regardless of whether booted via a boot loader
         or not.</para>
 
         <xi:include href="version-info.xml" xpointer="v257"/></listitem>
@@ -597,7 +597,7 @@
     </variablelist>
 
     <para>Note that some of the variables above may also be set by the boot loader. The stub will only set
-    them if they aren't set already. Some of these variables are defined by the <ulink
+    them if they are not set already. Some of these variables are defined by the <ulink
     url="https://systemd.io/BOOT_LOADER_INTERFACE">Boot Loader Interface</ulink>.</para>
   </refsect1>
 

man/systemd-sysext.xml

@@ -204,8 +204,8 @@
     component over the immutable OS image without doing a full OS rebuild or modifying the nominally
     immutable image. (e.g. "install" a locally built package with <command>DESTDIR=/var/lib/extensions/mytest
     make install &amp;&amp; systemd-sysext refresh</command>, making it available in
-    <filename>/usr/</filename> as if it was installed in the OS image itself.) This case works regardless if
-    the underlying host <filename>/usr/</filename> is managed as immutable disk image or is a traditional
+    <filename>/usr/</filename> as if it was installed in the OS image itself.) This case works regardless of
+    whether the underlying host <filename>/usr/</filename> is managed as immutable disk image or is a traditional
     package manager controlled (i.e. writable) tree.</para>
 
     <para>With <command>systemd-confext</command> one can perform runtime reconfiguration of OS services.
@@ -371,7 +371,7 @@
 
         <listitem><para>Takes an image policy string as argument, as per
         <citerefentry><refentrytitle>systemd.image-policy</refentrytitle><manvolnum>7</manvolnum></citerefentry>. The
-        policy is enforced when operating on system extension disk images. If not specified defaults to
+        policy is enforced when operating on system extension disk images. If not specified, defaults to
         <literal>root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent</literal>
         for system extensions, i.e. only the root and <filename>/usr/</filename> file systems in the image
         are used. For configuration extensions defaults to

man/systemd-system.conf.xml

@@ -192,7 +192,7 @@
         <term><varname>NUMAMask=</varname></term>
 
         <listitem><para>Configures the NUMA node mask that will be associated with the selected NUMA policy. Note that
-        <option>default</option> and <option>local</option> NUMA policies don't require explicit NUMA node mask and
+        <option>default</option> and <option>local</option> NUMA policies do not require explicit NUMA node mask and
         value of the option can be empty. Similarly to <varname>NUMAPolicy=</varname>, value can be overridden
         by individual services in unit files, see
         <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
@@ -371,7 +371,7 @@
         running and hence <varname>RuntimeWatchdogSec=</varname> is still honoured. In order to define a
         timeout on this first phase of system shutdown, configure <varname>JobTimeoutSec=</varname> and
         <varname>JobTimeoutAction=</varname> in the [Unit] section of the
-        <filename>shutdown.target</filename> unit. By default <varname>RuntimeWatchdogSec=</varname> defaults
+        <filename>shutdown.target</filename> unit. By default, <varname>RuntimeWatchdogSec=</varname> defaults
         to 0 (off), and <varname>RebootWatchdogSec=</varname> to 10min.</para>
 
         <para><varname>KExecWatchdogSec=</varname> may be used to additionally enable the watchdog when kexec