From 6f3926c5b2d414c61cef36e4062ca8b7918cfc15 Mon Sep 17 00:00:00 2001 From: Awiteb Date: Wed, 18 Jun 2025 18:53:58 +0300 Subject: [PATCH] nip-34: Improve readability (#1954) Signed-off-by: Awiteb --- 34.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/34.md b/34.md index 56ede853..fc25bdeb 100644 --- a/34.md +++ b/34.md @@ -70,9 +70,9 @@ The `refs` tag can be optionally extended to enable clients to identify how many Patches can be sent by anyone to any repository. Patches to a specific repository SHOULD be sent to the relays specified in that repository's announcement event's `"relays"` tag. Patch events SHOULD include an `a` tag pointing to that repository's announcement address. -Patches in a patch set SHOULD include a NIP-10 `e` `reply` tag pointing to the previous patch. +Patches in a patch set SHOULD include a [NIP-10](10.md) `e` `reply` tag pointing to the previous patch. -The first patch revision in a patch revision SHOULD include a NIP-10 `e` `reply` to the original root patch. +The first patch revision in a patch revision SHOULD include a [NIP-10](10.md) `e` `reply` to the original root patch. ```jsonc { @@ -125,7 +125,7 @@ Issues may have a `subject` tag, which clients can utilize to display a header. ## Replies -Replies to either a `kind:1621` _issue_ or a `kind:1617` _patch_ event should follow [NIP-22 comment](22.md). +Replies to either a `kind:1621` (_issue_) or a `kind:1617` (_patch_) event should follow [NIP-22 comment](22.md). ## Status @@ -161,9 +161,9 @@ Root Patches and Issues have a Status that defaults to 'Open' and can be set by } ``` -The Status event with the largest created_at date is valid. +The most recent Status event (by `created_at` date) from either the issue/patch author or a maintainer is considered valid. -The Status of a patch-revision defaults to either that of the root-patch, or `1632` (Closed) if the root-patch's Status is `1631` and the patch-revision isn't tagged in the `1631` event. +The Status of a patch-revision defaults to either that of the root-patch, or `1632` (_Closed_) if the root-patch's Status is `1631` (_Applied/Merged_) and the patch-revision isn't tagged in the `1631` (_Applied/Merged_) event. ## Possible things to be added later