From 0bc24cc4a6d80faf2a635aaa12d94b79eea78a85 Mon Sep 17 00:00:00 2001
From: quantumcthulhu <37197051+quantumcthulhu@users.noreply.github.com>
Date: Wed, 25 Nov 2020 00:31:11 +0200
Subject: [PATCH] node_client mistype

---
 node_client.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node_client.asciidoc b/node_client.asciidoc
index 897cd49..8437dc3 100644
--- a/node_client.asciidoc
+++ b/node_client.asciidoc
@@ -300,7 +300,7 @@ $ docker exec bitcoind bash -c "bitcoin-cli -datadir=/bitcoind getblockchaininfo
 189
 ----
 
-+jq .blocks+ instructs the +jq+ JSON decoder to extract the field +blocks" from the +getblockchaininfo+ result. In our case, it extracts and prints the value of 189 which we could use in a subsequent command.
++jq .blocks+ instructs the +jq+ JSON decoder to extract the field +blocks+ from the +getblockchaininfo+ result. In our case, it extracts and prints the value of 189 which we could use in a subsequent command.
 
 As you will see in the following sections, we can run several containers at the same time and then interact with them individually. We can issue commands to extract information such as the Lightning node public key or to take actions such as opening a Lightning channel to another node. The +docker run+ and +docker exec+ commands together with +jq+ for JSON decoding are all we need to build a working Lightning Network that mixes many different node implementations. This enables us to try out diverse experiments on our own computer.