X-Git-Url: https://git.gag.com/?p=web%2Fgag.com;a=blobdiff_plain;f=bdale%2Fblog%2Fposts%2FStrong_Keys.mdwn;h=beb5ff8d0b5f674443b4fe616ff149f020fd6312;hp=a25838bd2d47086dea424f449c2f1925c52098b9;hb=d54652281d5b87b22e63ab31e8cd19411a453adb;hpb=b96b2172effe99a3c2273b3198742bd8dd13ac9f

diff --git a/bdale/blog/posts/Strong_Keys.mdwn b/bdale/blog/posts/Strong_Keys.mdwn
index a25838b..beb5ff8 100644
--- a/bdale/blog/posts/Strong_Keys.mdwn
+++ b/bdale/blog/posts/Strong_Keys.mdwn
@@ -49,7 +49,7 @@ It bothered me that I had generated weak signatures with my new strong key,
 so I decided to re-sign the keys I had already signed with my new key so that
 all the signatures issued with my new strong key are strong signatures.  To
 do this, I used gpg's --edit-key option with gpg warped to point to 
-the caff home to 'delsig' the signatures I'd made to these keys, then use caff
+the caff home to 'delsig' the signatures I'd made to these keys, then used caff
 with the '--no-download' option to re-sign the keys and re-issue the associated
 emails.  Trolling ~/.caff/keys helped me discover which keys were in the 
 affected set, then I studied the command lines caff was feeding to gpg to