From: Brian Norris <computersforpeace@gmail.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: [PATCH] doc, faq: fix typos
Date: Fri, 21 Oct 2011 09:46:17 -0700 [thread overview]
Message-ID: <1319215577-30184-1-git-send-email-computersforpeace@gmail.com> (raw)
Fix spelling errors and a URL typo.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
doc/ubifs.xml | 2 +-
faq/nand.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ubifs.xml b/doc/ubifs.xml
index 9943508..bbe86f6 100644
--- a/doc/ubifs.xml
+++ b/doc/ubifs.xml
@@ -309,7 +309,7 @@ some specific aspects of MLC NAND flashes:</p>
<li>[<b>NEED WORK</b>] The "unstable bits issue", which is not
MLC-specific, described
- <a href="/ubifs.html#L_unstable_bits">here</a>.</li>
+ <a href="ubifs.html#L_unstable_bits">here</a>.</li>
</ul>
diff --git a/faq/nand.xml b/faq/nand.xml
index 9d9cd06..e142de8 100644
--- a/faq/nand.xml
+++ b/faq/nand.xml
@@ -186,7 +186,7 @@ Yes, you can. The requirements are the same as for boot-loaders
<P>
NAND simulator (<CODE>nandsim</CODE>) is an extremely useful debugging and
development tool which simulates NAND flashes in RAM or a file. To select the
-simulated flash type one should specify ID bytes of your flashe - the onese
+simulated flash type one should specify ID bytes of your flash - the ones
which are returned by the "Read ID" command (<CODE>0x90</CODE>) - consult the
flash manual. The following are examples of input parameters:
</P>
--
1.7.5.4
next reply other threads:[~2011-10-21 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 16:46 Brian Norris [this message]
2011-10-28 14:08 ` [PATCH] doc, faq: fix typos 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=1319215577-30184-1-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.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;
as well as URLs for NNTP newsgroup(s).