diff options
author | Dmitry V. Levin <ldv@strace.io> | 2023-01-15 08:00:00 +0000 |
---|---|---|
committer | Dmitry V. Levin <ldv@strace.io> | 2023-01-23 22:52:34 +0000 |
commit | e347d53aceaf882c26256bce3867d270a72d20ad (patch) | |
tree | ff2324b3b0c1c667df7e843dd6c4820cc73c80c0 /docs/ARCHITECTURE.md | |
parent | d8b67e05fbeb9d8ad1b37b1a15add5731a2b7f77 (diff) | |
download | systemd-e347d53aceaf882c26256bce3867d270a72d20ad.tar.gz |
docs: fix grammar a bit
Diffstat (limited to 'docs/ARCHITECTURE.md')
-rw-r--r-- | docs/ARCHITECTURE.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index eec2ff3026..c777fa75de 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -44,7 +44,7 @@ on `src/fundamental/` + `src/basic/`, or also on `src/libsystemd/`, or also on `src/shared/`. You might wonder what kind of code belongs where. In general, the rule is that -code should linked as few times as possible, ideally only once. Thus code that +code should be linked as few times as possible, ideally only once. Thus code that is used by "higher-level" components (e.g. our binaries which are linked to `libsystemd-shared-<nnn>.so`), would go to a subdirectory specific to that component if it is only used there. If the code is to be shared between @@ -99,7 +99,7 @@ setting, it is necessary to support all three input methods: unit settings being parsed by common helpers, with the definition in the generator file `src/core/load-fragment-gperf.gperf.in` 2. D-Bus messages are defined and parsed in `src/core/dbus-*.c` -3. `systemd-run` and `systemctl set-property` do client-side parsing and translating into +3. `systemd-run` and `systemctl set-property` do client-side parsing and translation into D-Bus messages in `src/shared/bus-unit-util.c` So that they are exercised by the fuzzing CI, new unit settings should also be listed in the |