intro.1, time.1, accept.2, bind.2, connect.2, execve.2, flock.2, getdents.2, getprior...

[thirdparty/man-pages.git] / man7 / signal.7

diff --git a/man7/signal.7 b/man7/signal.7
index 8c418f857d3cb8d401773e704d46c21f4a4cadca..cd55cc9644659b698acd2a8abe4321fca90b95f4 100644 (file)
--- a/man7/signal.7
+++ b/man7/signal.7
@@ -287,7 +287,7 @@ Up to and including Linux 2.2, the default behavior for
 and (on architectures other than SPARC and MIPS)
 .B SIGBUS
 was to terminate the process (without a core dump).
-(On some other Unix systems the default action for
+(On some other UNIX systems the default action for
 .BR SIGXCPU " and " SIGXFSZ
 is to terminate the process without a core dump.)
 Linux 2.4 conforms to the POSIX.1-2001 requirements for these signals,
@@ -321,17 +321,17 @@ on a sparc.)
 
 .B SIGEMT
 is not specified in POSIX.1-2001, but nevertheless appears
-on most other Unix systems,
+on most other UNIX systems,
 where its default action is typically to terminate
 the process with a core dump.
 
 .B SIGPWR
 (which is not specified in POSIX.1-2001) is typically ignored
-by default on those other Unix systems where it appears.
+by default on those other UNIX systems where it appears.
 
 .B SIGIO
 (which is not specified in POSIX.1-2001) is ignored by default
-on several other Unix systems.
+on several other UNIX systems.
 
 Where defined,
 .B SIGUNUSED
@@ -362,7 +362,7 @@ suitably (to 34 or 35).
 Because the range of available real-time signals varies according
 to the glibc threading implementation (and this variation can occur
 at run time according to the available kernel and glibc),
-and indeed the range of real-time signals varies across Unix systems,
+and indeed the range of real-time signals varies across UNIX systems,
 programs should
 .IR "never refer to real-time signals using hard-coded numbers" ,
 but instead should always refer to real-time signals using the notation
@@ -621,7 +621,7 @@ whether or not the signal handler was established using the
 .BR SA_RESTART
 flag (see
 .BR sigaction (2)).
-The details vary across Unix systems;
+The details vary across UNIX systems;
 below, the details for Linux.
 
 If a blocked call to one of the following interfaces is interrupted