Merge bitcoin/bitcoin#32866: doc: add note for watch-only wallet migration

5888b4a doc: add note for watch-only wallet migration (rkrux)

Pull request description:

  This was suggested in a previous PR #31423.

ACKs for top commit:
  achow101:
    ACK 5888b4a
  brunoerg:
    reACK 5888b4a
  jonatack:
    ACK 5888b4a

Tree-SHA512: 96e51eda30a1f31cfd82ae3296ca97c9236599b18e19086dbde3a908f6fe66af8f2de7aa147bdb9ebccb2059c809a25ddfb0c23da57e1a84a35b62ca0a44e3c3

Author: achow101

doc/managing-wallets.md

@@ -144,12 +144,15 @@ If the wallet passphrase is too complex and is subsequently forgotten or lost, t
 
 Legacy wallets (traditional non-descriptor wallets) can be migrated to become Descriptor wallets
 through the use of the `migratewallet` RPC. Migrated wallets will have all of their addresses and private keys added to
-a newly created Descriptor wallet that has the same name as the original wallet. Because Descriptor
-wallets do not support having private keys and watch-only scripts, there may be up to two
+a newly created Descriptor wallet that has the same name as the original wallet. As Descriptor
+wallets do not support having both private keys and watch-only scripts, there may be up to two
 additional wallets created after migration. In addition to a descriptor wallet of the same name,
 there may also be a wallet named `<name>_watchonly` and `<name>_solvables`. `<name>_watchonly`
-contains all of the watchonly scripts. `<name>_solvables` contains any scripts which the wallet
-knows but is not watching the corresponding P2(W)SH scripts.
+contains all of the watchonly scripts. `<name>_solvables` contains any scripts that the wallet
+knows but for which it is not watching the corresponding P2(W)SH scripts. If the legacy wallet
+contains only watch-only scripts and no private keys, then only the `<name>_watchonly` wallet
+will be created and the descriptor wallet with the same name will not be created. Additionally,
+the created watch-only descriptor wallet will not have private keys enabled.
 
 Migrated wallets will also generate new addresses differently. While the same BIP 32 seed will be
 used, the BIP 44, 49, 84, and 86 standard derivation paths will be used. After migrating, a new