diff --git a/docs/settings.rst b/docs/settings.rst
index a79dfd78..88004e11 100644
--- a/docs/settings.rst
+++ b/docs/settings.rst
@@ -43,20 +43,10 @@ Music from local storage
 ========================
 
 If you want use Mopidy to play music you have locally at your machine instead
-of using Spotify, you need to change the backend from the default to
-:mod:`mopidy.backends.local` by adding the following line to your settings
-file::
-
-    BACKENDS = (u'mopidy.backends.local.LocalBackend',)
-
-You may also want to change some of the ``LOCAL_*`` settings. See
-:mod:`mopidy.settings`, for a full list of available settings.
-
-.. note::
-
-    Currently, Mopidy supports using Spotify *or* local storage as a music
-    source. We're working on using both sources simultaneously, and will
-    have support for this in a future release.
+of or in addition to using Spotify, you need to review and maybe change some of
+the ``LOCAL_*`` settings. See :mod:`mopidy.settings`, for a full list of
+available settings. Then you need to generate a tag cache for your local
+music...
 
 
 .. _generating_a_tag_cache:
@@ -66,7 +56,7 @@ Generating a tag cache
 
 Before Mopidy 0.3 the local storage backend relied purely on ``tag_cache``
 files generated by the original MPD server. To remedy this the command
-:command:`mopidy-scan` has been created. The program will scan your current
+:command:`mopidy-scan` was created. The program will scan your current
 :attr:`mopidy.settings.LOCAL_MUSIC_PATH` and build a MPD compatible
 ``tag_cache``.