From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] docs/manual: update intro, make gender-neutral
Date: Mon, 27 Jul 2026 15:10:17 -0400 (EDT) [thread overview]
Message-ID: <4c1871d0-8cf8-e749-7d65-232c16460a3d@crashcourse.ca> (raw)
Besides just updating a little terminology, remove the awkward
reference to "his" when referring to developers.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
just testing if this first patch passes examination.
diff --git a/docs/manual/introduction.adoc b/docs/manual/introduction.adoc
index 476aa81edc..1a8cc6d13e 100644
--- a/docs/manual/introduction.adoc
+++ b/docs/manual/introduction.adoc
@@ -16,11 +16,11 @@ filesystem with Buildroot).
Buildroot is useful mainly for people working with embedded systems.
Embedded systems often use processors that are not the regular x86
-processors everyone is used to having in his PC. They can be PowerPC
-processors, MIPS processors, ARM processors, etc.
+processors developers are used to having in their PCs, including
+ARM (both 32- and 64-bit), MIPS, PowerPC, RISC-V and more.
Buildroot supports numerous processors and their variants; it also
-comes with default configurations for several boards available
+comes with default configurations for hundreds of boards available
off-the-shelf. Besides this, a number of third-party projects are based on,
or develop their BSP footnote:[BSP: Board Support Package] or
SDK footnote:[SDK: Software Development Kit] on top of Buildroot.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2026-07-27 19:26 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=4c1871d0-8cf8-e749-7d65-232c16460a3d@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=buildroot@buildroot.org \
/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;
as well as URLs for NNTP newsgroup(s).