From f440eac3dccefa5c0ec9d3964e1d08357fd31e09 Mon Sep 17 00:00:00 2001
From: daniele <github@dtonon.com>
Date: Thu, 30 Jan 2025 22:49:06 +0100
Subject: [PATCH] Remove reference to 'username' and update descriptions in
 metadata (#1726)

---
 01.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/01.md b/01.md
index e515d811..9e25ca9b 100644
--- a/01.md
+++ b/01.md
@@ -89,7 +89,7 @@ Kinds specify how clients should interpret the meaning of each event and the oth
 
 This NIP defines one basic kind:
 
-- `0`: **user metadata**: the `content` is set to a stringified JSON object `{name: <username>, about: <string>, picture: <url, string>}` describing the user who created the event. [Extra metadata fields](24.md#kind-0) may be set. A relay may delete older events once it gets a new one for the same pubkey.
+- `0`: **user metadata**: the `content` is set to a stringified JSON object `{name: <nickname or full name>, about: <short bio>, picture: <url of the image>}` describing the user who created the event. [Extra metadata fields](24.md#kind-0) may be set. A relay may delete older events once it gets a new one for the same pubkey.
 
 And also a convention for kind ranges that allow for easier experimentation and flexibility of relay implementation: