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/kernel/doc/src/error_logger.xml | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
(limited to 'lib/kernel/doc/src/error_logger.xml')
diff --git a/lib/kernel/doc/src/error_logger.xml b/lib/kernel/doc/src/error_logger.xml
index a8273e59e2..814e8eac46 100644
--- a/lib/kernel/doc/src/error_logger.xml
+++ b/lib/kernel/doc/src/error_logger.xml
@@ -33,7 +33,7 @@
The Erlang error logger is an event manager (see
OTP Design Principles and
- stdlib:gen_event(3)),
+ gen_event(3)),
registered as error_logger. Errors, warnings, and info events
are sent to the error logger from the Erlang runtime system and
the different Erlang/OTP applications. The events are, by default,
@@ -44,12 +44,12 @@
executing.
Initially, error_logger has only a primitive event
handler, which buffers and prints the raw event messages. During
- system startup, the Kernel application replaces this with a
+ system startup, the Kernel application replaces this with a
standard event handler, by default one that writes
- nicely formatted output to the terminal. Kernel can also be
+ nicely formatted output to the terminal. Kernel can also be
configured so that events are logged to a file instead, or not logged at all,
see kernel(6).
-
Also the SASL application, if started, adds its own event
+
Also the SASL application, if started, adds its own event
handler, which by default writes supervisor, crash, and progress
reports to the terminal. See
sasl(6).
@@ -58,9 +58,9 @@
User-defined event handlers can be added to handle application-specific
events, see
add_report_handler/1,2.
- Also, a useful event handler is provided in STDLIB for multi-file
+ Also, a useful event handler is provided in STDLIB for multi-file
logging of events, see
- stdlib:log_mf_h(3).
+ log_mf_h(3).
Warning events were introduced in Erlang/OTP R9C and are enabled
by default as from Erlang/OTP 18.0. To retain backwards compatibility
with existing user-defined event handlers, the warning events can be
@@ -82,7 +82,7 @@
Adds a new event handler to the error logger. The event
handler must be implemented as a gen_event callback
module, see
- stdlib:gen_event(3).
+ gen_event(3).
Handler is typically the name of the callback module
and Args is an optional term (defaults to []) passed
to the initialization callback function Handler:init/1.
@@ -97,7 +97,7 @@
Deletes an event handler from the error logger by calling
gen_event:delete_handler(error_logger, Handler, []),
- see stdlib:gen_event(3).
+ see gen_event(3).
@@ -110,7 +110,7 @@
The Format and Data arguments
are the same as the arguments of
io:format/2
- in STDLIB.
+ in STDLIB.
The event is handled by the standard event handler.
Example:
@@ -171,7 +171,7 @@ ok
The Format and Data arguments
are the same as the arguments of
io:format/2
- in STDLIB. The event is handled by the standard event handler.
+ in STDLIB. The event is handled by the standard event handler.
Example:
1> error_logger:info_msg("Something happened in ~p~n", [a_module]).
@@ -235,7 +235,7 @@ ok
Enables or disables printout of standard events to a file.
This is done by adding or deleting the standard event handler
for output to file. Thus, calling this function overrides
- the value of the Kernelerror_logger configuration
+ the value of the Kernel error_logger configuration
parameter.
Enabling file logging can be used together with calling
tty(false), to have a silent system where
@@ -274,7 +274,7 @@ ok
to the terminal.
This is done by adding or deleting the standard event handler
for output to the terminal. Thus, calling this function overrides
- the value of the Kernelerror_logger configuration parameter.
+ the value of the Kernel error_logger configuration parameter.
@@ -323,7 +323,7 @@ ok
The Format and Data arguments
are the same as the arguments of
io:format/2
- in STDLIB.
+ in STDLIB.
The event is handled by the standard event handler. It is tagged
as an error, warning, or info, see
warning_map/0.
@@ -416,8 +416,8 @@ ok
See Also
-