diff --git a/19.md b/19.md
index 3ea8e11..4e5e029 100644
--- a/19.md
+++ b/19.md
@@ -22,8 +22,6 @@ These are the possible bech32 prefixes:
 
 Example: the hex public key `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d` translates to `npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6`.
 
-The bech32 encodings of keys and ids are not meant to be used inside the standard NIP-01 event formats or inside the filters, they're meant for human-friendlier display and input only. Clients should still accept keys in both hex and npub format for now, and convert internally.
-
 ## Shareable identifiers with extra metadata
 
 When sharing a profile or an event, an app may decide to include relay information and other metadata such that other apps can locate and display these entities more easily.
@@ -65,5 +63,6 @@ These possible standardized `TLV` types are indicated here:
 
 ## Notes
 
+- Clients should still accept keys in both hex and npub format for now, and convert internally.
 - `npub` keys MUST NOT be used in NIP-01 events or in NIP-05 JSON responses, only the hex format is supported there.
 - When decoding a bech32-formatted string, TLVs that are not recognized or supported should be ignored, rather than causing an error.