thodg/mpd_client

diff --git a/MPD_COMMANDS.md b/MPD_COMMANDS.md
index 02945ff..6a0e8ec 100644
--- a/MPD_COMMANDS.md
+++ b/MPD_COMMANDS.md
@@ -1,15 +1,15 @@
-* [Status Commands](#status commands)
-* [Playback Option Commands](#playback option commands)
-* [Playback Control Commands](#playback control commands)
-* [Playlist Commands](#playlist commands)
-* [Stored Playlist Commands](#stored playlist commands)
-* [Database Commands](#database commands)
-* [Sticker Commands](#sticker commands)
-* [Connection Commands](#connection commands)
-* [Reflection Commands](#reflection commands)
-* [Client to client](#client to client)
+* [Status Commands](#status-commands)
+* [Playback Option Commands](#playback-option-commands)
+* [Playback Control Commands](#playback-control-commands)
+* [Playlist Commands](#playlist-commands)
+* [Stored Playlist Commands](#stored-playlist-commands)
+* [Database Commands](#database-commands)
+* [Sticker Commands](#sticker-commands)
+* [Connection Commands](#connection-commands)
+* [Reflection Commands](#reflection-commands)
+* [Client to client](#client-to-client)
 
-### <a id="status commands"></a>Status Commands ###
+### Status Commands ###
 
 ---
 `clearerror => fetch_nothing`
@@ -86,7 +86,7 @@
 * `db_update`: last db update in UNIX time
 * `playtime`: time length of music played
 
-### <a id="playback option commands"></a>Playback Option Commands ###
+### Playback Option Commands ###
 
 ---
 `consume {STATE} => fetch_nothing`
@@ -147,7 +147,7 @@
 
 > Changes volume by amount `CHANGE`.
 
-### <a id="playback control commands"></a>Playback Control Commands ###
+### Playback Control Commands ###
 
 ---
 `next => fetch_nothing`
@@ -196,7 +196,7 @@
 > Stops playing.
 
 
-### <a id="playlist commands"></a>Playlist Commands ###
+### Playlist Commands ###
 
 ---
 `add {URI} => fetch_nothing`
@@ -303,7 +303,7 @@
 
 Swaps the positions of `SONG1` and `SONG2` (both song ids).
 
-### <a id="stored playlist commands"></a>Stored Playlist Commands ###
+### Stored Playlist Commands ###
 
 Playlists are stored inside the configured playlist directory. They are addressed with their file name (without the directory and without the .m3u suffix).
 
@@ -368,7 +368,7 @@ Some of the commands described in this section can be used to run playlist plugi
 
 > Saves the current playlist to `NAME.m3u` in the playlist directory.
 
-### <a id="database commands"></a>Database Commands ###
+### Database Commands ###
 
 ---
 `count {TAG} {NEEDLE} => fetch_object`
@@ -455,7 +455,7 @@ Some of the commands described in this section can be used to run playlist plugi
 
 > The meaning of these depends on the codec, and not all decoder plugins support it.  For example, on Ogg files, this lists the Vorbis comments.
 
-### <a id="sticker commands"></a>Sticker Commands ###
+### Sticker Commands ###
 
 "Stickers" are pieces of information attached to existing MPD objects (e.g. song files, directories, albums). Clients can create arbitrary name/value pairs. MPD itself does not assume any special meaning in them.
 
@@ -490,7 +490,7 @@ Objects which may have stickers are addressed by their object type ("song" for s
 
 > Searches the sticker database for stickers with the specified name, below the specified directory (`URI`). For each matching song, it prints the URI and that one sticker's value.
 
-### <a id="connection commands"></a>Connection Commands ###
+### Connection Commands ###
 
 ---
 `close`
@@ -535,7 +535,7 @@ Objects which may have stickers are addressed by their object type ("song" for s
 > Turns an output on or off, depending on the current state.
 
 
-### <a id="reflection commands"></a>Reflection Commands ###
+### Reflection Commands ###
 
 ---
 `config => fetch_item`
@@ -574,7 +574,7 @@ Objects which may have stickers are addressed by their object type ("song" for s
 
 > Print a list of decoder plugins, followed by their supported suffixes and MIME types.
 
-### <a id="client to client"></a>Client to client ###
+### Client to client ###
 
 Clients can communicate with each others over "channels". A channel is created by a client subscribing to it. More than one client can be subscribed to a channel at a time; all of them will receive the messages which get sent to it.