[No QA] Update Expensify Card article with name and phone number details

[MelvinBot]

Summary

• Updates the Cardholder Settings and Features article title to "Update Your Expensify Card Details"
• Adds a section on how to update the name on your Expensify Card via Legal Name under Account > Profile > Private
• Adds a section on how to update the phone number linked to your Expensify Card for 3D Secure verification
• Adds FAQ entry for changing the embossed name on a physical card (update legal name + request replacement card)

$ https://github.com/Expensify/Expensify/issues/590265

Test plan

• Verify the article renders correctly on HelpDot
• Confirm navigation paths match the current UI (Account > Profile > Private > Legal name / Phone number)
• Verify cross-links to 3D Secure Verification article and other referenced articles work correctly

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR enhances the Cardholder Settings and Features article by adding two new procedural sections (updating the name and phone number on an Expensify Card) and a supporting FAQ entry. It also makes several housekeeping improvements: converting absolute URLs to relative paths, capitalizing section headings consistently, correcting product name capitalization ("Expensify Card" vs. "Expensify card"), and removing a stale link to an Expensify Classic article. The changes are well-structured and add genuinely useful content. A few areas could be tightened further.

Scores Summary

• Readability: 8/10 - Clear, step-by-step instructions written at an accessible reading level. Sentence structure is clean and logical. Minor deductions: the title change to "Update Your Expensify Card Details" narrows the scope implied by the title, since the article still covers activation, Smart Limits, notifications, expenses, virtual cards, digital wallets, and troubleshooting -- not just "updating details." The original title was arguably more representative of the full article, though neither is perfect.
• AI Readiness: 7/10 - Descriptive headings with full task phrasing ("How to Update the Name on Your Expensify Card") are strong. Keywords in YAML metadata are expanded appropriately. However, the article is missing the internalScope field that is present in 36 other New Expensify articles (including the sibling 3D Secure article in the same folder). A suggested value: internalScope: Audience is Expensify Card cardholders. Covers activating, using, and managing the Expensify Card, including updating the cardholder name and phone number, Smart Limits, notifications, virtual cards, digital wallets, and troubleshooting. Does not cover admin card issuance, card program setup, or accounting integrations.
• Style Compliance: 9/10 - Consistent "Expensify Card" capitalization, proper bold formatting for UI elements, relative URLs, and title-case headings. One small inconsistency: "Click Save" vs. "click Save" -- the imperative verb casing should be consistent across steps. Also, the button label "Reveal details" (lowercase "d") was changed from "Reveal Details" -- confirm this matches the actual UI label.

Key Findings

Positive aspects

• The two new sections are well-written, task-oriented, and follow a clear numbered-step format that is easy for users to follow.
• Converting absolute help.expensify.com URLs to relative paths is a good maintenance practice and keeps links functional across environments.
• Adding relevant keywords (update name, update phone number, legal name, 3D Secure) to the YAML front matter improves discoverability.
• The new FAQ entry ("How do I change the name embossed on my physical Expensify Card?") anticipates a natural follow-up question and ties the new content together well.
• Removing the link to the Expensify Classic article (expensify-classic/expensify-card/Request-the-Expensify-Card) is correct -- New Expensify articles should not cross-link to Classic documentation.

Items to address

• Missing internalScope in YAML metadata. This field is present in the sibling 3D Secure article and in 36 other New Expensify docs. Adding it would improve AI retrieval accuracy.
• Title mismatch with article scope. The new title "Update Your Expensify Card Details" suggests the article is only about updating card details, but the article still covers activation, Smart Limits, notifications, expenses, virtual cards, digital wallets, and FAQ troubleshooting. Consider a title that reflects the full breadth, such as "Manage Your Expensify Card" or "Expensify Card Cardholder Guide," or alternatively, split the update-specific content into its own focused article.
• "What if I haven't received my Expensify Card?" FAQ lost its guidance link. The old version linked to a guide for requesting a new card. The diff removes that link (correctly, since it pointed to Classic docs), but the replacement text ("confirm your mailing address is correct and request a new card") does not tell the user how to request a new card. Consider adding a cross-reference to the "How do I deactivate my card and request a replacement?" FAQ entry directly below, or inline the steps briefly.

Recommendations

1. Add the internalScope YAML field to align with the emerging standard across New Expensify documentation.
2. Reconsider the article title to better represent the full scope of the content, or split the new "update" sections into a separate article.
3. Add guidance to the "haven't received my card" FAQ so users know where to go for help now that the Classic link has been removed. A simple "See the replacement steps below" with an anchor or reference would suffice.
4. Verify the "Reveal details" button label matches the current UI exactly (the change from "Reveal Details" to "Reveal details" should be confirmed).

Files Reviewed

• docs/articles/new-expensify/expensify-card/Cardholder-Settings-and-Features.md (+52/-14) -- Two new procedural sections, one new FAQ entry, heading capitalization normalization, URL conversion to relative paths, removal of Classic cross-link, minor capitalization fixes. Overall a solid improvement with the caveats noted above.

Note: This review is based solely on the proposed diff, not on unchanged portions of the file.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://91147522.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/expensify-card/Cardholder-Settings-and-Features

[github-actions]

AI Readiness violation -- title does not reflect article scope: The new title "Update Your Expensify Card Details" suggests the article is only about updating card details, but this article covers much more: activation, Smart Limits, notifications, managing expenses, virtual cards, digital wallets, and troubleshooting. A title that is too narrow will cause AI systems and search to miss relevant content. Consider a title that captures the full scope, such as:

Suggested change

	title: Update Your Expensify Card Details
	title: Expensify Cardholder Settings and Features

Alternatively, if the intent is to narrow the article strictly to "updating details," the unrelated sections (Smart Limits, notifications, virtual cards, digital wallet, etc.) should be moved to separate articles.

[github-actions]

Readability / Style consistency violation: The "How to" prefix is unnecessary filler. Other H1 headings in this same article use a direct imperative verb style ("Activate Your Expensify Card", "Enable Notifications", "Manage Your Card Expenses"). This heading should follow the same pattern for consistency and scannability.

Suggested change

	# How to Update the Name on Your Expensify Card
	# Update the Name on Your Expensify Card

[github-actions]

Readability / Style consistency violation: Same "How to" prefix issue as the previous heading. Use a direct imperative verb form to match the other headings in this article.

Suggested change

	# How to Update the Phone Number Linked to Your Expensify Card
	# Update the Phone Number Linked to Your Expensify Card

[github-actions]

Readability violation -- repetitive phrasing: This sentence repeats "legal name," "profile," and "update" in close succession, making it feel redundant. Consider tightening it:

Suggested change

	The name embossed on your physical Expensify Card is pulled from the legal name in your profile. To update the name associated with your Expensify Card, update your legal name in your profile settings.
	The name on your physical Expensify Card comes from the legal name in your profile. To change it, update your legal name by following these steps:

[github-actions]

Expensify Style violation -- button label: Per Expensify style guidelines, the final action in a flow should use "Confirm" rather than "Save." If the UI button actually reads "Save," disregard this comment -- but please verify the button label matches what is shown in the app.

Suggested change

	5. Click **Save**.
	5. Click **Confirm**.

[github-actions]

Expensify Style violation -- button label: Same as the name update section -- "Save" should be "Confirm" at the end of a flow, unless the UI literally displays "Save." Please verify the actual button text.

Suggested change

	4. Enter your updated phone number and click **Save**.
	4. Enter your updated phone number and click **Confirm**.

[github-actions]

Readability violation -- verbose language: "you will need to request a replacement card" uses unnecessary filler ("you will need to"). Simplify for directness:

Suggested change

	Your updated name will be associated with your Expensify Card. To receive a new physical card with the updated name, you will need to request a replacement card. See the FAQ below for details.
	Your updated name will be associated with your Expensify Card. To get a new physical card with the updated name, request a replacement card. See the FAQ below for details.

[github-actions]

Readability violation -- redundant "Then" in numbered step: Numbered steps already convey sequence, so starting with "Then" is unnecessary filler. Remove it for cleaner instructions:

Suggested change

	2. Then request a replacement card by going to **Account > Wallet**, selecting your physical card, and clicking **Report card lost or damaged**.
	2. Request a replacement card by going to **Account > Wallet**, selecting your physical card, and clicking **Report card lost or damaged**.

[MelvinBot]

Closing this PR — it modified the wrong article. A new PR will be opened targeting the correct file.