langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-21 11:55:23 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #4041] [MERGED] docs: fix ambiguous wording in Chroma integration docs #4046

New Issue
Closed
opened 2026-06-05 18:54:00 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:54:00 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/4041
Author: @karan-singhh
Created: 5/18/2026
Status: ✅ Merged
Merged: 5/19/2026
Merged by: @mdrxy

Base: main ← Head: patch-1

📝 Commits (1)

  • 80f891a docs: fix ambiguous wording in Chroma integration docs

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 src/oss/python/integrations/vectorstores/chroma.mdx (+1 -1)

📄 Description

This updates the explanatory text in the Chroma integration docs to clarify that the example first sets up the embedding function and then configures local persistence in subsequent steps.

The previous wording could be interpreted as if the immediately shown code snippet handled both steps.

Overview

Clarifies ambiguous wording in the Chroma integration documentation to better reflect the sequence of the example setup.

Type of change

Type: Update existing documentation

Related issues/PRs

  • GitHub issue: None
  • Feature PR: None
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines, including the language policy
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed

(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow

Additional notes

This is a small documentation clarity improvement made via GitHub web edit for an existing docs page. No code examples or navigation structure were modified.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/4041 **Author:** [@karan-singhh](https://github.com/karan-singhh) **Created:** 5/18/2026 **Status:** ✅ Merged **Merged:** 5/19/2026 **Merged by:** [@mdrxy](https://github.com/mdrxy) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`80f891a`](https://github.com/langchain-ai/docs/commit/80f891a1aa4a34e3913772d1ff32c1b6f9a76c97) docs: fix ambiguous wording in Chroma integration docs ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/python/integrations/vectorstores/chroma.mdx` (+1 -1) </details> ### 📄 Description This updates the explanatory text in the Chroma integration docs to clarify that the example first sets up the embedding function and then configures local persistence in subsequent steps. The previous wording could be interpreted as if the immediately shown code snippet handled both steps. ## Overview Clarifies ambiguous wording in the Chroma integration documentation to better reflect the sequence of the example setup. ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: None - Feature PR: None <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md), including the [language policy](https://docs.langchain.com/oss/python/contributing/overview#language-policy) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed (Internal team members only / optional): Create a preview deployment as necessary using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> This is a small documentation clarity improvement made via GitHub web edit for an existing docs page. No code examples or navigation structure were modified. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:54:00 -04:00
yindo closed this issue 2026-06-05 18:54:00 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#4046
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?