From: Nguyen Duc Thinh <ducthinh100812@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Weijie Yuan <wy@wyuan.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nguyen Duc Thinh <ducthinh100812@gmail.com>
Subject: [PATCH 0/5] Documentation: process: Clean up grammar, tone,
Date: Wed, 2 Sep 2026 15:35:40 +0700 [thread overview]
Message-ID: <20260902083541.15555-1-ducthinh100812@gmail.com> (raw)
This patch series performs a thorough pass across several files
in the Linux kernel process documentation directory. The primary focus
is to improve readability and maintain a professional tone throughout
the guides for a global developer audience.
Core changes include:
- Expanding conversational contractions (e.g., "don't" to "do not").
- Rectifying minor punctuation oversights and grammatical typos.
- Standardizing terminology formatting to elevate professional voice.
Extra notes:
- I originally intended to send a 12-patch series to cover the whole
directory, but decided to scale it back to these 5 high-quality
patches to ensure thorough accuracy and a manageable review cycle.
Also I want to know the current progress of the patch titled
"Capitalize Git, Quilt, and Mercurial consistently".
And I would like to thank everyone for welcoming me to the community
and I hope everyone can forgive me for my mistakes in the past,
present, and in the future.
Nguyen Duc Thinh (5):
Documentation: process: Clean up grammar, tone, and contractions in
core files
Documentation: process: Clean up grammar and tone in next guide files
Documentation: process: Refine language, tone, and grammar in
subsequent files
Documentation: process: Refine language, tone, and grammar in
subsequent files
Documentation: process: Clean up grammar and tone across multiple
files
Documentation/process/1.Intro.rst | 18 ++---
Documentation/process/2.Process.rst | 22 +++---
Documentation/process/3.Early-stage.rst | 14 ++--
Documentation/process/4.Coding.rst | 48 ++++++-------
Documentation/process/5.Posting.rst | 34 +++++-----
Documentation/process/6.Followthrough.rst | 16 ++---
Documentation/process/7.AdvancedTopics.rst | 32 ++++-----
Documentation/process/8.Conclusion.rst | 4 +-
Documentation/process/applying-patches.rst | 20 +++---
Documentation/process/backporting.rst | 68 +++++++++----------
Documentation/process/botching-up-ioctls.rst | 54 +++++++--------
Documentation/process/changes.rst | 20 +++---
.../code-of-conduct-interpretation.rst | 14 ++--
Documentation/process/code-of-conduct.rst | 2 +-
Documentation/process/coding-assistants.rst | 12 ++--
Documentation/process/conclave.rst | 6 +-
.../process/contribution-maturity-model.rst | 4 +-
Documentation/process/cve.rst | 8 +--
Documentation/process/deprecated.rst | 14 ++--
Documentation/process/development-process.rst | 6 +-
Documentation/process/email-clients.rst | 32 ++++-----
21 files changed, 224 insertions(+), 224 deletions(-)
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-09-02 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 8:35 Nguyen Duc Thinh [this message]
2026-09-02 8:35 ` [PATCH 1/5] Documentation: process: Clean up grammar, tone, and contractions in core files Nguyen Duc Thinh
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=20260902083541.15555-1-ducthinh100812@gmail.com \
--to=ducthinh100812@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
--cc=wy@wyuan.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