Remove segwit appendix from book

Renumbered index references in subsequent chapters

appdx-bitcore.asciidoc

@@ -4,7 +4,7 @@
 == Bitcore
 
 
-((("Bitcore", id="bitcore17")))Bitcore is a suite of tools provided by BitPay. Its goal is to provide easy-to-use tools for Bitcoin developers. Almost all of Bitcore's code is written in JavaScript. There are some modules written specifically for NodeJS. Finally, the "node" module of Bitcore includes Bitcoin Core's C++ code. Please see https://bitcore.io for more information.
+((("Bitcore", id="bitcore16")))Bitcore is a suite of tools provided by BitPay. Its goal is to provide easy-to-use tools for Bitcoin developers. Almost all of Bitcore's code is written in JavaScript. There are some modules written specifically for NodeJS. Finally, the "node" module of Bitcore includes Bitcoin Core's C++ code. Please see https://bitcore.io for more information.
 
 === Bitcore's Feature List
 
@@ -91,7 +91,7 @@ Broadcasting a transaction to the Bitcoin network
 1. Copy the code below into a file called _broadcast.js_.
 2. The +tx+ and +rbfTx+ variables are the output of +tx.serialize()+ and +rbfTx.serialize()+, respectively.
 3. In order to replace-by-fee, the peer must support bitcoind option +mempoolreplace+ and have it set to +1+.
-4. Run the file node _broadcast.js_((("", startref="bitcore17"))):
+4. Run the file node _broadcast.js_((("", startref="bitcore16"))):
 
 ----
 var p2p = require('bitcore-p2p');

appdx-bx.asciidoc

@@ -3,7 +3,7 @@
 
 == Bitcoin Explorer (bx) Commands
 
-((("Bitcoin Explorer (bx) commands", id="BX19_1", range="startofrange")))Bitcoin Explorer (bx) is a command-line tool that offers a variety of commands for key management and transaction construction. It is part of the libbitcoin bitcoin library. 
+((("Bitcoin Explorer (bx) commands", id="BX18_1", range="startofrange")))Bitcoin Explorer (bx) is a command-line tool that offers a variety of commands for key management and transaction construction. It is part of the libbitcoin bitcoin library.
 
 ----
 Usage: bx COMMAND [--help]
@@ -95,7 +95,7 @@ Generate a random "seed" value using the +seed+ command, which uses the operatin
 
 ----
 $ bx seed | bx ec-new > private_key
-$ cat private_key 
+$ cat private_key
 73096ed11ab9f1db6135857958ece7d73ea7c30862145bcc4bbc7649075de474
 ----
 
@@ -103,14 +103,14 @@ Now, generate the public key from that private key using the +ec-to-public+ comm
 
 ----
 $ bx ec-to-public < private_key > public_key
-$ cat public_key 
+$ cat public_key
 02fca46a6006a62dfdd2dbb2149359d0d97a04f430f12a7626dd409256c12be500
 ----
 
 We can reformat the +public_key+ as an address using the +ec-to-address+ command. We pass the _public_key_ into standard input:
 
 ----
-$ bx ec-to-address < public_key 
+$ bx ec-to-address < public_key
 17re1S4Q8ZHyCP8Kw7xQad1Lr6XUzWUnkG
 ----
 
@@ -178,4 +178,4 @@ $ bx mnemonic-decode < words
 eb68ee9f3df6bd4441a9feadec179ff1
 ----
 
-Mnemonic encoding can make the seed easier to record and even remember.(((range="endofrange", startref="BX19_1")))
+Mnemonic encoding can make the seed easier to record and even remember.(((range="endofrange", startref="BX18_1")))

appdx-pycoin.asciidoc

@@ -9,7 +9,7 @@ The pycoin library supports both Python 2 (2.7.x) and Python 3 (after 3.3) and c
 
 === Key Utility (KU)
 
-((("key utility (ku)", id="keyutil18")))The command-line utility +ku+ ("key utility") is a Swiss Army knife for manipulating keys. It supports BIP-32 keys, WIF, and addresses (bitcoin and alt coins). Following are some examples.
+((("key utility (ku)", id="keyutil17")))The command-line utility +ku+ ("key utility") is a Swiss Army knife for manipulating keys. It supports BIP-32 keys, WIF, and addresses (bitcoin and alt coins). Following are some examples.
 
 Create a BIP-32 key using the default entropy sources of GPG and _/dev/random_:
 
@@ -329,7 +329,7 @@ Dogecoin address : DFpN6QqFfUm3gKNaxN6tNcab1FArL9cZLE
 
 ==== Transaction Utility (TX)
 
-((("transaction utility (TX)", id="TX18")))
+((("transaction utility (TX)", id="TX17")))
 The command-line utility +tx+ will display transactions in human-readable form, fetch base transactions from pycoin's transaction cache or from web services (blockchain.info, blockcypher.com, blockr.io and chain.so are currently supported), merge transactions, add or delete inputs or outputs, and sign transactions.
 
 Following are some examples.
@@ -405,7 +405,7 @@ Total fees        0.00000 mBTC
 all incoming transaction values validated
 ----
 
-((("", startref="TX18")))Now, let's look at unspent outputs for a specific address (UTXO). In block #1, we see a coinbase transaction to +12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX+. Let's use +fetch_unspent+ to find all coins in this address:
+((("", startref="TX17")))Now, let's look at unspent outputs for a specific address (UTXO). In block #1, we see a coinbase transaction to +12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX+. Let's use +fetch_unspent+ to find all coins in this address:
 
 ----
 $ fetch_unspent 12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX

book.asciidoc

@@ -34,8 +34,6 @@ include::appdx-scriptops.asciidoc[]
 
 include::appdx-bips.asciidoc[]
 
-include::appdx-segwit.asciidoc[]
-
 include::appdx-bitcore.asciidoc[]
 
 include::appdx-pycoin.asciidoc[]