mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Markus Heidelberg <m.heidelberg@cab.de>
To: <ptxdist@pengutronix.de>
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: [ptxdist] [PATCH] Fix various typos, grammar and spelling
Date: Fri, 9 Aug 2024 11:26:39 +0200	[thread overview]
Message-ID: <20240809092639.47100-1-m.heidelberg@cab.de> (raw)

In documentation, help texts and a comment.

Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
---
 bin/ptxdist                | 2 +-
 doc/ref_make_variables.rst | 6 +++---
 doc/ref_parameter.rst      | 6 +++---
 rules/linux-firmware.in    | 2 +-
 rules/project-name.in      | 2 +-
 scripts/git-ptx-patches    | 2 +-
 6 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/bin/ptxdist b/bin/ptxdist
index 6d6de64d8..8d3c4595c 100755
--- a/bin/ptxdist
+++ b/bin/ptxdist
@@ -826,7 +826,7 @@ Options:
   --debug, -d			print out additional info (like make decisions)
   --quiet, -q			suppress output, show only stderr
   --silent, -s			alias for --quiet
-  --verbose, -v			be more verbose, print command before execute them
+  --verbose, -v			be more verbose, print command before execution
   --output-sync			Improve output readability for parallel building.
 				Disabled by default except for quiet builds.
   --no-output-sync		Disable output-sync if enabled by default.
diff --git a/doc/ref_make_variables.rst b/doc/ref_make_variables.rst
index 775ff71be..20c98995f 100644
--- a/doc/ref_make_variables.rst
+++ b/doc/ref_make_variables.rst
@@ -61,7 +61,7 @@ Global Variables
 Other useful variables:
 
 ``CROSS_PATH``
-  Use to find cross tools. This path must be used to create anything that
+  Used to find cross tools. This path must be used to create anything that
   depends on the target’s architecture, but needs something running on the
   host to do the job. Examples:
 
@@ -272,7 +272,7 @@ of the corresponding target package if it exists.
   When PTXdist extracts source archives, it will create ``<PKG>_DIR``
   first and then extracts the archive there. If ``<PKG>_STRIP_LEVEL`` is
   set to 1 (the default) then PTXdist removes the first directory level
-  defined inside the archive. For most packages that this is the same as
+  defined inside the archive. For most packages this is the same as
   just extracting the archive. However, this is useful for packages with
   badly named top-level directories or packages where the directory must be
   renamed to avoid collisions (e.g. gdbserver).
@@ -293,7 +293,7 @@ of the corresponding target package if it exists.
   keep the source tree free of build files.
 
   ``KEEP`` can be used instead of ``YES``. In this case the build tree is
-  not deleted at the beginning of the prepare stage. This make
+  not deleted at the beginning of the prepare stage. This makes
   reconfiguration faster. This should only be used for packages that can
   handle configuration changes correctly and rebuild everything as needed.
 
diff --git a/doc/ref_parameter.rst b/doc/ref_parameter.rst
index dd71046bb..46a934aab 100644
--- a/doc/ref_parameter.rst
+++ b/doc/ref_parameter.rst
@@ -20,7 +20,7 @@ Setup and Project Actions
   *platform*, *boardsetup*, *setup*, *go* and *images*.
 
 ``select <config>``
-  this action will select a user land
+  this action will select a userland
   configuration. This step is only required in projects where no
   ``selected_ptxconfig`` file is present. The <config> argument must point
   to a valid userland configuration file. PTXdist provides this feature
@@ -53,7 +53,7 @@ Setup and Project Actions
 
 ``setup``
   PTXdist uses some global settings, independent from the
-  project it is working on. These settings belong to users preferences or
+  project it is working on. These settings belong to user preferences or
   simply some network settings to permit PTXdist to download required
   packages.
 
@@ -348,7 +348,7 @@ Options
   suppress output, show only stderr
 
 ``--verbose``, ``-v``
-  be more verbose, print command before execute them
+  be more verbose, print command before execution
 
 ``--output-sync``, ``--no-output-sync``
   enable or disable output synchronization. By default output
diff --git a/rules/linux-firmware.in b/rules/linux-firmware.in
index b37d04781..2ed139106 100644
--- a/rules/linux-firmware.in
+++ b/rules/linux-firmware.in
@@ -12,7 +12,7 @@ config LINUX_FIRMWARE_SELECTED_LICENSES
 	string
 	prompt "Linux-firmware license files to include"
 	help
-	  Set the firmware license files use.
+	  Set the firmware license files to use.
 	  Since there is no strict match between firmware files
 	  and license files, this must be provided by the user.
 	  Multiple license files are separated by space.
diff --git a/rules/project-name.in b/rules/project-name.in
index de3379909..ff20d6fc5 100644
--- a/rules/project-name.in
+++ b/rules/project-name.in
@@ -109,7 +109,7 @@ choice
 	prompt "SOURCE_DATE_EPOCH timestamps source"
 	default REPRODUCIBLE_TIMESTAMP_PTXDIST
 	help
-	  Use the specifies source to provide a stable SOURCE_DATE_EPOCH.
+	  Use the specified source to provide a stable SOURCE_DATE_EPOCH.
 	  This helps making builds more reproducible. See
 	  https://reproducible-builds.org/specs/source-date-epoch/ for more
 	  details about SOURCE_DATE_EPOCH.
diff --git a/scripts/git-ptx-patches b/scripts/git-ptx-patches
index b27dbe790..ed9f9b069 100755
--- a/scripts/git-ptx-patches
+++ b/scripts/git-ptx-patches
@@ -6,7 +6,7 @@
 # behaviour or patch output.
 pristine_git() {
 	# Notes from the git(1) manpage:
-	# - GIT_DIFF_OPTS takes takes precedence over -U command line parameter
+	# - GIT_DIFF_OPTS takes precedence over -U command line parameter
 	HOME=/nonexistent \
 	XDG_CONFIG_HOME=/nonexistent \
 	GIT_CONFIG_NOSYSTEM=true \
-- 
2.34.1





             reply	other threads:[~2024-08-09  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  9:26 Markus Heidelberg [this message]
2024-09-12 12:11 ` [ptxdist] [APPLIED] " 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=20240809092639.47100-1-m.heidelberg@cab.de \
    --to=m.heidelberg@cab.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