Feature/update casing secret recovery phrase #2691
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rickycodes
force-pushed
the
feature/update-casing-secret-recovery-phrase
branch
from
28074c8 to
4c55386
Compare
wachunei
approved these changes
May 17, 2021
….com:MetaMask/metamask-mobile into feature/update-casing-secret-recovery-phrase * 'feature/update-casing-secret-recovery-phrase' of github.com:MetaMask/metamask-mobile: Fix "use max" in send flow (#2689)
rickycodes
added a commit
that referenced
this pull request
Jan 31, 2022
* Update casing on Secret Recovery Phrase * Adjust wording to accomodate for space * Update snapshots * Update two other instances * Increase fieldCol width to allow for "Secret Recovery Phrase" * Update snapshots
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
It was recently brought to my attention that the casing in
Secret Recovery phrasefrom our recent update was incorrect and that thepinphraseshould be uppercase. This change takes care of that. I've also adjusted the wording slightly on the form fromImportFromSeedto better accommodate: