Fix spelling in legacy test and docs using aspell

README.md

@@ -8,7 +8,7 @@ btcwallet is a daemon handling bitcoin wallet functionality for a
 single user.  It acts as both an RPC client to btcd and an RPC server
 for wallet clients and legacy RPC applications.
 
-Public and private keys are derived using the heirarchical
+Public and private keys are derived using the hierarchical
 deterministic format described by
 [BIP0032](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki).
 Unencrypted private keys are not supported and are never written to

internal/legacy/keystore/keystore_test.go

@@ -1166,7 +1166,7 @@ func TestChangePassphrase(t *testing.T) {
 
 	// Change passphrase.
 	if err := w.ChangePassphrase([]byte("potato")); err != nil {
-		t.Errorf("Changing passhprase failed: %v", err)
+		t.Errorf("Changing passphrase failed: %v", err)
 		return
 	}
 

rpc/documentation/README.md

@@ -13,4 +13,4 @@ implementation:
 - [Making API changes](./serverchanges.md)
 
 A legacy RPC server based on the JSON-RPC API of Bitcoin Core's wallet is also
-available, but documenting its usage it out of scope for these documents.
+available, but documenting its usage is out of scope for these documents.

rpc/documentation/api.md

@@ -167,7 +167,7 @@ After opening a wallet, the `WalletService` service begins running.
 **Request:** `OpenWalletRequest`
 
 - `bytes public_passphrase`: The passphrase used for the outer wallet
-  encryption.  This passhprase protects data that is made public on the
+  encryption.  This passphrase protects data that is made public on the
   blockchain.  If this passphrase has zero length, an insecure default is used
   instead.
 

rpc/documentation/serverchanges.md

@@ -46,7 +46,7 @@ must always be appended.
 It is forbidden to use the `required` attribute on a message field as this can
 cause errors during parsing when the new API is used by an older client.
 Instead, the (implicit) optional attribute is used, and the server
-implementation must return an appropiate error if the new request field is not
+implementation must return an appropriate error if the new request field is not
 set to a valid value.
 
 ## Step 2: Compile the `.proto`

rpc/legacyrpc/errors.go

@@ -19,19 +19,19 @@ import (
 // errors, and their *btcjson.RPCError creation.
 type (
 	// DeserializationError describes a failed deserializaion due to bad
-	// user input.  It cooresponds to btcjson.ErrRPCDeserialization.
+	// user input.  It corresponds to btcjson.ErrRPCDeserialization.
 	DeserializationError struct {
 		error
 	}
 
 	// InvalidParameterError describes an invalid parameter passed by
-	// the user.  It cooresponds to btcjson.ErrRPCInvalidParameter.
+	// the user.  It corresponds to btcjson.ErrRPCInvalidParameter.
 	InvalidParameterError struct {
 		error
 	}
 
 	// ParseError describes a failed parse due to bad user input.  It
-	// cooresponds to btcjson.ErrRPCParse.
+	// corresponds to btcjson.ErrRPCParse.
 	ParseError struct {
 		error
 	}