From 253c932c6d32925a6e4327106afb63d6ff39f58b Mon Sep 17 00:00:00 2001 From: Nilanjan De Date: Tue, 8 Apr 2025 17:46:47 +0400 Subject: [PATCH] fix typos --- docs/core_abstraction/batch.md | 4 ++-- docs/guide.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/core_abstraction/batch.md b/docs/core_abstraction/batch.md index 6d7e0c2..1ddd7dd 100644 --- a/docs/core_abstraction/batch.md +++ b/docs/core_abstraction/batch.md @@ -82,7 +82,7 @@ summarize_all_files.run(shared) ## 3. Nested or Multi-Level Batches You can nest a **BatchFlow** in another **BatchFlow**. For instance: -- **Outer** batch: returns a list of diretory param dicts (e.g., `{"directory": "/pathA"}`, `{"directory": "/pathB"}`, ...). +- **Outer** batch: returns a list of directory param dicts (e.g., `{"directory": "/pathA"}`, `{"directory": "/pathB"}`, ...). - **Inner** batch: returning a list of per-file param dicts. At each level, **BatchFlow** merges its own param dict with the parent’s. By the time you reach the **innermost** node, the final `params` is the merged result of **all** parents in the chain. This way, a nested structure can keep track of the entire context (e.g., directory + file name) at once. @@ -104,4 +104,4 @@ class DirectoryBatchFlow(BatchFlow): # MapSummaries have params like {"directory": "/path/to/dirA", "filename": "file1.txt"} inner_flow = FileBatchFlow(start=MapSummaries()) outer_flow = DirectoryBatchFlow(start=inner_flow) -``` \ No newline at end of file +``` diff --git a/docs/guide.md b/docs/guide.md index eba0049..be26d4e 100644 --- a/docs/guide.md +++ b/docs/guide.md @@ -85,7 +85,7 @@ Agentic Coding should be a collaboration between Human System Design and Agent I prompt = "What is the meaning of life?" print(call_llm(prompt)) ``` - - > **Sometimes, design Utilies before Flow:** For example, for an LLM project to automate a legacy system, the bottleneck will likely be the available interface to that system. Start by designing the hardest utilities for interfacing, and then build the flow around them. + - > **Sometimes, design Utilities before Flow:** For example, for an LLM project to automate a legacy system, the bottleneck will likely be the available interface to that system. Start by designing the hardest utilities for interfacing, and then build the flow around them. {: .best-practice } 4. **Node Design**: Plan how each node will read and write data, and use utility functions. @@ -224,4 +224,4 @@ my_project/ if __name__ == "__main__": main() - ``` \ No newline at end of file + ```