From: Robert Karszniewicz <avoidr@posteo.de>
To: barebox@lists.infradead.org
Subject: [PATCH] README: add some commas for clarity
Date: Sat, 19 Sep 2020 16:55:58 +0200 [thread overview]
Message-ID: <20200919145558.12274-1-avoidr@posteo.de> (raw)
Signed-off-by: Robert Karszniewicz <avoidr@posteo.de>
---
README | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/README b/README
index d8077d21b..0a837b2de 100644
--- a/README
+++ b/README
@@ -114,7 +114,7 @@ in board/sandbox/env:
# ./scripts/bareboxenv -s -p 0x10000 arch/sandbox/board/env env.bin
-To get some files to play with you can generate a cramfs image:
+To get some files to play with, you can generate a cramfs image:
# mkcramfs somedir/ cramfs.bin
The barebox image is a normal Linux executable, so it can be started
@@ -133,14 +133,14 @@ given with '-i' will appear as /dev/fd[n].
If barebox finds a valid configuration sector on /dev/env0 it will
load it to /env. It then executes /env/init if it exists. If you have
-loaded the example environment barebox will show you a menu asking for
+loaded the example environment, barebox will show you a menu asking for
your settings.
-If you have started barebox as root you will find a new tap device on your
+If you have started barebox as root, you will find a new tap device on your
host which you can configure using ifconfig. Once you configured bareboxs
-network settings accordingly you can do a ping or tftpboot.
+network settings accordingly, you can do a ping or tftpboot.
-If you have mapped a cramfs image try mounting it with
+If you have mapped a cramfs image, try mounting it with
# mkdir /cram
# mount /dev/fd0 cramfs /cram
--
2.28.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2020-09-19 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 14:55 Robert Karszniewicz [this message]
2020-09-21 5:56 ` 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=20200919145558.12274-1-avoidr@posteo.de \
--to=avoidr@posteo.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