From 4051f13a08152cefe2dec3e71e559ba538d6260e Mon Sep 17 00:00:00 2001 From: yokota Date: Mon, 3 Apr 2000 09:38:52 +0000 Subject: Brush up the last commit. - Expand contractions. - Change some expressions. - Reword the sections that describe the reporting of down events. Submitted by: sheldonh --- usr.sbin/moused/moused.8 | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) (limited to 'usr.sbin/moused') diff --git a/usr.sbin/moused/moused.8 b/usr.sbin/moused/moused.8 index 4f3c1d7..5f0449f 100644 --- a/usr.sbin/moused/moused.8 +++ b/usr.sbin/moused/moused.8 @@ -100,7 +100,7 @@ in the text mode console. The user program which is reading mouse data via .Xr sysmouse 4 -won't be affected. +will not be affected. .It Fl D Lower DTR on the serial port. This option is valid only if @@ -117,7 +117,7 @@ the .Nm daemon waits .Ar timeout -msec at maximum before deciding if two buttons are pressed +msec at most before deciding whether two buttons are being pressed simultaneously. The default timeout is 200 msec. .It Fl F Ar rate @@ -135,7 +135,7 @@ If this option is given together with the .Fl i option, the .Nm -command won't be able to print useful information for the serial mouse. +command will not be able to print useful information for the serial mouse. .It Fl R Lower RTS on the serial port. This option is valid only if @@ -155,7 +155,7 @@ Select the baudrate for the serial port (1200 to 9600). Not all serial mice support this option. .It Fl c Some mice report middle button down events -as if the left and right buttons are pressed. +as if the left and right buttons are being pressed. This option handles this. .It Fl d Enable debugging messages. @@ -339,24 +339,24 @@ maybe: .It Ar y X or Y axis movement will be reported when the Z axis movement is detected. .It Ar N -Report the virtual buttons +Report down events for the virtual buttons .Ar N and .Ar N+1 -down events respectively when negative and positive Z axis movement +respectively when negative and positive Z axis movement is detected. -There doesn't need to be physical buttons +There do not need to be physical buttons .Ar N and .Ar N+1 . Note that mapping to logical buttons is carried out after mapping from the Z axis movement to the virtual buttons is done. .It Ar N1 N2 -Report the virtual buttons +Report down events for the virtual buttons .Ar N1 and .Ar N2 -down events respectively when negative and positive Z axis movement +respectively when negative and positive Z axis movement is detected. .It Ar N1 N2 N3 N4 This is useful for the mouse with two wheels of which @@ -373,7 +373,7 @@ If the buttons .Ar N3 and .Ar N4 -actually exist in this mouse, their actions won't be detected. +actually exist in this mouse, their actions will not be detected. .Pp Note that horizontal movement or second roller/wheel movement may not always be detected, @@ -480,10 +480,10 @@ protocol. 3-button serial mice may work with the .Ar mousesystems protocol. -If it doesn't, it may work with the +If it does not, it may work with the .Ar microsoft protocol although -the third (middle) button won't function. +the third (middle) button will not function. 3-button serial mice may also work with the .Ar mouseman protocol under which the third button may function as expected. @@ -530,7 +530,7 @@ to use .Xr sysmouse , then the application program will always see mouse data from either mice. When the serial mouse is not attached, the corresponding mouse daemon -won't detect any movement or button state change and the application +will not detect any movement or button state change and the application program will only see mouse data coming from the daemon for the PS/2 mouse. In contrast when both mice are attached and both of them -- cgit v1.1