From 5b86d78c17a412454420ccd110a9d5ffe032f414 Mon Sep 17 00:00:00 2001
From: 1VerdeMuXH1ApSZsQDkuHHZrwJaAtXTVn
 <1VerdeMuXH1ApSZsQDkuHHZrwJaAtXTVn@bitcoin.cash>
Date: Wed, 11 Dec 2019 16:15:41 -0500
Subject: [PATCH] wiki commit

---
 protocol/network/messages/verack.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/protocol/network/messages/verack.md b/protocol/network/messages/verack.md
index 121f82c..5f1056b 100644
--- a/protocol/network/messages/verack.md
+++ b/protocol/network/messages/verack.md
@@ -1,5 +1,7 @@
 # Handshake: Acknowledge ("verack")
 
-The `verack` message is sent in reply to a [version](/protocol/network/messages/version) message.  Sending a `verack` in response to a `version` message indicates to the remote that its connection and version has been accepted.  There is no version negotiation functionality between nodes; therefore if the node does not accept the version supplied by the remote then the node disconnects instead of responding with a `verack`.
+The `verack` message is sent in reply to a [version](/protocol/network/messages/version) message.  Sending a `verack` in response to a `version` message indicates to the remote that its connection and version has been accepted.
+
+There is no version negotiation functionality between nodes; therefore if the node does not accept the version supplied by the remote then the node disconnects instead of responding with a `verack`.
 
 This `verack` message consists of only a message header; the command string is "verack".
\ No newline at end of file