docs/man/clone.txt: revise vs. clone-outlet page

Signed-off-by: Jim Klimov <[email protected]>

docs/man/clone.txt

@@ -22,7 +22,16 @@ DESCRIPTION
 
 This driver, which sits on top of another driver socket, allows users to group
 clients to a particular outlet of a device and deal with this output as if it
-was a normal UPS.
+were a normal UPS. Unlike the linkman:clone-outlet[8] driver, this driver
+represents a manageable device for that can be used for monitoring and client
+and outlet shutdowns (it supports sending instant commands during run time).
+
+Unlike linkman:dummy-ups[8], this driver does not require a running `upsd`
+data server nor use the networked NUT protocol to talk to the "real" driver
+(which may be remote in case of `dummy-ups` repeater mode).
+
+Remote clients like `upsmon` can `MONITOR` the device entry presented by the
+data server with this driver.
 
 EXTRA ARGUMENTS
 ---------------
@@ -67,8 +76,9 @@ Set the remaining battery runtime when the clone UPS switches to LB
 IMPLEMENTATION
 --------------
 
-The port specification in the linkman:ups.conf[5] reference the driver
-socket that the "real" UPS driver is using. For example:
+The port specification in the linkman:ups.conf[5] should reference the
+local driver socket (or Windows named pipe) that the "real" UPS driver
+is using. For example:
 
 ------
   [realups]
@@ -132,14 +142,15 @@ SEE ALSO
 linkman:upscmd[1],
 linkman:upsrw[1],
 linkman:ups.conf[5],
+linkman:clone-outlet[8],
 linkman:nutupsdrv[8]
 
 Dummy driver:
 ~~~~~~~~~~~~~
 
 The "repeater" mode of 'dummy-ups' driver is in some ways similar to the
-'clone' driver, by relaying information from a locally or remotely running
-"real" device driver (and NUT data server).
+'clone' and 'clone-outlet' drivers, by relaying information from a locally
+or remotely running "real" device driver (and NUT data server).
 
 linkman:dummy-ups[8]