From b0de0878e91f31e82eec2169637002b3135ebdf1 Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Fri, 21 Nov 2014 05:23:31 -0800 Subject: [PATCH] Made changes to appdx-pycoin.asciidoc --- appdx-pycoin.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/appdx-pycoin.asciidoc b/appdx-pycoin.asciidoc index 21682013..66084c08 100644 --- a/appdx-pycoin.asciidoc +++ b/appdx-pycoin.asciidoc @@ -10,7 +10,7 @@ The pycoin library supports both Python 2 (2.7.x) and Python 3 (after 3.3), and === Key Utility (KU) -((("key utility (ku)", id="ix_appdx-pycoin-asciidoc0", range="startofrange")))The command-line utility +ku+ ("key utility") is a Swiss Army knife for manipulating keys. It supports BIP32 keys, WIF, and address (bitcoin and alt coins). Following are some examples. +((("key utility (ku)", id="ix_appdx-pycoin-asciidoc0", range="startofrange")))The command-line utility +ku+ ("key utility") is a Swiss Army knife for manipulating keys. It supports BIP32 keys, WIF, and addresses (bitcoin and alt coins). Following are some examples. Create a BIP32 key using the default entropy sources of GPG and _/dev/random_: @@ -394,7 +394,7 @@ including unspents in hex dump since transaction not fully signed ---- ==== -The final line appears because to validate the transactions' signatures, you technically need to the source transactions. So let's add +-a+ to augment the transactions with source information: +The final line appears because to validate the transactions' signatures, you technically need the source transactions. So let's add +-a+ to augment the transactions with source information: ==== ----