aboutsummaryrefslogtreecommitdiffstats
path: root/doc/specify-user-id.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/specify-user-id.texi')
-rw-r--r--doc/specify-user-id.texi12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/specify-user-id.texi b/doc/specify-user-id.texi
index 7643f93ec..7d23ed86f 100644
--- a/doc/specify-user-id.texi
+++ b/doc/specify-user-id.texi
@@ -12,8 +12,8 @@ This format is deduced from the length of the string and its content or
of its SHA-1 fingerprint. The use of key Ids is just a shortcut, for
all automated processing the fingerprint should be used.
-When using @command{gpg} an exclamation mark may be appended to force
-using the specified primary or secondary key and not to try and
+When using @command{gpg} an exclamation mark (!) may be appended to
+force using the specified primary or secondary key and not to try and
calculate which primary or secondary key to use.
The last four lines of the example give the key ID in their long form as
@@ -42,8 +42,8 @@ the @code{0x} prefix. Note, that only the 20 byte version fingerprint
is available with @command{gpgsm} (i.e. the SHA-1 hash of the
certificate).
-When using @command{gpg} an exclamation mark may be appended to force
-using the specified primary or secondary key and not to try and
+When using @command{gpg} an exclamation mark (!) may be appended to
+force using the specified primary or secondary key and not to try and
calculate which primary or secondary key to use.
The best way to specify a key Id is by using the fingerprint. This
@@ -121,8 +121,8 @@ This should return the Root cert of the issuer. See note above.
@item By exact match on serial number and issuer's DN.
-This is indicated by a hash mark, followed by the hexadecmal
-representation of the serial number, the followed by a slash and the
+This is indicated by a hash mark, followed by the hexadecimal
+representation of the serial number, then followed by a slash and the
RFC-2253 encoded DN of the issuer. See note above.
@cartouche