From: Jonathan Corbet <corbet@lwn.net>
To: Volodymyr Kot <volodymyr.kot.ua@gmail.com>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Volodymyr Kot <volodymyr.kot.ua@gmail.com>
Subject: Re: [PATCH] Doc: correct spelling and wording mistakes
Date: Tue, 06 Jan 2026 14:40:32 -0700 [thread overview]
Message-ID: <878qeae7xr.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251225133911.87512-1-volodymyr.kot.ua@gmail.com>
Volodymyr Kot <volodymyr.kot.ua@gmail.com> writes:
> Fixed capitalization and punctuation in process documentation.
>
> Signed-off-by: Volodymyr Kot <volodymyr.kot.ua@gmail.com>
> ---
> Documentation/process/1.Intro.rst | 2 +-
> Documentation/process/2.Process.rst | 2 +-
> Documentation/process/4.Coding.rst | 6 +++---
> Documentation/process/7.AdvancedTopics.rst | 2 +-
> 4 files changed, 6 insertions(+), 6 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2026-01-06 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 13:39 Volodymyr Kot
2026-01-06 21:40 ` Jonathan Corbet [this message]
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=878qeae7xr.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=volodymyr.kot.ua@gmail.com \
--cc=workflows@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