public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian Norris" <computersforpeace@gmail.com>
To: "Artem Bityutskiy" <dedekind1@gmail.com>
Cc: brian.foster@maxim-ic.com,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org
Subject: [PATCH 1/9] UBIFS FAQ: spelling, grammar
Date: Mon, 8 Aug 2011 12:37:11 -0700	[thread overview]
Message-ID: <1312832239-21759-2-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1312832239-21759-1-git-send-email-computersforpeace@gmail.com>

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
 faq/ubifs.xml |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/faq/ubifs.xml b/faq/ubifs.xml
index bd91733..f70c222 100644
--- a/faq/ubifs.xml
+++ b/faq/ubifs.xml
@@ -77,9 +77,9 @@ some specific aspects of MLC NAND flashes:</p>
 	this is also not a problem because it is exactly what UBI and UBIFS do
 	(see also <a href="ubi.html#L_restrict">this</a> section);</li>
 
-	<li>MLC flashes have rather short eraseblock life-cycle of just few
-	thousand of erase cycles; and this is not a problem, because UBI
-	uses deterministic wear-leveling algorithm
+	<li>MLC flashes have rather short eraseblock life-cycles of just a few
+	thousand erase cycles; this is not a problem because UBI uses a
+	deterministic wear-leveling algorithm
 	(see <a href="ubi.html#L_mlc">this</a> section);</li>
 
 	<li>MLC flashes exhibit bit flips as a result of "program disturb" and
@@ -1229,7 +1229,7 @@ The ways to solve this:
 	<li>Use <code>ubiformat</code> and format the NOR partition before
 	attaching it to UBI. But this will not help in situations when you
 	delete may files, and starts erasing many eraseblocks, so the "MTD/CFI
-	chip lock" becomes very condtended.</li>
+	chip lock" becomes very contended.</li>
 	<li>Use erase-suspend for writing (if your chip supports this).</li>
 </ol>
 </p>
-- 
1.7.0.4

  reply	other threads:[~2011-08-08 19:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 19:37 [PATCH 0/9] mtd-www: various fixes, bug reporting info Brian Norris
2011-08-08 19:37 ` Brian Norris [this message]
2011-08-08 19:37 ` [PATCH 2/9] faq: general: update "pleonasm" description Brian Norris
2011-08-08 19:37 ` [PATCH 3/9] faq: general: turn statement into a question Brian Norris
2011-08-08 19:37 ` [PATCH 4/9] faq/doc: ubi(fs): move "bug report" questions to FAQ Brian Norris
2011-08-08 19:37 ` [PATCH 5/9] doc: nand: update YAFFS URL Brian Norris
2011-08-08 19:37 ` [PATCH 6/9] doc: update info on compiling mtd-utils Brian Norris
2011-08-08 19:37 ` [PATCH 7/9] faq: ubi(fs): sending bug reports using `mtdinfo' Brian Norris
2011-08-09 22:03   ` [PATCH v2 " Brian Norris
2011-08-08 19:37 ` [PATCH 8/9] faq: ubi(fs): small spelling, URL fixups Brian Norris
2011-08-09 22:05   ` [PATCH v2 " Brian Norris
2011-08-08 19:37 ` [PATCH 9/9] faq: general: add bug reporting FAQ Brian Norris
2011-08-09  8:10   ` Brian Foster
2011-08-09 22:05   ` [PATCH v2 " Brian Norris
2011-08-10  7:54     ` Brian Foster
2011-08-10  8:34       ` [PATCH " Brian Norris
2011-08-08 20:00 ` [PATCH 0/9] mtd-www: various fixes, bug reporting info Artem Bityutskiy
2011-08-15 12:19 ` Artem Bityutskiy

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=1312832239-21759-2-git-send-email-computersforpeace@gmail.com \
    --to=computersforpeace@gmail.com \
    --cc=brian.foster@maxim-ic.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.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