AtHeartEngineer/specs
1
0
Fork 0
mirror of https://github.com/vacp2p/specs.git synced 2026-01-09 15:28:03 -05:00
Code Issues Packages Projects Releases Wiki Activity

2 one-char typo fixes.

Browse Source
This commit is contained in:
Max von Hippel
2020-11-12 13:06:09 -07:00
committed by GitHub
parent 898d72be28
commit d23d59d1f8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
pubsub/gossipsub/gossipsub-v1.0.md
View File

@@ -217,7 +217,7 @@ state](#peering-state), and state related to the [message cache](#message-cache)
### Peering State ### Peering State
Peering state is how the router keeps track of the pubsub-capable peers it's Peering state is how the router keeps track of the pubsub-capable peers its
aware of and the relationship with each of them. aware of and the relationship with each of them.
There are three main pieces of peering state: There are three main pieces of peering state:
@@ -375,7 +375,7 @@ messages:
- On receiving a [`PRUNE(topic)` message](#prune), the router will remove the - On receiving a [`PRUNE(topic)` message](#prune), the router will remove the
sender from `mesh[topic]`. sender from `mesh[topic]`.
- On receiving an [`IHAVE(ids)` message](#ihave), the router will check it's - On receiving an [`IHAVE(ids)` message](#ihave), the router will check its
`seen` cache. If the `IHAVE` message contains message IDs that have not been `seen` cache. If the `IHAVE` message contains message IDs that have not been
seen, the router will request them with an `IWANT` message. seen, the router will request them with an `IWANT` message.