+

[erhebend-tai]

We are excited to review your PR.

So we can do the best job, please check:

• There's a descriptive title that will make sense to other developers some time from now.
• There's associated issues. All PR's should have issue(s) associated - unless a trivial self-evident change such as fixing a typo. You can use the format Fixes #nnnn in your description to cause GitHub to automatically close the issue(s) when your PR is merged.
• Your change description explains what the change does, why you chose your approach, and anything else that reviewers should know.
• You have included any necessary tests in the same PR.

[Copilot]

Pull Request Overview

This PR improves the clarity of documentation in the Fairlearn metrics module by correcting grammatical usage in the interface documentation. The change updates "which key" to "where key" for better grammatical accuracy.

• Corrected grammatical phrasing in XML documentation comment

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ericstj]

This PR is only changing internal docs. While it does correct a grammatical problem, the PR is not a good use of resources or time. Please refrain from submitting these trivial PRs.

[erhebend-tai]

I see them every day. It’s terrifying. Like a one way conga line to redacted on the same day with everyone else in grammar zombie land  Sent from Proton Mail for iOS.

…

-------- Original Message --------

On Wednesday, 11/05/25 at 14:56 Eric StJohn ***@***.***> wrote: **ericstj** left a comment (dotnet/machinelearning#7541) This PR is only changing internal docs. While it does correct a grammatical problem, the PR is not a good use of resources or time. Please refrain from submitting these trivial PRs. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>