Skip to content

Conversation

@m4sterbunny
Copy link
Contributor

@m4sterbunny m4sterbunny commented Dec 28, 2025

Description

Light style and proof pass:

Removes latin eg/ie
Simplifies language instances
Aligns with style such as uses Next Steps in favor of multiple notes
Where possible, migrates from Web3 Auth to Embedded Wallets
Fixes links in components

Issue(s) fixed

Partial fix for 2483

Preview

Checklist

  • If this PR updates or adds documentation content that changes or adds technical meaning, it has received an approval from an engineer or DevRel from the relevant team.
  • If this PR updates or adds documentation content, it has received an approval from a technical writer.

External contributor checklist

  • I've read the contribution guidelines.
  • I've created a new issue (or assigned myself to an existing issue) describing what this PR addresses.

Note

Broad documentation style pass across Embedded Wallets features and related components.

  • Standardizes language (capitalization, punctuation, section titles like ## Next steps) and simplifies phrasing across multiple .mdx pages (funding, MPC, NFT minting, server-side verification, session management, smart accounts, wallet pregeneration, external wallets, whitelabel)
  • Replaces references to Web3Auth with Embedded Wallets where appropriate; updates links to authentication docs and dashboard
  • Adjusts bullets and headings (e.g., "Cross‑ecosystem:"), clarifies descriptions, and aligns terminology (EOA/AA, on‑ramp, allowlist)
  • Components PregenerateWallet and PregenrateSmartAccount: revise parameter descriptions, fix links, mark optional fields, minor accessibility/ARIA label improvements; no logic changes

Written by Cursor Bugbot for commit 9505a26. This will update automatically on new commits. Configure here.

@m4sterbunny m4sterbunny requested review from a team as code owners December 28, 2025 13:24
@vercel
Copy link

vercel bot commented Dec 28, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
metamask-docs Ready Ready Preview, Comment Jan 19, 2026 8:31am

Request Review

## Next steps

You can contact our [Business Team](https://calendly.com/elishamm/sales) for more information on how to access this feature.
- Contact our [Business Team](https://calendly.com/elishamm/sales) for more information on how to access this feature.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yashovardhan this is a very brittle way of offering support. Is it possible to use or create a generic bd contact that isnt tied to one individual?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

at this point no, we have only one BD person who is handling things. Even our website links to the same. Once that is resolved, we can change things here.

Copy link
Member

@yashovardhan yashovardhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good. Left a comment for the BD support call

## Next steps

You can contact our [Business Team](https://calendly.com/elishamm/sales) for more information on how to access this feature.
- Contact our [Business Team](https://calendly.com/elishamm/sales) for more information on how to access this feature.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

at this point no, we have only one BD person who is handling things. Even our website links to the same. Once that is resolved, we can change things here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants