Web site: Some grammatical fixes for the FAQ General page.

Submitted by Robert P. J. Day on Feb. 9, 2010, 1:44 p.m.

Details

Message ID alpine.LFD.2.00.1002090844070.8655@localhost
State New, archived
Headers show

Commit Message

Robert P. J. Day Feb. 9, 2010, 1:44 p.m.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---



rday
--

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

            Linux Consulting, Training and Kernel Pedantry.

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

Comments

Artem Bityutskiy Feb. 16, 2010, 7:58 a.m.
On Tue, 2010-02-09 at 08:44 -0500, Robert P. J. Day wrote:
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> 
> ---
> 
> diff --git a/faq/general.xml b/faq/general.xml
> index 81ba994..1c0551f 100644
> --- a/faq/general.xml
> +++ b/faq/general.xml
> @@ -79,7 +79,7 @@ also block devices.</P>

Pushed, thanks you.

Patch hide | download patch | download mbox

diff --git a/faq/general.xml b/faq/general.xml
index 81ba994..1c0551f 100644
--- a/faq/general.xml
+++ b/faq/general.xml
@@ -79,7 +79,7 @@  also block devices.</P>

 <TABLE cellpadding="5" cellspacing="0" border="1">
 	<TR>
-		<TD><B>Block drives</B></TD>
+		<TD><B>Block device</B></TD>
 		<TD><B>MTD device</B></TD>
 	</TR>
 	<TR>
@@ -104,7 +104,7 @@  also block devices.</P>
 		<TD>
 			Bad sectors are re-mapped and hidden by hardware (at
 			least in modern LBA hard drives); in case of FTL
-			devices it is the resposibility of FTL to provide this
+			devices it is the responsibility of FTL to provide this
 		</TD>
 		<TD>
 			Bad eraseblocks are not hidden and should be dealt with
@@ -164,7 +164,7 @@  device nodes.

 <P>
 But in many cases using <CODE>mtdblock</CODE> is a very bad idea because what
-it basically does if you change any sector of you mtdblockX device, it reads
+it basically does if you change any sector of your mtdblockX device, it reads
 the whole corresponding eraseblock into the memory, erases the eraseblock,
 changes the sector in RAM, and writes the whole eraseblock back. This is very
 straightforward. If you have a power failure when the eraseblock is being
@@ -183,7 +183,7 @@  UBI.
 <P>
 It makes sense to use <CODE>mtdblock_ro</CODE> for read-only file systems or
 read-only mounts. For example, one may use SquashFS as it compresses data quite
-well. But think twice before using <CODE>mtdblock</CODE> in read-write more.
+well. But think twice before using <CODE>mtdblock</CODE> in read-write mode.
 And don't try to use it on NAND flash as it is does not handle bad
 eraseblocks.
 </P>