feat(classification): fixed typo

[vitali-usik]

Summary

Typo fix for preview restriction controls. Follow-up fix to #4678

Summary by CodeRabbit

• Style
  • Updated security-control messages to use clearer, more consistent wording (“Only selected …” instead of “Only select …”).
  • Kept the same message content structure, including application-name and remaining-count details.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8631072e-b31e-4832-abea-78703359c06b

📥 Commits

Reviewing files that changed from the base of the PR and between b85ec1e and 0f7dd4d.

⛔ Files ignored due to path filters (1)

• i18n/en-US.properties is excluded by !i18n/**

📒 Files selected for processing (1)

• src/features/classification/security-controls/messages.js

🚧 Files skipped from review as they are similar to previous changes (1)

• src/features/classification/security-controls/messages.js

---

Walkthrough

Two security-control message strings now use “Only selected applications can read” while retaining their existing placeholders, descriptions, and IDs.

Changes

Security control messages

Layer / File(s)	Summary
Update whitelist message wording src/features/classification/security-controls/messages.js	Updates the standard and overflow whitelist messages from “select” to “selected”.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A bunny edits words with care,
“Selected” now blooms everywhere.
Placeholders stay in their place,
IDs keep their familiar face.
Hop, hop—cleaner messages there!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: a typo fix in classification preview restriction messaging.
Description check	✅ Passed	The description includes a summary and the follow-up context required by the template, and is not missing any critical information.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-20 08:05 UTC · Rule: Automatic strict merge · triggered by rule Automatic merge queue
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-07-20 08:05 UTC · at 0f7dd4d19699e0958b10c8176d8fb348b68c52bc · squash

This pull request spent 13 seconds in the queue, including 2 seconds running CI.

Required conditions to merge

• github-review-approved [🛡 GitHub branch protection] (documentation)
  • feat(classification): fixed typo #4699
• github-review-decision = APPROVED [🛡 GitHub branch protection] (documentation)
  • feat(classification): fixed typo #4699
• any of [🛡 GitHub branch protection]:
  • check-success = Summary
  • check-neutral = Summary
  • check-skipped = Summary
• any of [🛡 GitHub branch protection]:
  • check-success = lint_test_build
  • check-neutral = lint_test_build
  • check-skipped = lint_test_build
• any of [🛡 GitHub branch protection]:
  • check-success = license/cla
  • check-neutral = license/cla
  • check-skipped = license/cla
• any of [🛡 GitHub branch protection]:
  • check-success = lint_pull_request
  • check-neutral = lint_pull_request
  • check-skipped = lint_pull_request