diff --git a/book/source/06-signatures.md b/book/source/06-signatures.md
index 04a7348..042218d 100644
--- a/book/source/06-signatures.md
+++ b/book/source/06-signatures.md
@@ -16,7 +16,6 @@ The term *signature* can have multiple meanings in the context of OpenPGP:
 - Cryptographic keys create raw signatures which are byte sequences calculated according to some signature scheme.
 - [*OpenPGP signature packets*](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-signature-packet-type-id-2), which combine a *type* setting, additional metadata, and a raw cryptographic signature.
 
-
 ```{figure} diag/types_of_signatures.png
 
 Two meanings of the term "signature" in OpenPGP
@@ -52,11 +51,9 @@ As outlined above, an OpenPGP signature is a composite data structure, which com
   - Most of this metadata is encoded as so-called "subpackets," see {ref}`signature_subpackets`,
 - A raw cryptographic signature.
 
+```{figure} diag/signature_packet.png
 
-```{admonition} VISUAL
-:class: warning
-
-show a version of our "yellow tag-thing with sig-circle" visual?
+Structure of an OpenPGP signature packet
 ```
 
 The cryptographic signature is calculated by its issuer. It certifies a hash digest, which in turn combines a set of input data. The exact input data depends on the signature type. Roughly: the hash digest is over the elements that the OpenPGP signature makes a statement about, combined with the metadata in the OpenPGP signature packet itself. More on this later.