Skip to content

Conversation

@ahmed-abdulhuy
Copy link

@ahmed-abdulhuy ahmed-abdulhuy commented Oct 28, 2025

Fix Typo in trychroma.com guide

@github-actions
Copy link

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@propel-code-bot
Copy link
Contributor

propel-code-bot bot commented Oct 28, 2025

Docs: Correct grammatical article from "a SQL" to "an SQL" across documentation

This PR is a documentation-only cleanup that standardizes the phrasing "an SQL database" everywhere in the public docs, Markdoc source, generated text assets, and sample-data JSON. No application logic, APIs, or build tooling are modified. The change improves grammatical accuracy and professionalism without altering any technical content or behavior.

Key Changes

• Replaced all occurrences of "a SQL database" with "an SQL database" in Markdoc sources
• Regenerated public site assets to reflect the corrected wording
• Updated sample-data JSON containing embedded documentation text

Affected Areas

• docs/architecture/.md
• docs/troubleshooting/
.md
• site/public/**/* (generated HTML/MD)
• sample-data/*.json

This summary was automatically generated by @propel-code-bot

@ahmed-abdulhuy ahmed-abdulhuy changed the title Fix Documentation Typo DOC: Fix Documentation Typo Oct 28, 2025

This error happens when the HNSW index fails to retrieve the requested number of results for a query, given its structure and your data. he way to resolve this is to either decrease the number of results you request from a query (n_result), or increase the HNSW parameters `M`, `ef_construction`, and `ef_search`. You can read more about HNSW configurations [here](/docs/collections/configure).
This error happens when the HNSW index fails to retrieve the requested number of results for a query, given its structure and your data. The way to resolve this is to either decrease the number of results you request from a query (n_result), or increase the HNSW parameters `M`, `ef_construction`, and `ef_search`. You can read more about HNSW configurations [here](/docs/collections/configure).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Documentation]

Parameter name appears incorrect: use n_results (plural) instead of n_result.

Note: The ChromaDB query API consistently uses n_results (plural) across all implementations. This parameter specifies the number of nearest neighbors to return for each query, with a default value of 10.

Context for Agents
[**Documentation**]

Parameter name appears incorrect: use `n_results` (plural) instead of `n_result`.

Note: The ChromaDB query API consistently uses `n_results` (plural) across all implementations. This parameter specifies the number of nearest neighbors to return for each query, with a default value of 10.

File: docs/docs.trychroma.com/markdoc/content/docs/overview/troubleshooting.md
Line: 30

## Cannot return the results in a contiguous 2D array. Probably ef or M is too small

This error happens when the HNSW index fails to retrieve the requested number of results for a query, given its structure and your data. he way to resolve this is to either decrease the number of results you request from a query (n_result), or increase the HNSW parameters `M`, `ef_construction`, and `ef_search`. You can read more about HNSW configurations [here](/docs/collections/configure).
This error happens when the HNSW index fails to retrieve the requested number of results for a query, given its structure and your data. The way to resolve this is to either decrease the number of results you request from a query (n_result), or increase the HNSW parameters `M`, `ef_construction`, and `ef_search`. You can read more about HNSW configurations [here](/docs/collections/configure).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Documentation]

Parameter name appears incorrect: use n_results (plural) instead of n_result.

Note: The ChromaDB query API consistently uses n_results (plural) across all implementations. This parameter specifies the number of nearest neighbors to return for each query, with a default value of 10.

Context for Agents
[**Documentation**]

Parameter name appears incorrect: use `n_results` (plural) instead of `n_result`.

Note: The ChromaDB query API consistently uses `n_results` (plural) across all implementations. This parameter specifies the number of nearest neighbors to return for each query, with a default value of 10.

File: docs/docs.trychroma.com/public/llms-docs-overview-troubleshooting.txt
Line: 24


This error happens when the HNSW index fails to retrieve the requested number of results for a query, given its structure and your data. he way to resolve this is to either decrease the number of results you request from a query (n_result), or increase the HNSW parameters `M`, `ef_construction`, and `ef_search`. You can read more about HNSW configurations [here](/docs/collections/configure).
This error happens when the HNSW index fails to retrieve the requested number of results for a query, given its structure and your data. The way to resolve this is to either decrease the number of results you request from a query (n_result), or increase the HNSW parameters `M`, `ef_construction`, and `ef_search`. You can read more about HNSW configurations [here](/docs/collections/configure).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Documentation]

Parameter name appears incorrect: use n_results (plural) instead of n_result.

Note: The ChromaDB query API consistently uses n_results (plural) across all implementations. This parameter specifies the number of nearest neighbors to return for each query, with a default value of 10.

Context for Agents
[**Documentation**]

Parameter name appears incorrect: use `n_results` (plural) instead of `n_result`.

Note: The ChromaDB query API consistently uses `n_results` (plural) across all implementations. This parameter specifies the number of nearest neighbors to return for each query, with a default value of 10.

File: docs/docs.trychroma.com/public/llms-full.text
Line: 3045

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant