1 files changed, 14 insertions, 14 deletions
diff --git a/man7/unix.7 b/man7/unix.7
index 3ee333d61b..79effbe8d7 100644
--- a/man7/unix.7
+++ b/man7/unix.7
@@ -31,7 +31,7 @@ The
 .BR AF_LOCAL )
 socket family is used to communicate between processes on the same machine
 efficiently.
-Traditionally, Unix sockets can be either unnamed,
+Traditionally, UNIX sockets can be either unnamed,
 or bound to a file system pathname (marked as being of type socket).
 Linux also supports an abstract namespace which is independent of the
 file system.
@@ -41,17 +41,17 @@ Valid types are:
 for a stream-oriented socket and
 .BR SOCK_DGRAM ,
 for a datagram-oriented socket that preserves message boundaries
-(as on most Unix implementations, Unix domain datagram
+(as on most UNIX implementations, UNIX domain datagram
 sockets are always reliable and don't reorder datagrams);
 and (since Linux 2.6.4)
 .BR SOCK_SEQPACKET ,
 for a connection-oriented socket that preserves message boundaries
 and delivers messages in the order that they were sent.
 
-Unix sockets support passing file descriptors or process credentials
+UNIX sockets support passing file descriptors or process credentials
 to other processes using ancillary data.
 .SS Address Format
-A Unix domain socket address is represented in the following structure:
+A UNIX domain socket address is represented in the following structure:
 .in +4n
 .nf
 
@@ -71,7 +71,7 @@ always contains
 Three types of address are distinguished in this structure:
 .IP * 3
 .IR pathname :
-a Unix domain socket can be bound to a null-terminated file
+a UNIX domain socket can be bound to a null-terminated file
 system pathname using
 .BR bind (2).
 When the address of the socket is returned by
@@ -169,9 +169,9 @@ followed by 5 bytes in the character set
 (Thus, there is a limit of 2^20 autobind addresses.)
 .SS Sockets API
 The following paragraphs describe domain-specific details and
-unsupported features of the sockets API for Unix domain sockets on Linux.
+unsupported features of the sockets API for UNIX domain sockets on Linux.
 
-Unix domain sockets do not support the transmission of
+UNIX domain sockets do not support the transmission of
 out-of-band data (the
 .B MSG_OOB
 flag for
@@ -182,7 +182,7 @@ and
 The
 .BR send (2)
 .B MSG_MORE
-flag is not supported by Unix domain sockets.
+flag is not supported by UNIX domain sockets.
 
 The use of
 .B MSG_TRUNC
@@ -190,11 +190,11 @@ in the
 .I flags
 argument of
 .BR recv (2)
-is not supported by Unix domain sockets.
+is not supported by UNIX domain sockets.
 
 The
 .B SO_SNDBUF
-socket option does have an effect for Unix domain sockets, but the
+socket option does have an effect for UNIX domain sockets, but the
 .B SO_RCVBUF
 option does not.
 For datagram sockets, the
@@ -233,7 +233,7 @@ The passed file descriptors behave as though they have been created with
 .BR dup (2).
 .TP
 .B SCM_CREDENTIALS
-Send or receive Unix credentials.
+Send or receive UNIX credentials.
 This can be used for authentication.
 The credentials are passed as a
 .I struct ucred
@@ -398,7 +398,7 @@ Creation of a new socket will fail if the process does not have write and
 search (execute) permission on the directory the socket is created in.
 Connecting to the socket object requires read/write permission.
 This behavior differs from many BSD-derived systems which
-ignore permissions for Unix sockets.
+ignore permissions for UNIX sockets.
 Portable programs should not rely on
 this feature for security.
 
@@ -406,7 +406,7 @@ Binding to a socket with a filename creates a socket
 in the file system that must be deleted by the caller when it is no
 longer needed (using
 .BR unlink (2)).
-The usual Unix close-behind semantics apply; the socket can be unlinked
+The usual UNIX close-behind semantics apply; the socket can be unlinked
 at any time and will be finally removed from the file system when the last
 reference to it is closed.
 
@@ -419,7 +419,7 @@ or
 .BR recvmsg (2)
 call.
 
-Unix domain stream sockets do not support the notion of out-of-band data.
+UNIX domain stream sockets do not support the notion of out-of-band data.
 .SH EXAMPLE
 See
 .BR bind (2).