docs: simplify Graphiti setup

Present Graphiti MCP and FalkorDB as a single setup flow, and clarify that the plugin reuses the same storage layer for short-term memory alongside Graphiti's long-term knowledge graph.

Author: vicary

README.md

@@ -77,28 +77,22 @@ No Graphiti call ever blocks a hook return.
 
 ## Prerequisites
 
-### FalkorDB / Redis
-
-A running [FalkorDB](https://www.falkordb.com/) instance accessible via the
-Redis protocol. The easiest way to start one:
-
-```bash
-docker run -p 6379:6379 falkordb/falkordb:latest
-```
-
-### Graphiti MCP Server
-
-A running
+Start the
 [Graphiti MCP server](https://github.com/getzep/graphiti/tree/main/mcp_server)
-accessible over HTTP:
+with its default [FalkorDB](https://www.falkordb.com/) backend:
 
 ```bash
 git clone https://github.com/getzep/graphiti.git
 cd graphiti/mcp_server
 docker compose up -d
 ```
 
-This starts the MCP server at `http://localhost:8000/mcp`.
+This starts Graphiti at `http://localhost:8000/mcp` and FalkorDB/Redis on
+`localhost:6379`.
+
+This plugin reuses that same FalkorDB/Redis storage layer alongside Graphiti: it
+keeps short-term memory locally for every turn, while Graphiti builds the
+long-term knowledge graph on top of the same backend.
 
 > **Note:** Graphiti is optional for basic operation. If Graphiti is
 > unavailable, the plugin continues to function with FalkorDB/Redis-sourced