langchain/docs
Ran c3f8733aef
fix: correct spelling mistakes of "seperate, intialise, pre-defined" (#14647)
fix spellings

**seperate -> separate**: found more occurrences, see
https://github.com/langchain-ai/langchain/pull/14602
**initialise -> intialize**: the latter is more common in the repo
**pre-defined > predefined**: adding a comma after a prefix is a
delicate matter, but this is a generally accepted word

also, another word that appears in the repo is "fs" (stands for
filesystem), e.g., in `libs/core/langchain_core/prompts/loading.py`
` """Unified method for loading a prompt from LangChainHub or local
fs."""`
Isn't "filesystem" better?
2023-12-22 11:49:35 -08:00
..
api_reference infra: cut down on integration steps (#14785) 2023-12-17 12:55:59 -08:00
docs fix: correct spelling mistakes of "seperate, intialise, pre-defined" (#14647) 2023-12-22 11:49:35 -08:00
scripts docs[patch], templates[patch]: Import from core (#14575) 2023-12-11 16:49:10 -08:00
src docs[patch]: fix zoom (#14786) 2023-12-15 17:46:12 -08:00
static docs: update langchain diagram (#14619) 2023-12-12 16:36:15 -08:00
.local_build.sh docs: developer docs (#14776) 2023-12-17 12:55:49 -08:00
babel.config.js Restructure docs (#11620) 2023-10-10 12:55:19 -07:00
code-block-loader.js Restructure docs (#11620) 2023-10-10 12:55:19 -07:00
docusaurus.config.js docs: fix api ref link (#14679) 2023-12-13 13:42:01 -08:00
package-lock.json docs[patch]: search experiment (#14254) 2023-12-04 16:58:26 -08:00
package.json docs[patch]: search experiment (#14254) 2023-12-04 16:58:26 -08:00
README.md docs: developer docs (#14776) 2023-12-17 12:55:49 -08:00
settings.ini Restructure docs (#11620) 2023-10-10 12:55:19 -07:00
sidebars.js docs: developer docs (#14776) 2023-12-17 12:55:49 -08:00
vercel_build.sh docs: developer docs (#14776) 2023-12-17 12:55:49 -08:00
vercel_requirements.txt infra: docs build install community editable (#14739) 2023-12-14 16:13:09 -08:00
vercel.json docs: alibaba cloud (#14772) 2023-12-20 12:32:33 -08:00

LangChain Documentation

For more information on contributing to our documentation, see the Documentation Contributing Guide