OS X → macOS

README.md

@@ -22,7 +22,7 @@ Objective-C has come a long way in the past nine years and UKKQueue was long in
 	-- The code is *much* cleaner and simpler!
 	-- There is only one .h and one .m file to include.
 
-VDKQueue also fixes long-standing bugs in UKKQueue. For example: OS X limits the number of open file descriptors each process
+VDKQueue also fixes long-standing bugs in UKKQueue. For example: macOS limits the number of open file descriptors each process
 may have to about 3,000. If UKKQueue fails to open a new file descriptor because it has hit this limit, it will crash. VDKQueue will not.
 
 

VDKQueue.h

@@ -30,7 +30,7 @@
 //      VDKQueue is also simplified. The option to use it as a singleton is removed. You simply alloc/init an instance and add paths you want to
 //      watch. Your objects can be alerted to changes either by notifications or by a delegate method (or both). See below. 
 //
-//      It also fixes several bugs. For one, it won't crash if it can't create a file descriptor to a file you ask it to watch. (By default, an OS X process can only
+//      It also fixes several bugs. For one, it won't crash if it can't create a file descriptor to a file you ask it to watch. (By default, a macOS process can only
 //      have about 3,000 file descriptors open at once. If you hit that limit, UKKQueue will crash. VDKQueue will not.)
 //
 
@@ -43,7 +43,7 @@
 //
 //  IMPORTANT NOTE ABOUT ATOMIC OPERATIONS
 //
-//      There are two ways of saving a file on OS X: Atomic and Non-Atomic. In a non-atomic operation, a file is saved by directly overwriting it with new data.
+//      There are two ways of saving a file on macOS: Atomic and Non-Atomic. In a non-atomic operation, a file is saved by directly overwriting it with new data.
 //      In an Atomic save, a temporary file is first written to a different location on disk. When that completes successfully, the original file is deleted and the
 //      temporary one is renamed and moved into place where the original file existed.
 //