diff --git a/ch05_wallets.adoc b/ch05_wallets.adoc
index 87952d5c..3b72ebf7 100644
--- a/ch05_wallets.adoc
+++ b/ch05_wallets.adoc
@@ -408,7 +408,7 @@ codes continue to be widely ((("wallets", "recovery codes", startref="wallet-rec
 
 ==== Backing Up Nonkey Data
 
-The ((("wallets", "nonkey data", "backing up", id="wallet-nonkey-backups")))((("nonkey data", "backing up", id="nonkey-backups")))((("backing up", "nonkey data", id="backup-nonkey")))most important data in a wallet database is its private keys.  If
+The ((("wallets", "nonkey data, backing up", id="wallet-nonkey-backups")))((("nonkey data, backing up", id="nonkey-backups")))((("backing up", "nonkey data", id="backup-nonkey")))most important data in a wallet database is its private keys.  If
 you lose access to the private keys, you lose the ability to spend your
 bitcoins.  Deterministic key derivation and recovery codes provide a
 reasonably robust solution for backing up and recovering your keys and
@@ -502,7 +502,7 @@ Later, if the original wallet database is lost, the user can enter their
 recovery code into the wallet application to restore their seed.  The
 application can then retrieve the latest backup file, regenerate the
 encryption key, decrypt the backup, and restore all of the user's labels
-and additional ((("wallets", "nonkey data", "backing up", startref="wallet-nonkey-backups")))((("nonkey data", "backing up", startref="nonkey-backups")))((("backing up", "nonkey data", startref="backup-nonkey")))protocol data.
+and additional ((("wallets", "nonkey data, backing up", startref="wallet-nonkey-backups")))((("nonkey data, backing up", startref="nonkey-backups")))((("backing up", "nonkey data", startref="backup-nonkey")))protocol data.
 
 ==== Backing Up Key Derivation Paths