Unified naming of the Mac to 'macOS' as other names are outdated sinc…

…e 2016 (macOS Sierra, version 10.12)

doc/FileSystem.3

@@ -735,7 +735,7 @@ filesystems, so that they can easily retrieve the native (char* or
 TCHAR*) representation of a path. This function is a convenience
 wrapper around \fBTcl_FSGetInternalRep\fR. It may be desirable in the
 future to have non-string-based native representations (for example,
-on MacOSX, a representation using a fileSpec of FSRef structure would
+on macOS, a representation using a fileSpec of FSRef structure would
 probably be more efficient). On Windows a full Unicode representation
 would allow for paths of unlimited length. Currently the representation
 is simply a character string which may contain either the relative path

doc/exec.n

@@ -335,7 +335,7 @@ the caller must prepend the desired command with
 because built-in commands are not implemented using executables.
 .RE
 .TP
-\fBUnix\fR (including Mac OS X)
+\fBUnix\fR (including macOS)
 .
 The \fBexec\fR command is fully functional and works as described.
 .SH "UNIX EXAMPLES"

doc/file.n

@@ -78,7 +78,7 @@ names, the long name is retained. This attribute cannot be set.
 \fB\-system\fR gives or sets or clears the value of the system
 attribute of the file.
 .PP
-On Mac OS X and Darwin, \fB\-creator\fR gives or sets the
+On macOS and Darwin, \fB\-creator\fR gives or sets the
 Finder creator type of the file. \fB\-hidden\fR gives or sets or clears
 the hidden attribute of the file. \fB\-readonly\fR gives or sets or
 clears the readonly attribute of the file. \fB\-rsrclength\fR gives

doc/filename.n

@@ -42,7 +42,7 @@ The rules for native names depend on the value reported in the Tcl
 .TP 10
 \fBUnix\fR
 .
-On Unix and Apple MacOS X platforms, Tcl uses path names where the
+On Unix and Apple macOS platforms, Tcl uses path names where the
 components are separated by slashes.  Path names may be relative or
 absolute, and file names may contain any character other than slash.
 The file names \fB\&.\fR and \fB\&..\fR are special and refer to the
@@ -155,7 +155,7 @@ user. If the tilde is followed immediately by a separator, the
 \fB$HOME\fR environment variable is substituted. Otherwise the characters
 between the tilde and the next separator are taken as a user name, which is
 used to retrieve the user's home directory for substitution. This works on
-POSIX, MacOS X and Windows platforms.
+POSIX, macOS and Windows platforms.
 .SH "PORTABILITY ISSUES"
 .PP
 Not all file systems are case sensitive, so scripts should avoid code

doc/glob.n

@@ -102,11 +102,11 @@ a directory will be returned if \fB\-types d\fR was specified.
 The second form specifies types where all the types given must match.
 These are \fIr\fR, \fIw\fR, \fIx\fR as file permissions, and
 \fIreadonly\fR, \fIhidden\fR as special permission cases. On the
-Macintosh, MacOS types and creators are also supported, where any item
-which is four characters long is assumed to be a MacOS type
+Macintosh, macOS types and creators are also supported, where any item
+which is four characters long is assumed to be a macOS type
 (e.g. \fBTEXT\fR). Items which are of the form \fI{macintosh type XXXX}\fR
 or \fI{macintosh creator XXXX}\fR will match types or creators
-respectively. Unrecognized types, or specifications of multiple MacOS
+respectively. Unrecognized types, or specifications of multiple macOS
 types/creators will signal an error.
 .PP
 The two forms may be mixed, so \fB\-types {d f r w}\fR will find all