have setup for systemd, to ensure our codebase stays in good shape.
Please always test your work before submitting a PR. For many of the components
-of systemd testing is straight-forward as you can simply compile systemd and
+of systemd testing is straightforward as you can simply compile systemd and
run the relevant tool from the build directory.
For some components (most importantly, systemd/PID1 itself) this is not
or newline characters (or any other control characters or non-ASCII characters)
and may not be empty.
-Serialization into the datagram payload or `memfd` is straight-forward: each
+Serialization into the datagram payload or `memfd` is straightforward: each
key/value pair is serialized via one of two methods:
* The first method inserts a `=` character between key and value, and suffixes
rules above.
* No embedded NUL bytes (rationale: handling in C must be possible and
- straight-forward)
+ straightforward)
* No names consisting fully of digits (rationale: avoid confusion with numeric
UID/GID specifications)
<listitem>
<para>Dump the systemd manager environment block. This is the environment
block that is passed to all processes the manager spawns. The environment
- block will be dumped in straight-forward form suitable for sourcing into
+ block will be dumped in straightforward form suitable for sourcing into
most shells. If no special characters or whitespace is present in the variable
values, no escaping is performed, and the assignments have the form
<literal>VARIABLE=value</literal>. If whitespace or characters which have