diff options
| -rw-r--r-- | Documentation/lei-up.pod | 2 | ||||
| -rw-r--r-- | Documentation/technical/memory.txt | 2 | ||||
| -rw-r--r-- | lib/PublicInbox/LeiQuery.pm | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/lei-up.pod b/Documentation/lei-up.pod index 8fba0953..ac644a96 100644 --- a/Documentation/lei-up.pod +++ b/Documentation/lei-up.pod @@ -26,7 +26,7 @@ updates remote mailboxes (currently C<imap://> and C<imaps://>). Look for mail older than the time of the last successful query. Using a small interval will reduce bandwidth use. A larger -interval reduces the likelyhood of missing a result due to MTA +interval reduces the likelihood of missing a result due to MTA delays or downtime. The time(s) of the last successful queries are the C<lastresult> diff --git a/Documentation/technical/memory.txt b/Documentation/technical/memory.txt index bb1c92fd..ea7fb7b7 100644 --- a/Documentation/technical/memory.txt +++ b/Documentation/technical/memory.txt @@ -13,7 +13,7 @@ deterministically release memory back to the heap. We start with a simple data model with few circular references. This both eases human understanding and reduces -the likelyhood of bugs. +the likelihood of bugs. Knowing the relative sizes and quantities of our data structures, we limit the scope of allocations as much as diff --git a/lib/PublicInbox/LeiQuery.pm b/lib/PublicInbox/LeiQuery.pm index 51ee3d9c..c998e5c0 100644 --- a/lib/PublicInbox/LeiQuery.pm +++ b/lib/PublicInbox/LeiQuery.pm @@ -185,7 +185,7 @@ sub _complete_q { # FIXME: Getopt::Long doesn't easily let us support support options with # '.' in them (e.g. --http1.1) # TODO: should we depend on "-c http.*" options for things which have -# analogues in git(1)? that would reduce likelyhood of conflicts with +# analogues in git(1)? that would reduce likelihood of conflicts with # our other CLI options # Note: some names are renamed to avoid potential conflicts, # see %lei2curl in lib/PublicInbox/LeiCurl.pm |