mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Gavin Schenk <g.schenk@eckelmann.de>
To: ptxdist@pengutronix.de
Cc: Gavin Schenk <g.schenk@eckelmann.de>
Subject: [ptxdist] [PATCH] doc: Fix typo in layer documentation
Date: Mon, 24 Sep 2018 14:41:19 +0200	[thread overview]
Message-ID: <20180924124119.382-1-g.schenk@eckelmann.de> (raw)

Signed-off-by: Gavin Schenk <g.schenk@eckelmann.de>
---

Are there ways where PTXdist itself is not the bottom layer?
If not you could write "In a way ..." that would make it clearer.

Thanks for this cool feature.
At the moment I have not a usecas, but I will keep layers in mind.


 doc/dev_manual.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/dev_manual.rst b/doc/dev_manual.rst
index d571117ae..a461f6851 100644
--- a/doc/dev_manual.rst
+++ b/doc/dev_manual.rst
@@ -1634,7 +1634,7 @@ workspace of the PTXdist project. Any ``selected_*`` links and the platform
 build directory are created here. The layer below is defined by the
 subdirectory or symlink named ``base/``. More can be stacked the same
 way, so ``base/base/`` is the third layer and so on.
-In may ways, PTXdist itself can be considered as the bottom layer. This is
+In many ways, PTXdist itself can be considered as the bottom layer. This is
 either implicit or explicit with on last ``base/`` symlink.
 
 A project can overwrite files provided by PTXdist in many different ways,
-- 
2.19.0


-- 
Eckelmann AG
Vorstand: Dipl.-Ing. Peter Frankenbach (Sprecher) Dipl.-Wi.-Ing. Philipp Eckelmann
Dr.-Ing. Marco Münchhof Dr.-Ing. Frank Uhlemann
Vorsitzender des Aufsichtsrats: Hubertus G. Krossa
Stv. Vorsitzender des Aufsichtsrats: Dr.-Ing. Gerd Eckelmann
Sitz der Gesellschaft: Berliner Str. 161, 65205 Wiesbaden, Amtsgericht Wiesbaden HRB 12636
http://www.eckelmann.de

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2018-09-24 12:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180924124119.382-1-g.schenk@eckelmann.de \
    --to=g.schenk@eckelmann.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