From d1d438bf1458fc0f59a191631d10c0bde35353be Mon Sep 17 00:00:00 2001 From: Yasuhiro Matsumoto Date: Tue, 29 Aug 2023 00:45:45 +0900 Subject: [PATCH] fix typo --- 01.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/01.md b/01.md index d6ccfbe2..e4c0546c 100644 --- a/01.md +++ b/01.md @@ -62,7 +62,7 @@ Each tag is an array of strings of arbitrary size, with some conventions around The first element of the tag array is referred to as the tag _name_ or _key_ and the second as the tag _value_. So we can safely say that the event above has an `e` tag set to `"5c83da77af1dec6d7289834998ad7aafbd9e2191396d75ec3cc27f5a77226f36"`, an `alt` tag set to `"reply"` and so on. All elements after the second do not have a conventional name. -This NIP defines 3 standard tags that can be used accross all event kinds with the same meaning. They are as follows: +This NIP defines 3 standard tags that can be used across all event kinds with the same meaning. They are as follows: - The `e` tag, used to refer to an event: `["e", <32-bytes lowercase hex of the id of another event>, ]` - The `p` tag, used to refer to another user: `["p", <32-bytes lowercase hex of a pubkey>, ]`