See ChangeLog: Tue Aug 31 17:20:44 CEST 1999 Werner Koch

5 files changed, 24 insertions, 17 deletions

diff --git a/doc/DETAILS b/doc/DETAILS
index 67ca23c16..7c1e11edf 100644
--- a/doc/DETAILS
+++ b/doc/DETAILS
@@ -52,7 +52,7 @@ More fields may be added later.
 If field 1 has the tag "pkd", a listing looks like this:
 pkd:0:1024:B665B1435F4C2 .... FF26ABB:
     !  !   !-- the value
-    !  !------ for infomation number of bits in the value
+    !  !------ for information number of bits in the value
     !--------- index (eg. DSA goes from 0 to 3: p,q,g,y)
 
 
@@ -97,7 +97,7 @@ more arguments in future versions.
     ENC_TO  <long keyid>  <keytype>  <keylength>
 	The message is encrypted to this keyid.
 	keytype is the numerical value of the public key algorithm,
-	kenlength is the length of the key or 0 if it is not known
+	keylength is the length of the key or 0 if it is not known
 	(which is currently always the case).
 
     NODATA  <what>
@@ -147,7 +147,7 @@ more arguments in future versions.
 	No passphrase was supplied.  An application which encounters this
 	message may want to stop parsing immediately because the next message
 	will probably be a BAD_PASSPHRASE.  However, if the application
-	is a wrapper around the key edit menu functionalty it might not
+	is a wrapper around the key edit menu functionality it might not
 	make sense to stop parsing but simply ignoring the following
 	PAD_PASSPHRASE.
 
@@ -167,7 +167,7 @@ more arguments in future versions.
 	The decryption process succeeded.  This means, that either the
 	correct secret key has been used or the correct passphrase
 	for a conventional encrypted message was given.  The program
-	itself may return an errorcode becuase it may not be possible to
+	itself may return an errorcode because it may not be possible to
 	verify a signature for some reasons.
 
     NO_PUBKEY  <long keyid>
@@ -578,7 +578,7 @@ The standard http URL encoded query parameters are this (always key=value):
   are not searched for and the order of the words doesn't matter (but see
   next option).
 
-- exact=on. This switch tells the hkp server to only report exact mathing
+- exact=on. This switch tells the hkp server to only report exact matching
   keys back. In this case the order and the "delimiters" are important.
 
 - fingerprint=on. Also reports the fingerprints when used with 'index' or
@@ -592,7 +592,7 @@ A better way to to this would be a request like:
 
    /pks/lookup/<gnupg_formatierte_user_id>?op=<operation>
 
-this can be implemented using Hurd's translater mechanism.
-However, I think the whole key server stuff has to be re-thougth;
+this can be implemented using Hurd's translator mechanism.
+However, I think the whole key server stuff has to be re-thought;
 I have some ideas and probably create a white paper.
 
diff --git a/doc/FAQ b/doc/FAQ
index c879f93aa..aa8e0c4d7 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -333,7 +333,7 @@
      the displayed charset is the one you have activated on your system
      "iso-8859-1" is the most used one, so this is the default.  You can
      change the charset with the option "--charset".  It is important that
-     you active characterset matches the one displayed - if not, restrict
+     you active character set matches the one displayed - if not, restrict
      yourself to plain 7 bit ASCII and no mapping has to be done.
 
   Q: How do I transfer owner trust values from PGP to GnuPG?
diff --git a/doc/HACKING b/doc/HACKING
index bc06a7064..6f4c9ffd8 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -46,7 +46,7 @@ of the CVS head revision is also available.  See rsync(1) and try
 
 Special Tools
 =============
-Documention is based on the docbook DTD.  Actually we have only the
+Documentation is based on the docbook DTD.  Actually we have only the
 man page for now.  To build a man page you need the docbook-to-man
 tool and all the other thinks needed for SGML processing.  Debian
 comes with the docbook tools and you only need this docbook-to-man
@@ -203,7 +203,7 @@ How to use the cipher functions
 cipher/cipher.c implements the interface to symmetric encryption functions.
 As usual you have a function to open a cipher (which returns a handle to be used
 with all other functions), some functions to set the key and other stuff and
-a encrypt and decrypt function which does the real work.  YOu probably know
+a encrypt and decrypt function which does the real work.  You probably know
 how to work with files - so it should really be easy to work with these
 functions.  Here is an example:
 
@@ -211,7 +211,7 @@ functions.  Here is an example:
 
     hd = cipher_open( CIPHER_ALGO_TWOFISH, CIPHER_MODE_CFB, 0 );
     if( !hd )
-	oops( use other funtion to check for the real error );
+	oops( use other function to check for the real error );
     rc = cipher_setkey( hd, key256bit, 32 ) )
     if( rc )
 	oops( weak key or something like this );
diff --git a/doc/OpenPGP b/doc/OpenPGP
index a32da4723..148032ad9 100644
--- a/doc/OpenPGP
+++ b/doc/OpenPGP
@@ -39,7 +39,7 @@
 
      * PGP 5.x does not accept V4 signatures for anything other than
        key material.  The GnuPG option --force-v3-sigs mimics this
-       behaviour.
+       behavior.
 
      * PGP 5.x does not recognize the "five-octet" lengths in
        new-format headers or in signature subpacket lengths.
diff --git a/doc/gpg.sgml b/doc/gpg.sgml
index b4f0873cb..a5595400f 100644
--- a/doc/gpg.sgml
+++ b/doc/gpg.sgml
@@ -18,7 +18,7 @@
     Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
 -->
 <!-- This file should be processed by docbook-to-man to
-     create a manual page.  This program has currenlty the bug
+     create a manual page.  This program has currently the bug
      not to remove leading white space. So this source file does
      not look very pretty
 
@@ -469,7 +469,7 @@ values will be overwritten.
 <varlistentry>
 <term>--print-md <parameter>algo</parameter> &OptParmFiles;</term>
 <listitem><para>
-Print message digest og algorithm ALGO for all given files of stdin.
+Print message digest of algorithm ALGO for all given files of stdin.
 If "*" is used for the algorithm, digests for all available algorithms
 are printed.
 </para></listitem></varlistentry>
@@ -480,8 +480,8 @@ are printed.
 		   <optional><parameter>count</parameter></optional></term>
 <listitem><para>
 Emit COUNT random bytes of the given quality level. If count is not given
-or zero, an endless sequenece of random bytes will be emitted.
-PLEASE, don't use this command unless you know waht you are doing, it may
+or zero, an endless sequence of random bytes will be emitted.
+PLEASE, don't use this command unless you know what you are doing, it may
 remove precious entropy from the system!
 </para></listitem></varlistentry>
 
@@ -915,6 +915,13 @@ Use &ParmString; as the name of file which is stored in
 messages.
 </para></listitem></varlistentry>
 
+<varlistentry>
+<term>--use-embedded-filename</term>
+<listitem><para>
+Try to create a file with a name as embedded in the data.
+This can be a dangerous option as it allows to overwrite files.
+</para></listitem></varlistentry>
+
 
 <varlistentry>
 <term>--completes-needed &ParmN;</term>
@@ -1109,7 +1116,7 @@ This option might not be implemented yet.
 <term>--allow-non-selfsigned-uid</term>
 <listitem><para>
 Allow the import of keys with user IDs which are not self-signed.
-This is only allows the import - key validation will fail und you
+This is only allows the import - key validation will fail and you
 have to check the validity of the key my other means.  This hack is
 needed for some German keys generated with pgp 2.6.3in. You should really
 avoid using it, because OpenPGP has better mechanics to do separate signing