From 5651530955c6eab7cc7be315fa9fbab28d93cef2 Mon Sep 17 00:00:00 2001 From: June Han Date: Wed, 28 Feb 2024 09:27:46 +0900 Subject: [PATCH] fix: better clarity (#367) * fix: better clarity I interpreted the story differently, as in, I thought there were four participants here: me, QmAlice, QmBob, and QmRelay. `I have a peer with the Peer ID QmAlice` meant `I have a friend with Peer ID QmAlice` to me in the first place. * reword for better clarity --- content/concepts/nat/circuit-relay.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/nat/circuit-relay.md b/content/concepts/nat/circuit-relay.md index 1518bc9e..a2d69a4c 100644 --- a/content/concepts/nat/circuit-relay.md +++ b/content/concepts/nat/circuit-relay.md @@ -32,7 +32,7 @@ Today there are two versions of the circuit relay protocol, [v1](https://github. A relay circuit is identified using a [multiaddr][definition_multiaddress] that includes the [Peer ID]({{< relref "/concepts/fundamentals/peers.md#peer-id" >}}) of the peer whose traffic is being relayed (the listening peer or "relay target"). -Let's say that I have a peer with the Peer ID `QmAlice`. I want to give out my address to my friend `QmBob`, but I'm behind a NAT that won't let anyone dial me directly. +Let's say that I have a libp2p node with a Peer ID `QmAlice`. I want to give out my address to my friend `QmBob`, but I'm behind a NAT that won't let anyone dial me directly. The most basic `p2p-circuit` address I can construct looks like this: