Linux Documentation
 help / color / mirror / Atom feed
From: Brigham Campbell <me@brighamcampbell.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org (open list:DOCUMENTATION REPORTING
	ISSUES), linux-kernel@vger.kernel.org (open list)
Cc: Brigham Campbell <me@brighamcampbell.com>
Subject: [PATCH 1/1] docs: Fix minor grammatical error
Date: Thu,  4 Jun 2026 23:38:26 -0600	[thread overview]
Message-ID: <20260605053826.7836-1-me@brighamcampbell.com> (raw)

Fix minor grammatical error in the admin guide docs.

Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
---

I happened across this minor mistake while investigating techniques to
use a partial kernel config to generate a complete config. If
maintainers that I don't send out minor fixes like this, please let me
know and I'll remember that for the future.

 Documentation/admin-guide/quickly-build-trimmed-linux.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/admin-guide/quickly-build-trimmed-linux.rst b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
index cb178e0a6208..194d22f56449 100644
--- a/Documentation/admin-guide/quickly-build-trimmed-linux.rst
+++ b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
@@ -217,10 +217,10 @@ again.
 
    There is a catch: 'localmodconfig' is likely to disable kernel features you
    did not use since you booted your Linux -- like drivers for currently
-   disconnected peripherals or a virtualization software not haven't used yet.
-   You can reduce or nearly eliminate that risk with tricks the reference
-   section outlines; but when building a kernel just for quick testing purposes
-   it is often negligible if such features are missing. But you should keep that
+   disconnected peripherals or virtualization software not currently in use. You
+   can reduce or nearly eliminate that risk with tricks the reference section
+   outlines; but when building a kernel just for quick testing purposes it is
+   often negligible if such features are missing. But you should keep that
    aspect in mind when using a kernel built with this make target, as it might
    be the reason why something you only use occasionally stopped working.
 
-- 
2.54.0


             reply	other threads:[~2026-06-05  5:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  5:38 Brigham Campbell [this message]
2026-06-06 19:10 ` [PATCH 1/1] docs: Fix minor grammatical error Randy Dunlap
2026-06-09  5:50   ` Brigham Campbell
2026-06-09  6:15     ` Thorsten Leemhuis

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=20260605053826.7836-1-me@brighamcampbell.com \
    --to=me@brighamcampbell.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=skhan@linuxfoundation.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