readme and insecure flag docs fixed

README.md

@@ -24,6 +24,10 @@ If you like tracepusher and want to do the same thing with logs, check out [logp
 
 See [try tracepusher in-browser without installation](https://agardnerit.github.io/tracepusher/try/).
 
+## Standalone Binary
+
+See [download and use tracepusher as a standalone binary](https://agardnerit.github.io/tracepusher/usage/standalone.md)
+
 ## Python3 Usage
 
 See [use tracepusher as a Python script](https://agardnerit.github.io/tracepusher/usage/python).

docs/reference/insecure-flag.md

@@ -18,22 +18,23 @@ The `--insecure` is not available
 
 The `--insecure` flag defaults to `false` with the intention of meaning insecure endpoints are not allowed. However, to provide ample migration time for end users, the behaviour is as follows:
 
-- `--insecure` flag is omitted
+#### `--insecure` flag is omitted
 
-  This is the expected behaviour of everyone migrating from v0.8 to v0.9.
-  The flag defaults to `false` BUT will still allow `http://` endpoints, just like before.
+This is the expected behaviour of everyone migrating from v0.8 to v0.9.
+
+The flag defaults to `false` BUT will still allow `http://` endpoints, just like before.
 
-  Tracepusher will emit a soft `WARNING` message to inform users of the upcoming breaking change, like this:
+Tracepusher will emit a soft `WARNING` message to inform users of the upcoming breaking change, like this:
 
-  ```
-  WARN: --insecure flag is omitted or is set to false. Prior to v1.0 tracepusher still works as expected (span is sent). In v1.0 and above, you MUST set '--insecure true' if you want to send to an http:// endpoint. See https://github.com/agardnerIT/tracepusher/issues/78
-  ```
+```
+WARN: --insecure flag is omitted or is set to false. Prior to v1.0 tracepusher still works as expected (span is sent). In v1.0 and above, you MUST set '--insecure true' if you want to send to an http:// endpoint. See https://github.com/agardnerIT/tracepusher/issues/78
+```
 
-- `--insecure` flag is explicitly set to false
+#### `--insecure` flag is explicitly set to false
 
-  From v0.9 upwards, users are encouraged to get into the best practice habit of explicitly setting this to `false` or `true`.
+From v0.9 upwards, users are encouraged to get into the best practice habit of explicitly setting this to `false` or `true`.
 
-  Otherwise, for v0.9.*, the behaviour is as above.
+Otherwise, for v0.9.*, the behaviour is as above.
 
 ### v1.0