From 725dbe8ec8bc846a88f04e93b48bf4fdf0beea8a Mon Sep 17 00:00:00 2001 From: Eric Passmore Date: Tue, 20 Aug 2024 12:24:23 -0700 Subject: [PATCH] add missing word for clarity --- native/60_advanced-topics/20_introduction-finalizers-voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/native/60_advanced-topics/20_introduction-finalizers-voting.md b/native/60_advanced-topics/20_introduction-finalizers-voting.md index 777e627..1be2791 100644 --- a/native/60_advanced-topics/20_introduction-finalizers-voting.md +++ b/native/60_advanced-topics/20_introduction-finalizers-voting.md @@ -47,4 +47,4 @@ For this reason it is recommended that each producer instance uses its own uniqu ### Voting and Peering All the nodeos instance from the source of the votes, to the receiver of the votes, along with any intermediate nodes must be configured to send, receive, and propagate votes. This is accomplished by enabling the vote-threading pools, configuring `vote-threads` to a value greater than zero. By default `vote-threads` is greater than zero on all block production nodes. Therefore, when two finalizers are directly peered, votes are sent and received with no additional configuration changes needed. -When nodeos instances are not directly connected, and an intermediate nodeos instance is present, the intermediate nodes must update their configuration to enable vote-threading. Failure to enable vote-threading on intermediate nodes will prevent the finalizer votes associated your producer from reaching peers. +When nodeos instances are not directly connected, and an intermediate nodeos instance is present, the intermediate nodes must update their configuration to enable vote-threading. Failure to enable vote-threading on intermediate nodes will prevent the finalizer votes associated with your producer from reaching peers.