Capitalization, https, $(sysctl -n hw.availcpu)

Building-OpenRCT2-on-macOS-using-CMake.md

@@ -1,9 +1,9 @@
 To build natively on macOS, without using Xcode, you will need a set of libraries set up. This guide assumes you already have the following installed:
 
-- a copy of the game files, downloaded onto your machine.
+- A copy of the game files, downloaded onto your machine.
 - OS X Developer Tools
-- [Homebrew](http://brew.sh/) / MacPorts / Fink
-- Optional: Xcode
+- [Homebrew](https://brew.sh/) / MacPorts / Fink
+- Xcode *(optional)*
 
 ## Installing libraries
 
@@ -17,15 +17,15 @@ brew install cmake duktape freetype icu4c libpng libzip nlohmann-json openssl pk
 Navigate to the directory OpenRCT2 is in (`cd`), then make a build directory and invoke `cmake`:
 ```bash
 cd /path/to/repo/OpenRCT2
-mkdir build && cd ./build
+mkdir build && cd build
 cmake .. -DCMAKE_INSTALL_PREFIX=./install
-make -j4 install # the install step builds openrct, g2 and downloads OpenRCT2 data
+make -j$(sysctl -n hw.availcpu) install # the install step builds openrct, g2 and downloads OpenRCT2 data
 ```
 
 If any libraries are missing, you will see an error message. Adjust as needed or check out the `Troubleshooting` section below.
 Once all errors have been fixed we can start building:
 ```bash
-make -j4 install
+make -j$(sysctl -n hw.availcpu) install
 ```
 
 Now, before executing the game, link the just installed openrct2 data folder to the current directory to help `openrct2` find it. Then run the game. 
@@ -37,7 +37,7 @@ ln -s ./install/share/openrct2 data
 
 After the first install, you can build the `openrct2` binaries, no install required:
 ```bash
-make -j4
+make -j$(sysctl -n hw.availcpu)
 ```
 
 ### Troubleshooting
@@ -128,4 +128,4 @@ cmake ..
 
 Fire up the binary or application you just built. You should be good to go!
 
-That's it! If you run into problems please paste all of the information you have into a github issue and we'll take a look.
+That's it! If you run into problems please paste all of the information you have into a GitHub issue and we'll take a look.