From: Matt LaPlante <kernel1@cyberdogtech.com>
To: "David Rientjes" <rientjes@google.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 18-rc2] Fix typos in /Documentation : 'F'-'G'
Date: Mon, 24 Jul 2006 01:31:20 -0400 [thread overview]
Message-ID: <20060724013120.dc71ab61.kernel1@cyberdogtech.com> (raw)
In-Reply-To: <9ec263480607232144g5e283156p86e5f84e8a92380c@mail.google.com>
On Sun, 23 Jul 2006 21:44:49 -0700
"David Rientjes" <rientjes@google.com> wrote:
> On 7/23/06, Matt LaPlante <kernel1@cyberdogtech.com> wrote:
> > --- a/Documentation/input/ff.txt 2006-07-22 15:09:50.000000000 -0400
> > +++ b/Documentation/input/ff.txt 2006-07-22 17:07:10.000000000 -0400
> > @@ -13,7 +13,7 @@
> > At the moment, only I-Force devices are supported, and not officially. That
> > means I had to find out how the protocol works on my own. Of course, the
> > information I managed to grasp is far from being complete, and I can not
> > -guarranty that this driver will work for you.
> > +guaranty that this driver will work for you.
> > This document only describes the force feedback part of the driver for I-Force
> > devices. Please read joystick.txt before reading further this document.
> >
>
> guaranty?
It does look weird, although apparently it is not incorrect:
http://www.m-w.com/dictionary/guaranty
Generally speaking I've been trying to change as little as possible to achieve correctness...if we want to declare "guarantee" the official spelling for the kernel, theres no reason not to change this one too. :)
--
Matt LaPlante
CCNP, CCDP, A+, Linux+, CQS
kernel1@cyberdogtech.com
next prev parent reply other threads:[~2006-07-24 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 16:49 [PATCH 18-rc2] Fix typos in /Documentation : 'F'-'G' Matt LaPlante
2006-07-24 4:44 ` David Rientjes
2006-07-24 5:31 ` Matt LaPlante [this message]
2006-07-24 6:23 ` Adam Henley
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=20060724013120.dc71ab61.kernel1@cyberdogtech.com \
--to=kernel1@cyberdogtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--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