docs/man/nut.txt: reword coupling of upsmon with upssched

jimklimov · jimklimov · commit 45505a689788 · 2025-06-04T11:12:31.000+02:00
Signed-off-by: Jim Klimov &lt;jimklimov+nut@gmail.com&gt;
diff --git a/docs/man/nut.txt b/docs/man/nut.txt
@@ -134,8 +134,8 @@ NOTE: The `upsmon` client typically splits into two processes: an unprivileged
   the time comes.
 +
 NUT deployments which desire higher-fidelity control (e.g. different systems
-  shutting down after different time spent on battery) often couple `upsmon`
-  with linkman:upssched[8].
+  shutting down after different time spent on battery) often couple the
+  linkman:upsmon[8] with linkman:upssched[8] as their `NOTIFYCMD` handler.
 +
 The "primary" system is usually also responsible for commanding the managed
   UPS to shut itself down and power up when the "wall power" returns (or to

Original file line number	Diff line number	Diff line change
@@ -134,8 +134,8 @@ NOTE: The `upsmon` client typically splits into two processes: an unprivileged
`134`	`134`	`the time comes.`
`135`	`135`	`+`
`136`	`136`	`NUT deployments which desire higher-fidelity control (e.g. different systems`
`137`		- shutting down after different time spent on battery) often couple `upsmon`
`138`		`- with linkman:upssched[8].`
	`137`	`+ shutting down after different time spent on battery) often couple the`
	`138`	+ linkman:upsmon[8] with linkman:upssched[8] as their `NOTIFYCMD` handler.
`139`	`139`	`+`
`140`	`140`	`The "primary" system is usually also responsible for commanding the managed`
`141`	`141`	`UPS to shut itself down and power up when the "wall power" returns (or to`