diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 22:50:39 +0200 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:50:39 +0200 |
commit | 2fe0ae78c6975d6fa2fc0c84f2b8944543054105 (patch) | |
tree | 005a185c1043f5b99f4cd851ad071d6e95025064 /Documentation/input | |
parent | a2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df (diff) | |
download | linux-2fe0ae78c6975d6fa2fc0c84f2b8944543054105.tar.bz2 |
Fix typos in Documentation/: 'H'-'M'
This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letters 'H'-'M'.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/input')
-rw-r--r-- | Documentation/input/atarikbd.txt | 2 | ||||
-rw-r--r-- | Documentation/input/gameport-programming.txt | 4 | ||||
-rw-r--r-- | Documentation/input/input.txt | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/input/atarikbd.txt b/Documentation/input/atarikbd.txt index 3feb9f2f3682..7171fbf86fae 100644 --- a/Documentation/input/atarikbd.txt +++ b/Documentation/input/atarikbd.txt @@ -406,7 +406,7 @@ INTERROGATION MODE. 9.18 SET JOYSTICK MONITORING 0x17 - rate ; time between samples in hundreths of a second + rate ; time between samples in hundredths of a second Returns: (in packets of two as long as in mode) %000000xy ; where y is JOYSTICK1 Fire button ; and x is JOYSTICK0 Fire button diff --git a/Documentation/input/gameport-programming.txt b/Documentation/input/gameport-programming.txt index 1ba3d322e0ac..14e0a8b70225 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 diff --git a/Documentation/input/input.txt b/Documentation/input/input.txt index a8aa848f8656..fabb8235c279 100644 --- a/Documentation/input/input.txt +++ b/Documentation/input/input.txt @@ -279,7 +279,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 moment, 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 |