diff options
| -rw-r--r-- | Documentation/public-inbox-v2-format.pod | 2 | ||||
| -rw-r--r-- | TODO | 2 | ||||
| -rw-r--r-- | lib/PublicInbox/SolverGit.pm | 2 | ||||
| -rw-r--r-- | lib/PublicInbox/View.pm | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/public-inbox-v2-format.pod b/Documentation/public-inbox-v2-format.pod index 10c63090..0a391e1e 100644 --- a/Documentation/public-inbox-v2-format.pod +++ b/Documentation/public-inbox-v2-format.pod @@ -168,7 +168,7 @@ easier. object_id and Message-ID are already known. =item object_id The blob identifier git uses (currently SHA-1). No need to -publically expose this outside of normal git ops (cloning) and +publicly expose this outside of normal git ops (cloning) and there's no need to make this searchable. As with v1 of public-inbox, this is stored as part of the Xapian document so expensive name lookups can be avoided for document retrieval. @@ -21,7 +21,7 @@ all need to be considered for everything we introduce) * HTTP and NNTP proxy support. Allow us to be a frontend for firewalled off (or Tor-exclusive) instances. The use case is - for offering a publically accessible IP with a cheap VPS, + for offering a publicly accessible IP with a cheap VPS, yet storing large amounts of data on computers without a public IP behind a home Internet connection. diff --git a/lib/PublicInbox/SolverGit.pm b/lib/PublicInbox/SolverGit.pm index baad981d..06b4cdc4 100644 --- a/lib/PublicInbox/SolverGit.pm +++ b/lib/PublicInbox/SolverGit.pm @@ -5,7 +5,7 @@ # searching inboxes for post-image blobs. # this emits a lot of debugging/tracing information which may be -# publically viewed over HTTP(S). Be careful not to expose +# publicly viewed over HTTP(S). Be careful not to expose # local filesystem layouts in the process. package PublicInbox::SolverGit; use strict; diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm index d88b34da..83b622fb 100644 --- a/lib/PublicInbox/View.pm +++ b/lib/PublicInbox/View.pm @@ -149,7 +149,7 @@ EOF <hr><pre id=R><b>Reply instructions:</b> -You may reply publically to <a +You may reply publicly to <a href=#t>this message</a> via plain-text email using any one of the following methods: |