docs: `True, False and None`

docs/patterns/appdispatch.rst

@@ -176,7 +176,7 @@ request path up to the first slash::
             return app(environ, start_response)
 
 The big difference between this and the subdomain one is that this one
-falls back to another application if the creator function returns `None`::
+falls back to another application if the creator function returns ``None``::
 
     from myapplication import create_app, default_app, get_user_for_prefix
 

docs/patterns/caching.rst

@@ -50,7 +50,7 @@ operations: :meth:`~werkzeug.contrib.cache.BaseCache.get` and
 To get an item from the cache call
 :meth:`~werkzeug.contrib.cache.BaseCache.get` with a string as key name.
 If something is in the cache, it is returned.  Otherwise that function
-will return `None`::
+will return ``None``::
 
     rv = cache.get('my-item')
 

docs/patterns/distribute.rst

@@ -109,7 +109,7 @@ your tarball::
 
 Don't forget that even if you enlist them in your `MANIFEST.in` file, they
 won't be installed for you unless you set the `include_package_data`
-parameter of the `setup` function to `True`!
+parameter of the `setup` function to ``True``!
 
 
 Declaring Dependencies

docs/patterns/mongokit.rst

@@ -76,7 +76,7 @@ Here is an example document (put this also into `app.py`, e.g.)::
 This example shows you how to define your schema (named structure), a
 validator for the maximum character length and uses a special MongoKit feature
 called `use_dot_notation`.  Per default MongoKit behaves like a python
-dictionary but with `use_dot_notation` set to `True` you can use your
+dictionary but with `use_dot_notation` set to ``True`` you can use your
 documents like you use models in nearly any other ORM by using dots to
 separate between attributes.
 

docs/patterns/viewdecorators.rst

@@ -23,7 +23,7 @@ often forgotten, but you don't have to do that by hand, there is a
 function for that that is used like a decorator (:func:`functools.wraps`).
 
 This example assumes that the login page is called ``'login'`` and that
-the current user is stored as `g.user` and `None` if there is no-one
+the current user is stored as `g.user` and ``None`` if there is no-one
 logged in::
 
     from functools import wraps
@@ -120,7 +120,7 @@ As you can see, if no template name is provided it will use the endpoint
 of the URL map with dots converted to slashes + ``'.html'``.  Otherwise
 the provided template name is used.  When the decorated function returns,
 the dictionary returned is passed to the template rendering function.  If
-`None` is returned, an empty dictionary is assumed, if something else than
+``None`` is returned, an empty dictionary is assumed, if something else than
 a dictionary is returned we return it from the function unchanged.  That
 way you can still use the redirect function or return simple strings.
 
@@ -151,15 +151,15 @@ Endpoint Decorator
 ------------------
 
 When you want to use the werkzeug routing system for more flexibility you
-need to map the endpoint as defined in the :class:`~werkzeug.routing.Rule` 
-to a view function. This is possible with this decorator. For example:: 
+need to map the endpoint as defined in the :class:`~werkzeug.routing.Rule`
+to a view function. This is possible with this decorator. For example::
 
     from flask import Flask
     from werkzeug.routing import Rule
 
-    app = Flask(__name__)                                                          
-    app.url_map.add(Rule('/', endpoint='index'))                                   
+    app = Flask(__name__)
+    app.url_map.add(Rule('/', endpoint='index'))
 
-    @app.endpoint('index')                                                         
-    def my_index():                                                                
-        return "Hello world"     
+    @app.endpoint('index')
+    def my_index():
+        return "Hello world"

docs/patterns/wtforms.rst

@@ -64,7 +64,7 @@ Things to remember:
    the data is submitted via the HTTP `POST` method and
    :attr:`~flask.request.args` if the data is submitted as `GET`.
 2. to validate the data, call the :func:`~wtforms.form.Form.validate`
-   method which will return `True` if the data validates, `False`
+   method which will return ``True`` if the data validates, ``False``
    otherwise.
 3. to access individual values from the form, access `form.<NAME>.data`.