X-Git-Url: http://www.git.stargrave.org/?a=blobdiff_plain;f=Documentation%2Fdesign_notes.txt;fp=Documentation%2Fdesign_notes.txt;h=5da48b5dcc2b302e0267eacea43d1e0ae5336cca;hb=209476bb4cf497810564eb764e93854504a3aa6d;hp=ec1dc80084f65e1ea220e68bfaa0cf603d63fb8f;hpb=22f181c10256278f0fb4c9a664a82e3e68d208a6;p=public-inbox.git

diff --git a/Documentation/design_notes.txt b/Documentation/design_notes.txt
index ec1dc800..5da48b5d 100644
--- a/Documentation/design_notes.txt
+++ b/Documentation/design_notes.txt
@@ -41,7 +41,7 @@ Why email?
   developers and users of Free Software should not rely on proprietary
   tools or services.
 
-* Existing infrastrucuture, tools, and user familarity.
+* Existing infrastructure, tools, and user familiarity.
   There is already a large variety of tools, clients, and email providers
   available.  There are also many resources for users to run their own
   SMTP server on a domain they control.
@@ -143,10 +143,10 @@ Scalability notes
 Even with shallow clone, storing the history of large/busy mailing lists
 may place much burden on subscribers and servers.  However, having a
 single (or few) refs representing the entire history of a list is good
-for small lists since it's easier to lookup a message by Message-ID, so
+for small lists since it's easier to look up a message by Message-ID, so
 we want to avoid splitting refs with independent histories.
 
-ssoma will likely grow its own builtin ref rotation system based on
+ssoma will likely grow its own built-in ref rotation system based on
 message count (not rotating at fixed time intervals).  This would
 split the histories and require O(n) lookup time based on Message-ID,
 where `n' is the number of history splits.