Clarify educational goal in README

Author: ibigio

README.md

@@ -1,8 +1,8 @@
 ![Swarm Logo](assets/logo.png)
 
-# Swarm (experimental sample)
+# Swarm (experimental, educational)
 
-An ergonomic, lightweight multi-agent orchestration framework.
+An educational framework exploring ergonomic, lightweight multi-agent orchestration.
 
 > [!WARNING]
 > Swarm is currently an experimental sample framework intended to explore ergonomic interfaces for multi-agent systems. It is not intended to be used in production, and therefore has no official support. (This also means we will not be reviewing PRs or issues!)
@@ -84,9 +84,9 @@ These primitives are powerful enough to express rich dynamics between tools and
 
 ## Why Swarm
 
-Swarm is lightweight, scalable, and highly customizable by design. It is best suited for situations dealing with a large number of independent capabilities and instructions that are difficult to encode into a single prompt.
+Swarm explores patterns that are lightweight, scalable, and highly customizable by design. Approaches similar to Swarm are best suited for situations dealing with a large number of independent capabilities and instructions that are difficult to encode into a single prompt.
 
-The Assistants API is a great option for developers looking for fully-hosted threads and built in memory management and retrieval. However, Swarm is optimal for developers who want full transparency and fine-grained control over context, steps, and tool calls. Swarm runs (almost) entirely on the client and, much like the Chat Completions API, does not store state between calls.
+The Assistants API is a great option for developers looking for fully-hosted threads and built in memory management and retrieval. However, Swarm is an educational resource for developers curious to learn about multi-agent orchestration. Swarm runs (almost) entirely on the client and, much like the Chat Completions API, does not store state between calls.
 
 # Examples