diff --git a/DBus-service.md b/DBus-service.md
index 96d5d2a..a54940d 100644
--- a/DBus-service.md
+++ b/DBus-service.md
@@ -13,10 +13,10 @@ For dbus support you need jni/unix-java.so installed on your system (Debian: lib
 
 To run on the system bus you need to take some additional steps.
 It’s advisable to run signal-cli as a separate unix user, the following steps assume you created a user named *signal-cli*.
-These steps, executed as root, should work on all distributions using systemd.
+To run a service on the system bus, a config file is needed to allow the signal-cli user to take a name on the system bus. An example config file can be found in `data/org.asamk.Signal.conf`. This file also configures that any user can talk with the signal-cli daemon.
+The `data/org.asamk.Signal.service` and `data/signal.service` files configure a dbus activated systemd service for signal-cli, so the service is automatically started when the dbus service is requested.
 
-Mind the fact that signal.service executes the signal-cli with "--config /var/lib/signal-cli".
-If you registered with user signal-cli, remove the config option.
+These steps, executed as root, should work on all distributions using systemd.
 
 ```bash
 cp data/org.asamk.Signal.conf /etc/dbus-1/system.d/
@@ -28,4 +28,7 @@ systemctl enable signal.service
 systemctl reload dbus.service
 ```
 
+Mind the fact that signal.service executes the signal-cli with "--config /var/lib/signal-cli".
+If you registered with user signal-cli, remove the config option.
+
 Make sure to use "--dbus-system" with the send command, the service will be autostarted by dbus the first time it is requested.
\ No newline at end of file