[BUG](api): fix grammar errors in validation error messages in types.py

[rtmalikian]

Problem

Several validation error messages in chromadb/api/types.py contain grammar errors:

1. Line 1238: "an list" → "a list" (in validate_where $in/$nin error)
2. Line 1356: "a int" → "an int" (in validate_n_results error)
3. Line 1269: "those type" → "those types" (in validate_where operand error)

Affected Files

• chromadb/api/types.py — error message strings only, no logic changes

Proposed Fix

Fix the three grammar errors in the error message strings.

[smqd19]

Spelling and grammar in error messages might seem minor but they really improve the developer experience, especially when debugging complex validation issues. I’ve worked on APIs where clear error text reduced support tickets significantly. Since these messages come from validation functions, it’s good to keep them concise and consistent.

One potential improvement beyond just fixing grammar could be to standardize error message formatting using a helper function or even integrating i18n tooling if multi-language support is planned in the future. For now, correcting those three errors as you suggested is spot on. Also, running flake8 or pylint with a plugin like flake8-spellcheck can catch these types of typos automatically in the CI pipeline, saving time down the road.