Removed confusing comments from the docs.

The settings reference documentation doesn't seem the right place to
invite users to write their own db and cache backends.

Also the actual wording makes the task sound trivial, which is hardly
the case; writing a custom db backend is a very difficult task, and
writing a custom cache backend is full of gotcha.

1 files changed, 1 insertions, 5 deletions

diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 0c4924e0d3..b9a7fd1a81 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -183,8 +183,6 @@ The cache backend to use. The built-in cache backends are:
 You can use a cache backend that doesn't ship with Django by setting
 :setting:`BACKEND <CACHES-BACKEND>` to a fully-qualified path of a cache
 backend class (i.e. ``mypackage.backends.whatever.WhateverCache``).
-Writing a whole new cache backend from scratch is left as an exercise
-to the reader; see the other backends for examples.
 
 .. setting:: CACHES-KEY_FUNCTION
 
@@ -486,9 +484,7 @@ The database backend to use. The built-in database backends are:
 
 You can use a database backend that doesn't ship with Django by setting
 ``ENGINE`` to a fully-qualified path (i.e.
-``mypackage.backends.whatever``). Writing a whole new database backend from
-scratch is left as an exercise to the reader; see the other backends for
-examples.
+``mypackage.backends.whatever``).
 
 .. setting:: HOST