From 9ceafad0bb76e03b72f0f1be54e0d23250906267 Mon Sep 17 00:00:00 2001
From: "judymcconville@roadrunner.com" <judymcconville@roadrunner.com>
Date: Fri, 28 Apr 2017 08:59:46 -0700
Subject: [PATCH] Edited ch03.asciidoc with Atlas code editor

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

diff --git a/ch03.asciidoc b/ch03.asciidoc
index 91c4b257..ce9f9cdf 100644
--- a/ch03.asciidoc
+++ b/ch03.asciidoc
@@ -332,7 +332,7 @@ minrelaytxfee:: Set the minimum fee transaction you will relay. Below this value
 [[txindex]]
 .Transaction Database Index and txindex Option
 ****
-((("Bitcoin Core", "running core nodes", "database options")))((("transactions", "database configuration options")))By default, Bitcoin Core builds a database containing _only_ the transactions related to the user's wallet. If you want to be able to access _any_ transaction with commands like +getrawtransaction+ (see <<exploring_and_decoding_transanctions>>), you need to configure Bitcoin Core to build a complete transaction index, which can be achieved with the +txindex+ option. Set +txindex=1+ in the Bitcoin Core configuration file. If you don't set this option at first and later set it to full indexing, you need to restart +bitcoind+ with the +-reindex+ option and wait for it to rebuild the index.
+((("Bitcoin Core", "running core nodes", "database options")))((("transactions", "database configuration options")))((("txindex option")))By default, Bitcoin Core builds a database containing _only_ the transactions related to the user's wallet. If you want to be able to access _any_ transaction with commands like +getrawtransaction+ (see <<exploring_and_decoding_transanctions>>), you need to configure Bitcoin Core to build a complete transaction index, which can be achieved with the +txindex+ option. Set +txindex=1+ in the Bitcoin Core configuration file. If you don't set this option at first and later set it to full indexing, you need to restart +bitcoind+ with the +-reindex+ option and wait for it to rebuild the index.
 ****
 
 <<full_index_node>> shows how you might combine the preceding options, with a fully indexed node, running as an API backend for a bitcoin application.