docs: `Flask-Uploads, X-Forwarded-Host`

docs/deploying/wsgi-standalone.rst

@@ -104,8 +104,8 @@ localhost at port 8000, setting appropriate headers:
     }
 
 If your httpd is not providing these headers, the most common setup invokes the
-host being set from `X-Forwarded-Host` and the remote address from
-`X-Forwarded-For`::
+host being set from ``X-Forwarded-Host`` and the remote address from
+``X-Forwarded-For``::
 
     from werkzeug.contrib.fixers import ProxyFix
     app.wsgi_app = ProxyFix(app.wsgi_app)

docs/patterns/appdispatch.rst

@@ -144,7 +144,7 @@ Dispatch by Path
 ----------------
 
 Dispatching by a path on the URL is very similar.  Instead of looking at
-the `Host` header to figure out the subdomain one simply looks at the
+the ``Host`` header to figure out the subdomain one simply looks at the
 request path up to the first slash::
 
     from threading import Lock

docs/patterns/fileuploads.rst

@@ -184,7 +184,7 @@ An Easier Solution
 
 Because the common pattern for file uploads exists almost unchanged in all
 applications dealing with uploads, there is a Flask extension called
-`Flask-Uploads`_ that implements a full fledged upload mechanism with
+``Flask-Uploads``_ that implements a full fledged upload mechanism with
 white and blacklisting of extensions and more.
 
 .. _Flask-Uploads: http://pythonhosted.org/Flask-Uploads/