Merge pull request #4 from MostroP2P/fix-typos

fix-typos

Author: Catrya

src/how-it-works.md

@@ -48,4 +48,4 @@ If during the process, Alice and Bob decide not to proceed with the exchange, th
 4. **Alice releases the sats:**  
    When Alice presses the *release* button in her client, she sends a [NIP-59](https://github.com/nostr-protocol/nips/blob/master/59.md) message to Mostrod indicating that the sats should be released to Bob. Then, the LN node associated with that instance of Mostrod settles the payment of the [hold invoice](./hold-invoice.md) and pays the invoice provided by Bob. At the end of the process, Mostrod publishes an event 38383 for that order with the status `success` and sends a [NIP-59](https://github.com/nostr-protocol/nips/blob/master/59.md) message to Alice and Bob, requesting that they rate their counterparty, who send back their rating through a [NIP-59](https://github.com/nostr-protocol/nips/blob/master/59.md) message.
 
-For more details on the communication between Mostrod and its clients, you can read [here](https://mostro.network/messages).
+For more details on the communication between Mostrod and its clients, you can read [here](https://mostro.network/protocol/).

src/privacy.md

@@ -6,4 +6,4 @@ The [Mostro clients](./clients.md) will not share users' private keys with any M
 
 The communication between the buyer and seller during a transaction is client-to-client, using messages encrypted with the [NIP-44](https://github.com/nostr-protocol/nips/blob/master/44.md) algorithm. Although this reveals the public keys involved in the communication, users always must use a new Nostr identity for each transaction, ensuring their privacy. Additionally, these messages are not sent to Mostrod, meaning that it does not access or collect users' personal information.
 
-Moreover, [NIP-44](https://github.com/nostr-protocol/nips/blob/master/44.md) allows the client to create a *conversation key* associated with the key pair of the two users involved in a transaction, to which only they have access. This *conversation key* have a copy of the conversation between both users, and in case of a [dispute](./disputes.md), if the users wish, they can provide it to the administrator handling their case as evidence of the facts.
+Moreover, [NIP-44](https://github.com/nostr-protocol/nips/blob/master/44.md) allows the client to create a *conversation key* associated with the key pair of the two users involved in a transaction, to which only they have access. This *conversation key* has a copy of the conversation between both users, and in case of a [dispute](./disputes.md), if the users wish, they can provide it to the administrator handling their case as evidence of the facts.