Index: docs/faq.txt
===================================================================
--- docs/faq.txt	(revision 4528)
+++ docs/faq.txt	(working copy)
@@ -328,8 +328,9 @@
 
 Although we recommend mod_python for production use, you don't have to use it,
 thanks to the fact that Django uses an arrangement called WSGI_. Django can
-talk to any WSGI-enabled server. The most common non-mod_python deployment
-setup is FastCGI. See `How to use Django with FastCGI`_ for full information.
+talk to any WSGI-enabled server. Other common non-mod_python deployment
+setups are FastCGI, SCGI, or AJP. See `How to use Django with FastCGI`_ for 
+full information.
 
 Also, see the `server arrangements wiki page`_ for other deployment strategies.
 
Index: docs/fastcgi.txt
===================================================================
--- docs/fastcgi.txt	(revision 4528)
+++ docs/fastcgi.txt	(working copy)
@@ -3,10 +3,17 @@
 ==============================
 
 Although the `current preferred setup`_ for running Django is Apache_ with
-`mod_python`_, many people use shared hosting, on which FastCGI is the only
-viable option. In some setups, FastCGI also allows better security -- and,
-possibly, better performance -- than mod_python.
+`mod_python`_, many people use shared hosting, on which protocols such as
+FastCGI, SCGI, or AJP are the only viable options. In some setups, these protocols
+also allow better security -- and, possibly, better performance -- than mod_python.
 
+.. admonition:: Note
+
+    This document discusses FastCGI, but any flup-supported protocol can be 
+    selected by using the `protocol=`<protocol_name> option with 
+    `./manage.py runfcgi` where <protocol-name> may currently be one of: 
+    `fcgi` (the default), `scgi`, or `ajp`.    
+
 Essentially, FastCGI is an efficient way of letting an external application
 serve pages to a Web server. The Web server delegates the incoming Web requests
 (via a socket) to FastCGI, which executes the code and passes the response back
Index: docs/modpython.txt
===================================================================
--- docs/modpython.txt	(revision 4528)
+++ docs/modpython.txt	(working copy)
@@ -13,7 +13,8 @@
 Django requires Apache 2.x and mod_python 3.x, and you should use Apache's
 `prefork MPM`_, as opposed to the `worker MPM`_.
 
-You may also be interested in `How to use Django with FastCGI`_.
+You may also be interested in `How to use Django with FastCGI`_ (which also 
+covers SCGI and AJP).
 
 .. _Apache: http://httpd.apache.org/
 .. _mod_python: http://www.modpython.org/