Update OS X nomenaclature to macOS

Author: daviwil

README.md

@@ -10,7 +10,7 @@ that Visual Studio Code provides.
 
 - **Windows 7 through 10** with PowerShell v3 and higher
 - **Linux** with PowerShell v6 (all PowerShell-supported distribtions)
-- **Mac OS X** with PowerShell v6
+- **macOS and OS X** with PowerShell v6
 
 Read the [installation instructions](https://github.com/PowerShell/PowerShell/blob/master/docs/learning-powershell/using-vscode.md)
 to get more details on how to use the extension on these platforms.
@@ -67,7 +67,7 @@ Restart Visual Studio Code and try to reproduce the problem.  Once you are done
 that, zip up the logs in the corresponding folder for your operating system:
 
 - **Windows**: `$HOME\.vscode\extensions\ms-vscode.PowerShell-<CURRENT VERSION>\logs`
-- **Linux and Mac OS X**: `~/.vscode/extensions/ms-vscode.PowerShell-<CURRENT VERSION>/logs`
+- **Linux and macOS**: `~/.vscode/extensions/ms-vscode.PowerShell-<CURRENT VERSION>/logs`
 
 You have two options for sending us the logs:
 

docs/troubleshooting.md

@@ -3,11 +3,11 @@
 This document contains troubleshooting steps for commonly reported issues when using the
 PowerShell extension for Visual Studio Code.
 
-## Mac OS X
+## macOS (OS X)
 
 ### 1. PowerShell IntelliSense does not work, can't debug scripts
 
-The most common problem when the PowerShell extension doesn't work on Mac OS X is that
+The most common problem when the PowerShell extension doesn't work on macOS is that
 OpenSSL is not installed.  You can check for the installation of OpenSSL by looking for
 the following files:
 
@@ -30,7 +30,7 @@ do not have OpenSSL installed.
 
 #### Installing OpenSSL via Homebrew
 
-We **highly recommend** that you use [Homebrew](http://brew.sh) to install OpenSSL.  The PowerShell distribution for OS X
+We **highly recommend** that you use [Homebrew](http://brew.sh) to install OpenSSL.  The PowerShell distribution for macOS
 has built-in support for Homebrew's OpenSSL library paths.  If you install with Homebrew, you will avoid
 [security concerns](https://github.com/PowerShell/PowerShell/blob/master/docs/installation/linux.md#openssl)
 around creating symbolic links in your `/usr/local/lib` path which are needed when using other means of installation.

src/session.ts

@@ -454,15 +454,15 @@ export class SessionManager {
         else if (os.platform() == "darwin") {
             powerShellExePath = "/usr/local/bin/powershell";
 
-            // Check for OpenSSL dependency on OS X.  Look for the default Homebrew installation
+            // Check for OpenSSL dependency on macOS.  Look for the default Homebrew installation
             // path and if that fails check the system-wide library path.
             if (!(utils.checkIfFileExists("/usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib") &&
                   utils.checkIfFileExists("/usr/local/opt/openssl/lib/libssl.1.0.0.dylib")) &&
                 !(utils.checkIfFileExists("/usr/local/lib/libcrypto.1.0.0.dylib") &&
                   utils.checkIfFileExists("/usr/local/lib/libssl.1.0.0.dylib"))) {
                     var thenable =
                         vscode.window.showWarningMessage(
-                            "The PowerShell extension will not work without OpenSSL on Mac OS X",
+                            "The PowerShell extension will not work without OpenSSL on macOS and OS X",
                             "Show Documentation");
 
                     thenable.then(