1 files changed, 21 insertions, 21 deletions
diff --git a/man7/signal.7 b/man7/signal.7
index ea8cf51c68..8244dbbc77 100644
--- a/man7/signal.7
+++ b/man7/signal.7
@@ -54,7 +54,7 @@ Each signal has a current
 .IR disposition ,
 which determines how the process behaves when it is delivered
 the signal.
-
+.PP
 The entries in the "Action" column of the tables below specify
 the default disposition for each signal, as follows:
 .IP Term
@@ -90,11 +90,11 @@ It is possible to arrange that the signal handler
 uses an alternate stack; see
 .BR sigaltstack (2)
 for a discussion of how to do this and when it might be useful.)
-
+.PP
 The signal disposition is a per-process attribute:
 in a multithreaded application, the disposition of a
 particular signal is the same for all threads.
-
+.PP
 A child created via
 .BR fork (2)
 inherits a copy of its parent's signal dispositions.
@@ -174,7 +174,7 @@ which means that it will not be delivered until it is later unblocked.
 Between the time when it is generated and when it is delivered
 a signal is said to be
 .IR pending .
-
+.PP
 Each thread in a process has an independent
 .IR "signal mask" ,
 which indicates the set of signals that the thread is currently blocking.
@@ -183,13 +183,13 @@ A thread can manipulate its signal mask using
 In a traditional single-threaded application,
 .BR sigprocmask (2)
 can be used to manipulate the signal mask.
-
+.PP
 A child created via
 .BR fork (2)
 inherits a copy of its parent's signal mask;
 the signal mask is preserved across
 .BR execve (2).
-
+.PP
 A signal may be generated (and thus pending)
 for a process as a whole (e.g., when sent using
 .BR kill (2))
@@ -206,14 +206,14 @@ A process-directed signal may be delivered to any one of the
 threads that does not currently have the signal blocked.
 If more than one of the threads has the signal unblocked, then the
 kernel chooses an arbitrary thread to which to deliver the signal.
-
+.PP
 A thread can obtain the set of signals that it currently has pending
 using
 .BR sigpending (2).
 This set will consist of the union of the set of pending
 process-directed signals and the set of signals pending for
 the calling thread.
-
+.PP
 A child created via
 .BR fork (2)
 initially has an empty pending signal set;
@@ -231,7 +231,7 @@ and the last one for mips.
 .I not
 shown; see the Linux kernel source for signal numbering on that architecture.)
 A dash (\-) denotes that a signal is absent on the corresponding architecture.
-
+.PP
 First the signals described in the original POSIX.1-1990 standard.
 .TS
 l c c l
@@ -260,13 +260,13 @@ SIGTSTP	18,20,24	Stop	Stop typed at terminal
 SIGTTIN	21,21,26	Stop	Terminal input for background process
 SIGTTOU	22,22,27	Stop	Terminal output for background process
 .TE
-
+.sp 1
 The signals
 .B SIGKILL
 and
 .B SIGSTOP
 cannot be caught, blocked, or ignored.
-
+.PP
 Next the signals not in the POSIX.1-1990 standard but described in
 SUSv2 and POSIX.1-2001.
 .TS
@@ -288,7 +288,7 @@ SIGXCPU	24,24,30	Core	CPU time limit exceeded (4.2BSD);
 SIGXFSZ	25,25,31	Core	File size limit exceeded (4.2BSD);
 			see \fBsetrlimit\fP(2)
 .TE
-
+.sp 1
 Up to and including Linux 2.2, the default behavior for
 .BR SIGSYS ", " SIGXCPU ", " SIGXFSZ ", "
 and (on architectures other than SPARC and MIPS)
@@ -299,7 +299,7 @@ was to terminate the process (without a core dump).
 is to terminate the process without a core dump.)
 Linux 2.4 conforms to the POSIX.1-2001 requirements for these signals,
 terminating the process with a core dump.
-
+.PP
 Next various other signals.
 .TS
 l c c l
@@ -317,7 +317,7 @@ SIGLOST	\-,\-,\-	Term	File lock lost (unused)
 SIGWINCH	28,28,20	Ign	Window resize signal (4.3BSD, Sun)
 SIGUNUSED	\-,31,\-	Core	Synonymous with \fBSIGSYS\fP
 .TE
-
+.sp 1
 (Signal 29 is
 .B SIGINFO
 /
@@ -325,21 +325,21 @@ SIGUNUSED	\-,31,\-	Core	Synonymous with \fBSIGSYS\fP
 on an alpha but
 .B SIGLOST
 on a sparc.)
-
+.PP
 .B SIGEMT
 is not specified in POSIX.1-2001, but nevertheless appears
 on most other UNIX systems,
 where its default action is typically to terminate
 the process with a core dump.
-
+.PP
 .B SIGPWR
 (which is not specified in POSIX.1-2001) is typically ignored
 by default on those other UNIX systems where it appears.
-
+.PP
 .B SIGIO
 (which is not specified in POSIX.1-2001) is ignored by default
 on several other UNIX systems.
-
+.PP
 Where defined,
 .B SIGUNUSED
 is synonymous with
@@ -452,7 +452,7 @@ resource limit, which specifies a per-user limit for queued
 signals; see
 .BR setrlimit (2)
 for further details.
-
+.PP
 The addition of real-time signals required the widening
 of the signal set structure
 .RI ( sigset_t )
@@ -488,7 +488,7 @@ flag (see
 .BR sigaction (2)).
 The details vary across UNIX systems;
 below, the details for Linux.
-
+.PP
 If a blocked call to one of the following interfaces is interrupted
 by a signal handler, then the call will be automatically restarted
 after the signal handler returns if the
@@ -674,7 +674,7 @@ and then resumed via
 .BR SIGCONT .
 This behavior is not sanctioned by POSIX.1, and doesn't occur
 on other systems.
-
+.PP
 The Linux interfaces that display this behavior are:
 .IP * 2
 "Input" socket interfaces, when a timeout