Skip to content

typo: typos fixed #396

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

typo: typos fixed #396

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/concepts/multiplex/early-negotiation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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" >}}).

<!-- ADD DIAGRAM -->

Expand Down
2 changes: 1 addition & 1 deletion content/concepts/similar-projects/devp2p.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion content/concepts/transports/webrtc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down