* pgp-clean:

[pgp-tools.git] / caff / README.many-keys

diff --git a/caff/README.many-keys b/caff/README.many-keys
index d624eea047e800ba2d47638536aa210b2d6af34b..1fe8eb11ba6c45daea4022d23b31e23518b6b57e 100644 (file)
--- a/caff/README.many-keys
+++ b/caff/README.many-keys
@@ -2,7 +2,7 @@ Using caff to sign lots of keys
 -------------------------------
 
 If you have loads of keys to sign (sometimes, there are keysigning parties with
-more than 100 participants), keysigning can be arkward, even with caff. It gets
+more than 100 participants), keysigning can be awkward, even with caff. It gets
 worse if you have multiple local keys and want to sign with all.
 
 Some hints to get the signing done faster:
@@ -11,7 +11,8 @@ Some hints to get the signing done faster:
 
   caff and gpg allow you to specify the full fingerprint. This will save you
   from having to check the fingerprint yourself. If you have a text file with
-  all fingerprints, use that and then run
+  all fingerprints (with all the spaces stripped from them), use that and then
+  run
 
   $ caff <options> `cat ksp-fingerprints.txt`
 
@@ -43,8 +44,8 @@ Some hints to get the signing done faster:
   caff will send out all previously done signatures in the message. (Of course
   you have to configure $CONFIG{'keyid'} to contain all your key ids.)
 
-  $ caff --no-export-old --no-mail -u <mykey1> <other_key>
-  $ caff --no-download --no-export-old -u <mykey2> <other_key>
+  $ caff --no-export-old --no-mail -u <mykey1> <keyids to sign>
+  $ caff --no-download --no-export-old -u <mykey2> <keyids to sign>
 
 * Use gpg-agent.