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 3/9] faq: general: turn statement into a question
Date: Mon, 8 Aug 2011 12:37:13 -0700	[thread overview]
Message-ID: <1312832239-21759-4-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1312832239-21759-1-git-send-email-computersforpeace@gmail.com>

This looks like a statement, yet it's in the Frequently Asked Questions.
We can fix that.

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

diff --git a/faq/general.xml b/faq/general.xml
index 2dc64b3..0336a32 100644
--- a/faq/general.xml
+++ b/faq/general.xml
@@ -18,7 +18,7 @@
 	<LI><A HREF="general.html#L_mtd_vs_hdd">What are the differences between flash devices and block drives?</A></LI>
 	<LI><A HREF="general.html#L_ext2_mtd">Can I mount ext2 over an MTD device?</A></LI>
 	<LI><A HREF="general.html#L_point">What are the point() and unpoint() functions used for?</A></LI>
-	<LI><A HREF="general.html#L_unlock">I keep getting errors whenever I try to write or erase to my MTD device</A></LI>
+	<LI><A HREF="general.html#L_unlock">Why do I keep getting errors whenever I try to write to or erase my MTD device?</A></LI>
 	<LI><A HREF="general.html#L_compile_mtd">How do I compile the mtd-utils tree?</A></LI>
 </OL>
 
@@ -221,7 +221,7 @@ release the chip again.
 
 
 <A NAME="L_unlock">
-<H2>I keep getting errors whenever I try to write or erase to my MTD device</H2>
+<H2>Why do I keep getting errors whenever I try to write to or erase my MTD device?</H2>
 </A>
 
 <P>
-- 
1.7.0.4

  parent reply	other threads:[~2011-08-08 19:38 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 ` [PATCH 1/9] UBIFS FAQ: spelling, grammar Brian Norris
2011-08-08 19:37 ` [PATCH 2/9] faq: general: update "pleonasm" description Brian Norris
2011-08-08 19:37 ` Brian Norris [this message]
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-4-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