fix(eino): update en doc link

Author: shentongmartin

content/en/docs/eino/FAQ.md

@@ -134,7 +134,7 @@ If the subgraph and parent graph have different `State` types, use `ProcessState
 
 # Q: How does `eino-ext` adapt multimodal input/output for supported models?
 
-For multimodal support, see [https://www.cloudwego.io/en/docs/eino/ecosystem_integration/chat_model](https://www.cloudwego.io/en/docs/eino/ecosystem_integration/chat_model) and the corresponding examples for each model.
+For multimodal support, see [https://www.cloudwego.io/docs/eino/ecosystem_integration/chat_model](https://www.cloudwego.io/docs/eino/ecosystem_integration/chat_model) and the corresponding examples for each model.
 
 # Q: Using `UserInputMultiContent` for multimodal input, but the model side seems to miss the data or cannot read `multicontent`
 

content/en/docs/eino/core_modules/_index.md

@@ -9,14 +9,14 @@ weight: 3
 
 Eino’s core modules include the following parts:
 
-- **Components**: [Eino: Components](/en/docs/eino/core_modules/components)
+- **Components**: [Eino: Components](/docs/eino/core_modules/components)
 
   Eino abstracts commonly used components in LLM applications, such as `ChatModel`, `Embedding`, `Retriever`. These are the building blocks for application capabilities and the atomic objects in complex orchestration.
 
-- **Chain/Graph Orchestration**: [Eino: Chain/Graph Orchestration](/en/docs/eino/core_modules/chain_and_graph_orchestration/chain_graph_introduction)
+- **Chain/Graph Orchestration**: [Eino: Chain/Graph Orchestration](/docs/eino/core_modules/chain_and_graph_orchestration/chain_graph_introduction)
 
   Multiple components are combined to implement business logic. Eino provides Chain/Graph orchestration that encapsulates the complexity inside Eino, exposing easy-to-understand interfaces for logic composition and unified cross-cutting governance.
 
-- **Flow Integration (agents)**: [Eino: Flow Integration Components](/en/docs/eino/core_modules/flow_integration_components)
+- **Flow Integration (agents)**: [Eino: Flow Integration Components](/docs/eino/core_modules/flow_integration_components)
 
   Eino wraps common LLM application patterns into simple and easy-to-use tools to greatly simplify development for general scenarios. Currently available: `ReAct Agent` and `Host Multi Agent`.

content/en/docs/eino/core_modules/chain_and_graph_orchestration/_index.md

@@ -14,7 +14,7 @@ In LLM applications, `Components` provide atomic capabilities such as:
 - `Retriever`: retrieving relevant content
 - `ToolsNode`: invoking external tools
 
-> For component details: [Eino: Components](/en/docs/eino/core_modules/components)
+> For component details: [Eino: Components](/docs/eino/core_modules/components)
 
 Beyond atomic capabilities, applications must combine and chain them according to business scenarios. This is **orchestration**.
 
@@ -37,16 +37,16 @@ Therefore, Eino offers a graph-based model (`node + edge`) where **components**
 Specifically:
 
 - Everything centers on components. Clear encapsulation yields clear responsibilities and natural reuse.
-  - See: [Eino: Components](/en/docs/eino/core_modules/components)
+  - See: [Eino: Components](/docs/eino/core_modules/components)
 - Push business complexity into component implementations; the orchestration layer maintains global clarity.
 - Provide aspect capabilities via callbacks, enabling **unified governance** at the node level.
-  - See: [Eino: Callback Manual](/en/docs/eino/core_modules/chain_and_graph_orchestration/callback_manual)
+  - See: [Eino: Callback Manual](/docs/eino/core_modules/chain_and_graph_orchestration/callback_manual)
 - Provide call options for **extensibility** during rapid iteration.
-  - See: [Eino: Call Option Capabilities](/en/docs/eino/core_modules/chain_and_graph_orchestration/call_option_capabilities)
+  - See: [Eino: Call Option Capabilities](/docs/eino/core_modules/chain_and_graph_orchestration/call_option_capabilities)
 - Reinforce **type alignment** to reduce cognitive load and leverage Go’s type safety.
-  - See: [Eino: Orchestration Design Principles](/en/docs/eino/core_modules/chain_and_graph_orchestration/orchestration_design_principles)
+  - See: [Eino: Orchestration Design Principles](/docs/eino/core_modules/chain_and_graph_orchestration/orchestration_design_principles)
 - Provide **automatic stream conversion**, removing “stream handling” from the list of orchestration complexity sources.
-  - See: [Eino: Streaming Essentials](/en/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials)
+  - See: [Eino: Streaming Essentials](/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials)
 
 Graphs are powerful and semantically complete; you can express branches, parallelism, and loops. The tradeoff is using `graph.AddXXXNode()` and `graph.AddEdge()` — powerful, but a bit verbose.
 

content/en/docs/eino/core_modules/chain_and_graph_orchestration/callback_manual.md

@@ -189,11 +189,11 @@ func (cm *ChatModel) Stream(ctx context.Context, in []*schema.Message, opts ...f
 
 When a Component is orchestrated into a Graph Node, and the Component does not implement callbacks, the Node injects callback trigger points matching the Component’s streaming paradigm. For example, a ChatModelNode triggers OnStart/OnEnd around `Generate`, and OnStart/OnEndWithStreamOutput around `Stream`. Which timing is triggered depends on both Graph’s execution mode (Invoke/Stream/Collect/Transform) and the Component’s streaming support.
 
-See [Streaming Essentials](/en/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
+See [Streaming Essentials](/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
 
 ### Graph-level Callbacks
 
-Graph triggers callbacks at its own start/end/error timings. If Graph is called via `Invoke`, it triggers `OnStart/OnEnd/OnError`. If called via `Stream/Collect/Transform`, it triggers `OnStartWithStreamInput/OnEndWithStreamOutput/OnError` because Graph internally always executes as `Invoke` or `Transform`. See [Streaming Essentials](/en/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
+Graph triggers callbacks at its own start/end/error timings. If Graph is called via `Invoke`, it triggers `OnStart/OnEnd/OnError`. If called via `Stream/Collect/Transform`, it triggers `OnStartWithStreamInput/OnEndWithStreamOutput/OnError` because Graph internally always executes as `Invoke` or `Transform`. See [Streaming Essentials](/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
 
 Note: Graph is also a component. Therefore, a graph callback is a special form of component callback. Per Node Callback semantics, when a node’s internal component (including a nested graph added via `AddGraphNode`) implements callback timings itself, the node reuses the component’s behavior and does not add duplicate node-level callbacks.
 

content/en/docs/eino/core_modules/chain_and_graph_orchestration/checkpoint_interrupt.md

@@ -240,7 +240,7 @@ func StatefulInterrupt(ctx context.Context, info any, state any) error
 func CompositeInterrupt(ctx context.Context, info any, state any, errs ...error)
 ```
 
-See design details: [Eino human-in-the-loop framework: architecture guide](/en/docs/eino/core_modules/eino_adk/agent_hitl)
+See design details: [Eino human-in-the-loop framework: architecture guide](/docs/eino/core_modules/eino_adk/agent_hitl)
 
 ## CheckPoint in Streaming
 

content/en/docs/eino/core_modules/chain_and_graph_orchestration/orchestration_design_principles.md

@@ -140,7 +140,7 @@ AddChatModelNode("xxx", model, WithStreamStatePostHandler(postHandler))
 
 ### Invoke vs Stream Alignment
 
-`Runnable` offers `Invoke/Stream/Collect/Transform`. See [Streaming Essentials](/en/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
+`Runnable` offers `Invoke/Stream/Collect/Transform`. See [Streaming Essentials](/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
 
 Assume a `Graph[[]*schema.Message, []*schema.Message]` with a ChatModel node and a Lambda node, compiled to `Runnable[[]*schema.Message, []*schema.Message]`:
 
@@ -221,7 +221,7 @@ Workflow maps fields across nodes; upstream structs are converted to maps, so th
 - Auto merge: see Fan‑in above
 - Auto copy: duplicate streams where needed (fan‑out to multiple downstreams, callbacks)
 
-All orchestration elements can sense/handle streams (branch, state handler, callback handler, passthrough, lambda, etc.). See [Streaming Essentials](/en/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
+All orchestration elements can sense/handle streams (branch, state handler, callback handler, passthrough, lambda, etc.). See [Streaming Essentials](/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials).
 
 ### Global State
 
@@ -233,7 +233,7 @@ All orchestration elements can sense/handle streams (branch, state handler, call
 
 ### Callback Injection
 
-Components may or may not implement callback aspects. If a component implements `Checker` with `IsCallbacksEnabled()==true`, the framework uses the component’s internal callbacks; otherwise it wraps external callbacks reporting only input/output. Graph always injects callbacks with `RunInfo` for itself. See [Callback Manual](/en/docs/eino/core_modules/chain_and_graph_orchestration/callback_manual).
+Components may or may not implement callback aspects. If a component implements `Checker` with `IsCallbacksEnabled()==true`, the framework uses the component’s internal callbacks; otherwise it wraps external callbacks reporting only input/output. Graph always injects callbacks with `RunInfo` for itself. See [Callback Manual](/docs/eino/core_modules/chain_and_graph_orchestration/callback_manual).
 
 ### Option Distribution
 
@@ -242,7 +242,7 @@ Components may or may not implement callback aspects. If a component implements
 - Specific nodes — `DesignateNode(key ...string)`
 - Nested graphs or their nodes — `DesignateNodeWithPath(path ...*NodePath)`
 
-See [CallOption Capabilities](/en/docs/eino/core_modules/chain_and_graph_orchestration/call_option_capabilities).
+See [CallOption Capabilities](/docs/eino/core_modules/chain_and_graph_orchestration/call_option_capabilities).
 
 ### Graph Nesting
 

content/en/docs/eino/core_modules/chain_and_graph_orchestration/stream_programming_essentials.md

@@ -8,7 +8,7 @@ weight: 4
 ---
 
 > 💡
-> Recommended reading first: [Eino: Overview](/en/docs/eino/overview) and [Eino: Orchestration Design Principles](/en/docs/eino/core_modules/chain_and_graph_orchestration/orchestration_design_principles)
+> Recommended reading first: [Eino: Overview](/docs/eino/overview) and [Eino: Orchestration Design Principles](/docs/eino/core_modules/chain_and_graph_orchestration/orchestration_design_principles)
 
 ## Streaming in Orchestration: Overview
 
@@ -76,7 +76,7 @@ type Retriever interface {
 <tr><td>Tool</td><td>yes</td><td>yes</td><td>no</td><td>no</td></tr>
 </table>
 
-Official Eino components: only `ChatModel` and `Tool` also support `Stream`; all others support `Invoke` only. See: [Eino: Components](/en/docs/eino/core_modules/components)
+Official Eino components: only `ChatModel` and `Tool` also support `Stream`; all others support `Invoke` only. See: [Eino: Components](/docs/eino/core_modules/components)
 
 `Collect` and `Transform` are generally useful only within orchestration.
 
@@ -99,7 +99,7 @@ If the Tool is `StreamableTool` (output is `StreamReader[Message]`), then Tool 
 Eino’s automatic `StreamReader[T] → T` conversion applies whenever a component expects `T` but upstream produces `StreamReader[T]`. You may need to provide a custom concat function for `T`.
 
 > 💡
-> The `StreamReader[T] → T` conversion may require a user-provided concat function. See [Orchestration Design Principles](/en/docs/eino/core_modules/chain_and_graph_orchestration/orchestration_design_principles) under “merge frames”.
+> The `StreamReader[T] → T` conversion may require a user-provided concat function. See [Orchestration Design Principles](/docs/eino/core_modules/chain_and_graph_orchestration/orchestration_design_principles) under “merge frames”.
 
 Conversely, consider another ReAct diagram:
 

content/en/docs/eino/core_modules/components/_index.md

@@ -26,41 +26,41 @@ Mapping components to patterns:
 
 1. Template and parameter preparation for LLM interaction: `ChatTemplate`
 
-   - See [Eino: ChatTemplate Guide](/en/docs/eino/core_modules/components/chat_template_guide)
+   - See [Eino: ChatTemplate Guide](/docs/eino/core_modules/components/chat_template_guide)
 
 2. Direct LLM interaction: `ChatModel`
 
-   - See [Eino: ChatModel Guide](/en/docs/eino/core_modules/components/chat_model_guide)
+   - See [Eino: ChatModel Guide](/docs/eino/core_modules/components/chat_model_guide)
 
 **Text semantics components:**
 
 1. Document acquisition and processing: `Document.Loader`, `Document.Transformer`
 
-   - See [Document Loader Guide](/en/docs/eino/core_modules/components/document_loader_guide) and [Document Transformer Guide](/en/docs/eino/core_modules/components/document_transformer_guide)
+   - See [Document Loader Guide](/docs/eino/core_modules/components/document_loader_guide) and [Document Transformer Guide](/docs/eino/core_modules/components/document_transformer_guide)
 
 2. Semantic embedding of documents: `Embedding`
 
-   - See [Embedding Guide](/en/docs/eino/core_modules/components/embedding_guide)
+   - See [Embedding Guide](/docs/eino/core_modules/components/embedding_guide)
 
 3. Indexing and storage of embeddings: `Indexer`
 
-   - See [Indexer Guide](/en/docs/eino/core_modules/components/indexer_guide)
+   - See [Indexer Guide](/docs/eino/core_modules/components/indexer_guide)
 
 4. Retrieval of semantically related documents: `Retriever`
 
-   - See [Retriever Guide](/en/docs/eino/core_modules/components/retriever_guide)
+   - See [Retriever Guide](/docs/eino/core_modules/components/retriever_guide)
 
 **Decision and execution components:**
 
 1. Tool-enabled decision making for LLMs: `ToolsNode`
 
-   - See [ToolsNode Guide](/en/docs/eino/core_modules/components/tools_node_guide)
+   - See [ToolsNode Guide](/docs/eino/core_modules/components/tools_node_guide)
 
 **Custom logic:**
 
 1. User-defined business logic: `Lambda`
 
-   - See [Lambda Guide](/en/docs/eino/core_modules/components/lambda_guide)
+   - See [Lambda Guide](/docs/eino/core_modules/components/lambda_guide)
 
 Components provide application capabilities — the bricks and mortar of LLM app construction. Eino’s component abstractions follow these principles:
 

content/en/docs/eino/core_modules/components/chat_model_guide.md

@@ -274,10 +274,10 @@ result, _ := run.Invoke(ctx, messages, compose.WithCallbacks(helper))
 
 ## Existing Implementations
 
-1. OpenAI ChatModel: [ChatModel — OpenAI](/en/docs/eino/ecosystem_integration/chat_model/chat_model_openai)
-2. Ollama ChatModel: [ChatModel — Ollama](/en/docs/eino/ecosystem_integration/chat_model/chat_model_ollama)
-3. Ark ChatModel: [ChatModel — Ark](/en/docs/eino/ecosystem_integration/chat_model/chat_model_ark)
-4. More: [Eino ChatModel](/en/docs/eino/ecosystem_integration/chat_model/)
+1. OpenAI ChatModel: [ChatModel — OpenAI](/docs/eino/ecosystem_integration/chat_model/chat_model_openai)
+2. Ollama ChatModel: [ChatModel — Ollama](/docs/eino/ecosystem_integration/chat_model/chat_model_ollama)
+3. Ark ChatModel: [ChatModel — Ark](/docs/eino/ecosystem_integration/chat_model/chat_model_ark)
+4. More: [Eino ChatModel](/docs/eino/ecosystem_integration/chat_model/)
 
 ## Implementation Notes
 

content/en/docs/eino/core_modules/components/document_loader_guide/_index.md

@@ -141,9 +141,9 @@ log.Printf("doc content: %v", outDocs[0].Content)
 
 ## Existing Implementations
 
-1. File Loader — local filesystem: [Loader — local file](/en/docs/eino/ecosystem_integration/document/loader_local_file)
-2. Web Loader — HTTP/HTTPS: [Loader — web url](/en/docs/eino/ecosystem_integration/document/loader_web_url)
-3. S3 Loader — S3-compatible storage: [Loader — Amazon S3](/en/docs/eino/ecosystem_integration/document/loader_amazon_s3)
+1. File Loader — local filesystem: [Loader — local file](/docs/eino/ecosystem_integration/document/loader_local_file)
+2. Web Loader — HTTP/HTTPS: [Loader — web url](/docs/eino/ecosystem_integration/document/loader_web_url)
+3. S3 Loader — S3-compatible storage: [Loader — Amazon S3](/docs/eino/ecosystem_integration/document/loader_amazon_s3)
 
 ## Implementation Notes
 
@@ -252,7 +252,7 @@ func (l *CustomLoader) doLoad(ctx context.Context, src document.Source, opts *cu
 
 ## Other References
 
-- [Eino: Document Transformer Guide](/en/docs/eino/core_modules/components/document_transformer_guide)
-- [Eino: Embedding Guide](/en/docs/eino/core_modules/components/embedding_guide)
-- [Eino: Indexer Guide](/en/docs/eino/core_modules/components/indexer_guide)
-- [Eino: Retriever Guide](/en/docs/eino/core_modules/components/retriever_guide)
+- [Eino: Document Transformer Guide](/docs/eino/core_modules/components/document_transformer_guide)
+- [Eino: Embedding Guide](/docs/eino/core_modules/components/embedding_guide)
+- [Eino: Indexer Guide](/docs/eino/core_modules/components/indexer_guide)
+- [Eino: Retriever Guide](/docs/eino/core_modules/components/retriever_guide)