mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH 2/2] doc: environment: correct typos, grammar and wording
Date: Mon,  9 Sep 2019 13:47:29 +0200	[thread overview]
Message-ID: <20190909114729.11023-2-rhi@pengutronix.de> (raw)
In-Reply-To: <20190909114729.11023-1-rhi@pengutronix.de>

---
 doc/environment.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/environment.rst b/doc/environment.rst
index 8d025118bc15..64b0cd3af21d 100644
--- a/doc/environment.rst
+++ b/doc/environment.rst
@@ -585,8 +585,8 @@ be extracted there.
 This is a convenient way to build the toolchain once and install it on
 multiple hosts. The host applications and libraries in the tarball are
 stripped to reduce the used disk space. So it cannot be used to debug the
-toolchain itself (e.g. when an ICE (internal compiler error) occurs. The
-target libraries (e.g. glibc) are not touched to debugging target
+toolchain itself (e.g. when an ICE (internal compiler error) occurs). The
+target libraries (e.g. glibc) are not touched so debugging target
 applications works as usual.
 
 ::
@@ -608,7 +608,7 @@ Building additional Toolchains
 The OSELAS.Toolchain- bundle comes with various predefined toolchains.
 Refer the ``ptxconfigs/`` folder for other definitions. To build
 additional toolchains we only have to clean our current toolchain
-project, removing the current ``selected_ptxconfig`` link and creating a
+project, remove the current ``selected_ptxconfig`` link and create a
 new one.
 
 ::
@@ -618,18 +618,18 @@ new one.
     $ ptxdist select ptxconfigs/any_other_toolchain_def.ptxconfig
     $ ptxdist go
 
-And of course any additional steps needed to protect or install the
+This is then followed of course by any additional steps needed to protect or install the
 toolchain depending on the version.
 
-All toolchains will be installed side by side architecture dependent
-into directory
+All toolchains will be installed side by side into architecture dependent
+directories named
 
 ::
 
     /opt/OSELAS.Toolchain-|oselasTCNVendorVersion|/<architecture>
 
-Different toolchains for the same architecture will be installed side by
-side version dependent into directory
+Different toolchains for the same architecture will be installed side by side
+into version dependent directories named
 
 ::
 
-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2019-09-09 11:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 11:47 [ptxdist] [PATCH 1/2] doc: contributing: mention configure_helper.py support for cmake Roland Hieber
2019-09-09 11:47 ` Roland Hieber [this message]

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=20190909114729.11023-2-rhi@pengutronix.de \
    --to=rhi@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