From ca1bf7a9d915a973203aa046bb9f921c11681ee0 Mon Sep 17 00:00:00 2001
From: Siri Hansen <siri@erlang.org>
Date: Mon, 21 May 2018 16:52:23 +0200
Subject: Change handler id for sasl handler from sasl_h to sasl

---
 lib/kernel/doc/src/kernel_app.xml     | 2 +-
 lib/kernel/doc/src/logger_chapter.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

(limited to 'lib/kernel/doc')

diff --git a/lib/kernel/doc/src/kernel_app.xml b/lib/kernel/doc/src/kernel_app.xml
index 5bc423afb6..a9292e7660 100644
--- a/lib/kernel/doc/src/kernel_app.xml
+++ b/lib/kernel/doc/src/kernel_app.xml
@@ -192,7 +192,7 @@
 	  will not log any progress-, crash-, or supervisor reports.
           If the SASL application is started,
 	  these log events will be sent to a second handler instance
-	  named <c>sasl_h</c>, according to values of the SASL
+	  named <c>sasl</c>, according to values of the SASL
 	  configuration parameter <c>sasl_error_logger</c>
 	  and <c>sasl_errlog_type</c>, see
 	  <seealso marker="sasl:sasl_app#deprecated_error_logger_config">sasl(6)
diff --git a/lib/kernel/doc/src/logger_chapter.xml b/lib/kernel/doc/src/logger_chapter.xml
index 34c65be47a..1195808160 100644
--- a/lib/kernel/doc/src/logger_chapter.xml
+++ b/lib/kernel/doc/src/logger_chapter.xml
@@ -630,7 +630,7 @@
 	  configuration parameters</seealso> can then be used as
 	  before, and the SASL reports will only be printed if the
 	  SASL application is running, through a second log handler
-	  named <c>sasl_h</c>.</p>
+	  named <c>sasl</c>.</p>
 	<p>All SASL reports have a metadata
 	  field <c>domain=>[beam,erlang,otp,sasl]</c>, which can be
 	  used, for example, by filters to stop or allow the
-- 
cgit v1.2.3