From 080c88909b6c94e642742bf5e6bfcaf51098db85 Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Wed, 1 Nov 2023 21:16:19 +0100 Subject: [PATCH] Cut redundancy --- book/source/02-highlevel.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/book/source/02-highlevel.md b/book/source/02-highlevel.md index af539b3..621d3f1 100644 --- a/book/source/02-highlevel.md +++ b/book/source/02-highlevel.md @@ -104,8 +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/), and it may also come in handy for debugging issues. - -Gaining some familiarity with the internal structure of OpenPGP data will also help us to read the OpenPGP RFC, which describes the internal structure of OpenPGP packets in full detail. +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. (Most of the time, however, we will look at OpenPGP artifacts at a higher level of abstraction.)