linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: [PATCH] Web site:  A few grammatical fixes in Docs/General.
Date: Tue, 9 Feb 2010 06:34:13 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1002090631540.6317@localhost> (raw)


Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

  in addition to a few picky fixes on that page, toward the bottom of
that page, one reads:

"This is wrong in most cases. The mtdblock In other words, please, do
                                          ^^^ ???
not use mtdblock unless you know exactly what you are doing.

  there seems to be something missing there, i'll leave it to people
higher up the food chain to decide what to do there.


diff --git a/doc/general.xml b/doc/general.xml
index 8368b2e..14ba8ff 100644
--- a/doc/general.xml
+++ b/doc/general.xml
@@ -30,7 +30,7 @@ AG-AND, ECC'd NOR, etc.</p>
 <p>MTD subsystem does not deal with block devices like MMC, eMMC, SD,
 CompactFlash, etc. These devices are not raw flashes but they have a Flash
 Translation layer inside, which makes them look like block devices. These
-devices are subject of the Linux block subsystem, not MTD. Please, refer
+devices are the subject of the Linux block subsystem, not MTD. Please, refer to
 <a href="../faq/general.html#L_mtd_vs_hdd">this</a> FAQ section for a short
 list of the main differences between block and MTD devices. And the
 <a href="ubifs.html#L_raw_vs_ftl">raw flash vs. FTL devices</a> UBIFS section
@@ -46,15 +46,15 @@ discusses this in more details.</p>
 	them as bad or checking if an eraseblock is bad, getting information
 	about MTD devices, etc.</li>

-	<li>The <code>sysfs</code> interface is relatively and it provides full
-	information about each MTD device in the system. This interface is
+	<li>The <code>sysfs</code> interface is relatively newer and it provides
+	full information about each MTD device in the system. This interface is
 	easily extensible and developers are encouraged to use the
 	<code>sysfs</code> interface instead of older <code>ioctl</code> or
 	<code>/proc/mtd</code> interfaces, when possible.</li>

 	<li>The <code>/proc/mtd</code> proc file system file provides general
 	MTD information. This is a legacy interface and the sysfs interface
-	provide more information.</li>
+	provides more information.</li>
 </ul>

 <p>MTD subsystem supports bare <a href="nand.html">NAND</a> flashes with
@@ -77,7 +77,7 @@ starting from kernel version <code>2.6.29</code> and they live in the
 <code>drivers/mtd/tests</code> directory of the linux kernel source codes. You
 may compile the tests as kernel modules by enabling them in the kernel
 configuration menu by marking: "<b>Device Drivers</b>" ->
-"<b>Memory Technology Devices (MTD)</b>" -> "<b>MTD tests support</b>" (or
+"<b>Memory Technology Device (MTD) support</b>" -> "<b>MTD tests support</b>" (or
 the <code>MTD_TESTS</code> symbol in the <code>.config</code> file).</p>

 <p>If you have a pre-<code>2.6.29</code> kernel, you may find the tests


rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

             reply	other threads:[~2010-02-09 11:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 11:34 Robert P. J. Day [this message]
2010-02-15 20:27 ` [PATCH] Web site: A few grammatical fixes in Docs/General 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=alpine.LFD.2.00.1002090631540.6317@localhost \
    --to=rpjday@crashcourse.ca \
    --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).