From ad6e765bcd4f35a282ef00e38ed9129f3a5c1d83 Mon Sep 17 00:00:00 2001
From: Hans Bolinder
Date: Thu, 1 Sep 2016 14:32:27 +0200
Subject: doc: Correct errors introduced by Editorial changes
Fix some older errors as well.
---
lib/sasl/doc/src/error_logging.xml | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
(limited to 'lib/sasl/doc/src/error_logging.xml')
diff --git a/lib/sasl/doc/src/error_logging.xml b/lib/sasl/doc/src/error_logging.xml
index 8464a41ff9..4b2c960bbb 100644
--- a/lib/sasl/doc/src/error_logging.xml
+++ b/lib/sasl/doc/src/error_logging.xml
@@ -32,20 +32,20 @@
B
error_logging.xml
- The SASL application introduces three types of reports:
+ The SASL application introduces three types of reports:
- Supervisor report
- Progress report
- Crash report
- When the SASL application is started, it adds a handler that
+
When the SASL application is started, it adds a handler that
formats and writes these reports, as specified in the configuration
- parameters for SASL, that is, the environment variables
- in the SASL application specification, which is found in the
- .app file of SASL. For details, see the
+ parameters for SASL, that is, the environment variables
+ in the SASL application specification, which is found in the
+ .app file of SASL. For details, see the
sasl(6) application in the
Reference Manual and the app(4)
- file in the Kernel Reference Manual.
+ file in the Kernel Reference Manual.
Supervisor Report
@@ -180,14 +180,14 @@
The report browser is used to browse and format error reports
written by the error logger handler
log_mf_h
- defined in STDLIB.
+ defined in STDLIB.
The log_mf_h handler writes all reports to a
report logging directory, which is specified when
- configuring the SASL application.
+ configuring the SASL application.
If the report browser is
used offline, the reports can be copied to another directory
specified when starting the browser. If no such directory
- is specified, the browser reads reports from the SASL
+ is specified, the browser reads reports from the SASL
error_logger_mf_dir.