From 7b85c37b576e1bba57fa512e7e00a5160b77672b Mon Sep 17 00:00:00 2001 From: zachary62 Date: Mon, 6 Jan 2025 02:57:10 +0000 Subject: [PATCH] fix cases --- README.md | 2 +- docs/node.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3c2b571..84f8718 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ Mini LLM Flow is designed to be **the framework used by LLMs**. In the future, L 1. **👍 Good at Low-level Details:** LLMs can handle details like *wrappers, tools, and prompts*, which don't belong in a framework. Current frameworks are over-engineered, making them hard for humans (and LLMs) to maintain. -2. **👎 Bad at High-level Paradigms:** While paradigms like *MapReduce, task decomposition, and agents* are powerful, LLMs still struggle to design them elegantly. These high-level concepts should be emphasized in frameworks. +2. **👎 Bad at High-level Paradigms:** While paradigms like *MapReduce, Task Decomposition, and Agents* are powerful, LLMs still struggle to design them elegantly. These high-level concepts should be emphasized in frameworks. The ideal framework for LLMs should (1) **strip away low-level implementation details**, and (2) **keep high-level programming paradigms**. Hence, we provide this minimal (100-line) framework that allows LLMs to focus on what matters. diff --git a/docs/node.md b/docs/node.md index 965a529..4ddabfa 100644 --- a/docs/node.md +++ b/docs/node.md @@ -16,7 +16,7 @@ A **Node** is the smallest building block of Mini LLM Flow. Each Node has 3 step 2. `exec(prep_res)` - The **main execution** step, with optional retries and error handling (below). - - Examples: *primarily for LLMs, but can also for remote APIs*。 + - Examples: *primarily for LLMs, but can also for remote APIs*. - ⚠️ If retries enabled, ensure idempotent implementation. - Returns `exec_res`, which is passed to `post()`.