Wrong "Manual Backup" vernacular when creating a mobile wallet

[gomesalexandre]

Overview

The app seems to imply you're doing a manual explicit backup, while it's more like an implicit backup as part of the import flow :

• "Confirm Backup" is actually fine, you're technically backing the seed up as part of the import flow

• "Manual Backup" is not. We're not doing a manual backup here

Also feeling weird about the "Your wallet has been succesfully backed up" copy @shapeshift/product. This seems to imply the app did back things up, where really it's some user real-world (yes it exists) action happening off-the-app.
Maybe something like "Don't forget to keep your seed somewhere safe!" of sorts instead?

References and additional details

N/A

Acceptance Criteria

• For the sake of simplicity, let's use "Backup" vernacular consistently without the manual bit, which will work fine for both import and explicit backup

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

[NeOMakinG]

Pinging @shapeshift/product and setting "needs product" tag for this one so we don't to back and forth on copy changes

[0xApotheosis]

100% agree, this felt really weird to me too. More strange still is that the final message I got in the "create a wallet flow" is "wallet successfully backed up".

I was like "wait, I thought I was creating a wallet?".

[twblack88]

1. Confirm wallet is better. let's just do that earlier in the flow. That works with the copy too "save in a secure place..." yadda yadda.
2. final screen should be: Backup confirmed. You successfully created and secured your wallet. View wallet

Longer term, we should consider if we want the cta to be fund wallet and drop into that flow cc @tolltalcrypto