1 files changed, 4 insertions, 4 deletions

diff --git a/19.md b/19.md
index f3dd2b8..caf60f9 100644
--- a/19.md
+++ b/19.md
@@ -35,7 +35,7 @@ These are the possible bech32 prefixes with `TLV`:
   - `nprofile`: a nostr profile
   - `nevent`: a nostr event
   - `nrelay`: a nostr relay
-  - `nref`: a nostr parameterized replaceable event coordinate (NIP-33)
+  - `nitem`: a nostr parameterized replaceable event coordinate (NIP-33)
 
 These possible standardized `TLV` types are indicated here:
 
@@ -44,12 +44,12 @@ These possible standardized `TLV` types are indicated here:
     - for `nprofile` it will be the 32 bytes of the profile public key
     - for `nevent` it will be the 32 bytes of the event id
     - for `nrelay`, this is the relay URL
-    - for `nref`, it is the identifier (the `"d"` tag) of the event being referenced
+    - for `nitem`, it is the identifier (the `"d"` tag) of the event being referenced
   - for `nprofile`, `nevent` and `nrelay` this may be included only once.
 - `1`: `relay`
-  - for `nprofile`, `nevent` and `nref`, a relay in which the entity (profile or event) is more likely to be found, encoded as UTF-8. This may be included multiple times
+  - for `nprofile`, `nevent` and `nitem`, a relay in which the entity (profile or event) is more likely to be found, encoded as UTF-8. This may be included multiple times
 - `2`: `author`
-  - for `nref`, the 32 bytes of the pubkey of the event
+  - for `nitem`, the 32 bytes of the pubkey of the event
 
 
 ## Examples