From: "ᴋᴀʀᴛɪᴋ sʜᴀʜ" <kartikpro9599@gmail.com>
To: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net, bagasdotme@gmail.com
Subject: [PATCH v5] docs: improve introduction wording in howto.rst
Date: Mon, 8 Dec 2025 22:00:20 +0530 [thread overview]
Message-ID: <CAOCmVvAWc2U95-bWTsjELSdsj7eOvNBM25Y934T-LNOKGcbqqg@mail.gmail.com> (raw)
From 22538f030fd806d0cdeccb6bdd6fcbc7f5a449e7 Mon Sep 17 00:00:00 2001
From: Kartik Shah <kartikpro9599@gmail.com>
Date: Sun, 7 Dec 2025 13:53:02 +0530
Subject: [PATCH v5] docs: improve introduction wording in howto.rst
The original introduction paragraph was overly long and repetitive.
This patch rewrites it to be clearer and more concise while keeping
the same meaning. It removes redundant phrasing such as "learn how to
become" and improves readability without changing the document's
intent.
Signed-off-by: Kartik Shah <kartikpro9599@gmail.com>
---
Documentation/process/howto.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
index 9438e03d6..dd840115f 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -3,11 +3,11 @@
HOWTO do Linux kernel development
=================================
-This is the be-all, end-all document on this topic. It contains
-instructions on how to become a Linux kernel developer and how to learn
-to work with the Linux kernel development community. It tries to not
-contain anything related to the technical aspects of kernel programming,
-but will help point you in the right direction for that.
+This is a complete introductory document on this topic. It
+contains instructions on how to become a Linux kernel developer
+and how to work with the Linux kernel development community. It
+does not cover the technical aspects of kernel programming, but
+will help point you in the right direction for that.
If anything in this document becomes out of date, please send in patches
to the maintainer of this file, who is listed at the bottom of the
--
2.52.0.windows.1
reply other threads:[~2025-12-08 16:30 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=CAOCmVvAWc2U95-bWTsjELSdsj7eOvNBM25Y934T-LNOKGcbqqg@mail.gmail.com \
--to=kartikpro9599@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).