aboutsummaryrefslogtreecommitdiffstats
path: root/fetchmail-FAQ.html
diff options
context:
space:
mode:
authorMatthias Andree <matthias.andree@gmx.de>2013-05-11 13:17:10 +0200
committerMatthias Andree <matthias.andree@gmx.de>2013-05-11 13:20:53 +0200
commitff4bcbba4965b386a5d9498dbb2dfbd06809dd62 (patch)
treebc8ac792dd085aa0ae68ec438d730e47910e64b6 /fetchmail-FAQ.html
parent527a4077753ff05fccae54c0b68d29ceb548a081 (diff)
downloadfetchmail-ff4bcbba4965b386a5d9498dbb2dfbd06809dd62.tar.gz
fetchmail-ff4bcbba4965b386a5d9498dbb2dfbd06809dd62.tar.bz2
fetchmail-ff4bcbba4965b386a5d9498dbb2dfbd06809dd62.zip
Fix typo in 'you could [end] up' in FAQ.
Fixes Debian Bug#706776, submitted by David Lawyer.
Diffstat (limited to 'fetchmail-FAQ.html')
-rw-r--r--fetchmail-FAQ.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 6b425ea2..ca483fa3 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -688,7 +688,7 @@ client machine had when it started up.</p>
time) doesn't match the original, the most benign possible result
is that your MTA thinks it's seeing a relaying attempt and refuses.
More frequently, fetchmail will try to connect to a nonexistent
-host address and time out. Worst case, you could up forwarding your
+host address and time out. Worst case, you could end up forwarding your
mail to the wrong machine!</p>
<p>Use the <code>smtpaddress</code> option to force the appended