[Due for payment 2026-06-02] Device management - No period after Learn more link

[applause-bot]

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.80-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91323
Email or phone of affected tester (no customers): isjdosdjoijosdjosnj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: User Settings

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Account > Copilot.
   → There is a period after Learn more link.
3. Go to Account > Security.
4. Click Device management.

Expected Result:

There will be a period after Learn more link.

Actual Result:

There is no period after Learn more link.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7161013_1779491926146.3.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7161013

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/51678879314b3b784ef6a7a98c15f053d63dc89a442ee13ce59005a3d6d95b48

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #91323

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

Proposal

What is the root cause of that problem?

The Device Management page description string in en.ts:2294 ends with </a> but has no trailing period. The Copilot page avoids this because it renders the period as a separate JSX node after its <TextLink>, but the Device Management page uses RenderHTML with the translation string directly, so the period must be in the string itself.

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

Add a period (.) after the closing </a> tag in the deviceManagementPage.description string in both en.ts:2294 and es.ts:2108.

---

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.

[mountiny]

We dont have to block on this