From 6ee98c1bfbe5f4c28fd55bdc835b9a5621e5cab9 Mon Sep 17 00:00:00 2001 From: Jeff Thibault Date: Sat, 13 Aug 2022 14:08:14 -0400 Subject: [PATCH] spelling nit --- 22.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/22.md b/22.md index f62aa4e6..e31f24c7 100644 --- a/22.md +++ b/22.md @@ -22,7 +22,7 @@ The motivation for this NIP is to formalize a way for relays to restrict event t The event `created_at` field is just a unix timestamp and can be set to a time in the past or future. For example, the `created_at` field can be set to a time 20 years ago even though it was created today and still be a valid event. It can also be set to a time 20 years in the future and still be a valid event. This NIP aims to define a way for relays that do not want to store events with *any* timestamp to set their own restrictions. -A wide adoption of this could create a better UX on clients as well because it would decrease the liklihood of the user seeing events from dates such as 1984 or 2084, which could be confusing. +A wide adoption of this could create a better UX on clients as well because it would decrease the likelihood of the user seeing events from dates such as 1984 or 2084, which could be confusing. Python Example --------------