diff --git a/README.html b/README.html
index 216b869..515febb 100644
--- a/README.html
+++ b/README.html
@@ -465,17 +465,17 @@ clients to “pair” with the UxPlay server the first time they connect to
 it, by entering a 4-digit pin code that is displayed on the UxPlay
 terminal. (This is optional, but sometimes required if the client is a
 corporately-owned and -managed device with MDM Mobile Device
-Management.) Pairing occurs just once, is currently only recorded in the
-client, and persists unless the UxPlay public key is changed. By default
-(since v1.68) the public key is now generated using the “Device ID”,
-which is either the server’s hardware MAC address, or can be set with
-the -m option (most conveniently using the startup option file).
-(Storage of a more securely-generated persistent key as an OpenSSL “pem”
-file is still available with the -key option). For use of uxplay in a
-more public environment, a list of previously-registered clients can
-(since v1.68) be optionally-maintained using the -reg option: without
-this option, returning clients claiming to be registered are just
-trusted and not checked.</p></li>
+Management.) Pairing occurs just once, is currently only recorded by the
+client unless the -reg option is used, and persists until the UxPlay
+public key is changed. By default (since v1.68) the public key is now
+generated using the “Device ID”, which is either the server’s hardware
+MAC address, or can be set with the -m option (most conveniently using
+the startup option file). (Storage of a more securely-generated
+persistent key as an OpenSSL “pem” file is still available with the -key
+option). For use of uxplay in a more public environment, a list of
+previously-registered clients can (since v1.68) be optionally-maintained
+using the -reg option: without this option, returning clients claiming
+to be registered are just trusted and not checked.</p></li>
 <li><p>By default, UxPlay is locked to its current client until that
 client drops the connection; since UxPlay-1.58, the option
 <code>-nohold</code> modifies this behavior so that when a new client
diff --git a/README.md b/README.md
index 04db3aa..eb97463 100644
--- a/README.md
+++ b/README.md
@@ -379,7 +379,7 @@ help with this or other problems.
 the first time they connect to it, by entering
 a 4-digit pin code that is displayed on the UxPlay terminal.   (This is optional, but sometimes required if the client is a
 corporately-owned and -managed device with MDM Mobile Device Management.)   Pairing occurs just once, is currently only
-recorded in the client, and persists unless the
+recorded by the client unless the -reg option is used, and persists until the
 UxPlay public key is changed.  By default (since v1.68) the public key is now generated using  the  "Device ID", which is either the server's 
 hardware MAC address, or 
 can be set with the -m option (most conveniently using the startup option file).   (Storage of a more securely-generated
diff --git a/README.txt b/README.txt
index 6453826..664bd5c 100644
--- a/README.txt
+++ b/README.txt
@@ -455,18 +455,18 @@ below for help with this or other problems.
     entering a 4-digit pin code that is displayed on the UxPlay
     terminal. (This is optional, but sometimes required if the client is
     a corporately-owned and -managed device with MDM Mobile Device
-    Management.) Pairing occurs just once, is currently only recorded in
-    the client, and persists unless the UxPlay public key is changed. By
-    default (since v1.68) the public key is now generated using the
-    "Device ID", which is either the server's hardware MAC address, or
-    can be set with the -m option (most conveniently using the startup
-    option file). (Storage of a more securely-generated persistent key
-    as an OpenSSL "pem" file is still available with the -key option).
-    For use of uxplay in a more public environment, a list of
-    previously-registered clients can (since v1.68) be
-    optionally-maintained using the -reg option: without this option,
-    returning clients claiming to be registered are just trusted and not
-    checked.
+    Management.) Pairing occurs just once, is currently only recorded by
+    the client unless the -reg option is used, and persists until the
+    UxPlay public key is changed. By default (since v1.68) the public
+    key is now generated using the "Device ID", which is either the
+    server's hardware MAC address, or can be set with the -m option
+    (most conveniently using the startup option file). (Storage of a
+    more securely-generated persistent key as an OpenSSL "pem" file is
+    still available with the -key option). For use of uxplay in a more
+    public environment, a list of previously-registered clients can
+    (since v1.68) be optionally-maintained using the -reg option:
+    without this option, returning clients claiming to be registered are
+    just trusted and not checked.
 
 -   By default, UxPlay is locked to its current client until that client
     drops the connection; since UxPlay-1.58, the option `-nohold`