diff --git a/core/src/main/java/com/google/bitcoin/core/WalletEventListener.java b/core/src/main/java/com/google/bitcoin/core/WalletEventListener.java
index 4962babd..7e96baa3 100644
--- a/core/src/main/java/com/google/bitcoin/core/WalletEventListener.java
+++ b/core/src/main/java/com/google/bitcoin/core/WalletEventListener.java
@@ -25,7 +25,7 @@ import java.util.List;
  */
 public interface WalletEventListener {
     /**
-     * This is called on a Peer thread when a transaction is seen that sends coins <b>to</b> this wallet, either because it
+     * This is called when a transaction is seen that sends coins <b>to</b> this wallet, either because it
      * was broadcast across the network or because a block was received. If a transaction is seen when it was broadcast,
      * onCoinsReceived won't be called again when a block containing it is received. If you want to know when such a
      * transaction receives its first confirmation, register a {@link TransactionConfidence} event listener using
@@ -40,7 +40,7 @@ public interface WalletEventListener {
     void onCoinsReceived(Wallet wallet, Transaction tx, BigInteger prevBalance, BigInteger newBalance);
 
     /**
-     * This is called on a Peer thread when a transaction is seen that sends coins <b>from</b> this wallet, either
+     * This is called when a transaction is seen that sends coins <b>from</b> this wallet, either
      * because it was broadcast across the network or because a block was received. This may at first glance seem 
      * useless, because in the common case you already know about such transactions because you created them with
      * the Wallets createSend/sendCoins methods. However when you have a wallet containing only keys, and you wish
@@ -59,8 +59,8 @@ public interface WalletEventListener {
 
     // TODO: Finish onReorganize to be more useful.
     /**
-     * <p>This is called on a Peer thread when a block is received that triggers a block chain re-organization.
-     * </p>
+     * <p>This is called when a block is received that triggers a block chain re-organization.</p>
+     *
      * <p>A re-organize means that the consensus (chain) of the network has diverged and now changed from what we
      * believed it was previously. Usually this won't matter because the new consensus will include all our old
      * transactions assuming we are playing by the rules. However it's theoretically possible for our balance to
@@ -71,7 +71,7 @@ public interface WalletEventListener {
     void onReorganize(Wallet wallet);
 
     /**
-     * <p>Called on a Peer thread when a transaction changes its confidence level. You can also attach event listeners to
+     * <p>Called when a transaction changes its confidence level. You can also attach event listeners to
      * the individual transactions, if you don't care about all of them. Usually you would save the wallet to disk after
      * receiving this callback unless you already set up autosaving.</p>
      *