Skip to content

Commit

Permalink
Merge pull request #915 from xiaolou86/master
Browse files Browse the repository at this point in the history
Fix typos
  • Loading branch information
staab authored Dec 4, 2023
2 parents 9913395 + 8aba861 commit c07f0ea
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion 10.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Where:

* Many "e" tags: `["e", <root-id>]` `["e", <mention-id>]`, ..., `["e", <reply-id>]`<br>
There may be any number of `<mention-ids>`. These are the ids of events which may, or may not be in the reply chain.
They are citings from this event. `root-id` and `reply-id` are as above.
They are citing from this event. `root-id` and `reply-id` are as above.

>This scheme is deprecated because it creates ambiguities that are difficult, or impossible to resolve when an event references another but is not a reply.
Expand Down
2 changes: 1 addition & 1 deletion 47.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ Errors:
## Example pay invoice flow

0. The user scans the QR code generated by the **wallet service** with their **client** application, they follow a `nostr+walletconnect:` deeplink or configure the connection details manually.
1. **client** sends an event to the **wallet service** service with kind `23194`. The content is a `pay_invoice` request. The private key is the secret from the connection string above.
1. **client** sends an event to the **wallet service** with kind `23194`. The content is a `pay_invoice` request. The private key is the secret from the connection string above.
2. **wallet service** verifies that the author's key is authorized to perform the payment, decrypts the payload and sends the payment.
3. **wallet service** responds to the event by sending an event with kind `23195` and content being a response either containing an error message or a preimage.

Expand Down
2 changes: 1 addition & 1 deletion 53.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Live Activities

`draft` `optional`

Service providers want to offer live activities to the Nostr network in such a way that participants can easily logged and queried by clients. This NIP describes a general framework to advertise the involvement of pubkeys in such live activities.
Service providers want to offer live activities to the Nostr network in such a way that participants can easily log and query by clients. This NIP describes a general framework to advertise the involvement of pubkeys in such live activities.

## Concepts

Expand Down
2 changes: 1 addition & 1 deletion 90.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ There are two actors in the workflow described in this NIP:
* Service providers (npubs who fulfill jobs)

## Job request (`kind:5000-5999`)
A request to process data, published by a customer. This event signals that an customer is interested in receiving the result of some kind of compute.
A request to process data, published by a customer. This event signals that a customer is interested in receiving the result of some kind of compute.

```json
{
Expand Down

0 comments on commit c07f0ea

Please sign in to comment.