[No QA] Fix broken image on Update Expensify-Home-Overview.md

[stephanieelliott]

Fixed image that was not rendering

[OSBotify]

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

Updated articles:

• articles/new-expensify/getting-started/Expensify-Home-Overview

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR is a straightforward bug fix that corrects a broken image reference. The filename in the Markdown image tag was home-2.png but the actual asset file is home2.png (without the hyphen). The change is a single-character deletion that restores the image render. No content, structure, or metadata was altered.

Scores Summary

• Readability: 10/10 - The change corrects a broken image, which directly improves readability by ensuring the visual aid renders as intended. No text content was modified.
• AI Readiness: 10/10 - No impact on metadata, headings, or retrieval optimization. The existing YAML frontmatter (title, description, keywords, internalScope) remains intact and well-formed.
• Style Compliance: 10/10 - The fix does not introduce or modify any UI references, terminology, or navigation instructions. The image alt text (Home > For You on New Expensify) correctly uses the exact UI section name with proper capitalization.

Key Findings

• The fix is correct and narrowly scoped: home-2.png changed to home2.png to match the actual asset filename.
• The image alt text appropriately describes the screenshot content.
• No governance violations are introduced by this change.

Recommendations

• No actions needed. This is a clean, minimal fix.

Files Reviewed

• docs/articles/new-expensify/getting-started/Expensify-Home-Overview.md -- Image path corrected from home-2.png to home2.png. No other changes.

[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.3.42-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS