doc: Clarify theme use

Signed-off-by: Guido Günther <agx@sigxcpu.org>

README.md

@@ -70,11 +70,9 @@ See `examples/` for a simple python example using GObject introspection.
 
 ## How it works
 
-We're using a [event naming spec](./doc/Event-naming-spec-0.0.0.md)
-similar to <http://0pointer.de/public/sound-naming-spec.html> to name
-events. This will allow us to act as a system sound library so
-applications only need to call into this library and things like
-the quiet and silent profile work out of the box.
+Whenever an event is submitted to the daemon by a client via the DBus API *feedbackd*
+looks up the corresponding feedbacks according to the current profile in the currently
+active feedback theme (taking per application profile settings into account).
 
 Any feedback triggered by a client via an event will be stopped latest when the
 client disconnects from DBus. This makes sure all feedbacks get canceled if the
@@ -82,9 +80,9 @@ app that triggered it crashes.
 
 ### Feedback theme
 
-Events are then mapped to a specific type of feedback (sound, led, vibra) via a
-device specific theme - since devices have different capabilities and
-different users different needs.
+As devices have varying capabilities and users different needs, events
+are mapped to a feedbacks (sound, LED, vibra) via a configurable
+theme.
 
 Feedbackd is shipped with a default theme `default.json`.
 You can add your own themes in multiple ways: