Disambiguate Which Key Is Compromised When Ext. PubKey + PrivKey Are Leaked

I mistakenly inferred from the following clause that a parent extended
public key plus a child private key would be equivalent to knowing the
extended *child* private key---meaning that the *parent* private key was
still secure:

> knowledge of the extended public key + any non-hardened private key
> descending from it is equivalent to knowing the extended private key

This patch's addition of the word "parent" (twice) removes the ambiguity
and may help other readers draw the correct inference that the parent
private key is no longer secure in this case.

I also changed "+" to "plus" to avoid confusion with the actual
mathematical operations used in this BIP.
Clarify AES parameters passed in

There was some slight ambiguity in which items passed into AESEncrypt was the key and which was the block.
Add password to test vector section.
Run spell check.
BIP 44 - Specify that this BIP is not a central repository for registered coin types. Provide links to the central repo.
BIP39 grammar
Revert "Run spell check."

This reverts commit 11643a7585504d94996650fb7c390df0f4db4e41.
Restructure and make rules 2 and 4 unconditional
Merge pull request #84 from erasmospunk/master

BIP 44 - Specify that this BIP is not a central repository.
Added two BIP44 compatible wallets in Android

Subj :)
Please update info, not only the Trezor is copatible with BIP44 standard :)
BTCReceive works only with one account

It seems that it is only compatible with BIP32
Added Haskell implemetation.

Tested it and confirm it's functional.
Passphrase for test vectors + haskell implementation
Merge pull request #97 from jurov/patch-1

Added Haskell implementation.
BIP43: Block usage 0 because it's already used in BIP32. It would be unfortunate if BIP32 wallets would at one day overlap BIP43 wallets.
Clarify identifier serialization

I had a tough time interpreting "serialization of the public key", which is hashed to get the extended key identifier. Since the very next section is "Serialization format [for extended keys]" I thought that I was supposed to use the serialization of the /extended/ public key. Then I noticed "ignoring the chain code", so I tried skipping that part of the extended key serialization. Then I realized that what was meant was "the `K` half of `(K, c)`".
Merge pull request #90 from sipa/bip62up

Restructure and make rules 2 and 4 unconditional
Reverted test vectors passphrase info.

There's pull request for it already.
Removed spurious space.
Create spanish.txt