summaryrefslogtreecommitdiff
path: root/docs/HACKING.md
diff options
context:
space:
mode:
authorElias Probst <mail@eliasprobst.eu>2022-05-11 15:31:07 +0200
committerElias Probst <mail@eliasprobst.eu>2022-05-11 15:31:07 +0200
commit8f1a581e0de48fa2707ee289eab3c75df2b08c0e (patch)
tree2afb4e6933469faab7b8465e784f000f66195e62 /docs/HACKING.md
parent6f3961381aedbd9147020a50399cafbd330bd059 (diff)
downloadsystemd-8f1a581e0de48fa2707ee289eab3c75df2b08c0e.tar.gz
Use consistent formatting for `PID 1` across `docs/`
Diffstat (limited to 'docs/HACKING.md')
-rw-r--r--docs/HACKING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/HACKING.md b/docs/HACKING.md
index f6b42297e0..3f6838cfd0 100644
--- a/docs/HACKING.md
+++ b/docs/HACKING.md
@@ -30,7 +30,7 @@ Please always test your work before submitting a PR. For many of the components
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
+For some components (most importantly, systemd/PID 1 itself) this is not
possible, however. In order to simplify testing for cases like this we provide
a set of `mkosi` build files directly in the source tree.
[mkosi](https://github.com/systemd/mkosi) is a tool for building clean OS images