diff --git a/README.turnserver b/README.turnserver
index 72da1ce6..1074416e 100644
--- a/README.turnserver
+++ b/README.turnserver
@@ -592,14 +592,15 @@ limited time by an application that has to create a TURN server connection.
 The "classic" long-term credentials mechanism (LTCM) is described here:
 
 http://tools.ietf.org/html/rfc5389#section-10.2
+
 http://tools.ietf.org/html/rfc5389#section-15.4
 
-For authentication, each user must know two things: the username and the 
-password. Optionally, the user must supply the ORIGIN value, so that the 
+For authentication, each user must know two things: the username and the
+password. Optionally, the user must supply the ORIGIN value, so that the
 server can figure out the realm to be used for the user. The nonce and 
 the realm values are supplied by the TURN server. But LTCM is not saying 
-anything about the nature and about the persistence 
-of the username and of the password; and this is used by the REST API.
+anything about the nature and about the persistence of the username and 
+of the password; and this is used by the REST API.
 
 In the TURN REST API, there is no persistent passwords for users. A user has 
 just the username. The password is always temporary, and it is generated by 
diff --git a/man/man1/turnserver.1 b/man/man1/turnserver.1
index d188187d..9a7d19a0 100644
--- a/man/man1/turnserver.1
+++ b/man/man1/turnserver.1
@@ -827,14 +827,15 @@ limited time by an application that has to create a TURN server connection.
 The "classic" long\-term credentials mechanism (LTCM) is described here:
 .PP
 http://tools.ietf.org/html/rfc5389#section\-10.2
+.PP
 http://tools.ietf.org/html/rfc5389#section\-15.4
 .PP
-For authentication, each user must know two things: the username and the 
-password. Optionally, the user must supply the ORIGIN value, so that the 
+For authentication, each user must know two things: the username and the
+password. Optionally, the user must supply the ORIGIN value, so that the
 server can figure out the realm to be used for the user. The nonce and 
 the realm values are supplied by the TURN server. But LTCM is not saying 
-anything about the nature and about the persistence 
-of the username and of the password; and this is used by the REST API.
+anything about the nature and about the persistence of the username and 
+of the password; and this is used by the REST API.
 .PP
 In the TURN REST API, there is no persistent passwords for users. A user has 
 just the username. The password is always temporary, and it is generated by