Manage Your Wallet copy update

[josephjguerra]

remove the backslash from It's...: It's probably safest to write

Resolves brave/brave-browser#2693

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Windows
  • macOS
  • Linux
• Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
  • Windows
  • macOS
  • Linux
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

[NejcZdovc]

@josephjguerra would be awesome if you could create an issue for this PR here https://github.com/brave/brave-browser/issues so that we can link them together. If not just let me know and I can create it for you. Thank you

[josephjguerra]

added issue: brave/brave-browser#2693 @NejcZdovc Thank you

[NejcZdovc]

master (0.61) #1178
0.60 0a68e67

[NejcZdovc]

@josephjguerra thank you for the PR. 🎉 For some reason I missed that this PR was not targeted against master, so I needed to create a follow up #1178