From 26621a2729152d4579084a7cbb9bef939c126bf0 Mon Sep 17 00:00:00 2001 From: Pandit Dhamdhere Date: Wed, 12 Feb 2025 10:06:48 +0530 Subject: [PATCH] typos fixed --- content/concepts/multiplex/early-negotiation.md | 2 +- content/concepts/similar-projects/devp2p.md | 2 +- content/concepts/transports/webrtc.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/concepts/multiplex/early-negotiation.md b/content/concepts/multiplex/early-negotiation.md index 78c1d02a..575bb45f 100644 --- a/content/concepts/multiplex/early-negotiation.md +++ b/content/concepts/multiplex/early-negotiation.md @@ -23,7 +23,7 @@ second First, the security protocol is negotiated, then this protocol is used to perform a cryptographic handshake. libp2p currently supports [Noise]({{< relref "/concepts/secure-comm/noise.md" >}}) and [TLS 1.3]({{< relref "/concepts/secure-comm/tls.md" >}}). Once the cryptographic handshake completes, multistream-select runs again on top of -the secured connection to negotiate a steam multiplexer, like [yamux]({{< relref "/concepts/multiplex/yamux.md" >}}) or [mplex]({{< relref "/concepts/multiplex/mplex.md" >}}). +the secured connection to negotiate a stream multiplexer, like [yamux]({{< relref "/concepts/multiplex/yamux.md" >}}) or [mplex]({{< relref "/concepts/multiplex/mplex.md" >}}). diff --git a/content/concepts/similar-projects/devp2p.md b/content/concepts/similar-projects/devp2p.md index 1c17f4f5..ec8432cd 100644 --- a/content/concepts/similar-projects/devp2p.md +++ b/content/concepts/similar-projects/devp2p.md @@ -54,7 +54,7 @@ Modularity provides libp2p with a few advantages: *To learn more about browser connectivity, visit: [connectivity.libp2p.io](https://connectivity.libp2p.io/)* A great similarity that both devp2p and libp2p share is language interoperability. -For example, go-libp2p and rust-libp2p are written in different programming languages, but are still compatible and interoperabile with each other. The same holds true for devp2p. +For example, go-libp2p and rust-libp2p are written in different programming languages, but are still compatible and interoperable with each other. The same holds true for devp2p. [Ethereum Node Records]: https://github.com/ethereum/devp2p/blob/master/enr.md [Node Discovery Protocol v4]: https://github.com/ethereum/devp2p/blob/master/discv4.md diff --git a/content/concepts/transports/webrtc.md b/content/concepts/transports/webrtc.md index 7ffd213c..b41dea72 100644 --- a/content/concepts/transports/webrtc.md +++ b/content/concepts/transports/webrtc.md @@ -154,7 +154,7 @@ This works as follows: - _A_ initiates the `webrtc-signaling` protocol to _B_ via a stream over the relayed connection - This signaling stream is used to: - Exchange SDPs between nodes (an offer from _A_ and an answer from _B_) - - This include exchangning information about the network connection (in WebRTC parlance this is called [exchanging ICE candidates](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Connectivity#ice_candidates)) + - This include exchanging information about the network connection (in WebRTC parlance this is called [exchanging ICE candidates](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Connectivity#ice_candidates)) - The SDP messages are passed to the browsers WebRTC stack, which then tries to establish a direct connection. - A successful direct connection is established between _A_ and _B_ - In this case, both browser nodes will close the signaling protocol stream