refactor(semantic): fix typo in comment

[overlookmotel]

Follow-on after #12676. Fix a typo I introduced in that PR.

[overlookmotel]

• refactor(semantic): fix typo in comment #12714 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[overlookmotel]

Merge activity

• Aug 1, 10:12 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Aug 1, 10:19 AM UTC: overlookmotel added this pull request to the Graphite merge queue.
• Aug 1, 10:31 AM UTC: Merged by the Graphite merge queue.

[Boshen]

Why is this not done by AI?

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #12714 will not alter performance

_{Comparing 08-01-refactor_semantic_fix_typo_in_comment (090cf88) with main (737003e)}

Summary

✅ 34 untouched benchmarks

[overlookmotel]

Why is this not done by AI?

Not sure. Usually PR review bot catches these kinds of grammatical errors. Don't know why it didn't in this case.