unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <uwe@kleine-koenig.org>
To: meta@public-inbox.org
Subject: [PATCH] tree-wide: Fix typo likelyhood
Date: Fri,  1 Jul 2022 16:04:20 +0200	[thread overview]
Message-ID: <20220701140420.278395-1-uwe@kleine-koenig.org> (raw)

This was pointed out by the Debian package linter "lintian".
---
 Documentation/lei-up.pod           | 2 +-
 Documentation/technical/memory.txt | 2 +-
 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 8fba0953b1ef..ac644a9693fc 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 bb1c92fde1e7..ea7fb7b710e1 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 51ee3d9c83e4..c998e5c0ed7b 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

base-commit: 70209c643bd5b21d369dff684218714f5186993b
-- 
2.36.1


                 reply	other threads:[~2022-07-01 14:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220701140420.278395-1-uwe@kleine-koenig.org \
    --to=uwe@kleine-koenig.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.
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).