mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Enrico Jorns <ejo@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Enrico Jorns <ejo@pengutronix.de>
Subject: [PATCH 1/8] doc: bootchooser: fix typos etc.
Date: Fri, 15 Feb 2019 13:53:41 +0100	[thread overview]
Message-ID: <20190215125348.12851-2-ejo@pengutronix.de> (raw)
In-Reply-To: <20190215125348.12851-1-ejo@pengutronix.de>

Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
---
 Documentation/user/bootchooser.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst
index 05725d8f21..667ab7d736 100644
--- a/Documentation/user/bootchooser.rst
+++ b/Documentation/user/bootchooser.rst
@@ -3,7 +3,7 @@
 Barebox Bootchooser
 ===================
 
-In many cases embedded systems are layed out redundantly with multiple
+In many cases embedded systems are laid out redundantly with multiple
 kernels and multiple root file systems. The *bootchooser* framework provides
 the building blocks to model different use cases without the need to start
 from scratch over and over again.
@@ -60,7 +60,7 @@ the boot target won't be booted anymore. To prevent that, the ``remaining_attemp
 counter must be reset to its default. There are different flags in the
 *bootchooser* which control resetting the ``remaining_attempts`` counter,
 controlled by the ``global.bootchooser.reset_attempts`` variable. It holds a
-list of space separated flags. Possible values are:
+list of space-separated flags. Possible values are:
 
 - empty: counters will never be reset
 - ``power-on``: The ``remaining_attempts`` counters of all enabled boot targets are reset
@@ -97,7 +97,7 @@ options not specific to any boot target.
 ``global.bootchooser.reset_attempts``
   Already described in :ref:`Bootchooser Algorithm <bootchooser,algorithm>`
 ``global.bootchooser.reset_priorities``
-  A space separated list of events that cause *bootchooser* to reset the priorities of
+  A space-separated list of events that cause *bootchooser* to reset the priorities of
   all boot targets. Possible values:
 
   * empty: priorities will never be reset
@@ -111,7 +111,7 @@ options not specific to any boot target.
   Variable prefix when *bootchooser* is used with the *state* framework as backend
   for storing run-time data, see below.
 ``global.bootchooser.targets``
-  Space separated list of boot targets that are used. For each entry in the list
+  Space-separated list of boot targets that are used. For each entry in the list
   a corresponding
   set of ``global.bootchooser.<targetname>.<variablename>`` variables must exist.
 ``global.bootchooser.last_chosen``
@@ -125,7 +125,7 @@ Setup Example
 We want to set up a redundant machine with two bootable systems within one shared
 memory, here a NAND type flash memory with a UBI partition. We have a 512 MiB NAND
 type flash, to be used only for the root filesystem. The devicetree doesn't
-define any partition, because we want to run one UBI partition with two volumens
+define any partition, because we want to run one UBI partition with two volumes
 for the redundant root filesystems on this flash memory.
 
 .. code-block:: text
-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2019-02-15 12:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 12:53 [PATCH 0/8] Bootchooser Documentation Update Enrico Jorns
2019-02-15 12:53 ` Enrico Jorns [this message]
2019-02-15 12:53 ` [PATCH 2/8] doc: bootchooser: explicitly note configuration vs. storage backend Enrico Jorns
2019-02-15 12:53 ` [PATCH 3/8] doc: bootchooser: be more explicit what bootchooser.state_prefix is for Enrico Jorns
2019-02-15 12:53 ` [PATCH 4/8] doc: bootchooser: be more explicit about attempts reset on successful boot Enrico Jorns
2019-02-15 12:53 ` [PATCH 5/8] doc: bootchooser: note how to actually start the bootchooser Enrico Jorns
2019-02-15 12:53 ` [PATCH 6/8] doc: bootchooser: be more explicit about when the bootchooser terminates Enrico Jorns
2019-02-15 12:53 ` [PATCH 7/8] doc: bootchooser: add details about bootchooser.reset_attempts handling Enrico Jorns
2019-02-15 12:53 ` [PATCH 8/8] doc: bootchooser: add retry handling to algorithm description Enrico Jorns
2019-02-18  8:30 ` [PATCH 0/8] Bootchooser Documentation Update Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190215125348.12851-2-ejo@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox