From 041fd27990f21e53750b3b1b1cd76a8464a67d9a Mon Sep 17 00:00:00 2001
From: Stein Magnus Jodal <stein.magnus@jodal.no>
Date: Sun, 9 Oct 2011 19:30:57 +0200
Subject: [PATCH 1/3] docs: Add link from requirements to the MPRIS frontend

---
 docs/installation/index.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/installation/index.rst b/docs/installation/index.rst
index 198ac9e8..8fd3e840 100644
--- a/docs/installation/index.rst
+++ b/docs/installation/index.rst
@@ -46,6 +46,9 @@ Otherwise, make sure you got the required dependencies installed.
   - To use the Last.FM scrobbler, see :mod:`mopidy.frontends.lastfm` for
     additional requirements.
 
+  - To use the MPRIS frontend, e.g. using the Ubuntu Sound Menu, see
+    :mod:`mopidy.frontends.mpris` for additional requirements.
+
 
 Install latest stable release
 =============================

From a95f960fdb98f8a164ffd6649fb1b433ee678e56 Mon Sep 17 00:00:00 2001
From: Stein Magnus Jodal <stein.magnus@jodal.no>
Date: Sun, 9 Oct 2011 19:34:28 +0200
Subject: [PATCH 2/3] docs: Update location of settings file after
 XDG-ification

---
 docs/settings.rst | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/settings.rst b/docs/settings.rst
index 76eb6315..a6ad3693 100644
--- a/docs/settings.rst
+++ b/docs/settings.rst
@@ -10,10 +10,10 @@ changes you may want to do, and a complete listing of available settings.
 Changing settings
 =================
 
-Mopidy reads settings from the file ``~/.mopidy/settings.py``, where ``~``
-means your *home directory*. If your username is ``alice`` and you are running
-Linux, the settings file should probably be at
-``/home/alice/.mopidy/settings.py``.
+Mopidy reads settings from the file ``~/.config/mopidy/settings.py``, where
+``~`` means your *home directory*. If your username is ``alice`` and you are
+running Linux, the settings file should probably be at
+``/home/alice/.config/mopidy/settings.py``.
 
 You can either create the settings file yourself, or run the ``mopidy``
 command, and it will create an empty settings file for you.
@@ -22,7 +22,7 @@ When you have created the settings file, open it in a text editor, and add
 settings you want to change. If you want to keep the default value for setting,
 you should *not* redefine it in your own settings file.
 
-A complete ``~/.mopidy/settings.py`` may look as simple as this::
+A complete ``~/.config/mopidy/settings.py`` may look as simple as this::
 
     MPD_SERVER_HOSTNAME = u'::'
     SPOTIFY_USERNAME = u'alice'
@@ -77,7 +77,7 @@ To make a ``tag_cache`` of your local music available for Mopidy:
 
     mopidy --list-settings
 
-#. Scan your music library. Currently the command outputs the ``tag_cache`` to
+#. Scan your music library. The command outputs the ``tag_cache`` to
    ``stdout``, which means that you will need to redirect the output to a file
    yourself::
 

From 139ecb6ccf540287cb67f82ce8a4675f85b11675 Mon Sep 17 00:00:00 2001
From: Stein Magnus Jodal <stein.magnus@jodal.no>
Date: Sun, 9 Oct 2011 19:45:10 +0200
Subject: [PATCH 3/3] docs: Note on stopping Mopidy using kill/SIGTERM

---
 docs/running.rst | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/running.rst b/docs/running.rst
index 4912512f..6c8d0ede 100644
--- a/docs/running.rst
+++ b/docs/running.rst
@@ -10,4 +10,11 @@ When Mopidy says ``MPD server running at [127.0.0.1]:6600`` it's ready to
 accept connections by any MPD client. Check out our non-exhaustive
 :doc:`/clients/mpd` list to find recommended clients.
 
-To stop Mopidy, press ``CTRL+C``.
+To stop Mopidy, press ``CTRL+C`` in the terminal where you started Mopidy.
+
+Mopidy will also shut down properly if you send it the TERM signal, e.g. by
+using ``kill``::
+
+    kill `ps ax | grep mopidy | grep -v grep | cut -d' ' -f1`
+
+This can be useful e.g. if you create init script for managing Mopidy.