Fix an incorrect comment, and a typo

README.rst

@@ -83,7 +83,7 @@ Future/TODO
 - investigating leveldb space / speed tradeoffs
 - seeking out further efficiencies.  ElectrumX is CPU bound; it would not
   surprise me if there is a way to cut CPU load by 10-20% more.  To squeeze
-  more out would probably require some things to move to C or C++.
+  even more out would probably require some things to move to C or C++.
 
 Once I get round to writing the server part, I will add DoS
 protections if necessary to defend against requests for large
@@ -92,7 +92,7 @@ could smoothly serve the whole history of the biggest Satoshi dice
 address with minimal negative impact on other connections; we shall
 have to see.  If the requestor is running Electrum client I am
 confident that it would collapse under the load far more quickly that
-the server would; it is very inefficeint at handling large wallets
+the server would; it is very inefficient at handling large wallets
 and histories.
 
 

server/db.py

@@ -439,10 +439,10 @@ class DB(object):
         return sum(utxo.value for utxo in utxos)
 
     def get_history(self, hash160):
-        '''Returns a sorted list of (tx_hash, height) tuples of transactions
+        '''Returns an unpruned, sorted list of (tx_hash, height) tuples of
-        that touched the address, earliest in the blockchain first.
+        transactions that touched the address, earliest in the
-        Only includes outputs that have been spent.  Other
+        blockchain first.  Includes both spending and receiving
-        transactions will be in the UTXO set.
+        transactions.
         '''
         prefix = b'H' + hash160
         a = array.array('I')