Import 2.4.0-test6pre1

CREDITS

@@ -1071,15 +1071,11 @@ D: Berkshire PC Watchdog Driver
 D: Small/Industrial Driver Project
 
 N: Nick Holloway
-E: Nick.Holloway@alfie.demon.co.uk
-E: Nick.Holloway@parallax.co.uk
-W: http://www.alfie.demon.co.uk/
-P: 1024/75C49395 3A F0 E3 4E B7 9F E0 7E  47 A3 B0 D5 68 6A C2 FB
+E: Nick.Holloway@pyrites.org.uk
+W: http://www.pyrites.org.uk/
+P: 1024/36115A04 F4E1 3384 FCFD C055 15D6  BA4C AB03 FBF8 3611 5A04
 D: Occasional Linux hacker...
-S: 15 Duke Street
-S: Chapelfields
-S: Coventry
-S: CV5 8BZ
+S: (ask for current address)
 S: United Kingdom
 
 N: Ron Holt
@@ -1556,6 +1552,12 @@ S: 8786 Niwot Road
 S: Niwot, Colorado 80503
 S: USA
 
+N: Robert M. Love
+E: rml@tech9.net
+E: rml@ufl.edu
+D: misc. kernel hacking and debugging
+S: FL, USA
+
 N: Martin von Lwis
 E: loewis@informatik.hu-berlin.de
 D: script binary format

Documentation/DMA-mapping.txt

@@ -111,7 +111,7 @@ There are two types of DMA mappings:
 
 - Consistent DMA mappings which are usually mapped at driver
   initialization, unmapped at the end and for which the hardware should
-  guarentee that the device and the cpu can access the data
+  guarantee that the device and the cpu can access the data
   in parallel and will see updates made by each other without any
   explicit software flushing.
 
@@ -126,7 +126,7 @@ There are two types of DMA mappings:
 
   The invariant these examples all require is that any cpu store
   to memory is immediately visible to the device, and vice
-  versa.  Consistent mappings guarentee this.
+  versa.  Consistent mappings guarantee this.
 
 - Streaming DMA mappings which are usually mapped for one DMA transfer,
   unmapped right after it (unless you use pci_dma_sync below) and for which
@@ -171,9 +171,9 @@ it from the CPU and dma_handle which you pass to the card.
 The cpu return address and the DMA bus master address are both
 guaranteed to be aligned to the smallest PAGE_SIZE order which
 is greater than or equal to the requested size.  This invariant
-exists (for example) to guarentee that if you allocate a chunk
+exists (for example) to guarantee that if you allocate a chunk
 which is smaller than or equal to 64 kilobytes, the extent of the
-buffer you receive will not cross a 64K boundry.
+buffer you receive will not cross a 64K boundary.
 
 To unmap and free such a DMA region, you call:
 
@@ -203,7 +203,7 @@ as you possibly can.
 
 If you absolutely cannot know the direction of the DMA transfer,
 specify PCI_DMA_BIDIRECTIONAL.  It means that the DMA can go in
-either direction.  The platform guarentees that you may legally
+either direction.  The platform guarantees that you may legally
 specify this, and that it will work, but this may be at the
 cost of performance for example.
 

Documentation/IO-mapping.txt

@@ -176,7 +176,7 @@ ioremap() function "vremap()".  ioremap() is the proper name, but I
 didn't think straight when I wrote it originally.  People who have to
 support both can do something like:
  
-	/* support old naming sillyness */
+	/* support old naming silliness */
 	#if LINUX_VERSION_CODE < 0x020100                                     
 	#define ioremap vremap
 	#define iounmap vfree                                                     

Documentation/arm/SA1100/ThinClient

@@ -10,7 +10,7 @@ Current Linux support for this product has been provided by Nicolas Pitre
 <nico@cam.org>.
 
 It's currently possible to mount a root filesystem via NFS providing a
-complete Linux environment.  Otherwyse a ramdisk image may be used.  Use
+complete Linux environment.  Otherwise a ramdisk image may be used.  Use
 'make thinclient_config' before any 'make config'.  This will set up
 defaults for ThinClient support.
 

Documentation/arm/empeg/ir.txt

@@ -17,7 +17,7 @@ For each of the 32 bits
   Go low for less than 2T (Around 750us)
 
 Rather than repeat a signal when the button is held down certain buttons
-generate the following code to indicate repitition.
+generate the following code to indicate repetition.
 
 Go low for approx 16T
 Go high for approx 4T

Documentation/arm/nwfpe/README

@@ -15,7 +15,7 @@ have attempted to use the C_SYMBOL_NAME macro wherever this may be
 important.
 
 Another choice I made was in the file structure.  I have attempted to
-contain all operating system specfic code in one module (fpmodule.*).
+contain all operating system specific code in one module (fpmodule.*).
 All the other files contain emulator specific code.  This should allow
 others to port the emulator to NetBSD for instance relatively easily.
 

Documentation/cdrom/cdrom-standard.tex

@@ -919,7 +919,7 @@ the current flags.
   than fixing this interface by changing the assumptions it was made
   under, thereby breaking all user applications that use this
   function, the \UCD\ implements this $ioctl$ as follows: If the CD in
-  question has audio tracks on it, and it has absolutly no CD-I, XA,
+  question has audio tracks on it, and it has absolutely no CD-I, XA,
   or data tracks on it, it will be reported as $CDS_AUDIO$.  If it has
   both audio and data tracks, it will return $CDS_MIXED$.  If there
   are no audio tracks on the disc, and if the CD in question has any

Documentation/cdrom/ide-cd

@@ -286,7 +286,7 @@ b. Timeout/IRQ errors.
     Unfortunately, these drives seem to become very confused when we perform
     the standard Linux ATA disk drive probe. If you own one of these drives,
     you can bypass the ATA probing which confuses these CDROM drives, by 
-    adding `append="hdX=noprobe hdX=cdrom"' to your lilo.conf file and runing 
+    adding `append="hdX=noprobe hdX=cdrom"' to your lilo.conf file and running 
     lilo (again where X is the drive letter corresponding to where your drive 
     is installed.)
     

Documentation/computone.txt

@@ -93,7 +93,7 @@ Previously, the driver sources were packaged with a set of patch files
 to update the character drivers' makefile and configuration file, and other 
 kernel source files. A build script (ip2build) was included which applies 
 the patches if needed, and build any utilities needed.
-What you recieve may be a single patch file in conventional kernel
+What you receive may be a single patch file in conventional kernel
 patch format build script. That form can also be applied by
 running patch -p1 < ThePatchFile.  Otherwise run ip2build.
  
@@ -191,7 +191,7 @@ Higher speeds can be obtained using the setserial utility which remaps
 Intelliport II installations using the PowerPort expansion module can
 use the custom speed setting to select the highest speeds: 153,600 bps,
 230,400 bps, 307,200 bps, 460,800bps and 921,600 bps. The base for
-custom baud rate configuration is fixed at 921,600 for cards/expantion
+custom baud rate configuration is fixed at 921,600 for cards/expansion
 modules with ST654's and 115200 for those with Cirrus CD1400's.  This
 corresponds to the maximum bit rates those chips are capable.  
 For example if the baud base is 921600 and the baud divisor is 18 then
@@ -220,13 +220,13 @@ DEVFS is the DEVice File System available as an add on package for the
 2.2.x kernels and available as a configuration option in 2.3.46 and higher.
 Devfs allows for the automatic creation and management of device names
 under control of the device drivers themselves.  The Devfs namespace is
-hierarchial and reduces the clutter present in the normal flat /dev
+hierarchical and reduces the clutter present in the normal flat /dev
 namespace.  Devfs names and conventional device names may be intermixed.
 A userspace daemon, devfsd, exists to allow for automatic creation and
 management of symbolic links from the devfs name space to the conventional
 names.  More details on devfs can be found on the DEVFS home site at
 <http://www.atnf.csiro.au/~rgooch/linux/> or in the file kernel
-documenation files, .../linux/Documenation/filesystems/devfs/REAME.
+documentation files, .../linux/Documentation/filesystems/devfs/REAME.
 
 If you are using devfs, existing devices are automatically created within
 the devfs name space.  Normal devices will be ttf/0 - ttf/255 and callout

Documentation/cpqarray.txt

-This driver is for Compaq's SMART2 Intellegent Disk Array Controllers.
+This driver is for Compaq's SMART2 Intelligent Disk Array Controllers.
 
 Supported Cards:
 ----------------

Documentation/fb/aty128fb.txt

@@ -66,7 +66,7 @@ Limitations
 There are known and unknown bugs, features and misfeatures.
 Currently there are following known bugs:
  + This driver is still experimental and is not finished.  Too many
-   bugs/eratta to list here.
+   bugs/errata to list here.
 
 --
 Brad Douglas <brad@neruo.com>

Documentation/fb/matroxfb.txt

@@ -193,7 +193,7 @@ nocross4MB - pixel line must not cross 4MB boundary. It is default for
 	     XF86_FBDev.
 dfp      - enables digital flat panel interface. This option is incompatible with
            secondary (TV) output - if DFP is active, TV output must be
-	   inactive and vice versa. DFP always uses same timming as primary
+	   inactive and vice versa. DFP always uses same timing as primary
 	   (monitor) output.
 vesa:X   - selects startup videomode. X is number from 0 to 0x1FF, see table
            above for detailed explanation. Default is 640x480x8bpp if driver

Documentation/fb/vesafb.txt

@@ -62,7 +62,7 @@ So the table for the Kernel mode numbers are:
 16M |  0x312    0x315    0x318    0x31B   
 
 To enable one of those modes you have to specify "vga=ask" in the
-lilo.conf file and rerun LILO. Then you can type in the descired
+lilo.conf file and rerun LILO. Then you can type in the desired
 mode at the "vga=ask" prompt. For example if you like to use 
 1024x768x256 colors you have to say "305" at this prompt.
 

Documentation/filesystems/Locking

@@ -137,7 +137,7 @@ bmap:		yes
 may be called from the request handler (/dev/loop).
 	->sync_page() locking rules are not well-defined - usually it is called
 with lock on page, but that is not guaranteed. Considering the currently
-existsing instances of this method ->sync_page() itself doesn't look
+existing instances of this method ->sync_page() itself doesn't look
 well-defined...
 	->bmap() is currently used by legacy ioctl() (FIBMAP) provided by some
 filesystems and by the swapper. The latter will eventually go away. All

Documentation/filesystems/affs.txt

@@ -158,7 +158,7 @@ If you boot Windows 95 (don't know about 3.x, 98 and NT) while you
 have an Amiga harddisk connected to your PC, it will overwrite
 the bytes 0x00dc..0x00df of block 0 with garbage, thus invalidating
 the Rigid Disk Block. Sheer luck has it that this is an unused
-area of the RDB, so only the checksum doesn's match anymore.
+area of the RDB, so only the checksum doesn't match anymore.
 Linux will ignore this garbage and recognize the RDB anyway, but
 before you connect that drive to your Amiga again, you must
 restore or repair your RDB. So please do make a backup copy of it

Documentation/filesystems/coda.txt

@@ -1531,7 +1531,7 @@ kernel support.
 
 
   DDeessccrriippttiioonn Remove all entries in the cache lying in a directory
-  CodaFid, and all children of this directory. This call is issed when
+  CodaFid, and all children of this directory. This call is issued when
   Venus receives a callback on the directory.
 
 
@@ -1630,7 +1630,7 @@ kernel support.
 
   The following requirements should be accommodated:
 
-  1. The message queueus should have open and close routines.  On Unix
+  1. The message queues should have open and close routines.  On Unix
      the opening of the character devices are such routines.
 
   +o  Before opening, no messages can be placed.

Documentation/filesystems/fat_cvf.txt

@@ -140,7 +140,7 @@ It contains...
       THE KIND OF CVF I SUPPORT". The function must maintain the module
       usage counters for safety, i.e. do MOD_INC_USE_COUNT at the beginning
       and MOD_DEC_USE_COUNT at the end. The function *must not* assume that
-      successful recongition would lead to a call of the mount_cvf function
+      successful recognition would lead to a call of the mount_cvf function
       later. 
   - mount_cvf:
       A function that sets up some values or initializes something additional

Documentation/filesystems/hpfs.txt

@@ -25,14 +25,14 @@ conv=binary,text,auto (default binary)
 	- there is a list of text extensions (I thing it's better to not convert
 	text file than to damage binary file). If you want to change that list,
 	change it in the source. Original readonly HPFS contained some strange
-	heuristic alghoritm that I removed. I thing it's danger to let the
+	heuristic algorithm that I removed. I thing it's danger to let the
 	computer decide whether file is text or binary. For example, DJGPP
 	binaries contain small text message at the beginning and they could be
 	misidentified and damaged under some circumstances.
 check=none,normal,strict (default normal)
 	Check level. Selecting none will cause only little speedup and big
 	danger. I tried to write it so that it won't crash if check=normal on
-	corrupted filesystems. check=strict means many superflous checks -
+	corrupted filesystems. check=strict means many superfluous checks -
 	used for debugging (for example it checks if file is allocated in
 	bitmaps when accessing it).
 errors=continue,remount-ro,panic (default remount-ro)
@@ -65,12 +65,12 @@ access it under names 'a.', 'a..', 'a .  . . ' etc.
 
 Extended attributes
 
-On HPFS partion, OS/2 can associate to each file a special information called
+On HPFS partitions, OS/2 can associate to each file a special information called
 extended attributes. Extended attributes are pairs of (key,value) where key is
 an ascii string identifying that attribute and value is any string of bytes of
 variable length. OS/2 stores window and icon positions and file types there. So
 why not use it for unix-specific info like file owner or access rights? This
-driver can do it. If you chown/chgrp/chmod on a hpfs partion, extended
+driver can do it. If you chown/chgrp/chmod on a hpfs partition, extended
 attributes with keys "UID", "GID" or "MODE" and 2-byte values are created. Only
 that extended attributes those value differs from defaults specified in mount
 options are created. Once created, the extended attributes are never deleted,
@@ -89,7 +89,7 @@ values doesn't work.
 
 Symlinks
 
-You can do symlinks on HPFS partion, symlinks are achieved by setting extended
+You can do symlinks on HPFS partition, symlinks are achieved by setting extended
 attribute named "SYMLINK" with symlink value. Like on ext2, you can chown and
 chgrp symlinks but I don't know what is it good for. chmoding symlink results
 in chmoding file where symlink points. These symlinks are just for Linux use and
@@ -107,12 +107,12 @@ file has a pointer to codepage it's name is in. However OS/2 was created in
 America where people don't care much about codepages and so multiple codepages
 support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk.
 Once I booted English OS/2 working in cp 850 and I created a file on my 852
-partion. It marked file name codepage as 850 - good. But when I again booted
+partition. It marked file name codepage as 850 - good. But when I again booted
 Czech OS/2, the file was completely inaccessible under any name. It seems that
 OS/2 uppercases the search pattern with it's system code page (852) and file
 name it's comparing to with its code page (850). These could never match. Is it
-really what IBM developers wanted? But problems countinue. When I created in
-Czech OS/2 another file in that direcotry, that file was inaccesible too. OS/2
+really what IBM developers wanted? But problems continued. When I created in
+Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
 probably uses different uppercasing method when searching where to place a file
 (note, that files in HPFS directory must be sorted) and when searching for
 a file. Finally when I opened this directory in PmShell, PmShell crashed (the
@@ -199,7 +199,7 @@ File names like "a .b" are marked as 'long' by OS/2 but chkdsk "corrects" it and
 marks them as short (and writes "minor fs error corrected"). This bug is not in
 HPFS386.
 
-Codepage bugs decsribed above.
+Codepage bugs described above.
 
 If you don't install fixpacks, there are many, many more...
 
@@ -266,7 +266,7 @@ History
 1.99 Corrected a possible problem when there's not enough space while deleting
 	file
      Now it tries to truncate the file if there's not enough space when deleting
-     Removed a lot of redundat code
+     Removed a lot of redundant code
 2.00 Fixed a bug in rename (it was there since 1.96)
      Better anti-fragmentation strategy
 

Documentation/filesystems/proc.txt

@@ -1047,7 +1047,7 @@ low and the high value.
 
 On a  low-memory,  single  CPU system, you can safely set these values to 0 so
 you don't  waste  memory.  It  is  used  on SMP systems so that the system can
-perform fast  pagetable allocations without having to aquire the kernel memory
+perform fast  pagetable allocations without having to acquire the kernel memory
 lock.
 
 For large  systems,  the  settings  are probably fine. For normal systems they

Documentation/filesystems/ufs.txt

@@ -9,7 +9,7 @@ UFS OPTIONS
 
 ufstype=type_of_ufs
 	UFS is a file system widely used in different operating systems.
-	The problem are differencies among implementations. Features of
+	The problem are differences among implementations. Features of
 	some implementations are undocumented, so its hard to recognize
 	type of ufs automatically. That's why user must specify type of 
 	ufs manually by mount option ufstype. Possible values are:

Documentation/filesystems/vfs.txt

@@ -24,7 +24,7 @@ What is it?                                                           <section>
 
 The Virtual File System (otherwise known as the Virtual Filesystem
 Switch) is the software layer in the kernel that provides the
-filesystem interface to userspace programmes. It also provides an
+filesystem interface to userspace programs. It also provides an
 abstraction within the kernel which allows different filesystem
 implementations to co-exist.
 
@@ -34,7 +34,7 @@ A Quick Look At How It Works                                          <section>
 
 In this section I'll briefly describe how things work, before
 launching into the details. I'll start with describing what happens
-when user programmes open and manipulate files, and then look from the
+when user programs open and manipulate files, and then look from the
 other view which is how a filesystem is supported and subsequently
 mounted.
 

Documentation/floppy.txt

@@ -88,7 +88,7 @@ insmod), first check whether there is a more recent version.
 
 	If you have a FIFO-able FDC, the floppy driver automatically
 	falls back on non DMA mode if no DMA-able memory can be found.
-	If you want to avoid this, explicitely ask for 'yesdma'.
+	If you want to avoid this, explicitly ask for 'yesdma'.
 
  floppy=yesdma
 	Tells the floppy driver that a workable DMA channel is available.

Documentation/highuid.txt

@@ -20,7 +20,7 @@ What's left to be done for 32-bit UIDs on all Linux architectures:
 - Decide whether or not to keep backwards compatibility with the system
   accounting file, or if we should break it as the comments suggest
   (currently, the old 16-bit UID and GID are still written to disk, and
-  part of the former pad sparce is used to store separate 32-bit UID and
+  part of the former pad space is used to store separate 32-bit UID and
   GID)
 
 - Need to validate that OS emulation calls the 16-bit UID

Documentation/i2c/dev-interface

@@ -126,7 +126,7 @@ for details) through the following functions:
   __s32 i2c_smbus_read_block_data(int file, __u8 command, __u8 *values);
   __s32 i2c_smbus_write_block_data(int file, __u8 command, __u8 length, 
                                    __u8 *values);
-All these tranactions return -1 on failure; you can read errno to see
+All these transactions return -1 on failure; you can read errno to see
 what happened. The 'write' transactions return 0 on success; the
 'read' transactions return the read value, except for read_block, which
 returns the number of values read. The block buffers need not be longer

Documentation/i2c/i2c-protocol

@@ -18,7 +18,7 @@ Count (8 bits): A data byte containing the length of a block operation.
 [..]: Data sent by I2C device, as opposed to data sent by the host adapter.
 
 
-Simple send tranaction
+Simple send transaction
 ======================
 
 This corresponds to i2c_master_send.
@@ -34,7 +34,7 @@ This corresponds to i2c_master_recv
   S Addr Rd [A] [Data] A [Data] A ... A [Data] NA P
 
 
-Combined tranactions
+Combined transactions
 ====================
 
 This corresponds to i2c_transfer
@@ -54,7 +54,7 @@ We have found some I2C devices that needs the following modifications:
   Flag I2C_M_NOSTART: 
     In a combined transaction, no 'S Addr' is generated at some point.
     For example, setting I2C_M_NOSTART on the second partial message
-    generateds something like:
+    generates something like:
       S Addr Rd [A] [Data] NA Wr [A] Data [A] P
     If you set the I2C_M_NOSTART variable for the first partial message,
     we do not generate Addr, but we do generate the startbit S. This will

Documentation/i2c/writing-clients

@@ -36,7 +36,7 @@ address.
     /* dec_use        */  &foo_dev_use    /* May be NULL */
   }
  
-The name can be choosen freely, and may be upto 40 characters long. Please
+The name can be chosen freely, and may be upto 40 characters long. Please
 use something descriptive here.
 
 The id should be a unique ID. The range 0xf000 to 0xffff is reserved for
@@ -659,7 +659,7 @@ kernel booting is completed.
 Command function
 ================
 
-A generic ioctl-like function call back is supported. You will seldomly
+A generic ioctl-like function call back is supported. You will seldom
 need this. You may even set it to NULL.
 
   /* No commands defined */
@@ -733,7 +733,7 @@ SMBus communication
                                         u8 command, u8 length,
                                         u8 *values);
 
-All these tranactions return -1 on failure. The 'write' transactions 
+All these transactions return -1 on failure. The 'write' transactions 
 return 0 on success; the 'read' transactions return the read value, except 
 for read_block, which returns the number of values read. The block buffers 
 need not be longer than 32 bytes.
@@ -749,7 +749,7 @@ Below all general purpose routines are listed, that were not mentioned
 before.
 
   /* This call returns a unique low identifier for each registered adapter,
-   * or -1 if the adapter was not regisitered.
+   * or -1 if the adapter was not registered.
    */
   extern int i2c_adapter_id(struct i2c_adapter *adap);
 
@@ -791,7 +791,7 @@ The third, sixth and ninth parameters should always be NULL, and the
 fourth should always be 0. The fifth is the mode of the /proc file;
 0644 is safe, as the file will be owned by root:root. 
 
-The seventh and eigth parameters should be &sensors_proc_real and
+The seventh and eighth parameters should be &sensors_proc_real and
 &sensors_sysctl_real if you want to export lists of reals (scaled
 integers). You can also use your own function for them, as usual.
 Finally, the last parameter is the call-back to gather the data

Documentation/ia64/README

@@ -57,8 +57,8 @@ IA-64 SPECIFICS
       table and only if that fails fall back on walking the page table
       tree.
 	  
-    o Discontigous large memory support; memory above 4GB will be
-      discontigous since the 4GB-64MB is reserved for firmware and I/O
+    o Discontinuous large memory support; memory above 4GB will be
+      discontinuous since the 4GB-64MB is reserved for firmware and I/O
       space.
  
     o Correct mapping for PAL runtime code; PAL code needs to be

Documentation/ia64/efirtc.txt

@@ -36,7 +36,7 @@ The Epoch is January 1st 1998. For backward compatibility reasons we don't
 expose this new way of representing time. Instead we use something very 
 similar to the struct tm, i.e. struct rtc_time, as used by hwclock.
 One of the reasons for doing it this way is to allow for EFI to still evolve
-without necessarily impatcing any of the user applications. The decoupling
+without necessarily impacting any of the user applications. The decoupling
 enables flexibility and permits writing wrapper code is ncase things change.
 
 The driver exposes two interfaces, one via the device file and a set of ioctl()s.

Documentation/isdn/00-INDEX

@@ -31,7 +31,7 @@ README.act2000
 README.eicon
 	- info on driver for Eicon active cards.
 README.concap
-	- info on "CONCAP" ecapsulation protocol interface used for X.25.
+	- info on "CONCAP" encapsulation protocol interface used for X.25.
 README.diversion
 	- info on module for isdn diversion services.
 README.sc

Documentation/isdn/INTERFACE.fax

@@ -4,7 +4,7 @@ $Id: INTERFACE.fax,v 1.1 1999/08/11 20:30:28 armin Exp $
 Description of the fax-subinterface between linklevel and hardwarelevel of 
   isdn4linux. 
 
-  The communication between linklevel (LL) and harwarelevel (HL) for fax
+  The communication between linklevel (LL) and hardwarelevel (HL) for fax
   is based on the struct T30_s (defined in isdnif.h).
   This struct is allocated in the LL.  
   In order to use fax, the LL provides the pointer to this struct with the 
@@ -60,7 +60,7 @@ Structure T30_s:
   depending on progress and type of connection.
   If the phase changes because of an AT command, the LL driver
   changes this value. Otherwise the HL-driver takes care of it, but
-  only neccessary on call establishment (from IDLE to PHASE_A).
+  only necessary on call establishment (from IDLE to PHASE_A).
   (one of the constants ISDN_FAX_PHASE_[IDLE,A,B,C,D,E])
 
   -  direction

Documentation/isdn/README

@@ -146,7 +146,7 @@ README for the ISDN-subsystem
                             x = 38400: 198
                           Note on value in Reg 19:
                             There is _NO_ common convention for 38400 baud.
-                            The value 198 is choosen arbitrarily. Users
+                            The value 198 is chosen arbitrarily. Users
                             _MUST_ negotiate this value before establishing
                             a connection.
                AT&Sx    Set window-size (x = 1..8) (not yet implemented)

Documentation/isdn/README.HiSax

@@ -77,7 +77,7 @@ Note: PCF, PCF-Pro: up to now, only the ISDN part is supported
 
 If you know other passive cards with the Siemens chipset, please let me know.
 To use the PNP cards you need the isapnptools.
-You can combine any card, if there is no conflict between the ressources
+You can combine any card, if there is no conflict between the resources
 (io, mem, irq).
 
 
@@ -532,7 +532,7 @@ to e.g. the Internet:
       /sbin/isdnctrl huptimeout isdn0 0
       /sbin/isdnctrl l2_prot isdn0 hdlc
       # Attention you must not set an outgoing number !!! This won't work !!!
-      # The incomming number is LEASED0 for the first card, LEASED1 for the
+      # The incoming number is LEASED0 for the first card, LEASED1 for the
       # second and so on.
       /sbin/isdnctrl addphone isdn0 in LEASED0
       # Here is no need to bind the channel.
@@ -551,7 +551,7 @@ a) Use state of the art isdn4k-utils
 
 Here an example script:
 #!/bin/sh
-# Start/Stop ISDN lesaed line connection
+# Start/Stop ISDN leased line connection
 
 I4L_AS_MODULE=yes
 I4L_REMOTE_IS_CISCO=no

Documentation/isdn/README.act2000

@@ -7,7 +7,7 @@ There are 3 Types of this card available. A ISA-, MCA-, and PCMCIA-Bus
 Version. Currently, only the ISA-Bus version of the card is supported.
 However MCA and PCMCIA will follow soon.
 
-The ISA-Bus Version uses 8 IO-ports. The base port adress has to be set
+The ISA-Bus Version uses 8 IO-ports. The base port address has to be set
 manually using the DIP switches.
 
 Setting up the DIP switches for the IBM Active 2000 ISDN card:

Documentation/isdn/README.avmb1

@@ -175,7 +175,7 @@ a mail to majordomo@calle.in-berlin.de with
 subscribe linux-avmb1
 in the body.
 
-German documentaion and several scripts can be found at
+German documentation and several scripts can be found at
 ftp://ftp.avm.de/cardware/b1/linux/
 
 Bugs 

Documentation/isdn/README.concap

@@ -68,7 +68,7 @@ increased.
 Likewise, a similar encapsulation protocol will frequently be needed by
 several different interfaces of even different hardware type, e.g. the
 synchronous ppp implementation used by the isdn driver and the
-asyncronous ppp implementation used by the ppp driver have a lot of
+asynchronous ppp implementation used by the ppp driver have a lot of
 similar code in them. By cleanly separating the encapsulation protocol
 from the hardware specific interface stuff such code could be shared
 better in future.

Documentation/isdn/README.diversion

@@ -57,7 +57,7 @@ Table of contents
    compared to the mechanism of ipfwadm or ipchains. If a given rule matches
    the checking process is finished and the rule matching will be applied
    to the call.
-   The rules include primary and secondary service indentifiers, called 
+   The rules include primary and secondary service identifiers, called 
    number and subaddress, callers number and subaddress and whether the rule
    matches to all filtered calls or only those when all B-channel resources
    are exhausted.
@@ -82,7 +82,7 @@ Table of contents
    available in some countries (for example germany). Countries requiring the 
    keypad protocol for activating static diversions (like the netherlands) are
    not supported but may use the tty devices for this purpose.
-   The dynamic diversion servives may be used in all countries if the provider
+   The dynamic diversion services may be used in all countries if the provider
    enables the feature CF (call forwarding). This should work on both MSN- and
    point-to-point lines.
    To add and delete rules the additional divertctrl program is needed. This

Documentation/isdn/README.hysdn

@@ -92,7 +92,7 @@ Table of contents
    3 -> card is booted and active
 
    And the last field (device) shows the name of the ethernet device assigned
-   to this card. Up to the first successfull boot this field only shows a -
+   to this card. Up to the first successful boot this field only shows a -
    to tell that no net device has been allocated up to now. Once a net device
    has been allocated it remains assigned to this card, even if a card is
    rebooted and an boot error occurs. 
@@ -128,12 +128,12 @@ Table of contents
    get the cards and drivers log data. Card messages always start with the
    keyword LOG. All other lines are output from the driver. 
    The driver log data may be redirected to the syslog by selecting the 
-   approriate bitmask. The cards log messages will always be send to this
+   appropriate bitmask. The cards log messages will always be send to this
    interface but never to the syslog.
 
    A root user may write a decimal or hex (with 0x) value t this file to select
    desired output options. As mentioned above the cards log dat is always 
-   written to the cardlog file independant of the following options only used
+   written to the cardlog file independent of the following options only used
    to check and debug the driver itself:
 
    For example: 

Documentation/isdn/README.icn

@@ -139,7 +139,7 @@ Loading the firmware into the card:
   To load a 4B-card, the same command is used, except a second firmware
   file is appended to the commandline of icnctrl.
 
-  -> After dowloading firmware, the two LEDs at the back cover of the card
+  -> After downloading firmware, the two LEDs at the back cover of the card
      (ICN-4B: 4 LEDs) must be blinking intermittently now. If a connection
      is up, the corresponding led is lit continuously.
 

Documentation/isdn/README.sc

@@ -93,7 +93,7 @@ include:
     this driver release?
 
 Before you can compile, install and use the SpellCaster ISA ISDN driver, you
-must ensure that the following software is installed, configuraed and running:
+must ensure that the following software is installed, configured and running:
 
 	- Linux kernel 2.0.20 or later with the required init and ps
 	  versions. Please see your distribution vendor for the correct
@@ -189,7 +189,7 @@ A) 10 steps to the establishment of a basic HDLC connection
 	basic HDLC connection between its two channels.  Two network 
 	interfaces are created and two routes added between the channels.
 
-	i)   using the isdnctrl utitity, add an interface with "addif" and 
+	i)   using the isdnctrl utility, add an interface with "addif" and 
 	     name it "isdn0"
 	ii)  add the outgoing and inbound telephone numbers
 	iii) set the Layer 2 protocol to hdlc
@@ -213,7 +213,7 @@ B) Establishment of a PPP connection
 	This file is a script used to configure a BRI ISDN TA to establish a 
 	PPP connection 	between the two channels.  The file is almost 
 	identical to the HDLC connection example except that the packet 
-	ecapsulation type has to be set.
+	encapsulation type has to be set.
 	
 	use the same procedure as in the HDLC connection from steps i) to 
 	iii) then, after the Layer 2 protocol is set, set the encapsulation 
@@ -238,7 +238,7 @@ C) Establishment of a MLPPP connection
 	This file is a script used to configure a BRI ISDN TA to accept a 
 	Multi Link PPP connection. 
 	
-	i)   using the isdnctrl utitity, add an interface with "addif" and 
+	i)   using the isdnctrl utility, add an interface with "addif" and 
 	     name it "ippp0"
 	ii)  add the inbound telephone number
 	iii) set the Layer 2 protocol to hdlc and the Layer 3 protocol to 

Documentation/joystick-api.txt

@@ -29,13 +29,13 @@ By default, the device is opened in blocking mode.
 where js_event is defined as
 
 	struct js_event {
-		__u32 time;     /* event timestamp in miliseconds */
+		__u32 time;     /* event timestamp in milliseconds */
 		__s16 value;    /* value */
 		__u8 type;      /* event type */
 		__u8 number;    /* axis/button number */
 	};
 
-If the read is successfull, it will return sizeof(struct js_event), unless
+If the read is successful, it will return sizeof(struct js_event), unless
 you wanted to read more than one event per read as described in section 3.1.
 
 
@@ -225,7 +225,7 @@ JS_VERSION symbol
 ~~~~~~~~~~~~~~
 
 JSIOCGNAME(len) allows you to get the name string of the joystick - the same
-as is being printed at boot time. The 'len' argument is the lenght of the
+as is being printed at boot time. The 'len' argument is the length of the
 buffer provided by the application asking for the name. It is used to avoid
 possible overrun should the name be too long.
 

Documentation/joystick-parport.txt

@@ -22,7 +22,7 @@ connecting such devices.
 
 2. Devices supported
 ~~~~~~~~~~~~~~~~~~~~
-  Many console and 8-bit coputer gamepads and joysticks are supported. The
+  Many console and 8-bit computer gamepads and joysticks are supported. The
 following subsections discuss usage of each.
 
 2.1 NES and SNES
@@ -328,7 +328,7 @@ controllers:
 ~~~~~~~~
   All the Sega controllers are more or less based on the standard 2-button
 Multisystem joystick. However, since they don't use switches and use TTL
-logic, the only driver useable with them is the db9.c driver.
+logic, the only driver usable with them is the db9.c driver.
 
 2.4.1 Sega Master System
 ~~~~~~~~~~~~~~~~~~~~~~~~

Documentation/joystick.txt

@@ -166,7 +166,7 @@ other system.
 
   It also supports extensions like additional hats and buttons compatible
 with CH Flightstick Pro, ThrustMaster FCS or 6 and 8 button gamepads. Saitek
-Cyborg 'digital' joysticks are also supportted by this driver, because
+Cyborg 'digital' joysticks are also supported by this driver, because
 they're basically souped up CHF sticks.
 
   However the only types that can be autodetected are:
@@ -475,7 +475,7 @@ models, the additional buttons on the 'Plus' versions are not supported yet.
 	inputattach --magellan /dev/tts/x &
 
 command. After that the Magellan will be detected, initialized, will beep,
-and the /dev/input/jsX device should become useable.
+and the /dev/input/jsX device should become usable.
 
 3.17 I-Force devices 
 ~~~~~~~~~~~~~~~~~~~~
@@ -491,7 +491,7 @@ but is not limited to:
 	inputattach --iforce /dev/tts/x &
 
 command. After that the I-Force device will be detected, and the
-/dev/input/jsX device should become useable.
+/dev/input/jsX device should become usable.
 
   In case you're using the device via the USB port, the inputattach command
 isn't needed.

Documentation/kbuild/commands.txt

@@ -84,7 +84,7 @@ Here are the targets available at the top level:
 	occasionally.  If you are adding configuration options, it's
 	nice if you do it before you publish your patch!
 
-	You can run 'make checkhelp' withoug configuring the kernel.
+	You can run 'make checkhelp' without configuring the kernel.
 	Also, 'make checkhelp' does not modify any files.
 
     make dep, make depend

Documentation/kbuild/config-language.txt

@@ -80,7 +80,7 @@ Here are the basic grammar elements.
 
     A /word/ is a single unquoted word, a single-quoted string, or a
     double-quoted string.  If the word is unquoted or double quoted,
-    then $-substition will be performed on the word.
+    then $-substitution will be performed on the word.
 
     A /symbol/ is a single unquoted word.  A symbol must have a name of
     the form CONFIG_*.  scripts/mkdep.c relies on this convention in order
@@ -231,7 +231,7 @@ Note that the bool verb does not have a default value.  People keep
 trying to write Config Language scripts with a default value for bool,
 but *all* of the existing language interpreters discard additional values.
 Feel free to submit a multi-interpreter patch to linux-kbuild if you
-want to implement this as an enhancment.
+want to implement this as an enhancement.
 
 Configure:  implemented
 Menuconfig: implemented

Documentation/m68k/README.buddha

@@ -21,7 +21,7 @@ Rom-vector: $1000
 
 The  card  should be a Z-II board, size 64K, not for freemem
 list, Rom-Vektor is valid, no second Autoconfig-board on the
-same card, no space preferrence, supports "Shutup_forever".
+same card, no space preference, supports "Shutup_forever".
 
 Setting  the  base address should be done in two steps, just
 as  the Amiga Kickstart does:  The lower nibble of the 8-Bit
@@ -29,7 +29,7 @@ address is written to $4a, then the whole Byte is written to
 $48, while it doesn't matter how often you're writing to $4a
 as  long as $48 is not touched.  After $48 has been written,
 the  whole card disappears from $e8 and is mapped to the new
-addrress just written.  Make shure $4a is written befor $48,
+address just written.  Make shure $4a is written before $48,
 otherwise your chance is only 1:16 to find the board :-).
 
 The local memory-map is even active when mapped to $e8:
@@ -100,7 +100,7 @@ IRQ-lines  of  the  IDE-ports by reading from the three (two
 for  Buddha-only)  registers  $f00, $f40 and $f80.  This way
 more  than one I/O request can be handled and you can easily
 determine  what  driver  has  to serve the INT2.  Buddha and
-Catweasel  expansion  boards  can issue an INT6.  A seperate
+Catweasel  expansion  boards  can issue an INT6.  A separate
 memory  map  is available for the I/O module and the sysop's
 I/O module.
 

Documentation/m68k/kernel-options.txt

@@ -482,7 +482,7 @@ the physical linelength differs from the visible length. With ProMST,
 xres_virtual must be set to 2048. For ET4000, xres_virtual depends on the
 initialisation of the video-card.
 If you're missing a corresponding yres_virtual: the external part is legacy,
-therefore we don't support hardware-dependend functions like hardware-scroll,
+therefore we don't support hardware-dependent functions like hardware-scroll,
 panning or blanking.
 
 4.1.7) eclock:

Documentation/md.txt

@@ -6,7 +6,7 @@ Tools that manage md devices can be found at
 You can boot (if you selected boot support in the configuration) with your md 
 device with the following kernel command lines:
 
-for old raid arrays without persistant superblocks:
+for old raid arrays without persistent superblocks:
   md=<md device no.>,<raid level>,<chunk size factor>,<fault level>,dev0,dev1,...,devn
 
 for raid arrays with persistant superblocks

Documentation/moxa-smartio

@@ -23,7 +23,7 @@ Content
     -C168P/H/HS, C168H/PCI 8 port multiport board.
 
    This driver has been modified a little and cleaned up from the Moxa
-   contributed driver code and merged into Linux 2.2.14pre. In paticular
+   contributed driver code and merged into Linux 2.2.14pre. In particular
    official major/minor numbers have been assigned which are different to
    those the original Moxa supplied driver used.
 
@@ -83,7 +83,7 @@ Content
 
        PCI board
        ---------
-       You may need to adjust IRQ useage in BIOS to avoid from IRQ conflict
+       You may need to adjust IRQ usage in BIOS to avoid from IRQ conflict
        with other ISA devices. Please refer to hardware installation
        procedure in User's Manual in advance.
 
@@ -150,7 +150,7 @@ Content
 
 	  # insmod mxser
 
-	  to activate the moduler driver. You may run "lsmod" to check
+	  to activate the modular driver. You may run "lsmod" to check
 	  if "mxser.o" is activated.
 
        2. Create special files by executing "msmknod".
@@ -158,7 +158,7 @@ Content
 	  # ./msmknod
 
 	  Default major numbers for dial-in device and callout device are
-	  174, 175. Msmknod will delete any special files occuping the same
+	  174, 175. Msmknod will delete any special files occupying the same
 	  device naming.
 
        3. Up to now, you may manually execute "insmod mxser" to activate
@@ -209,7 +209,7 @@ Content
 	  below.
 	  a. # cd /moxa/mxser/driver
 	     # vi mxser.c
-	  b. Find the array mxserBoardCAP[] as belows.
+	  b. Find the array mxserBoardCAP[] as below.
 
 	     static int mxserBoardCAP[]
 	     = {0x00, 0x00, 0x00, 0x00};
@@ -260,7 +260,7 @@ Content
 	   f. cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz
 	   g. Please make sure the boot kernel (vmlinuz) is in the
 	      correct position. If you use 'lilo' utility, you should
-	      check /etc/lilo.conf 'image' item specifiedd the path
+	      check /etc/lilo.conf 'image' item specified the path
 	      which is the 'vmlinuz' path, or you will load wrong
 	      (or old) boot kernel image (vmlinuz).
 	   h. chmod 400 /vmlinuz
@@ -372,7 +372,7 @@ Content
 -----------------------------------------------------------------------------
 6. Troubleshooting
 
-   The boot time error mesages and solutions are stated as clearly as
+   The boot time error messages and solutions are stated as clearly as
    possible. If all the possible solutions fail, please contact our technical
    support team to get more help.
 
@@ -388,7 +388,7 @@ Content
    which device causes the situation,please check /proc/interrupts to find
    free IRQ and simply change another free IRQ for Moxa board.
 
-   Error msg: Board #: C1xx Series(CAP=xxx) interupt number invalid.
+   Error msg: Board #: C1xx Series(CAP=xxx) interrupt number invalid.
    Solution:
    Each port within the same multiport board shares the same IRQ. Please set
    one IRQ (IRQ doesn't equal to zero) for one Moxa board.

Documentation/mtrr.txt

@@ -31,7 +31,7 @@ Richard Gooch
 There are two interfaces to /proc/mtrr: one is an ASCII interface
 which allows you to read and write. The other is an ioctl()
 interface. The ASCII interface is meant for administration. The
-ioctl() interface is meant for C programmes (i.e. the X server). The
+ioctl() interface is meant for C programs (i.e. the X server). The
 interfaces are described below, with sample commands and C code.
 
 ===============================================================================
@@ -96,11 +96,11 @@ Removing MTRRs from the C-shell:
 or using bash:
 % echo "disable=2" >| /proc/mtrr
 ===============================================================================
-Reading MTRRs from a C programme using ioctl()'s:
+Reading MTRRs from a C program using ioctl()'s:
 
 /*  mtrr-show.c
 
-    Source file for mtrr-show (example programme to show MTRRs using ioctl()'s)
+    Source file for mtrr-show (example program to show MTRRs using ioctl()'s)
 
     Copyright (C) 1997-1998  Richard Gooch
 
@@ -124,7 +124,7 @@ Reading MTRRs from a C programme using ioctl()'s:
 */
 
 /*
-    This programme will use an ioctl() on /proc/mtrr to show the current MTRR
+    This program will use an ioctl() on /proc/mtrr to show the current MTRR
     settings. This is an alternative to reading /proc/mtrr.
 
 

Documentation/networking/README.sb1000

@@ -30,7 +30,7 @@ cable modem easy.
       http://home.adelphia.net/~siglercm/sb1000.html
       http://linuxpower.cx/~cable/
 
-   along with these utilties.
+   along with these utilities.
 
 3.) The standard isapnp tools.  These are necessary to configure your SB1000
 card at boot time (or afterwards by hand) since it's a PnP card.

Documentation/networking/comx.txt

@@ -63,7 +63,7 @@ values upon creation, so you don't necessarily have to change all of them.
 
 When you're ready with filling in the files in the comx[n] directory, you can
 configure the corresponding network interface with the standard network 
-configuration utilites. If you're unble to bring the interfaces up, look up
+configuration utilities. If you're unable to bring the interfaces up, look up
 the various kernel log files on your system, and consult the messages for
 a probable reason.
 

Documentation/networking/cs89x0.txt

@@ -214,7 +214,7 @@ Example:
 
     insmod cs89x0.o io=0x200 irq=0xA media=aui
 
-This exmaple loads the module and configures the adapter to use an IO port base
+This example loads the module and configures the adapter to use an IO port base
 address of 200h, interrupt 10, and use the AUI media connection.  The following
 configuration options are available on the command line:
 
@@ -259,7 +259,7 @@ e) The minimum command-line configuration required if an EEPROM is
    irq 
    media type (no autodetect)
 
-f) The following addtional parameters are CS89XX defaults (values
+f) The following additional parameters are CS89XX defaults (values
    used with no EEPROM or command-line argument).
 
    * DMA Burst = enabled

Documentation/networking/decnet.txt

@@ -44,7 +44,7 @@ The kernel command line takes options looking like the following:
 the two numbers are the node address 1,2 = 1.2 For 2.2.xx kernels
 and early 2.3.xx kernels, you must use a comma when specifying the
 DECnet address like this. For more recent 2.3.xx kernels, you may
-use almost charecter except space, although a `.` would be the most
+use almost any character except space, although a `.` would be the most
 obvious choice :-)
 
 There used to be a third number specifying the node type. This option

Documentation/networking/dmfe.txt

@@ -25,7 +25,7 @@
             -Wall -Wstrict-prototypes -O6 -c dmfe.c"
 
 
-  B. The following steps teach you how to active DM9102 board:
+  B. The following steps teach you how to activate a DM9102 board:
 
         1. Used the upper compiler command to compile dmfe.c
 
@@ -40,13 +40,13 @@
            "ifconfig eth0 172.22.3.18"
                           ^^^^^^^^^^^ Your IP address
 
-        4. Active the IP routing table. For some distributions, it is not
+        4. Activate the IP routing table. For some distributions, it is not
            necessary. You can type "route" to check.
 
            "route add default eth0"
 
 
-        5. Well done. Your DM9102 adapter actived now.
+        5. Well done. Your DM9102 adapter is now activated.
 
 
    C. Object files description:

Documentation/networking/ethertap.txt

 Documentation on setup and use of EtherTap.
 
 Contact Jay Schulist <jschlst@turbolinux.com> if you
-have questions or need futher assistance.
+have questions or need further assistance.
 
 Introduction
 ============

Documentation/networking/ip-sysctl.txt

@@ -88,7 +88,7 @@ tcp_keepalive_interval - INTEGER
 	will be aborted after ~11 minutes of retries.
 
 tcp_retries1 - INTEGER
-	How many times to retry before deciding that somethig is wrong
+	How many times to retry before deciding that something is wrong
 	and it is necessary to report this suspection to network layer.
 	Minimal RFC value is 3, it is default, which corresponds
 	to ~3sec-8min depending on RTO.
@@ -139,13 +139,13 @@ tcp_max_orphans - INTEGER
 	(probably, after increasing installed memory),
 	if network conditions require more than default value,
 	and tune network services to linger and kill such states
-	more aggressivley. Let me to remind again: each orphan eats
+	more aggressively. Let me to remind again: each orphan eats
 	up to ~64K of unswappable memory.
 
 tcp_abort_on_overflow - BOOLEAN
 	If listening service is too slow to accept new connections,
 	reset them. Default state is FALSE. It means that if overflow
-	occured due to a burst, connection will recover. Enable this
+	occurred due to a burst, connection will recover. Enable this
 	option _only_ if you are really sure that listening daemon
 	cannot be tuned to accept connections faster. Enabling this
 	option can harm clients of your server.
@@ -179,7 +179,7 @@ tcp_stdurg - BOOLEAN
 	
 tcp_max_syn_backlog - INTEGER
 	Maximal number of remembered connection requests, which are
-	still did not receive an acknowldgement from connecting client.
+	still did not receive an acknowledgement from connecting client.
 	Default value is 1024 for systems with more than 128Mb of memory,
 	and 128 for low memory machines. If server suffers of overload,
 	try to increase this number. Warning! If you make it greater

Documentation/networking/ipddp.txt

 Text file for ipddp.c:
 	AppleTalk-IP Decapsulation and AppleTalk-IP Encapsulation
 
-This text file writen by Jay Schulist <jschlst@turbolinux.com>
+This text file is written by Jay Schulist <jschlst@turbolinux.com>
 
 Introduction
 ------------

Documentation/networking/iphase.txt

@@ -137,7 +137,7 @@ Installation
          -Pcbr:max_pcr=<xxx>
          where:
              xxx = the maximum peak cell rate, from 170 - 353207.
-         This option may only be set on the trasmit machine.
+         This option may only be set on the transmit machine.
 
 
 OUTSTANDING ISSUES

Documentation/networking/olympic.txt

@@ -38,14 +38,14 @@ the driver now re-sizes buffers based on MTU settings as well.
 message_level: Controls level of messages created by the driver. Defaults to 0:
 which only displays start-up and critical messages.  Presently any non-zero 
 value will display all soft messages as well.  NB This does not turn 
-debuging messages on, that must be done by modified the source code.
+debugging messages on, that must be done by modified the source code.
 
 Multi-card:
 
 The driver will detect multiple cards and will work with shared interrupts,
 each card is assigned the next token ring device, i.e. tr0 , tr1, tr2.  The 
 driver should also happily reside in the system with other drivers.  It has 
-been tested with ibmtr.c running, and I personnally have had one Olicom PCI 
+been tested with ibmtr.c running, and I personally have had one Olicom PCI 
 card and two IBM olympic cards (all on the same interrupt), all running
 together. 
 
@@ -68,7 +68,7 @@ mode.  All unexpected MAC frames (beaconing etc.) will be received
 by the driver and the source and destination addresses printed. 
 Also an entry will be added in  /proc/net called olympic_tr. This 
 displays low level information about the configuration of the ring and
-the adapter. This feature has been designed for network adiministrators
+the adapter. This feature has been designed for network administrators
 to assist in the diagnosis of network / ring problems.
 
 6/8/99 Peter De Schrijver and Mike Phillips

Documentation/networking/shaper.txt

@@ -42,7 +42,7 @@ multiple route tables to get the flexibility.
 
 	There is no "borrowing" or "sharing" scheme. This is a simple
 traffic limiter. We implement Van Jacobson and Sally Floyd's CBQ
-architecture into Linux 2.2. THis is the preferred solution. Shaper is
+architecture into Linux 2.2. This is the preferred solution. Shaper is
 for simple or back compatible setups.
 
 Alan

Documentation/networking/sis900.txt

@@ -161,7 +161,7 @@
 
   Silicon Integrated System Corp. is cooperating closely with core Linux
   Kernel developers. The revisions of SiS 900 driver are distributed by
-  the usuall channels for kernel tar files and patches. Those kernel tar
+  the usual channels for kernel tar files and patches. Those kernel tar
   files for official kernel and patches for kernel pre-release can be
   download at official kernel ftp site
   <http://ftp.kernel.org/pub/linux/kernel/> and its mirrors.  The 1.06

Documentation/networking/sk98lin.txt

@@ -138,7 +138,7 @@ Insert a line of the form:
 options sk98lin ...
 
 For "...", use the same syntax as described below for the command
-line paramaters of insmod.
+line parameters of insmod.
 You either have to reboot your computer or unload and reload
 the driver to activate the new parameters.
 The syntax of the driver parameters is:
@@ -187,7 +187,7 @@ which you set the parameter (A or B).
   this port is not "Sense". If autonegotiation is "On", all
   three values are possible. If it is "Off", only "Full" and
   "Half" are allowed.
-  It is usefull if your link partner does not support all
+  It is useful if your link partner does not support all
   possible combinations.
 
 - Flow Control
@@ -269,7 +269,7 @@ which you set the parameter (A or B).
 
 Large frames (also called jumbo frames) are now supported by the
 driver. This can result in a greatly improved throughput if
-transfering large amounts of data.
+transferring large amounts of data.
 To enable large frames, set the MTU (maximum transfer unit)
 of the interface to the value you wish (up to 9000). The command
 for this is:
@@ -285,7 +285,7 @@ it will simply drop them.
 You can switch back to the standard ethernet frame size with:
   ifconfig eth0 mtu 1500
 
-To make this setting persitent, add a script with the 'ifconfig'
+To make this setting persistent, add a script with the 'ifconfig'
 line to the system startup sequence (named something like "S99sk98lin"
 in /etc/rc.d/rc2.d).
 ***

Documentation/networking/smctr.txt

@@ -62,5 +62,5 @@ Errata:
 
 This driver is under the GNU General Public License. Its Firmware image is
 included as an initialized C-array and is licensed by SMC to the Linux
-users of this driver. However no waranty about its fitness is expressed or
+users of this driver. However no warranty about its fitness is expressed or
 implied by SMC.

Documentation/networking/tlan.txt

@@ -51,7 +51,7 @@ II.   Driver Options
 	   0x01		Turn on general debugging messages.
 	   0x02		Turn on receive debugging messages.
 	   0x04		Turn on transmit debugging messages.
-	   0x08		Turn on list debugging messsages.
+	   0x08		Turn on list debugging messages.
 
 	2. You can append aui=1 to the end of the insmod line to cause
            the adapter to use the AUI interface instead of the 10 Base T

Documentation/networking/tms380tr.txt

@@ -10,8 +10,8 @@ Please point your browser to:
 http://www.linux-sna.org
 
 Many thanks to Christoph Goos for his excellent work on this driver and
-SysKonnect for donating the adapters to Linux-SNA for the testing and maintaince
-of this device driver.
+SysKonnect for donating the adapters to Linux-SNA for the testing and 
+maintenance of this device driver.
 
 Important information to be noted:
 1. Adapters can be slow to open (~20 secs) and close (~5 secs), please be 
@@ -52,7 +52,7 @@ to http://www.syskonnect.com
 
 This driver is under the GNU General Public License. Its Firmware image is 
 included as an initialized C-array and is licensed by SysKonnect to the Linux 
-users of this driver. However no waranty about its fitness is expressed or 
+users of this driver. However no warranty about its fitness is expressed or 
 implied by SysKonnect.
 
 Below find attached the setting for the SK NET TR 4/16 ISA adapters

Documentation/networking/tulip.txt

@@ -170,7 +170,7 @@ Version history
 
 0.9.4.3 (April 14, 2000):
 * mod_timer fix (Hal Murray)
-* PNIC2 resusitation (Chris Smith)
+* PNIC2 resuscitation (Chris Smith)
 
 0.9.4.2 (March 21, 2000):
 * Fix 21041 CSR7, CSR13/14/15 handling

Documentation/networking/vortex.txt

@@ -8,7 +8,7 @@ driver for Linux, 3c59x.c.
 
 The driver was written by Donald Becker <becker@cesdis.gsfc.nasa.gov>
 
-Don is no longer the prime maintener of this version of the driver. 
+Don is no longer the prime maintainer of this version of the driver. 
 Please report problems to one or more of:
 
   Andrew Morton <andrewm@uow.edu.au>
@@ -64,7 +64,7 @@ its module is loaded.  These are usually placed in /etc/modules.conf
 
 options 3c59x debug=3 rx_copybreak=300
 
-If you are using the PCMCIA tools (cardmgr) then theoptions may be
+If you are using the PCMCIA tools (cardmgr) then the options may be
 placed in /etc/pcmcia/config.opts:
 
 module "3c59x" opts "debug=3 extra_reset=1"
@@ -135,7 +135,7 @@ rx_copybreak=M
 max_interrupt_work=N
 
   The driver's interrupt service routine can handle many receive and
-  transmit packets in a single invokation.  It does this in a loop. 
+  transmit packets in a single invocation.  It does this in a loop. 
   The value of max_interrupt_work governs how mnay times the interrupt
   service routine will loop.  The default value is 32 loops.  If this
   is exceeded the interrupt service routine gives up and generates a

Documentation/networking/wan-router.txt

@@ -142,11 +142,11 @@ REVISION HISTORY
 
 2.0.8   Nov 02, 1999            - Fixed up the X25API code.
                                 - Clear call bug fixed.i
-                                - Eanbled driver for multi-card
+                                - Enabled driver for multi-card
                                   operation.                                
 
 2.0.7   Aug 26, 1999		- Merged X25API code into WANPIPE.
-				- Fixed a memeory leak for X25API
+				- Fixed a memory leak for X25API
 				- Updated the X25API code for 2.2.X kernels.
 				- Improved NEM handling.
 

Documentation/networking/wanpipe.txt

@@ -228,7 +228,7 @@ REVISION HISTORY
 				creating applications using BiSync
    				streaming.        
 
-2.0.5   Aug 04, 1999 		CHDLC initializatin bug fix.
+2.0.5   Aug 04, 1999 		CHDLC initialization bug fix.
 				PPP interrupt driven driver: 
   				Fix to the PPP line hangup problem.
 				New PPP firmware
@@ -241,13 +241,13 @@ REVISION HISTORY
 				Streaming HDLC API has been taken out.  
 				 Available as a patch.                 
 
-2.0.6   Aug 17, 1999		Increased debugging in statup scripts
-				Fixed insallation bugs from 2.0.5
+2.0.6   Aug 17, 1999		Increased debugging in startup scripts
+				Fixed installation bugs from 2.0.5
 				Kernel patch works for both 2.2.10 and 2.2.11 kernels.
 				There is no functional difference between the two packages         
 
 2.0.7   Aug 26, 1999		o  Merged X25API code into WANPIPE.
-				o  Fixed a memeory leak for X25API
+				o  Fixed a memory leak for X25API
 				o  Updated the X25API code for 2.2.X kernels.
 				o  Improved NEM handling.   
 

Documentation/networking/wavelan.txt

@@ -19,7 +19,7 @@ and many Linux driver to support it.
 
 	This is the driver for the ISA version of the first generation
 of the Wavelan, now discontinued. The device is 2 Mb/s, composed of a
-Intel 82586 controler and a Lucent Modem, and is NOT 802.11 compliant.
+Intel 82586 controller and a Lucent Modem, and is NOT 802.11 compliant.
 	The driver has been tested with the following hardware :
 	o Wavelan ISA 915 MHz (full length ISA card) 
 	o Wavelan ISA 915 MHz 2.0 (half length ISA card) 
@@ -38,7 +38,7 @@ Intel 82586 controler and a Lucent Modem, and is NOT 802.11 compliant.
 
 	This is the driver for the PCMCIA version of the first
 generation of the Wavelan, now discontinued. The device is 2 Mb/s,
-composed of a Intel 82593 controler (totally different from the 82586)
+composed of a Intel 82593 controller (totally different from the 82586)
 and a Lucent Modem, and NOT 802.11 compatible.
 	The driver has been tested with the following hardware :
 	o Wavelan Pcmcia 915 MHz 2.0 (Pcmcia card + separate

Documentation/nmi_watchdog.txt

@@ -7,7 +7,7 @@ on Intel SMP hardware there is a feature that enables us to generate
 'watchdog NMI interrupts'. (NMI: Non Maskable Interrupt - these get
 executed even if the system is otherwise locked up hard) This can be
 used to debug hard kernel lockups. By executing periodic NMI interrupts,
-the kernel can monitor wether any CPU has locked up, and print out
+the kernel can monitor whether any CPU has locked up, and print out
 debugging messages if so.  You can enable/disable the NMI watchdog at boot
 time with the 'nmi_watchdog=1' boot parameter. Eg. the relevant
 lilo.conf entry:

Documentation/powerpc/SBC8260_memory_mapping.txt

@@ -125,7 +125,7 @@ if you have questions, comments or corrections.
 
 	  Although platform dependent, and certainly the case for embedded
 	  8xx, traditionally memory is mapped at physical address zero,
-	  and I/O devices above phsical address 0x80000000.  The lowest
+	  and I/O devices above physical address 0x80000000.  The lowest
 	  and highest (above 0xf0000000) I/O addresses are traditionally 
 	  used for devices or registers we need to map during kernel 
 	  initialization and prior to KVM operation.  For this reason, 

Documentation/s390/DASD

@@ -30,7 +30,7 @@ an Enterprise Storage Server (Seascape) should work fine as well.
 We currently implement one partition per volume, which is the whole
 volume, skipping the first blocks up to the volume label. These are
 reserved for IPL records and IBM's volume label to assure
-accessability of the DASD from other OSs. In a later stage we will
+accessibility of the DASD from other OSs. In a later stage we will
 provide support of partitions, maybe VTOC oriented or using a kind of
 partition table in the label record.
 
@@ -38,7 +38,7 @@ USAGE
 
 -Low-level format (?CKD only)
 For using an ECKD-DASD as a Linux harddisk you have to low-level
-format the tracks by issueing the BLKDASDFORMAT-ioctl on that
+format the tracks by issuing the BLKDASDFORMAT-ioctl on that
 device. This will erase any data on that volume including IBM volume
 labels, VTOCs etc. The ioctl may take a 'struct format_data *' or
 'NULL' as an argument.  

Documentation/s390/cds.txt

@@ -778,7 +778,7 @@ flag    : 0 (zero) or DOIO_WAIT_FOR_INTERRUPT
 The halt_IO() function returns :
 
       0 - successful completion or request successfuly initiated
--EBUSY  - the device is currently performing a sysnchonous I/O
+-EBUSY  - the device is currently performing a synchronous I/O
           operation : do_IO() with flag DOIO_WAIT_FOR_INTERRUPT
           or an error was encountered and the device is currently
           be sensed

Documentation/sound/CMI8338

@@ -14,7 +14,7 @@ WHAT'S NEW
   1. Support modem interface for 8738. (select in kernel configuration)
   2. Enable S/PDIF-in to S/PDIF-out (S/PDIF loop).
   3. Enable 4 channels analog duplicate mode on 3 jack or 4 jack
-     configurateion.
+     configuration.
 
 
    Be aware: C-Media Electronics Inc. is basically an IC design house,

Documentation/sound/ESS

@@ -12,7 +12,7 @@ Every chip that's detected as a later-than-es1688 chip has a 6 bits logarithmic
 master volume control.
 
 Every chip that's detected as a ES1887 now has Full Duplex support. Made a 
-little testprogram that showes that is works, haven't seen a real program that
+little testprogram that shows that is works, haven't seen a real program that
 needs this however.
 
 For ESS chips an additional parameter "esstype" can be specified. This controls

Documentation/sound/Introduction

@@ -320,7 +320,7 @@ in the Sound-HOWTO).
 
 7)  Turn on debug in drivers/sound/sound_config.h (DEB, DDB, MDB).
 
-8)  If the system reports insuffcient DMA memory then you may want to
+8)  If the system reports insufficient DMA memory then you may want to
     load sound with the "dmabufs=1" option. Or in /etc/conf.modules add
 	
 	preinstall sound dmabufs=1
@@ -354,7 +354,7 @@ Module Loading:
 
 When a sound card is first referenced and sound is modular the sound system
 will ask for the sound devices to be loaded. Initially it requests that
-the driver for the sound system is loaded. It then wwill ask for 
+the driver for the sound system is loaded. It then will ask for 
 sound-slot-0, where 0 is the first sound card. (sound-slot-1 the second and
 so on). Thus you can do
 

Documentation/sound/Maestro

@@ -70,7 +70,7 @@ maestro chip.
 
 As this is a PCI device, the module does not need to be informed of
 any IO or IRQ resources it should use, it devines these from the
-system.  Somtimes, on sucky PCs, the BIOS fails to allocated resources
+system.  Sometimes, on sucky PCs, the BIOS fails to allocated resources
 for the maestro.  This will result in a message like:
 	maestro: PCI subsystem reports IRQ 0, this might not be correct.
 from the kernel.  Should this happen the sound chip most likely will

Documentation/sound/PSS

@@ -3,7 +3,7 @@ downloadable programs and also has an AD1848 "Microsoft Sound System"
 device. The PSS driver enables MSS and MPU401 modes of the card. SB 
 is not enabled since it doesn't work concurrently with MSS. 
 
-If you build this driver as a module then the driver takes the folowing
+If you build this driver as a module then the driver takes the following
 parameters
 
 pss_io. 	The I/O base the PSS card is configured at (normally 0x220

Documentation/sound/README.OSS

@@ -81,7 +81,7 @@ contributors. (I could have forgotten some names.)
 	Gregor Hoffleit	Mozart support (initial version)
 	Riccardo Facchetti Audio Excel DSP 16 (aedsp16) support
 	James Hightower Spotting a tiny but important bug in CS423x support.
-	Denis Sablic	OPTi 82C924 spesific enhancements (non PnP mode)
+	Denis Sablic	OPTi 82C924 specific enhancements (non PnP mode)
 	Tim MacKenzie	Full duplex support for OPTi 82C930.
 	
 	Please look at lowlevel/README for more contributors.
@@ -512,7 +512,7 @@ Yamaha OPL3-SA1
 
 	There are also chips called OPL3-SA2, OPL3-SA3, ..., OPL3SA-N. They
 	are PnP chips and will not work with the OPL3-SA1 driver. You should 
-	use the standard MSS, MPU401 and OPL3 options with thses chips and to
+	use the standard MSS, MPU401 and OPL3 options with these chips and to
 	activate the card using isapnptools.
 
 4Front Technologies SoftOSS
@@ -1275,7 +1275,7 @@ with ES688).
 NOTE! ESS cards are not compatible with MSS/WSS so don't worry if MSS support
 of OSS doesn't work with it.
 
-There are some ES1688/688 based sound cards and (particularily) motherboards
+There are some ES1688/688 based sound cards and (particularly) motherboards
 which use software configurable I/O port relocation feature of the chip.
 This ESS proprietary feature is supported only by OSS/Linux.
 
@@ -1285,7 +1285,7 @@ At least a card called (Pearl?) Hypersound 16 supports IRQ 15 but it doesn't
 work.
 
 ES1868 is a PnP chip which is (supposed to be) compatible with ESS1688
-brobably works with OSS/Free after initialization using isapnptools.
+probably works with OSS/Free after initialization using isapnptools.
 
 Reveal cards
 ------------

Documentation/sound/README.modules

@@ -77,7 +77,7 @@ Persistent DMA Buffers:
 The sound modules normally allocate DMA buffers during open() and
 deallocate them during close(). Linux can often have problems allocating
 DMA buffers for ISA cards on machines with more than 16MB RAM. This is
-because ISA DMA buffers must exist below the 16MB boundry and it is quite
+because ISA DMA buffers must exist below the 16MB boundary and it is quite
 possible that we can't find a large enough free block in this region after
 the machine has been running for any amount of time. The way to avoid this
 problem is to allocate the DMA buffers during module load and deallocate

Documentation/sound/README.ymfsb

@@ -28,7 +28,7 @@ ABOUT THIS DRIVER
  It can only play 22.05kHz / 8bit / Stereo samples, control external MIDI
  port.
  If you want to use your card as recent "16-bit" card, you should use
- Alsa or OSS/Linux driver. Ofcource you can write native PCI driver for
+ Alsa or OSS/Linux driver. Of course you can write native PCI driver for
  your cards :)
 
 

Documentation/stallion.txt

@@ -62,7 +62,7 @@ configuration structure. Note that kernel PCI support is required to use PCI
 boards.
 
 There are two methods of configuring ISA, EISA and MCA boards into the drivers.
-If using the driver as a loadable module then the simplist method is to pass
+If using the driver as a loadable module then the simplest method is to pass
 the driver configuration as module arguments. The other method is to modify
 the driver source to add configuration lines for each board in use.
 
@@ -108,7 +108,7 @@ when loading the driver. The general form of the configuration argument is
 
 where:
 
-    board?  -- specifies the arbitary board number of this board,
+    board?  -- specifies the arbitrary board number of this board,
                can be in the range 0 to 3.
 
     name    -- textual name of this board. The board name is the comman

Documentation/sysctl/vm.txt

@@ -118,11 +118,11 @@ freepages.min	When the number of free pages in the system
 		reaches this number, only the kernel can
 		allocate more memory.
 freepages.low	If the number of free pages gets below this
-		point, the kernel starts swapping agressively.
+		point, the kernel starts swapping aggressively.
 freepages.high	The kernel tries to keep up to this amount of
 		memory free; if memory comes below this point,
 		the kernel gently starts swapping in the hopes
-		that it never has to do real agressive swapping.
+		that it never has to do real aggressive swapping.
 
 ==============================================================
 
@@ -198,7 +198,7 @@ In 2.2, the page cache is used for 3 main purposes:
 - swap cache
 
 When your system is both deep in swap and high on cache,
-it probably means that a lot of the swaped data is being
+it probably means that a lot of the swapped data is being
 cached, making for more efficient swapping than possible
 with the 2.0 kernel.
 
@@ -213,7 +213,7 @@ each processor will be between the low and the high value.
 On a low-memory, single CPU system you can safely set these
 values to 0 so you don't waste the memory. On SMP systems it
 is used so that the system can do fast pagetable allocations
-without having to aquire the kernel memory lock.
+without having to acquire the kernel memory lock.
 
 For large systems, the settings are probably OK. For normal
 systems they won't hurt a bit. For small systems (<16MB ram)

Documentation/sysrq.txt

@@ -74,14 +74,14 @@ On other - If you know of the key combos for other architectures, please
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Well, un'R'aw is very handy when your X server or a svgalib program crashes.
 
-sa'K' (Secure Access Key) is usefull when you want to be sure there are no
+sa'K' (Secure Access Key) is useful when you want to be sure there are no
 trojan program is running at console and which could grab your password
 when you would try to login. It will kill all programs on given console
 and thus letting you make sure that the login prompt you see is actually
 the one from init, not some trojan program.
 IMPORTANT:In its true form it is not a true SAK like the one in   :IMPORTANT
 IMPORTATN:c2 compliant systems, and it should be mistook as such. :IMPORTANT
-	It seems other find it usefull as (System Attention Key) which is
+	It seems other find it useful as (System Attention Key) which is
 useful when you want to exit a program that will not let you switch consoles.
 (For example, X or a svgalib program.)
 

Documentation/usb/CREDITS

@@ -45,7 +45,7 @@ THANKS file in Inaky's driver):
 
         - USAR Systems provided us with one of their excellent USB
           Evaluation Kits. It allows us to test the Linux-USB driver
-          for compilance with the latest USB specification. USAR
+          for compliance with the latest USB specification. USAR
           Systems recognized the importance of an up-to-date open
           Operating System and supports this project with
           Hardware. Thanks!.
@@ -64,9 +64,9 @@ THANKS file in Inaky's driver):
           Linux users.
 
         - Many thanks to ing büro h doran [http://www.ibhdoran.com]!
-          It was almost imposible to get a PC backplate USB connector
+          It was almost impossible to get a PC backplate USB connector
           for the motherboard here at Europe (mine, home-made, was
-          quite lowsy :). Now I know where to adquire nice USB stuff!
+          quite lousy :). Now I know where to acquire nice USB stuff!
 
         - Genius Germany donated a USB mouse to test the mouse boot
           protocol. They've also donated a F-23 digital joystick and a
@@ -128,7 +128,7 @@ THANKS file in Inaky's driver):
           documentation for the UUSBD. Go for it!
 
         - Ric Klaren <ia_ric@cs.utwente.nl> for doing nice
-          introductory documents (compiting with Alberto's :).
+          introductory documents (competing with Alberto's :).
 
         - Christian Groessler <cpg@aladdin.de>, for it's help on those
           itchy bits ... :)
@@ -143,7 +143,7 @@ THANKS file in Inaky's driver):
         - Rasca Gmelch <thron@gmx.de> has revived the raw driver and
           pointed bugs, as well as started the uusbd-utils package.
 
-        - Peter Dettori <dettori@ozy.dec.com> is unconvering bugs like
+        - Peter Dettori <dettori@ozy.dec.com> is uncovering bugs like
           crazy, as well as making cool suggestions, great :)
 
         - All the Free Software and Linux community, the FSF & the GNU
@@ -153,7 +153,7 @@ THANKS file in Inaky's driver):
         - Big thanks to Richard Stallman for creating Emacs!
 
         - The people at the linux-usb mailing list, for reading so
-          many messages :) Ok, no more kidding; for all your advices!
+          many messages :) Ok, no more kidding; for all your advises!
 
         - All the people at the USB Implementors Forum for their
           help and assistance.

Documentation/usb/URB.txt

@@ -23,7 +23,7 @@ usage and information passing to the completion handler.
 - URBs can be linked. After completing one URB, the next one can be
 automatically submitted. This is especially useful for ISO transfers:
 You only have read/write the data from/to the buffers in the completion 
-handler, the continous streaming itself is transparently done by the 
+handler, the continuous streaming itself is transparently done by the 
 URB-machinery.
 
 1.2. The URB structure
@@ -104,7 +104,7 @@ transfer_flags.
 
 Usually, (to reduce restart time) the completion handler is called
 AFTER the URB re-submission. You can get the other way by setting
-USB_URB_EARLY_COMPLETE in transfer_flags. This is implicite for
+USB_URB_EARLY_COMPLETE in transfer_flags. This is implicit for
 INT transfers.
 
 1.5. How to submit an URB?
@@ -131,7 +131,7 @@ For isochronous endpoints, subsequent submitting of URBs to the same endpoint
 with the ASAP flag result in a seamless ISO streaming. Exception: The 
 execution cannot be scheduled later than 900 frames from the 'now'-time. 
 The same applies to INT transfers, but here the seamless continuation is 
-independent of the transfer flags (implicitely ASAP).
+independent of the transfer flags (implicitly ASAP).
 
 1.6. How to cancel an already running URB?
 
@@ -174,14 +174,14 @@ It is allowed to specify a varying length from frame to frame (e.g. for
 audio synchronisation/adaptive transfer rates). You can also use the length 
 0 to omit one or more frames (striping).
 
-As can be concluded from above, the UHCI-driver does not care for continous
+As can be concluded from above, the UHCI-driver does not care for continuous
 data in case of short packet ISO reads! There's no fixup_isoc() like in the 
 old driver. There may be a common routine to do this in the future, but this 
 has nothing to do with the UHCI-driver!
 
 For scheduling you can choose your own start frame or ASAP. As written above,
 queuing more than one ISO frame with ASAP to the same device&endpoint result 
-in seamless ISO streaming. For continous streaming you have to use URB
+in seamless ISO streaming. For continuous streaming you have to use URB
 linking. 
 
 1.9. How to start interrupt (INT) transfers?

Documentation/usb/input.txt

@@ -134,7 +134,7 @@ instead.
 
 3.1.3 usbkbd.c
 ~~~~~~~~~~~~~~
-  Much like usbmouse.c, this module talks to keyboards with a simpplified
+  Much like usbmouse.c, this module talks to keyboards with a simplified
 HIDBP protocol. It's smaller, but doesn't support any extra special keys.
 Use hid.c instead if there isn't any special reason to use this.
 
@@ -158,7 +158,7 @@ matter of a couple days to add it.
 
 3.2 Event handlers
 ~~~~~~~~~~~~~~~~~~
-  Event handlers distrubite the events from the devices to userland and
+  Event handlers distribute the events from the devices to userland and
 kernel, as needed.
 
 3.2.1 keybdev.c
@@ -230,7 +230,7 @@ And so on up to js31.
 ~~~~~~~~~~~~~
   Evdev is the generic input event interface. It passes the events generated
 in the kernel straight to the program, with timestamps. The API is still
-evolving, but should be useable now. It's described in section 5.
+evolving, but should be usable now. It's described in section 5.
 
   This should be the way for GPM and X to get keyboard and mouse mouse
 events. It allows for multihead in X without any specific multihead kernel
@@ -273,7 +273,7 @@ emulated, characters should appear if you move it.
   You can test the joystick emulation with the 'jstest' utility, available
 in the joystick package (see Documentation/joystick.txt).
 
-  You can test the event devics with the 'evtest' utitily available on the
+  You can test the event devics with the 'evtest' utility available on the
 input driver homepage (see the URL above).
 
 5. Event interface
@@ -295,7 +295,7 @@ struct input_event {
 };
 
   'time' is the timestamp, it returns the time at which the event happened.
-Type is for example EV_REL for relative momement, REL_KEY for a keypress or
+Type is for example EV_REL for relative movement, REL_KEY for a keypress or
 release. More types are defined in include/linux/input.h.
 
   'code' is event code, for example REL_X or KEY_BACKSPACE, again a complete

Documentation/usb/ohci.txt

 
 The OHCI HCD layer is a simple but nearly complete implementation of what the
 USB people would call a HCD  for the OHCI. 
- (ISO comming soon, Bulk, INT u. CTRL transfers enabled)
+ (ISO coming soon, Bulk, INT u. CTRL transfers enabled)
 It is based on Linus Torvalds UHCI code and Gregory Smith OHCI fragments (0.03 source tree).
 The layer (functions) on top of it, is for interfacing to the alternate-usb device-drivers. 
 
@@ -35,11 +35,11 @@ Features:
 
 - Endpoint Descriptor (ED) handling more static approach 
  (EDs should be allocated in parallel to the SET CONFIGURATION command and they live
- as long as the function (device) is alive or another configuration is choosen.
+ as long as the function (device) is alive or another configuration is chosen.
  In the HCD layer the EDs has to be allocated manually either by calling a subroutine
  or by sending a USB root hub vendor specific command to the virtual root hub.
  At the alternate linux usb stack EDs will be added (allocated) at their first use.
- ED will be unlinked from the HC chains if they are not bussy.
+ ED will be unlinked from the HC chains if they are not busy.
  
  files: ohci-hcd.c ohci-hcd.h
  routines:   (do not use for drivers, use the top layer alternate usb commands instead)

Documentation/usb/ov511.txt

@@ -158,7 +158,7 @@ MODULE PARAMETERS:
   DEFAULT: 5
   DESC: This is the number of times the driver will try to sync and detect the
         internal i2c bus (which connects the OV511 and sensor). If you are
-        getting intermittant detection failures ("Failed to read sensor ID...")
+        getting intermittent detection failures ("Failed to read sensor ID...")
         you should increase this by a modest amount. If setting it to 20 or so
         doesn't fix things, look elsewhere for the cause of the problem.
 

Documentation/usb/proc_usb_info.txt

@@ -103,7 +103,7 @@ S:  Product=ssss
 S:  SerialNumber=ssss
 |   |__Serial Number of this device as read from the device,
 |      except that it is a generated string for USB host controllers
-|      (virtual root hubs), and represent's the host controller's
+|      (virtual root hubs), and represents the host controller's
 |      unique identification in the system (currently I/O or
 |      memory-mapped base address).
 |__String info tag

Documentation/usb/scanner.txt

@@ -121,11 +121,11 @@ data in the file is raw data so it's not very useful for imaging.
 
 MESSAGES
 
-On occassion the message 'usb_control/bulk_msg: timeout' or something
+On occasions the message 'usb_control/bulk_msg: timeout' or something
 similar will appear in '/var/adm/messages' or on the console or both,
 depending on how your system is configured.  This is a side effect
 that scanners are sometimes very slow at warming up and/or
-initialiazing.  In most cases, however, only several of these messages
+initializing.  In most cases, however, only several of these messages
 should appear and is generally considered to be normal.  If you see
 a message of the type 'excessive NAK's received' then this should
 be considered abnormal and generally indicates that the USB system is

Documentation/usb/uhci.txt

@@ -32,7 +32,7 @@ The invention of the basic concept, and major coding were completed in two
 days (and nights) on the 16th and 17th of October 1999, now known as the
 great USB-October-Revolution started by GA, DF, and TS ;-)
 
-Since the concept is in no way UHCI dependant, we hope that it will also be 
+Since the concept is in no way UHCI dependent, we hope that it will also be 
 transfered to the OHCI-driver, so both drivers share a common API.
 
 1.2. Advantages and disadvantages
@@ -58,7 +58,7 @@ and its semantics were unnecessary complicated in our opinion.
 
 1.4. What's really working?
 
-As said above, CTRL und BULK already work fine even with the wrappers,
+As said above, CTRL and BULK already work fine even with the wrappers,
 so legacy code wouldn't notice the change.
 Regarding to Thomas, ISO transfers now run stable with USB audio.
 INT transfers (e.g. mouse driver) work fine, too.
@@ -113,7 +113,7 @@ before the End Chain QH (for BULK). Since only the QH->next pointers are
 affected, no atomic memory operation is required. The three QHs in the
 common chain are never equipped with TDs!
 
-For ISO or INT, the TD for each frame is simply inserted into the apropriate
+For ISO or INT, the TD for each frame is simply inserted into the appropriate
 ISO/INT-TD-chain for the desired frame. The 7 skeleton INT-TDs are scattered
 among the 1024 frames similar to the old UHCI driver.
 

Documentation/usb/usb-serial.txt

@@ -46,7 +46,7 @@ ConnectTech WhiteHEAT 4 port converter
 
 Current status:
   The device's firmware is downloaded on connection, the new firmware 
-  runs properly and all four ports are successfuly recognized and connected.
+  runs properly and all four ports are successfully recognized and connected.
   Data can be sent and received through the device on all ports.
   Hardware flow control needs to be implemented.
 

Documentation/video4linux/CQcam.txt

@@ -127,7 +127,7 @@ everything is working.
 
   The c-qcam is IEEE1284 compatible, so if you are using the proc file
 system (CONFIG_PROC_FS), the parallel printer support
-(CONFIG_PRINTER), the IEEE 1284 sytem,(CONFIG_PRINTER_READBACK), you
+(CONFIG_PRINTER), the IEEE 1284 system,(CONFIG_PRINTER_READBACK), you
 should be able to read some identification from your quickcam with
 
          modprobe -v parport

Documentation/video4linux/README.cpia

@@ -107,7 +107,7 @@ FEATURES:
   device opens
 - complete control over camera via proc-interface (_all_ camera settings are
   supported), there is also a python-gtk application available for this [3]
-- works under SMP (but the driver is completly serialized and synchronous)
+- works under SMP (but the driver is completely serialized and synchronous)
   so you get no benefit from SMP, but at least it does not crash your box
 - might work for non-Intel architecture, let us know about this
 
@@ -159,7 +159,7 @@ IMPLEMENTATION NOTES:
 
 The camera can act in two modes, streaming or grabbing. Right now a
 polling grab-scheme is used. Maybe interrupt driven streaming will be
-used for a ansychronous mmap interface in the next major release of the
+used for a asynchronous mmap interface in the next major release of the
 driver. This might give a better frame rate.
 
 ---------------------------------------------------------------------------

Documentation/video4linux/radiotrack.txt

@@ -35,7 +35,7 @@ PHYSICAL DESCRIPTION
 --------------------
 The RadioTrack card is an ISA 8-bit FM radio card.  The radio frequency (RF)
 input is simply an antenna lead, and the output is a power audio signal
-available through a miniature phono plug.  Its RF frequencies of operation are
+available through a miniature phone plug.  Its RF frequencies of operation are
 more or less limited from 87.0 to 109.0 MHz (the commercial FM broadcast
 band).  Although the registers can be programmed to request frequencies beyond
 these limits, experiments did not give promising results.  The variable

Documentation/video4linux/zr36120.txt

@@ -45,7 +45,7 @@ fps we ought to get... Here is the scenario: capturing frames
 to memory is done in the so-called snapshot mode. In this mode
 the Zoran stops after capturing a frame worth of data and wait
 till the application set GRAB bit to indicate readiness for the
-next frame. After detecting a set bit, the chip neetly waits
+next frame. After detecting a set bit, the chip neatly waits
 till the start of a frame, captures it and it goes back to off.
 Smart ppl will notice the problem here. Its the waiting on the
 _next_ frame each time we set the GRAB bit... Oh well, 12,5 fps

Documentation/vm/numa

@@ -14,7 +14,7 @@ across nodes, and trying to house all the data structures that
 key components of the kernel need on memory on that node.
 
 Currently, all the numa support is to provide efficient handling
-of widely discontiguous physical memory, so architectures which 
+of widely discontinuous physical memory, so architectures which 
 are not NUMA but can have huge holes in the physical address space
 can use the same code. All this code is bracketed by CONFIG_DISCONTIGMEM.
 

MAINTAINERS

@@ -393,8 +393,8 @@ L:	linux-kernel@vger.rutgers.edu
 S:	Maintained
 
 FILE LOCKING (flock() and fcntl()/lockf())
-P:	Andy Walker
-M:	andy@lysaker.kvaerner.no
+P:	Matthew Wilcox
+M:	willy@thepuffingroup.com
 L:	linux-kernel@vger.rutgers.edu
 S:	Maintained