Rename $IsOSX to $IsMacOS (#4757)

docs/learning-powershell/create-powershell-scripts.md

@@ -44,7 +44,7 @@ If you would like to author one script that will return the IP address across Li
 
 ```PowerShell
 # Script to return current IPv4 addresses for Linux, MacOS, or Windows
-$IP = if ($IsLinux -or $IsOSX) {
+$IP = if ($IsLinux -or $IsMacOS) {
     $ipInfo = ifconfig | Select-String 'inet'
     $ipInfo = [regex]::matches($ipInfo,"addr:\b(?:\d{1,3}\.){3}\d{1,3}\b") | ForEach-Object value
     foreach ($ip in $ipInfo) {

docs/maintainers/releasing.md

@@ -35,7 +35,7 @@ This is to help track the release preparation work.
      Delete the `docker` branch once the builds succeed.
    - Windows: queue a new build in `PowerShell Windows Docker Build` on VSTS.
 1. Verify the generated docker container images.
-1. [Update the homebrew formula](#homebrew) for the OSX package.
+1. [Update the homebrew formula](#homebrew) for the macOS package.
    This task usually will be taken care of by the community,
    so we can wait for one day or two and see if the homebrew formula has already been updated,
    and only do the update if it hasn't.
@@ -43,7 +43,7 @@ This is to help track the release preparation work.
 ## Building Packages
 
 > Note: Linux and Windows packages are taken care of by our release build pipeline in VSTS,
-while the OSX package needs to be built separately on a macOS.
+while the macOS package needs to be built separately on a macOS.
 
 The release build should be started based on the `release` branch.
 The release Git tag won't be created until all release preparation tasks are done,

docs/testing-guidelines/TestRoadmap.md

@@ -17,8 +17,8 @@ This will provide us much needed visibility in how PowerShell Core is being used
 We already have infrastructure in place to allow us see how PowerShell Core is being used, by collecting telemetry from PowerShell Core, we can improve our confidence as we drive to production quality.
 
 ### Logging
-The code which on Windows create ETW logging has been completely stubbed out on Linux/OSX.
-We should take advantage of the native logging mechanisms on Linux/OSX and implement a logger similar to the ETW logger on Windows using Syslog (or equivalent).
+The code which on Windows create ETW logging has been completely stubbed out on Linux/macOS.
+We should take advantage of the native logging mechanisms on Linux/macOS and implement a logger similar to the ETW logger on Windows using Syslog (or equivalent).
 We could use this data during test runs to identify test gaps.
 Simply by capturing the cmdlets and their parameters which are invoked during test would illuminate the gaps we have in our current tests, and allow us to easily fill them.
 It is not sufficient to support only one platform because we have many tests which determine at runtime whether or not it should run based on OS, so data from Windows will not be the same as that from Linux or MacOS.
@@ -69,7 +69,7 @@ In addition to loopback tests using both WSMan and SSH protocols, we should have
 * Windows Client->Nano Server
 * Windows Client->Linux Server
 * Linux Client -> Windows Server
-* OSX Client -> Nano Client
+* macOS Client -> Nano Client
 * PowerShell Core Client -> Full PowerShell Server
 * Full PowerShell Client -> PowerShell Core Server
 * Downlevel Full PowerShell Client -> PowerShell Core Server