Fix mis-ordered (.SH) sections.

man2/nanosleep.2

@@ -127,33 +127,6 @@ field was not in the range 0 to 999999999 or
 was negative.
 .SH "CONFORMING TO"
 POSIX.1-2001.
-.SH BUGS
-.SS "Old behavior"
-In order to support applications requiring much more precise pauses
-(e.g., in order to control some time-critical hardware),
-.BR nanosleep ()
-would handle pauses of up to 2\ ms by busy waiting with microsecond
-precision when called from a thread scheduled under a real-time policy
-like
-.B SCHED_FIFO
-or
-.BR SCHED_RR .
-This special extension was removed in kernel 2.5.39,
-hence is still present in
-current 2.4 kernels, but not in 2.6 kernels.
-.PP
-In Linux 2.4, if
-.BR nanosleep ()
-is stopped by a signal (e.g.,
-.BR SIGTSTP ),
-then the call fails with the error
-.B EINTR
-after the thread is resumed by a
-.B SIGCONT
-signal.
-If the system call is subsequently restarted,
-then the time that the thread spent in the stopped state is
-\fInot\fP counted against the sleep interval.
 .SH NOTES
 If the interval specified in
 .I req
@@ -204,6 +177,33 @@ function; ...
 Consequently, these time services shall expire when the requested relative
 interval elapses, independently of the new or old value of the clock.
 .RE
+.SH BUGS
+.SS "Old behavior"
+In order to support applications requiring much more precise pauses
+(e.g., in order to control some time-critical hardware),
+.BR nanosleep ()
+would handle pauses of up to 2\ ms by busy waiting with microsecond
+precision when called from a thread scheduled under a real-time policy
+like
+.B SCHED_FIFO
+or
+.BR SCHED_RR .
+This special extension was removed in kernel 2.5.39,
+hence is still present in
+current 2.4 kernels, but not in 2.6 kernels.
+.PP
+In Linux 2.4, if
+.BR nanosleep ()
+is stopped by a signal (e.g.,
+.BR SIGTSTP ),
+then the call fails with the error
+.B EINTR
+after the thread is resumed by a
+.B SIGCONT
+signal.
+If the system call is subsequently restarted,
+then the time that the thread spent in the stopped state is
+\fInot\fP counted against the sleep interval.
 .SH "SEE ALSO"
 .BR clock_nanosleep (2),
 .BR sched_setscheduler (2),

man3/inet_ntop.3

@@ -84,9 +84,6 @@ returns a non-null pointer to
 NULL is returned if there was an error, with
 .I errno
 set to indicate the error.
-.SH EXAMPLE
-See
-.BR inet_pton (3).
 .SH ERRORS
 .TP
 .B EAFNOSUPPORT
@@ -111,6 +108,9 @@ but 2.2 and later have
 .SH BUGS
 .B AF_INET6
 converts IPv4-mapped IPv6 addresses into an IPv6 format.
+.SH EXAMPLE
+See
+.BR inet_pton (3).
 .SH "SEE ALSO"
 .BR getnameinfo (3),
 .BR inet (3),

man3/inet_pton.3

@@ -126,12 +126,6 @@ is set to
 .BR EAFNOSUPPORT .
 .SH "CONFORMING TO"
 POSIX.1-2001.
-.SH BUGS
-.B AF_INET6
-does not recognize IPv4 addresses.
-An explicit IPv4-mapped IPv6 address must be supplied in
-.I src
-instead.
 .SH NOTES
 Unlike
 .BR inet_aton (3)
@@ -151,6 +145,12 @@ four bytes to be explicitly written).
 For an interface that handles both IPv6 addresses, and IPv4
 addresses in numbers-and-dots notation, see
 .BR getaddrinfo (3).
+.SH BUGS
+.B AF_INET6
+does not recognize IPv4 addresses.
+An explicit IPv4-mapped IPv6 address must be supplied in
+.I src
+instead.
 .SH EXAMPLE
 The program below demonstrates the use of
 .BR inet_pton ()

man3/scanf.3

@@ -595,41 +595,6 @@ documentation of
 .I GNU
 .I libc (glibc-1.08)
 for a more concise description.
-.SH BUGS
-All functions are fully C89 conformant, but provide the
-additional specifiers
-.B q
-and
-.B a
-as well as an additional behavior of the
-.B L
-and
-.B l
-specifiers.
-The latter may be considered to be a bug, as it changes the
-behavior of specifiers defined in C89.
-.PP
-Some combinations of the type modifiers and conversion
-specifiers defined by ANSI C do not make sense
-(e.g.
-.BR "%Ld" ).
-While they may have a well-defined behavior on Linux, this need not
-to be so on other architectures.
-Therefore it usually is better to use
-modifiers that are not defined by ANSI C at all, that is, use
-.B q
-instead of
-.B L
-in combination with
-\fBd\fP, \fBi\fP, \fBo\fP, \fBu\fP, \fBx\fP, and \fBX\fP
-conversions or
-.BR ll .
-.PP
-The usage of
-.B q
-is not the same as on 4.4BSD,
-as it may be used in float conversions equivalently to
-.BR L .
 .SH NOTES
 The GNU C library supports a non-standard extension that causes
 the library to dynamically allocate a string of sufficient size
@@ -706,6 +671,41 @@ floating-point conversion specifier (and is unaffected by
 etc.)
 .IP *
 It is specified in the upcoming revision of the POSIX.1 standard.
+.SH BUGS
+All functions are fully C89 conformant, but provide the
+additional specifiers
+.B q
+and
+.B a
+as well as an additional behavior of the
+.B L
+and
+.B l
+specifiers.
+The latter may be considered to be a bug, as it changes the
+behavior of specifiers defined in C89.
+.PP
+Some combinations of the type modifiers and conversion
+specifiers defined by ANSI C do not make sense
+(e.g.
+.BR "%Ld" ).
+While they may have a well-defined behavior on Linux, this need not
+to be so on other architectures.
+Therefore it usually is better to use
+modifiers that are not defined by ANSI C at all, that is, use
+.B q
+instead of
+.B L
+in combination with
+\fBd\fP, \fBi\fP, \fBo\fP, \fBu\fP, \fBx\fP, and \fBX\fP
+conversions or
+.BR ll .
+.PP
+The usage of
+.B q
+is not the same as on 4.4BSD,
+as it may be used in float conversions equivalently to
+.BR L .
 .SH "SEE ALSO"
 .BR getc (3),
 .BR printf (3),

man4/initrd.4

@@ -67,17 +67,6 @@ the RAM disk driver cannot be loaded as a module.
 .\"
 .\"
 .\"
-.SH FILES
-.I /dev/initrd
-.br
-.I /dev/ram0
-.br
-.I /linuxrc
-.br
-.I /initrd
-.\"
-.\"
-.\"
 .SH DESCRIPTION
 The special file
 .I /dev/initrd
@@ -429,6 +418,17 @@ from the CD-ROM.
 .\"
 .\"
 .\"
+.SH FILES
+.I /dev/initrd
+.br
+.I /dev/ram0
+.br
+.I /linuxrc
+.br
+.I /initrd
+.\"
+.\"
+.\"
 .SH NOTES
 .IP 1. 3
 With the current kernel, any file systems that remain mounted when