From b4493aa56abdea4b05780651e7af06ea13bbfafa Mon Sep 17 00:00:00 2001
From: fiatjaf <fiatjaf@gmail.com>
Date: Mon, 13 Feb 2023 08:47:23 -0300
Subject: rename coordinates: nitem->naddr, "i"->"a"

---
 33.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to '33.md')

diff --git a/33.md b/33.md
index 5b8ad66..409ce4f 100644
--- a/33.md
+++ b/33.md
@@ -38,11 +38,11 @@ Normally (as per NIP-01, NIP-12) the `"p"` tag is used for referencing public ke
 equivalents for event tags (i.e. an `nprofile` is generally translated into a tag
 `["p", "<event hex id>", "<relay url>"]`).
 
-To support linking to parameterized replaceable events, the `nitem` code is introduced on
+To support linking to parameterized replaceable events, the `naddr` code is introduced on
 NIP-19. It includes the public key of the event author and the `d` tag (and relays) such that
 the referenced combination of public key and `d` tag can be found.
 
-The equivalent in `tags` to the `nitem` code is the tag `"i"`, comprised of `["i", "<kind>:<pubkey>:<d-identifier>", "<relay url>"]`.
+The equivalent in `tags` to the `naddr` code is the tag `"a"`, comprised of `["a", "<kind>:<pubkey>:<d-identifier>", "<relay url>"]`.
 
 Client Behavior
 ---------------
-- 
cgit v1.2.3