summaryrefslogtreecommitdiff
path: root/docs/CODING_STYLE.md
diff options
context:
space:
mode:
authorDmitry V. Levin <ldv@strace.io>2023-01-15 08:00:00 +0000
committerDmitry V. Levin <ldv@strace.io>2023-01-23 22:52:34 +0000
commite347d53aceaf882c26256bce3867d270a72d20ad (patch)
treeff2324b3b0c1c667df7e843dd6c4820cc73c80c0 /docs/CODING_STYLE.md
parentd8b67e05fbeb9d8ad1b37b1a15add5731a2b7f77 (diff)
downloadsystemd-e347d53aceaf882c26256bce3867d270a72d20ad.tar.gz
docs: fix grammar a bit
Diffstat (limited to 'docs/CODING_STYLE.md')
-rw-r--r--docs/CODING_STYLE.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/CODING_STYLE.md b/docs/CODING_STYLE.md
index 4df3ccf08e..26183ff372 100644
--- a/docs/CODING_STYLE.md
+++ b/docs/CODING_STYLE.md
@@ -208,7 +208,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
variables if you are sure that thread-safety doesn't matter in your
case. Alternatively, consider using TLS, which is pretty easy to use with
gcc's `thread_local` concept. It's also OK to store data that is inherently
- global in global variables, for example data parsed from command lines, see
+ global in global variables, for example, data parsed from command lines, see
below.
- Our focus is on the GNU libc (glibc), not any other libcs. If other libcs are
@@ -604,7 +604,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
i.e. file system objects that are supposed to be regular files whose paths
were specified by the user and hence might actually refer to other types of
file system objects. This is a good idea so that we don't end up blocking on
- 'strange' file nodes, for example if the user pointed us to a FIFO or device
+ 'strange' file nodes, for example, if the user pointed us to a FIFO or device
node which may block when opening. Moreover even for actual regular files
`O_NONBLOCK` has a benefit: it bypasses any mandatory lock that might be in
effect on the regular file. If in doubt consider turning off `O_NONBLOCK`