(split) LDP_man-pages: update original to v3.34.

[linuxjm/LDP_man-pages.git] / original / man7 / path_resolution.7

diff --git a/original/man7/path_resolution.7 b/original/man7/path_resolution.7
index 7c10c71..5d3dc36 100644 (file)
--- a/original/man7/path_resolution.7
+++ b/original/man7/path_resolution.7
@@ -24,7 +24,7 @@
 .SH NAME
 path_resolution \- how a pathname is resolved to a file
 .SH DESCRIPTION
-Some Unix/Linux system calls have as parameter one or more filenames.
+Some UNIX/Linux system calls have as parameter one or more filenames.
 A filename (or pathname) is resolved as follows.
 .SS "Step 1: Start of the resolution process"
 If the pathname starts with the \(aq/\(aq character,
@@ -156,9 +156,9 @@ If the pathname (or some
 intermediate pathname obtained while resolving symbolic links)
 is too long, an
 .B ENAMETOOLONG
-error is returned ("File name too long").
+error is returned ("Filename too long").
 .SS "Empty pathname"
-In the original Unix, the empty pathname referred to the current directory.
+In the original UNIX, the empty pathname referred to the current directory.
 Nowadays POSIX decrees that an empty pathname must not be resolved
 successfully.
 Linux returns
@@ -201,7 +201,7 @@ See
 .BR setfsgid (2).
 .\" FIXME say something about file system mounted read-only ?
 .SS "Bypassing permission checks: superuser and capabilities"
-On a traditional Unix system, the superuser
+On a traditional UNIX system, the superuser
 .RI ( root ,
 user ID 0) is all-powerful, and bypasses all permissions restrictions
 when accessing files.