mirror of
git://git.gnupg.org/gnupg.git
synced 2025-01-02 12:01:32 +01:00
doc: fix minor spelling and tense errors
* doc/{gpg,gpgsm,wks}.texi: minor orthographic cleanup. Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
This commit is contained in:
parent
cba6e1bd72
commit
b7793c3af3
@ -1091,7 +1091,7 @@ Directly sign a key from the passphrase without any further user
|
||||
interaction. The @var{fpr} must be the verified primary fingerprint
|
||||
of a key in the local keyring. If no @var{names} are given, all
|
||||
useful user ids are signed; with given [@var{names}] only useful user
|
||||
ids matching one of theses names are signed. By default, or if a name
|
||||
ids matching one of these names are signed. By default, or if a name
|
||||
is prefixed with a '*', a case insensitive substring match is used.
|
||||
If a name is prefixed with a '=' a case sensitive exact match is done.
|
||||
|
||||
@ -3655,7 +3655,7 @@ files; They all live in the current home directory (@pxref{option
|
||||
certificates. The file name corresponds to the OpenPGP fingerprint of
|
||||
the respective key. It is suggested to backup those certificates and
|
||||
if the primary private key is not stored on the disk to move them to
|
||||
an external storage device. Anyone who can access theses files is
|
||||
an external storage device. Anyone who can access these files is
|
||||
able to revoke the corresponding key. You may want to print them out.
|
||||
You should backup all files in this directory and take care to keep
|
||||
this backup closed away.
|
||||
|
@ -224,7 +224,7 @@ mainly for debugging.
|
||||
@item --keydb-clear-some-cert-flags
|
||||
@opindex keydb-clear-some-cert-flags
|
||||
This is a debugging aid to reset certain flags in the key database
|
||||
which are used to cache certain certificate stati. It is especially
|
||||
which are used to cache certain certificate statuses. It is especially
|
||||
useful if a bad CRL or a weird running OCSP responder did accidentally
|
||||
revoke certificate. There is no security issue with this command
|
||||
because @command{gpgsm} always make sure that the validity of a certificate is
|
||||
|
@ -260,7 +260,7 @@ Display a brief help page and exit.
|
||||
@end ifset
|
||||
|
||||
@mansect description
|
||||
The @command{gpg-wks-server} is a server site implementation of the
|
||||
The @command{gpg-wks-server} is a server side implementation of the
|
||||
Web Key Service. It receives requests for publication, sends
|
||||
confirmation requests, receives confirmations, and published the key.
|
||||
It also has features to ease the setup and maintenance of a Web Key
|
||||
@ -268,7 +268,7 @@ Directory.
|
||||
|
||||
When used with the command @option{--receive} a single Web Key Service
|
||||
mail is processed. Commonly this command is used with the option
|
||||
@option{--send} to directly send the crerated mails back. See below
|
||||
@option{--send} to directly send the created mails back. See below
|
||||
for an installation example.
|
||||
|
||||
The command @option{--cron} is used for regular cleanup tasks. For
|
||||
@ -400,7 +400,7 @@ be the same address for all configured domains, for example:
|
||||
$ echo key-submission@@example.net >submission-address
|
||||
@end example
|
||||
|
||||
The protocol requires that the key to be published is send with an
|
||||
The protocol requires that the key to be published is sent with an
|
||||
encrypted mail to the service. Thus you need to create a key for
|
||||
the submission address:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user