[No QA] Update Uber.md

[stephanieelliott]

https://expensify.slack.com/archives/C02QSAC6BJ8/p1761328498436759

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

[melvin-bot]

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes focused improvements to the Uber integration documentation by adding critical clarifications about platform requirements and scope limitations. The changes enhance user understanding and prevent potential confusion.

Scores Summary

• Readability: 8/10 - Clear, well-structured content with good flow and appropriate detail level
• AI Readiness: 9/10 - Excellent heading structure, proper context, and clear feature descriptions
• Style Compliance: 8/10 - Follows Expensify voice standards with consistent formatting and terminology

Key Findings

Strengths:

• Critical platform clarification: The prominent note about mobile app requirement prevents user frustration
• Enhanced heading specificity: "Where to find and connect Uber to Expensify Classic" provides better context than generic "Connect Uber to Expensify"
• Improved step clarity: Adding "Open the Uber mobile app" and "In the Uber mobile app" makes instructions more explicit
• Valuable scope limitation: New FAQ clearly explains Business vs Personal profile behavior
• Consistent terminology: Proper use of "Expensify Classic" and UI element formatting

Areas for improvement:

• Minor inconsistency in action verbs ("click" vs "tap" - should be "tap" throughout for mobile)
• The prominent note could be better integrated into the flow rather than standalone

Recommendations

1. Consider standardizing to "tap" throughout the mobile instructions for consistency
2. The changes are ready for approval - they significantly improve user experience without introducing any critical issues
3. Future consideration: The platform limitation note could potentially be integrated more naturally into the introduction

Files Reviewed

• docs/articles/expensify-classic/connections/Uber.md - Approved with minor suggestions - Meaningful improvements to clarity and user guidance

Overall Score: 8.5/10 - These changes represent a solid improvement to the documentation that will genuinely help users avoid confusion and successfully complete the integration process.

[OSBotify]

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

Updated articles:

• articles/expensify-classic/connections/Uber

[zanyrenney]

LGTM. The "GH actions" still seem to be buggy though.

It says "Terminology violation: Use "tap" consistently instead of "click" for mobile app interactions. Since this is in the Uber mobile app, "tap" is more accurate." But it already said "tap".

[melvin-bot]

@zanyrenney 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.

[zanyrenney]

When I clicked merge there were no tests not passing but I am looking into it.

[OSBotify]

🚀 Deployed to staging by https://github.com/zanyrenney in version: 9.2.39-0 🚀

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

[stephanieelliott]

@zanyrenney we have GH open with a running list of QA bot bugs that need to be fixed, added this to it here: #72810 (comment)

[OSBotify]

🚀 Deployed to production by https://github.com/puneetlath in version: 9.2.39-3 🚀

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