summaryrefslogtreecommitdiff
path: root/docs/AUTOMATIC_BOOT_ASSESSMENT.md
diff options
context:
space:
mode:
authornikolas <nnyby@columbia.edu>2018-11-23 14:28:39 -0500
committerYu Watanabe <watanabe.yu+github@gmail.com>2018-11-24 04:28:39 +0900
commitb24546706e9728b313641e30587d50c46278cc65 (patch)
tree0eec5ca976c16b636599bafef7be595715dcf9b0 /docs/AUTOMATIC_BOOT_ASSESSMENT.md
parent1e268f423c66b818da70fbb30c3fb7657cd93080 (diff)
downloadsystemd-b24546706e9728b313641e30587d50c46278cc65.tar.gz
Fix a few docs typos (#10907)
Found with [codespell](https://github.com/codespell-project/codespell)
Diffstat (limited to 'docs/AUTOMATIC_BOOT_ASSESSMENT.md')
-rw-r--r--docs/AUTOMATIC_BOOT_ASSESSMENT.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/AUTOMATIC_BOOT_ASSESSMENT.md b/docs/AUTOMATIC_BOOT_ASSESSMENT.md
index 0909d88b5c..83acdab446 100644
--- a/docs/AUTOMATIC_BOOT_ASSESSMENT.md
+++ b/docs/AUTOMATIC_BOOT_ASSESSMENT.md
@@ -32,7 +32,7 @@ components:
* The
[`systemd-boot-check-no-failures.service(8)`](https://www.freedesktop.org/software/systemd/man/systemd-boot-check-no-failures.service.html)
service is a simple health check tool that determines whether the boot
- completed successfuly. When enabled it becomes an indirect dependency of
+ completed successfully. When enabled it becomes an indirect dependency of
`systemd-bless-boot.service` (by means of `boot-complete.target`, see
below), ensuring that the boot will not be considered successful if there are
any failed services.
@@ -99,7 +99,7 @@ Here's an example walkthrough of how this all fits together.
newest boot entry is now tried, i.e. the system automatically reverted back
to an earlier version.
-The above describes the walkthrough when the selected boot entry continously
+The above describes the walkthrough when the selected boot entry continuously
fails. Let's have a look at an alternative ending to this walkthrough. In this
scenario the first 4 steps are the same as above: