[ptxdist] [PATCH 2/4] doc: follow 'proselint' and improve the text

[Juergen Borleis <jbe@pengutronix.de>]

Follow the hints of the nice tool 'proselint'...

Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
---
 doc/daily_work.inc  | 2 +-
 doc/ref_manual.rst  | 4 ++--
 doc/user_manual.inc | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/daily_work.inc b/doc/daily_work.inc
index e4260e448..3fc894106 100644
--- a/doc/daily_work.inc
+++ b/doc/daily_work.inc
@@ -356,7 +356,7 @@ Using available CPU Cores
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 PTXdist uses all available CPU cores when building a project by default.
-But there are some exceptions:
+There are some exceptions:
 
 -  the prepare stage of all autotools build system based packages can
    use only one CPU core. This is due to the fact, the running
diff --git a/doc/ref_manual.rst b/doc/ref_manual.rst
index 96274ac97..69f7fdee8 100644
--- a/doc/ref_manual.rst
+++ b/doc/ref_manual.rst
@@ -556,7 +556,7 @@ Usage:
 
 This macro is very similar to ``world/compile``. The only differences is
 that is uses the specified ``build arguments`` instead of
-``<PKG>_MAKE_OPT``.  This is usefull if ``make`` needs to be called more
+``<PKG>_MAKE_OPT``. This is usefull if ``make`` needs to be called more
 than once in the compile stage.
 
 world/execute, execute
@@ -622,7 +622,7 @@ The ``<source>`` parameter can be:
   parameter in this case to locate the file to copy from. 
   The <destination> is uses a path relative to the :ref:`package install
   directory<pkg_pkgdir>`. This only works if the package uses the default
-  or a similar *install* stage.  For our *foo* example used source file is
+  or a similar *install* stage. For our *foo* example used source file is
   ``<platform-dir>/packages/foo-1.1.0/<destination>``.
 
 The ``<dest>`` parameter can be:
diff --git a/doc/user_manual.inc b/doc/user_manual.inc
index 9f78f5b46..0a4e4b34c 100644
--- a/doc/user_manual.inc
+++ b/doc/user_manual.inc
@@ -314,7 +314,7 @@ Next we will build the BSP to show some of PTXdist’s main features.
 Selecting a Userland Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-First of all we have to select a userland configuration. This step
+First we have to select a userland configuration. This step
 defines what kind of applications will be built for the hardware
 platform. The |ptxdistBSPName| project comes
 with a predefined configuration we select in the following step:
-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de