[No QA] Docs updates for E/A#91463 Update copilot button label in help article

[MelvinBot]

Summary

• Updates the Copilot-Access help article to reflect the new button label Add a copilot (changed from Add Copilot) to match the UI update in Update addCopilot copy #91463.

Test plan

• Verify the help article at docs/articles/new-expensify/settings/Copilot-Access.md references the correct button label Add a copilot in both step 2 and step 5.

---

@jamesdeanexpensify, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

[OSBotify]

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

Updated articles:

• articles/new-expensify/settings/Copilot-Access

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a focused, two-line change to the Copilot Access help article, updating the button label from Add Copilot to Add a copilot in steps 2 and 5 of the "Add a Copilot" section. The change aligns the documentation with the UI update introduced in PR #91463. This is exactly the kind of maintenance that keeps help content accurate.

Scores Summary

• Readability: 9/10 - The changed lines are clear, action-oriented, and fit naturally within the existing step sequence. No issues with the proposed text.
• AI Readiness: 8/10 - The updated button labels use the exact UI terminology, which supports accurate semantic retrieval. No metadata changes were needed for this label-only update. One minor note: the internalScope field is absent from this article's YAML frontmatter, but that is a pre-existing gap outside the scope of this diff.
• Style Compliance: 10/10 - The changes follow naming conventions precisely: the button name is bolded, matches the new UI label exactly (sentence case, no quotation marks), and no synonyms or paraphrases are introduced. This is textbook compliance with HELPSITE_NAMING_CONVENTIONS.md.

Key Findings

• The two updated lines correctly reflect the new button label Add a copilot with proper bold formatting and exact UI casing.
• The change is minimal and surgical, which is appropriate for a UI label update.
• No governance violations are introduced by this diff.

Recommendations

• No changes are required for this diff to merge.
• (Optional, out of scope) The existing article has several pre-existing governance gaps (multiple # headings, missing internalScope in YAML, non-task-based headings, three-dot menu reference using "three-dot menu" instead of the required "three dots (vertical ellipsis)" format). These are worth addressing in a future cleanup PR but are not introduced by this change.

Files Reviewed

• docs/articles/new-expensify/settings/Copilot-Access.md — Two button label updates from "Add Copilot" to "Add a copilot" in steps 2 and 5. Changes are accurate and compliant.

Note: No inline comments were posted as the diff contains no issues requiring line-level feedback.

[melvin-bot]

@stephanieelliott looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a small but important terminology correction in the Copilot Access article, updating the button label from "Add Copilot" to "Add a copilot" in two places (steps 2 and 5 of the "Add a Copilot" section). This aligns the documentation with the actual UI text, which is the core requirement of HelpDot naming conventions.

Scores Summary

• Readability: 9/10 - The changed lines are clear, action-oriented, and fit naturally within the existing step sequence. No issues with flow or scannability.
• AI Readiness: 8/10 - The changes themselves are fine. The broader article has pre-existing issues outside the scope of this diff (e.g., missing internalScope in YAML frontmatter, multiple # headings beyond the title and FAQ), but those are not introduced by this PR.
• Style Compliance: 10/10 - The change directly improves style compliance by correcting button labels to match the exact UI text. Bold formatting is correctly applied. This is exactly the kind of fix the naming conventions document calls for.

Key Findings

• The button label correction from Add Copilot to Add a copilot is the right fix. The governance rules require using "the exact text shown in the product UI" with matching capitalization.
• Both occurrences in the workflow (step 2 and step 5) are updated consistently, which is good.
• No new issues are introduced by this change.

Recommendations

• No changes needed for this PR -- it is a clean, targeted terminology fix.
• For a future PR, the article would benefit from addressing pre-existing issues: adding internalScope to the YAML frontmatter, consolidating multiple # headings to ## (per the one-#-title rule), making section headings task-based (e.g., "# Add a Copilot" could become "## How to add a Copilot"), and updating the three-dot menu references to use the required format ("the three dots (⋮)" instead of "three-dot menu").

Files Reviewed

• docs/articles/new-expensify/settings/Copilot-Access.md - Two button label corrections. Clean and correct.

This review assessed only the proposed changes in the diff, not pre-existing content.

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.84-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.86-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	cancelled 🔪

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.88-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.88-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌