docs(linter/no-console): correct typo in correct code example

[camc314]

closes oxc-project/oxc-project.github.io#457

[camc314]

• docs(linter/no-console): correct typo in correct code example #13182 👈 (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.

[Copilot]

Pull Request Overview

This PR corrects a documentation typo in the no-console linter rule where an example labeled as "incorrect" should have been labeled as "correct". The change fixes misleading documentation that could confuse users about what code is acceptable.

• Fixes documentation labeling in the no-console linter rule

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[camc314]

Merge activity

• Aug 18, 11:34 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 18, 11:38 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Aug 18, 11:42 AM UTC: Merged by the Graphite merge queue.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #13182 will not alter performance

_{Comparing c/08-18-docs_linter_no-console_correct_typo_in_correct_code_example (deddc8c) with main (3548cf4)¹}

Summary

✅ 34 untouched benchmarks

Footnotes

1. No successful run was found on main (deddc8c) during the generation of this report, so 3548cf4 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩