[No QA] Docs updates for E/A#94433 update login page URL to root

[MelvinBot]

Docs update for #94433

#94433 changed the logged-out sign-in page URL on web from /Home to the root / (a legacy /Home → / redirect is kept for cached paths).

The help site referenced the login page as https://new.expensify.com/Home, which is no longer the canonical URL. This PR updates that link to https://new.expensify.com/ to match current behavior.

Change

• docs/articles/new-expensify/settings/Account-Settings.md — updated the login page link from https://new.expensify.com/Home to https://new.expensify.com/ (also fixed a duplicate "from from" typo on the same line).

Related

• Source PR: Logged-out sign-in page URL shows /Home instead of root  #94433
• Fixed issue: [Due for payment 2026-07-13] [$250] [Web] Logged-out sign-in page URL shows /Home instead of root #94450

---

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR is a minimal, well-scoped maintenance change to docs/articles/new-expensify/settings/Account-Settings.md. It updates the login page link from https://new.expensify.com/Home to the new canonical root URL https://new.expensify.com/ (mirroring app change E/A#94433) and fixes a duplicate word ("from from") on the same line. The change is accurate, on-topic, and improves correctness.

Scores Summary

• Readability: 10/10 - Removing the duplicate "from from" fixes a grammatical error and makes the sentence read cleanly. The instruction remains clear and scannable.
• AI Readiness: 9/10 - The edited line sits under a properly task-based ## How to enable high contrast mode heading and uses the exact UI label Enable high contrast. No metadata or heading structure was touched, and none of the AI-retrieval rules are impacted by this diff.
• Style Compliance: 9/10 - The bold UI label Enable high contrast matches the naming conventions, and the descriptive anchor text "login page" avoids vague anchors like "click here". The full URL is appropriate here because this is an external product entry point (the login page), not an internal cross-link between help articles, so the relative-link rule does not apply.

Key Findings

• The URL correction is accurate and aligns the docs with the actual app behavior (root / is now canonical; /Home redirect is legacy).
• The "from from" typo fix is a genuine readability improvement.
• The surrounding section already complies with governance (single # title, task-based ## headings, exact bold UI labels), and this diff does not regress any of that.
• No structural, metadata, or heading changes were introduced, so no new compliance risks.

Recommendations

• No changes required. The PR is correct and ready as-is.
• Optional: consider adding an anchor text that reflects a fuller search phrase (for example, "Expensify login page"), though "login page" is acceptable.

Files Reviewed

• docs/articles/new-expensify/settings/Account-Settings.md - Approved. One line changed: URL updated to root and duplicate word removed. No issues.

Note: This change is a single line, so no separate inline comments were necessary.

[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 @jliexpensify

[melvin-bot]

@jliexpensify 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]

[jliexpensify]

LGTM

[OSBotify]

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

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

[OSBotify]

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.4.41-4 🚀

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

Bundle Size Analysis (Sentry):

• Android