[PATCH] Fix some spelling errors picked up by lintian.
Eric Dorland
eric at debian.org
Mon Dec 31 23:41:48 CET 2012
---
doc/dirmngr.texi | 4 ++--
doc/gpg-agent.texi | 18 +++++++++---------
doc/gpg.texi | 27 ++++++++++++++-------------
doc/gpgsm.texi | 14 +++++++-------
doc/scdaemon.texi | 6 +++---
doc/tools.texi | 14 +++++++-------
6 files changed, 42 insertions(+), 41 deletions(-)
diff --git a/doc/dirmngr.texi b/doc/dirmngr.texi
index e626487..5243dd0 100644
--- a/doc/dirmngr.texi
+++ b/doc/dirmngr.texi
@@ -299,8 +299,8 @@ Obviously this will lead to problems if the password has orginally been
encoded as Latin-1. There is no other solution here than to put such a
password in the binary encoding into the file (i.e. non-ascii characters
won't show up readable). at footnote{The @command{gpgconf} tool might be
-helpful for frontends as it allows to edit this configuration file using
-percent escaped strings.}
+helpful for frontends as it allows one to edit this configuration file
+using percent escaped strings.}
@item --ldaptimeout @var{secs}
diff --git a/doc/gpg-agent.texi b/doc/gpg-agent.texi
index dcd96fb..63f7be0 100644
--- a/doc/gpg-agent.texi
+++ b/doc/gpg-agent.texi
@@ -53,10 +53,10 @@ independently from any protocol. It is used as a backend for
utilities.
@ifset gpgtwoone
-The agent is usualy started on demand by @command{gpg}, @command{gpgsm},
- at command{gpgconf} or @command{gpg-connect-agent}. Thus there is no
-reason to start it manually. In case you want to use the included
-Secure Shell Agent you may start the agent using:
+The agent is usually started on demand by @command{gpg},
+ at command{gpgsm}, @command{gpgconf} or @command{gpg-connect-agent}.
+Thus there is no reason to start it manually. In case you want to use
+the included Secure Shell Agent you may start the agent using:
@example
gpg-connect-agent /bye
@@ -122,7 +122,7 @@ output of the @code{tty} command. For W32 systems this option is not
required.
Please make sure that a proper pinentry program has been installed
-under the default filename (which is system dependant) or use the
+under the default filename (which is system dependent) or use the
option @option{pinentry-program} to specify the full name of that program.
It is often useful to install a symbolic link from the actual used
pinentry (e.g. @file{/usr/bin/pinentry-gtk}) to the expected
@@ -577,8 +577,8 @@ agent. By default they may all be found in the current home directory
lines are ignored. To mark a key as trusted you need to enter its
fingerprint followed by a space and a capital letter @code{S}. Colons
may optionally be used to separate the bytes of a fingerprint; this
- allows to cut and paste the fingerprint from a key listing output. If
- the line is prefixed with a @code{!} the key is explicitly marked as
+ allows one to cut and paste the fingerprint from a key listing output.
+ If the line is prefixed with a @code{!} the key is explicitly marked as
not trusted.
Here is an example where two keys are marked as ultimately trusted
@@ -980,8 +980,8 @@ Here is an example session:
This is used to create a new keypair and store the secret key inside the
active PSE --- which is in most cases a Soft-PSE. An not yet defined
-option allows to choose the storage location. To get the secret key out
-of the PSE, a special export tool has to be used.
+option allows one to choose the storage location. To get the secret key
+out of the PSE, a special export tool has to be used.
@example
@ifset gpgtwoone
diff --git a/doc/gpg.texi b/doc/gpg.texi
index d679000..abc3c40 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -1232,9 +1232,9 @@ Use @code{file} to access the smartcard reader. The current default is
@ifset gpgone
@item --disable-ccid
@opindex disable-ccid
-Disable the integrated support for CCID compliant readers. This
-allows to fall back to one of the other drivers even if the internal
-CCID driver can handle the reader. Note, that CCID support is only
+Disable the integrated support for CCID compliant readers. This allows
+one to fall back to one of the other drivers even if the internal CCID
+driver can handle the reader. Note, that CCID support is only
available if libusb was available at build time.
@end ifset
@@ -1463,8 +1463,8 @@ mechanisms, in the order they are to be tried:
may be used here to query that particular keyserver.
@item local
- Locate the key using the local keyrings. This mechanism allows to
- select the order a local key lookup is done. Thus using
+ Locate the key using the local keyrings. This mechanism allows one
+ to select the order a local key lookup is done. Thus using
@samp{--auto-key-locate local} is identical to
@option{--no-auto-key-locate}.
@@ -1872,13 +1872,13 @@ Use @var{name} as the key to sign with. Note that this option overrides
@opindex try-secret-key
For hidden recipients GPG needs to know the keys to use for trial
decryption. The key set with @option{--default-key} is always tried
-first, but this is often not sufficient. This option allows to set more
-keys to be used for trial decryption. Although any valid user-id
-specification may be used for @var{name} it makes sense to use at least
-the long keyid to avoid ambiguities. Note that gpg-agent might pop up a
-pinentry for a lot keys to do the trial decryption. If you want to stop
-all further trial decryption you may use close-window button instead of
-the cancel button.
+first, but this is often not sufficient. This option allows one to
+set more keys to be used for trial decryption. Although any valid
+user-id specification may be used for @var{name} it makes sense to use
+at least the long keyid to avoid ambiguities. Note that gpg-agent
+might pop up a pinentry for a lot keys to do the trial decryption. If
+you want to stop all further trial decryption you may use close-window
+button instead of the cancel button.
@end ifset
@item --try-all-secrets
@@ -2475,7 +2475,8 @@ to display the message. This option overrides @option{--set-filename}.
@itemx --no-use-embedded-filename
@opindex use-embedded-filename
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. Defaults to no.
+a dangerous option as it allows one to overwrite files. Defaults to
+no.
@item --cipher-algo @code{name}
@opindex cipher-algo
diff --git a/doc/gpgsm.texi b/doc/gpgsm.texi
index bdb0378..136bbf8 100644
--- a/doc/gpgsm.texi
+++ b/doc/gpgsm.texi
@@ -611,15 +611,15 @@ interoperability problems.
@item --extra-digest-algo @var{name}
@opindex extra-digest-algo
-Sometimes signatures are broken in that they announce a different digest
-algorithm than actually used. @command{gpgsm} uses a one-pass data
-processing model and thus needs to rely on the announced digest
+Sometimes signatures are broken in that they announce a different
+digest algorithm than actually used. @command{gpgsm} uses a one-pass
+data processing model and thus needs to rely on the announced digest
algorithms to properly hash the data. As a workaround this option may
be used to tell gpg to also hash the data using the algorithm
- at var{name}; this slows processing down a little bit but allows to verify
-such broken signatures. If @command{gpgsm} prints an error like
-``digest algo 8 has not been enabled'' you may want to try this option,
-with @samp{SHA256} for @var{name}.
+ at var{name}; this slows processing down a little bit but allows one to
+verify such broken signatures. If @command{gpgsm} prints an error
+like ``digest algo 8 has not been enabled'' you may want to try this
+option, with @samp{SHA256} for @var{name}.
@item --faked-system-time @var{epoch}
diff --git a/doc/scdaemon.texi b/doc/scdaemon.texi
index 200fed8..f91d312 100644
--- a/doc/scdaemon.texi
+++ b/doc/scdaemon.texi
@@ -254,9 +254,9 @@ deprecated; it may be removed in future releases.
@item --disable-ccid
@opindex disable-ccid
Disable the integrated support for CCID compliant readers. This
-allows to fall back to one of the other drivers even if the internal
-CCID driver can handle the reader. Note, that CCID support is only
-available if libusb was available at build time.
+allows one to fall back to one of the other drivers even if the
+internal CCID driver can handle the reader. Note, that CCID support
+is only available if libusb was available at build time.
@item --reader-port @var{number_or_string}
@opindex reader-port
diff --git a/doc/tools.texi b/doc/tools.texi
index be1233b..74bf81c 100644
--- a/doc/tools.texi
+++ b/doc/tools.texi
@@ -235,7 +235,7 @@ commit the changes.
@command{gpgconf} provides the backend of a configuration editor. The
configuration editor would usually be a graphical user interface
-program, that allows to display the current options, their default
+program, that allows one to display the current options, their default
values, and allows the user to make changes to the options. These
changes can then be made active with @command{gpgconf} again. Such a
program that uses @command{gpgconf} in this way will be called GUI
@@ -972,12 +972,12 @@ no feature to change the global option file through @command{gpgconf}.
@mansect description
This script is a wrapper around @command{gpgconf} to run it with the
command @code{--apply-defaults} for all real users with an existing
-GnuPG home directory. Admins might want to use this script to update he
-GnuPG configuration files for all users after
- at file{/etc/gnupg/gpgconf.conf} has been changed. This allows to enforce
-certain policies for all users. Note, that this is not a bulletproof of
-forcing a user to use certain options. A user may always directly edit
-the configuration files and bypass gpgconf.
+GnuPG home directory. Admins might want to use this script to update
+he GnuPG configuration files for all users after
+ at file{/etc/gnupg/gpgconf.conf} has been changed. This allows one to
+enforce certain policies for all users. Note, that this is not a
+bulletproof of forcing a user to use certain options. A user may
+always directly edit the configuration files and bypass gpgconf.
@noindent
@command{applygnupgdefaults} is invoked by root as:
--
1.7.10.4
--
Eric Dorland <eric at kuroneko.ca>
ICQ: #61138586, Jabber: hooty at jabber.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/attachments/20121231/3dc248c8/attachment.pgp>
More information about the Gnupg-devel
mailing list