From: Felicitas Jung <f.jung@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Felicitas Jung <f.jung@pengutronix.de>
Subject: [ptxdist] [PATCH 2/2] readme: fix spelling
Date: Mon, 6 Apr 2020 14:02:27 +0200 [thread overview]
Message-ID: <20200406120227.8669-2-f.jung@pengutronix.de> (raw)
In-Reply-To: <20200406120227.8669-1-f.jung@pengutronix.de>
Signed-off-by: Felicitas Jung <f.jung@pengutronix.de>
---
README | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README b/README
index 54e64343d..60ac8b152 100644
--- a/README
+++ b/README
@@ -18,7 +18,7 @@ to build everything and
to install it. When you start using PTXdist, make sure your $PATH
environment variable points to <installpath>/bin, because that's where
-the ptxdist frontend program is being installed to.
+the PTXdist frontend program is being installed to.
For developers who want to work with git versions of PTXdist it is only
necessary to run "./autogen.sh && ./configure && make" and set the PATH
@@ -39,7 +39,7 @@ and you'll find a root tree in ./platform-<name>/root/, and disk images
in ./platform-<name>/images/. Voilà.
All magic necessary to do these things in a cross enviroment are written
-into "recipies", living in rules/*.make, and config menues in
+into "recipes", living in rules/*.make, and config menues in
rules/*.in.
Documentation
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-04-06 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 12:02 [ptxdist] [PATCH 1/2] doc/welcome.rst: " Felicitas Jung
2020-04-06 12:02 ` Felicitas Jung [this message]
2020-04-06 12:44 ` [ptxdist] [PATCH 2/2] readme: " Roland Hieber
2020-04-07 7:34 ` Michael Olbrich
2020-04-07 7:31 ` [ptxdist] [APPLIED] " Michael Olbrich
2020-04-07 7:31 ` Michael Olbrich
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=20200406120227.8669-2-f.jung@pengutronix.de \
--to=f.jung@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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