From f8880975b8c5d2a3fdf779a85453748701a526cf Mon Sep 17 00:00:00 2001
From: Thomas A Caswell <tcaswell@gmail.com>
Date: Mon, 26 Aug 2019 21:10:19 -0400
Subject: [PATCH] DOC: justify why you would want to sign your new key

---
 README.md | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 5f59497..ed476c0 100644
--- a/README.md
+++ b/README.md
@@ -416,16 +416,25 @@ Export the key ID as a [variable](https://stackoverflow.com/questions/1158091/de
 $ export KEYID=0xFF3E7D88647EBCDB
 ```
 
-# Sign with an existing key (if you have one)
+# Sign with an existing key (optional)
 
-Export your existing key to move it to the working keyring.  From a different terminal do:
+If you already have a pgp key you may want want to sign your new key
+with the old one to help prove that your new key is infact controlled
+by you.
 
-   $ gpg --export-secret-keys --armor --output /tmp/new.sec
+Export your existing key to move it to the working keyring.  From a
+different terminal do:
 
-and then
+```console
+$ gpg --export-secret-keys --armor --output /tmp/new.sec
+```
+
+to export your old key and then
 
-   $ gpg  --default-key $OLDKEY --sign-key $KEYID
 
+```console
+$ gpg  --default-key $OLDKEY --sign-key $KEYID
+```
 
 # Sub-keys