Edited ch05_wallets.adoc with Atlas code editor

ch05_wallets.adoc

@@ -321,6 +321,7 @@ Aezeed::
   on both the backup and the recovery software supporting the same
   word list.
 
+[role="less_space pagebreak-before"]
 Muun::
   Used in ((("Muun recovery codes")))the Muun wallet, which defaults to requiring spending
   transactions be signed by multiple keys, this is a nonword code that
@@ -373,7 +374,6 @@ seed for a BIP32 tree of keys, but they won't be the same trees.
 Different passphrases will result in different keys.  That can be a
 positive or a negative, depending on your perspective:
 
-[role="less_space pagebreak-before"]
 - On the positive, if someone obtains your recovery code (but not your
   passphrase), they will see a valid BIP32 tree of keys.
   If you prepared for that contingency and sent some bitcoins to the
@@ -382,7 +382,7 @@ positive or a negative, depending on your perspective:
   you with a warning that your recovery code has been compromised,
   allowing you to investigate and take corrective measures.
   The ability to create multiple passphrases for the same recovery code
-  that all look valid is a type of _plausible deniability._
+  that all look valid is a type of _plausible deniability_.
 
 - On the negative, if you're coerced to give an attacker a recovery
   code (with or without a passphrase) and it doesn't yield the amount of