All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Kit Dallege <xaum.io@gmail.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 3/3] docs: process: fix grammatical errors in 2.Process.rst
Date: Mon, 16 Mar 2026 07:43:45 -0600	[thread overview]
Message-ID: <871phjkhym.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260315170521.63794-4-xaum.io@gmail.com>

Kit Dallege <xaum.io@gmail.com> writes:

> Fix five minor grammatical issues:
> - Add comma after introductory phrase "At that point"
> - Add comma before conditional "if at all possible"
> - Change "close to ready" to "close to being ready"
> - Add article "a" before "more extensive review"
> - Add article "the" before "volume can reach"
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=214931
> Assisted-by: Claude:claude-opus-4-6
> Signed-off-by: Kit Dallege <xaum.io@gmail.com>
> ---
>  Documentation/process/2.Process.rst | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

Honestly, I don't see that any of these constitute an improvement to the
text.

Thanks,

jon

      reply	other threads:[~2026-03-16 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-15 17:05 [PATCH v2 0/3] docs: assorted documentation fixes Kit Dallege
2026-03-15 17:05 ` [PATCH v2 1/3] docs: kernel-doc: fix stale intel_audio.c path in examples Kit Dallege
2026-03-15 17:05 ` [PATCH v2 2/3] docs: sched-stats: fix misleading 'per-process' wording Kit Dallege
2026-03-16 13:44   ` Jonathan Corbet
2026-03-15 17:05 ` [PATCH v2 3/3] docs: process: fix grammatical errors in 2.Process.rst Kit Dallege
2026-03-16 13:43   ` 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=871phjkhym.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=xaum.io@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.