docs, man: consistently use comma after "For example"

docs/BUILDING_IMAGES.md

@@ -161,7 +161,7 @@ the OS should take possession of the backing storage as necessary, dynamically
 using available space. Specifically:
 
 1. Additional partitions should be created, that make no sense to ship
-   pre-built in the image. For example `/tmp/` or `/home/` partitions, or even
+   pre-built in the image. For example, `/tmp/` or `/home/` partitions, or even
    `/var/` or the root file system (see above).
 
 2. Additional partitions should be created that shall function as A/B

docs/CGROUP_DELEGATION.md

@@ -78,7 +78,7 @@ Note that cgroup v1 is currently the most deployed implementation, even though
 it's semantically broken in many ways, and in many cases doesn't actually do
 what people think it does. cgroup v2 is where things are going, and most new
 kernel features in this area are only added to cgroup v2, and not cgroup v1
-anymore. For example cgroup v2 provides proper cgroup-empty notifications, has
+anymore. For example, cgroup v2 provides proper cgroup-empty notifications, has
 support for all kinds of per-cgroup BPF magic, supports secure delegation of
 cgroup trees to less privileged processes and so on, which all are not
 available on cgroup v1.

docs/CODING_STYLE.md

@@ -712,7 +712,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
 ## Committing to git
 
 - Commit message subject lines should be prefixed with an appropriate component
-  name of some kind. For example "journal: ", "nspawn: " and so on.
+  name of some kind. For example, "journal: ", "nspawn: " and so on.
 
 - Do not use "Signed-Off-By:" in your commit messages. That's a kernel thing we
   don't do in the systemd project.

docs/PORTABILITY_AND_STABILITY.md

@@ -155,7 +155,7 @@ without communicating with the `systemd` process:
 `systemd-sysusers`.
 
 Many other programs support operation without the system manager except when
-the specific functionality requires such communication. For example
+the specific functionality requires such communication. For example,
 `journalctl` operates almost independently, but will query the boot id when
 `--boot` option is used; it also requires `systemd-journald` (and thus
 `systemd`) to be running for options like `--flush` and `--sync`.

docs/USERDB_AND_DESKTOPS.md

@@ -152,7 +152,7 @@ users registered in `/etc/passwd` or LDAP to users managed by
 ## Future Additions
 
 JSON user/group records are extensible, hence we can easily add any additional
-fields desktop environments require. For example pattern-based authentication
+fields desktop environments require. For example, pattern-based authentication
 is likely very useful on touch-based devices, and the user records should hence
 learn them natively. Fields for other authentication mechanisms, such as
 fingerprint authentication should be provided as well, eventually.

docs/USER_GROUP_API.md

@@ -129,7 +129,7 @@ interface. Specifically:
    `systemd-machined.service` and provides records for the users and groups used
    by local containers that use user namespacing.
 
-Other projects are invited to implement these services too. For example it
+Other projects are invited to implement these services too. For example, it
 would make sense for LDAP/ActiveDirectory projects to implement these
 interfaces, which would provide them a way to do per-user resource management
 enforced by systemd and defined directly in LDAP directories.

docs/USER_NAMES.md

@@ -151,7 +151,7 @@ user/group names accepted by the strict rules are also accepted by the relaxed
 rules, but not vice versa.
 
 Note that this relaxed mode does not refuse a couple of very questionable
-syntaxes. For example it permits a leading or embedded period. A leading period
+syntaxes. For example, it permits a leading or embedded period. A leading period
 is problematic because the matching home directory would typically be hidden
 from the user's/administrator's view. An embedded period is problematic since
 it creates ambiguity in traditional `chown` syntax (which is still accepted

man/systemd-system.conf.xml

@@ -464,7 +464,7 @@
         of slice units. Defaults to 15% of the minimum of <varname>kernel.pid_max=</varname>, <varname>kernel.threads-max=</varname>
         and root cgroup <varname>pids.max</varname>.
         Kernel has a default value for <varname>kernel.pid_max=</varname> and an algorithm of counting in case of more than 32 cores.
-        For example with the default <varname>kernel.pid_max=</varname>, <varname>DefaultTasksMax=</varname> defaults to 4915,
+        For example, with the default <varname>kernel.pid_max=</varname>, <varname>DefaultTasksMax=</varname> defaults to 4915,
         but might be greater in other systems or smaller in OS containers.</para></listitem>
       </varlistentry>
 

man/systemd.unit.xml

@@ -2329,7 +2329,7 @@ PrivateTmp=yes</programlisting>
       <title>Top level drop-ins with template units</title>
 
       <para>Top level per-type drop-ins can be used to change some aspect of
-      all units of a particular type. For example by creating the
+      all units of a particular type. For example, by creating the
       <filename index='false'>/etc/systemd/system/service.d/</filename>
       directory with a drop-in file, the contents of the drop-in file can be
       applied to all service units. We can take this further by having the