diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index a020214ac6..5bb13fcfe7 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -203,12 +203,18 @@
has RemainAfterExit= not set) it will not show up as started afterwards, but
as dead.
- Behavior of is similar to ; however, it is
- expected that the service acquires a name on the D-Bus bus, as configured by
- BusName=. systemd will proceed with starting follow-up units after the D-Bus bus name
- has been acquired. Service units with this option configured implicitly gain dependencies on the
- dbus.socket unit. This type is the default if BusName= is
- specified.
+ Behavior of is similar to ; however,
+ it is expected that the service acquires a name on the D-Bus bus, as configured by
+ BusName=. systemd will proceed with starting follow-up units after the D-Bus
+ bus name has been acquired. Service units with this option configured implicitly gain
+ dependencies on the dbus.socket unit. This type is the default if
+ BusName= is specified. A service unit of this type is considered to be in the
+ activating state until the specified bus name is acquired. It is considered activated while the
+ bus name is taken. Once the bus name is released the service is considered being no longer
+ functional which has the effect that the service manager attempts to terminate any remaining
+ processes belonging to the service. Services that drop their bus name as part of their shutdown
+ logic thus should be prepared to receive a SIGTERM (or whichever signal is
+ configured in KillSignal=) as result.Behavior of is similar to ; however, it is
expected that the service sends a notification message via