diff options
| author | Michael Prokop <mika@grml.org> | 2019-06-27 09:54:20 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-06-27 10:43:21 +0200 |
| commit | d238709c14c89884b2fdfc72c8228a4f30874df1 (patch) | |
| tree | 5e6a523c006ae991bac9aba5ad93cafdc757d725 /docs/CODING_STYLE.md | |
| parent | f9d269e14ddc77942ee6081e5317a9e0beb0ece9 (diff) | |
| download | systemd-d238709c14c89884b2fdfc72c8228a4f30874df1.tar.gz | |
docs: fix typos and duplicate words
s/and and/and/
s/explicity/explicitly/
s/that that/that/
s/the the/the/
s/is is/it is/
s/overriden/overridden/
Diffstat (limited to 'docs/CODING_STYLE.md')
| -rw-r--r-- | docs/CODING_STYLE.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/CODING_STYLE.md b/docs/CODING_STYLE.md index 517bd2b41d..bf7ba3ea69 100644 --- a/docs/CODING_STYLE.md +++ b/docs/CODING_STYLE.md @@ -206,7 +206,7 @@ title: Coding Style numeric. Specifically, if you have an `int b` and it's only used in a boolean sense, by all means check its state with `if (b) …` — but if `b` can actually have more than two semantic values, and you want to compare for non-zero, - then please write that explicity with `if (b != 0) …`. This helps readability + then please write that explicitly with `if (b != 0) …`. This helps readability as the value range and semantical behaviour is directly clear from the condition check. As a special addition: when dealing with pointers which you want to check for non-NULL-ness, you may also use downgrade-to-bool feature. |