Merge bug19200 into bug19193

1 files changed, 8 insertions, 5 deletions

diff --git a/docs/rabbitmqctl.pod b/docs/rabbitmqctl.pod
index 927fd8af40..b34cbca754 100644
--- a/docs/rabbitmqctl.pod
+++ b/docs/rabbitmqctl.pod
@@ -69,10 +69,13 @@ force_reset
 rotate_logs [suffix]
     instruct the RabbitMQ node to rotate the log files. The RabbitMQ
     broker will attempt to append the current contents of the log file
-    to the file with name composed of the original name and the suffix.
-    It will create a new file if such a file does not already exist.
-    When no I<suffix> is specified, the log file is simply reopened;
-    no rotation takes place. 
+    to the file with the name composed of the original name and the
+    suffix. It will create a new file if such a file does not already
+    exist. When no I<suffix> is specified, the empty log file is
+    simply created at the original location; no rotation takes place.
+    When an error occurs while appending the contents of the old log
+    file, the operation behaves in the same way as if no I<suffix> was
+    specified.
     This command might be helpful when you are e.g. writing your own
     logrotate script and you do not want to restart the RabbitMQ node.
     
@@ -129,7 +132,7 @@ default Erlang node:
 
     rabbitmqctl map_user_vhost foo test
     
-Append current logs' content to the files with ".1" suffix and reopen
+Append the current logs' content to the files with ".1" suffix and reopen
 them:
 
     rabbitmqctl rotate_logs .1