[PATCH] doc: varyus speling fickses

[PATCH] doc: varyus speling fickses

[Eric Wong]

Letz trie 2 uphear liter8
---
 Documentation/design_notes.txt | 6 +++---
 README                         | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/design_notes.txt b/Documentation/design_notes.txt
index ec1dc80..5da48b5 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.
diff --git a/README b/README
index af8fa15..a83a48f 100644
--- a/README
+++ b/README
@@ -7,7 +7,7 @@ read via NNTP, Atom feeds or HTML archives.
 
 public-inbox spawned around three main ideas:
 
-* Publically accessible and archived communication is essential to
+* Publicly accessible and archived communication is essential to
   Free Software development.
 
 * Contributing to Free Software projects should not require the
-- 
EW

[PATCH] doc: language-neutral client-side endpoints

[Eric Wong]

Be less specific, client-side code can be written in any
language (and I do not care for JS runtimes implemented in
C++ :P).
---
 Documentation/design_notes.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/design_notes.txt b/Documentation/design_notes.txt
index 5da48b5..c7a8b26 100644
--- a/Documentation/design_notes.txt
+++ b/Documentation/design_notes.txt
@@ -126,7 +126,7 @@ Web notes
 * Expose Message-ID in web views to encourage replies from drive-by
   contributors.
 
-* Raw text endpoint allows users to write client-side JS endpoints
+* Raw text endpoint allows users to write client-side endpoints
   without hosting the data themselves (or on a different server).
 
 What sucks about public-inbox
-- 
EW