From 1a8d8c449639e345fd1ee1496c0b0007e79fa7ce Mon Sep 17 00:00:00 2001 From: k Date: Mon, 23 Sep 2024 19:36:15 +0330 Subject: [PATCH] typos. --- 09.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/09.md b/09.md index a0c1ec6..70b7cf7 100644 --- a/09.md +++ b/09.md @@ -6,7 +6,7 @@ Event Deletion Request `draft` `optional` -A special event with kind `5`, meaning "deletion request" is defined as having a list of one or more `e` or `a` tags, each referencing an event the author is requesting to be deleted. Deletion requests SHOULD include a `k` tag for the kind of each event being requested for deletion. +A special event with kind `5`, meaning "deletion request" is defined as having a list of one or more `e` or `a` tags, each referencing an event the author requests to be deleted. Deletion requests SHOULD include a `k` tag for the kind of each event being requested for deletion. The event's `content` field MAY contain a text note describing the reason for the deletion request. @@ -53,11 +53,11 @@ For example: The above event requests the deletation of all text notes and reactions from a user. -A kind 5 MUST NOT contain a `f` tag beside other tags, or multiple `f` tags in one event. The `"authors"` field of filter should be implicit. +A kind 5 MUST NOT contain a `f` tag beside other tags, or multiple `f` tags in one event. The `"authors"` field of the filter should be implicit. ### Usages -User can make complex bulk deletation requests with consuming small space and this bring possiblited to remove ***all posts***, ***direct messages*** or ***delete account***. +User can make complex bulk deletation requests with consuming small space and this bring possiblited to remove ***all posts***, ***direct messages***, or ***delete account***. ## Client Usage @@ -79,4 +79,4 @@ Publishing a deletion request event against a deletion request has no effect. C ## Protection for a Deletion Request -if the deletion request is intended to be applied in a set of limited relays, clients can send them as protected events and expect other relays to don't execute them in sync or broadcasting. +if the deletion request is intended to be applied in a set of limited relays, clients can send them as protected events and expect other relays to not execute them in sync or broadcasting.