Skip to content

Commit

Permalink
docs: Fix concepts docs hash param (#6816)
Browse files Browse the repository at this point in the history
  • Loading branch information
jacoblee93 committed Sep 16, 2024
1 parent e5cd584 commit ee33e9f
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/core_docs/docs/how_to/output_parser_structured.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@
"id": "75976cd6-78e2-458b-821f-3ddf3683466b",
"metadata": {},
"source": [
"Output parsers implement the [Runnable interface](/docs/how_to/#langchain-expression-language-lcel), the basic building block of the [LangChain Expression Language (LCEL)](/docs/how_to/#langchain-expression-language-lcel). This means they support `invoke`, `stream`, `batch`, `streamLog` calls.\n",
"Output parsers implement the [Runnable interface](/docs/how_to/#langchain-expression-language-lcel), the basic building block of [LangChain Expression Language (LCEL)](/docs/how_to/#langchain-expression-language-lcel). This means they support `invoke`, `stream`, `batch`, `streamLog` calls.\n",
"\n",
"## Validation\n",
"\n",
Expand Down
2 changes: 1 addition & 1 deletion docs/core_docs/docs/how_to/routing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -65,4 +65,4 @@ import BranchExample from "@examples/guides/expression_language/how_to_routing_r

You've now learned how to add routing to your composed LCEL chains.

Next, check out the other [how-to guides on runnables](/docs/how_to/#langchain-expression-language-lcel) in this section.
Next, check out the other [how-to guides on runnables](/docs/how_to/#langchain-expression-language) in this section.
2 changes: 1 addition & 1 deletion docs/core_docs/docs/how_to/streaming.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"This guide assumes familiarity with the following concepts:\n",
"\n",
"- [Chat models](/docs/concepts/#chat-models)\n",
"- [LangChain Expression Language](/docs/concepts/#langchain-expression-language-lcel)\n",
"- [LangChain Expression Language](/docs/concepts/#langchain-expression-language)\n",
"- [Output parsers](/docs/concepts/#output-parsers)\n",
"\n",
":::\n",
Expand Down
2 changes: 1 addition & 1 deletion docs/core_docs/docs/tutorials/rag.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -607,7 +607,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"We’ll use the [LCEL Runnable](/docs/how_to/#langchain-expression-language-lcel) protocol to define the chain, allowing us to - pipe together components and functions in a transparent way - automatically trace our chain in LangSmith - get streaming, async, and batched calling out of the box"
"We’ll use [LangChain Expression Language (LCEL)](/docs/how_to/#langchain-expression-language-lcel) to define the chain, allowing us to - pipe together components and functions in a transparent way - automatically trace our chain in LangSmith - get streaming, async, and batched calling out of the box"
]
},
{
Expand Down
2 changes: 1 addition & 1 deletion docs/core_docs/src/theme/NotFound.js
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ const suggestedLinks = {
alternative: ["/v0.1/docs/expression_language/streaming/"],
},
"/docs/expression_language/why/": {
canonical: "/docs/concepts/#langchain-expression-language-lcel",
canonical: "/docs/concepts/#langchain-expression-language",
alternative: ["/v0.1/docs/expression_language/why/"],
},
"/docs/get_started/": {
Expand Down

0 comments on commit ee33e9f

Please sign in to comment.