From 139a543db28ec3e8f547da071ac9e6abe2bd0cbb Mon Sep 17 00:00:00 2001 From: "Tammi L. Coles" Date: Fri, 3 Nov 2023 11:59:37 +0100 Subject: [PATCH] resolve https://codeberg.org/openpgp/notes/pulls/104#issuecomment-1318049 --- book/source/02-highlevel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/source/02-highlevel.md b/book/source/02-highlevel.md index 621d3f1..3dbbb26 100644 --- a/book/source/02-highlevel.md +++ b/book/source/02-highlevel.md @@ -104,6 +104,6 @@ There is [ongoing work](https://datatracker.ietf.org/doc/draft-wussler-openpgp-p OpenPGP data is internally structured as "packets." We'll look into examples of this internal structure in a series of chapters at the end of this document. -Getting familiar with the internal format of OpenPGP data is a good way to get familiar with the [RFC](https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/),which describes the internal structure of OpenPGP packets in full detail. It may also come in handy for debugging issues. +Getting familiar with the internal format of OpenPGP data provides practical insight into the [RFC](https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/), which describes the internal structure of OpenPGP packets in full detail, and may also come in handy for debugging issues. (Most of the time, however, we will look at OpenPGP artifacts at a higher level of abstraction.)