4 files changed, 11 insertions, 6 deletions

diff --git a/01.md b/01.md
index 8b1471d..01cfcc1 100644
--- a/01.md
+++ b/01.md
@@ -78,6 +78,8 @@ Filter attributes containing lists (such as `ids`, `kinds`, or `#e`) are JSON ar
 
 The `ids` and `authors` lists contain lowercase hexadecimal strings, which may either be an exact 64-character match, or a prefix of the event value.  A prefix match is when the filter string is an exact string prefix of the event value.  The use of prefixes allows for more compact filters where a large number of values are queried, and can provide some privacy for clients that may not want to disclose the exact authors or events they are searching for.
 
+The `since` and `until` properties can be used to specify the time range of events returned in the subscription. If a filter includes the `since` property, events with `created_at` greater than or equal to `since` are considered to match the filter. The `until` property is similar except that `created_at` must be less than or equal to `until`. In short, an event matches a filter if `since <= created_at <= until` holds.
+
 All conditions of a filter that are specified must match for an event for it to pass the filter, i.e., multiple conditions are interpreted as `&&` conditions.
 
 A `REQ` message may contain multiple filters. In this case, events that match any of the filters are to be returned, i.e., multiple filters are to be interpreted as `||` conditions.
diff --git a/23.md b/23.md
index 4291228..7a06b0e 100644
--- a/23.md
+++ b/23.md
@@ -12,7 +12,11 @@ This NIP defines `kind:30023` (a parameterized replaceable event according to [N
 
 ### Format
 
-The `.content` of these events should be a string text in Markdown syntax.
+The `.content` of these events should be a string text in Markdown syntax. To maximize compatibility and readability between different clients and devices, any client that is creating long form notes:
+
+- MUST NOT hard line-break paragraphs of text, such as arbitrary line breaks at 80 column boundaries.
+
+- MUST NOT support adding HTML to Markdown.
 
 ### Metadata
 
diff --git a/25.md b/25.md
index 7a612a1..86ce763 100644
--- a/25.md
+++ b/25.md
@@ -52,7 +52,7 @@ func make_like_event(pubkey: String, privkey: String, liked: NostrEvent) -> Nost
 Custom Emoji Reaction
 ---------------------
 
-The client may specify a custom emoji ([NIP-30](30.md)) `:shortcode` in the
+The client may specify a custom emoji ([NIP-30](30.md)) `:shortcode:` in the
 reaction content. The client should refer to the emoji tag and render the
 content as an emoji if shortcode is specified.
 
diff --git a/56.md b/56.md
index 42174fb..43b7bad 100644
--- a/56.md
+++ b/56.md
@@ -63,10 +63,9 @@ Example events
 {
   "kind": 1984,
   "tags": [
-    ["p", <impersonator pubkey>, "impersonation"],
-    ["p", <victim pubkey>]
+    ["p", <impersonator pubkey>, "impersonation"]
   ],
-  "content": "Profile is imitating #[1]",
+  "content": "Profile is impersonating nostr:<victim bech32 pubkey>",
   ...
 }
 ```
@@ -75,7 +74,7 @@ Client behavior
 ---------------
 
 Clients can use reports from friends to make moderation decisions if they
-choose to. For instance, if 3+ of your friends report a profile as explicit,
+choose to. For instance, if 3+ of your friends report a profile for `nudity`,
 clients can have an option to automatically blur photos from said account.