diff --git a/docs/fastcgi.txt b/docs/fastcgi.txt
index eee9c8e337..41b9561b6d 100644
--- a/docs/fastcgi.txt
+++ b/docs/fastcgi.txt
@@ -3,7 +3,7 @@ How to use Django with FastCGI
 ==============================
 
 Although the current preferred setup for running Django is Apache_ with
-`mod_python`_, many people use shared hosting, on which FastCGI_ is the only
+`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.
 
@@ -259,4 +259,4 @@ restart your django application for you.
 If you have access to a command shell on a unix system, restarting the
 server can be done with the ``touch`` command::
 
-    touch mysite.fcgi
\ No newline at end of file
+    touch mysite.fcgi
diff --git a/docs/request_response.txt b/docs/request_response.txt
index 607839350e..1a37bb1e89 100644
--- a/docs/request_response.txt
+++ b/docs/request_response.txt
@@ -49,7 +49,8 @@ All attributes except ``session`` should be considered read-only.
     It's possible that a request can come in via POST with an empty ``POST``
     dictionary -- if, say, a form is requested via the POST HTTP method but
     does not include form data. Therefore, you shouldn't use ``if request.POST``
-    to check for use of the POST method; instead, check `method`_.
+    to check for use of the POST method; instead, use ``if reuqest.method ==
+    "POST"`` (see above).
 
     Note: ``POST`` does *not* include file-upload information. See ``FILES``.