fixup! Reflect the changes in documentation

doc/lightningd-config.5

@@ -312,12 +312,7 @@ and this will be used to configure a static Tor hidden service for port
 first IPv4 or IPv6 address we bind to and is by default unique to
 your nodes id. You can add the text ':torblob:' followed by up to
 64 Bytes of text to generate from this text a v3 onion service
-address unique to the first 32 bytes of this text. The later 32 bytes
-will determine mainly your Tor onions inner secret but will not
-change the text of the base32 encoded tor address.
-Those remaining 32 bytes should and can but must not be randomly selected.
-at startup. The text of the onion address is determined by
-the first 32 bytes of the blob.
+address text unique to the first 32 Byte of this text.
 You can also use an postfix '/torport=TORPORT' to select the external
 tor binding. The result is that over tor your node is accessible by a port
 defined by you and possible different from your local node port assignment

doc/lightningd-config.5.md

@@ -269,12 +269,7 @@ Set an IP address (v4 or v6) or automatic Tor address to listen on and
     first IPv4 or IPv6 address we bind to and is by default unique to
     your nodes id. You can add the text ':torblob:' followed by up to
     64 Bytes of text to generate from this text a v3 onion service
-    address unique to the first 32 bytes of this text. The later 32 bytes
-    will determine mainly your Tor onions inner secret but will not
-    change the text of the base32 encoded tor address.
-    Those remaining 32 bytes should and can but must not be randomly selected.
-    at startup. The text of the onion address is determined by
-    the first 32 bytes of the blob.
+    address text unique to the first 32 Byte of this text.
     You can also use an postfix '/torport=TORPORT' to select the external
     tor binding. The result is that over tor your node is accessible by a port
     defined by you and possible different from your local node port assignment