From: Artem Bityutskiy <dedekind@infradead.org>
To: MikeW <mw_phil@yahoo.co.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Typos on website
Date: Wed, 28 Feb 2007 14:03:39 +0200 [thread overview]
Message-ID: <1172664219.17031.22.camel@sauron> (raw)
In-Reply-To: <loom.20070228T120913-895@post.gmane.org>
On Wed, 2007-02-28 at 11:23 +0000, MikeW wrote:
> Since I couldn't find a 'contacts' address on the linux-mtd website,
> I will post these here.
>
> "For example, many USB sticks and other cards *loose* data in case
> of unclean ...
> In them first and the third cases, you just *loose* the very last
> data you have ..."
> www.linux-mtd.infradead.org/faq/jffs2.html
>
> "If you have a power failure when the eraseblock is being erased, you *loose*
> all the block device sectors in it. The flash will likely decay..."
> www.linux-mtd.infradead.org/faq/general.html
>
> "But the drawback of this method is that you may *loose* messages
> due to the kernel ring buffer overflow as UBI may produce ..."
> "To avoid *loosing* messages, you may try to configure a serial ..."
> www.linux-mtd.infradead.org/faq/ubi.html
>
> "It makes sure that the risk of *loosing* the bad block table information
> is reduced to the loss of the information about ..."
> www.linux-mtd.infradead.org/tech/mtdnand/x144.html
>
> All "loose"->"lose", "loosing"->"losing"
>
>
> "page(s) where we find the bbt, used with option BBT_ABSPAGE when bbt is
> searched, then we store the found bbts pages here. *Its* an array and supports
> up ..."
> www.linux-mtd.infradead.org/tech/mtdnand/r804.html
>
> "Address lines based example. *Its* assumed that the nCE pins are connected
> to an address decoder. static void board_select_chip ..."
> www.linux-mtd.infradead.org/tech/mtdnand/c96.html
>
> "MTD device structure. ofs. offset from device start. getchip. 0,
> if the chip is already selected. allowbbt. 1, if *its* allowed to
> access the bbt area ..."
> www.linux-mtd.infradead.org/tech/mtdnand/r1637.html
>
> Each "its"->"it's" (= it is)
Most of them are mine, I will fix them, thanks.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-02-28 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 11:23 Typos on website MikeW
2007-02-28 12:03 ` Artem Bityutskiy [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=1172664219.17031.22.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mw_phil@yahoo.co.uk \
/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