From acb1d9f7e1210895e409daea9f91ca08e8864e24 Mon Sep 17 00:00:00 2001 From: "Tammi L. Coles" Date: Fri, 3 Nov 2023 10:16:00 +0100 Subject: [PATCH] Resolve https://codeberg.org/openpgp/notes/pulls/81#issuecomment-1291281 --- book/source/04-certificates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/source/04-certificates.md b/book/source/04-certificates.md index 45abec7..dc75cf4 100644 --- a/book/source/04-certificates.md +++ b/book/source/04-certificates.md @@ -126,7 +126,7 @@ The key flags for a component key are not stored within the component key direc Instead, key flags, along with other metadata about that component key, such as the key expiration time, are stored using mechanisms that bind components into an OpenPGP certificate: - For the primary key, its key flags and other metadata can be defined in two ways: they can be linked with the [Primary User ID](primary_user_id) or through a [direct key signature](direct_key_signature). -- For subkeys, the key flags and other metadata are set using the mechanism that ties the subkey to the certificate, specifically through the primary key. Further details on [binding subkeys](binding_subkeys) are below. +- For subkeys, the key flags and other metadata are set using the mechanism that binds the subkey to the certificate, specifically through the primary key. Further details on [binding subkeys](binding_subkeys) are below. (identity_components)=