X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=fetchmail-FAQ.html;h=5a62cbe8d13983951fc27d17aa63d04a862cbbd9;hb=d2ebbc7eed0bb38bf18bf91ed2707317714f9648;hp=0e4e0054d5146d760e321700474b0f27109ab857;hpb=9347f01e7b1368a67b58437b45bc58bbec391a56;p=~andy%2Ffetchmail

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 0e4e0054..5a62cbe8 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
@@ -2538,10 +2538,11 @@ the most secure schemes are tried first.</p>
 
 <p>However, sometimes the server offers a secure authentication scheme
 that is not properly configured, or an authentication scheme such as
-GSSAPI does requires credentials to be acquired externally. In some
-situations, fetchmail cannot know the scheme will fail without trying
-it. In most cases, fetchmail should proceed to the next authentication
-scheme automatically, but this sometimes does not work.</p>
+GSSAPI that requires credentials to be acquired externally. In some
+situations, fetchmail cannot know that the scheme will fail beforehand,
+without trying it. In most cases, fetchmail should proceed to the next
+authentication scheme automatically, but this sometimes does not
+work.</p>
 
 <p><strong>Solution:</strong> Configure the right authentication scheme
 explicitly, for instance, with <kbd>--auth cram-md5</kbd> or <kbd>--auth