[$250] Help - Unexpected visible <div> tag displayed at end of help article content

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.62-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #86995
Email or phone of affected tester (no customers): jsat@applausemail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: All platforms
App Component: Other

Action Performed:

1. Launch Expensify App
2. Log in with valid credentials
3. Navigate to the help site article for "How to Pay Expenses in New Expensify"
4. Scroll to the FAQ entry about paying reports with only non-reimbursable expenses

Expected Result:

The help article displays correctly, without any visible HTML tags. No

tag should be visible to the user

Actual Result:

A

tag is visible at the end of the article content, making raw HTML appear to the user.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @brunovjk

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022049603041898279121
• Upwork Job ID: 2049603041898279121
• Last Price Increase: 2026-04-29

[MelvinBot]

Proposal

What is the root cause of that problem?

There is a stray </div> HTML tag on line 88 of Pay-Expenses.md. It has no matching opening <div> tag — it's simply leftover HTML that was accidentally left in the markdown source.

The help site renderer passes this through as raw visible text to the user.

What changes do you think we should make in order to solve the problem?

Remove the stray </div> tag on line 88 of docs/articles/new-expensify/wallet-and-payments/Pay-Expenses.md.

What alternative solutions did you explore? (Optional)

N/A — this is a single-character content fix. No alternative approach is needed.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022049603041898279121