From 80594c5442f199f47b1f0a15b4f9e825ee2f6095 Mon Sep 17 00:00:00 2001
From: "Paul J. Davis" <paul.joseph.davis@gmail.com>
Date: Sun, 12 Dec 2010 18:12:33 -0500
Subject: [PATCH] Fix errors spotted by jturnball.

---
 doc/htdocs/faq.html | 5 +++--
 doc/site/faq.rst    | 5 +++--
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/doc/htdocs/faq.html b/doc/htdocs/faq.html
index 2542e732..e2664fbc 100644
--- a/doc/htdocs/faq.html
+++ b/doc/htdocs/faq.html
@@ -65,8 +65,9 @@ machine. See the <a class="reference external" href="/configure.html#proc-name">
 <div class="section" id="why-is-there-no-http-keep-alive">
 <h3><a class="toc-backref" href="#contents">Why is there no HTTP Keep-Alive?</a></h3>
 <p>The default Sync workers are designed to run behind Nginx which only uses
-HTTP/1.0 with it's upstream servers. If you want to send requests directly
-to Nginx you should use one of the various async workers.</p>
+HTTP/1.0 with its upstream servers. If you want to deploy Gunicorn to
+handle unbuffered requests (ie, serving requests directly from the internet)
+you should use one of the async workers.</p>
 </div>
 </div>
 <div class="section" id="worker-processes">
diff --git a/doc/site/faq.rst b/doc/site/faq.rst
index f6f91c8b..532e5a9c 100644
--- a/doc/site/faq.rst
+++ b/doc/site/faq.rst
@@ -53,8 +53,9 @@ Why is there no HTTP Keep-Alive?
 --------------------------------
 
 The default Sync workers are designed to run behind Nginx which only uses
-HTTP/1.0 with it's upstream servers. If you want to send requests directly
-to Nginx you should use one of the various async workers.
+HTTP/1.0 with its upstream servers. If you want to deploy Gunicorn to
+handle unbuffered requests (ie, serving requests directly from the internet)
+you should use one of the async workers.
 
 .. _slowloris: http://ha.ckers.org/slowloris/
 .. _setproctitle: http://pypi.python.org/pypi/setproctitle