mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 18-rc1] Fix typos in /Documentation : 'A'
Date: Mon, 10 Jul 2006 19:12:18 -0700	[thread overview]
Message-ID: <20060710191218.d8ea2b6c.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060710210755.abb2af5d.kernel1@cyberdogtech.com>

On Mon, 10 Jul 2006 21:07:55 -0400 Matt LaPlante wrote:

> On Mon, 10 Jul 2006 10:34:33 -0700
> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> 
> > On Mon, 10 Jul 2006 13:05:49 -0400 Matt LaPlante wrote:
> > 
> > > This patch fixes typos in various Documentation txts. This patch addresses some words starting with the letter 'A'.
> > > 
> > > Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
> > 
> > Hi,
> > Looks mostly good.  I think it would be OK to fix other typos
> > on the same lines as the patches... see below.
> 
> The updated patch below fixes two of the three issues you mentioned.  I don't know what you'd want done with the dead URL, that file doesn't have a whole lot else in it, and I don’t know what the new URL would be.  
> 
> I agree fixing other typos is a worthy cause, though currently I haven't really made any changes other than spelling for a couple reasons:
> 
> 1- I'm detecting the spelling errors by scripting with aspell and custom wordlists.  This method doesn't reveal grammatical errors often, and I'm not reading much of the actual documents except to get context for the spelling errors.  (I _am_ making all changes manually, not scripting the actual corrections).
> 
> 2- Spelling errors are really hard to dispute (except for some nationality issues)...things are either spelled wrong or right.  I would be more hesitant to change actual grammar where I could also unwittingly change the meaning of a technical document (which I often don't have indepth knowledge of to begin with).
> 
> I'll certainly be willing to more thoroughly read through and correct the docs later on (and I'm sure I could learn quite a bit in the process).  I thought this round of tackling the most obvious errors assisted by scripting would be a good way to get acquainted with the patching process.

OK, thanks.

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

---
~Randy

  reply	other threads:[~2006-07-11  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 17:05 Matt LaPlante
2006-07-10 17:34 ` Randy.Dunlap
2006-07-11  1:07   ` Matt LaPlante
2006-07-11  2:12     ` Randy.Dunlap [this message]
2006-07-10 17:35 ` Alan Cox

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=20060710191218.d8ea2b6c.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=kernel1@cyberdogtech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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

all inboxes | Powered by JetHome®