intro section improvements

README.md

@@ -6,8 +6,11 @@ Although this guide was written for OS X, most commands should work in other ope
 
 [Discussion](https://news.ycombinator.com/item?id=12289481) on Hacker News.
 
-> **Note**: If you **don't** want to use Keybase.io, it is still fine. For section **Create a new GPG key on keybase.io**, **Set up Git to sign all commits**, and **Add public GPG key to GitHub** you follow a guide [here](https://help.github.com/articles/generating-a-new-gpg-key/) instead. It will give you a same result. Also for section **Import key to GPG on another host** you can follow step in this [answer](http://stackoverflow.com/a/3176373/571227) from Stackoverflow to export and import key. Both of key generation and import/export action don't involve Keybase.io
+> **Note**: If you **don't** want to use Keybase.io, follow [this guide][1] instead.
+> For manually transferring keys to different hosts, check out this [answer on Stack Overflow][2].
 
+[1]: https://help.github.com/articles/generating-a-new-gpg-key/
+[2]: https://stackoverflow.com/a/3176373/571227
 
 ## Requirements
 
@@ -89,7 +92,7 @@ If you use a UI such as Git Tower or Github Desktop, you may need to configure g
 git config --global gpg.program $(which gpg)
 ```
 
-## Optional: Disable TTY 
+## Optional: Disable TTY
 If you have problems with making autosigned commits from IDE or other software add no-tty config
 ```sh
 $ $EDITOR ~/.gnupg/gpg.conf