(split) LDP: Update original to LDP v3.54

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

diff --git a/original/man7/symlink.7 b/original/man7/symlink.7
index b4ca88a..236b88b 100644 (file)
--- a/original/man7/symlink.7
+++ b/original/man7/symlink.7
@@ -47,22 +47,22 @@ it is a reference to the object underlying the original filename.
 the same
 .IR "i-node number" ,
 where an i-node number is an index into the i-node table,
-which contains metadata about all files on a file system.
+which contains metadata about all files on a filesystem.
 See
 .BR stat (2).)
 Changes to a file are independent of the name used to reference the file.
 Hard links may not refer to directories
-(to prevent the possibility of loops within the file system tree,
+(to prevent the possibility of loops within the filesystem tree,
 which would confuse many programs)
-and may not refer to files on different file systems
-(because i-node numbers are not unique across file systems).
+and may not refer to files on different filesystems
+(because i-node numbers are not unique across filesystems).
 
 A symbolic link is a special type of file whose contents are a string
 that is the pathname another file, the file to which the link refers.
 In other words, a symbolic link is a pointer to another name,
 and not to an underlying object.
 For this reason, symbolic links may refer to directories and may cross
-file system boundaries.
+filesystem boundaries.
 
 There is no requirement that the pathname referred to by a symbolic link
 should exist.
@@ -70,7 +70,7 @@ A symbolic link that refers to a pathname that does not exist is said
 to be a
 .IR "dangling link" .
 
-Because a symbolic link and its referenced object coexist in the file system
+Because a symbolic link and its referenced object coexist in the filesystem
 name space, confusion can arise in distinguishing between the link itself
 and the referenced object.
 On historical systems,