From 854bf2c295a0c5f57a1fa01a341f814482b6583f Mon Sep 17 00:00:00 2001 From: Mal Curtis Date: Wed, 12 Jun 2024 11:27:05 +1200 Subject: [PATCH] Fix grammar in map-reduce.ipynb (#642) --- examples/map-reduce.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/map-reduce.ipynb b/examples/map-reduce.ipynb index 9a386b3aa..237ad240c 100644 --- a/examples/map-reduce.ipynb +++ b/examples/map-reduce.ipynb @@ -7,7 +7,7 @@ "source": [ "# Map Reduce\n", "\n", - "A common pattern in agents is to generate a list of objects, do some work on each of those objects, and then combine the results. This is very similar to the common [map-reduce](https://en.wikipedia.org/wiki/MapReduce) operation. This can be tricky for a few reasons. First, it can be tought to define in structured graph ahead of time because the length of the list of objects may be unknown. Second, in order to do this map-reduce you need multiple versions of the state to exist... but the graph shares a common shared state, so how can this be?\n", + "A common pattern in agents is to generate a list of objects, do some work on each of those objects, and then combine the results. This is very similar to the common [map-reduce](https://en.wikipedia.org/wiki/MapReduce) operation. This can be tricky for a few reasons. First, it can be tough to define a structured graph ahead of time because the length of the list of objects may be unknown. Second, in order to do this map-reduce you need multiple versions of the state to exist... but the graph shares a common shared state, so how can this be?\n", "\n", "LangGraph supports this via the `Send` api. This can be used to allow a conditional edge to `Send` multiple different states to multiple nodes. The state it sends can be different from the state of the core graph.\n", "\n",