X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=fetchmail-FAQ.html;h=6b425ea2c376cc9b7d049e76044f250bcaa9c6be;hb=49268a95ee78bc179fd3439b3f06e9a06c993c92;hp=c57438fc2f58ffb079e61712488d0e6f209ea0d8;hpb=ac5a23769a5b07a24fde7b7cd18940c27c6dfd6a;p=~andy%2Ffetchmail

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index c57438fc..6b425ea2 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -2532,10 +2532,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