diff --git a/doc/payment-disclosure.md b/doc/payment-disclosure.md
index 51fe900ba..02b4167da 100644
--- a/doc/payment-disclosure.md
+++ b/doc/payment-disclosure.md
@@ -28,7 +28,7 @@ The ZIP describes a method of proving that a payment was sent to a shielded addr
 
 ### Example Use Case
 
-Alice the customer sends 10 ZEC to Bob the merchant at the shielded address shown on their website.  However, Bob is not sure if he received the funds.
+Alice the customer sends 10 HUSH to Bob the merchant at the shielded address shown on their website.  However, Bob is not sure if he received the funds.
 
 Alice's node is running with payment disclosure enabled, so Alice generates a payment disclosure and provides it to Bob, who verifies the payment was made.
 
diff --git a/doc/shield-coinbase.md b/doc/shield-coinbase.md
index c48e32635..68a1ee156 100644
--- a/doc/shield-coinbase.md
+++ b/doc/shield-coinbase.md
@@ -24,7 +24,7 @@ The z_shieldcoinbase call makes it easy to sweep up coinbase rewards from multip
 
     z_shieldcoinbase fromaddress toaddress (fee) (limit)
 
-The default fee is 0.0010000 ZEC and the default limit on the maximum number of UTXOs to shield is 50.
+The default fee is 0.0010000 HUSH and the default limit on the maximum number of UTXOs to shield is 50.
 
 ## Examples
 
@@ -36,11 +36,11 @@ Sweep up coinbase UTXOs from multiple transparent addresses to a shielded addres
 
     hush-cli z_shieldcoinbase "*" zMyPrivateAddress
 
-Sweep up with a fee of 1.23 ZEC:
+Sweep up with a fee of 1.23 HUSH:
 
     hush-cli z_shieldcoinbase tMyMiningAddress zMyPrivateAddress 1.23
 
-Sweep up with a fee of 0.1 ZEC and set limit on the maximum number of UTXOs to shield at 25:
+Sweep up with a fee of 0.1 HUSH and set limit on the maximum number of UTXOs to shield at 25:
 
     hush-cli z_shieldcoinbase "*" zMyPrivateAddress 0.1 25
 
diff --git a/doc/wallet-backup.md b/doc/wallet-backup.md
index 968d6c903..24cd416b0 100644
--- a/doc/wallet-backup.md
+++ b/doc/wallet-backup.md
@@ -2,19 +2,19 @@
 
 ## Overview
 
-Backing up your Hush private keys is the best way to be proactive about preventing loss of access to your ZEC.
+Backing up your Hush private keys is the best way to be proactive about preventing loss of access to your HUSH.
 
 Problems resulting from bugs in the code, user error, device failure, etc. may lead to losing access to your wallet (and as a result, the private keys of addresses which are required to spend from them).
 
 No matter what the cause of a corrupted or lost wallet could be, we highly recommend all users backup on a regular basis. Anytime a new address in the wallet is generated, we recommending making a new backup so all private keys for addresses in your wallet are safe.
 
-Note that a backup is a duplicate of data needed to spend ZEC so where you keep your backup(s) is another important consideration. You should not store backups where they would be equally or increasingly susceptible to loss or theft. 
+Note that a backup is a duplicate of data needed to spend HUSH so where you keep your backup(s) is another important consideration. You should not store backups where they would be equally or increasingly susceptible to loss or theft. 
 
 ## Instructions for backing up your wallet and/or private keys
 
 These instructions are specific for the officially supported Hush Linux client. For backing up with third-party wallets, please consult with user guides or support channels provided for those services.
 
-There are multiple ways to make sure you have at least one other copy of the private keys needed to spend your ZEC and view your shielded ZEC.
+There are multiple ways to make sure you have at least one other copy of the private keys needed to spend your HUSH and view your shielded HUSH.
 
 For all methods, you will need to include an export directory setting in your config file (`zcash.conf` located in the data directory which is `~/.zcash/` unless it's been overridden with `datadir=` setting):