pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-07-23 03:45:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix typos (#2193)

Browse Source
This commit is contained in:
vuittont60
2023-11-07 20:11:06 +08:00
committed by GitHub
parent 295a848301
commit 4caa3d8d8e
23 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
polkadot/roadmap/implementers-guide/src/node/backing/statement-distribution-legacy.md
+1 -1
View File
@@ -149,7 +149,7 @@ The receiver of such a message needs to request the actual payload via request/r
This is necessary as distribution of a large payload (mega bytes) via gossip would make the network collapse and timely
distribution of statements would no longer be possible. By using request/response it is ensured that each peer only
transferes large data once. We only take good care to detect an overloaded peer early and immediately move on to a
transfers large data once. We only take good care to detect an overloaded peer early and immediately move on to a
different peer for fetching the data. This mechanism should result in a good load distribution and therefore a rather
optimal distribution path.
polkadot/roadmap/implementers-guide/src/node/backing/statement-distribution.md
+1 -1
View File
@@ -3,7 +3,7 @@
This subsystem is responsible for distributing signed statements that we have generated and forwarding statements
generated by our peers. Received candidate receipts and statements are passed to the [Candidate Backing
subsystem](candidate-backing.md) to handle producing local statements. On receiving
`StatementDistributionMessage::Share`, this subsystem distributes the message across the network with redundency to
`StatementDistributionMessage::Share`, this subsystem distributes the message across the network with redundancy to
ensure a fast backing process.
## Overview