tree-wide: Fix typo likelyhood

This was pointed out by the Debian package linter "lintian".

diff --git a/Documentation/lei-up.pod b/Documentation/lei-up.pod
index 8fba0953b1ef4948bb089da6b777b95e2b3b5d7f..ac644a9693fc9883ce5df359b5e613de33cdf091 100644 (file)
--- 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
 
 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>
 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 bb1c92fde1e7ea388409682d850dadb670140589..ea7fb7b710e1673f196576203aa76b6ede1e2a21 100644 (file)
--- 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
 
 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
 
 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 51ee3d9c83e47b1fed21f02a9cc02b51751d2507..c998e5c0ed7bbf07a09eeb7179857cfce789620c 100644 (file)
--- 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
 # 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
 # our other CLI options
 # Note: some names are renamed to avoid potential conflicts,
 # see %lei2curl in lib/PublicInbox/LeiCurl.pm