Fix inline code formatting.

Author: GrahamDumpleton

docs/configuration-directives/WSGIDaemonProcess.rst

@@ -376,10 +376,10 @@ Options which can be supplied to the ``WSGIDaemonProcess`` directive are:
     if possible.
 
     Note that when a process is restarted due to a request timeout, if the
-    Apache `LogLevel` is set to `info` or higher, or `wsgi:info` applied for
-    `LogLevel`, messages will be logged to the Apache error log file for the
-    request which gives the Python stack trace for any request handler threads
-    so you can work out where the request is blocking.
+    Apache ``LogLevel`` is set to ``info`` or higher, or ``wsgi:info`` applied
+    for ``LogLevel```, messages will be logged to the Apache error log file for
+    the request which gives the Python stack trace for any request handler
+    threads so you can work out where the request is blocking.
 
 .. _deadlock-timeout:
 

docs/configuration-directives/WSGIErrorOverride.rst

@@ -7,12 +7,12 @@ WSGIErrorOverride
 :Default: ``WSGIErrorOverride Off``
 :Context: server config, virtual host, directory, .htaccess
 
-The `WSGIErrorOverride`` directive when set to `On`, and the WSGI application is
-running in daemon mode, will result in Apache error documents being used rather
-than those passed back by the WSGI application. This allows error documents to
-match any web site that the WSGI application may be integrated as a part of.
-This feature is akin to the `ProxyErrorOverride`` directive of Apache but for
-mod_wsgi only.
+The ``WSGIErrorOverride`` directive when set to ``On``, and the WSGI application
+is running in daemon mode, will result in Apache error documents being used
+rather than those passed back by the WSGI application. This allows error
+documents to match any web site that the WSGI application may be integrated as a
+part of. This feature is akin to the ``ProxyErrorOverride`` directive of Apache
+but for mod_wsgi only.
 
 Note that this directive has no effect when the WSGI application is running in
 embedded mode.

docs/user-guides/debugging-techniques.rst

@@ -30,7 +30,7 @@ your prime source of information when things go wrong.
 Do note though that log messages generated by mod_wsgi are logged with
 various severity levels and which ones will be output to the Apache error
 log files will depend on how Apache has been configured. The standard
-configuration for Apache has the !LogLevel directive being set to 'warn'.
+configuration for Apache has the ``LogLevel`` directive being set to 'warn'.
 With this setting any important error messages will be output, but
 informational messages generated by mod_wsgi which can assist in working
 out what it is doing are not. Thus, if new to mod_wsgi or trying to debug a