From 77a0a69d781a342eaee3f72432c7cf9d4b858b2f Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Sat, 25 Nov 2023 17:43:22 +0100 Subject: [PATCH] clarify language --- book/source/08-signing_components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/source/08-signing_components.md b/book/source/08-signing_components.md index ee336be..2cb035a 100644 --- a/book/source/08-signing_components.md +++ b/book/source/08-signing_components.md @@ -385,7 +385,7 @@ Note that a value of `32` is not applicable in these signatures. Users may find themselves needing to revoke their entire OpenPGP certificate, rendering it unusable. This could be for various reasons, such as migrating to a new certificate or in response to a compromise of the certificate's secret key material. -While a soft-revoked certificate can be re-validated at a later time with a new certification, a hard revocation is typically permanent. +While a soft-revoked certificate can be re-validated at a later time with a new certification, a hard revocation is permanent. The recommended way to revoke a certificate is by issuing a *KeyRevocation* signature (type `0x20`). Its structure is similar to that of a *CertificationRevocation* signature.