From 697fa3a788bdd459f19bdf43e697e071b298d43e Mon Sep 17 00:00:00 2001 From: Sergey Kaunov Date: Mon, 7 Jul 2025 03:45:00 +0300 Subject: [PATCH] Update protocols.md Recover a sane sections levels. --- content/concepts/fundamentals/protocols.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/concepts/fundamentals/protocols.md b/content/concepts/fundamentals/protocols.md index 60b5f471..0326e798 100644 --- a/content/concepts/fundamentals/protocols.md +++ b/content/concepts/fundamentals/protocols.md @@ -47,13 +47,13 @@ developer-friendly and enables [easier matching by version](#match-using-semver) #### Handler functions To accept connections, a libp2p application will register handler functions for protocols using their protocol id with the -[switch][definition_switch] (aka "swarm"), or a higher level interface such as [go's Host interface](https://github.com/libp2p/go-libp2p/blob/master/core/host/host.go). +[switch][definition_switch] (aka "swarm"), or a higher level interface such as [the Host interface in the Go implementation](https://github.com/libp2p/go-libp2p/blob/master/core/host/host.go). The handler function will be invoked when an incoming stream is tagged with the registered protocol id. If you register your handler with a [match function](#using-a-match-function), you can choose whether to accept non-exact string matches for protocol ids, for example, to match on [semantic major versions](#match-using-semver). -#### Binary streams +### Binary streams The "medium" over which a libp2p protocol transpires is a bi-directional binary stream with the following properties: