diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index 159f629498..a4de424835 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -537,7 +537,14 @@
Similar to Requires=.
However, if the units listed here are not started already,
they will not be started and the transaction will fail
- immediately.
+ immediately.
+
+ When Requisite=b.service is used on
+ a.service, this dependency will show as
+ RequisiteOf=a.service in property listing of
+ b.service. RequisiteOf=
+ dependency cannot be specified directly.
+
@@ -575,7 +582,14 @@
enters inactive state, but also one that is bound to another unit that gets skipped due to a failed condition
check (such as ConditionPathExists=, ConditionPathIsSymbolicLink=, … —
see below) will be stopped, should it be running. Hence, in many cases it is best to combine
- BindsTo= with After=.
+ BindsTo= with After=.
+
+ When BindsTo=b.service is used on
+ a.service, this dependency will show as
+ BoundBy=a.service in property listing of
+ b.service. BoundBy=
+ dependency cannot be specified directly.
+
@@ -586,7 +600,14 @@
restarting of units. When systemd stops or restarts the units
listed here, the action is propagated to this unit. Note that
this is a one-way dependency — changes to this unit do not
- affect the listed units.
+ affect the listed units.
+
+ When PartOf=b.service is used on
+ a.service, this dependency will show as
+ ConsistsOf=a.service in property listing of
+ b.service. ConsistsOf=
+ dependency cannot be specified directly.
+