doc: Correct errors introduced by Editorial changes

Fix some older errors as well.

12 files changed, 51 insertions, 51 deletions

diff --git a/lib/sasl/doc/src/alarm_handler.xml b/lib/sasl/doc/src/alarm_handler.xml
index 8550a88b28..4160757164 100644
--- a/lib/sasl/doc/src/alarm_handler.xml
+++ b/lib/sasl/doc/src/alarm_handler.xml
@@ -54,7 +54,7 @@
       format is defined by the user. For example, an event handler
       for SNMP can be defined, together with an alarm Management
       Information Base (MIB).</p>
-    <p>The alarm handler is part of the <c>SASL</c> application.</p>
+    <p>The alarm handler is part of the SASL application.</p>
     <p>When writing new event handlers for the alarm handler, the
       following events must be handled:</p>
     <taglist>
@@ -76,7 +76,7 @@
       {NewHandler, Args})</c>. <c>NewHandler:init({Args, {alarm_handler,
       Alarms}})</c> is called. For more details, see
       <seealso marker="stdlib:gen_event"><c>gen_event(3)</c></seealso>
-      in <c>STDLIB</c>.</p>
+      in STDLIB.</p>
   </description>
 
   <funcs>
diff --git a/lib/sasl/doc/src/appup.xml b/lib/sasl/doc/src/appup.xml
index 6fbdcb9f5b..a43a966dcb 100644
--- a/lib/sasl/doc/src/appup.xml
+++ b/lib/sasl/doc/src/appup.xml
@@ -362,12 +362,12 @@ point_of_no_return</pre>
       system is restarted.</p>
     <pre>
 restart_new_emulator</pre>
-    <p>This instruction is used when the application <c>ERTS</c>,
-      <c>Kernel</c>, <c>STDLIB</c>, or <c>SASL</c> is
+    <p>This instruction is used when the application ERTS,
+      Kernel, STDLIB, or SASL is
       upgraded. It shuts down the current emulator and starts a new
       one. All processes are terminated gracefully, and the new
-      version of <c>ERTS</c>, <c>Kernel</c>, <c>STDLIB</c>, and
-      <c>SASL</c> are used when the emulator restarts.
+      version of ERTS, Kernel, STDLIB, and
+      SASL are used when the emulator restarts.
       Only one <c>restart_new_emulator</c> instruction is allowed
       in the <c>relup</c> file, and it must be placed first.
       <seealso marker="systools#make_relup/3"><c>systools:make_relup/3,4</c></seealso>
@@ -385,7 +385,7 @@ restart_new_emulator</pre>
     <warning>
       <p>As stated earlier, instruction <c>restart_new_emulator</c>
         causes the emulator to be restarted with new versions of
-        <c>ERTS</c>, <c>Kernel</c>, <c>STDLIB</c>, and <c>SASL</c>.
+        ERTS>, Kernel, STDLIB, and SASL.
         However, all other applications do at startup run their old
         versions in this new emulator. This is usually no problem,
         but every now and then incompatible changes occur to the
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 @@
     <rev>B</rev>
     <file>error_logging.xml</file>
     </header>
-  <p>The <c>SASL</c> application introduces three types of reports:</p>
+  <p>The SASL application introduces three types of reports:</p>
   <list type="bulleted">
     <item>Supervisor report</item>
     <item>Progress report</item>
     <item>Crash report</item>
   </list>
-  <p>When the <c>SASL</c> application is started, it adds a handler that 
+  <p>When the SASL application is started, it adds a handler that
     formats and writes these reports, as specified in the configuration
-    parameters for <c>SASL</c>, that is, the environment variables
-    in the <c>SASL</c> application specification, which is found in the 
-    <c>.app</c> file of <c>SASL</c>. For details, see the
+    parameters for SASL, that is, the environment variables
+    in the SASL application specification, which is found in the
+    <c>.app</c> file of SASL. For details, see the
     <seealso marker="sasl_app"><c>sasl(6)</c></seealso> application in the
     Reference Manual and the <seealso marker="kernel:app"><c>app(4)</c></seealso>
-    file in the <c>Kernel</c> Reference Manual.</p>
+    file in the Kernel Reference Manual.</p>
 
   <section>
     <title>Supervisor Report</title>
@@ -180,14 +180,14 @@
     <p>The report browser is used to browse and format error reports
       written by the error logger handler 
       <seealso marker="stdlib:log_mf_h"><c>log_mf_h</c></seealso> 
-      defined in <c>STDLIB</c>.</p>
+      defined in STDLIB.</p>
     <p>The <c>log_mf_h</c> handler writes all reports to a
       report logging directory, which is specified when
-      configuring the <c>SASL</c> application.</p>
+      configuring the SASL application.</p>
     <p>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 <c>SASL</c>
+      is specified, the browser reads reports from the SASL
       <c>error_logger_mf_dir</c>.</p>
 
     <section>
diff --git a/lib/sasl/doc/src/notes.xml b/lib/sasl/doc/src/notes.xml
index dae73f8b23..bd713af932 100644
--- a/lib/sasl/doc/src/notes.xml
+++ b/lib/sasl/doc/src/notes.xml
@@ -824,7 +824,7 @@
       <list>
         <item>
 	    <p>Use an infinity timeout in all calls to
-	    <c>gen_server:call()</c> in the <c>sasl</c>
+	    <c>gen_server:call()</c> in the SASL
 	    application.</p>
           <p>
 	    Own Id: OTP-8506 Aux Id: seq11509 </p>
diff --git a/lib/sasl/doc/src/part.xml b/lib/sasl/doc/src/part.xml
index f531ed2dea..659710487e 100644
--- a/lib/sasl/doc/src/part.xml
+++ b/lib/sasl/doc/src/part.xml
@@ -30,7 +30,7 @@
     <file>part.xml</file>
   </header>
   <description>
-    <p>The System Architecture Support Libraries <c>SASL</c> application
+    <p>The System Architecture Support Libraries SASL application
       provides support for alarm handling, release handling, and
       related functions.</p>
   </description>
diff --git a/lib/sasl/doc/src/rb.xml b/lib/sasl/doc/src/rb.xml
index 1ce19046eb..d5df4fd345 100644
--- a/lib/sasl/doc/src/rb.xml
+++ b/lib/sasl/doc/src/rb.xml
@@ -38,7 +38,7 @@
     <p>The Report Browser (RB) tool is used to browse and
       format error reports written by the error logger handler
       <seealso marker="stdlib:log_mf_h"><c>log_mf_h</c></seealso>
-      in <c>STDLIB</c>.</p>
+      in STDLIB.</p>
   </description>
 
   <funcs>
@@ -62,7 +62,7 @@
           reports that match that filter.</p>
         <p>The reports are matched using the
           <seealso marker="stdlib:proplists"><c>proplists</c></seealso>
-          module in <c>STDLIB</c>. The report must be a proplist
+          module in STDLIB. The report must be a proplist
           to be matched against any of the filters.</p>
         <p>If the filter has the form <c>{Key, RegExp, re}</c>, the
           report must contain an element with key equal to <c>Key</c> and
@@ -102,7 +102,7 @@
         </list>
         <p>For a definition of valid regular expressions and options, see
           the <seealso marker="stdlib:re"><c>re</c></seealso> module in
-          <c>STDLIB</c> and in particular function <c>re:run/3</c>.</p>
+          STDLIB and in particular function <c>re:run/3</c>.</p>
 	  <p>For details about data type <c>mp()</c>, see 
 	<seealso marker="stdlib:re#type-mp"><c>re:mp()</c></seealso>.</p>
       </desc>
diff --git a/lib/sasl/doc/src/ref_man.xml b/lib/sasl/doc/src/ref_man.xml
index 42045df5ec..78cf1eb26e 100644
--- a/lib/sasl/doc/src/ref_man.xml
+++ b/lib/sasl/doc/src/ref_man.xml
@@ -30,7 +30,7 @@
     <file>application.xml</file>
   </header>
   <description>
-    <p>The <c>SASL</c> application provides support for alarm handling,
+    <p>The SASL application provides support for alarm handling,
       release handling, and related functions.</p>
   </description>
   <xi:include href="sasl_app.xml"/>
diff --git a/lib/sasl/doc/src/rel.xml b/lib/sasl/doc/src/rel.xml
index d6558c06b4..9356b2cd47 100644
--- a/lib/sasl/doc/src/rel.xml
+++ b/lib/sasl/doc/src/rel.xml
@@ -59,7 +59,7 @@
       <tag><c>Vsn = string()</c></tag>
         <item><p>Release version.</p></item>
       <tag><c>EVsn = string()</c></tag>
-        <item><p><c>ERTS</c> version the release is intended for.</p></item>
+        <item><p>ERTS version the release is intended for.</p></item>
       <tag><c>Application = atom()</c></tag>
         <item><p>Name of an application included in the release.</p></item>
       <tag><c>AppVsn = string()</c></tag>
@@ -82,8 +82,8 @@
           to the same value as in the application resource file.</p></item>
     </taglist>
     <note>
-      <p>The list of applications must contain the <c>Kernel</c> and
-        <c>STDLIB</c> applications.</p>
+      <p>The list of applications must contain the Kernel and
+        STDLIB applications.</p>
     </note>
   </section>
 
diff --git a/lib/sasl/doc/src/release_handler.xml b/lib/sasl/doc/src/release_handler.xml
index bcbc5f5339..8f073807fb 100644
--- a/lib/sasl/doc/src/release_handler.xml
+++ b/lib/sasl/doc/src/release_handler.xml
@@ -31,7 +31,7 @@
   <module>release_handler</module>
   <modulesummary>Unpacking and Installation of Release Packages</modulesummary>
   <description>
-    <p>The <em>release handler</em> process belongs to the <c>SASL</c>
+    <p>The <em>release handler</em> process belongs to the SASL
       application, which is responsible for <em>release handling</em>,
       that is, unpacking, installation, and removal of release packages.</p>
     <p>An introduction to release handling and an example is provided in
@@ -44,7 +44,7 @@
       directory of the previous version of the release, where
       <c>$ROOT</c> is the installation root directory,
       <seealso marker="kernel:code#root_dir/0"><c>code:root_dir()</c></seealso>.
-      Another <c>releases</c> directory can be specified using the <c>SASL</c>
+      Another <c>releases</c> directory can be specified using the SASL
       configuration parameter <c>releases_dir</c> or the OS environment
       variable <c>RELDIR</c>. The release handler must have write access
       to this directory to install the new release.
@@ -56,7 +56,7 @@
       <item>A boot script, <c>Name.boot</c></item>
     </list>
     <p>The <c>.rel</c> file contains information about the release: its name,
-      version, and which <c>ERTS</c> and application versions it uses.</p>
+      version, and which ERTS and application versions it uses.</p>
     <p>A release package can also contain:</p>
     <list type="bulleted">
       <item>A release upgrade file, <c>relup</c></item>
@@ -115,7 +115,7 @@
       <em>System Documentation</em>. In this case, the system
       configuration file <c>sys.config</c> is mandatory.</p>
     <p>The installation of a new release can restart the system. Which
-      program to use is specified by the <c>SASL</c> configuration
+      program to use is specified by the SASL configuration
       parameter <c>start_prg</c>, which defaults
       to <c>$ROOT/bin/start</c>.</p>
     <p>The emulator restart on Windows NT expects that the system is
@@ -132,7 +132,7 @@
       is made permanent.</p>
     <p>The release handler at a node running on a diskless machine,
       or with a read-only file system, must be configured accordingly
-      using the following <c>SASL</c> configuration parameters (for
+      using the following SASL configuration parameters (for
       details, see <seealso marker="sasl_app">sasl(6)</seealso>):</p>
     <taglist>
       <tag><c>masters</c></tag>
@@ -287,7 +287,7 @@
 	  returned, the emulator is restarted
 	  before the upgrade instructions are executed. This
 	  occurs if the emulator or any of the applications
-          <c>Kernel</c>, <c>STDLIB</c>, or <c>SASL</c>
+          Kernel, STDLIB, or SASL
 	  are updated. The new emulator version
 	  and these core applications execute after the restart.
 	  For all other applications the old versions are
@@ -310,13 +310,13 @@
           <tag><c>code_change_timeout</c></tag>
             <item><p>Defines the time-out
             for all calls to 
-	    <seealso marker="stdlib:sys#change_code/4"><c>stdlib:sys:change_code</c></seealso>. 
+	    <seealso marker="stdlib:sys#change_code/4"><c>sys:change_code</c></seealso>.
 	    If no value is specified or <c>default</c> is specified, the 
 	    default value defined in <c>sys</c> is used.</p></item>
           <tag><c>suspend_timeout</c></tag>
             <item><p>Defines the time-out for 
             all calls to 
-	    <seealso marker="stdlib:sys#suspend/1"><c>stdlib:sys:suspend</c></seealso>. 
+	    <seealso marker="stdlib:sys#suspend/1"><c>sys:suspend</c></seealso>.
 	    If no value is specified, the values defined by the <c>Timeout</c> 
 	    parameter of the <c>upgrade</c> or <c>suspend</c> instructions are used.
             If <c>default</c> is specified, the default value defined in
@@ -342,7 +342,7 @@ release_handler:set_unpacked(RelFile, [{myapp,"1.0","/home/user"},...]).
 => {ok,NewVsn}</code>
             <p>If <c>NewVsn</c> is installed with option
               <c>{update_paths,true}</c>, then
-              <seealso marker="kernel:code#lib_dir/1"><c>kernel:code:lib_dir(myapp)</c></seealso> 
+              <seealso marker="kernel:code#lib_dir/1"><c>code:lib_dir(myapp)</c></seealso>
 	      returns <c>/home/user/myapp-1.0</c>.</p></item>
         </taglist>
 	<note>
@@ -801,7 +801,7 @@ release_handler:set_unpacked(RelFile, [{myapp,"1.0","/home/user"},...]).
           is an atom named from the Posix error codes, such as
           <c>enoent</c>, <c>eacces</c>, or <c>eisdir</c>. See
           <seealso marker="kernel:file"><c>file(3)</c></seealso>
-          in <c>Kernel</c>.</p></item>
+          in Kernel.</p></item>
       <tag><c>Posix</c></tag>
         <item><p>Some file operation failed, as for the previous item in
           the list.</p></item>
diff --git a/lib/sasl/doc/src/sasl_app.xml b/lib/sasl/doc/src/sasl_app.xml
index 52f449c2a8..0576397f9b 100644
--- a/lib/sasl/doc/src/sasl_app.xml
+++ b/lib/sasl/doc/src/sasl_app.xml
@@ -31,17 +31,17 @@
     <app>sasl</app>
     <appsummary>The SASL application</appsummary>
     <description>
-    <p>The <c>SASL</c> application provides the following services:</p>
+    <p>The SASL application provides the following services:</p>
     <list type="bulleted">
       <item><c>alarm_handler</c></item>
       <item><c>rb</c></item>
       <item><c>release_handler</c></item>
       <item><c>systools</c></item>
     </list>
-    <p>The <c>SASL</c> application also includes <c>error_logger</c> event
-      handlers for formatting <c>SASL</c> error and crash reports.</p>
+    <p>The SASL application also includes <c>error_logger</c> event
+      handlers for formatting SASL error and crash reports.</p>
     <note>
-       <p>The <c>SASL</c> application in OTP has nothing to do with
+       <p>The SASL application in OTP has nothing to do with
           "Simple Authentication and Security Layer" (RFC 4422).</p>
     </note>
   </description>
@@ -49,7 +49,7 @@
   <section>
     <title>Error Logger Event Handlers</title>
     <p>The following error logger event handlers are used by
-      the <c>SASL</c> application.</p>
+      the SASL application.</p>
     <taglist>
       <tag><c>sasl_report_tty_h</c></tag>
       <item>
@@ -57,7 +57,7 @@
         reports</em>, and <em>progress reports</em> to <c>stdio</c>.
         This error logger event handler uses
 	<seealso marker="kernel:kernel_app#error_logger_format_depth">error_logger_format_depth</seealso>
-	in the <c>Kernel</c> application to limit how much detail is
+	in the Kernel application to limit how much detail is
         printed in crash and supervisor reports.</p>
       </item>
       <tag><c>sasl_report_file_h</c></tag>
@@ -66,7 +66,7 @@
         report</em>, and <em>progress report</em> to a single file.
         This error logger event handler uses
 	<seealso marker="kernel:kernel_app#error_logger_format_depth">error_logger_format_depth</seealso>
-	in the <c>Kernel</c> application to limit the details
+	in the Kernel application to limit the details
         printed in crash and supervisor reports.</p>
       </item>
       <tag><c>log_mf_h</c></tag>
@@ -75,9 +75,9 @@
           error logger to disk. Multiple files and log rotation are
           used. For efficiency reasons, each event is written as a
           binary. For more information about this handler,
-          see <seealso marker="stdlib:log_mf_h">the <c>STDLIB</c> Reference
+          see <seealso marker="stdlib:log_mf_h">the STDLIB Reference
           Manual</seealso>.</p>
-        <p>To activate this event handler, three <c>SASL</c>
+        <p>To activate this event handler, three SASL
           configuration parameters must be set,
           <c>error_logger_mf_dir</c>, <c>error_logger_mf_maxbytes</c>,
           and <c>error_logger_mf_maxfiles</c>. The next section provides
@@ -88,9 +88,9 @@
 
   <section>
     <title>Configuration</title>
-    <p>The following configuration parameters are defined for the <c>SASL</c>
+    <p>The following configuration parameters are defined for the SASL
       application. For more information about configuration parameters, see
-      <seealso marker="kernel:app"><c>app(4)</c></seealso> in <c>Kernel</c>.</p>
+      <seealso marker="kernel:app"><c>app(4)</c></seealso> in Kernel.</p>
     <p>All configuration parameters are optional.</p>
     <taglist>
       <tag><c><![CDATA[sasl_error_logger = Value ]]></c></tag>
@@ -112,7 +112,7 @@
             Use <c>[append]</c> to have the <c>FileName</c> open in append mode.
             <c>FileName</c> is a string.</p></item>
           <tag><c>false</c></tag>
-          <item><p>No <c>SASL</c> error logger handler is installed.</p></item>
+          <item><p>No SASL error logger handler is installed.</p></item>
         </taglist>
       </item>
       <tag><c><![CDATA[errlog_type = error | progress | all ]]></c></tag>
diff --git a/lib/sasl/doc/src/sasl_intro.xml b/lib/sasl/doc/src/sasl_intro.xml
index b71dafb192..f74a7c1db8 100644
--- a/lib/sasl/doc/src/sasl_intro.xml
+++ b/lib/sasl/doc/src/sasl_intro.xml
@@ -32,7 +32,7 @@
 
   <section>
     <title>Scope</title>
-    <p>The <c>SASL</c> application provides support for:</p>
+    <p>The SASL application provides support for:</p>
     <list type="bulleted">
       <item>Error logging</item>
       <item>Alarm handling</item>
diff --git a/lib/sasl/doc/src/systools.xml b/lib/sasl/doc/src/systools.xml
index 7446762de4..fa503fa573 100644
--- a/lib/sasl/doc/src/systools.xml
+++ b/lib/sasl/doc/src/systools.xml
@@ -85,7 +85,7 @@
           </item>
           <item>
             <p>If the emulator needs to be restarted after upgrading or
-              downgrading, that is, if the <c>ERTS</c> version differs
+              downgrading, that is, if the ERTS version differs
               between <c>Name.rel</c> and <c>Name2.rel</c></p>
           </item>
         </list>
@@ -201,10 +201,10 @@
           between the applications. Where there are no dependencies,
           the order in the <c>.rel</c> file is kept.</p>
         <p>The function fails if the mandatory
-          applications <c>Kernel</c> and <c>STDLIB</c> are not
+          applications Kernel and STDLIB are not
           included in the <c>.rel</c> file and have start
           type <c>permanent</c> (which is default).</p>
-        <p>If <c>SASL</c> is not included as an application in
+        <p>If SASL is not included as an application in
           the <c>.rel</c> file, a warning is issued because such a
           release cannot be used in an upgrade. To turn off this
           warning, add option <c>no_warn_sasl</c>.</p>