Open files and
diff --git a/system/doc/efficiency_guide/profiling.xml b/system/doc/efficiency_guide/profiling.xml
index 1f3d503170..bf50a03fa6 100644
--- a/system/doc/efficiency_guide/profiling.xml
+++ b/system/doc/efficiency_guide/profiling.xml
@@ -128,7 +128,7 @@
performance impact. Using fprof is just a matter of
calling a few library functions, see the
fprof manual page in
- tools .fprof was introduced in R8.
+ Tools .fprof was introduced in R8.
@@ -138,7 +138,7 @@
and in which function calls this time has been spent. Time is
shown as percentage of total time and absolute time. For more
information, see the eprof
- manual page in tools.
+ manual page in Tools.
@@ -152,7 +152,7 @@
optimization. Using cover is just a matter of calling a
few library functions, see the
cover manual page in
- tools.
+ Tools.
@@ -165,7 +165,7 @@
any modules to profile (compared with cover).
For more information, see the
cprof manual page in
- tools.
+ Tools.
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 @@
For Windows NT running on standard PCs with ISA and/or PCI bus,
an extension card with a hardware watchdog can be installed.
For more information, see the heart(3) manual page in
- kernel.
+ Kernel.
@@ -72,7 +72,7 @@
to install the Erlang process as a Windows system service.
This service can start after Windows NT has booted.
For more information, see the erlsrv manual page
- in erts.
+ in ERTS.
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
the onboard hardware watchdog can be activated,
provided a VME bus driver is added to the operating system
(see also Installation Problems).
- See also the heart(3) manual page in kernel.
+ See also the heart(3) manual page in Kernel.
@@ -206,7 +206,7 @@ esac
chown 0 /usr/sbin/reboot
chmod 4755 /usr/sbin/reboot
- See also the heart(3) manual page in kernel.
+ See also the heart(3) manual page in Kernel.
@@ -413,8 +413,8 @@ chown root mod_syslog]]>
Related Documents
See the os_mon(3) application,
- the application(3) manual page in kernel,
- and the erl(1) manual page in erts.
+ the application(3) manual page in Kernel,
+ and the erl(1) manual page in ERTS.
@@ -474,7 +474,7 @@ chown root mod_syslog]]>
default, it must be called start and reside in
/bin]]>. Another start
program can be used, by using configuration parameter
- start_prg in application sasl.
+ start_prg in application SASL.
The start program must call run_erl as shown below.
It must also take an optional parameter, which defaults to
/releases/start_erl.data]]>.
@@ -484,7 +484,7 @@ chown root mod_syslog]]>
The ]]> directory is where new release
packets are installed, and where the release handler keeps
information about releases. For more information, see the
- release_handler(3) manual page in sasl.
+ release_handler(3) manual page in SASL.
The following script illustrates the default behaviour of the
program:
If a diskless and/or read-only client node with the
- sasl configuration parameter static_emulator set
+ SASL configuration parameter static_emulator set
to true is about to start, the -boot and
-config flags must be changed.
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 start and reside in
/bin]]>. Another start program can be
used, by using the configuration parameter start_prg in
- the application sasl.
+ application SASL.
The start program must call run_erl as shown below.
It must also take an optional parameter which defaults to
/bin/start_erl.data]]>.
@@ -80,8 +80,8 @@
The ]]> directory is where new release packets
are installed, and where the release handler keeps information
- about releases. See release_handler(3) in the
- application sasl for further information.
+ about releases. See release_handler(3) in
+ application SASL for further information.
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 $*
- If a diskless and/or read-only client node with the sasl
+ If a diskless and/or read-only client node with the SASL
configuration parameter static_emulator set to true
is about to start the -boot and -config flags must be
changed. As such a client can not read a new start_erl.data
diff --git a/system/doc/oam/oam_intro.xml b/system/doc/oam/oam_intro.xml
index cdcb6e3111..8b8d69e638 100644
--- a/system/doc/oam/oam_intro.xml
+++ b/system/doc/oam/oam_intro.xml
@@ -178,7 +178,7 @@
MIB Structure
The top-level OTP MIB is called OTP-REG and it is
- included in the sasl application. All other OTP MIBs
+ included in the SASL application. All other OTP MIBs
import some objects from this MIB.
Each MIB is contained in one application. The MIB text
@@ -188,7 +188,7 @@
.hrl]]>, and the compiled MIBs
are stored under .bin]]>.
For example, the OTP-MIB is included in the
- sasl application:
+ SASL application:
sasl-1.3/mibs/OTP-MIB.mib
@@ -211,11 +211,11 @@ snmp:c("MY-MIB", [{il, ["sasl/priv/mibs"]}]).
The following MIBs are defined in the OTP system:
- OTP-REG) (in sasl) contains the top-level
+ OTP-REG) (in SASL) contains the top-level
OTP registration objects, used by all other MIBs.
- OTP-TC (in sasl) contains the general
+ OTP-TC (in SASL) contains the general
Textual Conventions, which can be used by any other MIB.
- OTP-MIB (in sasl) contains objects for
+ OTP-MIB (in SASL) contains objects for
instrumentation of the Erlang nodes, the Erlang machines,
and the applications in the system.
OTP-OS-MON-MIB (in oc_mon) contains
diff --git a/system/doc/programming_examples/records.xml b/system/doc/programming_examples/records.xml
index da346dd0b3..074aa636b4 100644
--- a/system/doc/programming_examples/records.xml
+++ b/system/doc/programming_examples/records.xml
@@ -93,7 +93,7 @@ person
at compile time, not at runtime. For details on records
in the shell, see the
shell(3)
- manual page in stdlib.
+ manual page in STDLIB.
diff --git a/system/doc/reference_manual/typespec.xml b/system/doc/reference_manual/typespec.xml
index f17e5df277..1899efd5f3 100644
--- a/system/doc/reference_manual/typespec.xml
+++ b/system/doc/reference_manual/typespec.xml
@@ -47,7 +47,7 @@
- To document function interfaces
- To provide more information for bug detection tools,
- such as Dialyzer
+ such as Dialyzer
- To be exploited by documentation tools, such as EDoc, for
generating program documentation of various forms
--
cgit v1.2.3
|