nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 16:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix typos about inline code

Browse Source
This commit is contained in:
erechorse 2023-07-21 00:48:55 +09:00
parent ad39e1f3ca
commit d0cb9d0c24
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
56.md
View File

@ -10,7 +10,7 @@ Reporting
A report is a `kind 1984` note that is used to report other notes for spam,
illegal and explicit content.
The content MAY contain additional information submitted by the entity
The `content` MAY contain additional information submitted by the entity
reporting the content.
Tags

2
57.md
View File

@ -126,7 +126,7 @@ When receiving a payment, the following steps are executed:
The following should be true of the `zap receipt` event:
- The content SHOULD be empty.
- The `content` SHOULD be empty.
- The `created_at` date SHOULD be set to the invoice `paid_at` date for idempotency.
- `tags` MUST include the `p` tag AND optional `e` tag from the `zap request`.
- The `zap receipt` MUST have a `bolt11` tag containing the description hash bolt11 invoice.

6
65.md
View File

@ -10,7 +10,7 @@ A special replaceable event meaning "Relay List Metadata" is defined as an event
The primary purpose of this relay list is to advertise to others, not for configuring one's client.
The content is not used and SHOULD be an empty string.
The `content` is not used and SHOULD be an empty string.
The `r` tags can have a second parameter as either `read` or `write`. If it is omitted, it means the author uses the relay for both purposes.
@ -53,12 +53,12 @@ Authors may post events outside of the feed that they wish their followers to fo
It is suggested that relays allow any user to write their own kind `10002` event (optionally with AUTH to verify it is their own) even if they are not otherwise subscribed to the relay because
- finding where someone posts is rather important
- these events do not have content that needs management
- these events do not have `content` that needs management
- relays only need to store one replaceable event per pubkey to offer this service
### Why not in kind `0` Metadata
Even though this is user related metadata, it is a separate event from kind `0` in order to keep it small (as it should be widely spread) and to not have content that may require moderation by relay operators so that it is more acceptable to relays.
Even though this is user related metadata, it is a separate event from kind `0` in order to keep it small (as it should be widely spread) and to not have `content` that may require moderation by relay operators so that it is more acceptable to relays.
### Example