Doc: Explain temp token validity

diff --git a/client/subauth.1.txt b/client/subauth.1.txt
index 23edea555f1a22908f44b6cc83a596f9c92066ba..6bb6604abad34a1a51c6d6e405c58687b40a21f3 100644 (file)
--- a/client/subauth.1.txt
+++ b/client/subauth.1.txt
@@ -46,10 +46,11 @@ not be available in all zones.
   to have it removed.
 
 * *Temporary token:* this is a randomly generated cryptographically signed string,
-  allowing access to the given user in the given zone for a limited time. This
+  allowing access to the given user in the given zone for a limited time. Temporary tokens
   can be useful for services which are used so scarcely that it does not make
   sense to remember permanent credentials of any kind. Use *subauth --temp-token*
-  to obtain a temporary token.
+  to obtain a temporary token. You can set how long will the token be valid
+  up to a limit configured by the administrator for the given zone.
 
 The sub-accounts are managed by the *subauthd*(8) daemon.
 The *subauth*(1) command is a front-end to this daemon, through which