From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc: varyus speling fickses
Date: Sat, 5 Mar 2016 07:02:49 +0000 [thread overview]
Message-ID: <20160305070249.27798-1-e@80x24.org> (raw)
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
next reply other threads:[~2016-03-05 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 7:02 Eric Wong [this message]
2016-03-05 7:10 ` [PATCH] doc: language-neutral client-side endpoints Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160305070249.27798-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).