Minor readme changes

HACKING.md

@@ -14,13 +14,12 @@ comprehensive; you could craft commands that lead to undefined
 behaviour.  If you have `socat`, you can use the control socket
 interactively like this:
 ```sh
-rlwrap socat STDIN UNIX-CONNECT:control.sock
-```
-`rlwrap` only adds line editing and is optional. If you don't have it
-you can still get (inferior) line editing by doing:
-```sh
 socat READLINE UNIX-CONNECT:control.sock
 ```
+If you have it, you can use `rlwrap` to get line editing that's a bit nicer:
+```sh
+rlwrap socat STDIN UNIX-CONNECT:control.sock
+```
 Once connected, type "help" and press enter to get a list of commands.
 
 ### Event socket

README.md

@@ -29,14 +29,14 @@ source venv/bin/activate
 python -m pip install -r requirements.txt
 ```
 
-Before you run it you may want to edit the config ([/config.toml][config]).
-Most of the defaults are probably okay, but here are some that you might want
-to know what they do:
+This is all the setup needed to run the application, but before you do you may
+want to edit the config ([/config.toml][config]).  Most of the defaults are
+probably okay, but here are some that you might want to know what they do:
 
 * `secret_key`:
   used for cryptography, make it any long random string (e.g.
-  `$ dd if=/dev/urandom bs=16 count=1 | base64`), definitely set this
-  yourself before running in "production" (whatever that is for you)
+  `$ dd if=/dev/urandom bs=16 count=1 | base64`); set this
+  before running in "production"
 
 * `segments/directory`:
   directory containing stream segments, the default is `stream/` in