Yocto Project Documentation
 help / color / mirror / Atom feed
From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH] ref-manual: fix some repeated strings
Date: Fri, 10 Jul 2026 10:57:59 +0200	[thread overview]
Message-ID: <20260710-repeated-strings-v1-1-e170bab49db3@bootlin.com> (raw)

Grepped with git grep --extended-regexp " ([a-zA-Z]+)\s\1 ".

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/classes.rst             | 2 +-
 documentation/ref-manual/system-requirements.rst | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index f826bbdbc..ae0f771c9 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -560,7 +560,7 @@ as well as in ``tmp/deploy/spdx``.
 
 The exact behaviour of this class, and the amount of output can be controlled
 by the :term:`SPDX_PRETTY`, :term:`SPDX_INCLUDE_SOURCES` and other variables
-starting with with ``SPDX_``.
+starting with ``SPDX_``.
 
 See the description of these variables and the
 ":ref:`dev-manual/sbom:creating a software bill of materials`"
diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
index 63291cae3..8317452b2 100644
--- a/documentation/ref-manual/system-requirements.rst
+++ b/documentation/ref-manual/system-requirements.rst
@@ -514,7 +514,7 @@ installer and automatically installs the tools for you:
 
    After you have sourced the setup script, the tools are added to
    ``PATH`` and any other environment variables required to run the
-   tools are initialized. The results are working versions versions of
+   tools are initialized. The results are working versions of
    Git, tar, Python and ``chrpath``. And in the case of the
    :term:`buildtools-extended` tarball, additional working versions of tools
    including ``gcc``, ``make`` and the other tools included in
@@ -555,7 +555,7 @@ steps:
 
    After you have sourced the setup script, the tools are added to
    ``PATH`` and any other environment variables required to run the
-   tools are initialized. The results are working versions versions of
+   tools are initialized. The results are working versions of
    Git, tar, Python and ``chrpath``. And in the case of the
    :term:`buildtools-extended` tarball, additional working versions of tools
    including ``gcc``, ``make`` and the other tools included in
@@ -626,7 +626,7 @@ installer:
 
    After you have sourced the setup script, the tools are added to
    ``PATH`` and any other environment variables required to run the
-   tools are initialized. The results are working versions versions of
+   tools are initialized. The results are working versions of
    Git, tar, Python and ``chrpath``. And in the case of the
    :term:`buildtools-extended` tarball, additional working versions of tools
    including ``gcc``, ``make`` and the other tools included in

---
base-commit: 0cd9c643c0185c60eb9aae90fe48c3597b1781d6
change-id: 20260710-repeated-strings-8eb8f8baf911



                 reply	other threads:[~2026-07-10  8:58 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=20260710-repeated-strings-v1-1-e170bab49db3@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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