Index: nano.man
==================================================================
--- nano.man
+++ nano.man
@@ -238,11 +238,11 @@
 Nano uses Ed25519 with Blake2b as the cryptographic hashing primitive for
 digital signatures, rather than the common construction of Ed25519 with the
 SHA2-512 cryptographic hashing function.
 
 Nano implements a "blockchain", which is a cryptographic linked-list, by
-identifying every "block" by its crytographic hash and providing a pointer from
+identifying every "block" by its cryptographic hash and providing a pointer from
 every block to its predecessor in the "chain" as part of the hashed data.
 
 This predecessors is referred to here as the "previous" block.  In Nano,
 each account has its own blockchain and they reference each other using a
 data structure referred to as "block lattice", where the individual chains
@@ -274,17 +274,17 @@
 .RI ( i.e. ,
 a block with a unique
 .I previous
 value).  Since voting is an active and on-going process that occurs on the Nano
 peer-to-peer network, participants must be online to vote their stake.  As this
-is often inconvienent or impossible, stakeholders may select another
+is often inconvenient or impossible, stakeholders may select another
 stakeholder to vote their share of the network.  This delegate is referred to
 as a
 .IR representative .
 
 Representatives should be chosen carefully by stakeholders since malicious
-representatives may attempt to gather voting power and destablize the Nano
+representatives may attempt to gather voting power and destabilize the Nano
 network by altering decisions made by consensus previously.
 
 Nano accounts are referred to by address.  A Nano address starts with the
 prefix
 .RB \(dq nano_ "\(dq or \(dq" xrb_ \(dq.
@@ -298,11 +298,11 @@
 .IR wallet .
 A
 .I wallet
 is a conceptual entity that is used to refer to a
 .IR seed ,
-which is a random 256-bit number that can be used to derive mulitple
+which is a random 256-bit number that can be used to derive multiple
 private/public keypairs from.
 
 Balances in Nano are stored in a 128-bit integer value.  There are various
 units for representing the balance, the smallest and base unit is called
 .RI \(dq raw \(dq.
@@ -314,11 +314,11 @@
 Nano addresses are composed of a prefix (either
 .RB \(dq nano_ \(dq
 or
 .RB \(dq xrb_ \(dq)
 and 300 bits of base32 encoded data.  The 300-bits of base32 encoded data
-produce a string that is 6 charectars long using the base32 alphabet
+produce a string that is 6 characters long using the base32 alphabet
 .BR 13456789abcdefghijkmnopqrstuwxyz .
 The format of these 300 bits are
 .EX
 
   [Padding (4 bits: 0)].[Public Key (256 bits)].[Checksum (40 bits)]
@@ -344,11 +344,11 @@
 .RB ? -verify | -no-verify ?
 .BI " -> " publicKey
 
 Converts a Nano address to a public key.  The
 .B -hex
-option indicates that the public key should be returned in hexidecimal form.
+option indicates that the public key should be returned in hexadecimal form.
 The
 .-B -binary
 option indicates that the public key should be returned in binary form.
 The
 .B -verify
@@ -384,11 +384,11 @@
 .TP
 .B ::nano::key::newSeed
 .RB ? -hex | -binary ?
 .RI "-> " seed
 
-Generates a new seed.  A seed is a 256-bit bitfield which, along with a 32-bit
+Generates a new seed.  A seed is a 256-bit bit-field which, along with a 32-bit
 index, is used to derive enumerated keys from a single point of entropy.  See
 the
 .B fromSeed
 procedure.
 .HB
@@ -397,11 +397,11 @@
 .B ::nano::key::newKey
 .RB ? -hex | -binary ?
 .RI " -> " privateKey
 
 Generates a new private key.  A private key can be used to sign transactions,
-which can then be verified with its cooresponding public key (see
+which can then be verified with its corresponding public key (see
 .BR publicKeyFromPrivateKey ).
 This procedure is normally not used, but rather private keys are derived
 from a
 .I seed
 and
@@ -439,11 +439,11 @@
 .I privateKey
 .RB ? -hex | -binary ?
 .RI " -> " publicKey
 
 Converts a private key into its corresponding public key.  Normally Ed25519
-private keys are a concatencation of the private and public keys, however in
+private keys are a concatenation of the private and public keys, however in
 this package they are each treated separately.
 .HB
 
 .SS Low-level Block
 .TP
@@ -580,11 +580,11 @@
 .I blockData
 .I privateKey
 .RB ? -hex | -binary ?
 .RI " -> " signature
 
-This is a convienence procedure which computes the hash of a block given as
+This is a convenience procedure which computes the hash of a block given as
 .IR blockData ,
 and then calls
 .BR signBlockHash .
 .HB
 
@@ -608,11 +608,11 @@
 .I blockData
 .I signature
 .I publicKey
 .RI " -> " boolean
 
-This is a convienence procedure which computes the hash of a block given as
+This is a convenience procedure which computes the hash of a block given as
 .IR blockData ,
 and then calls
 .BR verifyBlockHash .
 
 .TP
@@ -736,11 +736,11 @@
 .TP
 .B ::nano::work::fromBlock
 .I blockData
 .RI " -> " work
 
-This is a convienence procedure which computes work data (either a block hash
+This is a convenience procedure which computes work data (either a block hash
 or a public key) for a given block and then calls
 .BR fromWorkData .
 
 .TP
 .B ::nano::work::validate