Merge git://git.infradead.org/battery-2.6

[pandora-kernel.git] / Documentation / scsi / aic7xxx_old.txt

diff --git a/Documentation/scsi/aic7xxx_old.txt b/Documentation/scsi/aic7xxx_old.txt
index 433e942..7bd210a 100644 (file)
--- a/Documentation/scsi/aic7xxx_old.txt
+++ b/Documentation/scsi/aic7xxx_old.txt
@@ -102,7 +102,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
     The hardware RAID devices sold by Adaptec are *NOT* supported by this
     driver (and will people please stop emailing me about them, they are
     a totally separate beast from the bare SCSI controllers and this driver
-    can not be retrofitted in any sane manner to support the hardware RAID
+    cannot be retrofitted in any sane manner to support the hardware RAID
     features on those cards - Doug Ledford).
     
 
@@ -241,7 +241,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
         that instead of dumping the register contents on the card, this
        option dumps the contents of the sequencer program RAM.  This gives
        the ability to verify that the instructions downloaded to the
-       card's sequencer are indeed what they are suppossed to be.  Again,
+       card's sequencer are indeed what they are supposed to be.  Again,
        unless you have documentation to tell you how to interpret these
        numbers, then it is totally useless.
        
@@ -256,7 +256,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
              En/Disable High Byte LVD Termination
 
        The upper 2 bits that deal with LVD termination only apply to Ultra2
-       controllers.  Futhermore, due to the current Ultra2 controller
+       controllers.  Furthermore, due to the current Ultra2 controller
        designs, these bits are tied together such that setting either bit
        enables both low and high byte LVD termination.  It is not possible
        to only set high or low byte LVD termination in this manner.  This is
@@ -356,7 +356,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
         or enable Tagged Command Queueing (TCQ) on specific devices.  As of
        driver version 5.1.11, TCQ is now either on or off by default
        according to the setting you choose during the make config process.
-       In order to en/disable TCQ for certian devices at boot time, a user
+       In order to en/disable TCQ for certain devices at boot time, a user
        may use this boot param.  The driver will then parse this message out
         and en/disable the specific device entries that are present based upon
         the value given.  The param line is parsed in the following manner:
@@ -436,7 +436,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
     the commas to periods, insmod won't interpret this as more than one
     string and write junk into our binary image.  I consider it a bug in
     the insmod program that even if you wrap your string in quotes (quotes
-    that pass the shell mind you and that insmod sees) it still treates
+    that pass the shell mind you and that insmod sees) it still treats
     a comma inside of those quotes as starting a new variable, resulting
     in memory scribbles if you don't switch the commas to periods.