[No QA] Docs updates for E/A#90936 Update wallet Cards section label in help docs

[MelvinBot]

Summary

• Updates help site articles to reflect the Wallet section header rename from Assigned cards to Cards (per Update wallet Assigned Cards copy #90936)
• Affected articles:
  • Connect-Personal-Cards.md — updated 2 references
  • Manage-Personal-Cards.md — updated 4 references (including keywords)
  • Import-Personal-Card-Transactions-From-a-Spreadsheet.md — updated 1 reference

Test plan

• Verify all references to the Wallet section now say Cards instead of Assigned cards
• Confirm the updated articles render correctly on the help site

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR is a straightforward UI terminology update across three help articles, renaming Assigned cards to Cards to match a Wallet section header change (per #90936). The changes are minimal, consistent, and correctly applied across all affected references including body text, step instructions, and YAML keywords.

Scores Summary

• Readability: 9/10 - All changes maintain clear, scannable step formatting. One pre-existing issue in Import-Personal-Card-Transactions-From-a-Spreadsheet.md has duplicate step numbering (steps 3 and 3, then 5), but this is not introduced by the PR.
• AI Readiness: 9/10 - Keywords in Manage-Personal-Cards.md were correctly updated from "assigned cards" to "cards" to match the new UI label, preserving search accuracy. YAML metadata including internalScope is present and appropriate in the affected file.
• Style Compliance: 10/10 - The changes correctly follow naming conventions: the new label Cards is bolded, uses exact UI terminology, and matches the product change. No prohibited language introduced.

Key Findings

• All seven references to "Assigned cards" have been consistently updated to "Cards" across three files.
• The keyword array in Manage-Personal-Cards.md was also updated, which is good practice for maintaining AI retrieval accuracy.
• Pre-existing issue (not introduced by this PR): Import-Personal-Card-Transactions-From-a-Spreadsheet.md has a duplicate step 3 (lines with different leading whitespace) and skips step 4. This should be addressed in a separate PR.

Recommendations

• Consider filing a follow-up to fix the duplicate step numbering in Import-Personal-Card-Transactions-From-a-Spreadsheet.md.
• No blocking issues with the proposed changes.

Files Reviewed

• docs/articles/new-expensify/connect-credit-cards/Connect-Personal-Cards.md -- 2 references updated, clean
• docs/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet.md -- 1 reference updated, clean (pre-existing step numbering issue noted)
• docs/articles/new-expensify/connect-credit-cards/Manage-Personal-Cards.md -- 4 references updated (including keywords), clean

This is a low-risk terminology alignment PR. No inline comments needed -- all changes are correct and consistent.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR is a focused terminology update, renaming Assigned cards to Cards across three help articles to match a UI change (per #90936). The changes are minimal, consistent, and correctly applied -- including updating the keywords metadata in Manage-Personal-Cards.md.

Scores Summary

• Readability: 9/10 - All changes are clear, concise, and maintain the existing step-by-step structure. No new awkward phrasing introduced.
• AI Readiness: 9/10 - Keywords metadata was properly updated to replace "assigned cards" with "cards" in Manage-Personal-Cards.md. YAML frontmatter (title, description, keywords, internalScope) remains intact across all files.
• Style Compliance: 10/10 - The rename aligns with the core UI referencing rule: "Use the exact text shown in the product UI." Bold formatting is correctly applied to the new Cards label. No prohibited language or naming convention violations.

Key Findings

• All seven references to "Assigned cards" / "Assigned Cards" have been correctly updated to "Cards" across the three affected files.
• The keyword array in Manage-Personal-Cards.md was also updated, which is good attention to detail for search and retrieval.
• One pre-existing issue noticed (not introduced by this PR): Import-Personal-Card-Transactions-From-a-Spreadsheet.md has a duplicate step 3 (lines with different leading whitespace) and misnumbered step 5. This is out of scope for this review but worth noting for a follow-up fix.

Recommendations

• No blocking changes needed for this PR -- the terminology updates are correct and complete.
• Consider a follow-up PR to fix the pre-existing duplicate step numbering in Import-Personal-Card-Transactions-From-a-Spreadsheet.md.

Files Reviewed

• Connect-Personal-Cards.md -- 2 references updated; clean.
• Import-Personal-Card-Transactions-From-a-Spreadsheet.md -- 1 reference updated; clean (pre-existing step numbering issue noted).
• Manage-Personal-Cards.md -- 4 references updated (including keywords metadata); clean.

[OSBotify]

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

Updated articles:

• articles/new-expensify/connect-credit-cards/Connect-Personal-Cards
• articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet
• articles/new-expensify/connect-credit-cards/Manage-Personal-Cards

[melvin-bot]

Concierge reviewer checklist:

• I have verified the accuracy of the article
  • The article is within a hub that makes sense, and the navigation is correct
  • All processes, screenshots, and examples align with current product behavior.
  • All links within the doc have been verified for correct destination and functionality.
• I have verified the readability of the article
  • The article's language is clear, concise, and free of jargon.
  • The grammar, spelling, and punctuation are correct.
  • The article contains at least one image, or that an image is not necessary
• I have verified the formatting of the article
  • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • The article has proper text spacing and breaks for readability.
• I have verified the article has the appropriate tone and style
  • The article's tone is professional, friendly, and suitable for the target audience.
  • The article's tone, terminology, and voice are consistent throughout.
• I have verified the overall quality of the article
  • The article is not missing any information, nor does it contain redundant information.
  • The article fully addresses user needs.
• I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @greg-schroeder

[melvin-bot]

@greg-schroeder Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]