doc: Correct errors introduced by Editorial changes

Fix some older errors as well.

3 files changed, 13 insertions, 13 deletions

diff --git a/system/doc/embedded/embedded_nt.xml b/system/doc/embedded/embedded_nt.xml
index a1a4b90f3c..8e05100585 100644
--- a/system/doc/embedded/embedded_nt.xml
+++ b/system/doc/embedded/embedded_nt.xml
@@ -62,7 +62,7 @@
       <p>For Windows NT running on standard PCs with ISA and/or PCI bus,
         an extension card with a hardware watchdog can be installed.</p>
       <p>For more information, see the <c>heart(3)</c> manual page in
-        <c>kernel</c>.</p>
+        Kernel.</p>
     </section>
   </section>
 
@@ -72,7 +72,7 @@
       to install the Erlang process as a Windows system service.
       This service can start after Windows NT has booted.</p>
     <p>For more information, see the <c>erlsrv</c> manual page
-      in <c>erts</c>.</p>
+      in ERTS.</p>
   </section>
 </chapter>
 
diff --git a/system/doc/embedded/embedded_solaris.xml b/system/doc/embedded/embedded_solaris.xml
index f8febcc546..eaa334fb39 100644
--- a/system/doc/embedded/embedded_solaris.xml
+++ b/system/doc/embedded/embedded_solaris.xml
@@ -190,7 +190,7 @@ esac</pre>
         the onboard hardware watchdog can be activated,
 	provided a VME bus driver is added to the operating system
         (see also Installation Problems).</p>
-      <p>See also the <c>heart(3)</c> manual page in <c>kernel</c>.</p>
+      <p>See also the <c>heart(3)</c> manual page in Kernel.</p>
     </section>
 
     <section>
@@ -206,7 +206,7 @@ esac</pre>
       <pre>
         chown 0 /usr/sbin/reboot
         chmod 4755 /usr/sbin/reboot</pre>
-      <p>See also the <c>heart(3)</c> manual page in <c>kernel</c>.</p>
+      <p>See also the <c>heart(3)</c> manual page in Kernel.</p>
     </section>
 
     <section>
@@ -413,8 +413,8 @@ chown root mod_syslog]]></code>
     <section>
       <title>Related Documents</title>
       <p>See the <c>os_mon(3)</c> application,
-      the <c>application(3)</c> manual page in <c>kernel</c>,
-      and the <c>erl(1)</c> manual page in <c>erts</c>.</p>
+      the <c>application(3)</c> manual page in Kernel,
+      and the <c>erl(1)</c> manual page in ERTS.</p>
     </section>
   </section>
 
@@ -474,7 +474,7 @@ chown root mod_syslog]]></code>
         default, it must be called <c>start</c> and reside in
         <c><![CDATA[<ERL_INSTALL_DIR>/bin]]></c>. Another start
 	program can be used, by using configuration parameter
-	<c>start_prg</c> in application <c>sasl</c>.</p>
+	<c>start_prg</c> in application SASL.</p>
       <p>The start program must call <c>run_erl</c> as shown below.
         It must also take an optional parameter, which defaults to
         <c><![CDATA[<ERL_INSTALL_DIR>/releases/start_erl.data]]></c>.</p>
@@ -484,7 +484,7 @@ chown root mod_syslog]]></code>
       <p>The <c><![CDATA[<RELDIR>]]></c> directory is where new release
         packets are installed, and where the release handler keeps
 	information about releases. For more information, see the
-	<c>release_handler(3)</c> manual page in <c>sasl</c>.</p>
+	<c>release_handler(3)</c> manual page in SASL.</p>
       <p>The following script illustrates the default behaviour of the
         program:</p>
       <code type="none"><![CDATA[
@@ -624,7 +624,7 @@ export RELDIR
 exec $BINDIR/erlexec -boot $RELDIR/$VSN/start -config $RELDIR/$VSN/sys $*</code>
 
       <p>If a diskless and/or read-only client node with the
-        <c>sasl</c> configuration parameter <c>static_emulator</c> set
+        SASL configuration parameter <c>static_emulator</c> set
         to <c>true</c> is about to start, the <c>-boot</c> and
         <c>-config</c> flags must be changed.</p>
 	<p>As such a client cannot
diff --git a/system/doc/embedded/starting.xml b/system/doc/embedded/starting.xml
index 720383e8ac..11bf9b412a 100644
--- a/system/doc/embedded/starting.xml
+++ b/system/doc/embedded/starting.xml
@@ -69,7 +69,7 @@
         default, it must be called <c>start</c> and reside in
         <c><![CDATA[<ERL_INSTALL_DIR>/bin]]></c>.  Another start program can be
         used, by using the configuration parameter <c>start_prg</c> in
-        the application <c>sasl</c>.</p>
+        application SASL.</p>
       <p>The start program must call <c>run_erl</c> as shown below.
         It must also take an optional parameter which defaults to
         <c><![CDATA[<ERL_INSTALL_DIR>/bin/start_erl.data]]></c>.
@@ -80,8 +80,8 @@
         </p>
       <p>The <c><![CDATA[<RELDIR>]]></c> directory is where new release packets
         are installed, and where the release handler keeps information
-        about releases.  See <c>release_handler(3)</c> in the
-        application <c>sasl</c> for further information.
+        about releases.  See <c>release_handler(3)</c> in
+        application SASL for further information.
         </p>
       <p>The following script illustrates the default behaviour of the
         program.
@@ -228,7 +228,7 @@ export PROGNAME
 export RELDIR
 
 exec $BINDIR/erlexec -boot $RELDIR/$VSN/start -config $RELDIR/$VSN/sys $*      </code>
-      <p>If a diskless and/or read-only client node with the <c>sasl</c>
+      <p>If a diskless and/or read-only client node with the SASL
         configuration parameter <c>static_emulator</c> set to <c>true</c>
         is about to start the <c>-boot</c> and <c>-config</c> flags must be
         changed. As such a client can not read a new <c>start_erl.data</c>