Merge pull request #4 from 2016bgeyer/patch-1

fix: Fixed typo in README.md

README.md

@@ -206,7 +206,8 @@ All these memories need to go somewhere reliable. All LangGraph deployments come
 
 You can learn more about Storage in LangGraph [here](https://langchain-ai.github.io/langgraph/how-tos/memory/shared-state/).
 
-In our case, we are saving all memories namespaced by `user_id` and by the memory scheam you provide. That way you can easily search for memories for a given user and of a particular type. This diagram shows how these pieces fit together:
+In our case, we are saving all memories namespaced by `user_id` and by the memory schema you provide. That way you can easily search for memories for a given user and of a particular type. This diagram shows how these pieces fit together:
+
 
 ![Memory types](./static/memory_types.png)
 

src/chatbot/graph.py

@@ -61,7 +61,7 @@ async def schedule_memories(state: ChatState, config: RunnableConfig) -> None:
         multitask_strategy="enqueue",
         # This lets us "debounce" repeated requests to the memory graph
         # if the user is actively engaging in a conversation. This saves us $$ and
-        # can help reduce the occurence of duplicate memories.
+        # can help reduce the occurrence of duplicate memories.
         after_seconds=configurable.delay_seconds,
         # Specify the graph and/or graph configuration to handle the memory processing
         assistant_id=configurable.mem_assistant_id,