diff options
author | Anita Zhang <the.anitazha@gmail.com> | 2019-11-05 16:20:42 -0800 |
---|---|---|
committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2019-11-06 10:38:53 +0900 |
commit | 7792d9cdd484dcd8552cce0ea778eb09ed7fbc10 (patch) | |
tree | a496045f1c0cca7dd8caac95e12aa51e47b557b9 /man | |
parent | f03378805f23e85f8463913ee92b99d810b61594 (diff) | |
download | systemd-7792d9cdd484dcd8552cce0ea778eb09ed7fbc10.tar.gz |
man: small grammatical/word choice fixes to crypttab man page
Closes #13608
Diffstat (limited to 'man')
-rw-r--r-- | man/crypttab.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/man/crypttab.xml b/man/crypttab.xml index 76eef06bed..e4b1e43e42 100644 --- a/man/crypttab.xml +++ b/man/crypttab.xml @@ -208,11 +208,11 @@ <term><option>nofail</option></term> <listitem><para>This device will not be a hard dependency of - <filename>cryptsetup.target</filename>. It'll be still pulled in and started, but the system + <filename>cryptsetup.target</filename>. It'll still be pulled in and started, but the system will not wait for the device to show up and be unlocked, and boot will not fail if this is unsuccessful. Note that other units that depend on the unlocked device may still fail. In - particular, if the device is used for a mount point, the mount point itself is also needs to - have <option>noauto</option> option, or the boot will fail if the device is not unlocked + particular, if the device is used for a mount point, the mount point itself also needs to + have the <option>nofail</option> option, or the boot will fail if the device is not unlocked successfully.</para></listitem> </varlistentry> |