mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to the

bottom of the manpages and order them consistently.

GNU groff doesn't care about the ordering, and doesn't even mention
CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put
them.

Found by:	mdocml lint run
Reviewed by:	ru

1 files changed, 30 insertions, 30 deletions

diff --git a/share/man/man4/psm.4 b/share/man/man4/psm.4
index b61a4d3..ed911bd 100644
--- a/share/man/man4/psm.4
+++ b/share/man/man4/psm.4
@@ -817,36 +817,6 @@ The rest of the lines show the device ID code, the number of detected
 buttons and internal variables.
 .Pp
 At debug level 2, much more detailed information is logged.
-.Sh CAVEATS
-Many pad devices behave as if the first (left) button were pressed if
-the user `taps' the surface of the pad.
-In contrast, some pad products, e.g.\& some versions of ALPS GlidePoint
-and Interlink VersaPad, treat the tapping action
-as fourth button events.
-.Pp
-It is reported that Interlink VersaPad requires both
-.Em HOOKRESUME
-and
-.Em INITAFTERSUSPEND
-flags in order to recover from suspended state.
-These flags are automatically set when VersaPad is detected by the
-.Nm
-driver.
-.Pp
-Some PS/2 mouse models from MouseSystems require to be put in the
-high resolution mode to work properly.
-Use the driver flag to
-set resolution.
-.Pp
-There is not a guaranteed way to re-synchronize with the first byte
-of the packet once we are out of synchronization with the data
-stream.
-However, if you are using the \fIXFree86\fP server and experiencing
-the problem, you may be able to make the X server synchronize with the mouse
-by switching away to a virtual terminal and getting back to the X server,
-unless the X server is accessing the mouse via
-.Xr moused 8 .
-Clicking any button without moving the mouse may also work.
 .Sh SEE ALSO
 .Xr ioctl 2 ,
 .Xr syslog 3 ,
@@ -878,6 +848,36 @@ to name the few.
 .Pp
 This manual page was written by
 .An Kazutaka Yokota Aq yokota@FreeBSD.org .
+.Sh CAVEATS
+Many pad devices behave as if the first (left) button were pressed if
+the user `taps' the surface of the pad.
+In contrast, some pad products, e.g.\& some versions of ALPS GlidePoint
+and Interlink VersaPad, treat the tapping action
+as fourth button events.
+.Pp
+It is reported that Interlink VersaPad requires both
+.Em HOOKRESUME
+and
+.Em INITAFTERSUSPEND
+flags in order to recover from suspended state.
+These flags are automatically set when VersaPad is detected by the
+.Nm
+driver.
+.Pp
+Some PS/2 mouse models from MouseSystems require to be put in the
+high resolution mode to work properly.
+Use the driver flag to
+set resolution.
+.Pp
+There is not a guaranteed way to re-synchronize with the first byte
+of the packet once we are out of synchronization with the data
+stream.
+However, if you are using the \fIXFree86\fP server and experiencing
+the problem, you may be able to make the X server synchronize with the mouse
+by switching away to a virtual terminal and getting back to the X server,
+unless the X server is accessing the mouse via
+.Xr moused 8 .
+Clicking any button without moving the mouse may also work.
 .Sh BUGS
 The ioctl command
 .Dv MOUSEIOCREAD