From dc290d7b8793bd39c24f3842d37db4d31cabb8af Mon Sep 17 00:00:00 2001
From: jerzybrzoska <51721153+jerzybrzoska@users.noreply.github.com>
Date: Sat, 30 Jan 2021 16:14:37 +0100
Subject: [PATCH] "verack message" instead of "verack"

The reader was not introduced to the term verack earlier - 'verack' appears only once in this chapter. Thus, "verack message" seems more readable.
---
 ch08.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ch08.asciidoc b/ch08.asciidoc
index b5e4f7bd..8474ebea 100644
--- a/ch08.asciidoc
+++ b/ch08.asciidoc
@@ -76,7 +76,7 @@ To connect to a known peer, nodes establish a TCP connection, usually to port 83
 
 (See http://bit.ly/1qlsC7w[GitHub] for an example of the +version+ network message.)
 
-The +version+ message is always the first message sent by any peer to another peer. The local peer receiving a +version+ message will examine the remote peer's reported +nVersion+ and decide if the remote peer is compatible. If the remote peer is compatible, the local peer will acknowledge the +version+ message and establish a connection by sending a +verack+.
+The +version+ message is always the first message sent by any peer to another peer. The local peer receiving a +version+ message will examine the remote peer's reported +nVersion+ and decide if the remote peer is compatible. If the remote peer is compatible, the local peer will acknowledge the +version+ message and establish a connection by sending a +verack+ message.
 
 How does a new node find peers? The first method is to query DNS using a number of "DNS seeds," which are DNS servers that provide a list of IP addresses of bitcoin nodes. Some of those DNS seeds provide a static list of IP addresses of stable bitcoin listening nodes. Some of the DNS seeds are custom implementations of BIND (Berkeley Internet Name Daemon) that return a random subset from a list of bitcoin node addresses collected by a crawler or a long-running bitcoin node.  The Bitcoin Core client contains the names of nine different DNS seeds. The diversity of ownership and diversity of implementation of the different DNS seeds offers a high level of reliability for the initial bootstrapping process. In the Bitcoin Core client, the option to use the DNS seeds is controlled by the option switch +-dnsseed+ (set to 1 by default, to use the DNS seed).