X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=Documentation%2Finput%2Fgameport-programming.txt;h=14e0a8b70225f5cce93c2cf8bdb85a0aa984b8ee;hb=a2f44b27303a5353859d77a3e96a1d3f33f56ab7;hp=1ba3d322e0acbe88cd7769d009e7cfa8438b9ff0;hpb=134734d875a0a48d994ef20b9905209b4b8b6f75;p=linux-2.6.git

diff --git a/Documentation/input/gameport-programming.txt b/Documentation/input/gameport-programming.txt
index 1ba3d322e..14e0a8b70 100644
--- a/Documentation/input/gameport-programming.txt
+++ b/Documentation/input/gameport-programming.txt
@@ -18,8 +18,8 @@ Make sure struct gameport is initialized to 0 in all other fields. The
 gameport generic code will take care of the rest.
 
 If your hardware supports more than one io address, and your driver can
-choose which one program the hardware to, starting from the more exotic
-addresses is preferred, because the likelyhood of clashing with the standard
+choose which one to program the hardware to, starting from the more exotic
+addresses is preferred, because the likelihood of clashing with the standard
 0x201 address is smaller.
 
 Eg. if your driver supports addresses 0x200, 0x208, 0x210 and 0x218, then