public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <M.Heidelberg@cab.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: fix spelling, typos, grammar, duplicated words
Date: Mon, 29 Sep 2025 09:06:01 +0000	[thread overview]
Message-ID: <aNpL6DOVTu4mpL2L@KAN23-025> (raw)
In-Reply-To: <44f3bd7c-b32c-420e-a738-02f40853e472@infradead.org>

On Fri, Sep 26, 2025 at 10:36:28AM -0700, Randy Dunlap wrote:
> On 9/26/25 2:53 AM, Markus Heidelberg wrote:
> > Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
> > ---
> >  Documentation/bpf/prog_flow_dissector.rst  | 4 ++--
> >  Documentation/fb/fbcon.rst                 | 2 +-
> >  Documentation/filesystems/path-lookup.rst  | 2 +-
> >  Documentation/hwmon/lm75.rst               | 2 +-
> >  Documentation/kernel-hacking/hacking.rst   | 2 +-
> >  Documentation/networking/phy.rst           | 8 ++++----
> >  Documentation/process/management-style.rst | 2 +-
> >  7 files changed, 11 insertions(+), 11 deletions(-)
> 
> These changes mostly look good. I'm curious about how you
> found these. ??

Hi Randy,

I just stumbled upon them while reading the documentation.
The "the to -> to the" swap I originally found in another file and then
searched for more occurrences with something like this:

  $ git grep -w -C1 "the to"

Markus

      reply	other threads:[~2025-09-29  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26  9:53 [PATCH] Documentation: fix spelling, typos, grammar, duplicated words Markus Heidelberg
2025-09-26 12:32 ` Jonathan Corbet
2025-09-26 14:26   ` Markus Heidelberg
2025-09-26 17:36 ` Randy Dunlap
2025-09-29  9:06   ` Markus Heidelberg [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=aNpL6DOVTu4mpL2L@KAN23-025 \
    --to=m.heidelberg@cab.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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