From a8d33c84b559e09811ea4ddcbb76d353959755e6 Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Thu, 14 Dec 2023 15:17:56 +0100 Subject: [PATCH] Fix glossary link markup (Thanks, Ryan!) --- book/source/certificates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/source/certificates.md b/book/source/certificates.md index 345c75f..30e9744 100644 --- a/book/source/certificates.md +++ b/book/source/certificates.md @@ -185,7 +185,7 @@ To form an {term}`OpenPGP certificate`, individual {term}`components` In very abstract terms, the {term}`primary key` of a {term}`certificate` acts as a root of trust or "{term}`certification authority`." It is responsible for: - issuing {term}`signatures` that express the {term}`certificate holder`'s intent to use specific {term}`subkeys` or {term}`identity components`; -- conducting other lifecycle operations, including setting {term}`expiration` dates and marking {term}`components` as {term}`invalidated` or "`revoked`." +- conducting other lifecycle operations, including setting {term}`expiration` dates and marking {term}`components` as {term}`invalidated` or "{term}`revoked`." By binding {term}`components` using digital {term}`signatures`, recipients of an {term}`OpenPGP certificate` need only {term}`validate` the {term}`authenticity` of the {term}`primary key` to use for their communication partner. Traditionally, this is done by manually verifying the *{term}`fingerprint`* of the {term}`primary key`. Once the {term}`validity` of the {term}`primary key` is confirmed, the {term}`validity` of the remaining {term}`components` can be automatically assessed by the user's OpenPGP software. Generally, {term}`components` are {term}`valid` parts of a {term}`certificate` if there is a statement signed by the {term}`certificate`'s {term}`primary key` endorsing this {term}`validity`.