git » homepage.git » commit 68d0e3a

diff --git a/md/_GridCalc.md b/md/_GridCalc.md
index 4ceb1bb..0a7d89e 100644
--- a/md/_GridCalc.md
+++ b/md/_GridCalc.md
@@ -18,16 +18,18 @@ What follows is a retrospective on how that happened, why it looks the way it do
 
 ## The seed: Forth and touchscreens
 
-I learned [Forth](https://en.wikipedia.org/wiki/Forth_(programming_language)) around 2011, and what stuck with me was not just the stack but the flatness of the syntax: words, space-separated, linear, no parentheses, no precedence, a stream of tokens in plain sight.
+I learned some [Forth](https://en.wikipedia.org/wiki/Forth_(programming_language)) around 2011, and what stuck with me was not just the stack but the flatness of the syntax: words, space-separated, linear, no parentheses, no precedence, a stream of tokens in plain sight.
 
 It felt like a language that wanted to be handled like physical tokens, where you drag words around, reorder them, insert one between two others, and treat the code as something you can literally move with your hands.
 
-An implication of that kind of free drag-and-drop editing is that you can accidentally land in a structurally invalid program. On mobile I was dissatisfied with open editing, because it seemed like you want constrained, structural editing. The grid sketch was my answer: a constrained layout that only lets you build valid programs. I never prototyped that idea, but it never went away.
+I never prototyped that idea, but it never went away.
 
 ## The notebook sketch
 
 Then, in early February 2026 I woke up and drew a sketch in a tiny 3x5 notepad. The idea was a grid that represents time. Left to right, top to bottom, every entry or operation becomes a persistent cell. The grid is not a table. It is a linear program with a 2D view so references are easy.
 
+The grid is also not a free form touch-editing interface for Forth like I'd previously imagined, because only structurally valid manipulations are possible. Furthermore, the the manipulations themselves are represented on the grid. The grid is the data, the program, and the historical timeline all in one.
+
 The sketch shows the basics: inputs and operations flow left to right and then top to bottom, and because the program sits on a 2D grid you can reference earlier results by cell coordinates the same way you do in a spreadsheet.
 
 <figure style="float: left; margin: 0 1.5rem 1rem 0; width: 306px;">