mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manuel Ebner <manuelebnerli@mailbox.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: Manuel Ebner <manuelebnerli@mailbox.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] docs: doc-guide: improve language
Date: Sun, 15 Nov 2026 22:04:23 +0100	[thread overview]
Message-ID: <20261115210423.1089716-2-manuelebnerli@mailbox.org> (raw)

There is no 'kernel process' thus change to 'kernel contribution process'.

Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
---
 Documentation/doc-guide/contributing.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/doc-guide/contributing.rst b/Documentation/doc-guide/contributing.rst
index f8047e6331..0f0804f82d 100644
--- a/Documentation/doc-guide/contributing.rst
+++ b/Documentation/doc-guide/contributing.rst
@@ -14,10 +14,10 @@ it needs to be to support a project of this size and importance.
 
 This guide is for contributors who would like to improve that situation.
 Kernel documentation improvements can be made by developers at a variety of
-skill levels; they are a relatively easy way to learn the kernel process in
-general and find a place in the community.  The bulk of what follows is the
-documentation maintainer's list of tasks that most urgently need to be
-done.
+skill levels; they are a relatively easy way to learn the kernel contribution
+process in general and find a place in the community.  The bulk of what
+follows is the documentation maintainer's list of tasks that most urgently
+need to be done.
 
 The documentation TODO list
 ---------------------------
-- 
2.56.0


             reply	other threads:[~2026-11-15 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 21:04 Manuel Ebner [this message]
2026-11-15 23:27 ` Bagas Sanjaya

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=20261115210423.1089716-2-manuelebnerli@mailbox.org \
    --to=manuelebnerli@mailbox.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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

all inboxes | Powered by JetHome®