From 53539ee751da408029c9dfae80384fdec6c7a552 Mon Sep 17 00:00:00 2001
From: Siri Hansen <siri@erlang.org>
Date: Tue, 22 May 2018 13:22:55 +0200
Subject: Update documentation of logger and error_logger

---
 system/doc/system_principles/error_logging.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'system/doc')

diff --git a/system/doc/system_principles/error_logging.xml b/system/doc/system_principles/error_logging.xml
index 2e28753c02..9d95ce8f3b 100644
--- a/system/doc/system_principles/error_logging.xml
+++ b/system/doc/system_principles/error_logging.xml
@@ -67,10 +67,10 @@ Error in process <0.27.0> with exit value: {{badmatch,[1,2,3]},[{m,f,1},{shell,e
       reports, crash reports and other error and information reports
       are by default logged through the log handler which is
       set up when the Kernel application is started.</p>
-    <p>Prior to OTP-21, supervisor, crash, and progress reports were
-      only logged when the SASL application was running. This
-      behaviour can, for backwards compatibility, be enabled by
-      setting the Kernel configuration
+    <p>Prior to Erlang/OTP 21.0, supervisor, crash, and progress
+      reports were only logged when the SASL application was
+      running. This behaviour can, for backwards compatibility, be
+      enabled by setting the Kernel configuration
       parameter <c>logger_sasl_compatible</c> to <c>true</c>. For more
       information, see
       <seealso marker="sasl:error_logging">SASL Error Logging</seealso>
-- 
cgit v1.2.3