summaryrefslogtreecommitdiff
path: root/docs/JOURNAL_NATIVE_PROTOCOL.md
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2022-03-15 17:04:36 +0100
committerLuca Boccassi <luca.boccassi@gmail.com>2022-03-15 22:46:09 +0000
commit4bb37359f68f800f6ef46fa7560a715ff5254de9 (patch)
tree4476ba53d87c8a104a19e34d18b96006f306e98a /docs/JOURNAL_NATIVE_PROTOCOL.md
parent3b1276c28b76108fcf0509ff8f2c386221b082c3 (diff)
downloadsystemd-4bb37359f68f800f6ef46fa7560a715ff5254de9.tar.gz
docs: s/straight-forward/straightforward/
Inspired by https://github.com/systemd/systemd/pull/20156#discussion_r810878846
Diffstat (limited to 'docs/JOURNAL_NATIVE_PROTOCOL.md')
-rw-r--r--docs/JOURNAL_NATIVE_PROTOCOL.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/JOURNAL_NATIVE_PROTOCOL.md b/docs/JOURNAL_NATIVE_PROTOCOL.md
index d3fa9b7f73..77fb27fa07 100644
--- a/docs/JOURNAL_NATIVE_PROTOCOL.md
+++ b/docs/JOURNAL_NATIVE_PROTOCOL.md
@@ -60,7 +60,7 @@ bytes however, as well as any other binary data. Keys may not include the `=`
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