From 887b8126b8f8dbc473e9ff5a15de1cad7386359e Mon Sep 17 00:00:00 2001
From: Samuel Stroschein <35429197+samuelstroschein@users.noreply.github.com>
Date: Mon, 7 Oct 2024 23:49:17 +0200
Subject: [PATCH] extend explanation

---
 lix/packages/sdk/docs/20-concepts/30-change-graph.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/lix/packages/sdk/docs/20-concepts/30-change-graph.md b/lix/packages/sdk/docs/20-concepts/30-change-graph.md
index 95feaa3312..383d8fa84d 100644
--- a/lix/packages/sdk/docs/20-concepts/30-change-graph.md
+++ b/lix/packages/sdk/docs/20-concepts/30-change-graph.md
@@ -65,4 +65,6 @@ graph TB
 
 ### Why not call it change history?
 
-The term "history" implies a linear sequence of changes which is incorrect. A lix change graph visualizes the relationships between changes, which includes the history but also includes other relationships such as dependencies and merges.
+A lix change graph provides more than history.
+
+The term "history" implies a linear sequence of changes. That holds true in most apps like Google Docs that provide a "history" feature. In lix however, changes are tracked as graph. The graph includes the history but also includes the relationships between changes, such as dependencies and merges.