From c7191fc2f518aa85b6437c001c1fdcadaa0b38a3 Mon Sep 17 00:00:00 2001
From: Semisol <45574030+Semisol@users.noreply.github.com>
Date: Sat, 2 Sep 2023 14:34:39 +0300
Subject: [PATCH] fix inconsistency

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

diff --git a/01.md b/01.md
index 1831438e..7a304e0d 100644
--- a/01.md
+++ b/01.md
@@ -82,7 +82,7 @@ Kinds specify how clients should interpret the meaning of each event and the oth
 And also a convention for kind ranges that allow for easier experimentation and flexibility of relay implementation:
 
 - for kind `n` such that `1000 <= n < 10000`, events are **regular**, which means they're all expected to be stored by relays.
-- for kind `n` such that `10000 <= n < 20000 || k == 0 || k == 3`, events are **replaceable**, which means that, for each combination of `pubkey` and `kind`, only the latest event is expected to (SHOULD) be stored by relays, older versions are expected to be discarded.
+- for kind `n` such that `10000 <= n < 20000 || n == 0 || n == 3`, events are **replaceable**, which means that, for each combination of `pubkey` and `kind`, only the latest event is expected to (SHOULD) be stored by relays, older versions are expected to be discarded.
 - for kind `n` such that `20000 <= n < 30000`, events are **ephemeral**, which means they are not expected to be stored by relays.
 - for kind `n` such that `30000 <= n < 40000`, events are **parameterized replaceable**, which means that, for each combination of `pubkey`, `kind` and the `d` tag, only the latest event is expected to be stored by relays, older versions are expected to be discarded.