Possible errata for FAQ file

[gnupg-doc@gnupg.org]

--- ../share/src/gnupg/gnupg-1.0.1h/doc/FAQ	Mon Jun  5 21:34:34 2000
+++ FAQ	Mon Jul  3 14:35:42 2000
@@ -126,7 +126,7 @@
        gpg --rfc1991 --cipher-algo 3des ...
 
     Please don't pipe the data to encrypt to gpg but give it as a filename;
-    other wise, pgp 2 will not be able to handle it.
+    otherwise, pgp 2 will not be able to handle it.
 
  Q: How can I conventional encrypt a message, so that PGP can decrypt it?
  A: You can't do this for PGP 2.  For PGP 5 you should use this:
@@ -145,7 +145,7 @@
   we (on Linux the /dev/random device) must collect some random data.
   It is really not easy to fill the Linux internal entropy buffer; I
   talked to Ted Ts'o and he commented that the best way to fill the buffer
-  is to play with your keyboard. Good security has it's price. What I do
+  is to play with your keyboard.  Good security has its price.  What I do
   is to hit several times on the shift, control, alternate, and capslock
   keys, because these keys do not produce output to the screen. This way
   you get your keys really fast (it's the same thing pgp2 does).
@@ -187,7 +187,7 @@
      q = Undefined (no value assigned)
      n = Don't trust this key at all
      m = There is marginal trust in this key
-     f = The key is full trusted.
+     f = The key is full trusted
      u = The key is ultimately trusted; this
 	 is only used for keys for which
 	 the secret key is also available.
@@ -282,7 +282,7 @@
      other keys.  "validity", or calculated trust, is a value which
      says how much GnuPG thinks a key is valid (that it really belongs
      to the one who claims to be the owner of the key).
-     For more see the chapter "The Web of Trust" in the Manual
+     For more see the chapter "The Web of Trust" in the Manual.
 
   Q: How do I interpret some of the informational outputs?
   A: While checking the validity of a key, GnuPG sometimes prints
@@ -342,7 +342,7 @@
      where pgpkeyring is the original keyring and not the GnuPG one you
      might have created in the first step.
 
-  Q: Are the headerlines of a cleartext signater part of the signed
+  Q: Are the headerlines of a cleartext signature part of the signed
      material?
   A: No.  For example you can add or remove "Comment:" lines.  They
      have a purpose like the mail header lines.  However a "Hash:"
@@ -357,7 +357,7 @@
   Q: PGP 5.x, 6.x does not like my secret key.
   A: PGP probably bails out on some private comment packets used by GnuPG.
      These packets are fully in compliance with OpenPGP; however PGP is not
-     really OpenPGP aware.  A workaround is to eport the secret keys with
+     really OpenPGP aware.  A workaround is to export the secret keys with
      this command:
 
 	gpg --export-secret-keys --no-comment -a your-key-id
@@ -376,7 +376,7 @@
   A: You should use the option --batch and don't use passphrases as
      there is usually no way to store it more secure than the secret
      keyring itself.  The suggested way to create the keys for the
-     automated envirionment ist:
+     automated environment is:
 	On a secure machine:
 	1. If you want to do automatic signing, create a signing subkey
 	   for your key (edit menu, choose "addkey" and the DSA).
@@ -384,7 +384,7 @@
 	   implementation)
 	3. gpg --export-secret-subkeys --no-comment foo >secring.auto
 	4. Copy secring.auto and the public keyring to a test directory.
-	5. Cd to this diectory
+	5. Cd to this diectory.
 	6. gpg --homedir . --edit foo
 	   and use "passwd" to remove the passphrase from the subkeys.
 	   You may also want to remove all unused subkeys.

--
  iida