X-Git-Url: http://ftp.safe.ca/?a=blobdiff_plain;f=Documentation%2Fblock%2Fdata-integrity.txt;h=2d735b0ae383b625c87f37ed2603ec829adf6746;hb=61fd21670d048017c81e62f60894ef1b04b481db;hp=e8ca040ba2cff4bb5b938939f75c1bb97f0610af;hpb=e83c2b0ff325f52dda1aff3572d0e1516216c54b;p=safe%2Fjmp%2Flinux-2.6

diff --git a/Documentation/block/data-integrity.txt b/Documentation/block/data-integrity.txt
index e8ca040..2d735b0 100644
--- a/Documentation/block/data-integrity.txt
+++ b/Documentation/block/data-integrity.txt
@@ -50,7 +50,7 @@ encouraged them to allow separation of the data and integrity metadata
 scatter-gather lists.
 
 The controller will interleave the buffers on write and split them on
-read.  This means that the Linux can DMA the data buffers to and from
+read.  This means that Linux can DMA the data buffers to and from
 host memory without changes to the page cache.
 
 Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
@@ -66,7 +66,7 @@ software RAID5).
 
 The IP checksum is weaker than the CRC in terms of detecting bit
 errors.  However, the strength is really in the separation of the data
-buffers and the integrity metadata.  These two distinct buffers much
+buffers and the integrity metadata.  These two distinct buffers must
 match up for an I/O to complete.
 
 The separation of the data and integrity metadata buffers as well as