--- a/README.asc
+++ b/README.asc
@@ -1,19 +1,20 @@
-= upmpdcli: an UPnP front-end to the Music Player Daemon
+=== upmpdcli: an UPnP front-end to the Music Player Daemon
-upmpdcli implements an UPnP Media Renderer, using MPD to perform the real
-work.
+*upmpdcli* implements an *UPnP* _Media Renderer_, using *MPD* to perform
+the real work.
-It has been tested with a number of UPnP control points running on Android
-and Windows. Because of their good support of OpenHome Playlists, which are
-a significant improvement over bare UPnP, and their general quality, Bubble
-UPnP (Android app) and Linn Kinsky (free on Windows) work best with it.
+It has been tested with a number of *UPnP* control points running on
+*Android* and *Windows*. Because of their good support of *OpenHome*
+_Playlists_, which are a significant improvement over bare *UPnP*, and
+their general quality, *Bubble UPnP* (*Android* app) and Linn *Kinsky* (free on
+*Windows*) work best with it.
-== How things work:
+==== How things work:
-The Control Points uses the UPnP protocols to browse the tracks on the
-Media Server and choses URIs to be played. It then talks UPnP to umpdcli,
-which uses the mpd client protocol to place the URIs into the MPD
-playlist. mpd finally retrieves the data from the Media Server using HTTP.
+The Control Points uses the *UPnP* protocols to browse the tracks on the
+_Media Server_ and choses URIs to be played. It then talks *UPnP* to *umpdcli*,
+which uses the *MPD* client protocol to place the URIs into the *MPD*
+playlist. *MPD* finally retrieves the data from the _Media Server_ using HTTP.
....
[UPnP Control Point]
@@ -31,10 +32,7 @@
[MPD]<--(HTTP)-->[UPnP Media Server]
....
-Each of the Control point, Media Server, mpd and upmpdcli processes can run
-on any network host, there is no reason, for example, for mpd and upmpdcli
-to run on the same host.
+Each of the _Control point_, _Media Server_, *MPD* and *upmpdcli* processes
+can run on any network host.
More information: http://www.lesbonscomptes.com/upmpdcli
-
-