From 123d6b5d5a86ae2a19cfd538c05614fa316d7869 Mon Sep 17 00:00:00 2001 From: Mike Shaver Date: Mon, 6 Jul 2026 10:26:34 -0400 Subject: [PATCH] typo: "achitectural" -> "architectural" --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7c3128d..fa92dc4 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ The primary attribute of a Thundersnap system is Durability — the D in database “ACID” terminology. Thundersnap works pretty hard to make your data durable. It doesn’t particularly try at Atomicity, Consistency, or Isolation. In this version it’s probably not super Durable either, but -that’s not an achitectural limit. +that’s not an architectural limit. The underlying thesis of Thundersnap is that modern distributed storage needs to rely on *snapshots* rather than real-time synchronization. Nothing