From 663f8cf7cc8fe2518ca801d054d250d4a6d31e9f Mon Sep 17 00:00:00 2001 From: clenser Date: Wed, 18 Oct 2023 19:11:17 +0000 Subject: [PATCH] Edited ch05_wallets.adoc with Atlas code editor --- ch05_wallets.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch05_wallets.adoc b/ch05_wallets.adoc index 2b222cfa..edafc24e 100644 --- a/ch05_wallets.adoc +++ b/ch05_wallets.adoc @@ -348,7 +348,7 @@ status]. .Recovery Code Passphrases **** -The BIP39, ((("passphrases (for recovery codes)", id="passphrase")))Electrum v2, Aezeed, and SLIP39 schemes may all be used with an +The BIP39, ((("wallets", "recovery codes", "passphrases", id="wallet-recovery-passphrase")))((("recovery codes", "passphrases", id="recovery-code-passphrase")))((("passphrases (for recovery codes)", id="passphrase")))Electrum v2, Aezeed, and SLIP39 schemes may all be used with an optional passphrase. If the only place you keep this passphrase is in your memory, it has the same advantages and disadvantages as memorizing your recovery code. However, there's a further set of trade-offs @@ -403,7 +403,7 @@ Many users and developers disagree on which approach is better, with some strongly in favor of plausible deniability and others preferring the increased safety that error detection gives novice users and those under duress. We suspect the debate will continue for as long as recovery -codes continue to be widely ((("wallets", "recovery codes", startref="wallet-recovery2")))((("recovery codes", startref="recovery-code2")))((("passphrases (for recovery codes)", startref="passphrase")))used. +codes continue to be widely ((("wallets", "recovery codes", startref="wallet-recovery2")))((("recovery codes", startref="recovery-code2")))((("passphrases (for recovery codes)", startref="passphrase")))((("wallets", "recovery codes", "passphrases", startref="wallet-recovery-passphrase")))((("recovery codes", "passphrases", startref="recovery-code-passphrase")))used. **** ==== Backing Up Nonkey Data