diff --git a/book/source/07-signing_data.md b/book/source/07-signing_data.md
index a219643..c95be3b 100644
--- a/book/source/07-signing_data.md
+++ b/book/source/07-signing_data.md
@@ -69,7 +69,7 @@ To produce an {term}`inline signature`, the {term}`signer` processes the entiret
 
 For efficient {term}`verification`, an application must understand how to handle the {term}`literal data<Literal Data Packet>` prior to its reading. This requirement is addressed by the {term}`one-pass signature packets<One-pass Signature Packet>` located at the beginning of {term}`inline-signed<Inline Signature>` messages. These {term}`packets<Packet>` include essential information such as the {term}`fingerprint<OpenPGP Fingerprint>` of the {term}`signing key<OpenPGP Component Key>` and the {term}`hash<Hash Digest>` algorithm used for computing the {term}`signature<OpenPGP Signature Packet>`'s {term}`hash digest`. This setup enables the verifier to process the data correctly and efficiently.
 
-Strictly speaking, the hash algorithm would be sufficient to begin the verification process, but having the signers fingerprint/key-id available upfront allows to fetch the signers certificate before processing the entirety of the - potentially large - signed data.
+Strictly speaking, knowing just the hash algorithm would be sufficient to begin the verification process. However, having efficient access to the signer's fingerprint or key ID upfront allows OpenPGP software to fetch the signer's certificates before processing the entirety of the - potentially large - signed data, and .
 
 #### Verification