Update README Instructions (#3)

Author: suyashkumar

README.md

@@ -1,18 +1,26 @@
 # ssl-proxy
-A simple Golang SSL reverse proxy that serves traffic over HTTPS and proxies it to any other web server you might be running. Overall, a simple way to add SSL/TLS to a web service. `ssl-proxy` will auto-generate self-signed certificates for you if none are provided to it (useful for things like `jupyter` notebooks in a pinch). 
+A simple Golang SSL reverse proxy that serves traffic over HTTPS and proxies it to any other web server you might be running. `ssl-proxy` will auto-generate self-signed certificates for you if none are provided to it (useful for things like `jupyter` notebooks in a pinch). Usage is simple:
+## Usage
+```sh
+ssl-proxy -from 0.0.0.0:4430 -to 127.0.0.1:8000
+```
+This will immediately generate self-signed certificates and being proxying HTTPS traffic from https://0.0.0.0:4430 to http://127.0.0.1:8000. No need to ever call openssl. It will print the SHA256 fingerprint of the cert being used for you to perform manual certificate verification in the browser if you would like (before you "trust" the cert).
 
 I know `nginx` is often used for stuff like this, but I got tired of dealing with the boilerplate and wanted to explore something fun. So I ended up throwing this together. 
 
-## Quick Start
+### Provide your own certs
 ```sh
-ssl-proxy -from 0.0.0.0:4430 -to http://127.0.0.1:8000
+ssl-proxy -cert cert.pem -key myKey.pem -from 0.0.0.0:4430 -to 127.0.0.1:8000
 ```
-This will immediately generate self-signed certificates and being proxying HTTPS traffic from `0.0.0.0:4430` to `http://127.0.0.1:8000`. No need to ever call `openssl`. 
+You can provide your own existing certs, of course. Jenkins still has issues serving the fullchain certs from letsencrypt properly, so this tool has come in handy for me there. 
 
-It will output the SHA256 fingerprint for you to perform manual certificate verification in the browser if needed (before you "trust" the cert). 
+## Installation
+Simply download and uncompress the proper prebuilt binary for your system from the [releases tab](https://github.com/suyashkumar/ssl-proxy/releases/). Then, add the binary to your path or start using it locally (`./ssl-proxy`).
 
-## Provide your own certs
+If you're using `wget`, you can fetch and uncompress the proper binary in one command:
 ```sh
-ssl-proxy -cert cert.pem -key myKey.pem -from 0.0.0.0:4430 -to http://127.0.0.1:8000
+wget -qO- $BINARY_RELEASE_LINK | tar xvz
 ```
-You can provide your own existing certs, of course. Jenkins still has issues serving the fullchain certs from letsencrypt properly, so this tool has come in handy for me there. 
+
+### Build from source
+You must have Golang installed on your system along with `make`. Then simply clone the repository and run `make`.