chore: Update Spanish strings for Card onboarding flow cp-7.58.3

[Montoya]

Correct translation for card onboarding flow in Spanish

Description

A typo and poor translation in the card onboarding flow needed correcting for Spanish

Changelog

CHANGELOG entry: null

Related issues

Fixes: n/a

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Refines Spanish text for MetaMask Card onboarding by correcting the non-cardholder title and description.

^{Written by Cursor Bugbot for commit 356e6fb. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

The only changed file is locales/languages/es.json, which is a Spanish language translation file. This is a pure localization change that:

1. Does not affect functionality: Translation files only contain translated strings and do not contain any executable code or logic
2. Does not impact E2E tests: E2E tests typically use test IDs and selectors that are not language-dependent, and there's no evidence of E2E tests relying on Spanish translations (search found no references to Spanish locale in e2e/ directory)
3. Low risk: Translation updates cannot break core wallet functionality, network operations, UI logic, or any critical user flows
4. No code changes: Only JSON translation data was modified

Since this is purely a content/localization change with no functional impact, no E2E tests need to be run. The risk is low and confidence is high (95%) because:

• The change is confined to translation content only
• No code logic, components, controllers, or critical paths were modified
• E2E tests don't validate translated text content
• The file type and location clearly indicate non-functional changes

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud