Skip to content

typo: "achitectural" -> "architectural" #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
apenwarr merged 1 commit into from
Jul 8, 2026
Merged

typo: "achitectural" -> "architectural" #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down