Update README.md

README.md

@@ -18,7 +18,7 @@ The MHL file generated on the sending side and verified on the receiving side fu
 
 ## System requirements
 - The [MHL tool](https://github.com/pomfort/mhl-tool) should be installed into your `$PATH`. On CentOS 7.7 and Fedora 31, after compiling from source so that `mhl` will call the properly installed versions of the OpenSSL libraries, it is [recommended](https://unix.stackexchange.com/questions/8656/usr-bin-vs-usr-local-bin-on-linux/8658#8658) that you manually move the `mhl` binary into `/usr/local/bin`, since the program will not be managed by the distribution's package manager.
-- The [`.pkg` installer from Pomfort]() will install a precompiled binary for macOS into `/usr/local/bin`, which is included by default in macOS's `$PATH`.
+- The [`.pkg` installer from Pomfort](http://download.pomfort.com/mhl-tool.zip) will install a precompiled binary for macOS into `/usr/local/bin`, which is included by default in macOS's `$PATH`.
 - On Windows, download and extract [the precompiled binary from Pomfort](http://download.pomfort.com/mhl-tool.zip), and then copy or move `mhl.exe` into `C:\Windows\System32\`, which is included by default in the Windows `Path` system environment variables.
 - The [AWS CLI](https://aws.amazon.com/cli/) should be installed and configured on both endpoints, with:
   - The sending IAM user having at least full S3 write access on the AWS account