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 | |
| 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')
| -rw-r--r-- | docs/AUTOMATIC_BOOT_ASSESSMENT.md | 2 | ||||
| -rw-r--r-- | docs/BLOCK_DEVICE_LOCKING.md | 2 | ||||
| -rw-r--r-- | docs/CODING_STYLE.md | 2 | ||||
| -rw-r--r-- | docs/ENVIRONMENT.md | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/docs/AUTOMATIC_BOOT_ASSESSMENT.md b/docs/AUTOMATIC_BOOT_ASSESSMENT.md index 6f7182a4b3..1ef4bdcfe1 100644 --- a/docs/AUTOMATIC_BOOT_ASSESSMENT.md +++ b/docs/AUTOMATIC_BOOT_ASSESSMENT.md @@ -97,7 +97,7 @@ Here's an example walkthrough of how this all fits together. see the `+1-2` tag, and rename the file to `4.14.11-300.fc27.x86_64+0-3.conf` and boot it. -6. If this boot also fails, on the next boot the boot loader will see the the +6. If this boot also fails, on the next boot the boot loader will see the tag `+0-3`, i.e. the counter reached zero. At this point the entry will be considered "bad", and ordered to the end of the list of entries. The next newest boot entry is now tried, i.e. the system automatically reverted back diff --git a/docs/BLOCK_DEVICE_LOCKING.md b/docs/BLOCK_DEVICE_LOCKING.md index 58178ad2f7..5509b41942 100644 --- a/docs/BLOCK_DEVICE_LOCKING.md +++ b/docs/BLOCK_DEVICE_LOCKING.md @@ -34,7 +34,7 @@ formatting tools to safely and easily take exclusive ownership of a block device while operating: before starting work on the block device, they should take an `LOCK_EX` lock on it. This has two effects: first of all, in case `systemd-udevd` is still processing the device the tool will wait for it to -finish. Second, after the lock is taken, it can be sure that that +finish. Second, after the lock is taken, it can be sure that `systemd-udevd` will refrain from processing the block device, and thus all other client applications subscribed to it won't get device notifications from potentially half-written data either. After the operation is complete the 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. diff --git a/docs/ENVIRONMENT.md b/docs/ENVIRONMENT.md index f72ed20dd0..e81eaf2a35 100644 --- a/docs/ENVIRONMENT.md +++ b/docs/ENVIRONMENT.md @@ -217,7 +217,7 @@ systemd itself: systemd-remount-fs: -* `$SYSTEMD_REMOUNT_ROOT_RW=1` — if set and and no entry for the root directory +* `$SYSTEMD_REMOUNT_ROOT_RW=1` — if set and no entry for the root directory exists in /etc/fstab (this file always takes precedence), then the root directory is remounted writable. This is primarily used by systemd-gpt-auto-generator to ensure the root partition is mounted writable |