From 1da5da4e6b562358ab8b5fc76fb39657f02c40f5 Mon Sep 17 00:00:00 2001 From: Nils Ellmenreich Date: Mon, 2 Apr 2001 17:22:17 +0000 Subject: [PATCH] typo corrections by jkane89@softhome.net --- doc/gpg.sgml | 94 ++++++++++++++++++++++++++-------------------------- 1 file changed, 47 insertions(+), 47 deletions(-) diff --git a/doc/gpg.sgml b/doc/gpg.sgml index a57d59b86..abadb1382 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -72,7 +72,7 @@ -This man page does only list the commands and options available. +This man page only lists the commands and options available. For a more verbose documentation get the GNU Privacy Handbook (GPH), which is available at http://www.gnupg.org/gph/ . You will find a list of HOWTO documents at http://www.gnupg.org/docs.html . @@ -119,7 +119,7 @@ Encrypt data. This option may be combined with --sign. -c, --symmetric -Encrypt with symmetric cipher only +Encrypt with symmetric cipher only. This command asks for a passphrase. @@ -168,7 +168,7 @@ material from stdin without denoting it in the above way. This is a special version of the --verify command which does not work with detached signatures. The command expects the files to be verified either -on the commandline or reads the filenames from stdin; each name must be on +on the command line or reads the filenames from stdin; each name must be on separate line. The command is intended for quick checking of many files. @@ -243,10 +243,10 @@ useful for debugging. --gen-key Generate a new key pair. This command is normally only used -interactive. +interactively. -There is an experimental feature which allows to create keys +There is an experimental feature which allows you to create keys in batch mode. See the file doc/DETAILS in the source distribution on how to use this. @@ -302,7 +302,7 @@ Create an alternate user id. deluid -Delete an user id. +Delete a user id. addkey @@ -379,14 +379,14 @@ trust value. Letters are used for the values: --sign-key &ParmName; -Sign a public key with you secret key. This is a shortcut version +Sign a public key with your secret key. This is a shortcut version of the subcommand "sign" from --edit. --lsign-key &ParmName; -Sign a public key with you secret key but mark it as non-exportable. +Sign a public key with your secret key but mark it as non-exportable. This is a shortcut version of the subcommand "lsign" from --edit. @@ -397,7 +397,7 @@ Assume that the specified key (which must be given as a full 8 byte key ID) is as trustworthy as one of your own secret keys. This option is useful if you don't want to keep your secret keys (or one of them) -online but still be able to check the validity of a given +online but still want to be able to check the validity of a given recipient's or signator's key. @@ -453,8 +453,8 @@ or changed by you. --export-all &OptParmNames; -Same as --export, but does also export keys which -are not compatible to OpenPGP. +Same as --export, but also exports keys which +are not compatible with OpenPGP. @@ -462,12 +462,12 @@ are not compatible to OpenPGP. --export-secret-keys &OptParmNames; --export-secret-subkeys &OptParmNames; -Same as --export, but does export the secret keys. +Same as --export, but exports the secret keys instead. This is normally not very useful and a security risk. -the second form of the command has the special property to +The second form of the command has the special property to render the secret part of the primary key useless; this is a GNU extension to OpenPGP and other implementations can -not be expected to successful import such a key. +not be expected to successfully import such a key. @@ -483,7 +483,7 @@ command --update-trustdb. There are a few other options which control how this command works. -Most notable here is the --merge-only options which does not insert new keys +Most notable here is the --merge-only option which does not insert new keys but does only the merging of new signatures, user-IDs and subkeys. See also the option --allow-secret-key-import. @@ -502,7 +502,7 @@ give the name of this keyserver. --export-ownertrust List the assigned ownertrust values in ASCII format -for backup purposes +for backup purposes. @@ -530,7 +530,7 @@ are printed. Emit COUNT random bytes of the given quality level. If count is not given 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 +PLEASE, don't use this command unless you know what you are doing; it may remove precious entropy from the system! @@ -561,8 +561,8 @@ Print warranty information. -h, --help -Print usage information. This is a really long list even it does list -not all options. +Print usage information. This is a really long list even though it doesn't list +all options. @@ -630,7 +630,7 @@ specified, GnuPG asks for the user-id unless --default-recipient is given --default-recipient &ParmName; Use &ParmName; as default recipient if option --recipient is not used and -don't ask if this is a valid one. &ParmName; must be a non empty. +don't ask if this is a valid one. &ParmName; must be non-empty. @@ -651,9 +651,9 @@ Reset --default-recipient and --default-recipient-self. --encrypt-to &ParmName; -Same as --recipient but this one is intended for -in the options file and may be used together with -an own user-id as an "encrypt-to-self". These keys +Same as --recipient but this one is intended for use +in the options file and may be used with +your own user-id as an "encrypt-to-self". These keys are only used when there are other recipients given either by use of --recipient or by the asked user id. No trust checking is performed for these user ids and @@ -730,7 +730,7 @@ commands. Make sure that the TTY (terminal) is never used for any output. This option is needed in some cases because GnuPG sometimes prints -warnings to the TTY if if --batch is used. +warnings to the TTY if --batch is used. @@ -785,8 +785,8 @@ that you get different key servers. --no-auto-key-retrieve This option disables the automatic retrieving of keys from a keyserver -while verifying signatures. This option allows to keep a keyserver in -the options file or the --send-keys and --recv-keys commands. +while verifying signatures. This option allows you to keep a keyserver in +the options file for the --send-keys and --recv-keys commands. @@ -857,8 +857,8 @@ Valid values for &ParmName; are: Assume that the arguments are already given as UTF8 strings. The default (--no-utf8-strings) is to assume that arguments are encoded in the character set as specified -by --charset. These options effects all following arguments. Both options may -used multiple times. +by --charset. These options affect all following arguments. Both options may +be used multiple times. @@ -965,10 +965,10 @@ signatures. Use this to overwrite a previous -N, --notation-data &ParmNameValue; Put the name value pair into the signature as notation data. -&ParmName; must consists only of alphanumeric characters, digits +&ParmName; must consist only of alphanumeric characters, digits or the underscore; the first character must not be a digit. -&ParmValue; may be any printable string; it will encoded in UTF8, -so sou should have check that your --charset is set right. +&ParmValue; may be any printable string; it will be encoded in UTF8, +so you should check that your --charset is set correctly. If you prefix &ParmName; with an exclamation mark, the notation data will be flagged as critical (rfc2440:5.2.3.15). @@ -1112,7 +1112,7 @@ Does not not cache the verification status of key signatures. Caching gives a much better performance in key listings, however if you suspect that your public keyring is not saved against write modifications, you can use this option to disable the caching. It -probably does not make sense to disable it because all kind of damange +probably does not make sense to disable it because all kind of damage can be done if someone else has write access to your public keyring. @@ -1120,11 +1120,11 @@ can be done if someone else has write access to your public keyring. --no-sig-create-check GnuPG normally verifies each signature right after creation to protect -against bugs and hardware mal functions which could leak out bits from +against bugs and hardware malfunctions which could leak out bits from the secret key. This extra verification needs some time (about 115% fro DSA keys), and so this option can be used to disable it. However, due to the fact that the signature creation needs manual -interaction, this performance penality does not matter in most setting. +interaction, this performance penalty does not matter in most setting. @@ -1174,7 +1174,7 @@ Don't use this option if you can avoid it. --command-fd &ParmN; -This is a replacement for the depreciated shared-memory IPC mode. +This is a replacement for the deprecated shared-memory IPC mode. If this option is enabled, user input on questions is not expected from the TTY but from the given file descriptor. It should be used together with --status-fd. See the file doc/DETAILS in the source @@ -1206,7 +1206,7 @@ disabled. OpenPGP states that an implementation should generate v4 signatures but PGP 5.x recognizes v4 signatures only -on key material. This options forces v3 signatures for +on key material. This option forces v3 signatures for signatures on data. @@ -1215,7 +1215,7 @@ signatures on data. --force-mdc Force the use of encryption with appended manipulation -code. This is always used with the newer cipher (those +code. This is always used with the newer ciphers (those with a blocksize greater than 64 bit). This option might not be implemented yet. @@ -1257,7 +1257,7 @@ The ASCII armor used by OpenPG is protected by a CRC checksum against transmission errors. Sometimes it happens that the CRC gets mangled somewhere on the transmission channel but the actual content (which is anyway protected by -the OpenPGP protocol) is still okay. This options will let gpg ignore +the OpenPGP protocol) is still okay. This option will let gpg ignore CRC errors. @@ -1284,7 +1284,7 @@ from a config file. Disable locking entirely. This option should be used only in very special environments, where it can be assured that only one process -is accessing those files. A bootable floppy with a standalone +is accessing those files. A bootable floppy with a stand-alone encryption system will probably use this. Improper usage of this option may lead to data and key corruption. @@ -1292,9 +1292,9 @@ option may lead to data and key corruption. --no-random-seed-file -GnuPG uses a file to store it's internal random pool over invocations. +GnuPG uses a file to store its internal random pool over invocations. This makes random generation faster; however sometimes write operations -are not desired. This option can be used to achive that with the cost of +are not desired. This option can be used to achieve that with the cost of slower random generation. @@ -1370,7 +1370,7 @@ and may be used together with another command. Changes the output of the list commands to work faster; this is achieved by leaving some parts empty. Some applications don't need the user ID and the trust information given in the listings. By using this options they -can get a faster listing. The excact behaviour of this option may change +can get a faster listing. The exact behaviour of this option may change in future versions. @@ -1385,7 +1385,7 @@ Do not merge user ID and primary key in --with-colon listing mode. Changes the behaviour of some commands. This is like --dry-run but different in some cases. The semantic of this command may be extended in -the future. Currently it does only skip the actual decryption pass and +the future. Currently it only skips the actual decryption pass and therefore enables a fast listing of the encryption keys. @@ -1404,7 +1404,7 @@ This is not for normal use. Use the source to see for what it might be useful. --emulate-md-encode-bug -GnuPG versions prior to 1.0.2 had a bug in the way a signature was encode. +GnuPG versions prior to 1.0.2 had a bug in the way a signature was encoded. This options enables a workaround by checking faulty signatures again with the encoding used in old versions. This may only happen for ElGamal signatures which are not widely used. @@ -1479,7 +1479,7 @@ here are some examples: -Used to locate the default home directory. + @@ -1553,7 +1553,7 @@ only a number. *Heine By case insensitive substring matching. This is the default mode but -applications may want to explicitely indicate this by putting the asterisk +applications may want to explicitly indicate this by putting the asterisk in front. @@ -1729,7 +1729,7 @@ commandline or using - to specify stdin. On many systems this program should be installed as setuid(root). This is necessary to lock memory pages. Locking memory pages prevents the operating system from writing memory pages to disk. If you get no -warning message about insecure memory 3our operating system supports +warning message about insecure memory your operating system supports locking without being root. The program drops root privileges as soon as locked memory is allocated.