erts: Editorial changes

33 files changed, 17154 insertions, 14811 deletions

diff --git a/erts/doc/src/absform.xml b/erts/doc/src/absform.xml
index 0b04f8f70e..c7f1285879 100644
--- a/erts/doc/src/absform.xml
+++ b/erts/doc/src/absform.xml
@@ -26,144 +26,198 @@
     <prepared>Arndt Jonasson</prepared>
     <responsible>Kenneth Lundin</responsible>
     <docno>1</docno>
-    <approved>Jultomten</approved>
+    <approved></approved>
     <checked></checked>
-    <date>00-12-01</date>
+    <date>2000-12-01</date>
     <rev>A</rev>
     <file>absform.xml</file>
   </header>
-  <p></p>
-  <p>This document describes the standard representation of parse trees for Erlang
-    programs as Erlang terms. This representation is known as the <em>abstract format</em>.
-    Functions dealing with such parse trees are <c>compile:forms/[1,2]</c>
-    and functions in the modules
-    <c>epp</c>,
-    <c>erl_eval</c>,
-    <c>erl_lint</c>,
-    <c>erl_pp</c>,
-    <c>erl_parse</c>,
-    and
-    <c>io</c>.
-    They are also used as input and output for parse transforms (see the module
-    <c>compile</c>).</p>
+  <p>This secion describes the standard representation of parse trees for Erlang
+    programs as Erlang terms. This representation is known as the <em>abstract
+    format</em>. Functions dealing with such parse trees are
+    <seealso marker="compiler:compile#forms/1">
+    <c>compile:forms/1,2</c></seealso> and functions in the following
+    modules:</p>
+
+  <list type="bulleted">
+    <item><seealso marker="stdlib:epp">
+      <c>stdlib:epp</c></seealso></item>
+    <item><seealso marker="stdlib:erl_eval">
+      <c>stdlib:erl_eval</c></seealso></item>
+    <item><seealso marker="stdlib:erl_lint">
+      <c>stdlib:erl_lint</c></seealso></item>
+    <item><seealso marker="stdlib:erl_parse">
+      <c>sdlib:erl_parse</c></seealso></item>
+    <item><seealso marker="stdlib:erl_pp">
+      <c>stdlib:erl_pp</c></seealso></item>
+    <item><seealso marker="stdlib:io">
+      <c>stdlib:io</c></seealso></item>
+  </list>
+
+  <p>The functions are also used as input and output for parse transforms (see
+    the <seealso marker="compiler:compile"><c>compiler:compile</c></seealso>
+    module.</p>
+
   <p>We use the function <c>Rep</c> to denote the mapping from an Erlang source
     construct <c>C</c> to its abstract format representation <c>R</c>, and write
-    <c>R = Rep(C)</c>.
-    </p>
-  <p>The word <c>LINE</c> below represents an integer, and denotes the
+    <c>R = Rep(C)</c>.</p>
+
+  <p>The word <c>LINE</c> in this section represents an integer, and denotes the
     number of the line in the source file where the construction occurred.
-    Several instances of <c>LINE</c> in the same construction may denote
+    Several instances of <c>LINE</c> in the same construction can denote
     different lines.</p>
-  <p>Since operators are not terms in their own right, when operators are
-    mentioned below, the representation of an operator should be taken to
+
+  <p>As operators are not terms in their own right, when operators are
+    mentioned below, the representation of an operator is to be taken to
     be the atom with a printname consisting of the same characters as the
-    operator.
-    </p>
+    operator.</p>
 
   <section>
     <title>Module Declarations and Forms</title>
-    <p>A module declaration consists of a sequence of forms that are either
+    <p>A module declaration consists of a sequence of forms, which are either
       function declarations or attributes.</p>
+
     <list type="bulleted">
-      <item>If D is a module declaration consisting of the forms
-      <c>F_1</c>, ..., <c>F_k</c>, then
-       Rep(D) = <c>[Rep(F_1), ..., Rep(F_k)]</c>.</item>
-      <item>If F is an attribute <c>-export([Fun_1/A_1, ..., Fun_k/A_k])</c>, then
-       Rep(F) = <c>{attribute,LINE,export,[{Fun_1,A_1}, ..., {Fun_k,A_k}]}</c>.</item>
-      <item>If F is an attribute <c>-import(Mod,[Fun_1/A_1, ..., Fun_k/A_k])</c>, then
-       Rep(F) = <c>{attribute,LINE,import,{Mod,[{Fun_1,A_1}, ..., {Fun_k,A_k}]}}</c>.</item>
-      <item>If F is an attribute <c>-module(Mod)</c>, then
-       Rep(F) = <c>{attribute,LINE,module,Mod}</c>.</item>
-      <item>If F is an attribute <c>-file(File,Line)</c>, then
-       Rep(F) = <c>{attribute,LINE,file,{File,Line}}</c>.</item>
-      <item>If F is a function declaration
-       <c>Name Fc_1 ; ... ; Name Fc_k</c>,
-       where each <c>Fc_i</c> is a function clause with a
-       pattern sequence of the same length <c>Arity</c>, then
-       Rep(F) = <c>{function,LINE,Name,Arity,[Rep(Fc_1), ...,Rep(Fc_k)]}</c>.
-      </item>
-      <item>If F is a function specification
-       <c>-Spec Name Ft_1; ...; Ft_k</c>,
-       where <c>Spec</c> is either the atom <c>spec</c> or the atom
-       <c>callback</c>, and each <c>Ft_i</c> is a possibly constrained
-       function type with an argument sequence of the same length
-       <c>Arity</c>, then Rep(F) =
-       <c>{attribute,Line,Spec,{{Name,Arity},[Rep(Ft_1), ..., Rep(Ft_k)]}}</c>.
-      </item>
-      <item>If F is a function specification
-       <c>-spec Mod:Name Ft_1; ...; Ft_k</c>,
-       where each <c>Ft_i</c> is a possibly constrained
-       function type with an argument sequence of the same length
-       <c>Arity</c>, then Rep(F) =
-       <c>{attribute,Line,spec,{{Mod,Name,Arity},[Rep(Ft_1), ..., Rep(Ft_k)]}}</c>.
-      </item>
-      <item>If F is a record declaration
-       <c>-record(Name,{V_1, ..., V_k})</c>,
-       where each <c>V_i</c> is a record field, then Rep(F) =
-       <c>{attribute,LINE,record,{Name,[Rep(V_1), ..., Rep(V_k)]}}</c>.
-       For Rep(V), see below.</item>
-      <item>If F is a type declaration
-       <c>-Type Name(V_1, ..., V_k) :: T</c>, where
-       <c>Type</c> is either the atom <c>type</c> or the atom <c>opaque</c>,
-       each <c>V_i</c> is a variable, and <c>T</c> is a type, then Rep(F) =
-       <c>{attribute,LINE,Type,{Name,Rep(T),[Rep(V_1), ..., Rep(V_k)]}}</c>.
-      </item>
-      <item>If F is a wild attribute <c>-A(T)</c>, then
-       Rep(F) = <c>{attribute,LINE,A,T}</c>.
-      <br></br></item>
+      <item>
+        <p>If D is a module declaration consisting of the forms
+          <c>F_1</c>, ..., <c>F_k</c>, then
+          Rep(D) = <c>[Rep(F_1), ..., Rep(F_k)]</c>.</p>
+      </item>
+      <item>
+        <p>If F is an attribute <c>-export([Fun_1/A_1, ..., Fun_k/A_k])</c>,
+          then Rep(F) =
+          <c>{attribute,LINE,export,[{Fun_1,A_1}, ..., {Fun_k,A_k}]}</c>.</p>
+      </item>
+      <item>
+        <p>If F is an attribute <c>-import(Mod,[Fun_1/A_1, ..., Fun_k/A_k])</c>,
+          then Rep(F) =
+          <c>{attribute,LINE,import,{Mod,[{Fun_1,A_1}, ...,
+          {Fun_k,A_k}]}}</c>.</p>
+      </item>
+      <item>
+        <p>If F is an attribute <c>-module(Mod)</c>, then
+          Rep(F) = <c>{attribute,LINE,module,Mod}</c>.</p>
+      </item>
+      <item>
+        <p>If F is an attribute <c>-file(File,Line)</c>, then
+          Rep(F) = <c>{attribute,LINE,file,{File,Line}}</c>.</p>
+      </item>
+      <item>
+        <p>If F is a function declaration <c>Name Fc_1 ; ... ; Name Fc_k</c>,
+          where each <c>Fc_i</c> is a function clause with a pattern sequence of
+          the same length <c>Arity</c>, then Rep(F) =
+          <c>{function,LINE,Name,Arity,[Rep(Fc_1), ...,Rep(Fc_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If F is a function specification <c>-Spec Name Ft_1; ...; Ft_k</c>,
+          where <c>Spec</c> is either the atom <c>spec</c> or the atom
+          <c>callback</c>, and each <c>Ft_i</c> is a possibly constrained
+          function type with an argument sequence of the same length
+          <c>Arity</c>, then Rep(F) =
+          <c>{attribute,Line,Spec,{{Name,Arity},[Rep(Ft_1), ...,
+          Rep(Ft_k)]}}</c>.</p>
+      </item>
+      <item>
+        <p>If F is a function specification
+          <c>-spec Mod:Name Ft_1; ...; Ft_k</c>, where each <c>Ft_i</c> is a
+          possibly constrained function type with an argument sequence of the
+          same length <c>Arity</c>, then Rep(F) =
+          <c>{attribute,Line,spec,{{Mod,Name,Arity},[Rep(Ft_1), ...,
+          Rep(Ft_k)]}}</c>.</p>
+      </item>
+      <item>
+        <p>If F is a record declaration <c>-record(Name,{V_1, ..., V_k})</c>,
+          where each <c>V_i</c> is a record field, then Rep(F) =
+          <c>{attribute,LINE,record,{Name,[Rep(V_1), ..., Rep(V_k)]}}</c>.
+          For Rep(V), see below.</p>
+      </item>
+      <item>
+        <p>If F is a type declaration <c>-Type Name(V_1, ..., V_k) :: T</c>,
+          where <c>Type</c> is either the atom <c>type</c> or the atom
+          <c>opaque</c>, each <c>V_i</c> is a variable, and <c>T</c> is a type,
+          then Rep(F) =
+          <c>{attribute,LINE,Type,{Name,Rep(T),[Rep(V_1), ...,
+          Rep(V_k)]}}</c>.</p>
+      </item>
+      <item>
+        <p>If F is a wild attribute <c>-A(T)</c>, then
+          Rep(F) = <c>{attribute,LINE,A,T}</c>.</p>
+      </item>
     </list>
 
     <section>
       <title>Record Fields</title>
-      <p>Each field in a record declaration may have an optional
-        explicit default initializer expression, as well as an
+      <p>Each field in a record declaration can have an optional,
+        explicit, default initializer expression, and an
         optional type.</p>
+
       <list type="bulleted">
-        <item>If V is <c>A</c>, then
-         Rep(V) = <c>{record_field,LINE,Rep(A)}</c>.</item>
-        <item>If V is <c>A = E</c>,
-	 where <c>E</c> is an expression, then
-         Rep(V) = <c>{record_field,LINE,Rep(A),Rep(E)}</c>.</item>
-        <item>If V is <c>A :: T</c>, where <c>T</c> is a type, then Rep(V) =
-          <c>{typed_record_field,{record_field,LINE,Rep(A)},Rep(T)}</c>.
-          </item>
-        <item>If V is <c>A = E :: T</c>, where
-          <c>E</c> is an expression and <c>T</c> is a type, then Rep(V) =
-          <c>{typed_record_field,{record_field,LINE,Rep(A),Rep(E)},Rep(T)}</c>.
+        <item>
+          <p>If V is <c>A</c>, then
+            Rep(V) = <c>{record_field,LINE,Rep(A)}</c>.</p>
+        </item>
+        <item>
+          <p>If V is <c>A = E</c>, where <c>E</c> is an expression, then
+            Rep(V) = <c>{record_field,LINE,Rep(A),Rep(E)}</c>.</p>
+        </item>
+        <item>
+          <p>If V is <c>A :: T</c>, where <c>T</c> is a type, then Rep(V) =
+            <c>{typed_record_field,{record_field,LINE,Rep(A)},Rep(T)}</c>.</p>
+        </item>
+        <item>
+          <p>If V is <c>A = E :: T</c>, where
+            <c>E</c> is an expression and <c>T</c> is a type, then Rep(V) =
+            <c>{typed_record_field,{record_field,LINE,Rep(A),Rep(E)},Rep(T)}</c>.
+          </p>
         </item>
       </list>
     </section>
 
     <section>
-      <title>Representation of Parse Errors and End-of-file</title>
+      <title>Representation of Parse Errors and End-of-File</title>
       <p>In addition to the representations of forms, the list that represents
-        a module declaration (as returned by functions in <c>erl_parse</c> and
-        <c>epp</c>) may contain tuples <c>{error,E}</c> and
-	<c>{warning,W}</c>, denoting syntactically incorrect forms and
-	warnings, and <c>{eof,LINE}</c>, denoting an end-of-stream
-	encountered before a complete form had been parsed.</p>
+        a module declaration (as returned by functions in
+        <seealso marker="stdlib:epp"><c>stdlib:epp</c></seealso> and
+        <seealso marker="stdlib:erl_parse"><c>sdlib:erl_parse</c></seealso>)
+        can contain the following:</p>
+
+      <list type="bulleted">
+        <item>Tuples <c>{error,E}</c> and <c>{warning,W}</c>, denoting
+          syntactically incorrect forms and warnings</item>
+        <item><c>{eof,LINE}</c>, denoting an end-of-stream
+          encountered before a complete form had been parsed</item>
+      </list>
     </section>
   </section>
 
   <section>
     <title>Atomic Literals</title>
     <p>There are five kinds of atomic literals, which are represented in the
-      same way in patterns, expressions and guards:</p>
+      same way in patterns, expressions, and guards:</p>
+
     <list type="bulleted">
-      <item>If L is an atom literal, then
-       Rep(L) = <c>{atom,LINE,L}</c>.</item>
-      <item>If L is a character literal, then
-       Rep(L) = <c>{char,LINE,L}</c>.</item>
-      <item>If L is a float literal, then
-       Rep(L) = <c>{float,LINE,L}</c>.</item>
-      <item>If L is an integer literal, then
-       Rep(L) = <c>{integer,LINE,L}</c>.</item>
-      <item>If L is a string literal consisting of the characters
-      <c>C_1</c>, ..., <c>C_k</c>, then
-       Rep(L) = <c>{string,LINE,[C_1, ..., C_k]}</c>.</item>
+      <item>
+        <p>If L is an atom literal, then Rep(L) = <c>{atom,LINE,L}</c>.</p>
+      </item>
+      <item>
+        <p>If L is a character literal, then Rep(L) = <c>{char,LINE,L}</c>.</p>
+      </item>
+      <item>
+        <p>If L is a float literal, then Rep(L) = <c>{float,LINE,L}</c>.</p>
+      </item>
+      <item>
+        <p>If L is an integer literal, then
+          Rep(L) = <c>{integer,LINE,L}</c>.</p>
+      </item>
+      <item>
+        <p>If L is a string literal consisting of the characters
+          <c>C_1</c>, ..., <c>C_k</c>, then
+          Rep(L) = <c>{string,LINE,[C_1, ..., C_k]}</c>.</p>
+      </item>
     </list>
-    <p>Note that negative integer and float literals do not occur as such; they are
-      parsed as an application of the unary negation operator.</p>
+
+    <p>Notice that negative integers and float literals do not occur as such;
+      they are parsed as an application of the unary negation operator.</p>
   </section>
 
   <section>
@@ -171,288 +225,424 @@
     <p>If Ps is a sequence of patterns <c>P_1, ..., P_k</c>, then
       Rep(Ps) = <c>[Rep(P_1), ..., Rep(P_k)]</c>. Such sequences occur as the
       list of arguments to a function or fun.</p>
+
     <p>Individual patterns are represented as follows:</p>
+
     <list type="bulleted">
-      <item>If P is an atomic literal <c>L</c>, then Rep(P) = Rep(L).</item>
-      <item>If P is a bit string pattern
-       <c>&lt;&lt;P_1:Size_1/TSL_1, ..., P_k:Size_k/TSL_k>></c>, where each
-       <c>Size_i</c> is an expression that can be evaluated to an integer
-       and each <c>TSL_i</c> is a type specificer list, then
-       Rep(P) = <c>{bin,LINE,[{bin_element,LINE,Rep(P_1),Rep(Size_1),Rep(TSL_1)}, ..., {bin_element,LINE,Rep(P_k),Rep(Size_k),Rep(TSL_k)}]}</c>.
-       For Rep(TSL), see below.
-       An omitted <c>Size_i</c> is represented by <c>default</c>.
-       An omitted <c>TSL_i</c> is represented by <c>default</c>.</item>
-      <item>If P is a compound pattern <c>P_1 = P_2</c>, then
-       Rep(P) = <c>{match,LINE,Rep(P_1),Rep(P_2)}</c>.</item>
-      <item>If P is a cons pattern <c>[P_h | P_t]</c>, then
-       Rep(P) = <c>{cons,LINE,Rep(P_h),Rep(P_t)}</c>.</item>
-      <item>If P is a map pattern <c>#{A_1, ..., A_k}</c>, where each
-       <c>A_i</c> is an association <c>P_i_1 := P_i_2</c>, then Rep(P) =
-       <c>{map,LINE,[Rep(A_1), ..., Rep(A_k)]}</c>. For Rep(A), see
-       below.</item>
-      <item>If P is a nil pattern <c>[]</c>, then
-       Rep(P) = <c>{nil,LINE}</c>.</item>
-      <item>If P is an operator pattern <c>P_1 Op P_2</c>,
-       where <c>Op</c> is a binary operator (this is either an occurrence
-       of <c>++</c> applied to a literal string or character
-       list, or an occurrence of an expression that can be evaluated to a number
-       at compile time),
-       then Rep(P) = <c>{op,LINE,Op,Rep(P_1),Rep(P_2)}</c>.</item>
-      <item>If P is an operator pattern <c>Op P_0</c>,
-       where <c>Op</c> is a unary operator (this is an occurrence of
-       an expression that can be evaluated to a number at compile
-       time), then Rep(P) = <c>{op,LINE,Op,Rep(P_0)}</c>.</item>
-      <item>If P is a parenthesized pattern <c>( P_0 )</c>, then
-       Rep(P) = <c>Rep(P_0)</c>,
-       that is, parenthesized patterns cannot be distinguished from their
-       bodies.</item>
-      <item>If P is a record field index pattern <c>#Name.Field</c>,
-       where <c>Field</c> is an atom, then
-       Rep(P) = <c>{record_index,LINE,Name,Rep(Field)}</c>.</item>
-      <item>If P is a record pattern
-       <c>#Name{Field_1=P_1, ..., Field_k=P_k}</c>,
-       where each <c>Field_i</c> is an atom or <c>_</c>, then Rep(P) =
-       <c>{record,LINE,Name,[{record_field,LINE,Rep(Field_1),Rep(P_1)}, ..., {record_field,LINE,Rep(Field_k),Rep(P_k)}]}</c>.</item>
-      <item>If P is a tuple pattern <c>{P_1, ..., P_k}</c>, then
-       Rep(P) = <c>{tuple,LINE,[Rep(P_1), ..., Rep(P_k)]}</c>.</item>
-      <item>If P is a universal pattern <c>_</c>, then
-       Rep(P) = <c>{var,LINE,'_'}</c>.</item>
-      <item>If P is a variable pattern <c>V</c>, then
-       Rep(P) = <c>{var,LINE,A}</c>,
-       where A is an atom with a printname consisting of the same characters as
-      <c>V</c>.</item>
+      <item>
+        <p>If P is an atomic literal <c>L</c>, then Rep(P) = Rep(L).</p>
+      </item>
+      <item>
+        <p>If P is a bitstring pattern
+          <c>&lt;&lt;P_1:Size_1/TSL_1, ..., P_k:Size_k/TSL_k>></c>, where each
+          <c>Size_i</c> is an expression that can be evaluated to an integer,
+          and each <c>TSL_i</c> is a type specificer list, then Rep(P) =
+          <c>{bin,LINE,[{bin_element,LINE,Rep(P_1),Rep(Size_1),Rep(TSL_1)},
+          ..., {bin_element,LINE,Rep(P_k),Rep(Size_k),Rep(TSL_k)}]}</c>.
+          For Rep(TSL), see below.
+          An omitted <c>Size_i</c> is represented by <c>default</c>.
+          An omitted <c>TSL_i</c> is represented by <c>default</c>.</p>
+      </item>
+      <item>
+        <p>If P is a compound pattern <c>P_1 = P_2</c>, then Rep(P) =
+          <c>{match,LINE,Rep(P_1),Rep(P_2)}</c>.</p>
+      </item>
+      <item>
+        <p>If P is a cons pattern <c>[P_h | P_t]</c>, then Rep(P) =
+          <c>{cons,LINE,Rep(P_h),Rep(P_t)}</c>.</p>
+      </item>
+      <item>
+        <p>If P is a map pattern <c>#{A_1, ..., A_k}</c>, where each
+          <c>A_i</c> is an association <c>P_i_1 := P_i_2</c>, then Rep(P) =
+          <c>{map,LINE,[Rep(A_1), ..., Rep(A_k)]}</c>.
+          For Rep(A), see below.</p>
+      </item>
+      <item>
+        <p>If P is a nil pattern <c>[]</c>, then Rep(P) =
+          <c>{nil,LINE}</c>.</p>
+      </item>
+      <item>
+        <p>If P is an operator pattern <c>P_1 Op P_2</c>, where <c>Op</c> is a
+          binary operator (this is either an occurrence of <c>++</c> applied to
+          a literal string or character list, or an occurrence of an expression
+          that can be evaluated to a number at compile time), then Rep(P) =
+          <c>{op,LINE,Op,Rep(P_1),Rep(P_2)}</c>.</p>
+      </item>
+      <item>
+        <p>If P is an operator pattern <c>Op P_0</c>, where <c>Op</c> is a
+          unary operator (this is an occurrence of an expression that can be
+          evaluated to a number at compile time), then Rep(P) =
+          <c>{op,LINE,Op,Rep(P_0)}</c>.</p>
+      </item>
+      <item>
+        <p>If P is a parenthesized pattern <c>( P_0 )</c>, then Rep(P) =
+          <c>Rep(P_0)</c>, that is, parenthesized patterns cannot be
+          distinguished from their bodies.</p>
+      </item>
+      <item>
+        <p>If P is a record field index pattern <c>#Name.Field</c>,
+          where <c>Field</c> is an atom, then Rep(P) =
+          <c>{record_index,LINE,Name,Rep(Field)}</c>.</p>
+      </item>
+      <item>
+        <p>If P is a record pattern <c>#Name{Field_1=P_1, ..., Field_k=P_k}</c>,
+          where each <c>Field_i</c> is an atom or <c>_</c>, then Rep(P) =
+          <c>{record,LINE,Name,[{record_field,LINE,Rep(Field_1),Rep(P_1)}, ...,
+          {record_field,LINE,Rep(Field_k),Rep(P_k)}]}</c>.</p>
+      </item>
+      <item>
+        <p>If P is a tuple pattern <c>{P_1, ..., P_k}</c>, then Rep(P) =
+          <c>{tuple,LINE,[Rep(P_1), ..., Rep(P_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If P is a universal pattern <c>_</c>, then Rep(P) =
+          <c>{var,LINE,'_'}</c>.</p></item>
+      <item>
+        <p>If P is a variable pattern <c>V</c>, then Rep(P) =
+          <c>{var,LINE,A}</c>, where A is an atom with a printname consisting
+          of the same characters as <c>V</c>.</p>
+      </item>
     </list>
-    <p>Note that every pattern has the same source form as some expression, and is
-      represented the same way as the corresponding expression.</p>
+
+    <p>Notice that every pattern has the same source form as some expression,
+      and is represented in the same way as the corresponding expression.</p>
   </section>
 
   <section>
     <title>Expressions</title>
-    <p>A body B is a nonempty sequence of expressions <c>E_1, ..., E_k</c>,
+    <p>A body B is a non-empty sequence of expressions <c>E_1, ..., E_k</c>,
       and Rep(B) = <c>[Rep(E_1), ..., Rep(E_k)]</c>.</p>
-    <p>An expression E is one of the following alternatives:</p>
+
+    <p>An expression E is one of the following:</p>
+
     <list type="bulleted">
-      <item>If E is an atomic literal <c>L</c>, then Rep(E) = Rep(L).</item>
-      <item>If E is a bit string comprehension
-       <c>&lt;&lt;E_0 || Q_1, ..., Q_k>></c>,
-       where each <c>Q_i</c> is a qualifier, then
-       Rep(E) = <c>{bc,LINE,Rep(E_0),[Rep(Q_1), ..., Rep(Q_k)]}</c>.
-       For Rep(Q), see below.</item>
-      <item>If E is a bit string constructor
-       <c>&lt;&lt;E_1:Size_1/TSL_1, ..., E_k:Size_k/TSL_k>></c>,
-       where each <c>Size_i</c> is an expression and each
-       <c>TSL_i</c> is a type specificer list, then Rep(E) =
-       <c>{bin,LINE,[{bin_element,LINE,Rep(E_1),Rep(Size_1),Rep(TSL_1)}, ..., {bin_element,LINE,Rep(E_k),Rep(Size_k),Rep(TSL_k)}]}</c>.
-       For Rep(TSL), see below.
-       An omitted <c>Size_i</c> is represented by <c>default</c>.
-       An omitted <c>TSL_i</c> is represented by <c>default</c>.</item>
-      <item>If E is a block expression <c>begin B end</c>,
-       where <c>B</c> is a body, then
-       Rep(E) = <c>{block,LINE,Rep(B)}</c>.</item>
-      <item>If E is a case expression <c>case E_0 of Cc_1 ; ... ; Cc_k end</c>,
-       where <c>E_0</c> is an expression and each <c>Cc_i</c> is a
-       case clause then Rep(E) =
-      <c>{'case',LINE,Rep(E_0),[Rep(Cc_1), ..., Rep(Cc_k)]}</c>.</item>
-      <item>If E is a catch expression <c>catch E_0</c>, then
-       Rep(E) = <c>{'catch',LINE,Rep(E_0)}</c>.</item>
-      <item>If E is a cons skeleton <c>[E_h | E_t]</c>, then
-       Rep(E) = <c>{cons,LINE,Rep(E_h),Rep(E_t)}</c>.</item>
-      <item>If E is a fun expression <c>fun Name/Arity</c>, then
-       Rep(E) = <c>{'fun',LINE,{function,Name,Arity}}</c>.</item>
-      <item>If E is a fun expression
-       <c>fun Module:Name/Arity</c>, then Rep(E) =
-       <c>{'fun',LINE,{function,Rep(Module),Rep(Name),Rep(Arity)}}</c>.
-       (Before the R15 release: Rep(E) =
-       <c>{'fun',LINE,{function,Module,Name,Arity}}</c>.)</item>
-      <item>If E is a fun expression <c>fun Fc_1 ; ... ; Fc_k end</c>,
-       where each <c>Fc_i</c> is a function clause then Rep(E) =
-      <c>{'fun',LINE,{clauses,[Rep(Fc_1), ..., Rep(Fc_k)]}}</c>.</item>
-      <item>If E is a fun expression
-       <c>fun Name Fc_1 ; ... ; Name Fc_k end</c>,
-       where <c>Name</c> is a variable and each
-       <c>Fc_i</c> is a function clause then Rep(E) =
-       <c>{named_fun,LINE,Name,[Rep(Fc_1), ..., Rep(Fc_k)]}</c>.
-       </item>
-      <item>If E is a function call <c>E_0(E_1, ..., E_k)</c>, then
-       Rep(E) = <c>{call,LINE,Rep(E_0),[Rep(E_1), ..., Rep(E_k)]}</c>.</item>
-      <item>If E is a function call <c>E_m:E_0(E_1, ..., E_k)</c>,
-       then Rep(E) =
-       <c>{call,LINE,{remote,LINE,Rep(E_m),Rep(E_0)},[Rep(E_1), ...,  Rep(E_k)]}</c>.
-      </item>
-      <item>If E is an if expression <c>if Ic_1 ; ... ; Ic_k  end</c>,
-       where each <c>Ic_i</c> is an if clause then Rep(E) =
-      <c>{'if',LINE,[Rep(Ic_1), ..., Rep(Ic_k)]}</c>.</item>
-      <item>If E is a list comprehension <c>[E_0 || Q_1, ..., Q_k]</c>,
-       where each <c>Q_i</c> is a qualifier, then Rep(E) =
-       <c>{lc,LINE,Rep(E_0),[Rep(Q_1), ..., Rep(Q_k)]}</c>. For Rep(Q), see
-       below.</item>
-      <item>If E is a map creation <c>#{A_1, ..., A_k}</c>,
-       where each <c>A_i</c> is an association <c>E_i_1 => E_i_2</c>
-       or <c>E_i_1 := E_i_2</c>, then Rep(E) =
-       <c>{map,LINE,[Rep(A_1), ..., Rep(A_k)]}</c>. For Rep(A), see
-       below.</item>
-      <item>If E is a map update <c>E_0#{A_1, ..., A_k}</c>,
-       where each <c>A_i</c> is an association <c>E_i_1 => E_i_2</c>
-       or <c>E_i_1 := E_i_2</c>, then Rep(E) =
-       <c>{map,LINE,Rep(E_0),[Rep(A_1), ..., Rep(A_k)]}</c>.
-       For Rep(A), see below.</item>
-      <item>If E is a match operator expression <c>P = E_0</c>,
-       where <c>P</c> is a pattern, then
-       Rep(E) = <c>{match,LINE,Rep(P),Rep(E_0)}</c>.</item>
-      <item>If E is nil, <c>[]</c>, then
-       Rep(E) = <c>{nil,LINE}</c>.</item>
-      <item>If E is an operator expression <c>E_1 Op E_2</c>,
-       where <c>Op</c> is a binary operator other than the match
-       operator <c>=</c>, then
-       Rep(E) = <c>{op,LINE,Op,Rep(E_1),Rep(E_2)}</c>.</item>
-      <item>If E is an operator expression <c>Op E_0</c>,
-       where <c>Op</c> is a unary operator, then
-       Rep(E) = <c>{op,LINE,Op,Rep(E_0)}</c>.</item>
-      <item>If E is a parenthesized expression <c>( E_0 )</c>, then
-       Rep(E) = <c>Rep(E_0)</c>, that is, parenthesized
-       expressions cannot be distinguished from their bodies.</item>
-      <item>If E is a receive expression <c>receive Cc_1 ; ... ; Cc_k end</c>,
-       where each <c>Cc_i</c> is a case clause then Rep(E) =
-      <c>{'receive',LINE,[Rep(Cc_1), ..., Rep(Cc_k)]}</c>.</item>
-      <item>If E is a receive expression
-       <c>receive Cc_1 ; ... ; Cc_k after E_0 -> B_t end</c>,
-       where each <c>Cc_i</c> is a case clause,
-      <c>E_0</c> is an expression and <c>B_t</c> is a body, then Rep(E) =
-      <c>{'receive',LINE,[Rep(Cc_1), ..., Rep(Cc_k)],Rep(E_0),Rep(B_t)}</c>.</item>
-      <item>If E is a record creation
-       <c>#Name{Field_1=E_1, ..., Field_k=E_k}</c>,
-       where each <c>Field_i</c> is an atom or <c>_</c>, then Rep(E) =
-      <c>{record,LINE,Name,[{record_field,LINE,Rep(Field_1),Rep(E_1)}, ..., {record_field,LINE,Rep(Field_k),Rep(E_k)}]}</c>.</item>
-      <item>If E is a record field access <c>E_0#Name.Field</c>,
-       where <c>Field</c> is an atom, then
-       Rep(E) = <c>{record_field,LINE,Rep(E_0),Name,Rep(Field)}</c>.</item>
-      <item>If E is a record field index <c>#Name.Field</c>,
-       where <c>Field</c> is an atom, then
-       Rep(E) = <c>{record_index,LINE,Name,Rep(Field)}</c>.</item>
-      <item>If E is a record update
-       <c>E_0#Name{Field_1=E_1, ..., Field_k=E_k}</c>,
-       where each <c>Field_i</c> is an atom, then Rep(E) =
-      <c>{record,LINE,Rep(E_0),Name,[{record_field,LINE,Rep(Field_1),Rep(E_1)}, ..., {record_field,LINE,Rep(Field_k),Rep(E_k)}]}</c>.</item>
-      <item>If E is a tuple skeleton <c>{E_1, ..., E_k}</c>, then
-       Rep(E) = <c>{tuple,LINE,[Rep(E_1), ..., Rep(E_k)]}</c>.</item>
-      <item>If E is a try expression <c>try B catch Tc_1 ; ... ; Tc_k end</c>,
-       where <c>B</c> is a body and each <c>Tc_i</c> is a catch clause then
-       Rep(E) =
-      <c>{'try',LINE,Rep(B),[],[Rep(Tc_1), ..., Rep(Tc_k)],[]}</c>.</item>
-      <item>If E is a try expression
-       <c>try B of Cc_1 ; ... ; Cc_k catch Tc_1 ; ... ; Tc_n end</c>,
-       where <c>B</c> is a body,
-       each <c>Cc_i</c> is a case clause and
-       each <c>Tc_j</c> is a catch clause then Rep(E) =
-      <c>{'try',LINE,Rep(B),[Rep(Cc_1), ..., Rep(Cc_k)],[Rep(Tc_1), ..., Rep(Tc_n)],[]}</c>.</item>
-      <item>If E is a try expression <c>try B after A end</c>,
-       where <c>B</c> and <c>A</c> are bodies then Rep(E) =
-      <c>{'try',LINE,Rep(B),[],[],Rep(A)}</c>.</item>
-      <item>If E is a try expression
-       <c>try B of Cc_1 ; ... ; Cc_k after A end</c>,
-       where <c>B</c> and <c>A</c> are a bodies and
-       each <c>Cc_i</c> is a case clause then Rep(E) =
-      <c>{'try',LINE,Rep(B),[Rep(Cc_1), ..., Rep(Cc_k)],[],Rep(A)}</c>.</item>
-      <item>If E is a try expression
-       <c>try B catch Tc_1 ; ... ; Tc_k after A end</c>,
-       where <c>B</c> and <c>A</c> are bodies and
-       each <c>Tc_i</c> is a catch clause then Rep(E) =
-      <c>{'try',LINE,Rep(B),[],[Rep(Tc_1), ..., Rep(Tc_k)],Rep(A)}</c>.</item>
-      <item>If E is a try expression
-       <c>try B of Cc_1 ; ... ; Cc_k  catch Tc_1 ; ... ; Tc_n after A end</c>,
-       where <c>B</c> and <c>A</c> are a bodies,
-       each <c>Cc_i</c> is a case clause, and
-       each <c>Tc_j</c> is a catch clause then
-       Rep(E) =
-      <c>{'try',LINE,Rep(B),[Rep(Cc_1), ..., Rep(Cc_k)],[Rep(Tc_1),  ..., Rep(Tc_n)],Rep(A)}</c>.</item>
-      <item>If E is a variable <c>V</c>, then Rep(E) = <c>{var,LINE,A}</c>,
-       where <c>A</c> is an atom with a printname consisting of the same
-       characters as <c>V</c>.</item>
+      <item>
+        <p>If E is an atomic literal <c>L</c>, then Rep(E) = Rep(L).</p>
+      </item>
+      <item>
+        <p>If E is a bitstring comprehension
+          <c>&lt;&lt;E_0 || Q_1, ..., Q_k>></c>,
+          where each <c>Q_i</c> is a qualifier, then Rep(E) =
+          <c>{bc,LINE,Rep(E_0),[Rep(Q_1), ..., Rep(Q_k)]}</c>.
+          For Rep(Q), see below.</p>
+      </item>
+      <item>
+        <p>If E is a bitstring constructor
+          <c>&lt;&lt;E_1:Size_1/TSL_1, ..., E_k:Size_k/TSL_k>></c>,
+          where each <c>Size_i</c> is an expression and each
+          <c>TSL_i</c> is a type specificer list, then Rep(E) =
+          <c>{bin,LINE,[{bin_element,LINE,Rep(E_1),Rep(Size_1),Rep(TSL_1)},
+          ..., {bin_element,LINE,Rep(E_k),Rep(Size_k),Rep(TSL_k)}]}</c>.
+          For Rep(TSL), see below.
+          An omitted <c>Size_i</c> is represented by <c>default</c>.
+          An omitted <c>TSL_i</c> is represented by <c>default</c>.</p>
+      </item>
+      <item>
+        <p>If E is a block expression <c>begin B end</c>,
+          where <c>B</c> is a body, then Rep(E) =
+          <c>{block,LINE,Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a case expression <c>case E_0 of Cc_1 ; ... ; Cc_k end</c>,
+          where <c>E_0</c> is an expression and each <c>Cc_i</c> is a
+          case clause, then Rep(E) =
+          <c>{'case',LINE,Rep(E_0),[Rep(Cc_1), ..., Rep(Cc_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a catch expression <c>catch E_0</c>, then Rep(E) =
+          <c>{'catch',LINE,Rep(E_0)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a cons skeleton <c>[E_h | E_t]</c>, then Rep(E) =
+          <c>{cons,LINE,Rep(E_h),Rep(E_t)}</c>.</p>
+      </item>
+      <item>
+        <p>>If E is a fun expression <c>fun Name/Arity</c>, then Rep(E) =
+          <c>{'fun',LINE,{function,Name,Arity}}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a fun expression <c>fun Module:Name/Arity</c>, then Rep(E) =
+          <c>{'fun',LINE,{function,Rep(Module),Rep(Name),Rep(Arity)}}</c>.
+          (Before Erlang/OTP R15: Rep(E) =
+          <c>{'fun',LINE,{function,Module,Name,Arity}}</c>.)</p>
+      </item>
+      <item>
+        <p>If E is a fun expression <c>fun Fc_1 ; ... ; Fc_k end</c>,
+          where each <c>Fc_i</c> is a function clause, then Rep(E) =
+          <c>{'fun',LINE,{clauses,[Rep(Fc_1), ..., Rep(Fc_k)]}}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a fun expression <c>fun Name Fc_1 ; ... ; Name Fc_k end</c>,
+          where <c>Name</c> is a variable and each
+          <c>Fc_i</c> is a function clause, then Rep(E) =
+          <c>{named_fun,LINE,Name,[Rep(Fc_1), ..., Rep(Fc_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a function call <c>E_0(E_1, ..., E_k)</c>, then Rep(E) =
+          <c>{call,LINE,Rep(E_0),[Rep(E_1), ..., Rep(E_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a function call <c>E_m:E_0(E_1, ..., E_k)</c>, then Rep(E) =
+          <c>{call,LINE,{remote,LINE,Rep(E_m),Rep(E_0)},[Rep(E_1), ...,
+          Rep(E_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is an if expression <c>if Ic_1 ; ... ; Ic_k  end</c>,
+          where each <c>Ic_i</c> is an if clause, then Rep(E) =
+          <c>{'if',LINE,[Rep(Ic_1), ..., Rep(Ic_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a list comprehension <c>[E_0 || Q_1, ..., Q_k]</c>,
+          where each <c>Q_i</c> is a qualifier, then Rep(E) =
+          <c>{lc,LINE,Rep(E_0),[Rep(Q_1), ..., Rep(Q_k)]}</c>.
+          For Rep(Q), see below.</p>
+      </item>
+      <item>
+        <p>If E is a map creation <c>#{A_1, ..., A_k}</c>,
+          where each <c>A_i</c> is an association <c>E_i_1 => E_i_2</c>
+          or <c>E_i_1 := E_i_2</c>, then Rep(E) =
+          <c>{map,LINE,[Rep(A_1), ..., Rep(A_k)]}</c>.
+          For Rep(A), see below.</p>
+      </item>
+      <item>
+        <p>If E is a map update <c>E_0#{A_1, ..., A_k}</c>,
+          where each <c>A_i</c> is an association <c>E_i_1 => E_i_2</c>
+          or <c>E_i_1 := E_i_2</c>, then Rep(E) =
+          <c>{map,LINE,Rep(E_0),[Rep(A_1), ..., Rep(A_k)]}</c>.
+          For Rep(A), see below.</p>
+      </item>
+      <item>
+        <p>If E is a match operator expression <c>P = E_0</c>,
+          where <c>P</c> is a pattern, then Rep(E) =
+          <c>{match,LINE,Rep(P),Rep(E_0)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is nil, <c>[]</c>, then Rep(E) = <c>{nil,LINE}</c>.</p>
+      </item>
+      <item>
+        <p>If E is an operator expression <c>E_1 Op E_2</c>,
+          where <c>Op</c> is a binary operator other than match operator
+          <c>=</c>, then Rep(E) =
+          <c>{op,LINE,Op,Rep(E_1),Rep(E_2)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is an operator expression <c>Op E_0</c>,
+          where <c>Op</c> is a unary operator, then Rep(E) =
+          <c>{op,LINE,Op,Rep(E_0)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a parenthesized expression <c>( E_0 )</c>, then Rep(E) =
+          <c>Rep(E_0)</c>, that is, parenthesized expressions cannot be
+          distinguished from their bodies.</p>
+      </item>
+      <item>
+        <p>If E is a receive expression <c>receive Cc_1 ; ... ; Cc_k end</c>,
+          where each <c>Cc_i</c> is a case clause, then Rep(E) =
+          <c>{'receive',LINE,[Rep(Cc_1), ..., Rep(Cc_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a receive expression
+          <c>receive Cc_1 ; ... ; Cc_k after E_0 -> B_t end</c>,
+          where each <c>Cc_i</c> is a case clause, <c>E_0</c> is an expression,
+          and <c>B_t</c> is a body, then Rep(E) =
+          <c>{'receive',LINE,[Rep(Cc_1), ...,
+          Rep(Cc_k)],Rep(E_0),Rep(B_t)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a record creation
+          <c>#Name{Field_1=E_1, ..., Field_k=E_k}</c>,
+          where each <c>Field_i</c> is an atom or <c>_</c>, then Rep(E) =
+          <c>{record,LINE,Name,[{record_field,LINE,Rep(Field_1),Rep(E_1)},
+          ..., {record_field,LINE,Rep(Field_k),Rep(E_k)}]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a record field access <c>E_0#Name.Field</c>,
+          where <c>Field</c> is an atom, then Rep(E) =
+          <c>{record_field,LINE,Rep(E_0),Name,Rep(Field)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a record field index <c>#Name.Field</c>,
+          where <c>Field</c> is an atom, then Rep(E) =
+          <c>{record_index,LINE,Name,Rep(Field)}</c>.</p></item>
+      <item>
+        <p>If E is a record update
+          <c>E_0#Name{Field_1=E_1, ..., Field_k=E_k}</c>,
+          where each <c>Field_i</c> is an atom, then Rep(E) =
+          <c>{record,LINE,Rep(E_0),Name,[{record_field,LINE,Rep(Field_1),Rep(E_1)},
+      ..., {record_field,LINE,Rep(Field_k),Rep(E_k)}]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a tuple skeleton <c>{E_1, ..., E_k}</c>, then Rep(E) =
+          <c>{tuple,LINE,[Rep(E_1), ..., Rep(E_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a try expression <c>try B catch Tc_1 ; ... ; Tc_k end</c>,
+          where <c>B</c> is a body and each <c>Tc_i</c> is a catch clause,
+          then Rep(E) =
+          <c>{'try',LINE,Rep(B),[],[Rep(Tc_1), ..., Rep(Tc_k)],[]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a try expression
+          <c>try B of Cc_1 ; ... ; Cc_k catch Tc_1 ; ... ; Tc_n end</c>,
+          where <c>B</c> is a body, each <c>Cc_i</c> is a case clause, and
+          each <c>Tc_j</c> is a catch clause, then Rep(E) =
+          <c>{'try',LINE,Rep(B),[Rep(Cc_1), ..., Rep(Cc_k)],[Rep(Tc_1), ...,
+          Rep(Tc_n)],[]}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a try expression <c>try B after A end</c>,
+          where <c>B</c> and <c>A</c> are bodies, then Rep(E) =
+          <c>{'try',LINE,Rep(B),[],[],Rep(A)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a try expression
+          <c>try B of Cc_1 ; ... ; Cc_k after A end</c>,
+          where <c>B</c> and <c>A</c> are a bodies,
+          and each <c>Cc_i</c> is a case clause, then Rep(E) =
+          <c>{'try',LINE,Rep(B),[Rep(Cc_1), ...,
+          Rep(Cc_k)],[],Rep(A)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a try expression
+          <c>try B catch Tc_1 ; ... ; Tc_k after A end</c>,
+          where <c>B</c> and <c>A</c> are bodies,
+          and each <c>Tc_i</c> is a catch clause, then Rep(E) =
+          <c>{'try',LINE,Rep(B),[],[Rep(Tc_1), ...,
+          Rep(Tc_k)],Rep(A)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a try expression
+          <c>try B of Cc_1 ; ... ; Cc_k  catch Tc_1 ; ... ; Tc_n after A
+          end</c>, where <c>B</c> and <c>A</c> are a bodies,
+          each <c>Cc_i</c> is a case clause,
+          and each <c>Tc_j</c> is a catch clause, then Rep(E) =
+          <c>{'try',LINE,Rep(B),[Rep(Cc_1), ..., Rep(Cc_k)],[Rep(Tc_1), ...,
+          Rep(Tc_n)],Rep(A)}</c>.</p>
+      </item>
+      <item>
+        <p>If E is a variable <c>V</c>, then Rep(E) = <c>{var,LINE,A}</c>,
+          where <c>A</c> is an atom with a printname consisting of the same
+          characters as <c>V</c>.</p>
+      </item>
     </list>
 
     <section>
       <title>Qualifiers</title>
-      <p>A qualifier Q is one of the following alternatives:</p>
+      <p>A qualifier Q is one of the following:</p>
+
       <list type="bulleted">
-        <item>If Q is a filter <c>E</c>, where <c>E</c> is an expression, then
-         Rep(Q) = <c>Rep(E)</c>.</item>
-        <item>If Q is a generator <c>P &lt;- E</c>, where <c>P</c> is
-	 a pattern and <c>E</c> is an expression, then
-         Rep(Q) = <c>{generate,LINE,Rep(P),Rep(E)}</c>.</item>
-        <item>If Q is a bit string generator
-	 <c>P &lt;= E</c>, where <c>P</c> is
-	 a pattern and <c>E</c> is an expression, then
-         Rep(Q) = <c>{b_generate,LINE,Rep(P),Rep(E)}</c>.</item>
+        <item>
+          <p>If Q is a filter <c>E</c>, where <c>E</c> is an expression, then
+            Rep(Q) = <c>Rep(E)</c>.</p>
+        </item>
+        <item>
+          <p>If Q is a generator <c>P &lt;- E</c>, where <c>P</c> is
+            a pattern and <c>E</c> is an expression, then Rep(Q) =
+            <c>{generate,LINE,Rep(P),Rep(E)}</c>.</p>
+        </item>
+        <item>
+          <p>If Q is a bitstring generator <c>P &lt;= E</c>, where <c>P</c> is
+            a pattern and <c>E</c> is an expression, then Rep(Q) =
+            <c>{b_generate,LINE,Rep(P),Rep(E)}</c>.</p>
+        </item>
       </list>
     </section>
 
     <section>
-      <title>Bit String Element Type Specifiers</title>
-      <p>A type specifier list TSL for a bit string element is a sequence
+      <title>Bitstring Element Type Specifiers</title>
+      <p>A type specifier list TSL for a bitstring element is a sequence
         of type specifiers <c>TS_1 - ... - TS_k</c>, and
         Rep(TSL) = <c>[Rep(TS_1), ..., Rep(TS_k)]</c>.</p>
+
       <list type="bulleted">
-        <item>If TS is a type specifier <c>A</c>, where <c>A</c> is an atom,
-	 then Rep(TS) = <c>A</c>.</item>
-        <item>If TS is a type specifier <c>A:Value</c>,
-	 where <c>A</c> is an atom and <c>Value</c> is an integer,
-	 then Rep(TS) = <c>{A,Value}</c>.</item>
+        <item>
+          <p>If TS is a type specifier <c>A</c>, where <c>A</c> is an atom,
+            then Rep(TS) = <c>A</c>.</p>
+        </item>
+        <item>
+          <p>If TS is a type specifier <c>A:Value</c>,
+            where <c>A</c> is an atom and <c>Value</c> is an integer,
+            then Rep(TS) = <c>{A,Value}</c>.</p>
+        </item>
       </list>
     </section>
 
     <section>
       <title>Associations</title>
-      <p>An association A is one of the following alternatives:</p>
+      <p>An association A is one of the following:</p>
+
       <list type="bulleted">
-	<item>If A is an association <c>K => V</c>,
-	 then Rep(A) = <c>{map_field_assoc,LINE,Rep(K),Rep(V)}</c>.
-         </item>
-	<item>If A is an association <c>K := V</c>,
-         then Rep(A) = <c>{map_field_exact,LINE,Rep(K),Rep(V)}</c>.
-         </item>
+         <item>
+           <p>If A is an association <c>K => V</c>,
+             then Rep(A) = <c>{map_field_assoc,LINE,Rep(K),Rep(V)}</c>.</p>
+        </item>
+        <item>
+          <p>If A is an association <c>K := V</c>,
+            then Rep(A) = <c>{map_field_exact,LINE,Rep(K),Rep(V)}</c>.</p>
+        </item>
       </list>
     </section>
   </section>
 
   <section>
     <title>Clauses</title>
-    <p>There are function clauses, if clauses, case clauses
+    <p>There are function clauses, if clauses, case clauses,
       and catch clauses.</p>
-    <p>A clause <c>C</c> is one of the following alternatives:</p>
+
+    <p>A clause C is one of the following:</p>
+
     <list type="bulleted">
-      <item>If C is a case clause <c>P -> B</c>,
-       where <c>P</c> is a pattern and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,[Rep(P)],[],Rep(B)}</c>.</item>
-      <item>If C is a case clause <c>P when Gs -> B</c>,
-       where <c>P</c> is a pattern,
-      <c>Gs</c> is a guard sequence and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,[Rep(P)],Rep(Gs),Rep(B)}</c>.</item>
-      <item>If C is a catch clause <c>P -> B</c>,
-       where <c>P</c> is a pattern and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,[Rep({throw,P,_})],[],Rep(B)}</c>.</item>
-      <item>If C is a catch clause <c>X : P -> B</c>,
-       where <c>X</c> is an atomic literal or a variable pattern,
-      <c>P</c> is a pattern, and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,[Rep({X,P,_})],[],Rep(B)}</c>.</item>
-      <item>If C is a catch clause <c>P when Gs -> B</c>,
-       where <c>P</c> is a pattern, <c>Gs</c> is a guard sequence,
-       and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,[Rep({throw,P,_})],Rep(Gs),Rep(B)}</c>.</item>
-      <item>If C is a catch clause <c>X : P when Gs -> B</c>,
-       where <c>X</c> is an atomic literal or a variable pattern,
-      <c>P</c> is a pattern, <c>Gs</c> is a guard sequence,
-       and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,[Rep({X,P,_})],Rep(Gs),Rep(B)}</c>.</item>
-      <item>If C is a function clause <c>( Ps ) -> B</c>,
-       where <c>Ps</c> is a pattern sequence and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,Rep(Ps),[],Rep(B)}</c>.</item>
-      <item>If C is a function clause <c>( Ps ) when Gs -> B</c>,
-       where <c>Ps</c> is a pattern sequence,
-      <c>Gs</c> is a guard sequence and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,Rep(Ps),Rep(Gs),Rep(B)}</c>.</item>
-      <item>If C is an if clause <c>Gs -> B</c>,
-       where <c>Gs</c> is a guard sequence and <c>B</c> is a body, then
-       Rep(C) = <c>{clause,LINE,[],Rep(Gs),Rep(B)}</c>.</item>
+      <item>
+        <p>If C is a case clause <c>P -> B</c>,
+          where <c>P</c> is a pattern and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,[Rep(P)],[],Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is a case clause <c>P when Gs -> B</c>,
+          where <c>P</c> is a pattern,
+          <c>Gs</c> is a guard sequence, and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,[Rep(P)],Rep(Gs),Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is a catch clause <c>P -> B</c>,
+          where <c>P</c> is a pattern and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,[Rep({throw,P,_})],[],Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is a catch clause <c>X : P -> B</c>,
+          where <c>X</c> is an atomic literal or a variable pattern,
+          <c>P</c> is a pattern, and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,[Rep({X,P,_})],[],Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is a catch clause <c>P when Gs -> B</c>,
+          where <c>P</c> is a pattern, <c>Gs</c> is a guard sequence,
+          and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,[Rep({throw,P,_})],Rep(Gs),Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is a catch clause <c>X : P when Gs -> B</c>,
+          where <c>X</c> is an atomic literal or a variable pattern,
+          <c>P</c> is a pattern, <c>Gs</c> is a guard sequence,
+          and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,[Rep({X,P,_})],Rep(Gs),Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is a function clause <c>( Ps ) -> B</c>,
+          where <c>Ps</c> is a pattern sequence and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,Rep(Ps),[],Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is a function clause <c>( Ps ) when Gs -> B</c>,
+          where <c>Ps</c> is a pattern sequence,
+          <c>Gs</c> is a guard sequence and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,Rep(Ps),Rep(Gs),Rep(B)}</c>.</p>
+      </item>
+      <item>
+        <p>If C is an if clause <c>Gs -> B</c>,
+          where <c>Gs</c> is a guard sequence and <c>B</c> is a body, then
+          Rep(C) = <c>{clause,LINE,[],Rep(Gs),Rep(B)}</c>.</p>
+      </item>
     </list>
   </section>
 
@@ -460,205 +650,292 @@
     <title>Guards</title>
     <p>A guard sequence Gs is a sequence of guards <c>G_1; ...; G_k</c>, and
       Rep(Gs) = <c>[Rep(G_1), ..., Rep(G_k)]</c>. If the guard sequence is
-      empty, Rep(Gs) = <c>[]</c>.</p>
-    <p>A guard G is a nonempty sequence of guard tests
+      empty, then Rep(Gs) = <c>[]</c>.</p>
+
+    <p>A guard G is a non-empty sequence of guard tests
       <c>Gt_1, ..., Gt_k</c>, and Rep(G) =
       <c>[Rep(Gt_1), ..., Rep(Gt_k)]</c>.</p>
-    <p>A guard test <c>Gt</c> is one of the following alternatives:</p>
+
+    <p>A guard test Gt is one of the following:</p>
+
     <list type="bulleted">
-      <item>If Gt is an atomic literal <c>L</c>, then Rep(Gt) = Rep(L).</item>
-      <item>If Gt is a bit string constructor
-       <c>&lt;&lt;Gt_1:Size_1/TSL_1, ..., Gt_k:Size_k/TSL_k>></c>,
-       where each <c>Size_i</c> is a guard test and each
-       <c>TSL_i</c> is a type specificer list, then
-       Rep(Gt) = <c>{bin,LINE,[{bin_element,LINE,Rep(Gt_1),Rep(Size_1),Rep(TSL_1)}, ..., {bin_element,LINE,Rep(Gt_k),Rep(Size_k),Rep(TSL_k)}]}</c>.
-       For Rep(TSL), see above.
-       An omitted <c>Size_i</c> is represented by <c>default</c>.
-       An omitted <c>TSL_i</c> is represented by <c>default</c>.</item>
-      <item>If Gt is a cons skeleton <c>[Gt_h | Gt_t]</c>, then
-       Rep(Gt) = <c>{cons,LINE,Rep(Gt_h),Rep(Gt_t)}</c>.</item>
-      <item>If Gt is a function call <c>A(Gt_1, ..., Gt_k)</c>,
-       where <c>A</c> is an atom, then Rep(Gt) =
-       <c>{call,LINE,Rep(A),[Rep(Gt_1), ..., Rep(Gt_k)]}</c>.</item>
-      <item>If Gt is a function call <c>A_m:A(Gt_1, ..., Gt_k)</c>,
-       where <c>A_m</c> is the atom <c>erlang</c> and <c>A</c> is
-       an atom or an operator, then Rep(Gt) =
-       <c>{call,LINE,{remote,LINE,Rep(A_m),Rep(A)},[Rep(Gt_1), ..., Rep(Gt_k)]}</c>.</item>
-      <item>If Gt is a map creation <c>#{A_1, ..., A_k}</c>,
-       where each <c>A_i</c> is an association <c>Gt_i_1 => Gt_i_2</c>
-       or <c>Gt_i_1 := Gt_i_2</c>, then Rep(Gt) =
-       <c>{map,LINE,[Rep(A_1), ..., Rep(A_k)]}</c>. For Rep(A), see
-       above.</item>
-      <item>If Gt is a map update <c>Gt_0#{A_1, ..., A_k}</c>, where each
-       <c>A_i</c> is an association <c>Gt_i_1 => Gt_i_2</c>
-       or <c>Gt_i_1 := Gt_i_2</c>, then Rep(Gt) =
-       <c>{map,LINE,Rep(Gt_0),[Rep(A_1), ..., Rep(A_k)]}</c>.
-       For Rep(A), see above.</item>
-      <item>If Gt is nil, <c>[]</c>,
-       then Rep(Gt) = <c>{nil,LINE}</c>.</item>
-      <item>If Gt is an operator guard test <c>Gt_1 Op Gt_2</c>,
-       where <c>Op</c> is a binary operator other than the match
-       operator <c>=</c>, then
-       Rep(Gt) = <c>{op,LINE,Op,Rep(Gt_1),Rep(Gt_2)}</c>.</item>
-      <item>If Gt is an operator guard test <c>Op Gt_0</c>,
-       where <c>Op</c> is a unary operator, then
-       Rep(Gt) = <c>{op,LINE,Op,Rep(Gt_0)}</c>.</item>
-      <item>If Gt is a parenthesized guard test <c>( Gt_0 )</c>, then
-       Rep(Gt) = <c>Rep(Gt_0)</c>, that is, parenthesized
-       guard tests cannot be distinguished from their bodies.</item>
-      <item>If Gt is a record creation
-       <c>#Name{Field_1=Gt_1, ..., Field_k=Gt_k}</c>,
-       where each <c>Field_i</c> is an atom or <c>_</c>, then Rep(Gt) =
-      <c>{record,LINE,Name,[{record_field,LINE,Rep(Field_1),Rep(Gt_1)}, ..., {record_field,LINE,Rep(Field_k),Rep(Gt_k)}]}</c>.</item>
-      <item>If Gt is  a record field access <c>Gt_0#Name.Field</c>,
-       where <c>Field</c> is an atom, then
-       Rep(Gt) = <c>{record_field,LINE,Rep(Gt_0),Name,Rep(Field)}</c>.</item>
-      <item>If Gt is a record field index <c>#Name.Field</c>,
-       where <c>Field</c> is an atom, then
-       Rep(Gt) = <c>{record_index,LINE,Name,Rep(Field)}</c>.</item>
-      <item>If Gt is a tuple skeleton <c>{Gt_1, ..., Gt_k}</c>, then
-       Rep(Gt) = <c>{tuple,LINE,[Rep(Gt_1), ..., Rep(Gt_k)]}</c>.</item>
-      <item>If Gt is a variable pattern <c>V</c>, then
-       Rep(Gt) = <c>{var,LINE,A}</c>, where A is an atom with
-       a printname consisting of the same characters as <c>V</c>.</item>
+      <item>
+        <p>If Gt is an atomic literal <c>L</c>, then Rep(Gt) = Rep(L).</p>
+      </item>
+      <item>
+        <p>If Gt is a bitstring constructor
+          <c>&lt;&lt;Gt_1:Size_1/TSL_1, ..., Gt_k:Size_k/TSL_k>></c>,
+          where each <c>Size_i</c> is a guard test and each
+          <c>TSL_i</c> is a type specificer list, then Rep(Gt) =
+          <c>{bin,LINE,[{bin_element,LINE,Rep(Gt_1),Rep(Size_1),Rep(TSL_1)},
+          ..., {bin_element,LINE,Rep(Gt_k),Rep(Size_k),Rep(TSL_k)}]}</c>.
+          For Rep(TSL), see above.
+          An omitted <c>Size_i</c> is represented by <c>default</c>.
+          An omitted <c>TSL_i</c> is represented by <c>default</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a cons skeleton <c>[Gt_h | Gt_t]</c>, then Rep(Gt) =
+          <c>{cons,LINE,Rep(Gt_h),Rep(Gt_t)}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a function call <c>A(Gt_1, ..., Gt_k)</c>,
+          where <c>A</c> is an atom, then Rep(Gt) =
+          <c>{call,LINE,Rep(A),[Rep(Gt_1), ..., Rep(Gt_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a function call <c>A_m:A(Gt_1, ..., Gt_k)</c>,
+          where <c>A_m</c> is the atom <c>erlang</c> and <c>A</c> is
+          an atom or an operator, then Rep(Gt) =
+          <c>{call,LINE,{remote,LINE,Rep(A_m),Rep(A)},[Rep(Gt_1), ...,
+          Rep(Gt_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a map creation <c>#{A_1, ..., A_k}</c>,
+          where each <c>A_i</c> is an association <c>Gt_i_1 => Gt_i_2</c>
+          or <c>Gt_i_1 := Gt_i_2</c>, then Rep(Gt) =
+          <c>{map,LINE,[Rep(A_1), ..., Rep(A_k)]}</c>.
+          For Rep(A), see above.</p>
+      </item>
+      <item>
+        <p>If Gt is a map update <c>Gt_0#{A_1, ..., A_k}</c>,
+          where each <c>A_i</c> is an association <c>Gt_i_1 => Gt_i_2</c>
+          or <c>Gt_i_1 := Gt_i_2</c>, then Rep(Gt) =
+          <c>{map,LINE,Rep(Gt_0),[Rep(A_1), ..., Rep(A_k)]}</c>.
+          For Rep(A), see above.</p>
+      </item>
+      <item>
+        <p>If Gt is nil, <c>[]</c>, then Rep(Gt) = <c>{nil,LINE}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is an operator guard test <c>Gt_1 Op Gt_2</c>,
+          where <c>Op</c> is a binary operator other than match
+          operator <c>=</c>, then Rep(Gt) =
+          <c>{op,LINE,Op,Rep(Gt_1),Rep(Gt_2)}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is an operator guard test <c>Op Gt_0</c>,
+          where <c>Op</c> is a unary operator, then Rep(Gt) =
+          <c>{op,LINE,Op,Rep(Gt_0)}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a parenthesized guard test <c>( Gt_0 )</c>, then Rep(Gt) =
+          <c>Rep(Gt_0)</c>, that is, parenthesized
+          guard tests cannot be distinguished from their bodies.</p>
+      </item>
+      <item>
+        <p>If Gt is a record creation
+          <c>#Name{Field_1=Gt_1, ..., Field_k=Gt_k}</c>,
+           where each <c>Field_i</c> is an atom or <c>_</c>, then Rep(Gt) =
+           <c>{record,LINE,Name,[{record_field,LINE,Rep(Field_1),Rep(Gt_1)},
+           ..., {record_field,LINE,Rep(Field_k),Rep(Gt_k)}]}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is  a record field access <c>Gt_0#Name.Field</c>,
+          where <c>Field</c> is an atom, then Rep(Gt) =
+          <c>{record_field,LINE,Rep(Gt_0),Name,Rep(Field)}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a record field index <c>#Name.Field</c>,
+          where <c>Field</c> is an atom, then Rep(Gt) =
+          <c>{record_index,LINE,Name,Rep(Field)}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a tuple skeleton <c>{Gt_1, ..., Gt_k}</c>, then Rep(Gt) =
+          <c>{tuple,LINE,[Rep(Gt_1), ..., Rep(Gt_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If Gt is a variable pattern <c>V</c>, then Rep(Gt) =
+          <c>{var,LINE,A}</c>, where A is an atom with
+          a printname consisting of the same characters as <c>V</c>.</p>
+      </item>
     </list>
-    <p>Note that every guard test has the same source form as some expression,
-      and is represented the same way as the corresponding expression.</p>
+
+    <p>Notice that every guard test has the same source form as some expression,
+      and is represented in the same way as the corresponding expression.</p>
   </section>
 
   <section>
     <title>Types</title>
     <list type="bulleted">
-      <item>If T is an annotated type <c>A :: T_0</c>,
-       where <c>A</c> is a variable, then Rep(T) =
-       <c>{ann_type,LINE,[Rep(A),Rep(T_0)]}</c>.</item>
-      <item>If T is an atom or integer literal L, then Rep(T) = Rep(L).
-      </item>
-      <item>If T is a bit string type <c>&lt;&lt;_:M,_:_*N>></c>,
-       where <c>M</c> and <c>N</c> are singleton integer types, then Rep(T) =
-       <c>{type,LINE,binary,[Rep(M),Rep(N)]}</c>.</item>
-      <item>If T is the empty list type <c>[]</c>, then Rep(T) =
-       <c>{type,Line,nil,[]}</c>.</item>
-      <item>If T is a fun type <c>fun()</c>, then Rep(T) =
-       <c>{type,LINE,'fun',[]}</c>.</item>
-      <item>If T is a fun type <c>fun((...) -> T_0)</c>, then
-       Rep(T) = <c>{type,LINE,'fun',[{type,LINE,any},Rep(T_0)]}</c>.
-       </item>
-      <item>If T is a fun type <c>fun(Ft)</c>, where
-       <c>Ft</c> is a function type,
-       then Rep(T) = <c>Rep(Ft)</c>. For Rep(Ft), see below.</item>
-      <item>If T is an integer range type <c>L .. H</c>,
-       where <c>L</c> and <c>H</c> are singleton integer types, then
-       Rep(T) = <c>{type,LINE,range,[Rep(L),Rep(H)]}</c>.</item>
-      <item>If T is a map type <c>map()</c>, then Rep(T) =
-       <c>{type,LINE,map,any}</c>.</item>
-      <item>If T is a map type <c>#{A_1, ..., A_k}</c>, where each
-       <c>A_i</c> is an association type, then Rep(T) =
-       <c>{type,LINE,map,[Rep(A_1), ..., Rep(A_k)]}</c>.
-       For Rep(A), see below.</item>
-      <item>If T is an operator type <c>T_1 Op T_2</c>,
-       where <c>Op</c> is a binary operator (this is an occurrence of
-       an expression that can be evaluated to an integer at compile
-       time), then
-       Rep(T) = <c>{op,LINE,Op,Rep(T_1),Rep(T_2)}</c>.</item>
-      <item>If T is an operator type <c>Op T_0</c>, where <c>Op</c> is a
-       unary operator (this is an occurrence of
-       an expression that can be evaluated to an integer at compile time),
-       then Rep(T) = <c>{op,LINE,Op,Rep(T_0)}</c>.</item>
-      <item>If T is <c>( T_0 )</c>, then Rep(T) = <c>Rep(T_0)</c>,
-       that is, parenthesized types cannot be distinguished from their
-       bodies.</item>
-      <item>If T is a predefined (or built-in) type <c>N(T_1, ..., T_k)</c>,
-       then Rep(T) =
-       <c>{type,LINE,N,[Rep(T_1), ..., Rep(T_k)]}</c>.</item>
-      <item>If T is a record type <c>#Name{F_1, ..., F_k}</c>,
-       where each <c>F_i</c> is a record field type, then Rep(T) =
-       <c>{type,LINE,record,[Rep(Name),Rep(F_1), ..., Rep(F_k)]}</c>.
-       For Rep(F), see below.</item>
-      <item>If T is a remote type <c>M:N(T_1, ..., T_k)</c>, then Rep(T) =
-       <c>{remote_type,LINE,[Rep(M),Rep(N),[Rep(T_1), ..., Rep(T_k)]]}</c>.
-       </item>
-      <item>If T is a tuple type <c>tuple()</c>, then Rep(T) =
-       <c>{type,LINE,tuple,any}</c>.</item>
-      <item>If T is a tuple type <c>{T_1, ..., T_k}</c>, then Rep(T) =
-       <c>{type,LINE,tuple,[Rep(T_1), ..., Rep(T_k)]}</c>.</item>
-      <item>If T is a type union <c>T_1 | ... | T_k</c>, then Rep(T) =
-       <c>{type,LINE,union,[Rep(T_1), ..., Rep(T_k)]}</c>.</item>
-      <item>If T is a type variable <c>V</c>, then Rep(T) =
-       <c>{var,LINE,A}</c>, where <c>A</c> is an atom with a printname
-       consisting of the same characters as <c>V</c>. A type variable
-       is any variable except underscore (<c>_</c>).</item>
-      <item>If T is a user-defined type <c>N(T_1, ..., T_k)</c>,
-       then Rep(T) =
-       <c>{user_type,LINE,N,[Rep(T_1), ..., Rep(T_k)]}</c>.</item>
+      <item>
+        <p>If T is an annotated type <c>A :: T_0</c>,
+          where <c>A</c> is a variable, then Rep(T) =
+          <c>{ann_type,LINE,[Rep(A),Rep(T_0)]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is an atom or integer literal L, then Rep(T) = Rep(L).</p>
+      </item>
+      <item>
+        <p>If T is a bitstring type <c>&lt;&lt;_:M,_:_*N>></c>,
+          where <c>M</c> and <c>N</c> are singleton integer types, then Rep(T) =
+          <c>{type,LINE,binary,[Rep(M),Rep(N)]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is the empty list type <c>[]</c>, then Rep(T) =
+          <c>{type,Line,nil,[]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a fun type <c>fun()</c>, then Rep(T) =
+          <c>{type,LINE,'fun',[]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a fun type <c>fun((...) -> T_0)</c>, then Rep(T) =
+          <c>{type,LINE,'fun',[{type,LINE,any},Rep(T_0)]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a fun type <c>fun(Ft)</c>, where
+          <c>Ft</c> is a function type, then Rep(T) = <c>Rep(Ft)</c>.
+          For Rep(Ft), see below.</p>
+      </item>
+      <item>
+        <p>If T is an integer range type <c>L .. H</c>,
+          where <c>L</c> and <c>H</c> are singleton integer types, then Rep(T) =
+          <c>{type,LINE,range,[Rep(L),Rep(H)]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a map type <c>map()</c>, then Rep(T) =
+          <c>{type,LINE,map,any}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a map type <c>#{A_1, ..., A_k}</c>, where each
+          <c>A_i</c> is an association type, then Rep(T) =
+          <c>{type,LINE,map,[Rep(A_1), ..., Rep(A_k)]}</c>.
+          For Rep(A), see below.</p>
+      </item>
+      <item>
+        <p>If T is an operator type <c>T_1 Op T_2</c>,
+          where <c>Op</c> is a binary operator (this is an occurrence of
+          an expression that can be evaluated to an integer at compile
+          time), then Rep(T) =
+          <c>{op,LINE,Op,Rep(T_1),Rep(T_2)}</c>.</p>
+      </item>
+      <item>
+        <p>If T is an operator type <c>Op T_0</c>, where <c>Op</c> is a
+          unary operator (this is an occurrence of an expression that can
+          be evaluated to an integer at compile time), then Rep(T) =
+          <c>{op,LINE,Op,Rep(T_0)}</c>.</p>
+      </item>
+      <item>
+        <p>If T is <c>( T_0 )</c>, then Rep(T) = <c>Rep(T_0)</c>, that is,
+          parenthesized types cannot be distinguished from their bodies.</p>
+      </item>
+      <item>
+        <p>If T is a predefined (or built-in) type <c>N(T_1, ..., T_k)</c>,
+          then Rep(T) = <c>{type,LINE,N,[Rep(T_1), ..., Rep(T_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a record type <c>#Name{F_1, ..., F_k}</c>,
+          where each <c>F_i</c> is a record field type, then Rep(T) =
+          <c>{type,LINE,record,[Rep(Name),Rep(F_1), ..., Rep(F_k)]}</c>.
+          For Rep(F), see below.</p>
+      </item>
+      <item>
+        <p>If T is a remote type <c>M:N(T_1, ..., T_k)</c>, then Rep(T) =
+          <c>{remote_type,LINE,[Rep(M),Rep(N),[Rep(T_1), ...,
+          Rep(T_k)]]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a tuple type <c>tuple()</c>, then Rep(T) =
+          <c>{type,LINE,tuple,any}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a tuple type <c>{T_1, ..., T_k}</c>, then Rep(T) =
+          <c>{type,LINE,tuple,[Rep(T_1), ..., Rep(T_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a type union <c>T_1 | ... | T_k</c>, then Rep(T) =
+          <c>{type,LINE,union,[Rep(T_1), ..., Rep(T_k)]}</c>.</p>
+      </item>
+      <item>
+        <p>If T is a type variable <c>V</c>, then Rep(T) =
+          <c>{var,LINE,A}</c>, where <c>A</c> is an atom with a printname
+          consisting of the same characters as <c>V</c>. A type variable
+          is any variable except underscore (<c>_</c>).</p>
+      </item>
+      <item>
+        <p>If T is a user-defined type <c>N(T_1, ..., T_k)</c>, then Rep(T) =
+          <c>{user_type,LINE,N,[Rep(T_1), ..., Rep(T_k)]}</c>.</p>
+      </item>
     </list>
 
     <section>
       <title>Function Types</title>
-      <p>A function type Ft is one of the following alternatives:</p>
+      <p>A function type Ft is one of the following:</p>
+
       <list type="bulleted">
-       <item>If Ft is a constrained function type <c>Ft_1 when Fc</c>,
-	where <c>Ft_1</c> is a function type and
-	<c>Fc</c> is a function constraint, then Rep(T) =
-	<c>{type,LINE,bounded_fun,[Rep(Ft_1),Rep(Fc)]}</c>.
-        For Rep(Fc), see below.</item>
-       <item>If Ft is a function type <c>(T_1, ..., T_n) -> T_0</c>,
-        where each <c>T_i</c> is a type, then
-	Rep(Ft) = <c>{type,LINE,'fun',[{type,LINE,product,[Rep(T_1),
-	..., Rep(T_n)]},Rep(T_0)]}</c>.</item>
+        <item>
+          <p>If Ft is a constrained function type <c>Ft_1 when Fc</c>,
+            where <c>Ft_1</c> is a function type and
+            <c>Fc</c> is a function constraint, then Rep(T) =
+            <c>{type,LINE,bounded_fun,[Rep(Ft_1),Rep(Fc)]}</c>.
+            For Rep(Fc), see below.</p>
+        </item>
+        <item>
+          <p>If Ft is a function type <c>(T_1, ..., T_n) -> T_0</c>,
+            where each <c>T_i</c> is a type, then Rep(Ft) =
+            <c>{type,LINE,'fun',[{type,LINE,product,[Rep(T_1), ...,
+            Rep(T_n)]},Rep(T_0)]}</c>.</p>
+        </item>
       </list>
     </section>
 
     <section>
       <title>Function Constraints</title>
-      <p>A function constraint Fc is a nonempty sequence of constraints
-	<c>C_1, ..., C_k</c>, and
-	Rep(Fc) = <c>[Rep(C_1), ..., Rep(C_k)]</c>.</p>
+      <p>A function constraint Fc is a non-empty sequence of constraints
+        <c>C_1, ..., C_k</c>, and
+        Rep(Fc) = <c>[Rep(C_1), ..., Rep(C_k)]</c>.</p>
+
       <list type="bulleted">
-       <item>If C is a constraint <c>is_subtype(V, T)</c> or <c>V :: T</c>,
-        where <c>V</c> is a type variable and <c>T</c> is a type, then
-        Rep(C) = <c>{type,LINE,constraint,[{atom,LINE,is_subtype},[Rep(V),Rep(T)]]}</c>.
-       </item>
+        <item>If C is a constraint <c>is_subtype(V, T)</c> or <c>V :: T</c>,
+          where <c>V</c> is a type variable
+          and <c>T</c> is a type, then Rep(C) =
+          <c>{type,LINE,constraint,[{atom,LINE,is_subtype},[Rep(V),Rep(T)]]}</c>.
+        </item>
       </list>
     </section>
 
     <section>
       <title>Association Types</title>
       <list type="bulleted">
-       <item>If A is an association type <c>K => V</c>, where
-        <c>K</c> and <c>V</c> are types, then Rep(A) =
-        <c>{type,LINE,map_field_assoc,[Rep(K),Rep(V)]}</c>.</item>
-       <item>If A is an association type <c>K := V</c>, where
-        <c>K</c> and <c>V</c> are types, then Rep(A) =
-        <c>{type,LINE,map_field_exact,[Rep(K),Rep(V)]}</c>.</item>
+        <item>
+          <p>If A is an association type <c>K => V</c>,
+            where <c>K</c> and <c>V</c> are types, then Rep(A) =
+            <c>{type,LINE,map_field_assoc,[Rep(K),Rep(V)]}</c>.</p>
+        </item>
+        <item>
+          <p>If A is an association type <c>K := V</c>,
+            where <c>K</c> and <c>V</c> are types, then Rep(A) =
+            <c>{type,LINE,map_field_exact,[Rep(K),Rep(V)]}</c>.</p>
+        </item>
       </list>
     </section>
 
     <section>
       <title>Record Field Types</title>
       <list type="bulleted">
-       <item>If F is a record field type <c>Name :: Type</c>,
-	where <c>Type</c> is a type, then Rep(F) =
-	<c>{type,LINE,field_type,[Rep(Name),Rep(Type)]}</c>.</item>
+        <item>If F is a record field type <c>Name :: Type</c>,
+          where <c>Type</c> is a type, then Rep(F) =
+          <c>{type,LINE,field_type,[Rep(Name),Rep(Type)]}</c>.
+        </item>
       </list>
     </section>
   </section>
 
   <section>
-    <title>The Abstract Format After Preprocessing</title>
-    <p>The compilation option <c>debug_info</c> can be given to the
+    <title>The Abstract Format after Preprocessing</title>
+    <p>The compilation option <c>debug_info</c> can be specified to the
       compiler to have the abstract code stored in
-      the <c>abstract_code</c> chunk in the BEAM file
+      the <c>abstract_code</c> chunk in the Beam file
       (for debugging purposes).</p>
-    <p>In OTP R9C and later, the <c>abstract_code</c> chunk will
-      contain</p>
-    <p><c>{raw_abstract_v1,AbstractCode}</c></p>
-    <p>where <c>AbstractCode</c> is the abstract code as described
-      in this document.</p>
-    <p>In releases of OTP prior to R9C, the abstract code after some more
-      processing was stored in the BEAM file. The first element of the
-      tuple would be either <c>abstract_v1</c> (R7B) or <c>abstract_v2</c>
-      (R8B).</p>
+
+    <p>As from Erlang/OTP R9C, the <c>abstract_code</c> chunk contains
+      <c>{raw_abstract_v1,AbstractCode}</c>, where <c>AbstractCode</c> is the
+      abstract code as described in this section.</p>
+
+    <p>In OTP releases before R9C, the abstract code after some more
+      processing was stored in the Beam file. The first element of the
+      tuple would be either <c>abstract_v1</c> (in OTP R7B) or
+      <c>abstract_v2</c> (in OTP R8B).</p>
   </section>
 </chapter>
 
diff --git a/erts/doc/src/alt_dist.xml b/erts/doc/src/alt_dist.xml
index e283acc1b4..67d30a03c2 100644
--- a/erts/doc/src/alt_dist.xml
+++ b/erts/doc/src/alt_dist.xml
@@ -22,7 +22,8 @@
 
     </legalnotice>
 
-    <title>How to implement an alternative carrier for  the Erlang distribution</title>
+    <title>How to Implement an Alternative Carrier for the Erlang Distribution
+    </title>
     <prepared>Patrik Nyblom</prepared>
     <responsible></responsible>
     <docno></docno>
@@ -32,203 +33,271 @@
     <rev>PA2</rev>
     <file>alt_dist.xml</file>
   </header>
-  <p>This document describes how one can implement ones own carrier
+  <p>This section describes how to implement an own carrier
     protocol for the Erlang distribution. The distribution is normally
-    carried by the TCP/IP protocol. What's explained here is the method for 
-    replacing TCP/IP with another protocol. </p>
-  <p>The document is a step by step explanation of the <c><![CDATA[uds_dist]]></c> example 
-    application (seated in the kernel applications <c><![CDATA[examples]]></c> directory). 
-    The <c><![CDATA[uds_dist]]></c> application implements distribution over Unix domain 
-    sockets and is written for the Sun Solaris 2 operating environment. The 
-    mechanisms are however general and applies to any operating system Erlang 
-    runs on. The reason the C code is not made portable, is simply readability.</p>
-  <note><p>This document was written a long time ago. Most of it is still
-           valid, but some things have changed since it was first written.
-	   Most notably the driver interface. There have been some updates
-	   to the documentation of the driver presented in this documentation,
-	   but more could be done and are planned for the future. The
-	   reader is encouraged to also read the
-	   <seealso marker="erl_driver">erl_driver</seealso>, and the
-	   <seealso marker="erl_driver">driver_entry</seealso> documentation.
-   </p></note>
+    carried by TCP/IP. Here is explained a method for replacing TCP/IP
+    with another protocol.</p>
+
+  <p>The section is a step-by-step explanation of the
+    <c><![CDATA[uds_dist]]></c> example application (in the
+    <c>Kernel</c> application <c><![CDATA[examples]]></c> directory). The
+    <c><![CDATA[uds_dist]]></c> application implements distribution over Unix
+    domain sockets and is written for the Sun Solaris 2 operating environment.
+    The mechanisms are however general and apply to any operating system Erlang
+    runs on. The reason the C code is not made portable, is simply
+    readability.</p>
+
+  <note>
+    <p>This section was written a long time ago. Most of it is still
+      valid, but some things have changed since then.
+      Most notably is the driver interface. Some updates have been made
+      to the documentation of the driver presented here,
+      but more can be done and is planned for the future.
+      The reader is encouraged to read the
+      <seealso marker="erl_driver"><c>erl_driver</c></seealso> and
+      <seealso marker="driver_entry"><c>driver_entry</c></seealso>
+      documentation also.</p>
+  </note>
 
   <section>
     <title>Introduction</title>
-    <p>To implement a new carrier for the Erlang distribution, one must first
-      make the protocol available to the Erlang machine, which involves writing 
-      an Erlang driver. There is no way one can use a port program,
-      there <em>has</em> to
-      be an Erlang driver. Erlang drivers can either be statically
-      linked
-      to the emulator, which can be an alternative when using the open source
-      distribution of Erlang, or dynamically loaded into the Erlang machines
-      address space, which is the only alternative if a precompiled version of 
-      Erlang is to be used. </p>
-    <p>Writing an Erlang driver is by no means easy. The driver is written 
-      as a couple of call-back functions called by the Erlang emulator when
-      data is sent to the driver or the driver has any data available on a file
-      descriptor. As the driver call-back routines execute in the main
-      thread of the Erlang machine, the call-back functions can perform
-      no blocking activity whatsoever. The call-backs should only set up
-      file descriptors for waiting and/or read/write available data. All
-      I/O has to be non blocking. Driver call-backs are however executed
-      in sequence, why a global state can safely be updated within the
-      routines. </p>
-    <p>When the driver is implemented, one would preferably write an
-      Erlang interface for the driver to be able to test the
-      functionality of the driver separately. This interface can then
-      be used by the distribution module which will cover the details of
-      the protocol from the <c><![CDATA[net_kernel]]></c>. The easiest path is to
-      mimic the <c><![CDATA[inet]]></c> and <c><![CDATA[inet_tcp]]></c> interfaces, but a lot of
-      functionality in those modules need not be implemented. In the
-      example application, only a few of the usual interfaces are
-      implemented, and they are much simplified.</p>
-    <p>When the protocol is available to Erlang through a driver and an
-      Erlang interface module, a distribution module can be
-      written. The distribution module is a module with well defined
-      call-backs, much like a <c><![CDATA[gen_server]]></c> (there is no compiler support
-      for checking the call-backs though). The details of finding other
-      nodes (i.e. talking to epmd or something similar), creating a
-      listen port (or similar), connecting to other nodes and performing
-      the handshakes/cookie verification are all implemented by this
-      module. There is however a utility module, <c><![CDATA[dist_util]]></c>, that
-      will do most of the hard work of handling handshakes, cookies,
-      timers and ticking. Using <c><![CDATA[dist_util]]></c> makes implementing a
-      distribution module much easier and that's what we are doing in
-      the example application.</p>
-    <p>The last step is to create boot scripts to make the protocol
-      implementation available at boot time. The implementation can be
-      debugged by starting the distribution when all of the system is
-      running, but in a real system the distribution should start very
-      early, why a boot-script and some command line parameters are
-      necessary. This last step also implies that the Erlang code in the 
-      interface and distribution modules is written in such a way that
-      it can be run in the startup phase. Most notably there can be no
-      calls to the <c><![CDATA[application]]></c> module or to any modules not
-      loaded at boot-time (i.e. only <c><![CDATA[kernel]]></c>, <c><![CDATA[stdlib]]></c> and the
-      application itself can be used).</p>
+    <p>To implement a new carrier for the Erlang distribution, the main
+      steps are as follows.</p>
+
+    <section>
+      <title>Writing an Erlang Driver</title>
+      <p>First, the protocol must be available to the Erlang machine, which
+        involves writing an Erlang driver. A port program cannot be used,
+        an Erlang driver is required. Erlang drivers can be:</p>
+
+      <list type="bulleted">
+        <item>
+          <p>Statically linked to the emulator, which can be an alternative
+            when using the open source distribution of Erlang, or</p>
+        </item>
+        <item>
+          <p>Dynamically loaded into the Erlang machines address space,
+            which is the only alternative if a precompiled version of 
+            Erlang is to be used</p>
+        </item>
+      </list>
+
+      <p>Writing an Erlang driver is not easy. The driver is written
+        as some callback functions called by the Erlang emulator when
+        data is sent to the driver, or the driver has any data available on
+        a file descriptor. As the driver callback routines execute in the main
+        thread of the Erlang machine, the callback functions can perform
+        no blocking activity whatsoever. The callbacks are only to set up
+        file descriptors for waiting and/or read/write available data. All
+        I/O must be non-blocking. Driver callbacks are however executed
+        in sequence, why a global state can safely be updated within the
+        routines.</p>
+    </section>
+
+    <section>
+      <title>Writing an Erlang Interface for the Driver</title>
+      <p>When the driver is implemented, one would preferably write an
+        Erlang interface for the driver to be able to test the
+        functionality of the driver separately. This interface can then
+        be used by the distribution module, which will cover the details of
+        the protocol from the <c><![CDATA[net_kernel]]></c>.</p>
+
+      <p>The easiest path
+        is to mimic the <c><![CDATA[inet]]></c> and <c><![CDATA[inet_tcp]]></c>
+        interfaces, but not much
+        functionality in those modules needs to be implemented. In the
+        example application, only a few of the usual interfaces are
+        implemented, and they are much simplified.</p>
+    </section>
+
+    <section>
+      <title>Writing a Distribution Module</title>
+      <p>When the protocol is available to Erlang through a driver and an
+        Erlang interface module, a distribution module can be written.
+        The distribution module is a module with well-defined callbacks,
+        much like a <c><![CDATA[gen_server]]></c> (there is no compiler support
+        for checking the callbacks, though). This module implements:</p>
+
+      <list type="bulleted">
+        <item>The details of finding other nodes (that is, talking to
+          <c>epmd</c> or something similar)</item>
+        <item>Creating a listen port (or similar)</item>
+        <item>Connecting to other nodes</item>
+        <item>Performing the handshakes/cookie verification</item>
+      </list>
+
+      <p>There is however a utility module, <c><![CDATA[dist_util]]></c>, which
+        does most of the hard work of handling handshakes, cookies, timers,
+        and ticking. Using <c><![CDATA[dist_util]]></c> makes implementing a
+        distribution module much easier and that is done in
+        the example application.</p>
+    </section>
+
+    <section>
+      <title>Creating Boot Scripts</title>
+      <p>The last step is to create boot scripts to make the protocol
+        implementation available at boot time. The implementation can be
+        debugged by starting the distribution when all the system is
+        running, but in a real system the distribution is to start very
+        early, why a boot script and some command-line parameters are
+        necessary.</p>
+
+      <p>This step also implies that the Erlang code in the
+        interface and distribution modules is written in such a way that
+        it can be run in the startup phase. In particular, there can be no
+        calls to the <c><![CDATA[application]]></c> module or to any modules
+        not loaded at boot time. That is, only <c><![CDATA[Kernel]]></c>,
+        <c><![CDATA[STDLIB]]></c>, and the application itself can be used.</p>
+    </section>
   </section>
 
   <section>
-    <title>The driver</title>
-    <p>Although Erlang drivers in general may be beyond the scope of this
-      document, a brief introduction seems to be in place.</p>
+    <title>The Driver</title>
+    <p>Although Erlang drivers in general can be beyond the scope of this
+      section, a brief introduction seems to be in place.</p>
 
     <section>
-      <title>Drivers in general</title>
+      <title>Drivers in General</title>
       <p>An Erlang driver is a native code module written in C (or
-        assembler) which serves as an interface for some special operating
+        assembler), which serves as an interface for some special operating
         system service. This is a general mechanism that is used
         throughout the Erlang emulator for all kinds of I/O. An Erlang
         driver can be dynamically linked (or loaded) to the Erlang
         emulator at runtime by using the <c><![CDATA[erl_ddll]]></c> Erlang
         module. Some of the drivers in OTP are however statically linked
-        to the runtime system, but that's more an optimization than a
+        to the runtime system, but that is more an optimization than a
         necessity.</p>
-      <p>The driver data-types and the functions available to the driver
-        writer are defined in the header file <c><![CDATA[erl_driver.h]]></c> (there
-        is also an deprecated version called <c><![CDATA[driver.h]]></c>, don't use
-        that one.) seated in Erlang's include directory (and in
-        $ERL_TOP/erts/emulator/beam in the source code
-        distribution). Refer to that file for function prototypes etc.</p>
+
+      <p>The driver data types and the functions available to the driver
+        writer are defined in header file <c><![CDATA[erl_driver.h]]></c> (there
+        is also a deprecated version called <c><![CDATA[driver.h]]></c>, do not
+        use that one) seated in Erlang's include directory (and in
+        <c>$ERL_TOP/erts/emulator/beam</c> in the source code
+        distribution). See that file for function prototypes, and so on.</p>
+
       <p>When writing a driver to make a communications protocol available
         to Erlang, one should know just about everything worth knowing
-        about that particular protocol. All operation has to be non
-        blocking and all possible situations should be accounted for in
-        the driver. A non stable driver will affect and/or crash the
-        whole Erlang runtime system, which is seldom what's wanted. </p>
+        about that particular protocol. All operation must be
+        non-blocking and all possible situations are to be accounted for in
+        the driver. A non-stable driver will affect and/or crash the
+        whole Erlang runtime system.</p>
+
       <p>The emulator calls the driver in the following situations:</p>
+
       <list type="bulleted">
-        <item>When the driver is loaded. This call-back has to have a
-         special name and will inform the emulator of what call-backs should
-         be used by returning a pointer to a <c><![CDATA[ErlDrvEntry]]></c> struct,
-         which should be properly filled in (see below).</item>
-        <item>When a port to the driver is opened (by a <c><![CDATA[open_port]]></c>
-         call from Erlang). This routine should set up internal data
-         structures and return an opaque data entity of the type
-        <c><![CDATA[ErlDrvData]]></c>, which is a data-type large enough to hold a
-         pointer. The pointer returned by this function will be the first
-         argument to all other call-backs concerning this particular
-         port. It is usually called the port handle. The emulator only
-         stores the handle and does never try to interpret it, why it can
-         be virtually anything (well anything not larger than a pointer
-         that is) and can point to anything if it is a pointer. Usually
-         this pointer will refer to a structure holding information about
-         the particular port, as i t does in our example.</item>
-        <item>When an Erlang process sends data to the port. The data will
-         arrive as a buffer of bytes, the interpretation is not defined,
-         but is up to the implementor. This call-back returns nothing to the
-         caller, answers are sent to the caller as messages (using a
-         routine called <c><![CDATA[driver_output]]></c> available to all
-         drivers). There is also a way to talk in a synchronous way to
-         drivers, described below. There can be an additional call-back
-         function for handling data that is fragmented (sent in a deep
-         io-list). That interface will get the data in a form suitable for
-         Unix <c><![CDATA[writev]]></c> rather than in a single buffer. There is no
-         need for a distribution driver to implement such a call-back, so
-         we wont.</item>
-        <item>When a file descriptor is signaled for input. This call-back
-         is called when the emulator detects input on a file descriptor
-         which the driver has marked for monitoring by using the interface
-        <c><![CDATA[driver_select]]></c>. The mechanism of driver select makes it
-         possible to read non blocking from file descriptors by calling
-        <c><![CDATA[driver_select]]></c> when reading is needed and then do the actual
-         reading in this call-back (when reading is actually possible). The
-         typical scenario is that <c><![CDATA[driver_select]]></c> is called when an 
-         Erlang process orders a read operation, and that this routine
-         sends the answer when data is available on the file descriptor.</item>
-        <item>When a file descriptor is signaled for output. This call-back
-         is called in a similar way as the previous, but when writing to a
-         file descriptor is possible. The usual scenario is that Erlang
-         orders writing on a file descriptor and that the driver calls
-        <c><![CDATA[driver_select]]></c>. When the descriptor is ready for output,
-         this call-back is called an the driver can try to send the
-         output. There may of course be queuing involved in such
-         operations, and there are some convenient queue routines available
-         to the driver writer to use in such situations.</item>
-        <item>When a port is closed, either by an Erlang process or by the
-         driver calling one of the <c><![CDATA[driver_failure_XXX]]></c> routines. This
-         routine should clean up everything connected to one particular
-         port. Note that when other call-backs call a
-        <c><![CDATA[driver_failure_XXX]]></c> routine, this routine will be
-         immediately called and the call-back routine issuing the error can
-         make no more use of the data structures for the port, as this
-         routine surely has freed all associated data and closed all file
-         descriptors. If the queue utility available to driver writes is
-         used, this routine will however <em>not</em> be called until the
-         queue is empty.</item>
-        <item>When an Erlang process calls <c>erlang:port_control/3</c>,
-         which is a synchronous interface to drivers. The control interface
-         is used to set driver options, change states of ports etc. We'll
-         use this interface quite a lot in our example.</item>
-        <item>When a timer expires. The driver can set timers with the
-         function <c><![CDATA[driver_set_timer]]></c>. When such timers expire, a
-         specific call-back function is called. We will not use timers in
-         our example.</item>
-        <item>When the whole driver is unloaded. Every resource allocated
-         by the driver should be freed.</item>
+        <item>
+          <p>When the driver is loaded. This callback must have a special
+            name and inform the emulator of what callbacks are to be used 
+            by returning a pointer to a <c><![CDATA[ErlDrvEntry]]></c> struct,
+            which is to be properly filled in (see below).</p>
+        </item>
+        <item>
+          <p>When a port to the driver is opened (by a
+            <c><![CDATA[open_port]]></c> call from Erlang). This routine is to
+            set up internal data structures and return an opaque data entity of
+            the type <c><![CDATA[ErlDrvData]]></c>, which is a data type large
+            enough to hold a pointer.
+            The pointer returned by this function is the first
+            argument to all other callbacks concerning this particular
+            port. It is usually called the port handle. The emulator only
+            stores the handle and does never try to interpret it, why it can
+            be virtually anything (anything not larger than a pointer
+            that is) and can point to anything if it is a pointer. Usually
+            this pointer refers to a structure holding information about
+            the particular port, as it does in the example.</p>
+        </item>
+        <item>
+          <p>When an Erlang process sends data to the port. The data
+            arrives as a buffer of bytes, the interpretation is not defined,
+            but is up to the implementor. This callback returns nothing to the
+            caller, answers are sent to the caller as messages (using a
+            routine called <c><![CDATA[driver_output]]></c> available to all
+            drivers). There is also a way to talk in a synchronous way to
+            drivers, described below. There can be an additional callback
+            function for handling data that is fragmented (sent in a deep
+            io-list). That interface gets the data in a form suitable for
+            Unix <c><![CDATA[writev]]></c> rather than in a single buffer.
+            There is no need for a distribution driver to implement such a
+            callback, so we will not.</p>
+        </item>
+        <item>
+          <p>When a file descriptor is signaled for input. This callback
+            is called when the emulator detects input on a file descriptor
+            that the driver has marked for monitoring by using the interface
+            <c><![CDATA[driver_select]]></c>. The mechanism of driver select
+            makes it possible to read non-blocking from file descriptors by
+            calling <c><![CDATA[driver_select]]></c> when reading is needed, and
+            then do the reading in this callback (when reading is possible).
+            The typical scenario is that <c><![CDATA[driver_select]]></c> is
+            called when an Erlang process orders a read operation, and that
+            this routine sends the answer when data is available on the file
+            descriptor.</p>
+        </item>
+        <item>
+          <p>When a file descriptor is signaled for output. This callback
+            is called in a similar way as the previous, but when writing to a
+            file descriptor is possible. The usual scenario is that Erlang
+            orders writing on a file descriptor and that the driver calls
+            <c><![CDATA[driver_select]]></c>. When the descriptor is ready for
+            output, this callback is called and the driver can try to send the
+            output. Queuing can be involved in such operations, and there are
+            convenient queue routines available to the driver writer to use.</p>
+        </item>
+        <item>
+          <p>When a port is closed, either by an Erlang process or by the
+            driver calling one of the <c><![CDATA[driver_failure_XXX]]></c>
+            routines. This routine is to clean up everything connected to one
+            particular port. When other callbacks call a
+            <c><![CDATA[driver_failure_XXX]]></c> routine, this routine is
+            immediately called. The callback routine issuing the error can
+            make no more use of the data structures for the port, as this
+            routine surely has freed all associated data and closed all file
+            descriptors. If the queue utility available to driver writer is
+            used, this routine is however <em>not</em> called until the
+            queue is empty.</p>
+        </item>
+        <item>
+          <p>When an Erlang process calls
+            <seealso marker="erlang#port_control/3">
+            <c>erlang:port_control/3</c></seealso>,
+            which is a synchronous interface to drivers. The control interface
+            is used to set driver options, change states of ports, and so on.
+            This interface is used a lot in the example.</p>
+        </item>
+        <item>
+          <p>When a timer expires. The driver can set timers with the function
+            <c><![CDATA[driver_set_timer]]></c>. When such timers expire, a
+            specific callback function is called. No timers are used in
+            the example.</p>
+        </item>
+        <item>
+          <p>When the whole driver is unloaded. Every resource allocated
+            by the driver is to be freed.</p>
+        </item>
       </list>
     </section>
 
     <section>
-      <title>The distribution driver's data structures</title>
-      <p>The driver used for Erlang distribution should implement a
-        reliable, order maintaining, variable length packet oriented
-        protocol. All error correction, re-sending and such need to be
+      <title>The Data Structures of the Distribution Driver</title>
+      <p>The driver used for Erlang distribution is to implement a
+        reliable, order maintaining, variable length packet-oriented
+        protocol. All error correction, resending and such need to be
         implemented in the driver or by the underlying communications
-        protocol. If the protocol is stream oriented (as is the case with
+        protocol. If the protocol is stream-oriented (as is the case with
         both TCP/IP and our streamed Unix domain sockets), some mechanism
         for packaging is needed. We will use the simple method of having a
-        header of four bytes containing the length of the package in a big
-        endian 32 bit integer (as Unix domain sockets only can be used
-        between processes on the same machine, we actually don't need to
-        code the integer in some special endianess, but I'll do it anyway
-        because in most situation you do need to do it. Unix domain
-        sockets are reliable and order maintaining, so we don't need to
-        implement resends and such in our driver.</p>
-      <p>Lets start writing our example Unix domain sockets driver by
-        declaring prototypes and filling in a static ErlDrvEntry
-        structure.</p>
+        header of four bytes containing the length of the package in a
+        big-endian 32-bit integer. As Unix domain sockets only can be used
+        between processes on the same machine, we do not need to
+        code the integer in some special endianess, but we will do it anyway
+        because in most situation you need to do it. Unix domain
+        sockets are reliable and order maintaining, so we do not need to
+        implement resends and such in the driver.</p>
+
+      <p>We start writing the example Unix domain sockets driver by
+        declaring prototypes and filling in a static <c>ErlDrvEntry</c>
+        structure:</p>
+
       <code type="none"><![CDATA[
 ( 1) #include <stdio.h>
 ( 2) #include <stdlib.h>
@@ -286,94 +355,123 @@
 (51)     NULL,                            /* process_exit callback */
 (52)     NULL                             /* stop_select callback */
 (53) };]]></code>
-      <p>On line 1 to 10 we have included the OS headers needed for our
-        driver. As this driver is written for Solaris, we know that the
-        header <c><![CDATA[uio.h]]></c> exists, why we can define the preprocessor
-        variable <c><![CDATA[HAVE_UIO_H]]></c> before we include <c><![CDATA[erl_driver.h]]></c> 
-        at line 12. The definition of <c><![CDATA[HAVE_UIO_H]]></c> will make the
+
+      <p>On line 1-10 the OS headers needed for the driver are included.
+        As this driver is written for Solaris, we know that the
+        header <c><![CDATA[uio.h]]></c> exists. So the preprocessor variable
+        <c><![CDATA[HAVE_UIO_H]]></c> can be defined before
+        <c><![CDATA[erl_driver.h]]></c> is included on line 12.
+        The definition of <c><![CDATA[HAVE_UIO_H]]></c> will make the
         I/O vectors used in Erlang's driver queues to correspond to the
         operating systems ditto, which is very convenient.</p>
-      <p>The different call-back functions are declared ("forward
-        declarations") on line 16 to 23.</p>
-      <p>The driver structure is similar for statically linked in
-        drivers and dynamically loaded. However some of the fields
-        should be left empty (i.e. initialized to NULL) in the
+
+      <p>On line 16-23 the different callback functions are declared ("forward
+        declarations").</p>
+
+      <p>The driver structure is similar for statically linked-in
+        drivers and dynamically loaded. However, some of the fields
+        are to be left empty (that is, initialized to NULL) in the
         different types of drivers. The first field (the <c><![CDATA[init]]></c>
         function pointer) is always left blank in a dynamically loaded
-        driver, which can be seen on line 26. The NULL on line 37
-        should always be there, the field is no longer used and is
-        retained for backward compatibility. We use no timers in this
-        driver, why no call-back for timers is needed. The <c>outputv</c> field
+        driver, see line 26. <c>NULL</c> on line 37
+        is always to be there, the field is no longer used and is
+        retained for backward compatibility. No timers are used in this
+        driver, why no callback for timers is needed. The <c>outputv</c> field
         (line 40) can be used to implement an interface similar to
         Unix <c><![CDATA[writev]]></c> for output. The Erlang runtime
-	system could previously not use <c>outputv</c> for the
-	distribution, but since erts version 5.7.2 it can.
-	Since this driver was written before erts version 5.7.2 it does 
-	not use the <c>outputv</c> callback. Using the <c>outputv</c>
-	callback is preferred since it reduces copying of data. (We
-	will however use scatter/gather I/O internally in the driver).</p>
-      <p>As of erts version 5.5.3 the driver interface was extended with
-         version control and the possibility to pass capability information.
-	 Capability flags are present at line 48. As of erts version 5.7.4
-	 the
-	 <seealso marker="driver_entry#driver_flags">ERL_DRV_FLAG_SOFT_BUSY</seealso>
-	 flag is required for drivers that are to be used by the distribution.
-	 The soft busy flag implies that the driver is capable of handling
-	 calls to the <c>output</c> and <c>outputv</c> callbacks even though
-	 it has marked itself as busy. This has always been a requirement
-	 on drivers used by the distribution, but there have previously not
-	 been any capability information available about this. For more
-	 information see
-         <seealso marker="erl_driver#set_busy_port">set_busy_port()</seealso>).
-</p>
+        system could previously not use <c>outputv</c> for the
+        distribution, but it can as from <c>ERTS</c> 5.7.2.
+        As this driver was written before <c>ERTS</c> 5.7.2 it does 
+        not use the <c>outputv</c> callback. Using the <c>outputv</c>
+        callback is preferred, as it reduces copying of data. (We
+        will however use scatter/gather I/O internally in the driver.)</p>
+
+      <p>As from <c>ERTS</c> 5.5.3 the driver interface was extended with
+        version control and the possibility to pass capability information.
+        Capability flags are present on line 48. As from <c>ERTS</c> 5.7.4 flag
+        <seealso marker="driver_entry#driver_flags">
+        <c>ERL_DRV_FLAG_SOFT_BUSY</c></seealso> is required for drivers that
+        are to be used by the distribution. The soft busy flag implies that the
+        driver can handle calls to the <c>output</c> and <c>outputv</c>
+        callbacks although it has marked itself as busy. This has always been a
+        requirement on drivers used by the distribution, but no capability
+        information has been available about this previously. For more
+        information. see <seealso marker="erl_driver#set_busy_port">
+        <c>erl_driver:set_busy_port()</c></seealso>).</p>
+
       <p>This driver was written before the runtime system had SMP support.
-         The driver will still function in the runtime system with SMP support,
-	 but performance will suffer from lock contention on the driver lock
-	 used for the driver. This can be alleviated by reviewing and perhaps
-	 rewriting the code so that each instance of the driver safely can
-	 execute in parallel. When instances safely can execute in parallel it
-	 is safe to enable instance specific locking on the driver. This is done
-	 by passing
-	 <seealso marker="driver_entry#driver_flags">ERL_DRV_FLAG_USE_PORT_LOCKING</seealso>
-	 as a driver flag. This is left as an exercise for the reader.</p>
-      <p>Our defined call-backs thus are:</p>
-      <list type="bulleted">
-        <item>uds_start, which shall initiate data for a port. We wont
-         create any actual sockets here, just initialize data structures.</item>
-        <item>uds_stop, the function called when a port is closed.</item>
-        <item>uds_command, which will handle messages from Erlang. The
-         messages can either be plain data to be sent or more subtle
-         instructions to the driver. We will use this function mostly for
-         data pumping.</item>
-        <item>uds_input, this is the call-back which is called when we have
-         something to read from a socket.</item>
-        <item>uds_output, this is the function called when we can write to a
-         socket.</item>
-        <item>uds_finish, which is called when the driver is unloaded. A
-         distribution driver will actually (or hopefully) never be unloaded,
-         but we include this for completeness. Being able to clean up after
-         oneself is always a good thing.</item>
-        <item>uds_control, the <c>erlang:port_control/2</c> call-back, which
-         will be used a lot in this implementation.</item>
-      </list>
-      <p>The ports implemented by this driver will operate in two major
-        modes, which i will call the <em>command</em> and <em>data</em>
-        modes. In command mode, only passive reading and writing (like
-        gen_tcp:recv/gen_tcp:send) can be
-        done, and this is the mode the port will be in during the
-        distribution handshake. When the connection is up, the port will
-        be switched to data mode and all data will be immediately read and
-        passed further to the Erlang emulator. In data mode, no data
-        arriving to the uds_command will be interpreted, but just packaged
-        and sent out on the socket. The uds_control call-back will do the
-        switching between those two modes.</p>
-      <p>While the <c><![CDATA[net_kernel]]></c> informs different subsystems that the
-        connection is coming up, the port should accept data to send, but
-        not receive any data, to avoid that data arrives from another node
-        before every kernel subsystem is prepared to handle it. We have a
-        third mode for this intermediate stage, lets call it the
-        <em>intermediate</em> mode.</p>
-      <p>Lets define an enum for the different types of ports we have:</p>
+        The driver will still function in the runtime system with SMP support,
+        but performance will suffer from lock contention on the driver lock
+        used for the driver. This can be alleviated by reviewing and perhaps
+        rewriting the code so that each instance of the driver safely can
+        execute in parallel. When instances safely can execute in parallel, it
+        is safe to enable instance-specific locking on the driver. This is done
+        by passing <seealso marker="driver_entry#driver_flags">
+        <c>ERL_DRV_FLAG_USE_PORT_LOCKING</c></seealso> as a driver flag. This
+        is left as an exercise for the reader.</p>
+
+      <p>Thus, the defined callbacks are as follows:</p>
+
+      <taglist>
+        <tag><c>uds_start</c></tag>
+        <item>
+          <p>Must initiate data for a port. We do not create any sockets
+            here, only initialize data structures.</p>
+        </item>
+        <tag><c>uds_stop</c></tag>
+        <item>
+          <p>Called when a port is closed.</p>
+        </item>
+        <tag><c>uds_command</c></tag>
+        <item>
+          <p>Handles messages from Erlang. The
+            messages can either be plain data to be sent or more subtle
+            instructions to the driver. This function is here mostly for
+            data pumping.</p>
+        </item>
+        <tag><c>uds_input</c></tag>
+        <item>
+          <p>Called when there is something to read from a socket.</p>
+        </item>
+        <tag><c>uds_output</c></tag>
+        <item>
+          <p>Called when it is possible to write to a socket.</p>
+        </item>
+        <tag><c>uds_finish</c></tag>
+        <item>
+          <p>Called when the driver is unloaded. A distribution driver will
+            actually (or hopefully) never be unloaded, but we include this for
+            completeness. To be able to clean up after oneself is always a good
+            thing.</p>
+        </item>
+        <tag><c>uds_control</c></tag>
+        <item>
+          <p>The <seealso marker="erlang#port_control/3">
+            <c>erlang:port_control/3</c></seealso> callback, which is
+            used a lot in this implementation.</p>
+        </item>
+      </taglist>
+
+      <p>The ports implemented by this driver operate in two major modes,
+        named <c>command</c> and <c>data</c>. In <c>command</c> mode,
+        only passive reading and writing (like
+        <c>gen_tcp:recv</c>/<c>gen_tcp:send</c>) can be done. The port is in
+        this mode during the distribution handshake. When the connection is up,
+        the port is switched to <c>data</c> mode and all data is immediately
+        read and passed further to the Erlang emulator. In <c>data</c>
+        mode, no data arriving to <c>uds_command</c> is interpreted, only
+        packaged and sent out on the socket. The <c>uds_control</c> callback
+        does the switching between those two modes.</p>
+
+      <p>While <c><![CDATA[net_kernel]]></c> informs different subsystems
+        that the connection is coming up, the port is to accept data to send.
+        However, the port receives no data, to avoid that data arrives from
+        another node before every kernel subsystem is prepared to handle it.
+        A third mode, named <c>intermediate</c>, is used for this
+        intermediate stage.</p>
+
+      <p>An enum is defined for the different types of ports:</p>
+
       <code type="none"><![CDATA[
 ( 1) typedef enum { 
 ( 2)     portTypeUnknown,      /* An uninitialized port */
@@ -384,40 +482,63 @@
 ( 7)     portTypeCommand,      /* A connected open port in command mode */
 ( 8)     portTypeIntermediate, /* A connected open port in special
 ( 9)                              half active mode */
-(10)     portTypeData          /* A connectec open port in data mode */ 
+(10)     portTypeData          /* A connected open port in data mode */ 
 (11) } PortType;      ]]></code>
-      <p>Lets look at the different types:</p>
-      <list type="bulleted">
-        <item>portTypeUnknown - The type a port has when it's opened, but
-         not actually bound to any file descriptor.</item>
-        <item>portTypeListener - A port that is connected to a listen
-         socket. This port will not do especially much, there will be no data
-         pumping done on this socket, but there will be read data available
-         when one is trying to do an accept on the port.</item>
-        <item>portTypeAcceptor - This is a port that is to represent the
-         result of an accept operation. It is created when one wants to
-         accept from a listen socket, and it will be converted to a
-         portTypeCommand when the accept succeeds.</item>
-        <item>portTypeConnector - Very similar to portTypeAcceptor, an
-         intermediate stage between the request for a connect operation and
-         that the socket is really connected to an accepting ditto in the
-         other end. As soon as the sockets are connected, the port will
-         switch type to portTypeCommand.</item>
-        <item>portTypeCommand - A connected socket (or accepted socket if
-         you want) that is in the command mode mentioned earlier.</item>
-        <item>portTypeIntermediate - The intermediate stage for a connected
-         socket. There should be no processing of input for this socket.</item>
-        <item>portTypeData - The mode where data is pumped through the port
-         and the uds_command routine will regard every call as a call where
-         sending is wanted. In this mode all input available will be read and
-         sent to Erlang as soon as it arrives on the socket, much like in the
-         active mode of a <c><![CDATA[gen_tcp]]></c> socket.</item>
-      </list>
-      <p>Now lets look at the state we'll need for our ports. One can note
-        that not all fields are used for all types of ports and that one
-        could save some space by using unions, but that would clutter the
-        code with multiple indirections, so i simply use one struct for
-        all types of ports, for readability.</p>
+
+      <p>The different types are as follows:</p>
+
+      <taglist>
+        <tag><c>portTypeUnknown</c></tag>
+        <item>
+          <p>The type a port has when it is opened, but
+            not bound to any file descriptor.</p>
+        </item>
+        <tag><c>portTypeListener</c></tag>
+        <item>
+          <p>A port that is connected to a listen socket. This port does not
+            do much, no data pumping is done on this socket, but read data is
+            available when one is trying to do an accept on the port.</p>
+        </item>
+        <tag><c>portTypeAcceptor</c></tag>
+        <item>
+          <p>This port is to represent the result of an accept operation. It is
+            created when one wants to accept from a listen socket, and it is
+            converted to a <c>portTypeCommand</c> when the accept succeeds.</p>
+        </item>
+        <tag><c>portTypeConnector</c></tag>
+        <item>
+          <p>Very similar to <c>portTypeAcceptor</c>, an
+            intermediate stage between the request for a connect operation and
+            that the socket is connected to an accepting ditto in the
+            other end. When the sockets are connected, the port
+            switches type to <c>portTypeCommand</c>.</p>
+        </item>
+        <tag><c>portTypeCommand</c></tag>
+        <item>
+          <p>A connected socket (or accepted socket) in <c>command</c> mode
+            mentioned earlier.</p>
+        </item>
+        <tag><c>portTypeIntermediate</c></tag>
+        <item>
+          <p>The intermediate stage for a connected socket.
+            There is to be no processing of input for this socket.</p>
+        </item>
+        <tag><c>portTypeData</c></tag>
+        <item>
+          <p>The mode where data is pumped through the port and the
+            <c>uds_command</c> routine regards every call as a call where
+            sending is wanted. In this mode, all input available is read and
+            sent to Erlang when it arrives on the socket, much like in the
+            active mode of a <c><![CDATA[gen_tcp]]></c> socket.</p>
+        </item>
+      </taglist>
+
+      <p>We study the state that is needed for the ports. Notice
+        that not all fields are used for all types of ports. Some space
+        could be saved by using unions, but that would clutter the
+        code with multiple indirections, so here is used one struct for
+        all types of ports, for readability:</p>
+
       <code type="none"><![CDATA[
 ( 1) typedef unsigned char Byte;
 ( 2) typedef unsigned int Word;
@@ -428,7 +549,7 @@
 ( 6)     int lockfd;               /* The file descriptor for a lock file in 
 ( 7)                                  case of listen sockets */
 ( 8)     Byte creation;            /* The creation serial derived from the 
-( 9)                                  lockfile */
+( 9)                                  lock file */
 (10)     PortType type;            /* Type of port */
 (11)     char *name;               /* Short name of socket for unlink */
 (12)     Word sent;                /* Bytes sent */
@@ -442,114 +563,154 @@
 (20)                                  input buffer */
 (21)     Byte *buffer;             /* The actual input buffer */
 (22) } UdsData;      ]]></code>
+
       <p>This structure is used for all types of ports although some
         fields are useless for some types. The least memory consuming
         solution would be to arrange this structure as a union of
-        structures, but the multiple indirections in the code to
-        access a field in such a structure will clutter the code to
+        structures. However, the multiple indirections in the code to
+        access a field in such a structure would clutter the code too
         much for an example.</p>
-      <p>Let's look at the fields in our structure:</p>
-      <list type="bulleted">
-        <item>fd - The file descriptor of the socket associated with the
-         port.</item>
-        <item>port - The port identifier for the port which this structure
-         corresponds to. It is needed for most <c><![CDATA[driver_XXX]]></c>
-         calls from the driver back to the emulator.</item>
+
+      <p>The fields in the structure are as follows:</p>
+
+      <taglist>
+        <tag><c>fd</c></tag>
         <item>
-          <p>lockfd - If the socket is a listen socket, we use a separate
+          <p>The file descriptor of the socket associated with the port.</p>
+        </item>
+        <tag><c>port</c></tag>
+        <item>
+          <p>The port identifier for the port that this structure
+            corresponds to. It is needed for most <c><![CDATA[driver_XXX]]></c>
+            calls from the driver back to the emulator.</p>
+        </item>
+        <tag><c>lockfd</c></tag>
+        <item>
+          <p>If the socket is a listen socket, we use a separate
             (regular) file for two purposes:</p>
           <list type="bulleted">
-            <item>We want a locking mechanism that gives no race
-             conditions, so that we can be sure of if another Erlang
-             node uses the listen socket name we require or if the
-             file is only left there from a previous (crashed)
-             session.</item>
             <item>
-              <p>We store the <em>creation</em> serial number in the
-                file. The <em>creation</em> is a number that should
+              <p>We want a locking mechanism that gives no race
+                conditions, to be sure if another Erlang
+                node uses the listen socket name we require or if the
+                file is only left there from a previous (crashed) session.</p>
+            </item>
+            <item>
+              <p>We store the <c>creation</c> serial number in the
+                file. The <c>creation</c> is a number that is to
                 change between different instances of different Erlang
                 emulators with the same name, so that process
-                identifiers from one emulator won't be valid when sent
+                identifiers from one emulator do not become valid when sent
                 to a new emulator with the same distribution name. The
-                creation can be between 0 and 3 (two bits) and is stored
-                in every process identifier sent to another node. </p>
-              <p>In a system with TCP based distribution, this data is
+                creation can be from 0 through 3 (two bits) and is stored
+                in every process identifier sent to another node.</p>
+              <p>In a system with TCP-based distribution, this data is
                 kept in the <em>Erlang port mapper daemon</em>
                 (<c><![CDATA[epmd]]></c>), which is contacted when a distributed
-                node starts. The lock-file and a convention for the UDS
-                listen socket's name will remove the need for
+                node starts. The lock file and a convention for the UDS
+                listen socket's name remove the need for
                 <c><![CDATA[epmd]]></c> when using this distribution module. UDS
                 is always restricted to one host, why avoiding a port
                 mapper is easy.</p>
             </item>
           </list>
         </item>
-        <item>creation - The creation number for a listen socket, which is
-         calculated as (the value found in the lock-file + 1) rem
-         4. This creation value is also written back into the
-         lock-file, so that the next invocation of the emulator will
-         found our value in the file.</item>
-        <item>type - The current type/state of the port, which can be one
-         of the values declared above.</item>
-        <item>name - The name of the socket file (the path prefix
-         removed), which allows for deletion (<c><![CDATA[unlink]]></c>) when the
-         socket is closed.</item>
-        <item>sent - How many bytes that have been sent over the
-         socket. This may wrap, but that's no problem for the
-         distribution, as the only thing that interests the Erlang
-         distribution is if this value has changed (the Erlang
-         net_kernel <em>ticker</em> uses this value by calling the
-         driver to fetch it, which is done through the
-	 <c>erlang:port_control</c> routine).</item>
-        <item>received - How many bytes that are read (received) from the
-         socket, used in similar ways as <c><![CDATA[sent]]></c>.</item>
-        <item>partner - A pointer to another port structure, which is
-         either the listen port from which this port is accepting a
-         connection or the other way around. The "partner relation"
-         is always bidirectional.</item>
-        <item>next - Pointer to next structure in a linked list of all
-         port structures. This list is used when accepting
-         connections and when the driver is unloaded.</item>
-        <item>buffer_size, buffer_pos, header_pos, buffer - data for input
-         buffering. Refer to the source code (in the kernel/examples
-         directory) for details about the input buffering. That
-         certainly goes beyond the scope of this document.</item>
-      </list>
+        <tag><c>creation</c></tag>
+        <item>
+          <p>The creation number for a listen socket, which is
+            calculated as (the value found in the lock-file + 1) rem 4.
+            This creation value is also written back into the
+            lock file, so that the next invocation of the emulator
+            finds our value in the file.</p>
+        </item>
+        <tag><c>type</c></tag>
+        <item>
+          <p>The current type/state of the port, which can be one
+            of the values declared above.</p>
+        </item>
+        <tag><c>name</c></tag>
+        <item>
+          <p>The name of the socket file (the path prefix removed),
+            which allows for deletion (<c><![CDATA[unlink]]></c>) when the
+            socket is closed.</p>
+        </item>
+        <tag><c>sent</c></tag>
+        <item>
+          <p>How many bytes that have been sent over the
+            socket. This can wrap, but that is no problem for the
+            distribution, as the Erlang distribution is only interested in
+            if this value has changed. (The Erlang
+            <c>net_kernel</c> <c>ticker</c> uses this value by calling the
+            driver to fetch it, which is done through the
+            <seealso marker="erlang#port_control/3">
+            <c>erlang:port_control/3</c></seealso> routine.)</p>
+        </item>
+        <tag><c>received</c></tag>
+        <item>
+          <p>How many bytes that are read (received) from the
+            socket, used in similar ways as <c><![CDATA[sent]]></c>.</p>
+        </item>
+        <tag><c>partner</c></tag>
+        <item>
+          <p>A pointer to another port structure, which is
+            either the listen port from which this port is accepting a
+            connection or conversely. The "partner relation"
+            is always bidirectional.</p>
+        </item>
+        <tag><c>next</c></tag>
+        <item>
+          <p>Pointer to next structure in a linked list of all
+            port structures. This list is used when accepting
+            connections and when the driver is unloaded.</p>
+        </item>
+        <tag><c>buffer_size</c>, <c>buffer_pos</c>, <c>header_pos</c>,
+          <c>buffer</c></tag>
+        <item>
+          <p>Data for input buffering. For details about the input buffering,
+            see the source code in directory <c>kernel/examples</c>. That
+            certainly goes beyond the scope of this section.</p>
+        </item>
+      </taglist>
     </section>
 
     <section>
-      <title>Selected parts of the distribution driver implementation</title>
-      <p>The distribution drivers implementation is not completely
-        covered in this text, details about buffering and other things
+      <title>Selected Parts of the Distribution Driver Implementation</title>
+      <p>The implemenation of the distribution driver is not completely
+        covered here, details about buffering and other things
         unrelated to driver writing are not explained. Likewise are
         some peculiarities of the UDS protocol not explained in
         detail. The chosen protocol is not important.</p>
-      <p>Prototypes for the driver call-back routines can be found in
+
+      <p>Prototypes for the driver callback routines can be found in
         the <c><![CDATA[erl_driver.h]]></c> header file.</p>
+
       <p>The driver initialization routine is (usually) declared with a
         macro to make the driver easier to port between different
-        operating systems (and flavours of systems). This is the only
-        routine that has to have a well defined name. All other
-        call-backs are reached through the driver structure. The macro
+        operating systems (and flavors of systems). This is the only
+        routine that must have a well-defined name. All other
+        callbacks are reached through the driver structure. The macro
         to use is named <c><![CDATA[DRIVER_INIT]]></c> and takes the driver name
-        as parameter.</p>
+        as parameter:</p>
+
       <code type="none"><![CDATA[
 (1) /* Beginning of linked list of ports */
 (2) static UdsData *first_data;
 
-
 (3) DRIVER_INIT(uds_drv)
 (4) {
 (5)     first_data = NULL;
 (6)     return &uds_driver_entry;
 (7) }      ]]></code>
+
       <p>The routine initializes the single global data structure and
-        returns a pointer to the driver entry. The routine will be
-        called when <c><![CDATA[erl_ddll:load_driver]]></c> is called from Erlang.</p>
-      <p>The <c><![CDATA[uds_start]]></c> routine is called when a port is opened
-        from Erlang. In our case, we only allocate a structure and
+        returns a pointer to the driver entry. The routine is called
+        when <c><![CDATA[erl_ddll:load_driver]]></c> is called from Erlang.</p>
+
+      <p>The <c><![CDATA[uds_start]]></c> routine is called when a port is
+        opened from Erlang. In this case, we only allocate a structure and
         initialize it. Creating the actual socket is left to the
         <c><![CDATA[uds_command]]></c> routine.</p>
+
       <code type="none"><![CDATA[
 ( 1) static ErlDrvData uds_start(ErlDrvPort port, char *buff)
 ( 2) {
@@ -574,15 +735,18 @@
 (21)     
 (22)     return((ErlDrvData) ud);
 (23) }      ]]></code>
-      <p>Every data item is initialized, so that no problems will arise
+
+      <p>Every data item is initialized, so that no problems arise
         when a newly created port is closed (without there being any
         corresponding socket). This routine is called when
-        <c><![CDATA[open_port({spawn, "uds_drv"},[])]]></c> is called from Erlang.</p>
-      <p>The <c><![CDATA[uds_command]]></c> routine is the routine called when an
-        Erlang process sends data to the port. All asynchronous
-        commands when the port is in <em>command mode</em> as well as 
-        the sending of all data when the port is in <em>data mode</em>
-        is handled in this9s routine. Let's have a look at it:</p>
+        <c><![CDATA[open_port({spawn, "uds_drv"},[])]]></c> is called from
+        Erlang.</p>
+
+      <p>The <c><![CDATA[uds_command]]></c> routine is the routine called when
+        an Erlang process sends data to the port. This routine handles all
+        asynchronous commands when the port is in <c>command</c> mode and
+        the sending of all data when the port is in <c>data</c> mode:</p>
+
       <code type="none"><![CDATA[
 ( 1) static void uds_command(ErlDrvData handle, char *buff, int bufflen)
 ( 2) {
@@ -636,57 +800,77 @@
 (49)         return;
 (50)     }
 (51) }      ]]></code>
-      <p>The command routine takes three parameters; the handle
-        returned for the port by <c><![CDATA[uds_start]]></c>, which is a pointer
-        to the internal port structure, the data buffer and the length
+
+      <p>The command routine takes three parameters; the handle returned for
+        the port by <c><![CDATA[uds_start]]></c>, which is a pointer
+        to the internal port structure, the data buffer, and the length
         of the data buffer. The buffer is the data sent from Erlang
-        (a list of bytes) converted to an C array (of bytes). </p>
-      <p>If Erlang sends i.e. the list <c><![CDATA[[$a,$b,$c]]]></c> to the port,
-        the <c><![CDATA[bufflen]]></c> variable will be <c><![CDATA[3]]></c> ant the
-        <c><![CDATA[buff]]></c> variable will contain <c><![CDATA[{'a','b','c'}]]></c> (no
-        null termination). Usually the first byte is used as an
-        opcode, which is the case in our driver to (at least when the
-        port is in command mode). The opcodes are defined as:</p>
-      <list type="bulleted">
-        <item>'L'&lt;socketname&gt;: Create and listen on socket with the
-         given name.</item>
-        <item>'A'&lt;listennumber as 32 bit bigendian&gt;: Accept from the
-         listen socket identified by the given identification
-         number. The identification number is retrieved with the
-         uds_control routine.</item>
-        <item>'C'&lt;socketname&gt;: Connect to the socket named
-         &lt;socketname&gt;.</item>
-        <item>'S'&lt;data&gt;: Send the data &lt;data&gt; on the
-         connected/accepted socket (in command mode). The sending is
-         acked when the data has left this process.</item>
-        <item>'R': Receive one packet of data.</item>
-      </list>
-      <p>One may wonder what is meant by "one packet of data" in the
-        'R' command. This driver always sends data packeted with a 4
-        byte header containing a big endian 32 bit integer that
+        (a list of bytes) converted to an C array (of bytes).</p>
+
+      <p>If Erlang sends, for example, the list <c><![CDATA[[$a,$b,$c]]]></c>
+        to the port, the <c><![CDATA[bufflen]]></c> variable is
+        <c><![CDATA[3]]></c> and the <c><![CDATA[buff]]></c> variable contains
+        <c><![CDATA[{'a','b','c'}]]></c> (no
+        <c>NULL</c> termination). Usually the first byte is used as an
+        opcode, which is the case in this driver too (at least when the
+        port is in <c>command</c> mode). The opcodes are defined as follows:</p>
+
+      <taglist>
+        <tag><c>'L'&lt;socket name&gt;</c></tag>
+        <item>
+          <p>Creates and listens on socket with the specified name.</p>
+        </item>
+        <tag><c>'A'&lt;listen number as 32-bit big-endian&gt;</c></tag>
+        <item>
+          <p>Accepts from the listen socket identified by the specified
+            identification number. The identification number is retrieved with
+            the <c>uds_control</c> routine.</p>
+        </item>
+        <tag><c>'C'&lt;socket name&gt;</c></tag>
+        <item>
+          <p>Connects to the socket named &lt;socket name&gt;.</p>
+        </item>
+        <tag><c>'S'&lt;data&gt;</c></tag>
+        <item>
+          <p>Sends the data &lt;data&gt; on the
+            connected/accepted socket (in <c>command</c> mode). The sending is
+            acknowledged when the data has left this process.</p>
+        </item>
+        <tag><c>'R'</c></tag>
+        <item>
+          <p>Receives one packet of data.</p>
+        </item>
+      </taglist>
+
+      <p>"One packet of data" in command <c>'R'</c> can be explained
+        as follows. This driver always sends data packaged with a 4
+        byte header containing a big-endian 32-bit integer that
         represents the length of the data in the packet. There is no
         need for different packet sizes or some kind of streamed
-        mode, as this driver is for the distribution only. One may
-        wonder why the header word is coded explicitly in big endian
-        when an UDS socket is local to the host. The answer simply is
-        that I see it as a good practice when writing a distribution
-        driver, as distribution in practice usually cross the host
-        boundaries. </p>
-      <p>On line 4-8 we handle the case where the port is in data or
-        intermediate mode, the rest of the routine handles the
-        different commands. We see (first on line 15) that the routine
-        uses the <c><![CDATA[driver_failure_posix()]]></c> routine to report
-        errors. One important thing to remember is that the failure
-        routines make a call to our <c><![CDATA[uds_stop]]></c> routine, which
-        will remove the internal port data. The handle (and the casted
-        handle <c><![CDATA[ud]]></c>) is therefore <em>invalid pointers</em> after a
-        <c><![CDATA[driver_failure]]></c> call and we should <em>immediately return</em>. The runtime system will send exit signals to all
+        mode, as this driver is for the distribution only.
+        Why is the header word coded explicitly in big-endian when a UDS
+        socket is local to the host? It is good practice when writing a
+        distribution driver, as distribution in practice usually crosses
+        the host boundaries.</p>
+
+      <p>On line 4-8 is handled the case where the port is in <c>data</c> mode
+        or <c>intermediate</c> mode and the remaining routine handles the
+        different commands. The routine uses the
+        <c><![CDATA[driver_failure_posix()]]></c> routine to report errors
+        (see, for example, line 15). Notice that the failure routines make
+        a call to the <c><![CDATA[uds_stop]]></c> routine, which will
+        remove the internal port data. The handle (and the casted handle
+        <c><![CDATA[ud]]></c>) is therefore <em>invalid pointers</em> after a
+        <c><![CDATA[driver_failure]]></c> call and we should <em>return
+        immediately</em>. The runtime system will send exit signals to all
         linked processes.</p>
-      <p>The uds_input routine gets called when data is available on a
-        file descriptor previously passed to the <c><![CDATA[driver_select]]></c>
-        routine. Typically this happens when a read command is issued
-        and no data is available. Lets look at the <c><![CDATA[do_recv]]></c>
-        routine:</p>
+
+      <p>The <c>uds_input</c> routine is called when data is available on a
+        file descriptor previously passed to the
+        <c><![CDATA[driver_select]]></c> routine. This occurs typically when
+        a read command is issued and no data is available. The
+        <c><![CDATA[do_recv]]></c> routine is as follows:</p>
+
       <code type="none"><![CDATA[
 ( 1) static void do_recv(UdsData *ud)
 ( 2) {
@@ -716,29 +900,34 @@
 (26)         }
 (27)     }
 (28) }      ]]></code>
+
       <p>The routine tries to read data until a packet is read or the
         <c><![CDATA[buffered_read_package]]></c> routine returns a
-        <c><![CDATA[NORMAL_READ_FAILURE]]></c> (an internally defined constant for
-        the module that means that the read operation resulted in an
-        <c><![CDATA[EWOULDBLOCK]]></c>). If the port is in command mode, the
-        reading stops when one package is read, but if it is in data
-        mode, the reading continues until the socket buffer is empty
-        (read failure). If no more data can be read and more is wanted
-        (always the case when socket is in data mode) driver_select is
-        called to make the <c><![CDATA[uds_input]]></c> call-back be called when
-        more data is available for reading.</p>
-      <p>When the port is in data mode, all data is sent to Erlang in a
-        format that suits the distribution, in fact the raw data will
+        <c><![CDATA[NORMAL_READ_FAILURE]]></c> (an internally defined constant
+        for the module, which means that the read operation resulted in an
+        <c><![CDATA[EWOULDBLOCK]]></c>). If the port is in <c>command</c> mode,
+        the reading stops when one package is read. If the port is in
+        <c>data</c> mode, the reading continues until the socket buffer is empty
+        (read failure). If no more data can be read and more is wanted (which
+        is always the case when the socket is in <c>data</c> mode),
+        <c>driver_select</c> is called to make the <c><![CDATA[uds_input]]></c>
+        callback be called when more data is available for reading.</p>
+
+      <p>When the port is in <c>data</c> mode, all data is sent to Erlang in a
+        format that suits the distribution. In fact, the raw data will
         never reach any Erlang process, but will be
         translated/interpreted by the emulator itself and then
         delivered in the correct format to the correct processes. In
-        the current emulator version, received data should be tagged
-        with a single byte of 100. Thats what the macro
-        <c><![CDATA[DIST_MAGIC_RECV_TAG]]></c> is defined to. The tagging of data
-        in the distribution will possibly change in the future.</p>
-      <p>The <c><![CDATA[uds_input]]></c> routine will handle other input events
-        (like nonblocking <c><![CDATA[accept]]></c>), but most importantly handle
+        the current emulator version, received data is to be tagged
+        with a single byte of 100. That is what the macro
+        <c><![CDATA[DIST_MAGIC_RECV_TAG]]></c> is defined to. The tagging of
+        data in the distribution can be changed in the future.</p>
+
+      <p>The <c><![CDATA[uds_input]]></c> routine handles other input events
+        (like non-blocking <c><![CDATA[accept]]></c>), but most importantly
+        handle
         data arriving at the socket by calling <c><![CDATA[do_recv]]></c>:</p>
+
       <code type="none"><![CDATA[
 ( 1) static void uds_input(ErlDrvData handle, ErlDrvEvent event)
 ( 2) {
@@ -768,13 +957,16 @@
 (24)     }
 (25)     do_recv(ud);
 (26) }      ]]></code>
-      <p>The important line here is the last line in the function, the
-        <c><![CDATA[do_read]]></c> routine is called to handle new input. The rest
-        of the function handles input on a listen socket, which means
-        that there should be possible to do an accept on the
+
+      <p>The important line is the last line in the function: the
+        <c><![CDATA[do_read]]></c> routine is called to handle new input.
+        The remaining function handles input on a listen socket, which means
+        that it is to be possible to do an accept on the
         socket, which is also recognized as a read event.</p>
-      <p>The output mechanisms are similar to the input. Lets first
-        look at the <c><![CDATA[do_send]]></c> routine:</p>
+
+      <p>The output mechanisms are similar to the input.
+        The <c><![CDATA[do_send]]></c> routine is as follows:</p>
+
       <code type="none"><![CDATA[
 ( 1) static void do_send(UdsData *ud, char *buff, int bufflen) 
 ( 2) {
@@ -816,33 +1008,36 @@
 (37)     driver_enqv(ud->port, &eio, written);
 (38)     send_out_queue(ud);
 (39) }      ]]></code>
+
       <p>This driver uses the <c><![CDATA[writev]]></c> system call to send data
-        onto the socket. A combination of writev and the driver output
-        queues is very convenient. An <em>ErlIOVec</em> structure
-        contains a <em>SysIOVec</em> (which is equivalent to the
-        <c><![CDATA[struct iovec]]></c> structure defined in <c><![CDATA[uio.h]]></c>. The
-        ErlIOVec also contains an array of <em>ErlDrvBinary</em>
+        onto the socket. A combination of <c>writev</c> and the driver output
+        queues is very convenient. An <c>ErlIOVec</c> structure
+        contains a <c>SysIOVec</c> (which is equivalent to the
+        <c><![CDATA[struct iovec]]></c> structure defined in
+        <c><![CDATA[uio.h]]></c>. The
+        <c>ErlIOVec</c> also contains an array of <c>ErlDrvBinary</c>
         pointers, of the same length as the number of buffers in the
         I/O vector itself. One can use this to allocate the binaries
-        for the queue "manually" in the driver, but we'll just fill
-        the binary array with NULL values (line 7) , which will make
-        the runtime system allocate its own buffers when we call
-        <c><![CDATA[driver_enqv]]></c> (line 37).</p>
-      <p></p>
+        for the queue "manually" in the driver, but here
+        the binary array is filled with <c>NULL</c> values (line 7).
+        The runtime system then allocates its own buffers when
+        <c><![CDATA[driver_enqv]]></c> is called (line 37).</p>
+
       <p>The routine builds an I/O vector containing the header bytes
         and the buffer (the opcode has been removed and the buffer
         length decreased by the output routine). If the queue is
-        empty, we'll write the data directly to the socket (or at
+        empty, we write the data directly to the socket (or at
         least try to). If any data is left, it is stored in the queue
-        and then we try to send the queue (line 38). An ack is sent
-        when the message is delivered completely (line 22). The
-        <c><![CDATA[send_out_queue]]></c> will send acks if the sending is
-        completed there. If the port is in command mode, the Erlang
+        and then we try to send the queue (line 38). An acknowledgement
+        is sent when the message is delivered completely (line 22). The
+        <c><![CDATA[send_out_queue]]></c> sends acknowledgements if the sending
+        is completed there. If the port is in <c>command</c> mode, the Erlang
         code serializes the send operations so that only one packet
-        can be waiting for delivery at a time. Therefore the ack can
-        be sent simply whenever the queue is empty.</p>
-      <p></p>
-      <p>A short look at the <c><![CDATA[send_out_queue]]></c> routine:</p>
+        can be waiting for delivery at a time. Therefore the acknowledgement
+        can be sent whenever the queue is empty.</p>
+
+      <p>The <c><![CDATA[send_out_queue]]></c> routine is as follows:</p>
+
       <code type="none"><![CDATA[
 ( 1) static int send_out_queue(UdsData *ud)
 ( 2) {
@@ -874,20 +1069,24 @@
 (28)         ud->sent += wrote;
 (29)     }
 (30) }      ]]></code>
-      <p>What we do is simply to pick out an I/O vector from the queue
-        (which is the whole queue as an <em>SysIOVec</em>). If the I/O
-        vector is to long (IO_VECTOR_MAX is defined to 16), the vector
+
+      <p>We simply pick out an I/O vector from the queue
+        (which is the whole queue as a <c>SysIOVec</c>). If the I/O
+        vector is too long (<c>IO_VECTOR_MAX</c> is defined to 16), the vector
         length is decreased (line 15), otherwise the <c><![CDATA[writev]]></c>
-        (line 17) call will
-        fail. Writing is tried and anything written is dequeued (line
-        27). If the write fails with <c><![CDATA[EWOULDBLOCK]]></c> (note that all
-        sockets are in nonblocking mode), <c><![CDATA[driver_select]]></c> is
+        call (line 17) fails. Writing is tried and anything written is dequeued
+        (line 27).
+        If the write fails with <c><![CDATA[EWOULDBLOCK]]></c> (notice that all
+        sockets are in non-blocking mode), <c><![CDATA[driver_select]]></c> is
         called to make the <c><![CDATA[uds_output]]></c> routine be called when
         there is space to write again.</p>
-      <p>We will continue trying to write until the queue is empty or
-        the writing would block.</p>
-      <p>The routine above are called from the <c><![CDATA[uds_output]]></c>
-        routine, which looks like this:</p>
+
+      <p>We continue trying to write until the queue is empty or
+        the writing blocks.</p>
+
+      <p>The routine above is called from the <c><![CDATA[uds_output]]></c>
+        routine:</p>
+
       <code type="none"><![CDATA[
 ( 1) static void uds_output(ErlDrvData handle, ErlDrvEvent event)
 ( 2) {
@@ -900,51 +1099,80 @@
 ( 9)    }
 (10)    send_out_queue(ud);
 (11) }      ]]></code>
-      <p>The routine is simple, it first handles the fact that the
+
+      <p>The routine is simple: it first handles the fact that the
         output select will concern a socket in the business of
         connecting (and the connecting blocked). If the socket is in
-        a connected state it simply sends the output queue, this
-        routine is called when there is possible to write to a socket
+        a connected state, it simply sends the output queue. This
+        routine is called when it is possible to write to a socket
         where we have an output queue, so there is no question what to
         do.</p>
+
       <p>The driver implements a control interface, which is a
         synchronous interface called when Erlang calls
-        <c><![CDATA[erlang:port_control/3]]></c>. This is the only interface
-        that can control the driver when it is in data mode and it may
+        <seealso marker="erlang#port_control/3">
+        <c>erlang:port_control/3</c></seealso>. Only this interface
+        can control the driver when it is in <c>data</c> mode. It can
         be called with the following opcodes:</p>
-      <list type="bulleted">
-        <item>'C': Set port in command mode.</item>
-        <item>'I': Set port in intermediate mode.</item>
-        <item>'D': Set port in data mode.</item>
-        <item>'N': Get identification number for listen port, this
-         identification number is used in an accept command to the
-         driver, it is returned as a big endian 32 bit integer, which
-         happens to be the file identifier for the listen socket.</item>
-        <item>'S': Get statistics, which is the number of bytes received,
-         the number of bytes sent and the number of bytes pending in
-         the output queue. This data is used when the distribution
-         checks that a connection is alive (ticking). The statistics
-         is returned as 3 32 bit big endian integers.</item>
-        <item>'T': Send a tick message, which is a packet of length
-         0. Ticking is done when the port is in data mode, so the
-         command for sending data cannot be used (besides it ignores
-         zero length packages in command mode). This is used by the
-         ticker to send dummy data when no other traffic is present.
-	 <em>Note</em> that it is important that the interface for
-	 sending ticks is not blocking. This implementation uses
-	 <c>erlang:port_control/3</c> which does not block the caller.
-	 If <c>erlang:port_command</c> is used, use
-	 <c>erlang:port_command/3</c> and pass <c>[force]</c> as
-	 option list; otherwise, the caller can be blocked indefinitely
-	 on a busy port and prevent the system from taking down a
-	 connection that is not functioning.</item>
-        <item>'R': Get creation number of listen socket, which is used to
-         dig out the number stored in the lock file to differentiate
-         between invocations of Erlang nodes with the same name.</item>
-      </list>
+
+      <taglist>
+        <tag><c>'C'</c></tag>
+        <item>
+          <p>Sets port in <c>command</c> mode.</p>
+        </item>
+        <tag><c>'I'</c></tag>
+        <item>
+          <p>Sets port in <c>intermediate</c> mode.</p>
+        </item>
+        <tag><c>'D'</c></tag>
+        <item>
+          <p>Sets port in <c>data</c> mode.</p>
+        </item>
+        <tag><c>'N'</c></tag>
+        <item>
+          <p>Gets identification number for listen port. This
+            identification number is used in an accept command to the
+            driver. It is returned as a big-endian 32-bit integer, which
+            is the file identifier for the listen socket.</p>
+        </item>
+        <tag><c>'S'</c></tag>
+        <item>
+          <p>Gets statistics, which is the number of bytes received,
+            the number of bytes sent, and the number of bytes pending in
+            the output queue. This data is used when the distribution
+            checks that a connection is alive (ticking). The statistics
+            is returned as three 32-bit big-endian integers.</p>
+        </item>
+        <tag><c>'T'</c></tag>
+        <item>
+          <p>Sends a tick message, which is a packet of length 0.
+            Ticking is done when the port is in <c>data</c> mode, so the
+            command for sending data cannot be used (besides it ignores
+            zero length packages in <c>command</c> mode). This is used by the
+            ticker to send dummy data when no other traffic is present.</p>
+          <p><em>Note:</em> It is important that the interface for
+            sending ticks is not blocking. This implementation uses
+            <seealso marker="erlang#port_control/3">
+            <c>erlang:port_control/3</c></seealso>, which does not block the
+            caller. If <c>erlang:port_command</c> is used, use
+            <seealso marker="erlang#port_command/3">
+            <c>erlang:port_command/3</c></seealso> and pass <c>[force]</c> as
+            option list; otherwise the caller can be blocked indefinitely
+            on a busy port and prevent the system from taking down a
+            connection that is not functioning.</p>
+        </item>
+        <tag><c>'R'</c></tag>
+        <item>
+          <p>Gets creation number of a listen socket, which is used to
+            dig out the number stored in the lock file to differentiate
+            between invocations of Erlang nodes with the same name.</p>
+        </item>
+      </taglist>
+
       <p>The control interface gets a buffer to return its value in,
-        but is free to allocate its own buffer is the provided one is
-        to small. Here is the code for <c><![CDATA[uds_control]]></c>:</p>
+        but is free to allocate its own buffer if the provided one is
+        too small. The <c><![CDATA[uds_control]]></c> code is as follows:</p>
+
       <code type="none"><![CDATA[
 ( 1) static int uds_control(ErlDrvData handle, unsigned int command, 
 ( 2)                        char* buf, int count, char** res, int res_size)
@@ -1025,47 +1253,55 @@
 (75)    }
 (76) #undef ENSURE
 (77) }      ]]></code>
-      <p>The macro <c><![CDATA[ENSURE]]></c> (line 5 to 10) is used to ensure that
-        the buffer is large enough for our answer. We switch on the
-        command and take actions, there is not much to say about this
-        routine. Worth noting is that we always has read select active
-        on a port in data mode (achieved by calling <c><![CDATA[do_recv]]></c> on
-        line 45), but turn off read selection in intermediate and
-        command modes (line 27 and 36).</p>
-      <p>The rest of the driver is more or less UDS specific and not of
+
+      <p>The macro <c><![CDATA[ENSURE]]></c> (line 5-10) is used to ensure that
+        the buffer is large enough for the answer. We switch on the command and
+        take actions. We always have read select active on a port in <c>data</c>
+        mode (achieved by calling <c><![CDATA[do_recv]]></c> on line 45), but
+        we turn off read selection in <c>intermediate</c> and <c>command</c>
+        modes (line 27 and 36).</p>
+
+      <p>The rest of the driver is more or less UDS-specific and not of
         general interest.</p>
     </section>
   </section>
 
   <section>
-    <title>Putting it all together</title>
-    <p>To test the distribution, one can use the
-      <c><![CDATA[net_kernel:start/1]]></c> function, which is useful as it starts
-      the distribution on a running system, where tracing/debugging
-      can be performed. The <c><![CDATA[net_kernel:start/1]]></c> routine takes a
-      list as its single argument. The lists first element should be
-      the node name (without the "@hostname") as an atom, and the second (and
-      last) element should be one of the atoms <c><![CDATA[shortnames]]></c> or 
-      <c><![CDATA[longnames]]></c>. In the example case <c><![CDATA[shortnames]]></c> is
-      preferred. </p>
-    <p>For net kernel to find out which distribution module to use, the
-      command line argument <c><![CDATA[-proto_dist]]></c> is used. The argument
-      is followed by one or more distribution module names, with the
-      "_dist" suffix removed, i.e. uds_dist as a distribution module
+    <title>Putting It All Together</title>
+    <p>To test the distribution, the <c><![CDATA[net_kernel:start/1]]></c>
+      function can be used. It is useful, as it starts the distribution on a
+      running system, where tracing/debugging can be performed.
+      The <c><![CDATA[net_kernel:start/1]]></c> routine takes a
+      list as its single argument. The list first element in the list is to be
+      the node name (without the "@hostname") as an atom. The second (and
+      last) element is to be one of the atoms <c><![CDATA[shortnames]]></c> or 
+      <c><![CDATA[longnames]]></c>. In the example case,
+      <c><![CDATA[shortnames]]></c> is preferred.</p>
+
+    <p>For <c>net_kernel</c> to find out which distribution module to use,
+      command-line argument <c><![CDATA[-proto_dist]]></c> is used. It
+      is followed by one or more distribution module names, with suffix
+      "_dist" removed, that is, <c>uds_dist</c> as a distribution module
       is specified as <c><![CDATA[-proto_dist uds]]></c>.</p>
-    <p>If no epmd (TCP port mapper daemon) is used, one should also
-      specify the command line option <c><![CDATA[-no_epmd]]></c>, which will make
-      Erlang skip the epmd startup, both as a OS process and as an
+
+    <p>If no <c>epmd</c> (TCP port mapper daemon) is used, also command-line
+      option <c><![CDATA[-no_epmd]]></c> is to be specified, which makes
+      Erlang skip the <c>epmd</c> startup, both as an OS process and as an
       Erlang ditto.</p>
+
     <p>The path to the directory where the distribution modules reside
-      must be known at boot, which can either be achieved by
-      specifying <c><![CDATA[-pa <path>]]></c> on the command line or by building
-      a boot script containing the applications used for your
-      distribution protocol (in the uds_dist protocol, it's only the
-      uds_dist application that needs to be added to the script).</p>
-    <p>The distribution will be started at boot if all the above is
+      must be known at boot. This can be achieved either by
+      specifying <c><![CDATA[-pa <path>]]></c> on the command line or by
+      building a boot script containing the applications used for your
+      distribution protocol. (In the <c>uds_dist</c> protocol, only the
+      <c>uds_dist</c> application needs to be added to the script.)</p>
+
+    <p>The distribution starts at boot if all the above is
       specified and an <c><![CDATA[-sname <name>]]></c> flag is present at the
-      command line, here follows two examples: </p>
+      command line.</p>
+
+    <p><em>Example 1:</em></p>
+
     <pre>
 $ <input>erl -pa $ERL_TOP/lib/kernel/examples/uds_dist/ebin -proto_dist uds -no_epmd</input>
 Erlang (BEAM) emulator version 5.0 
@@ -1074,7 +1310,9 @@ Eshell V5.0  (abort with ^G)
 1> <input>net_kernel:start([bing,shortnames]).</input>
 {ok,&lt;0.30.0>}
 (bing@hador)2></pre>
-    <p>...</p>
+
+    <p><em>Example 2:</em></p>
+
     <pre>
 $ <input>erl -pa $ERL_TOP/lib/kernel/examples/uds_dist/ebin -proto_dist uds \ </input>
 <input>      -no_epmd -sname bong</input>
@@ -1082,8 +1320,10 @@ Erlang (BEAM) emulator version 5.0
  
 Eshell V5.0  (abort with ^G)
 (bong@hador)1></pre>
-    <p>One can utilize the ERL_FLAGS environment variable to store the
+
+    <p>The <c>ERL_FLAGS</c> environment variable can be used to store the
       complicated parameters in:</p>
+
     <pre>
 $ <input>ERL_FLAGS=-pa $ERL_TOP/lib/kernel/examples/uds_dist/ebin \ </input>
 <input>      -proto_dist uds -no_epmd</input>
@@ -1093,8 +1333,8 @@ Erlang (BEAM) emulator version 5.0
  
 Eshell V5.0  (abort with ^G)
 (bang@hador)1></pre>
-    <p>The <c><![CDATA[ERL_FLAGS]]></c> should preferably not include the name of
-      the node.</p>
+
+    <p><c><![CDATA[ERL_FLAGS]]></c> should not include the node name.</p>
   </section>
 </chapter>
 
diff --git a/erts/doc/src/communication.xml b/erts/doc/src/communication.xml
index 1eb05310e9..632ca6c212 100644
--- a/erts/doc/src/communication.xml
+++ b/erts/doc/src/communication.xml
@@ -26,63 +26,72 @@
     <prepared>Rickard Green</prepared>
     <responsible></responsible>
     <docno></docno>
-    <approved></approved>
+    <approved>uy</approved>
     <checked></checked>
     <date>2012-12-03</date>
     <rev>PA1</rev>
     <file>communication.xml</file>
   </header>
   <p>Communication in Erlang is conceptually performed using
-     asynchronous signaling. All different executing entities
-     such as processes, and ports communicate via asynchronous
+     asynchronous signaling. All different executing entities,
+     such as processes and ports, communicate through asynchronous
      signals. The most commonly used signal is a message. Other
-     common signals are exit, link, unlink, monitor, demonitor
+     common signals are exit, link, unlink, monitor, and demonitor
      signals.</p>
+
   <section>
     <title>Passing of Signals</title>
-    <p>The amount of time that passes between a signal being sent
+    <p>The amount of time that passes between a signal is sent
     and the arrival of the signal at the destination is unspecified
-    but positive. If the receiver has terminated, the signal will
-    not arrive, but it is possible that it triggers another signal.
-    For example, a link signal sent to a non-existing process will
-    trigger an exit signal which will be sent back to where the link
+    but positive. If the receiver has terminated, the signal does
+    not arrive, but it can trigger another signal.
+    For example, a link signal sent to a non-existing process
+    triggers an exit signal, which is sent back to where the link
     signal originated from. When communicating over the distribution,
-    signals may be lost if the distribution channel goes down.</p>
-    <p>The only signal ordering guarantee given is the following. If
+    signals can be lost if the distribution channel goes down.</p>
+
+    <p>The only signal ordering guarantee given is the following: if
     an entity sends multiple signals to the same destination entity,
-    the order will be preserved. That is, if <c>A</c> sends
+    the order is preserved; that is, if <c>A</c> sends
     a signal <c>S1</c> to <c>B</c>, and later sends
-    the signal <c>S2</c> to <c>B</c>, <c>S1</c> is guaranteed not to
+    signal <c>S2</c> to <c>B</c>, <c>S1</c> is guaranteed not to
     arrive after <c>S2</c>.</p>
   </section>
+
   <section>
     <title>Synchronous Communication</title>
     <p>Some communication is synchronous. If broken down into pieces,
-    a synchronous communication operation, consists of two asynchronous
-    signals. One request signal and one reply signal. An example of 
-    such a synchronous communication is a call to <c>process_info/2</c>
-    when the first argument is not <c>self()</c>. The caller will send
-    an asynchronous signal requesting information, and will then
-    wait for the reply signal containing the requested information. When
-    the request signal reaches its destination the destination process
+    a synchronous communication operation consists of two asynchronous
+    signals; one request signal and one reply signal. An example of
+    such a synchronous communication is a call to
+    <seealso marker="erlang:process_info/2">
+    <c>erlang:process_info/2</c></seealso>
+    when the first argument is not <c>self()</c>. The caller sends
+    an asynchronous signal requesting information, and then
+    waits for the reply signal containing the requested information. When
+    the request signal reaches its destination, the destination process
     replies with the requested information.</p>
   </section>
+
   <section>
     <title>Implementation</title>
-    <p>The implementation of different asynchronous signals in the
-    VM may vary over time, but the behaviour will always respect this
+    <p>The implementation of different asynchronous signals in the virtual
+    machine can vary over time, but the behavior always respects this
     concept of asynchronous signals being passed between entities
     as described above.</p>
-    <p>By inspecting the implementation you might notice that some
-    specific signal actually gives a stricter guarantee than described
+
+    <p>By inspecting the implementation, you might notice that some
+    specific signal gives a stricter guarantee than described
     above. It is of vital importance that such knowledge about the
-    implementation is <em>not</em> used by Erlang code, since the
-    implementation might change at any time without prior notice.</p>
-    <p>Some example of major implementation changes:</p>
+    implementation is <em>not</em> used by Erlang code, as the
+    implementation can change at any time without prior notice.</p>
+
+    <p>Examples of major implementation changes:</p>
+
     <list type="bulleted">
-      <item>As of ERTS version 5.5.2 exit signals to processes are truly
+      <item>As from <c>ERTS</c> 5.5.2 exit signals to processes are truly
       asynchronously delivered.</item>
-      <item>As of ERTS version 5.10 all signals from processes to ports
+      <item>As from <c>ERTS</c> 5.10 all signals from processes to ports
       are truly asynchronously delivered.</item>
     </list>
   </section>
diff --git a/erts/doc/src/crash_dump.xml b/erts/doc/src/crash_dump.xml
index 0b827ae583..f143be87d6 100644
--- a/erts/doc/src/crash_dump.xml
+++ b/erts/doc/src/crash_dump.xml
@@ -22,7 +22,7 @@
 
     </legalnotice>
 
-    <title>How to interpret the Erlang crash dumps</title>
+    <title>How to Interpret the Erlang Crash Dumps</title>
     <prepared>Patrik Nyblom</prepared>
     <responsible></responsible>
     <docno></docno>
@@ -32,401 +32,539 @@
     <rev>PA1</rev>
     <file>crash_dump.xml</file>
   </header>
-  <p>This document describes the <c><![CDATA[erl_crash.dump]]></c> file generated
-    upon abnormal exit of the Erlang runtime system.</p>
-  <p><em>Important:</em> For OTP release R9C the Erlang crash dump has
-    had a major facelift. This means that the information in this
-    document will not be directly applicable for older dumps. However,
-    if you use the Crashdump Viewer tool on older dumps, the crash
-    dumps are translated into a format similar to this.</p>
-  <p>The system will write the crash dump in the current directory of
+  <p>This section describes the <c><![CDATA[erl_crash.dump]]></c> file
+    generated upon abnormal exit of the Erlang runtime system.</p>
+
+  <note>
+    <p>The Erlang crash dump had a major facelift in Erlang/OTP R9C. The
+      information
+      in this section is therefore not directly applicable for older dumps.
+      However, if you use the <seealso marker="observer:crashdump_viewer">
+      <c>crashdump_viewer</c></seealso> tool in the <c>Observer</c> application
+      on older dumps,
+      the crash dumps are translated into a format similar to this.</p>
+  </note>
+
+  <p>The system writes the crash dump in the current directory of
     the emulator or in the file pointed out by the environment variable
     (whatever that means on the current operating system)
-    ERL_CRASH_DUMP. For a crash dump to be written, there has to be a
-    writable file system mounted.</p>
+    <c>ERL_CRASH_DUMP</c>. For a crash dump to be written, a
+    writable file system must be mounted.</p>
+
   <p>Crash dumps are written mainly for one of two reasons: either the
-    builtin function <c><![CDATA[erlang:halt/1]]></c> is called explicitly with a
-    string argument from running Erlang code, or else the runtime
+    built-in function <c><![CDATA[erlang:halt/1]]></c> is called explicitly
+    with a string argument from running Erlang code, or the runtime
     system has detected an error that cannot be handled. The most
-    usual reason that the system can't handle the error is that the
+    usual reason that the system cannot handle the error is that the
     cause is external limitations, such as running out of memory. A
-    crash dump due to an internal error may be caused by the system
+    crash dump caused by an internal error can be caused by the system
     reaching limits in the emulator itself (like the number of atoms
-    in the system, or too many simultaneous ets tables). Usually the
+    in the system, or too many simultaneous <c>ets</c> tables). Usually the
     emulator or the operating system can be reconfigured to avoid the
     crash, which is why interpreting the crash dump correctly is
     important.</p>
+
   <p>On systems that support OS signals, it is also possible to stop
-    the runtime system and generate a crash dump by sending the SIGUSR1.</p>
-  <p>The erlang crash dump is a readable text file, but it might not be
-    very easy to read. Using the Crashdump Viewer tool in the
-    <c><![CDATA[observer]]></c> application will simplify the task. This is an
-    wx-widget based tool for browsing Erlang crash dumps.</p>
+    the runtime system and generate a crash dump by sending the <c>SIGUSR1</c>
+    signal.</p>
+
+  <p>The Erlang crash dump is a readable text file, but it can be difficult
+    to read. Using the Crashdump Viewer tool in the
+    <c><![CDATA[Observer]]></c> application simplifies the task. This is a
+    wx-widget-based tool for browsing Erlang crash dumps.</p>
 
   <section>
     <marker id="general_info"></marker>
-    <title>General information</title>
-    <p>The first part of the dump shows the creation time for the dump,
-      a slogan indicating the reason for the dump, the system version,
-      of the node from which the dump originates, the compile time of
-      the emulator running the originating node, the number of
-      atoms in the atom table and the runtime system thread that caused
-      the crash dump to happen.
-      </p>
+    <title>General Information</title>
+    <p>The first part of the crash dump shows the following:</p>
+
+    <list type="bulleted">
+      <item>The creation time for the dump</item>
+      <item>A slogan indicating the reason for the dump</item>
+      <item>The system version of the node from which the dump originates</item>
+      <item>The compile time of the emulator running the originating node</item>
+      <item>The number of atoms in the atom table</item>
+      <item>The runtime system thread that caused the crash dump</item>
+    </list>
 
     <section>
-      <title>Reasons for crash dumps (slogan)</title>
-      <p>The reason for the dump is noted in the beginning of the file
-        as <em>Slogan: &lt;reason&gt;</em> (the word "slogan" has historical
-        roots). If the system is halted by the BIF
+      <title>Reasons for Crash Dumps (Slogan)</title>
+      <p>The reason for the dump is shown in the beginning of the file as:</p>
+
+      <pre>
+Slogan: &lt;reason&gt;</pre>
+
+      <p>(The word "slogan" has historical roots.)
+        If the system is halted by the BIF
         <c><![CDATA[erlang:halt/1]]></c>, the slogan is the string parameter
         passed to the BIF, otherwise it is a description generated by
         the emulator or the (Erlang) kernel. Normally the message
-        should be enough to understand the problem, but nevertheless
-        some messages are described here. Note however that the
-        suggested reasons for the crash are <em>only suggestions</em>. The exact reasons for the errors may vary
+        is enough to understand the problem, but
+        some messages are described here. Notice that the
+        suggested reasons for the crash are <em>only suggestions</em>.
+        The exact reasons for the errors can vary
         depending on the local applications and the underlying
         operating system.</p>
-      <list type="bulleted">
-        <item>"<em>&lt;A&gt;</em>: Cannot allocate <em>&lt;N&gt;</em>
-         bytes of memory (of type "<em>&lt;T&gt;</em>")." - The system
-         has run out of memory. &lt;A&gt; is the allocator that failed
-         to allocate memory, &lt;N&gt; is the number of bytes that
-         &lt;A&gt; tried to allocate, and &lt;T&gt; is the memory block
-         type that the memory was needed for. The most common case is
-         that a process stores huge amounts of data. In this case
-         &lt;T&gt; is most often <c><![CDATA[heap]]></c>, <c><![CDATA[old_heap]]></c>,
-        <c><![CDATA[heap_frag]]></c>, or <c><![CDATA[binary]]></c>. For more information on
-         allocators see
-        <seealso marker="erts_alloc">erts_alloc(3)</seealso>.</item>
-        <item>"<em>&lt;A&gt;</em>: Cannot reallocate <em>&lt;N&gt;</em>
-         bytes of memory (of type "<em>&lt;T&gt;</em>")." - Same as
-         above with the exception that memory was being reallocated
-         instead of being allocated when the system ran out of memory.</item>
-        <item>"Unexpected op code <em>N</em>" - Error in compiled
-         code, <c><![CDATA[beam]]></c> file damaged or error in the compiler.</item>
-        <item>"Module <em>Name</em> undefined" <c><![CDATA[|]]></c> "Function
-        <em>Name</em> undefined" <c><![CDATA[|]]></c> "No function
-        <em>Name</em>:<em>Name</em>/1" <c><![CDATA[|]]></c> "No function
-        <em>Name</em>:start/2" - The kernel/stdlib applications are
-         damaged or the start script is damaged.</item>
-        <item>"Driver_select called with too large file descriptor
-        <c><![CDATA[N]]></c>" - The number of file descriptors for sockets
-         exceed 1024 (Unix only). The limit on file-descriptors in
-         some Unix flavors can be set to over 1024, but only 1024
-         sockets/pipes can be used simultaneously by Erlang (due to
-         limitations in the Unix <c><![CDATA[select]]></c> call).  The number of
-         open regular files is not affected by this.</item>
-        <item>"Received SIGUSR1" - Sending the SIGUSR1 signal to a
-         Erlang machine (Unix only) forces a crash dump. This slogan reflects
-         that the Erlang machine crash-dumped due to receiving that signal.</item>
-        <item>"Kernel pid terminated (<em>Who</em>)
-         (<em>Exit-reason</em>)" - The kernel supervisor has detected
-         a failure, usually that the <c><![CDATA[application_controller]]></c>
-         has shut down (<c><![CDATA[Who]]></c> = <c><![CDATA[application_controller]]></c>,
-        <c><![CDATA[Why]]></c> = <c><![CDATA[shutdown]]></c>).  The application controller
-         may have shut down for a number of reasons, the most usual
-         being that the node name of the distributed Erlang node is
-         already in use. A complete supervisor tree "crash" (i.e.,
-         the top supervisors have exited) will give about the same
-         result. This message comes from the Erlang code and not from
-         the virtual machine itself. It is always due to some kind of
-         failure in an application, either within OTP or a
-         "user-written" one. Looking at the error log for your
-         application is probably the first step to take.</item>
-        <item>"Init terminating in do_boot ()" - The primitive Erlang boot
-         sequence was terminated, most probably because the boot
-         script has errors or cannot be read. This is usually a
-         configuration error - the system may have been started with
-         a faulty <c><![CDATA[-boot]]></c> parameter or with a boot script from
-         the wrong version of OTP.</item>
-        <item>"Could not start kernel pid (<em>Who</em>) ()" - One of the
-         kernel processes could not start. This is probably due to
-         faulty arguments (like errors in a <c><![CDATA[-config]]></c> argument)
-         or faulty configuration files. Check that all files are in
-         their correct location and that the configuration files (if
-         any) are not damaged. Usually there are also messages
-         written to the controlling terminal and/or the error log
-         explaining what's wrong.</item>
-      </list>
-      <p>Other errors than the ones mentioned above may occur, as the
-        <c><![CDATA[erlang:halt/1]]></c> BIF may generate any message. If the
+
+      <taglist>
+        <tag><em>&lt;A&gt;: Cannot allocate &lt;N&gt; bytes of memory (of type
+           "&lt;T&gt;")</em></tag>
+        <item>
+          <p>The system has run out of memory. &lt;A&gt; is the allocator that
+            failed to allocate memory, &lt;N&gt; is the number of bytes that
+            &lt;A&gt; tried to allocate, and &lt;T&gt; is the memory block
+            type that the memory was needed for. The most common case is
+            that a process stores huge amounts of data. In this case
+            &lt;T&gt; is most often <c><![CDATA[heap]]></c>,
+            <c><![CDATA[old_heap]]></c>, <c><![CDATA[heap_frag]]></c>, or
+            <c><![CDATA[binary]]></c>. For more information on allocators, see
+            <seealso marker="erts_alloc"><c>erts_alloc(3)</c></seealso>.</p>
+        </item>
+        <tag><em>&lt;A&gt;: Cannot reallocate &lt;N&gt; bytes of memory (of
+          type "&lt;T&gt;")</em></tag>
+        <item>
+          <p>Same as above except that memory was reallocated
+            instead of allocated when the system ran out of memory.</p>
+        </item>
+        <tag><em>Unexpected op code &lt;N&gt;</em></tag>
+        <item>
+          <p>Error in compiled code, <c><![CDATA[beam]]></c> file damaged, or
+            error in the compiler.</p>
+        </item>
+        <tag><em>Module &lt;Name&gt; undefined <c><![CDATA[|]]></c> Function
+          &lt;Name&gt; undefined <c><![CDATA[|]]></c> No function
+          &lt;Name&gt;:&lt;Name&gt;/1 <c><![CDATA[|]]></c> No function
+          &lt;Name&gt;:start/2</em></tag>
+        <item>
+          <p>The <c>Kernel</c>/<c>STDLIB</c> applications are
+            damaged or the start script is damaged.</p>
+        </item>
+        <tag><em>Driver_select called with too large file descriptor
+          <c><![CDATA[N]]></c></em></tag>
+        <item>
+          <p>The number of file descriptors for sockets
+            exceeds 1024 (Unix only). The limit on file descriptors in
+            some Unix flavors can be set to over 1024, but only 1024
+            sockets/pipes can be used simultaneously by Erlang (because of
+            limitations in the Unix <c><![CDATA[select]]></c> call). The number
+            of open regular files is not affected by this.</p>
+        </item>
+        <tag><em>Received SIGUSR1</em></tag>
+        <item>
+          <p>Sending the <c>SIGUSR1</c> signal to an Erlang machine (Unix only)
+            forces a crash dump. This slogan reflects that the Erlang machine
+            crash-dumped because of receiving that signal.</p>
+        </item>
+        <tag><em>Kernel pid terminated (&lt;Who&gt;) (&lt;Exit
+          reason&gt;)</em></tag>
+        <item>
+          <p>The kernel supervisor has detected a failure, usually that the
+            <c><![CDATA[application_controller]]></c> has shut down
+            (<c><![CDATA[Who]]></c> = <c><![CDATA[application_controller]]></c>,
+            <c><![CDATA[Why]]></c> = <c><![CDATA[shutdown]]></c>).
+            The application controller
+            can have shut down for many reasons, the most usual
+            is that the node name of the distributed Erlang node is
+            already in use. A complete supervisor tree "crash" (that is,
+            the top supervisors have exited) gives about the same
+            result. This message comes from the Erlang code and not from
+            the virtual machine itself. It is always because of some
+            failure in an application, either within OTP or a
+            "user-written" one. Looking at the error log for your
+            application is probably the first step to take.</p>
+        </item>
+        <tag><em>Init terminating in do_boot ()</em></tag>
+        <item>
+          <p>The primitive Erlang boot sequence was terminated, most probably
+            because the boot script has errors or cannot be read. This is
+            usually a configuration error; the system can have been started
+            with a faulty <c><![CDATA[-boot]]></c> parameter or with a boot
+            script from the wrong OTP version.</p>
+        </item>
+        <tag><em>Could not start kernel pid (&lt;Who&gt;) ()</em></tag>
+        <item>
+          <p>One of the kernel processes could not start. This is probably
+            because of faulty arguments (like errors in a
+            <c><![CDATA[-config]]></c> argument)
+            or faulty configuration files. Check that all files are in
+            their correct location and that the configuration files (if
+            any) are not damaged. Usually messages are also
+            written to the controlling terminal and/or the error log
+            explaining what is wrong.</p>
+        </item>
+      </taglist>
+
+      <p>Other errors than these can occur, as the
+        <c><![CDATA[erlang:halt/1]]></c> BIF can generate any message. If the
         message is not generated by the BIF and does not occur in the
-        list above, it may be due to an error in the emulator. There
-        may however be unusual messages that I haven't mentioned, that
-        still are connected to an application failure. There is a lot
-        more information available, so more thorough reading of the
-        crash dump may reveal the crash reason. The size of processes,
-        the number of ets tables and the Erlang data on each process
-        stack can be useful for tracking down the problem.</p>
+        list above, it can be because of an error in the emulator. There
+        can however be unusual messages, not mentioned here, which
+        are still connected to an application failure. There is much
+        more information available, so a thorough reading of the
+        crash dump can reveal the crash reason. The size of processes,
+        the number of <c>ets</c> tables, and the Erlang data on each process
+        stack can be useful to find the problem.</p>
     </section>
 
     <section>
-      <title>Number of atoms</title>
+      <title>Number of Atoms</title>
       <p>The number of atoms in the system at the time of the crash is
         shown as <em>Atoms: &lt;number&gt;</em>. Some ten thousands atoms is
-        perfectly normal, but more could indicate that the BIF
-        <c><![CDATA[erlang:list_to_atom/1]]></c> is used to dynamically generate a
-        lot of <em>different</em> atoms, which is never a good idea.</p>
+        perfectly normal, but more can indicate that the BIF
+        <c><![CDATA[erlang:list_to_atom/1]]></c> is used to generate many
+        <em>different</em> atoms dynamically, which is never a good idea.</p>
     </section>
   </section>
 
   <section>
     <marker id="scheduler"></marker>
-    <title>Scheduler information</title>
-    <p>Under the tag <em>=scheduler</em> information about the current state
-    and statistics of the schedulers in the runtime system is displayed.
-    On OSs that do allow instant suspension of other threads, the data within
-    this section will reflect what the runtime system looks like at the moment
-    when the crash happens.</p>
+    <title>Scheduler Information</title>
+    <p>Under the tag <em>=scheduler</em> is shown information about the current
+      state and statistics of the schedulers in the runtime system. On
+      operating systems that allow instant suspension of other threads, the
+      data within this section reflects what the runtime system looks like
+      when a crash occurs.</p>
+
     <p>The following fields can exist for a process:</p>
+
     <taglist>
       <tag><em>=scheduler:id</em></tag>
-      <item>Header, states the scheduler identifier.</item>
+      <item>
+        <p>Heading. States the scheduler identifier.</p>
+      </item>
       <tag><em>Scheduler Sleep Info Flags</em></tag>
-      <item>If empty the scheduler was doing some work.
-      If not empty the scheduler is either in some state of sleep,
-      or suspended. This entry is only present in a SMP enabled emulator</item>
+      <item>
+        <p>If empty, the scheduler was doing some work.
+          If not empty, the scheduler is either in some state of sleep,
+          or suspended. This entry is only present in an SMP-enabled
+          emulator.</p>
+      </item>
       <tag><em>Scheduler Sleep Info Aux Work</em></tag>
-      <item>If not empty, a scheduler internal auxiliary work is scheduled
-      to be done.</item>
+      <item>
+        <p>If not empty, a scheduler internal auxiliary work is scheduled
+          to be done.</p>
+      </item>
       <tag><em>Current Port</em></tag>
-      <item>The port identifier of the port that is currently being
-      executed by the scheduler.</item>
+      <item>
+        <p>The port identifier of the port that is currently
+          executed by the scheduler.</p>
+      </item>
       <tag><em>Current Process</em></tag>
-      <item>The process identifier of the process that is currently being
-      executed by the scheduler. If there is such a process this entry is
-      followed by the <em>State</em>,<em>Internal State</em>,
-      <em>Program Counter</em>, <em>CP</em> of that same process. See
-      <seealso marker="#processes">Process Information</seealso> for a
-      description what the different entries mean. Keep in mind that
-      this is a snapshot of what the entries are exactly when the crash
-      dump is starting to be generated. Therefore they will most likely
-      be different (and more telling) then the entries for the same
-      processes found in the <em>=proc</em> section. If there is no currently
-      running process, only the <em>Current Process</em> entry will be printed.
+      <item>
+        <p>The process identifier of the process that is currently
+          executed by the scheduler. If there is such a process, this entry is
+          followed by the <em>State</em>, <em>Internal State</em>,
+          <em>Program Counter</em>, and <em>CP</em> of that same process.
+          The entries are described in section
+          <seealso marker="#processes">Process Information</seealso>.</p>
+        <p>Notice that this is a snapshot of what the entries are exactly when
+          the crash dump is starting to be generated. Therefore they are most
+          likely different (and more telling) than the entries for the same
+          processes found in the <em>=proc</em> section. If there is no
+          currently running process, only the <em>Current Process</em> entry is
+          shown.</p>
       </item>
       <tag><em>Current Process Limited Stack Trace</em></tag>
-      <item>This entry only shows up if there is a current process. It is very
-      similar to <seealso marker="#proc_data"><em>=proc_stack</em></seealso>,
-      except that only the function frames are printed (i.e. the stack variables
-      are omited). It is also limited to only print the top and bottom part
-      of the stack. If the stack is small (less that 512 slots) then the
-      entire stack will be printed. If not, an entry stating
-      <code>skipping ## slots</code> will be printed where ## is
-      replaced by the number of slots that has been skipped.</item>
+      <item>
+        <p>This entry is shown only if there is a current process. It is
+          similar to <seealso marker="#proc_data">
+          <em>=proc_stack</em></seealso>, except that only the function frames
+          are shown (that is, the stack variables are omitted).
+          Also, only the top and bottom part of the stack are shown. If the
+          stack is small (&lt; 512 slots), the entire stack is shown. Otherwise
+          the entry <em>skipping ## slots</em> is shown, where <c>##</c>
+          is replaced by the number of slots that has been skipped.</p>
+      </item>
       <tag><em>Run Queue</em></tag>
-      <item>Displays statistics about how many processes and ports
-      of different priorities are scheduled on this scheduler.</item>
+      <item>
+        <p>Shows statistics about how many processes and ports
+          of different priorities are scheduled on this scheduler.</p>
+      </item>
       <tag><em>** crashed **</em></tag>
-      <item>This entry is normally not printed. It signifies that getting
-      the rest of the information about this scheduler failed for some reason.
+      <item>
+        <p>This entry is normally not shown. It signifies that getting the rest
+          of the information about this scheduler failed for some reason.</p>
       </item>
     </taglist>
   </section>
 
   <section>
     <marker id="memory"></marker>
-    <title>Memory information</title>
-    <p>Under the tag <em>=memory</em> you will find information similar
-      to what you can obtain on a living node with
-      <seealso marker="erts:erlang#erlang:memory/0">erlang:memory()</seealso>.</p>
+    <title>Memory Information</title>
+    <p>Under the tag <em>=memory</em> is shown information similar
+      to what can be obtainted on a living node with
+      <seealso marker="erts:erlang#erlang:memory/0">
+      <c>erlang:memory()</c></seealso>.</p>
   </section>
 
   <section>
     <marker id="internal_tables"></marker>
-    <title>Internal table information</title>
-    <p>The tags <em>=hash_table:&lt;table_name&gt;</em> and
-      <em>=index_table:&lt;table_name&gt;</em> presents internal
-      tables. These are mostly of interest for runtime system
-      developers.</p>
+    <title>Internal Table Information</title>
+    <p>Under the tags <em>=hash_table:&lt;table_name&gt;</em> and
+      <em>=index_table:&lt;table_name&gt;</em> is shown internal
+      tables. These are mostly of interest for runtime system developers.</p>
   </section>
 
   <section>
     <marker id="allocated_areas"></marker>
-    <title>Allocated areas</title>
-    <p>Under the tag <em>=allocated_areas</em> you will find information
-      similar to what you can obtain on a living node with
-      <seealso marker="erts:erlang#system_info_allocated_areas">erlang:system_info(allocated_areas)</seealso>.</p>
+    <title>Allocated Areas</title>
+    <p>Under the tag <em>=allocated_areas</em> is shown information
+      similar to what can be obtained on a living node with
+      <seealso marker="erts:erlang#system_info_allocated_areas">
+      <c>erlang:system_info(allocated_areas)</c></seealso>.</p>
   </section>
 
   <section>
     <marker id="allocator"></marker>
     <title>Allocator</title>
-    <p>Under the tag <em>=allocator:&lt;A&gt;</em> you will find
+    <p>Under the tag <em>=allocator:&lt;A&gt;</em> is shown
       various information about allocator &lt;A&gt;. The information
-      is similar to what you can obtain on a living node with
-      <seealso marker="erts:erlang#system_info_allocator_tuple">erlang:system_info({allocator, &lt;A&gt;})</seealso>.
-      For more information see the documentation of
-      <seealso marker="erts:erlang#system_info_allocator_tuple">erlang:system_info({allocator, &lt;A&gt;})</seealso>,
-      and the
-      <seealso marker="erts_alloc">erts_alloc(3)</seealso>
-      documentation.</p>
+      is similar to what can be obtained on a living node with
+      <seealso marker="erts:erlang#system_info_allocator_tuple">
+      <c>erlang:system_info({allocator, &lt;A&gt;})</c></seealso>.
+      For more information, see also
+      <seealso marker="erts_alloc"><c>erts_alloc(3)</c></seealso>.</p>
   </section>
 
   <section>
     <marker id="processes"></marker>
-    <title>Process information</title>
+    <title>Process Information</title>
     <p>The Erlang crashdump contains a listing of each living Erlang
-      process in the system. The process information for one process
-      may look like this (line numbers have been added):
-      </p>
-    <p>The following fields can exist for a process:</p>
+      process in the system. The following fields can exist for a process:</p>
+
     <taglist>
       <tag><em>=proc:&lt;pid&gt;</em></tag>
-      <item>Heading, states the process identifier</item>
+      <item>
+        <p>Heading. States the process identifier.</p>
+      </item>
       <tag><em>State</em></tag>
       <item>
         <p>The state of the process. This can be one of the following:</p>
-        <list type="bulleted">
-          <item><em>Scheduled</em> - The process was scheduled to run
-           but not currently running ("in the run queue").</item>
-          <item><em>Waiting</em> - The process was waiting for
-           something (in <c><![CDATA[receive]]></c>).</item>
-          <item><em>Running</em> - The process was currently
-           running. If the BIF <c><![CDATA[erlang:halt/1]]></c> was called, this was
-           the process calling it.</item>
-          <item><em>Exiting</em> - The process was on its way to
-           exit.</item>
-          <item><em>Garbing</em> - This is bad luck, the process was
-           garbage collecting when the crash dump was written, the rest
-           of the information for this process is limited.</item>
-          <item><em>Suspended</em> - The process is suspended, either
-           by the BIF <c><![CDATA[erlang:suspend_process/1]]></c> or because it is
-           trying to write to a busy port.</item>
-        </list>
+        <taglist>
+          <tag><em>Scheduled</em></tag>
+          <item>The process was scheduled to run
+            but is currently not running ("in the run queue").</item>
+          <tag><em>Waiting</em></tag>
+          <item>The process was waiting for
+            something (in <c><![CDATA[receive]]></c>).</item>
+          <tag><em>Running</em></tag>
+          <item>The process was currently running.
+            If the BIF <c><![CDATA[erlang:halt/1]]></c> was called, this was
+            the process calling it.</item>
+          <tag><em>Exiting</em></tag>
+          <item>The process was on its way to exit.</item>
+          <tag><em>Garbing</em></tag>
+          <item>This is bad luck, the process was
+            garbage collecting when the crash dump was written. The rest
+            of the information for this process is limited.</item>
+          <tag><em>Suspended</em></tag>
+          <item>The process is suspended, either
+            by the BIF <c><![CDATA[erlang:suspend_process/1]]></c> or because
+            it tries to write to a busy port.</item>
+        </taglist>
       </item>
       <tag><em>Registered name</em></tag>
-      <item>The registered name of the process, if any.</item>
+      <item>
+        <p>The registered name of the process, if any.</p>
+      </item>
       <tag><em>Spawned as</em></tag>
-      <item>The entry point of the process, i.e., what function was
-       referenced in the <c><![CDATA[spawn]]></c> or <c><![CDATA[spawn_link]]></c> call that
-       started the process.</item>
+      <item>
+        <p>The entry point of the process, that is, what function was
+          referenced in the <c><![CDATA[spawn]]></c> or
+          <c><![CDATA[spawn_link]]></c> call that
+          started the process.</p>
+      </item>
       <tag><em>Last scheduled in for | Current call</em></tag>
-      <item>The current function of the process. These fields will not
-       always exist.</item>
+      <item>
+        <p>The current function of the process. These fields do not
+          always exist.</p>
+      </item>
       <tag><em>Spawned by</em></tag>
-      <item>The parent of the process, i.e. the process which executed
-      <c><![CDATA[spawn]]></c> or <c><![CDATA[spawn_link]]></c>.</item>
+      <item>
+        <p>The parent of the process, that is, the process that executed
+          <c><![CDATA[spawn]]></c> or <c><![CDATA[spawn_link]]></c>.</p>
+      </item>
       <tag><em>Started</em></tag>
-      <item>The date and time when the process was started.</item>
+      <item>
+        <p>The date and time when the process was started.</p>
+      </item>
       <tag><em>Message queue length</em></tag>
-      <item>The number of messages in the process' message queue.</item>
+      <item>
+        <p>The number of messages in the process' message queue.</p>
+      </item>
       <tag><em>Number of heap fragments</em></tag>
-      <item>The number of allocated heap fragments.</item>
+      <item>
+        <p>The number of allocated heap fragments.</p>
+      </item>
       <tag><em>Heap fragment data</em></tag>
-      <item>Size of fragmented heap data. This is data either created by
-       messages being sent to the process or by the Erlang BIFs. This
-       amount depends on so many things that this field is utterly
-       uninteresting.</item>
+      <item>
+        <p>Size of fragmented heap data. This is data either created by
+          messages sent to the process or by the Erlang BIFs. This
+          amount depends on so many things that this field is utterly
+          uninteresting.</p>
+      </item>
       <tag><em>Link list</em></tag>
-      <item>Process id's of processes linked to this one. May also contain
-       ports. If process monitoring is used, this field also tells in
-       which direction the monitoring is in effect, i.e., a link
-       being "to" a process tells you that the "current" process was
-       monitoring the other and a link "from" a process tells you
-       that the other process was monitoring the current one.</item>
+      <item>
+        <p>Process IDs of processes linked to this one. Can also contain
+          ports. If process monitoring is used, this field also tells in
+          which direction the monitoring is in effect. That is, a link
+          "to" a process tells you that the "current" process was
+          monitoring the other, and a link "from" a process tells you
+         that the other process was monitoring the current one.</p>
+      </item>
       <tag><em>Reductions</em></tag>
-      <item>The number of reductions consumed by the process.</item>
+      <item>
+        <p>The number of reductions consumed by the process.</p>
+      </item>
       <tag><em>Stack+heap</em></tag>
-      <item>The size of the stack and heap (they share memory segment)</item>
+      <item>
+        <p>The size of the stack and heap (they share memory segment).</p>
+      </item>
       <tag><em>OldHeap</em></tag>
-      <item>The size of the "old heap". The Erlang virtual machine uses
-       generational garbage collection with two generations. There is
-       one heap for new data items and one for the data that have
-       survived two garbage collections. The assumption (which is
-       almost always correct) is that data that survive two garbage
-       collections can be "tenured" to a heap more seldom garbage
-       collected, as they will live for a long period. This is a
-       quite usual technique in virtual machines.  The sum of the
-       heaps and stack together constitute most of the process's
-       allocated memory.</item>
+      <item>
+        <p>The size of the "old heap". The Erlang virtual machine uses
+          generational garbage collection with two generations. There is
+          one heap for new data items and one for the data that has
+          survived two garbage collections. The assumption (which is
+          almost always correct) is that data surviving two garbage
+          collections can be "tenured" to a heap more seldom garbage
+          collected, as they will live for a long period. This is a
+          usual technique in virtual machines. The sum of the
+          heaps and stack together constitute most of the
+          allocated memory of the process.</p>
+      </item>
       <tag><em>Heap unused, OldHeap unused</em></tag>
-      <item>The amount of unused memory on each heap. This information is
-       usually useless.</item>
+      <item>
+        <p>The amount of unused memory on each heap. This information is
+          usually useless.</p>
+      </item>
       <tag><em>Stack</em></tag>
-      <item>If the system uses shared heap, the fields
-      <em>Stack+heap</em>, <em>OldHeap</em>, <em>Heap unused</em>
-       and <em>OldHeap unused</em> do not exist. Instead this field
-       presents the size of the process' stack.</item>
+      <item>
+        <p>If the system uses shared heap, the fields
+          <em>Stack+heap</em>, <em>OldHeap</em>, <em>Heap unused</em>,
+          and <em>OldHeap unused</em> do not exist. Instead this field
+          shows the size of the process stack.</p>
+      </item>
       <tag><em>Memory</em></tag>
-      <item>The total memory used by this process. This includes call stack,
-      heap and internal structures. Same as <seealso marker="erlang#process_info-2">erlang:process_info(Pid,memory)</seealso>.
+      <item>
+        <p>The total memory used by this process. This includes call stack,
+          heap, and internal structures. Same as
+          <seealso marker="erlang#process_info-2">
+          <c>erlang:process_info(Pid,memory)</c></seealso>.</p>
       </item>
       <tag><em>Program counter</em></tag>
-      <item>The current instruction pointer. This is only interesting for
-       runtime system developers. The function into which the program
-       counter points is the current function of the process.</item>
+      <item>
+        <p>The current instruction pointer. This is only of interest for
+          runtime system developers. The function into which the program
+          counter points is the current function of the process.</p>
+      </item>
       <tag><em>CP</em></tag>
-      <item>The continuation pointer, i.e. the return address for the
-       current call. Usually useless for other than runtime system
-       developers. This may be followed by the function into which
-       the CP points, which is the function calling the current
-       function.</item>
+      <item>
+        <p>The continuation pointer, that is, the return address for the
+          current call. Usually useless for other than runtime system
+          developers. This can be followed by the function into which
+          the CP points, which is the function calling the current
+          function.</p>
+      </item>
       <tag><em>Arity</em></tag>
-      <item>The number of live argument registers. The argument registers,
-       if any are live, will follow. These may contain the arguments
-       of the function if they are not yet moved to the stack.</item>
-       <item><em>Internal State</em></item>
-       <item>A more detailed internal represantation of the state of
-       this process.</item>
+      <item>
+        <p>The number of live argument registers. The argument registers
+          if any are live will follow. These can contain the arguments
+          of the function if they are not yet moved to the stack.</p>
+      </item>
+      <tag><em>Internal State</em></tag>
+      <item>
+        <p>A more detailed internal representation of the state of
+          this process.</p>
+      </item>
     </taglist>
-    <p>See also the section about <seealso marker="#proc_data">process data</seealso>.</p>
+    <p>See also section <seealso marker="#proc_data">Process Data</seealso>.</p>
   </section>
 
   <section>
     <marker id="ports"></marker>
-    <title>Port information</title>
+    <title>Port Information</title>
     <p>This section lists the open ports, their owners, any linked
-      processed, and the name of their driver or external process.</p>
+      processes, and the name of their driver or external process.</p>
   </section>
 
   <section>
     <marker id="ets_tables"></marker>
-    <title>ETS tables</title>
-    <p>This section contains information about all the ETS tables in
-      the system. The following fields are interesting for each table:</p>
+    <title>ETS Tables</title>
+    <p>This section contains information about all the <c>ets</c> tables in
+      the system. The following fields are of interest for each table:</p>
+
     <taglist>
       <tag><em>=ets:&lt;owner&gt;</em></tag>
-      <item>Heading, states the owner of the table (a process identifier)</item>
+      <item>
+        <p>Heading. States the table owner (a process identifier).</p>
+      </item>
       <tag><em>Table</em></tag>
-      <item>The identifier for the table. If the table is a
-      <c><![CDATA[named_table]]></c>, this is the name.</item>
+      <item>
+        <p>The identifier for the table. If the table is a
+          <c><![CDATA[named_table]]></c>, this is the name.</p>
+      </item>
       <tag><em>Name</em></tag>
-      <item>The name of the table, regardless of whether it is a
-      <c><![CDATA[named_table]]></c> or not.</item>
+      <item>
+        <p>The table name, regardless of if it is a
+          <c><![CDATA[named_table]]></c> or not.</p>
+      </item>
       <tag><em>Hash table, Buckets</em></tag>
-      <item>This occurs if the table is a hash table, i.e. if it is not an
-      <c><![CDATA[ordered_set]]></c>.</item>
+      <item>
+        <p>If the table is a hash table, that is, if it is not an
+          <c><![CDATA[ordered_set]]></c>.</p>
+      </item>
       <tag><em>Hash table, Chain Length</em></tag>
-      <item>Only applicable for hash tables. Contains statistics about the
-      hash table, such as the max, min and avg chain length. Having a max much
-      larger than the avg, and a std dev much larger that
-      the expected std dev is a sign that the hashing of the terms is
-      behaving badly for some reason.</item>
+      <item>
+        <p>If the table is a hash table. Contains statistics about the
+          table, such as the maximum, minimum, and average chain length.
+          Having a maximum much larger than the average, and a standard
+          deviation much larger than the expected standard deviation is
+          a sign that the hashing of the terms
+          behaves badly for some reason.</p>
+      </item>
       <tag><em>Ordered set (AVL tree), Elements</em></tag>
-      <item>This occurs only if the table is an <c><![CDATA[ordered_set]]></c>. (The
-       number of elements is the same as the number of objects in the
-       table.)</item>
+      <item>
+        <p>If the table is an <c><![CDATA[ordered_set]]></c>. (The
+          number of elements is the same as the number of objects in the
+          table.)</p>
+      </item>
       <tag><em>Fixed</em></tag>
-      <item>If the table is fixed using ets:safe_fixtable or some internal
-      mechanism.</item>
+      <item>
+        <p>If the table is fixed using
+          <seealso marker="stdlib:ets#ets:safe_fixtable">
+          <c>ets:safe_fixtable</c></seealso> or some internal mechanism.</p>
+      </item>
       <tag><em>Objects</em></tag>
-      <item>The number of objects in the table</item>
+      <item>
+        <p>The number of objects in the table.</p>
+      </item>
       <tag><em>Words</em></tag>
-      <item>The number of words (usually 4 bytes/word) allocated to data
-       in the table.</item>
+      <item>
+        <p>The number of words (usually 4 bytes/word) allocated to data
+          in the table.</p>
+      </item>
       <tag><em>Type</em></tag>
-      <item>The type of the table, i.e. <c>set</c>, <c>bag</c>,
-      <c>dublicate_bag</c> or <c>ordered_set</c>.</item>
+      <item>
+        <p>The table type, that is, <c>set</c>, <c>bag</c>,
+          <c>dublicate_bag</c>, or <c>ordered_set</c>.</p>
+      </item>
       <tag><em>Compressed</em></tag>
-      <item>If this table was compressed.</item>
+      <item>
+        <p>If the table was compressed.</p>
+      </item>
       <tag><em>Protection</em></tag>
-      <item>The protection of this table.</item>
+      <item>
+        <p>The protection of the table.</p>
+      </item>
       <tag><em>Write Concurrency</em></tag>
-      <item>If write_concurrency was enabled for this table.</item>
+      <item>
+        <p>If <c>write_concurrency</c> was enabled for the table.</p>
+      </item>
       <tag><em>Read Concurrency</em></tag>
-      <item>If read_concurrency was enabled for this table.</item>
+      <item>
+        <p>If <c>read_concurrency</c> was enabled for the table.</p>
+      </item>
     </taglist>
   </section>
 
@@ -435,167 +573,252 @@
     <title>Timers</title>
     <p>This section contains information about all the timers started
       with the BIFs <c><![CDATA[erlang:start_timer/3]]></c> and
-      <c><![CDATA[erlang:send_after/3]]></c>. The following fields exists for each
-      timer:</p>
+      <c><![CDATA[erlang:send_after/3]]></c>. The following fields exist
+      for each timer:</p>
+
     <taglist>
       <tag><em>=timer:&lt;owner&gt;</em></tag>
-      <item>Heading, states the owner of the timer (a process identifier)
-       i.e. the process to receive the message when the timer
-       expires.</item>
+      <item>
+        <p>Heading. States the timer owner (a process identifier),
+          that is, the process to receive the message when the timer
+          expires.</p>
+      </item>
       <tag><em>Message</em></tag>
-      <item>The message to be sent.</item>
+      <item>
+        <p>The message to be sent.</p>
+      </item>
       <tag><em>Time left</em></tag>
-      <item>Number of milliseconds left until the message would have been
-       sent.</item>
+      <item>
+        <p>Number of milliseconds left until the message would have been
+          sent.</p>
+      </item>
     </taglist>
   </section>
 
   <section>
     <marker id="distribution_info"></marker>
-    <title>Distribution information</title>
-    <p>If the Erlang node was alive, i.e., set up for communicating
+    <title>Distribution Information</title>
+    <p>If the Erlang node was alive, that is, set up for communicating
       with other nodes, this section lists the connections that were
       active. The following fields can exist:</p>
+
     <taglist>
       <tag><em>=node:&lt;node_name&gt;</em></tag>
-      <item>The name of the node</item>
+      <item>
+        <p>The node name.</p>
+      </item>
       <tag><em>no_distribution</em></tag>
-      <item>This will only occur if the node was not distributed.</item>
+      <item>
+        <p>If the node was not distributed.</p>
+      </item>
       <tag><em>=visible_node:&lt;channel&gt;</em></tag>
-      <item>Heading for a visible nodes, i.e. an alive node with a
-       connection to the node that crashed. States the channel number
-       for the node.</item>
+      <item>
+        <p>Heading for a visible node, that is, an alive node with a
+          connection to the node that crashed. States the channel number
+          for the node.</p>
+      </item>
       <tag><em>=hidden_node:&lt;channel&gt;</em></tag>
-      <item>Heading for a hidden node. A hidden node is the same as a
-       visible node, except that it is started with the "-hidden"
-       flag. States the channel number for the node.</item>
+      <item>
+        <p>Heading for a hidden node. A hidden node is the same as a
+          visible node, except that it is started with the <c>"-hidden"</c>
+          flag. States the channel number for the node.</p>
+      </item>
       <tag><em>=not_connected:&lt;channel&gt;</em></tag>
-      <item>Heading for a node which is has been connected to the crashed
-       node earlier. References (i.e. process or port identifiers)
-       to the not connected node existed at the time of the crash.
-       exist. States the channel number for the node.</item>
+      <item>
+        <p>Heading for a node that was connected to the crashed
+          node earlier. References (that is, process or port identifiers)
+          to the not connected node existed at the time of the crash.
+          States the channel number for the node.</p>
+      </item>
       <tag><em>Name</em></tag>
-      <item>The name of the remote node.</item>
+      <item>
+        <p>The name of the remote node.</p>
+      </item>
       <tag><em>Controller</em></tag>
-      <item>The port which controls the communication with the remote node.</item>
+      <item>
+        <p>The port controlling communication with the remote node.</p>
+      </item>
       <tag><em>Creation</em></tag>
-      <item>An integer (1-3) which together with the node name identifies
-       a specific instance of the node.</item>
-      <tag><em>Remote monitoring: &lt;local_proc&gt;  &lt;remote_proc&gt;</em></tag>
-      <item>The local process was monitoring the remote process at the
-       time of the crash.</item>
-      <tag><em>Remotely monitored by: &lt;local_proc&gt;  &lt;remote_proc&gt;</em></tag>
-      <item>The remote process was monitoring the local process at the
-       time of the crash.</item>
+      <item>
+        <p>An integer (1-3) that together with the node name identifies
+          a specific instance of the node.</p>
+      </item>
+      <tag><em>Remote monitoring: &lt;local_proc&gt;  &lt;remote_proc&gt;</em>
+      </tag>
+      <item>
+        <p>The local process was monitoring the remote process at the
+          time of the crash.</p>
+      </item>
+      <tag><em>Remotely monitored by: &lt;local_proc&gt;
+        &lt;remote_proc&gt;</em></tag>
+      <item>
+        <p>The remote process was monitoring the local process at the
+          time of the crash.</p>
+      </item>
       <tag><em>Remote link: &lt;local_proc&gt; &lt;remote_proc&gt;</em></tag>
-      <item>A link existed between the local process and the remote
-       process at the time of the crash.</item>
+      <item>
+        <p>A link existed between the local process and the remote
+          process at the time of the crash.</p>
+      </item>
     </taglist>
   </section>
 
   <section>
     <marker id="loaded_modules"></marker>
-    <title>Loaded module information</title>
-    <p>This section contains information about all loaded modules.
-      First, the memory usage by loaded code is summarized. There is
-      one field for "Current code" which is code that is the current
-      latest version of the modules. There is also a field for "Old
-      code" which is code where there exists a newer version in the
-      system, but the old version is not yet purged. The memory usage
-      is in bytes.</p>
-    <p>All loaded modules are then listed. The following fields exist:</p>
+    <title>Loaded Module Information</title>
+    <p>This section contains information about all loaded modules.</p>
+
+    <p>First, the memory use by the loaded code is summarized:</p>
+
+    <taglist>
+      <tag><em>Current code</em></tag>
+      <item>
+        <p>Code that is the current latest version of the modules.</p>
+      </item>
+      <tag><em>Old code</em></tag>
+      <item>
+        <p>Code where there exists a newer version in the
+          system, but the old version is not yet purged.</p>
+      </item>
+    </taglist>
+
+    <p>The memory use is in bytes.</p>
+
+    <p>Then, all loaded modules are listed. The following fields exist:</p>
+
     <taglist>
       <tag><em>=mod:&lt;module_name&gt;</em></tag>
-      <item>Heading, and the name of the module.</item>
+      <item>
+        <p>Heading. States the module name.</p>
+      </item>
       <tag><em>Current size</em></tag>
-      <item>Memory usage for the loaded code in bytes</item>
+      <item>
+        <p>Memory use for the loaded code, in bytes.</p>
+      </item>
       <tag><em>Old size</em></tag>
-      <item>Memory usage for the old code, if any.</item>
+      <item>
+        <p>Memory use for the old code, if any.</p>
+      </item>
       <tag><em>Current attributes</em></tag>
-      <item>Module attributes for the current code. This field is decoded
-       when looked at by the Crashdump Viewer tool.</item>
+      <item>
+        <p>Module attributes for the current code. This field is decoded
+          when looked at by the Crashdump Viewer tool.</p>
+      </item>
       <tag><em>Old attributes</em></tag>
-      <item>Module attributes for the old code, if any. This field is
-       decoded when looked at by the Crashdump Viewer tool.</item>
+      <item>
+        <p>Module attributes for the old code, if any. This field is
+          decoded when looked at by the Crashdump Viewer tool.</p>
+      </item>
       <tag><em>Current compilation info</em></tag>
-      <item>Compilation information (options) for the current code. This
-       field is decoded when looked at by the Crashdump Viewer tool.</item>
+      <item>
+        <p>Compilation information (options) for the current code. This
+          field is decoded when looked at by the Crashdump Viewer tool.</p>
+      </item>
       <tag><em>Old compilation info</em></tag>
-      <item>Compilation information (options) for the old code, if
-       any. This field is decoded when looked at by the Crashdump
-       Viewer tool.</item>
+      <item>
+        <p>Compilation information (options) for the old code, if
+          any. This field is decoded when looked at by the Crashdump
+          Viewer tool.</p>
+      </item>
     </taglist>
   </section>
 
   <section>
     <marker id="funs"></marker>
-    <title>Fun information</title>
-    <p>In this section, all funs are listed. The following fields exist
-      for each fun:</p>
+    <title>Fun Information</title>
+    <p>This section lists all funs. The following fields exist for each fun:</p>
+
     <taglist>
       <tag><em>=fun</em></tag>
-      <item>Heading</item>
+      <item>
+        <p>Heading.</p>
+      </item>
       <tag><em>Module</em></tag>
-      <item>The name of the module where the fun was defined.</item>
+      <item>
+        <p>The name of the module where the fun was defined.</p>
+      </item>
       <tag><em>Uniq, Index</em></tag>
-      <item>Identifiers</item>
+      <item>
+        <p>Identifiers.</p>
+      </item>
       <tag><em>Address</em></tag>
-      <item>The address of the fun's code.</item>
+      <item>
+        <p>The address of the fun's code.</p>
+      </item>
       <tag><em>Native_address</em></tag>
-      <item>The address of the fun's code when HiPE is enabled.</item>
+      <item>
+        <p>The address of the fun's code when HiPE is enabled.</p>
+      </item>
       <tag><em>Refc</em></tag>
-      <item>The number of references to the fun.</item>
+      <item>
+        <p>The number of references to the fun.</p>
+      </item>
     </taglist>
   </section>
 
   <section>
     <marker id="proc_data"></marker>
     <title>Process Data</title>
-    <p>For each process there will be at least one <em>=proc_stack</em>
-      and one <em>=proc_heap</em> tag followed by the raw memory
+    <p>For each process there is at least one <em>=proc_stack</em>
+      and one <em>=proc_heap</em> tag, followed by the raw memory
       information for the stack and heap of the process.</p>
-    <p>For each process there will also be a <em>=proc_messages</em>
-      tag if the process' message queue is non-empty and a
-      <em>=proc_dictionary</em> tag if the process' dictionary (the
-      <c><![CDATA[put/2]]></c> and <c><![CDATA[get/1]]></c> thing) is non-empty.</p>
+
+    <p>For each process there is also a <em>=proc_messages</em>
+      tag if the process message queue is non-empty, and a
+      <em>=proc_dictionary</em> tag if the process dictionary (the
+      <c><![CDATA[put/2]]></c> and <c><![CDATA[get/1]]></c> thing) is
+      non-empty.</p>
+
     <p>The raw memory information can be decoded by the Crashdump
-      Viewer tool. You will then be able to see the stack dump, the
-      message queue (if any) and the dictionary (if any).</p>
+      Viewer tool. You can then see the stack dump, the
+      message queue (if any), and the dictionary (if any).</p>
+
     <p>The stack dump is a dump of the Erlang process stack. Most of
-      the live data (i.e., variables currently in use) are placed on
-      the stack; thus this can be quite interesting. One has to
-      "guess" what's what, but as the information is symbolic,
-      thorough reading of this information can be very useful. As an
-      example we can find the state variable of the Erlang primitive
-      loader on line <c><![CDATA[(5)]]></c> in the example below:</p>
+      the live data (that is, variables currently in use) are placed on
+      the stack; thus this can be interesting. One has to
+      "guess" what is what, but as the information is symbolic,
+      thorough reading of this information can be useful. As an
+      example, we can find the state variable of the Erlang primitive
+      loader online <c><![CDATA[(5)]]></c> and <c><![CDATA[(6)]]></c>
+      in the following example:</p>
+
     <code type="none"><![CDATA[
 (1)  3cac44   Return addr 0x13BF58 (<terminate process normally>)
-(2)  y(0)     ["/view/siri_r10_dev/clearcase/otp/erts/lib/kernel/ebin","/view/siri_r10_dev/
-(3)  clearcase/otp/erts/lib/stdlib/ebin"]
+(2)  y(0)     ["/view/siri_r10_dev/clearcase/otp/erts/lib/kernel/ebin",
+(3)            "/view/siri_r10_dev/clearcase/otp/erts/lib/stdlib/ebin"]
 (4)  y(1)     <0.1.0>
-(5)  y(2)     {state,[],none,#Fun<erl_prim_loader.6.7085890>,undefined,#Fun<erl_prim_loader.7.9000327>,#Fun<erl_prim_loader.8.116480692>,#Port<0.2>,infinity,#Fun<erl_prim_loader.9.10708760>}
-(6)  y(3)     infinity    ]]></code>
+(5)  y(2)     {state,[],none,#Fun<erl_prim_loader.6.7085890>,undefined,#Fun<erl_prim_loader.7.9000327>,
+(6)            #Fun<erl_prim_loader.8.116480692>,#Port<0.2>,infinity,#Fun<erl_prim_loader.9.10708760>}
+(7)  y(3)     infinity    ]]></code>
+
     <p>When interpreting the data for a process, it is helpful to know
-      that anonymous function objects (funs) are given a name
-      constructed from the name of the function in which they are
-      created, and a number (starting with 0) indicating the number of
-      that fun within that function.</p>
+      that anonymous function objects (funs) are given the following:</p>
+
+    <list type="bulleted">
+      <item>A name constructed from the name of the function in which they are
+        created
+      </item>
+      <item>A number (starting with 0) indicating the number of that fun within
+        that function
+      </item>
+    </list>
   </section>
 
   <section>
     <marker id="atoms"></marker>
     <title>Atoms</title>
-    <p>Now all the atoms in the system are written. This is only
-      interesting if one suspects that dynamic generation of atoms could
+    <p>This section presents all the atoms in the system. This is only
+      of interest if one suspects that dynamic generation of atoms can
       be a problem, otherwise this section can be ignored.</p>
-    <p>Note that the last created atom is printed first.</p>
+
+    <p>Notice that the last created atom is shown first.</p>
   </section>
 
   <section>
     <title>Disclaimer</title>
-    <p>The format of the crash dump evolves between releases of
-      OTP. Some information here may not apply to your
-      version. A description as this will never be complete; it is meant as
+    <p>The format of the crash dump evolves between OTP releases.
+      Some information described here may not apply to your
+      version. A description like this will never be complete; it is meant as
       an explanation of the crash dump in general and as a help
       when trying to find application errors, not as a complete
       specification.</p>
diff --git a/erts/doc/src/driver.xml b/erts/doc/src/driver.xml
index 4bef5e1388..2dae01b143 100644
--- a/erts/doc/src/driver.xml
+++ b/erts/doc/src/driver.xml
@@ -22,103 +22,115 @@
 
     </legalnotice>
 
-    <title>How to implement a driver</title>
+    <title>How to Implement a Driver</title>
     <prepared>Jakob C</prepared>
     <docno></docno>
     <date>2000-11-28</date>
     <rev>PA1</rev>
     <file>driver.xml</file>
   </header>
-
-  <note><p>This document was written a long time ago. A lot of it is still
-           interesting since it explains important concepts, but it was
-	   written for an older driver interface so the examples do not
-	   work anymore. The reader is encouraged to read
-	   <seealso marker="erl_driver">erl_driver</seealso> and the
-	   <seealso marker="driver_entry">driver_entry</seealso> documentation.
-   </p></note>
+  <note>
+    <p>This section was written a long time ago. Most of it is still
+      valid, as it explains important concepts, but this was
+      written for an older driver interface so the examples do not
+      work anymore. The reader is encouraged to read the
+      <seealso marker="erl_driver"><c>erl_driver</c></seealso> and
+      <seealso marker="driver_entry"><c>driver_entry</c></seealso>
+      documentation also.</p>
+  </note>
 
   <section>
     <title>Introduction</title>
-    <p>This chapter tells you how to build your own driver for erlang.</p>
-    <p>A driver in Erlang is a library written in C, that is linked to
-      the Erlang emulator and called from erlang. Drivers can be used
-      when C is more suitable than Erlang, to speed things up, or to
-      provide access to OS resources not directly accessible from
-      Erlang.</p>
+    <p>This section describes how to build your own driver for Erlang.</p>
+
+    <p>A driver in Erlang is a library written in C, which is linked to
+      the Erlang emulator and called from Erlang. Drivers can be used
+      when C is more suitable than Erlang, to speed up things, or to
+      provide access to OS resources not directly accessible from Erlang.</p>
+
     <p>A driver can be dynamically loaded, as a shared library (known as
-      a DLL on windows), or statically loaded, linked with the emulator
+      a DLL on Windows), or statically loaded, linked with the emulator
       when it is compiled and linked. Only dynamically loaded drivers
       are described here, statically linked drivers are beyond the scope
-      of this chapter.</p>
-    <p>When a driver is loaded it is executed in the context of the
-      emulator, shares the same memory and the same thread. This means
-      that all operations in the driver must be non-blocking, and that
-      any crash in the driver will bring the whole emulator down. In
-      short: you have to be extremely careful!</p>
-    <p></p>
+      of this section.</p>
+
+    <warning>
+      <p>When a driver is loaded it is executed in the context of the
+        emulator, shares the same memory and the same thread. This means
+        that all operations in the driver must be non-blocking, and that
+        any crash in the driver brings the whole emulator down. In short,
+        be careful.</p>
+    </warning>
   </section>
 
   <section>
-    <title>Sample driver</title>
-    <p>This is a simple driver for accessing a postgres
+    <title>Sample Driver</title>
+    <p>This section describes a simple driver for accessing a postgres
       database using the libpq C client library. Postgres
-      is used because it's free and open source. For information
-      on postgres, refer to the website
-      <url href="http://www.postgres.org">www.postgres.org</url>.</p>
+      is used because it is free and open source. For information on postgres,
+      see <url href="http://www.postgres.org">www.postgres.org</url>.</p>
+
     <p>The driver is synchronous, it uses the synchronous calls of
-      the client library. This is only for simplicity, and is
-      generally not good, since it will
-      halt the emulator while waiting for the database.
-      This will be improved on below with an asynchronous
-      sample driver.</p>
-    <p>The code is quite straight-forward: all
+      the client library. This is only for simplicity, but not good, as it
+      halts the emulator while waiting for the database.
+      This is improved below with an asynchronous sample driver.</p>
+
+    <p>The code is straightforward: all
       communication between Erlang and the driver
       is done with <c><![CDATA[port_control/3]]></c>, and the
       driver returns data back using the <c><![CDATA[rbuf]]></c>.</p>
+
     <p>An Erlang driver only exports one function: the driver
       entry function. This is defined with a macro,
-      <c><![CDATA[DRIVER_INIT]]></c>, and returns a pointer to a
+      <c><![CDATA[DRIVER_INIT]]></c>, which returns a pointer to a
       C <c><![CDATA[struct]]></c> containing the entry points that are
       called from the emulator. The <c><![CDATA[struct]]></c> defines the
       entries that the emulator calls to call the driver, with
       a <c><![CDATA[NULL]]></c> pointer for entries that are not defined
       and used by the driver.</p>
+
     <p>The <c><![CDATA[start]]></c> entry is called when the driver
       is opened as a port with <c><![CDATA[open_port/2]]></c>. Here
       we allocate memory for a user data structure.
-      This user data will be passed every time the emulator
-      calls us. First we store the driver handle, because it
-      is needed in subsequent calls. We allocate memory for
+      This user data is passed every time the emulator
+      calls us. First we store the driver handle, as it
+      is needed in later calls. We allocate memory for
       the connection handle that is used by LibPQ. We also
       set the port to return allocated driver binaries, by
-      setting the flag <c><![CDATA[PORT_CONTROL_FLAG_BINARY]]></c>, calling
+      setting flag <c><![CDATA[PORT_CONTROL_FLAG_BINARY]]></c>, calling
       <c><![CDATA[set_port_control_flags]]></c>. (This is because
-      we don't know whether our data will fit in the
-      result buffer of <c><![CDATA[control]]></c>, which has a default size
-      set up by the emulator, currently 64 bytes.)</p>
-    <p>There is an entry <c><![CDATA[init]]></c> which is called when
-      the driver is loaded, but we don't use this, since
+      we do not know if our data will fit in the
+      result buffer of <c><![CDATA[control]]></c>, which has a default size,
+      64 bytes, set up by the emulator.)</p>
+
+    <p>An entry <c><![CDATA[init]]></c> is called when
+      the driver is loaded. However, we do not use this, as
       it is executed only once, and we want to have the
       possibility of several instances of the driver.</p>
+
     <p>The <c><![CDATA[stop]]></c> entry is called when the port
       is closed.</p>
+
     <p>The <c><![CDATA[control]]></c> entry is called from the emulator
       when the Erlang code calls <c><![CDATA[port_control/3]]></c>,
       to do the actual work. We have defined a simple set of
-      commands: <c><![CDATA[connect]]></c> to login to the database, <c><![CDATA[disconnect]]></c>
-      to log out and <c><![CDATA[select]]></c> to send a SQL-query and get the result.
+      commands: <c><![CDATA[connect]]></c> to log on to the database,
+      <c><![CDATA[disconnect]]></c> to log out, and <c><![CDATA[select]]></c>
+      to send a SQL-query and get the result.
       All results are returned through <c><![CDATA[rbuf]]></c>.
-      The library <c><![CDATA[ei]]></c> in <c><![CDATA[erl_interface]]></c> is used
-      to encode data in binary term format. The result is returned
+      The library <c><![CDATA[ei]]></c> in <c><![CDATA[erl_interface]]></c> is
+      used to encode data in binary term format. The result is returned
       to the emulator as binary terms, so <c><![CDATA[binary_to_term]]></c>
       is called in Erlang to convert the result to term form.</p>
-    <p>The code is available in <c><![CDATA[pg_sync.c]]></c> in the <c><![CDATA[sample]]></c>
-      directory of <c><![CDATA[erts]]></c>.</p>
+
+    <p>The code is available in <c><![CDATA[pg_sync.c]]></c> in the
+      <c><![CDATA[sample]]></c> directory of <c><![CDATA[erts]]></c>.</p>
+
     <p>The driver entry contains the functions that
-      will be called by the emulator. In our simple
-      example, we only provide <c><![CDATA[start]]></c>, <c><![CDATA[stop]]></c>
-      and <c><![CDATA[control]]></c>.</p>
+      will be called by the emulator. In this simple example,
+      only <c><![CDATA[start]]></c>, <c><![CDATA[stop]]></c>,
+      and <c><![CDATA[control]]></c> are provided:</p>
+
     <code type="none"><![CDATA[
 /* Driver interface declarations */
 static ErlDrvData start(ErlDrvPort port, char *command);
@@ -128,15 +140,15 @@ static int control(ErlDrvData drv_data, unsigned int command, char *buf,
 
 static ErlDrvEntry pq_driver_entry = {
     NULL,                        /* init */
-    start, 
-    stop, 
+    start,
+    stop,
     NULL,                        /* output */
     NULL,                        /* ready_input */
-    NULL,                        /* ready_output */ 
+    NULL,                        /* ready_output */
     "pg_sync",                   /* the name of the driver */
     NULL,                        /* finish */
     NULL,                        /* handle */
-    control, 
+    control,
     NULL,                        /* timeout */
     NULL,                        /* outputv */
     NULL,                        /* ready_async */
@@ -145,14 +157,18 @@ static ErlDrvEntry pq_driver_entry = {
     NULL                         /* event */
 };
     ]]></code>
+
     <p>We have a structure to store state needed by the driver,
-      in this case we only need to keep the database connection.</p>
+      in this case we only need to keep the database connection:</p>
+
     <code type="none"><![CDATA[
 typedef struct our_data_s {
     PGconn* conn;
 } our_data_t;
     ]]></code>
-    <p>These are control codes we have defined.</p>
+
+    <p>The control codes that we have defined are as follows:</p>
+
     <code type="none"><![CDATA[
 /* Keep the following definitions in alignment with the
  * defines in erl_pq_sync.erl
@@ -162,10 +178,12 @@ typedef struct our_data_s {
 #define DRV_DISCONNECT          'D'
 #define DRV_SELECT              'S'
     ]]></code>
-    <p>This just returns the driver structure. The macro
+
+    <p>This only returns the driver structure. The macro
       <c><![CDATA[DRIVER_INIT]]></c> defines the only exported function.
       All the other functions are static, and will not be exported
       from the library.</p>
+
     <code type="none"><![CDATA[
 /* INITIALIZATION AFTER LOADING */
 
@@ -180,9 +198,11 @@ DRIVER_INIT(pq_drv)
     return &pq_driver_entry;
 }
     ]]></code>
-    <p>Here we do some initialization, <c><![CDATA[start]]></c> is called from
-      <c><![CDATA[open_port]]></c>. The data will be passed to <c><![CDATA[control]]></c>
-      and <c><![CDATA[stop]]></c>.</p>
+
+    <p>Here some initialization is done, <c><![CDATA[start]]></c> is called from
+      <c><![CDATA[open_port]]></c>. The data will be passed to
+      <c><![CDATA[control]]></c> and <c><![CDATA[stop]]></c>.</p>
+
     <code type="none"><![CDATA[
 /* DRIVER INTERFACE */
 static ErlDrvData start(ErlDrvPort port, char *command)
@@ -195,8 +215,10 @@ static ErlDrvData start(ErlDrvPort port, char *command)
     return (ErlDrvData)data;
 }
     ]]></code>
+
     <p>We call disconnect to log out from the database.
       (This should have been done from Erlang, but just in case.)</p>
+
     <code type="none"><![CDATA[
 static int do_disconnect(our_data_t* data, ei_x_buff* x);
 
@@ -208,22 +230,27 @@ static void stop(ErlDrvData drv_data)
     driver_free(data);
 }
     ]]></code>
+
     <p>We use the binary format only to return data to the emulator;
-      input data is a string paramater for <c><![CDATA[connect]]></c> and
+      input data is a string parameter for <c><![CDATA[connect]]></c> and
       <c><![CDATA[select]]></c>. The returned data consists of Erlang terms.</p>
-    <p>The functions <c><![CDATA[get_s]]></c> and <c><![CDATA[ei_x_to_new_binary]]></c> are
-      utilities that are used to make the code shorter. <c><![CDATA[get_s]]></c>
-      duplicates the string and zero-terminates it, since the
+
+    <p>The functions <c><![CDATA[get_s]]></c> and
+      <c><![CDATA[ei_x_to_new_binary]]></c> are utilities that are used to
+      make the code shorter. <c><![CDATA[get_s]]></c>
+      duplicates the string and zero-terminates it, as the
       postgres client library wants that. <c><![CDATA[ei_x_to_new_binary]]></c>
-      takes an <c><![CDATA[ei_x_buff]]></c> buffer and allocates a binary and
-      copies the data there. This binary is returned in <c><![CDATA[*rbuf]]></c>.
-      (Note that this binary is freed by the emulator, not by us.)</p>
+      takes an <c><![CDATA[ei_x_buff]]></c> buffer, allocates a binary, and
+      copies the data there. This binary is returned in
+      <c><![CDATA[*rbuf]]></c>.
+      (Notice that this binary is freed by the emulator, not by us.)</p>
+
     <code type="none"><![CDATA[
 static char* get_s(const char* buf, int len);
 static int do_connect(const char *s, our_data_t* data, ei_x_buff* x);
 static int do_select(const char* s, our_data_t* data, ei_x_buff* x);
 
-/* Since we are operating in binary mode, the return value from control
+/* As we are operating in binary mode, the return value from control
  * is irrelevant, as long as it is not negative.
  */
 static int control(ErlDrvData drv_data, unsigned int command, char *buf, 
@@ -246,10 +273,12 @@ static int control(ErlDrvData drv_data, unsigned int command, char *buf,
     return r;
 }
     ]]></code>
-    <p><c><![CDATA[do_connect]]></c> is where we log in to the database. If the connection
-      was successful we store the connection handle in our driver
-      data, and return ok. Otherwise, we return the error message
-      from postgres, and store <c><![CDATA[NULL]]></c> in the driver data.</p>
+
+    <p><c><![CDATA[do_connect]]></c> is where we log on to the database. If the
+      connection was successful, we store the connection handle in the driver
+      data, and return OK. Otherwise, we return the error message
+      from postgres and store <c><![CDATA[NULL]]></c> in the driver data.</p>
+
     <code type="none"><![CDATA[
 static int do_connect(const char *s, our_data_t* data, ei_x_buff* x)
 {
@@ -265,10 +294,13 @@ static int do_connect(const char *s, our_data_t* data, ei_x_buff* x)
     return 0;
 }
     ]]></code>
-    <p>If we are connected (if the connection handle is not <c><![CDATA[NULL]]></c>),
+
+    <p>If we are connected (and if the connection handle is not
+      <c><![CDATA[NULL]]></c>),
       we log out from the database. We need to check if we should
-      encode an ok, since we might get here from the <c><![CDATA[stop]]></c>
-      function, which doesn't return data to the emulator.</p>
+      encode an OK, as we can get here from function <c><![CDATA[stop]]></c>,
+      which does not return data to the emulator:</p>
+
     <code type="none"><![CDATA[
 static int do_disconnect(our_data_t* data, ei_x_buff* x)
 {
@@ -281,9 +313,11 @@ static int do_disconnect(our_data_t* data, ei_x_buff* x)
     return 0;
 }
     ]]></code>
-    <p>We execute a query and encode the result. Encoding is done
-      in another C module, <c><![CDATA[pg_encode.c]]></c> which is also provided
+
+    <p>We execute a query and encode the result. Encoding is done in
+      another C module, <c><![CDATA[pg_encode.c]]></c>, which is also provided
       as sample code.</p>
+
     <code type="none"><![CDATA[
 static int do_select(const char* s, our_data_t* data, ei_x_buff* x)
 {
@@ -293,12 +327,14 @@ static int do_select(const char* s, our_data_t* data, ei_x_buff* x)
     return 0;
 }
     ]]></code>
-    <p>Here we simply check the result from postgres, and
-      if it's data we encode it as lists of lists with
+
+    <p>Here we check the result from postgres.
+      If it is data, we encode it as lists of lists with
       column data. Everything from postgres is C strings,
-      so we just use <c><![CDATA[ei_x_encode_string]]></c> to send
+      so we only use <c><![CDATA[ei_x_encode_string]]></c> to send
       the result as strings to Erlang. (The head of the list
       contains the column names.)</p>
+
     <code type="none"><![CDATA[
 void encode_result(ei_x_buff* x, PGresult* res, PGconn* conn)
 {
@@ -338,33 +374,36 @@ void encode_result(ei_x_buff* x, PGresult* res, PGconn* conn)
   </section>
 
   <section>
-    <title>Compiling and linking the sample driver</title>
-    <p>The driver should be compiled and linked to a shared
-      library (DLL on windows). With gcc this is done
-      with the link flags <c><![CDATA[-shared]]></c> and <c><![CDATA[-fpic]]></c>.
-      Since we use the <c><![CDATA[ei]]></c> library we should include
+    <title>Compiling and Linking the Sample Driver</title>
+    <p>The driver is to be compiled and linked to a shared
+      library (DLL on Windows). With gcc, this is done with
+      link flags <c><![CDATA[-shared]]></c> and <c><![CDATA[-fpic]]></c>.
+      As we use the <c><![CDATA[ei]]></c> library, we should include
       it too. There are several versions of <c><![CDATA[ei]]></c>, compiled
       for debug or non-debug and multi-threaded or single-threaded.
-      In the makefile for the samples the <c><![CDATA[obj]]></c> directory
+      In the makefile for the samples, the <c><![CDATA[obj]]></c> directory
       is used for the <c><![CDATA[ei]]></c> library, meaning that we use
       the non-debug, single-threaded version.</p>
   </section>
 
   <section>
-    <title>Calling a driver as a port in Erlang</title>
+    <title>Calling a Driver as a Port in Erlang</title>
     <p>Before a driver can be called from Erlang, it must be
       loaded and opened. Loading is done using the <c><![CDATA[erl_ddll]]></c>
       module (the <c><![CDATA[erl_ddll]]></c> driver that loads dynamic
-      driver, is actually a driver itself). If loading is ok
+      driver is actually a driver itself). If loading is OK,
       the port can be opened with <c><![CDATA[open_port/2]]></c>. The port
       name must match the name of the shared library and
       the name in the driver entry structure.</p>
+
     <p>When the port has been opened, the driver can be called. In
-      the <c><![CDATA[pg_sync]]></c> example, we don't have any data from
+      the <c><![CDATA[pg_sync]]></c> example, we do not have any data from
       the port, only the return value from the
       <c><![CDATA[port_control]]></c>.</p>
+
     <p>The following code is the Erlang part of the synchronous
-      postgres driver, <c><![CDATA[pg_sync.erl]]></c>.</p>
+      postgres driver, <c><![CDATA[pg_sync.erl]]></c>:</p>
+
     <code type="none"><![CDATA[
 -module(pg_sync).
 
@@ -394,20 +433,35 @@ disconnect(Port) ->
 select(Port, Query) ->
     binary_to_term(port_control(Port, ?DRV_SELECT, Query)).
     ]]></code>
-    <p>The API is simple: <c><![CDATA[connect/1]]></c> loads the driver, opens it
-      and logs on to the database, returning the Erlang port
-      if successful, <c><![CDATA[select/2]]></c> sends a query to the driver,
-      and returns the result, <c><![CDATA[disconnect/1]]></c> closes the
-      database connection and the driver. (It does not unload it,
-      however.) The connection string should be a connection
-      string for postgres.</p>
-    <p>The driver is loaded with <c><![CDATA[erl_ddll:load_driver/2]]></c>,
-      and if this is successful, or if it's already loaded,
+
+    <p>The API is simple:</p>
+
+    <list type="bulleted">
+      <item>
+        <p><c><![CDATA[connect/1]]></c> loads the driver, opens it,
+          and logs on to the database, returning the Erlang port
+          if successful.</p>
+      </item>
+      <item>
+        <p><c><![CDATA[select/2]]></c> sends a query to the driver
+          and returns the result.</p>
+      </item>
+      <item>
+        <p><c><![CDATA[disconnect/1]]></c> closes the database
+          connection and the driver. (However, it does not unload it.)</p>
+      </item>
+    </list>
+
+    <p>The connection string is to be a connection string for postgres.</p>
+
+    <p>The driver is loaded with <c><![CDATA[erl_ddll:load_driver/2]]></c>.
+      If this is successful, or if it is already loaded,
       it is opened. This will call the <c><![CDATA[start]]></c> function
       in the driver.</p>
+
     <p>We use the <c><![CDATA[port_control/3]]></c> function for all
-      calls into the driver, the result from the driver is
-      returned immediately, and converted to terms by calling
+      calls into the driver. The result from the driver is
+      returned immediately and converted to terms by calling
       <c><![CDATA[binary_to_term/1]]></c>. (We trust that the terms returned
       from the driver are well-formed, otherwise the
       <c><![CDATA[binary_to_term]]></c> calls could be contained in a
@@ -415,16 +469,18 @@ select(Port, Query) ->
   </section>
 
   <section>
-    <title>Sample asynchronous driver</title>
-    <p>Sometimes database queries can take long time to
+    <title>Sample Asynchronous Driver</title>
+    <p>Sometimes database queries can take a long time to
       complete, in our <c><![CDATA[pg_sync]]></c> driver, the emulator
       halts while the driver is doing its job. This is
-      often not acceptable, since no other Erlang process
+      often not acceptable, as no other Erlang process
       gets a chance to do anything. To improve on our
-      postgres driver, we reimplement it using the asynchronous
+      postgres driver, we re-implement it using the asynchronous
       calls in LibPQ.</p>
-    <p>The asynchronous version of the driver is in the
-      sample files <c><![CDATA[pg_async.c]]></c> and <c><![CDATA[pg_asyng.erl]]></c>.</p>
+
+    <p>The asynchronous version of the driver is in the sample files
+      <c><![CDATA[pg_async.c]]></c> and <c><![CDATA[pg_asyng.erl]]></c>.</p>
+
     <code type="none"><![CDATA[
 /* Driver interface declarations */
 static ErlDrvData start(ErlDrvPort port, char *command);
@@ -459,22 +515,26 @@ typedef struct our_data_t {
     int connecting;
 } our_data_t;
     ]]></code>
-    <p>Here some things have changed from <c><![CDATA[pg_sync.c]]></c>: we use the
-      entry <c><![CDATA[ready_io]]></c> for <c><![CDATA[ready_input]]></c> and
-      <c><![CDATA[ready_output]]></c> which will be called from the emulator only
-      when there is input to be read from the socket. (Actually, the
+
+    <p>Some things have changed from <c><![CDATA[pg_sync.c]]></c>: we use
+      the entry <c><![CDATA[ready_io]]></c> for <c><![CDATA[ready_input]]></c>
+      and <c><![CDATA[ready_output]]></c>, which is called from the emulator
+      only when there is input to be read from the socket. (Actually, the
       socket is used in a <c><![CDATA[select]]></c> function inside
-      the emulator, and when the socket is signalled,
-      indicating there is data to read, the <c><![CDATA[ready_input]]></c> entry
-      is called. More on this below.)</p>
+      the emulator, and when the socket is signaled,
+      indicating there is data to read, the <c><![CDATA[ready_input]]></c>
+      entry is called. More about this below.)</p>
+
     <p>Our driver data is also extended, we keep track of the
       socket used for communication with postgres, and also
       the port, which is needed when we send data to the port with
-      <c><![CDATA[driver_output]]></c>. We have a flag <c><![CDATA[connecting]]></c> to tell
+      <c><![CDATA[driver_output]]></c>. We have a flag
+      <c><![CDATA[connecting]]></c> to tell
       whether the driver is waiting for a connection or waiting
-      for the result of a query. (This is needed since the entry
-      <c><![CDATA[ready_io]]></c> will be called both when connecting and
+      for the result of a query. (This is needed, as the entry
+      <c><![CDATA[ready_io]]></c> is called both when connecting and
       when there is a query result.)</p>
+
     <code type="none"><![CDATA[
 static int do_connect(const char *s, our_data_t* data)
 {
@@ -498,16 +558,20 @@ static int do_connect(const char *s, our_data_t* data)
     return 0;
 }
     ]]></code>
-    <p>The <c><![CDATA[connect]]></c> function looks a bit different too. We connect
-      using the asynchronous <c><![CDATA[PQconnectStart]]></c> function. After the
-      connection is started, we retrieve the socket for the connection
+
+    <p>The <c><![CDATA[connect]]></c> function looks a bit different too. We
+      connect using the asynchronous <c><![CDATA[PQconnectStart]]></c> function.
+      After the connection is started, we retrieve the socket for the connection
       with <c><![CDATA[PQsocket]]></c>. This socket is used with the
       <c><![CDATA[driver_select]]></c> function to wait for connection. When
-      the socket is ready for input or for output, the <c><![CDATA[ready_io]]></c>
-      function will be called.</p>
-    <p>Note that we only return data (with <c><![CDATA[driver_output]]></c>) if there
+      the socket is ready for input or for output, the
+      <c><![CDATA[ready_io]]></c> function is called.</p>
+
+    <p>Notice that we only return data (with <c><![CDATA[driver_output]]></c>)
+      if there
       is an error here, otherwise we wait for the connection to be completed,
-      in which case our <c><![CDATA[ready_io]]></c> function will be called.</p>
+      in which case our <c><![CDATA[ready_io]]></c> function is called.</p>
+
     <code type="none"><![CDATA[
 static int do_select(const char* s, our_data_t* data)
 {
@@ -525,9 +589,11 @@ static int do_select(const char* s, our_data_t* data)
     return 0;
 }
     ]]></code>
+
     <p>The <c><![CDATA[do_select]]></c> function initiates a select, and returns
-      if there is no immediate error. The actual result will be returned
+      if there is no immediate error. The result is returned
       when <c><![CDATA[ready_io]]></c> is called.</p>
+
     <code type="none"><![CDATA[
 static void ready_io(ErlDrvData drv_data, ErlDrvEvent event)
 {
@@ -566,26 +632,31 @@ static void ready_io(ErlDrvData drv_data, ErlDrvEvent event)
     ei_x_free(&x);
 }
     ]]></code>
-    <p>The <c><![CDATA[ready_io]]></c> function will be called when the socket
+
+    <p>The <c><![CDATA[ready_io]]></c> function is called when the socket
       we got from postgres is ready for input or output. Here
       we first check if we are connecting to the database. In that
-      case we check connection status and return ok if the 
-      connection is successful, or error if it's not. If the
-      connection is not yet established, we simply return; <c><![CDATA[ready_io]]></c>
-      will be called again.</p>
+      case, we check connection status and return OK if the 
+      connection is successful, or error if it is not. If the
+      connection is not yet established, we simply return;
+      <c><![CDATA[ready_io]]></c> is called again.</p>
+
     <p>If we have a result from a connect, indicated by having data in
       the <c><![CDATA[x]]></c> buffer, we no longer need to select on
       output (<c><![CDATA[ready_output]]></c>), so we remove this by calling
       <c><![CDATA[driver_select]]></c>.</p>
-    <p>If we're not connecting, we're waiting for results from a
+
+    <p>If we are not connecting, we wait for results from a
       <c><![CDATA[PQsendQuery]]></c>, so we get the result and return it. The
       encoding is done with the same functions as in the earlier
       example.</p>
-    <p>We should add error handling here, for instance checking
-      that the socket is still open, but this is just a simple
-      example.</p>
+
+    <p>Error handling is to be added here, for example, checking
+      that the socket is still open, but this is only a simple example.</p>
+
     <p>The Erlang part of the asynchronous driver consists of the
       sample file <c><![CDATA[pg_async.erl]]></c>.</p>
+
     <code type="none"><![CDATA[
 -module(pg_async).
 
@@ -626,45 +697,50 @@ return_port_data(Port) ->
             binary_to_term(Data)
     end.
     ]]></code>
-    <p>The Erlang code is slightly different, this is because we
-      don't return the result synchronously from <c><![CDATA[port_control]]></c>,
+
+    <p>The Erlang code is slightly different, as we do not
+      return the result synchronously from <c><![CDATA[port_control]]></c>,
       instead we get it from <c><![CDATA[driver_output]]></c> as data in the
       message queue. The function <c><![CDATA[return_port_data]]></c> above
-      receives data from the port. Since the data is in
+      receives data from the port. As the data is in
       binary format, we use <c><![CDATA[binary_to_term/1]]></c> to convert
-      it to an Erlang term. Note that the driver is opened in
-      binary mode (<c><![CDATA[open_port/2]]></c> is called with the option
+      it to an Erlang term. Notice that the driver is opened in
+      binary mode (<c><![CDATA[open_port/2]]></c> is called with option
       <c><![CDATA[[binary]]]></c>). This means that data sent from the driver
-      to the emulator is sent as binaries. Without the <c><![CDATA[binary]]></c>
-      option, they would have been lists of integers.</p>
+      to the emulator is sent as binaries. Without option
+      <c><![CDATA[binary]]></c>, they would have been lists of integers.</p>
   </section>
 
   <section>
-    <title>An asynchronous driver using driver_async</title>
-    <p>As a final example we demonstrate the use of <c><![CDATA[driver_async]]></c>.
+    <title>An Asynchronous Driver Using driver_async</title>
+    <p>As a final example we demonstrate the use of
+      <c><![CDATA[driver_async]]></c>.
       We also use the driver term interface. The driver is written
-      in C++. This enables us to use an algorithm from STL. We will
-      use the <c><![CDATA[next_permutation]]></c> algorithm to get the next permutation
-      of a list of integers. For large lists (more than 100000
-      elements), this will take some time, so we will perform this
+      in C++. This enables us to use an algorithm from STL. We use
+      the <c><![CDATA[next_permutation]]></c> algorithm to get the next
+      permutation of a list of integers. For large lists (&gt; 100,000
+      elements), this takes some time, so we perform this
       as an asynchronous task.</p>
-    <p>The asynchronous API for drivers is quite complicated. First
-      of all, the work must be prepared. In our example we do this
-      in <c><![CDATA[output]]></c>. We could have used <c><![CDATA[control]]></c> just as well,
-      but we want some variation in our examples. In our driver, we allocate
-      a structure that contains anything that's needed for the asynchronous task
-      to do the work. This is done in the main emulator thread.
+
+    <p>The asynchronous API for drivers is complicated. First,
+      the work must be prepared. In the example, this is done in
+      <c><![CDATA[output]]></c>. We could have used <c><![CDATA[control]]></c>,
+      but we want some variation in the examples. In our driver, we allocate
+      a structure that contains anything that is needed for the asynchronous
+      task to do the work. This is done in the main emulator thread.
       Then the asynchronous function is called from a driver thread,
-      separate from the main emulator thread. Note that the driver-functions
-      are not reentrant, so they shouldn't be used.
+      separate from the main emulator thread. Notice that the driver functions
+      are not re-entrant, so they are not to be used.
       Finally, after the function is completed, the driver callback
       <c><![CDATA[ready_async]]></c> is called from the main emulator thread,
-      this is where we return the result to Erlang. (We can't
-      return the result from within the asynchronous function, since
-      we can't call the driver-functions.)</p>
-    <p>The code below is from the sample file <c><![CDATA[next_perm.cc]]></c>.</p>
-    <p>The driver entry looks like before, but also contains the
-      call-back <c><![CDATA[ready_async]]></c>.</p>
+      this is where we return the result to Erlang. (We cannot
+      return the result from within the asynchronous function, as
+      we cannot call the driver functions.)</p>
+
+    <p>The following code is from the sample file
+      <c><![CDATA[next_perm.cc]]></c>. The driver entry looks like before,
+      but also contains the callback <c><![CDATA[ready_async]]></c>.</p>
+
     <code type="none"><![CDATA[
 static ErlDrvEntry next_perm_driver_entry = {
     NULL,                        /* init */
@@ -685,17 +761,21 @@ static ErlDrvEntry next_perm_driver_entry = {
     NULL                         /* event */
 };
     ]]></code>
-    <p>The <c><![CDATA[output]]></c> function allocates the work-area of the
-      asynchronous function. Since we use C++, we use a struct,
-      and stuff the data in it. We have to copy the original data,
+
+    <p>The <c><![CDATA[output]]></c> function allocates the work area of the
+      asynchronous function. As we use C++, we use a struct,
+      and stuff the data in it. We must copy the original data,
       it is not valid after we have returned from the <c><![CDATA[output]]></c>
-      function, and the <c><![CDATA[do_perm]]></c> function will be called later,
-      and from another thread. We return no data here, instead it will
-      be sent later from the <c><![CDATA[ready_async]]></c> call-back.</p>
-    <p>The <c><![CDATA[async_data]]></c> will be passed to the <c><![CDATA[do_perm]]></c> function.
-      We do not use a <c><![CDATA[async_free]]></c> function (the last argument to
-      <c><![CDATA[driver_async]]></c>), it's only used if the task is cancelled
+      function, and the <c><![CDATA[do_perm]]></c> function is called
+      later, and from another thread. We return no data here, instead it
+      is sent later from the <c><![CDATA[ready_async]]></c> callback.</p>
+
+    <p>The <c><![CDATA[async_data]]></c> is passed to the
+      <c><![CDATA[do_perm]]></c> function. We do not use a
+      <c><![CDATA[async_free]]></c> function (the last argument to
+      <c><![CDATA[driver_async]]></c>), it is only used if the task is cancelled
       programmatically.</p>
+
     <code type="none"><![CDATA[
 struct our_async_data {
     bool prev;
@@ -720,8 +800,10 @@ static void output(ErlDrvData drv_data, char *buf, int len)
     driver_async(port, NULL, do_perm, async_data, do_free);
 }
     ]]></code>
-    <p>In the <c><![CDATA[do_perm]]></c> we simply do the work, operating
+
+    <p>In the <c><![CDATA[do_perm]]></c> we do the work, operating
       on the structure that was allocated in <c><![CDATA[output]]></c>.</p>
+
     <code type="none"><![CDATA[
 static void do_perm(void* async_data)
 {
@@ -732,13 +814,17 @@ static void do_perm(void* async_data)
         next_permutation(d->data.begin(), d->data.end());
 }
     ]]></code>
-    <p>In the <c><![CDATA[ready_async]]></c> function, the output is sent back to the
+
+    <p>In the <c><![CDATA[ready_async]]></c> function the output is sent back
+      to the
       emulator. We use the driver term format instead of <c><![CDATA[ei]]></c>.
-      This is the only way to send Erlang terms directly to a driver,
-      without having the Erlang code to call <c><![CDATA[binary_to_term/1]]></c>. In
-      our simple example this works well, and we don't need to use
+      This is the only way to send Erlang terms directly to a driver, without
+      having the Erlang code to call <c><![CDATA[binary_to_term/1]]></c>. In
+      the simple example this works well, and we do not need to use
       <c><![CDATA[ei]]></c> to handle the binary term format.</p>
-    <p>When the data is returned we deallocate our data.</p>
+
+    <p>When the data is returned, we deallocate our data.</p>
+
     <code type="none"><![CDATA[
 static void ready_async(ErlDrvData drv_data, ErlDrvThreadData async_data)
 {
@@ -759,12 +845,15 @@ static void ready_async(ErlDrvData drv_data, ErlDrvThreadData async_data)
     delete d;
 }
     ]]></code>
-    <p>This driver is called like the others from Erlang, however, since
+
+    <p>This driver is called like the others from Erlang. However, as
       we use <c><![CDATA[driver_output_term]]></c>, there is no need to call
-      binary_to_term. The Erlang code is in the sample file
+      <c>binary_to_term</c>. The Erlang code is in the sample file
       <c><![CDATA[next_perm.erl]]></c>.</p>
+
     <p>The input is changed into a list of integers and sent to
       the driver.</p>
+
     <code type="none"><![CDATA[
 -module(next_perm).
 
diff --git a/erts/doc/src/driver_entry.xml b/erts/doc/src/driver_entry.xml
index ae7f264d0c..dea003f091 100644
--- a/erts/doc/src/driver_entry.xml
+++ b/erts/doc/src/driver_entry.xml
@@ -33,55 +33,64 @@
     <file>driver_entry.xml</file>
   </header>
   <lib>driver_entry</lib>
-  <libsummary>The driver-entry structure used by erlang drivers.</libsummary>
+  <libsummary>The driver-entry structure used by Erlang drivers.</libsummary>
   <description>
     <marker id="WARNING"/>
-      <warning><p><em>Use this functionality with extreme care!</em></p>
+    <warning>
+      <p><em>Use this functionality with extreme care.</em></p>
       <p>A driver callback is executed as a direct extension of the
-      native code of the VM. Execution is not made in a safe environment.
-      The VM can <em>not</em> provide the same services as provided when
-      executing Erlang code, such as preemptive scheduling or memory
-      protection. If the driver callback function doesn't behave well,
-      the whole VM will misbehave.</p>
-      <list>
-	<item><p>A driver callback that crash will crash the whole VM.</p></item>
-	<item><p>An erroneously implemented driver callback might cause
-	a VM internal state inconsistency which may cause a crash of the VM,
-	or miscellaneous misbehaviors of the VM at any point after the call
-	to the driver callback.</p></item>
-	<item><p>A driver callback that do
-	<seealso marker="erl_driver#lengthy_work">lengthy work</seealso>
-	before returning will degrade responsiveness of the VM,
-	and may cause miscellaneous strange behaviors. Such strange behaviors
-	include, but are not limited to, extreme memory usage, and bad load
-	balancing between schedulers. Strange behaviors that might occur due
-	to lengthy work may also vary between OTP releases.</p></item>
+        native code of the VM. Execution is not made in a safe environment.
+        The VM <em>cannot</em> provide the same services as provided when
+        executing Erlang code, such as pre-emptive scheduling or memory
+        protection. If the driver callback function does not behave well,
+        the whole VM will misbehave.</p>
+      <list type="bulleted">
+        <item>
+          <p>A driver callback that crash will crash the whole VM.</p>
+        </item>
+        <item>
+          <p>An erroneously implemented driver callback can cause a VM
+            internal state inconsistency, which can cause a crash of the VM,
+            or miscellaneous misbehaviors of the VM at any point after the
+            call to the driver callback.</p>
+        </item>
+        <item>
+          <p>A driver callback doing
+            <seealso marker="erl_driver#lengthy_work">lengthy work</seealso>
+            before returning degrades responsiveness of the VM, and can cause
+            miscellaneous strange behaviors. Such strange behaviors
+            include, but are not limited to, extreme memory usage, and bad
+            load balancing between schedulers. Strange behaviors that can
+            occur because of lengthy work can also vary between Erlang/OTP
+            releases.</p>
+        </item>
       </list>
-      </warning>
-    <p>
-      As of erts version 5.9 (OTP release R15B) the driver interface
+    </warning>
+
+    <p>As from <c>ERTS</c> 5.9 (Erlang/OTP R15B) the driver interface
       has been changed with larger types for the callbacks
-      <seealso marker="#output">output</seealso>,
-      <seealso marker="#control">control</seealso> and
-      <seealso marker="#call">call</seealso>.
+      <seealso marker="#output"><c>output</c></seealso>,
+      <seealso marker="#control"><c>control</c></seealso>, and
+      <seealso marker="#call"><c>call</c></seealso>.
       See driver <seealso marker="erl_driver#version_management">
       version management</seealso> in
-      <seealso marker="erl_driver">erl_driver</seealso>.
-    </p>
+      <seealso marker="erl_driver"><c>erl_driver</c></seealso>.</p>
+
     <note>
       <p>Old drivers (compiled with an <c>erl_driver.h</c> from an
-      earlier erts version than 5.9) have to be updated and have
-      to use the extended interface (with
-      <seealso marker="erl_driver#version_management">version management
-      </seealso>).</p>
+        <c>ERTS</c> version earlier than 5.9) must be updated and have
+        to use the extended interface (with
+        <seealso marker="erl_driver#version_management">version management
+        </seealso>).</p>
     </note>
-    <p>The <c>driver_entry</c> structure is a C struct that all erlang
-      drivers define. It contains entry points for the erlang driver
-      that are called by the erlang emulator when erlang code accesses
+
+    <p>The <c>driver_entry</c> structure is a C struct that all Erlang
+      drivers define. It contains entry points for the Erlang driver,
+      which are called by the Erlang emulator when Erlang code accesses
       the driver.</p>
-    <p>      
-      <marker id="emulator"></marker>
-      The <seealso marker="erl_driver">erl_driver</seealso> driver
+
+    <p><marker id="emulator"></marker>
+      The <seealso marker="erl_driver"><c>erl_driver</c></seealso> driver
       API functions need a port handle
       that identifies the driver instance (and the port in the
       emulator). This is only passed to the <c>start</c> function, but
@@ -90,416 +99,466 @@
       common practice is to have the <c>start</c> function allocate
       some application-defined structure and stash the <c>port</c>
       handle in it, to use it later with the driver API functions.</p>
-    <p>The driver call-back functions are called synchronously from the
-      erlang emulator. If they take too long before completing, they
-      can cause timeouts in the emulator. Use the queue or
-      asynchronous calls if necessary, since the emulator must be
+
+    <p>The driver callback functions are called synchronously from the
+      Erlang emulator. If they take too long before completing, they
+      can cause time-outs in the emulator. Use the queue or
+      asynchronous calls if necessary, as the emulator must be
       responsive.</p>
-    <p>The driver structure contains the name of the driver and some
-      15 function pointers. These pointers are called at different
+
+    <p>The driver structure contains the driver name and some
+      15 function pointers, which are called at different
       times by the emulator.</p>
+
     <p>The only exported function from the driver is
       <c>driver_init</c>. This function returns the <c>driver_entry</c>
       structure that points to the other functions in the driver. The
-      <c>driver_init</c> function is declared with a macro
-      <c>DRIVER_INIT(drivername)</c>. (This is because different OS's
-      have different names for it.)</p>
-    <p>When writing a driver in C++, the driver entry should be of
-      <c>"C"</c> linkage. One way to do this is to put this line
-      somewhere before the driver entry:
-      <c>extern "C" DRIVER_INIT(drivername);</c>.</p>
+      <c>driver_init</c> function is declared with a macro,
+      <c>DRIVER_INIT(drivername)</c>. (This is because different
+      operating systems have different names for it.)</p>
+
+    <p>When writing a driver in C++, the driver entry is to be of
+      <c>"C"</c> linkage. One way to do this is to put the
+      following line somewhere before the driver entry:</p>
+
+    <pre>
+extern "C" DRIVER_INIT(drivername);</pre>
+
     <p>When the driver has passed the <c>driver_entry</c> over to
       the emulator, the driver is <em>not</em> allowed to modify the
       <c>driver_entry</c>.</p>
-    <p>If compiling a driver for static inclusion via --enable-static-drivers you
-    have to define STATIC_ERLANG_DRIVER before the DRIVER_INIT declaration.</p>
+
+    <p>If compiling a driver for static inclusion through
+      <c>--enable-static-drivers</c>, you must define
+      <c>STATIC_ERLANG_DRIVER</c> before the <c>DRIVER_INIT</c> declaration.</p>
+
     <note>
-      <p>Do <em>not</em> declare the <c>driver_entry</c> <c>const</c>. This since the emulator needs to
-        modify the <c>handle</c>, and the <c>handle2</c>
-        fields. A statically allocated, and <c>const</c>
-        declared <c>driver_entry</c> may be located in
-        read only memory which will cause the emulator
-        to crash.</p>
+      <p>Do <em>not</em> declare the <c>driver_entry</c> <c>const</c>.
+        This because the emulator must
+        modify the <c>handle</c> and the <c>handle2</c>
+        fields. A statically allocated, and <c>const</c>-declared
+        <c>driver_entry</c> can be located in
+        read-only memory, which causes the emulator to crash.</p>
     </note>
   </description>
 
   <section>
-    <title>DATA TYPES</title>
-    <taglist>
-    <tag><em>ErlDrvEntry</em></tag>
-    <item>
-    <p/>
+    <title>Data Types</title>
+    <p><c>ErlDrvEntry</c></p>
     <code type="none">
 typedef struct erl_drv_entry {
-    int (*init)(void);          /* called at system start up for statically
+    int (*init)(void);          /* Called at system startup for statically
                                    linked drivers, and after loading for
-                                   dynamically loaded drivers */ 
-
+                                   dynamically loaded drivers */
 #ifndef ERL_SYS_DRV
     ErlDrvData (*start)(ErlDrvPort port, char *command);
-                                /* called when open_port/2 is invoked.
-                                   return value -1 means failure. */
+                                /* Called when open_port/2 is invoked,
+                                   return value -1 means failure */
 #else
     ErlDrvData (*start)(ErlDrvPort port, char *command, SysDriverOpts* opts);
-                                /* special options, only for system driver */
+                                /* Special options, only for system driver */
 #endif
     void (*stop)(ErlDrvData drv_data);
-                                /* called when port is closed, and when the
-                                   emulator is halted. */
+                                /* Called when port is closed, and when the
+                                   emulator is halted */
     void (*output)(ErlDrvData drv_data, char *buf, ErlDrvSizeT len);
-                                /* called when we have output from erlang to 
+                                /* Called when we have output from Erlang to
                                    the port */
     void (*ready_input)(ErlDrvData drv_data, ErlDrvEvent event); 
-                                /* called when we have input from one of 
+                                /* Called when we have input from one of
                                    the driver's handles */
     void (*ready_output)(ErlDrvData drv_data, ErlDrvEvent event);  
-                                /* called when output is possible to one of 
+                                /* Called when output is possible to one of
                                    the driver's handles */
-    char *driver_name;          /* name supplied as command 
-                                   in open_port XXX ? */
-    void (*finish)(void);       /* called before unloading the driver -
-                                   DYNAMIC DRIVERS ONLY */
-    void *handle;               /* Reserved -- Used by emulator internally */
+    char *driver_name;          /* Name supplied as command in
+                                   erlang:open_port/2 */
+    void (*finish)(void);       /* Called before unloading the driver -
+                                   dynamic drivers only */
+    void *handle;               /* Reserved, used by emulator internally */
     ErlDrvSSizeT (*control)(ErlDrvData drv_data, unsigned int command,
                             char *buf, ErlDrvSizeT len,
 			    char **rbuf, ErlDrvSizeT rlen);
-                                /* "ioctl" for drivers - invoked by 
+                                /* "ioctl" for drivers - invoked by
                                    port_control/3 */
-    void (*timeout)(ErlDrvData drv_data);        /* Handling of timeout in driver */
+    void (*timeout)(ErlDrvData drv_data);
+                                /* Handling of time-out in driver */
     void (*outputv)(ErlDrvData drv_data, ErlIOVec *ev);
-                                /* called when we have output from erlang
+                                /* Called when we have output from Erlang
                                    to the port */
     void (*ready_async)(ErlDrvData drv_data, ErlDrvThreadData thread_data);
     void (*flush)(ErlDrvData drv_data);
-                                /* called when the port is about to be 
-                                   closed, and there is data in the 
-                                   driver queue that needs to be flushed
+                                /* Called when the port is about to be
+                                   closed, and there is data in the
+                                   driver queue that must be flushed
                                    before 'stop' can be called */
     ErlDrvSSizeT (*call)(ErlDrvData drv_data, unsigned int command,
                          char *buf, ErlDrvSizeT len,
 			 char **rbuf, ErlDrvSizeT rlen, unsigned int *flags);
                                 /* Works mostly like 'control', a synchronous
-                                   call into the driver. */
+                                   call into the driver */
     void (*event)(ErlDrvData drv_data, ErlDrvEvent event,
                   ErlDrvEventData event_data);
-                                /* Called when an event selected by 
+                                /* Called when an event selected by
                                    driver_event() has occurred */
     int extended_marker;        /* ERL_DRV_EXTENDED_MARKER */
     int major_version;          /* ERL_DRV_EXTENDED_MAJOR_VERSION */
     int minor_version;          /* ERL_DRV_EXTENDED_MINOR_VERSION */
     int driver_flags;           /* ERL_DRV_FLAGs */
-    void *handle2;              /* Reserved -- Used by emulator internally */
+    void *handle2;              /* Reserved, used by emulator internally */
     void (*process_exit)(ErlDrvData drv_data, ErlDrvMonitor *monitor);
                                 /* Called when a process monitor fires */
     void (*stop_select)(ErlDrvEvent event, void* reserved);
                                 /* Called to close an event object */
- } ErlDrvEntry;
-    </code>
-    <p/>
+ } ErlDrvEntry;</code>
     <taglist>
-      <tag><marker id="init"/>int (*init)(void)</tag>
-      <item>        
-        <p>This is called directly after the driver has been loaded by
-          <c>erl_ddll:load_driver/2</c>. (Actually when the driver is
-          added to the driver list.) The driver should return 0, or if
-          the driver can't initialize, -1.</p>
+      <tag><marker id="init"/><c>int (*init)(void)</c></tag>
+      <item>       
+        <p>Called directly after the driver has been loaded by
+          <seealso marker="kernel:erl_ddll#load_driver/2">
+          <c>erl_ddll:load_driver/2</c></seealso> (actually when the driver is
+          added to the driver list). The driver is to return <c>0</c>, or, if
+          the driver cannot initialize, <c>-1</c>.</p>
       </item>
-      <tag><marker id="start"/>ErlDrvData (*start)(ErlDrvPort port, char* command)</tag>
+      <tag><marker id="start"/>
+        <c>ErlDrvData (*start)(ErlDrvPort port, char* command)</c></tag>
       <item>
-        <p>This is called when the driver is instantiated, when
-          <c>open_port/2</c> is called. The driver should return a
-          number &gt;= 0 or a pointer, or if the driver can't be started,
-          one of three error codes should be returned:</p>
-        <p>ERL_DRV_ERROR_GENERAL - general error, no error code</p>
-        <p>ERL_DRV_ERROR_ERRNO - error with error code in <c>errno</c></p>
-        <p>ERL_DRV_ERROR_BADARG - error, badarg</p>
-        <p>If an error code is returned, the port isn't started.</p>
+        <p>Called when the driver is instantiated, when
+          <seealso marker="erlang#open_port/2">
+          <c>erlang:open_port/2</c></seealso> is called.
+          The driver is to return a number &gt;= 0 or a pointer, or, if the
+          driver cannot be started, one of three error codes:</p>
+        <taglist>
+          <tag><c>ERL_DRV_ERROR_GENERAL</c></tag>
+          <item>General error, no error code</item>
+          <tag><c>ERL_DRV_ERROR_ERRNO</c></tag>
+          <item>Error with error code in <c>errno</c></item>
+          <tag><c>ERL_DRV_ERROR_BADARG</c></tag>
+          <item>Error, <c>badarg</c></item>
+        </taglist>
+        <p>If an error code is returned, the port is not started.</p>
       </item>
-      <tag><marker id="stop"/>void (*stop)(ErlDrvData drv_data)</tag>
+      <tag><marker id="stop"/><c>void (*stop)(ErlDrvData drv_data)</c></tag>
       <item>
-        <p>This is called when the port is closed, with
-          <c>port_close/1</c> or <c>Port ! {self(), close}</c>. Note
-          that terminating the port owner process also closes the
+        <p>Called when the port is closed, with
+          <seealso marker="erlang#port_close/1">
+          <c>erlang:port_close/1</c></seealso> or <c>Port ! {self(), close}</c>.
+          Notice that terminating the port owner process also closes the
           port. If <c>drv_data</c> is a pointer to memory allocated in
-	  <c>start</c>, then <c>stop</c> is the place to deallocate that
-	  memory.</p>
+          <c>start</c>, then <c>stop</c> is the place to deallocate that
+          memory.</p>
       </item>
-      <tag><marker id="output"/>void (*output)(ErlDrvData drv_data, char *buf, ErlDrvSizeT len)</tag>
+      <tag><marker id="output"/>
+        <c>void (*output)(ErlDrvData drv_data, char *buf, ErlDrvSizeT len)</c>
+      </tag>
       <item>
-        <p>This is called when an erlang process has sent data to the
-          port. The data is pointed to by <c>buf</c>, and is
-          <c>len</c> bytes.  Data is sent to the port with <c>Port ! {self(), {command, Data}}</c>, or with
-          <c>port_command/2</c>. Depending on how the port was opened,
-          it should be either a list of integers 0...255 or a
-          binary. See <c>open_port/3</c> and <c>port_command/2</c>.</p>
+        <p>Called when an Erlang process has sent data to the port. The data is
+          pointed to by <c>buf</c>, and is <c>len</c> bytes. Data is sent to
+          the port with <c>Port ! {self(), {command, Data}}</c> or with
+          <c>erlang:port_command/2</c>. Depending on how the port was
+          opened, it is to be either a list of integers <c>0...255</c> or a
+          binary. See <seealso marker="erlang#open_port/2">
+          <c>erlang:open_port/2</c></seealso> and
+          <seealso marker="erlang#port_command/2">
+          <c>erlang:port_command/2</c></seealso>.</p>
       </item>
-
-      <tag><marker id="ready_input"/>void (*ready_input)(ErlDrvData drv_data, ErlDrvEvent event)</tag>
-      <item/>
-      <tag><marker id="ready_output"/>void (*ready_output)(ErlDrvData drv_data, ErlDrvEvent event)</tag>
+      <tag><marker id="ready_input"/>
+        <c>void (*ready_input)(ErlDrvData drv_data, ErlDrvEvent event)</c>
+      </tag>
+      <item></item>
+      <tag><marker id="ready_output"/>
+        <c>void (*ready_output)(ErlDrvData drv_data, ErlDrvEvent event)</c>
+      </tag>
       <item>
-        <p>This is called when a driver event (given in the
-          <c>event</c> parameter) is signaled. This is used to help
-          asynchronous drivers "wake up" when something happens.</p>
-        <p>On unix the <c>event</c> is a pipe or socket handle (or
+        <p>Called when a driver event (specified in parameter
+          <c>event</c>) is signaled. This is used to help
+          asynchronous drivers "wake up" when something occurs.</p>
+        <p>On Unix the <c>event</c> is a pipe or socket handle (or
           something that the <c>select</c> system call understands).</p>
-        <p>On Windows the <c>event</c> is an Event or Semaphore (or
-          something that the <c>WaitForMultipleObjects</c> API
+        <p>On Windows the <c>event</c> is an <c>Event</c> or <c>Semaphore</c>
+          (or something that the <c>WaitForMultipleObjects</c> API
           function understands). (Some trickery in the emulator allows
           more than the built-in limit of 64 <c>Events</c> to be used.)</p>
         <p>To use this with threads and asynchronous routines, create a
-          pipe on unix and an Event on Windows. When the routine
+          pipe on Unix and an <c>Event</c> on Windows. When the routine
           completes, write to the pipe (use <c>SetEvent</c> on
-          Windows), this will make the emulator call
+          Windows), this makes the emulator call
           <c>ready_input</c> or <c>ready_output</c>.</p>
-          <p>Spurious events may happen. That is, calls to <c>ready_input</c>
-          or <c>ready_output</c> even though no real events are signaled. In
-          reality it should be rare (and OS dependant), but a robust driver
+        <p>False events can occur. That is, calls to <c>ready_input</c>
+          or <c>ready_output</c> although no real events are signaled. In
+          reality, it is rare (and OS-dependant), but a robust driver
           must nevertheless be able to handle such cases.</p>
       </item>
-      <tag><marker id="driver_name"/>char *driver_name</tag>
+      <tag><marker id="driver_name"/><c>char *driver_name</c></tag>
       <item>
-        <p>This is the name of the driver, it must correspond to the
-          atom used in <c>open_port</c>, and the name of the driver
+        <p>The driver name. It must correspond to the atom used in
+          <seealso marker="erlang#open_port/2">
+          <c>erlang:open_port/2</c></seealso>, and the name of the driver
           library file (without the extension).</p>
       </item>
-      <tag><marker id="finish"/>void (*finish)(void)</tag>
+      <tag><marker id="finish"/><c>void (*finish)(void)</c></tag>
       <item>
-        <p>This function is called by the <c>erl_ddll</c> driver when the
+        <p>Called by the <c>erl_ddll</c> driver when the
           driver is unloaded. (It is only called in dynamic drivers.)</p>
         <p>The driver is only unloaded as a result of calling
-          <c>unload_driver/1</c>, or when the emulator halts.</p>
+          <seealso marker="kernel:erl_ddll#unload_driver/1">
+          <c>erl_ddll:unload_driver/1</c></seealso>,
+          or when the emulator halts.</p>
       </item>
-      <tag>void *handle</tag>
+      <tag><c>void *handle</c></tag>
       <item>
         <p>This field is reserved for the emulator's internal use. The
-          emulator will modify this field; therefore, it is important
-          that the <c>driver_entry</c> isn't declared <c>const</c>.</p> 
+          emulator will modify this field, so it is important
+          that the <c>driver_entry</c> is not declared <c>const</c>.</p> 
       </item>
-      <tag><marker id="control"></marker>ErlDrvSSizeT (*control)(ErlDrvData drv_data, unsigned int command, char *buf, ErlDrvSizeT len, char **rbuf, ErlDrvSizeT rlen)</tag>
+      <tag><marker id="control"></marker>
+        <c>ErlDrvSSizeT (*control)(ErlDrvData drv_data, unsigned int command,
+        char *buf, ErlDrvSizeT len, char **rbuf, ErlDrvSizeT rlen)</c></tag>
       <item>
-        <p>This is a special routine invoked with the erlang function
-          <c>port_control/3</c>. It works a little like an "ioctl" for
-          erlang drivers. The data given to <c>port_control/3</c>
-          arrives in <c>buf</c> and <c>len</c>. The driver may send
+        <p>A special routine invoked with
+          <seealso marker="erlang#port_control/3">
+          <c>erlang:port_control/3</c></seealso>.
+          It works a little like an "ioctl" for
+          Erlang drivers. The data specified to <c>port_control/3</c>
+          arrives in <c>buf</c> and <c>len</c>. The driver can send
           data back, using <c>*rbuf</c> and <c>rlen</c>.</p>
         <p>This is the fastest way of calling a driver and get a
-          response. It won't make any context switch in the erlang
-          emulator, and requires no message passing. It is suitable
-          for calling C function to get faster execution, when erlang
+          response. It makes no context switch in the Erlang
+          emulator and requires no message passing. It is suitable
+          for calling C function to get faster execution, when Erlang
           is too slow.</p>
-        <p>If the driver wants to return data, it should return it in
+        <p>If the driver wants to return data, it is to return it in
           <c>rbuf</c>. When <c>control</c> is called,
           <c>*rbuf</c> points to a default buffer of <c>rlen</c> bytes, which
-          can be used to return data. Data is returned different depending on
+          can be used to return data. Data is returned differently depending on
           the port control flags (those that are set with
-          <seealso marker="erl_driver#set_port_control_flags">set_port_control_flags</seealso>).
-          </p>
+          <seealso marker="erl_driver#set_port_control_flags">
+          <c>erl_driver:set_port_control_flags</c></seealso>).</p>
         <p>If the flag is set to <c>PORT_CONTROL_FLAG_BINARY</c>,
-           a binary will be returned. Small binaries can be returned by writing
-           the raw data into the default buffer. A binary can also be
-           returned by setting <c>*rbuf</c> to point to a binary allocated with
-          <seealso marker="erl_driver#driver_alloc_binary">driver_alloc_binary</seealso>.
-          This binary will be freed automatically after <c>control</c> has returned.
+          a binary is returned. Small binaries can be returned by writing
+          the raw data into the default buffer. A binary can also be
+          returned by setting <c>*rbuf</c> to point to a binary allocated with
+          <seealso marker="erl_driver#driver_alloc_binary">
+          <c>erl_driver:driver_alloc_binary</c></seealso>.
+          This binary is freed automatically after <c>control</c> has returned.
           The driver can retain the binary for <em>read only</em> access with
-          <seealso marker="erl_driver#driver_binary_inc_refc">driver_binary_inc_refc</seealso> to be freed later with
-          <seealso marker="erl_driver#driver_free_binary">driver_free_binary</seealso>.
-          It is never allowed to alter the binary after <c>control</c> has returned.
-          If <c>*rbuf</c> is set to NULL, an empty list will be returned.
-          </p>
+          <seealso marker="erl_driver#driver_binary_inc_refc">
+          <c>erl_driver:driver_binary_inc_refc</c></seealso> to be freed later
+          with <seealso marker="erl_driver#driver_free_binary">
+          <c>erl_driver:driver_free_binary</c></seealso>.
+          It is never allowed to change the binary after <c>control</c> has
+          returned. If <c>*rbuf</c> is set to <c>NULL</c>, an empty list is
+          returned.</p>
         <p>If the flag is set to <c>0</c>, data is returned as a
           list of integers. Either use the default buffer or set
           <c>*rbuf</c> to point to a larger buffer allocated with
-          <seealso marker="erl_driver#driver_alloc">driver_alloc</seealso>.
-          The buffer will be freed automatically after <c>control</c> has returned.</p>
+          <seealso marker="erl_driver#driver_alloc">
+          <c>erl_driver:driver_alloc</c></seealso>. The
+          buffer is freed automatically after <c>control</c> has returned.</p>
         <p>Using binaries is faster if more than a few bytes are returned.</p>
-        <p>The return value is the number of bytes returned in
-          <c>*rbuf</c>.</p>
+        <p>The return value is the number of bytes returned in <c>*rbuf</c>.</p>
       </item>
-
-      <tag><marker id="timeout"/>void (*timeout)(ErlDrvData drv_data)</tag>
+      <tag><marker id="timeout"/><c>void (*timeout)(ErlDrvData drv_data)</c>
+      </tag>
       <item>
-        <p>This function is called any time after the driver's timer
-          reaches 0. The timer is activated with
-          <c>driver_set_timer</c>. There are no priorities or ordering
-          among drivers, so if several drivers time out at the same
-          time, any one of them is called first.</p>
+        <p>Called any time after the driver's timer reaches <c>0</c>.
+          The timer is activated with
+          <seealso marker="erl_driver#driver_set_timer">
+          <c>erl_driver:driver_set_timer</c></seealso>. No priorities or
+          ordering exist among drivers, so if several drivers time out at
+          the same time, anyone of them is called first.</p>
       </item>
-
-      <tag><marker id="outputv"/>void (*outputv)(ErlDrvData drv_data, ErlIOVec *ev)</tag>
+      <tag><marker id="outputv"/>
+        <c>void (*outputv)(ErlDrvData drv_data, ErlIOVec *ev)</c></tag>
       <item>
-        <p>This function is called whenever the port is written to. If
+        <p>Called whenever the port is written to. If
           it is <c>NULL</c>, the <c>output</c> function is called
-          instead. This function is faster than <c>output</c>, because
+          instead. This function is faster than <c>output</c>, as
           it takes an <c>ErlIOVec</c> directly, which requires no
-          copying of the data. The port should be in binary mode, see
-          <c>open_port/2</c>.</p>
-        <p>The <c>ErlIOVec</c> contains both a <c>SysIOVec</c>,
+          copying of the data. The port is to be in binary mode, see
+          <seealso marker="erlang#open_port/2">
+          <c>erlang:open_port/2</c></seealso>.</p>
+        <p><c>ErlIOVec</c> contains both a <c>SysIOVec</c>,
           suitable for <c>writev</c>, and one or more binaries. If
-          these binaries should be retained, when the driver returns
-          from <c>outputv</c>, they can be queued (using <seealso marker="erl_driver#driver_enq_bin">driver_enq_bin</seealso>
-          for instance), or if they are kept in a static or global
+          these binaries are to be retained when the driver returns
+          from <c>outputv</c>, they can be queued (using, for example,
+          <seealso marker="erl_driver#driver_enq_bin">
+          <c>erl_driver:driver_enq_bin</c></seealso>)
+          or, if they are kept in a static or global
           variable, the reference counter can be incremented.</p>
       </item>
-      <tag><marker id="ready_async"/>void (*ready_async)(ErlDrvData drv_data, ErlDrvThreadData thread_data)</tag>
+      <tag><marker id="ready_async"/>
+        <c>void (*ready_async)(ErlDrvData drv_data, ErlDrvThreadData
+        thread_data)</c></tag>
       <item>
-        <p>This function is called after an asynchronous call has
-          completed. The asynchronous call is started with <seealso marker="erl_driver#driver_async">driver_async</seealso>.
-          This function is called from the erlang emulator thread, as
+        <p>Called after an asynchronous call has completed.
+          The asynchronous call is started with
+          <seealso marker="erl_driver#driver_async">
+          <c>erl_driver:driver_async</c></seealso>.
+          This function is called from the Erlang emulator thread, as
           opposed to the asynchronous function, which is called in
-          some thread (if multithreading is enabled).</p>
+          some thread (if multi-threading is enabled).</p>
+      </item>
+      <tag><c>void (*flush)(ErlDrvData drv_data)</c></tag>
+      <item>
+        <p>Called when the port is about to be closed,
+          and there is data in the driver queue that must be flushed
+          before 'stop' can be called.</p>
       </item>
-      <tag><marker id="call"/>ErlDrvSSizeT (*call)(ErlDrvData drv_data, unsigned int command, char *buf, ErlDrvSizeT len, char **rbuf, ErlDrvSizeT rlen, unsigned int *flags)</tag>
+      <tag><marker id="call"/><c>ErlDrvSSizeT (*call)(ErlDrvData drv_data,
+        unsigned int command, char *buf, ErlDrvSizeT len, char **rbuf,
+        ErlDrvSizeT rlen, unsigned int *flags)</c></tag>
       <item>
-        <p>This function is called from <c>erlang:port_call/3</c>. It
-          works a lot like the <c>control</c> call-back, but uses the
+        <p>Called from <seealso marker="erlang#port_call/3">
+          <c>erlang:port_call/3</c></seealso>.
+          It works a lot like the <c>control</c> callback, but uses the
           external term format for input and output.</p>
         <p><c>command</c> is an integer, obtained from the call from
-          erlang (the second argument to <c>erlang:port_call/3</c>).</p>
+          Erlang (the second argument to <c>erlang:port_call/3</c>).</p>
         <p><c>buf</c> and <c>len</c> provide the arguments to the call
           (the third argument to <c>erlang:port_call/3</c>). They can
           be decoded using <c>ei</c> functions.</p>
         <p><c>rbuf</c> points to a return buffer, <c>rlen</c> bytes
-          long. The return data should be a valid erlang term in the
-          external (binary) format. This is converted to an erlang
+          long. The return data is to be a valid Erlang term in the
+          external (binary) format. This is converted to an Erlang
           term and returned by <c>erlang:port_call/3</c> to the
-          caller.  If more space than <c>rlen</c> bytes is needed to
+          caller. If more space than <c>rlen</c> bytes is needed to
           return data, <c>*rbuf</c> can be set to memory allocated with
-          <c>driver_alloc</c>. This memory will be freed automatically
-          after <c>call</c> has returned.</p>
+          <seealso marker="erl_driver#driver_alloc">
+          <c>erl_driver:driver_alloc</c></seealso>.
+          This memory is freed automatically after <c>call</c> has returned.</p>
         <p>The return value is the number of bytes returned in
           <c>*rbuf</c>. If <c>ERL_DRV_ERROR_GENERAL</c> is returned
-          (or in fact, anything &lt; 0), <c>erlang:port_call/3</c> will
-          throw a <c>BAD_ARG</c>.</p>
+          (or in fact, anything &lt; 0), <c>erlang:port_call/3</c>
+          throws a <c>BAD_ARG</c>.</p>
       </item>
-      <tag>void (*event)(ErlDrvData drv_data, ErlDrvEvent event, ErlDrvEventData event_data)</tag>
+      <tag><c>void (*event)(ErlDrvData drv_data, ErlDrvEvent event,
+        ErlDrvEventData event_data)</c></tag>
       <item>
         <p>Intentionally left undocumented.</p>
       </item>
-      <tag><marker id="extended_marker"/>int extended_marker</tag>
+      <tag><marker id="extended_marker"/><c>int extended_marker</c></tag>
       <item>
-        <p>
-          This field should either be equal to <c>ERL_DRV_EXTENDED_MARKER</c>
+        <p>This field is either to be equal to <c>ERL_DRV_EXTENDED_MARKER</c>
           or <c>0</c>. An old driver (not aware of the extended driver
-          interface) should set this field to <c>0</c>. If this field is
-          equal to <c>0</c>, all the fields following this field also
-          <em>have</em> to be <c>0</c>, or <c>NULL</c> in case it is a
-          pointer field.
-        </p>
+          interface) is to set this field to <c>0</c>. If this field is
+          <c>0</c>, all the following fields <em>must</em> also be <c>0</c>,
+          or <c>NULL</c> if it is a pointer field.</p>
       </item>
-      <tag>int major_version</tag>
+      <tag><c>int major_version</c></tag>
       <item>
-        <p>This field should equal <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c> if
-          the <c>extended_marker</c> field equals
+        <p>This field is to equal <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c> if
+          field <c>extended_marker</c> equals
           <c>ERL_DRV_EXTENDED_MARKER</c>.</p> 
       </item>
-      <tag>int minor_version</tag>
+      <tag><c>int minor_version</c></tag>
       <item>
-        <p>
-          This field should equal <c>ERL_DRV_EXTENDED_MINOR_VERSION</c> if
-          the <c>extended_marker</c> field equals
-          <c>ERL_DRV_EXTENDED_MARKER</c>.
-        </p>
+        <p>This field is to equal <c>ERL_DRV_EXTENDED_MINOR_VERSION</c> if
+          field <c>extended_marker</c> equals
+          <c>ERL_DRV_EXTENDED_MARKER</c>.</p>
       </item>
-
-      <tag><marker id="driver_flags"/>int driver_flags</tag>
+      <tag><marker id="driver_flags"/><c>int driver_flags</c></tag>
       <item>
         <p>This field is used to pass driver capability and other
-	  information to the runtime system. If the
-	  <c>extended_marker</c> field equals <c>ERL_DRV_EXTENDED_MARKER</c>,
-	  it should contain <c>0</c> or  driver flags (<c>ERL_DRV_FLAG_*</c>)
-	  ored bitwise. Currently the following driver flags exist:
-        </p>
+          information to the runtime system. If
+          field <c>extended_marker</c> equals <c>ERL_DRV_EXTENDED_MARKER</c>,
+          it is to contain <c>0</c> or driver flags (<c>ERL_DRV_FLAG_*</c>)
+          OR'ed bitwise. The following driver flags exist:</p>
         <taglist>
           <tag><c>ERL_DRV_FLAG_USE_PORT_LOCKING</c></tag>
           <item>
-            The runtime system will use port level locking on
-            all ports executing this driver instead of driver
-            level locking when the driver is run in a runtime
-            system with SMP support. For more information see the
-            <seealso marker="erl_driver#smp_support">erl_driver</seealso> 
-            documentation.
-          </item> 
+            <p>The runtime system uses port-level locking on
+              all ports executing this driver instead of driver-level
+              locking when the driver is run in a runtime
+              system with SMP support. For more information, see
+              <seealso marker="erl_driver#smp_support">
+              <c>erl_driver</c></seealso>.</p>
+          </item>
           <tag><c>ERL_DRV_FLAG_SOFT_BUSY</c></tag>
           <item>
-            Marks that driver instances can handle being called
-	    in the <seealso marker="#output">output</seealso> and/or
-	    <seealso marker="#outputv">outputv</seealso> callbacks even
-	    though a driver instance has marked itself as busy (see
-            <seealso marker="erl_driver#set_busy_port">set_busy_port()</seealso>).
-	    Since erts version 5.7.4 this flag is required for drivers used
-	    by the Erlang distribution (the behaviour has always been
-	    required by drivers used by the distribution).
+            <p>Marks that driver instances can handle being called
+              in the <seealso marker="#output"><c>output</c></seealso> and/or
+              <seealso marker="#outputv"><c>outputv</c></seealso> callbacks
+              although a driver instance has marked itself as busy (see
+              <seealso marker="erl_driver#set_busy_port">
+              <c>erl_driver:set_busy_port</c></seealso>).
+              As from <c>ERTS</c> 5.7.4 this flag is required for drivers used
+              by the Erlang distribution (the behavior has always been
+              required by drivers used by the distribution).</p>
           </item>
           <tag><c>ERL_DRV_FLAG_NO_BUSY_MSGQ</c></tag>
-          <item>Disable busy port message queue functionality. For
-	  more information, see the documentation of the
-	  <seealso marker="erl_driver#erl_drv_busy_msgq_limits">erl_drv_busy_msgq_limits()</seealso>
-	  function.
+          <item>
+            <p>Disables busy port message queue functionality. For
+              more information, see
+              <seealso marker="erl_driver#erl_drv_busy_msgq_limits">
+              <c>erl_driver:erl_drv_busy_msgq_limits</c></seealso>.</p>
           </item>
           <tag><c>ERL_DRV_FLAG_USE_INIT_ACK</c></tag>
-          <item>When this flag is given the linked-in driver has to manually
-          acknowledge that the port has been successfully started using 
-	  <seealso marker="erl_driver#erl_drv_init_ack">erl_drv_init_ack()</seealso>.
-          This allows the implementor to make the erlang:open_port exit with
-          badarg after some initial asynchronous initialization has been done.
+          <item>
+            <p>When this flag is specified, the linked-in driver must manually
+              acknowledge that the port has been successfully started using
+              <seealso marker="erl_driver#erl_drv_init_ack">
+              <c>erl_driver:erl_drv_init_ack()</c></seealso>.
+              This allows the implementor to make the
+              <c>erlang:open_port</c> exit with <c>badarg</c> after some
+              initial asynchronous initialization has been done.</p>
           </item>
         </taglist>
       </item>
-      <tag>void *handle2</tag>
+      <tag><c>void *handle2</c></tag>
       <item>
-        <p>
-          This field is reserved for the emulator's internal use. The
-          emulator will modify this field; therefore, it is important
-          that the <c>driver_entry</c> isn't declared <c>const</c>.
-        </p>
+        <p>This field is reserved for the emulator's internal use. The
+          emulator modifies this field, so it is important
+          that the <c>driver_entry</c> is not declared <c>const</c>.</p>
       </item>
-      <tag><marker id="process_exit"/>void (*process_exit)(ErlDrvData drv_data, ErlDrvMonitor *monitor)</tag>
+      <tag><marker id="process_exit"/>
+        <c>void (*process_exit)(ErlDrvData drv_data, ErlDrvMonitor *monitor)</c>
+      </tag>
       <item>
-        <p>This callback is called when a monitored process exits. The
+        <p>Called when a monitored process exits. The
           <c>drv_data</c> is the data associated with the port for which
-          the process is monitored (using <seealso marker="erl_driver#driver_monitor_process">driver_monitor_process</seealso>)
-          and the <c>monitor</c> corresponds to the <c>ErlDrvMonitor</c> 
+          the process is monitored (using
+          <seealso marker="erl_driver#driver_monitor_process">
+          <c>erl_driver:driver_monitor_process</c></seealso>)
+          and the <c>monitor</c> corresponds to the <c>ErlDrvMonitor</c>
           structure filled
           in when creating the monitor. The driver interface function
-          <seealso marker="erl_driver#driver_get_monitored_process">driver_get_monitored_process</seealso>
-          can be used to retrieve the process id of the exiting process as
+          <seealso marker="erl_driver#driver_get_monitored_process">
+          <c>erl_driver:driver_get_monitored_process</c></seealso>
+          can be used to retrieve the process ID of the exiting process as
           an <c>ErlDrvTermData</c>.</p>
       </item>
-      <tag><marker id="stop_select"/>void (*stop_select)(ErlDrvEvent event, void* reserved)</tag>
+      <tag><marker id="stop_select"/>
+        <c>void (*stop_select)(ErlDrvEvent event, void* reserved)</c></tag>
       <item>
-        <p>This function is called on behalf of
-           <seealso marker="erl_driver#driver_select">driver_select</seealso>
-           when it is safe to close an event object.</p>
+        <p>Called on behalf of
+          <seealso marker="erl_driver#driver_select">
+          <c>erl_driver:driver_select</c></seealso>
+          when it is safe to close an event object.</p>
         <p>A typical implementation on Unix is to do
-           <c>close((int)event)</c>.</p>
-        <p>Argument <c>reserved</c> is intended for future use and should be ignored.</p>
-        <p>In contrast to most of the other call-back functions,
-           <c>stop_select</c> is called independent of any port. No
-           <c>ErlDrvData</c> argument is passed to the function. No
-           driver lock or port lock is guaranteed to be held. The port that
-           called <c>driver_select</c> might even be closed at the
-           time <c>stop_select</c> is called. But it could also be
-           the case that <c>stop_select</c> is called directly by
-           <c>driver_select</c>.</p>
+          <c>close((int)event)</c>.</p>
+        <p>Argument <c>reserved</c> is intended for future use and is to be
+          ignored.</p>
+        <p>In contrast to most of the other callback functions,
+          <c>stop_select</c> is called independent of any port. No
+          <c>ErlDrvData</c> argument is passed to the function. No
+          driver lock or port lock is guaranteed to be held. The port that
+          called <c>driver_select</c> can even be closed at the
+          time <c>stop_select</c> is called. But it can also be
+          the case that <c>stop_select</c> is called directly by
+          <c>erl_driver:driver_select</c>.</p>
         <p>It is not allowed to call any functions in the
-           <seealso marker="erl_driver">driver API</seealso> from
-           <c>stop_select</c>. This strict limitation is due to the
-           volatile context that <c>stop_select</c> may be called.</p>
+          <seealso marker="erl_driver">driver API</seealso> from
+          <c>stop_select</c>. This strict limitation is because the
+          volatile context that <c>stop_select</c> can be called.</p>
       </item>
-
-    </taglist>
-    </item>
-
     </taglist>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="erl_driver">erl_driver(3)</seealso>, 
-      <seealso marker="kernel:erl_ddll">erl_ddll(3)</seealso>,
-      <seealso marker="erlang">erlang(3)</seealso>,
-      kernel(3)</p>
+    <title>See Also</title>
+    <p><seealso marker="erl_driver"><c>erl_driver(3)</c></seealso>,
+      <seealso marker="erlang"><c>erlang(3)</c></seealso>,
+      <seealso marker="kernel:erl_ddll"><c>kernel:erl_ddll(3)</c></seealso></p>
   </section>
 </cref>
 
diff --git a/erts/doc/src/epmd.xml b/erts/doc/src/epmd.xml
index d9f580d081..7b026e17f8 100644
--- a/erts/doc/src/epmd.xml
+++ b/erts/doc/src/epmd.xml
@@ -28,242 +28,260 @@
     <docno>1</docno>
     <approved></approved>
     <checked></checked>
-    <date>98-01-05</date>
+    <date>1998-01-05</date>
     <rev>A</rev>
     <file>epmd.xml</file>
   </header>
 
   <com>epmd</com>
   <comsummary>
-  <p>Erlang Port Mapper Daemon</p>
-  <taglist>
-  <tag><c><![CDATA[epmd [-d|-debug] [DbgExtra...] [-address Addresses] [-port No] [-daemon] [-relaxed_command_check]]]></c></tag>
-  <item>
-  <p>Starts the port mapper daemon</p>
-  </item>
-  <tag><c><![CDATA[epmd [-d|-debug] [-port No] [-names|-kill|-stop Name]]]></c></tag>
-  <item>
-  <p>Communicates with a running port mapper daemon</p>
-  </item>
-  </taglist>
+    <p>Erlang Port Mapper Daemon</p>
+
+    <taglist>
+      <tag><c><![CDATA[epmd [-d|-debug] [DbgExtra...] [-address Addresses]
+        [-port No] [-daemon] [-relaxed_command_check]]]></c></tag>
+      <item>
+	<p>Starts the port mapper daemon.</p>
+      </item>
+      <tag><c><![CDATA[epmd [-d|-debug] [-port No]
+        [-names|-kill|-stop Name]]]></c></tag>
+      <item>
+	<p>Communicates with a running port mapper daemon.</p>
+      </item>
+    </taglist>
   </comsummary>
-  <description>
 
-    <p>This daemon acts as a name server on all hosts  involved  in
-      distributed  Erlang computations. When an Erlang node 
-      starts, the node has a name and it obtains an address from the host 
-      OS kernel.
-      The name and the address are sent to the
+  <description>
+    <p>This daemon acts as a name server on all hosts involved in
+      distributed Erlang computations. When an Erlang node starts,
+      the node has a name and it obtains an address from the host
+      OS kernel. The name and address are sent to the
       <c><![CDATA[epmd]]></c> daemon running on the local host.
       In a TCP/IP environment, the address consists
-      of the IP address and a port number. The name of the node is
+      of the IP address and a port number. The node name is
       an atom on the form of <c><![CDATA[Name@Node]]></c>.
       The job of the <c><![CDATA[epmd]]></c> daemon is to keep track of which
       node name listens on which address. Hence, <c><![CDATA[epmd]]></c> maps
       symbolic node names to machine addresses.</p>
 
-      <p>The TCP/IP <c>epmd</c> daemon actually only keeps track of
+    <p>The TCP/IP <c>epmd</c> daemon only keeps track of
       the <c>Name</c> (first) part of an Erlang node name. The <c>Host</c>
       part (whatever is after the <c><![CDATA[@]]></c>) is implicit in the
-      node name where the <c>epmd</c> daemon was actually contacted,
+      node name where the <c>epmd</c> daemon was contacted,
       as is the IP address where the Erlang node can be
       reached. Consistent and correct TCP naming services are
       therefore required for an Erlang network to function
       correctly.</p>
 
     <taglist>
-    <tag>Starting the port mapper daemon</tag>
-    <item>
-
-        <p>The daemon is started automatically by the <c>erl</c>
-        command if the node is to be distributed and there is no
-        running instance present. If automatically launched,
-        environment variables have to be used to alter the behavior of
-        the daemon. See the <seealso
-        marker="#environment_variables">Environment
-        variables</seealso> section below.</p>
-
-        <p>If the -daemon argument is not given, 
-        <c><![CDATA[epmd]]></c> runs as a normal program with the
-	controlling terminal of the shell in which it is
-	started. Normally, it should run as a daemon.</p>
-
-	<p>Regular start-up options are described in the
-	<seealso marker="#daemon_flags">Regular options</seealso>
-	section below.</p>
-
-	<p>The <c>DbgExtra</c> options are described in the
-	<seealso marker="#debug_flags">DbgExtra options</seealso>
-        section below.</p>
-
-     </item>
-     <tag>Communicating with a running port mapper daemon</tag>
-     <item>
-
-	<p>Communicating with the running epmd daemon by means of the
-	<c>epmd</c> program is done primarily for debugging
-	purposes.</p>
-
-	<p>The different queries are described in the <seealso
-        marker="#interactive_flags">Interactive options</seealso>
-        section below.</p>
-
-     </item>
-     </taglist>
+      <tag>Starting the port mapper daemon</tag>
+      <item>
+        <p>The daemon is started automatically by command
+          <seealso marker="erl"><c>erl</c></seealso>
+          if the node is to be distributed and no running
+          instance is present. If automatically launched
+          environment variables must be used to change the behavior
+          of the daemon; see section
+          <seealso marker="#environment_variables">Environment
+          Variables</seealso>.</p>
+        <p>If argument <c>-daemon</c> is not specified,
+          <c><![CDATA[epmd]]></c> runs as a normal program with the
+          controlling terminal of the shell in which it is
+          started. Normally, it is to be run as a daemon.</p>
+        <p>Regular startup options are described in section
+          <seealso marker="#daemon_flags">Regular Options</seealso>.</p>
+        <p>The <c>DbgExtra</c> options are described in section
+          <seealso marker="#debug_flags">DbgExtra Options</seealso>.</p>
+      </item>
+      <tag>Communicating with a running port mapper daemon</tag>
+      <item>
+        <p>Communicating with the running <c>epmd</c> daemon by the
+          <c>epmd</c> program is done primarily for debugging purposes.</p>
+        <p>The different queries are described in section <seealso
+          marker="#interactive_flags">Interactive options</seealso>.</p>
+      </item>
+    </taglist>
   </description>
+
   <section>
     <marker id="daemon_flags"></marker>
-    <title>Regular options</title>
+    <title>Regular Options</title>
+    <p>These options are available when starting the name server. The name
+      server is normally started automatically by command
+      <seealso marker="erl"><c>erl</c></seealso> (if not already available),
+      but it can also be started at system startup.</p>
 
-    <p>These options are available when starting the actual name server. The name server is normally started automatically by the <c>erl</c> command (if not already available), but it can also be started at i.e. system start-up.</p>
     <taglist>
-    <tag><c><![CDATA[-address List]]></c></tag>
-    <item>
-    <p>Let this instance of <c>epmd</c> listen only on the
-      comma-separated list of IP addresses and on the loopback address
-      (which is implicitly added to the list if it has not been
-      specified). This can also be set using the
-      <c><![CDATA[ERL_EPMD_ADDRESS]]></c> environment variable. See the
-      section <seealso marker="#environment_variables">Environment
-      variables</seealso> below.</p>
-    </item>
-    <tag><c><![CDATA[-port No]]></c></tag>
-    <item>
-      <p>Let this instance of epmd listen to another TCP port than
-      default 4369. This can also be set using the
-      <c><![CDATA[ERL_EPMD_PORT]]></c> environment variable. See the
-      section <seealso marker="#environment_variables">Environment
-      variables</seealso> below</p>
-    </item>
-    <tag><c><![CDATA[-d | -debug]]></c></tag>
-    <item>
-
-      <p>Enable debug output. The more <c>-d</c> flags given, the more
-      debug output you will get (to a certain limit). This option is
-      most useful when the epmd daemon is not started as a daemon.</p>
-    </item>
-    <tag><c><![CDATA[-daemon]]></c></tag>
-    <item>
-      <p>Start epmd detached from the controlling terminal. Logging will end up in syslog when available and correctly configured. If the epmd daemon is started at boot, this option should definitely be used. It is also used when the <c>erl</c> command automatically starts <c>epmd</c>.</p>
-    </item>
-    <tag><c><![CDATA[-relaxed_command_check]]></c></tag>
-    <item>
-      <p>Start the epmd program with relaxed command checking (mostly for backward compatibility). This affects the following:</p>
-      <list type="bulleted">
-          <item>
-            <p>With relaxed command checking, the <c>epmd</c> daemon can be killed from the localhost with i.e. <c>epmd -kill</c> even if there are active nodes registered. Normally only daemons with an empty node database can be killed with the <c>epmd -kill</c> command.</p>
+      <tag><c><![CDATA[-address List]]></c></tag>
+      <item>
+	<p>Lets this instance of <c>epmd</c> listen only on the
+	  comma-separated list of IP addresses and on the loopback address
+	  (which is implicitly added to the list if it has not been
+	  specified). This can also be set using environment variable
+	  <c><![CDATA[ERL_EPMD_ADDRESS]]></c>; see section <seealso
+	  marker="#environment_variables">Environment Variables</seealso>.</p>
+      </item>
+      <tag><c><![CDATA[-port No]]></c></tag>
+      <item>
+	<p>Lets this instance of <c>epmd</c> listen to another TCP port than
+	  default 4369. This can also be set using environment variable
+	  <c><![CDATA[ERL_EPMD_PORT]]></c>; see section <seealso
+	  marker="#environment_variables">Environment Variables</seealso>.</p>
+      </item>
+      <tag><c><![CDATA[-d | -debug]]></c></tag>
+      <item>
+	<p>Enables debug output. The more <c>-d</c> flags specified, the more
+	  debug output you will get (to a certain limit). This option is  most
+	  useful when the <c>epmd</c> daemon is not started as a daemon.</p>
+      </item>
+      <tag><c><![CDATA[-daemon]]></c></tag>
+      <item>
+	<p>Starts <c>epmd</c> detached from the controlling terminal. Logging
+	  ends up in syslog when available and correctly configured. If the
+	  <c>epmd</c> daemon is started at boot, this option is definitely
+	  to be used. It is also used when command <c>erl</c> automatically
+	  starts <c>epmd</c>.</p>
+      </item>
+      <tag><c><![CDATA[-relaxed_command_check]]></c></tag>
+      <item>
+	<p>Starts the <c>epmd</c> program with relaxed command checking
+	  (mostly for backward compatibility). This affects the following:</p>
+	<list type="bulleted">
+	  <item>
+	    <p>With relaxed command checking, the <c>epmd</c> daemon can be
+	      killed from the local host with, for example, command
+	      <c>epmd -kill</c> even if active nodes are registered. Normally
+	      only daemons with an empty node database can be killed with
+	      <c>epmd -kill</c>.</p>
 	  </item>
 	  <item>
-	    <p>The <c>epmd -stop</c> command (and the corresponding messages to epmd, as can be given using <c>erl_interface/ei</c>) is normally always ignored, as it opens up the possibility of a strange situation where two nodes of the same name can be alive at the same time. A node unregisters itself by just closing the connection to epmd, which is why the <c>stop</c> command was only intended for use in debugging situations.</p>
-	    <p>With relaxed command checking enabled, you can forcibly unregister live nodes.</p>
+	    <p>Command <c>epmd -stop</c> (and the corresponding messages to
+	      <c>epmd</c>, as can be specified using <seealso
+	      marker="erl_interface:ei"><c>erl_interface:ei</c></seealso>) is
+	      normally always ignored. This because it can cause a strange
+	      situation where two nodes of the same name can be alive at the
+	      same time. A node unregisters itself by only closing the
+	      connection to <c>epmd</c>, which is why command <c>stop</c>
+	      was only intended for use in debugging situations.</p>
+	    <p>With relaxed command checking enabled, you can forcibly
+	      unregister live nodes.</p>
 	  </item>
-        </list>
-	<p>Relaxed command checking can also be enabled by setting the environment variable <c>ERL_EPMD_RELAXED_COMMAND_CHECK</c> prior to starting <c>epmd</c>.</p>
-	<p>Only use relaxed command checking on systems with very limited interactive usage.</p>
-    </item>
-  </taglist>
+	</list>
+	<p>Relaxed command checking can also be enabled by setting environment
+	  variable <c>ERL_EPMD_RELAXED_COMMAND_CHECK</c> before starting
+	  <c>epmd</c>.</p>
+	<p>Use relaxed command checking only on systems with very limited
+	  interactive usage.</p>
+      </item>
+    </taglist>
   </section>
 
   <section>
     <marker id="debug_flags"></marker>
-    <title>DbgExtra options</title>
-    <p>These options are purely for debugging and testing epmd clients. They should not be used in normal operation.</p>
+    <title>DbgExtra Options</title>
+    <note>
+      <p>These options are only for debugging and testing <c>epmd</c> clients.
+      They are not to be used in normal operation.</p>
+    </note>
 
     <taglist>
-    <tag><c><![CDATA[-packet_timeout Seconds]]></c></tag>
-    <item>
-    <p>Set the number of seconds a connection can be
-    inactive before epmd times out and closes the
-    connection (default 60).</p>
-    </item>
-    <tag><c><![CDATA[-delay_accept Seconds]]></c></tag>
-    <item>
-    <p>To simulate a busy server you can insert a delay between when epmd
-    gets notified that a new connection is requested and
-    when the connection gets accepted.</p>
-    </item>
-    <tag><c><![CDATA[-delay_write Seconds]]></c></tag>
-    <item>
-    <p>Also a simulation of a busy server. Inserts
-    a delay before a reply is sent.</p>
-    </item>
+      <tag><c><![CDATA[-packet_timeout Seconds]]></c></tag>
+      <item>
+	<p>Sets the number of seconds a connection can be
+	  inactive before <c>epmd</c> times out and closes the
+	  connection. Defaults to 60.</p>
+      </item>
+      <tag><c><![CDATA[-delay_accept Seconds]]></c></tag>
+      <item>
+	<p>To simulate a busy server, you can insert a delay between when
+	  <c>epmd</c> gets notified that a new connection is requested and
+	  when the connection gets accepted.</p>
+      </item>
+      <tag><c><![CDATA[-delay_write Seconds]]></c></tag>
+      <item>
+	<p>Also a simulation of a busy server. Inserts
+	  a delay before a reply is sent.</p>
+      </item>
     </taglist>
   </section>
+
   <section>
     <marker id="interactive_flags"></marker>
-    <title>Interactive options</title>
-    <p>These options make <c>epmd</c> run as an interactive command, displaying the results of sending queries to an already running instance of <c>epmd</c>. The epmd contacted is always on the local node, but the <c>-port</c> option can be used to select between instances if several are running using different ports on the host.</p>
-    <taglist>
-    <tag><c><![CDATA[-port No]]></c></tag>
-    <item>
-      <p>Contacts the <c>epmd</c> listening on the given TCP port number
-      (default 4369). This can also be set using the
-      <c><![CDATA[ERL_EPMD_PORT]]></c> environment variable. See the
-      section <seealso marker="#environment_variables">Environment
-      variables</seealso> below.</p>
-    </item>
-    <tag><c><![CDATA[-names]]></c></tag>
-    <item>
-      <p>List names registered with the currently running epmd</p>
-    </item>
-    <tag><c><![CDATA[-kill]]></c></tag>
-    <item>
-      <p>Kill the currently running <c>epmd</c>.</p>
+    <title>Interactive Options</title>
+    <p>These options make <c>epmd</c> run as an interactive command,
+      displaying the results of sending queries to an already running
+      instance of <c>epmd</c>. The <c>epmd</c> contacted is always on the
+      local node, but option <c>-port</c> can be used to select between
+      instances if several are running using different ports on the host.</p>
 
-      <p>Killing the running <c>epmd</c> is only allowed if <c>epmd
-        -names</c> shows an empty database or
-        <c>-relaxed_command_check</c> was given when the running
-        instance of <c>epmd</c> was started. Note that
-        <c>-relaxed_command_check</c> is given when starting the
-        daemon that is to accept killing when it has live nodes
-        registered. When running epmd interactively,
-        <c>-relaxed_command_check</c> has no effect. A daemon that is
-        started without relaxed command checking has to be killed
-        using i.e. signals or some other OS specific method if it has
-        active clients registered.</p>
-    </item>
-    <tag><c><![CDATA[-stop Name]]></c></tag>
-    <item>
-       <p>Forcibly unregister a live node from <c>epmd</c>'s database</p>
-
-       <p>This command can only be used when contacting <c>epmd</c>
-       instances started with the <c>-relaxed_command_check</c>
-       flag. Note that relaxed command checking has to be enabled for
-       the <c>epmd</c> daemon contacted. When running epmd
-       interactively,
-        <c>-relaxed_command_check</c> has no effect.</p>
-    </item>
-  </taglist>
+    <taglist>
+      <tag><c><![CDATA[-port No]]></c></tag>
+      <item>
+	<p>Contacts the <c>epmd</c> listening on the specified TCP port
+	  number (default 4369). This can also be set using environment
+	  variable <c><![CDATA[ERL_EPMD_PORT]]></c>; see section <seealso
+	  marker="#environment_variables">Environment Variables</seealso>.</p>
+      </item>
+      <tag><c><![CDATA[-names]]></c></tag>
+      <item>
+	<p>Lists names registered with the currently running <c>epmd</c>.</p>
+      </item>
+      <tag><c><![CDATA[-kill]]></c></tag>
+      <item>
+	<p>Kills the currently running <c>epmd</c>.</p>
+	<p>Killing the running <c>epmd</c> is only allowed if
+	  <c>epmd -names</c> shows an empty database or if
+	  <c>-relaxed_command_check</c> was specified when the running
+	  instance of <c>epmd</c> was started.</p>
+	<p>Notice that <c>-relaxed_command_check</c> is specified when
+	  starting the daemon that is to accept killing when it has live
+	  nodes registered. When running <c>epmd</c> interactively,
+	  <c>-relaxed_command_check</c> has no effect. A daemon that is
+	  started without relaxed command checking must be killed using,
+	  for example, signals or some other OS-specific method if it has
+	active clients registered.</p>
+      </item>
+      <tag><c><![CDATA[-stop Name]]></c></tag>
+      <item>
+	<p>Forcibly unregisters a live node from the <c>epmd</c> database.</p>
+	<p>This command can only be used when contacting <c>epmd</c>
+	  instances started with flag <c>-relaxed_command_check</c>.</p>
+	<p>Notice that relaxed command checking must enabled for the
+	  <c>epmd</c> daemon contacted. When running <c>epmd</c>
+	  interactively, <c>-relaxed_command_check</c> has no effect.</p>
+      </item>
+    </taglist>
   </section>
+
   <section>
     <marker id="environment_variables"></marker>
-    <title>Environment variables</title>
+    <title>Environment Variables</title>
     <taglist>
       <tag><c><![CDATA[ERL_EPMD_ADDRESS]]></c></tag>
       <item>
-        <p>This environment variable may be set to a comma-separated
-          list of IP addresses, in which case the <c>epmd</c> daemon
-          will listen only on the specified address(es) and on the
-          loopback address (which is implicitly added to the list if it
-          has not been specified). The default behaviour is to listen on
-          all available IP addresses.</p>
+	<p>Can be set to a comma-separated
+	  list of IP addresses, in which case the <c>epmd</c> daemon
+	  will listen only on the specified address(es) and on the
+	  loopback address (which is implicitly added to the list if it
+	  has not been specified). The default behavior is to listen on
+	  all available IP addresses.</p>
       </item>
       <tag><c><![CDATA[ERL_EPMD_PORT]]></c></tag>
       <item>
-        <p>This environment variable can contain the port number epmd will use.
-          The default port will work fine in most cases. A different port can
-          be specified to allow several instances of epmd, representing
-          independent clusters of nodes, to co-exist on the same host.
-          All nodes in a cluster must use the same epmd port number.</p>
+	<p>Can contain the port number <c>epmd</c> will use.
+	  The default port will work fine in most cases. A different port can
+	  be specified to allow several instances of <c>epmd</c>, representing
+	  independent clusters of nodes, to co-exist on the same host.
+	  All nodes in a cluster must use the same <c>epmd</c> port number.</p>
       </item>
       <tag><c><![CDATA[ERL_EPMD_RELAXED_COMMAND_CHECK]]></c></tag>
       <item>
-        <p>If set prior to start, the <c>epmd</c> daemon will behave
-        as if the <c>-relaxed_command_check</c> option was given at
-        start-up. Consequently, if this option is set before starting
-        the Erlang virtual machine, the automatically started
-        <c>epmd</c> will accept the <c>-kill</c> and <c>-stop</c>
-        commands without restrictions.</p>
+	<p>If set before start, the <c>epmd</c> daemon behaves
+	  as if option <c>-relaxed_command_check</c> was specified at
+	  startup. Consequently, if this option is set before starting
+	  the Erlang virtual machine, the automatically started
+	  <c>epmd</c> accepts the <c>-kill</c> and <c>-stop</c>
+	  commands without restrictions.</p>
       </item>
     </taglist>
   </section>
@@ -271,41 +289,45 @@
   <section>
     <title>Logging</title>
     <p>On some operating systems <em>syslog</em> will be used for
-      error reporting when epmd runs as an daemon. To enable
-      the error logging you have to edit <path unix="" windows="">/etc/syslog.conf</path>
-      file and add an entry</p>
+      error reporting when <c>epmd</c> runs as a daemon. To enable
+      the error logging, you must edit the
+      <path unix="" windows="">/etc/syslog.conf</path> file and add an
+      entry:</p>
+
     <code type="none"><![CDATA[
-      !epmd
-      *.*<TABs>/var/log/epmd.log
-    ]]></code>
-    <p>where &lt;TABs&gt; are at least one real tab character. Spaces will
-      silently be ignored.
-      </p>
+  !epmd
+  *.*<TABs>/var/log/epmd.log
+]]></code>
+
+    <p>where <c>&lt;TABs&gt;</c> are at least one real tab character.
+      Spaces are silently ignored.</p>
   </section>
+
   <section>
-  <title>Access restrictions</title>
-  <p>The <c>epmd</c> daemon accepts messages from both localhost and
-  remote hosts. However, only the query commands are answered (and
-  acted upon) if the query comes from a remote host. It is always an
-  error to try to register a nodename if the client is not a process
-  located on the same host as the <c>epmd</c> instance is running on-
-  such requests are considered hostile and the connection is
-  immediately closed.</p>
+    <title>Access Restrictions</title>
+    <p>The <c>epmd</c> daemon accepts messages from both the local host and
+      remote hosts. However, only the query commands are answered (and
+      acted upon) if the query comes from a remote host. It is always an
+      error to try to register a node name if the client is not a process
+      on the same host as the <c>epmd</c> instance is running on. Such
+      requests are considered hostile and the connection is closed
+      immediately.</p>
 
-  <p>The queries accepted from remote nodes are:</p>
-      <list type="bulleted">
-          <item>
-	  <p>Port queries - i.e. on which port does the node with a given
-	  name listen</p>
-	  </item>
-	  <item>
-	  <p>Name listing - i.e. give a list of all names registered on
+    <p>The following queries are accepted from remote nodes:</p>
+
+    <list type="bulleted">
+      <item>
+	<p>Port queries, that is, on which port the node with a specified
+	  name listens</p>
+      </item>
+      <item>
+	<p>Name listing, that is, gives a list of all names registered on
 	  the host</p>
-	  </item>
-     </list>
-  <p>To restrict access further, firewall software has to be used.</p>
-  </section>
+      </item>
+    </list>
 
+    <p>To restrict access further, firewall software must be used.</p>
+  </section>
 </comref>
 
 
diff --git a/erts/doc/src/erl.xml b/erts/doc/src/erl.xml
index 37387f2c59..5559aec30e 100644
--- a/erts/doc/src/erl.xml
+++ b/erts/doc/src/erl.xml
@@ -30,86 +30,92 @@
     <file>erl.xml</file>
   </header>
   <com>erl</com>
-  <comsummary>The Erlang Emulator</comsummary>
+  <comsummary>The Erlang emulator.</comsummary>
   <description>
     <p>The <c><![CDATA[erl]]></c> program starts an Erlang runtime system.
-      The exact details (for example, whether <c><![CDATA[erl]]></c> is a script or
-      a program and which other programs it calls) are system-dependent.</p>
-    <p>Windows users probably wants to use the <c><![CDATA[werl]]></c> program
+      The exact details (for example, whether <c><![CDATA[erl]]></c> is a
+      script or a program and which other programs it calls) are
+      system-dependent.</p>
+
+    <p>Windows users probably want to use the <c><![CDATA[werl]]></c> program
       instead, which runs in its own window with scrollbars and supports
-      command-line editing. The <c><![CDATA[erl]]></c> program on Windows provides
-      no line editing in its shell, and on Windows 95 there is no way
-      to scroll back to text which has scrolled off the screen.
-      The <c><![CDATA[erl]]></c> program must be used, however, in pipelines or if
+      command-line editing. The <c><![CDATA[erl]]></c> program on Windows
+      provides no line editing in its shell, and on Windows 95 there is no way
+      to scroll back to text that has scrolled off the screen. The
+      <c><![CDATA[erl]]></c> program must be used, however, in pipelines or if
       you want to redirect standard input or output.</p>
-      <note><p>As of ERTS version 5.9 (OTP-R15B) the runtime system will by
-               default <em>not</em> bind schedulers to logical processors.
-	       For more information see documentation of the
-	       <seealso marker="#+sbt">+sbt</seealso> system flag.
-	    </p>
-      </note>
+
+    <note>
+      <p>As from <c>ERTS</c> 5.9 (Erlang/OTP R15B) the runtime system does by
+        default <em>not</em> bind schedulers to logical processors.
+	For more information, see system flag
+	<seealso marker="#+sbt"><c>+sbt</c></seealso>.</p>
+    </note>
   </description>
+
   <funcs>
     <func>
       <name>erl &lt;arguments></name>
-      <fsummary>Start an Erlang runtime system</fsummary>
+      <fsummary>Start an Erlang runtime system.</fsummary>
       <desc>
-        <p>Starts an Erlang runtime system.</p>
-        <p>The arguments can be divided into <em>emulator flags</em>,
-          <em>flags</em> and <em>plain arguments</em>:</p>
-        <list type="bulleted">
-          <item>
-            <p>Any argument starting with the character <c><![CDATA[+]]></c> is
-              interpreted as an <seealso marker="#emu_flags">emulator flag</seealso>.</p>
-            <p>As indicated by the name, emulator flags controls
-              the behavior of the emulator.</p>
-          </item>
-          <item>
-            <p>Any argument starting with the character <c><![CDATA[-]]></c>
-              (hyphen) is interpreted as a
-              <seealso marker="#init_flags">flag</seealso> which should
-              be passed to the Erlang part of the runtime system, more
-              specifically to the <c><![CDATA[init]]></c> system process, see
-              <seealso marker="init">init(3)</seealso>.</p>
-            <p>The <c><![CDATA[init]]></c> process itself interprets some of these
-              flags, the <em>init flags</em>. It also stores any
-              remaining flags, the <em>user flags</em>. The latter can
-              be retrieved by calling <c><![CDATA[init:get_argument/1]]></c>.</p>
-            <p>It can be noted that there are a small number of "-"
-              flags which now actually are emulator flags, see
-              the description below.</p>
-          </item>
-          <item>
-            <p>Plain arguments are not interpreted in any way. They are
-              also stored by the <c><![CDATA[init]]></c> process and can be
-              retrieved by calling <c><![CDATA[init:get_plain_arguments/0]]></c>.
-              Plain arguments can occur before the first flag, or after
-              a <c><![CDATA[--]]></c> flag. Additionally, the flag <c><![CDATA[-extra]]></c>
-              causes everything that follows to become plain arguments.</p>
-          </item>
-        </list>
-        <p>Example:</p>
-        <pre>
+	<p>Starts an Erlang runtime system.</p>
+	<p>The arguments can be divided into <em>emulator flags</em>,
+	  <em>flags</em>, and <em>plain arguments</em>:</p>
+	<list type="bulleted">
+	  <item>
+	    <p>Any argument starting with character <c><![CDATA[+]]></c> is
+	      interpreted as an
+	      <seealso marker="#emu_flags">emulator flag</seealso>.</p>
+	    <p>As indicated by the name, emulator flags control
+	      the behavior of the emulator.</p>
+	  </item>
+	  <item>
+	    <p>Any argument starting with character <c><![CDATA[-]]></c>
+	      (hyphen) is interpreted as a
+	      <seealso marker="#init_flags">flag</seealso>, which is to
+	      be passed to the Erlang part of the runtime system, more
+	      specifically to the <c><![CDATA[init]]></c> system process, see
+	      <seealso marker="init"><c>init(3)</c></seealso>.</p>
+	    <p>The <c><![CDATA[init]]></c> process itself interprets some of
+	      these flags, the <em>init flags</em>. It also stores any
+	      remaining flags, the <em>user flags</em>. The latter can be
+	      retrieved by calling <c><![CDATA[init:get_argument/1]]></c>.</p>
+	    <p>A small number of "-" flags exist, which now actually are
+	      emulator flags, see the description below.</p>
+	  </item>
+	  <item>
+	    <p>Plain arguments are not interpreted in any way. They are also
+	      stored by the <c><![CDATA[init]]></c> process and can be retrieved
+	      by calling <c><![CDATA[init:get_plain_arguments/0]]></c>.
+	      Plain arguments can occur before the first flag, or after a
+	      <c><![CDATA[--]]></c> flag. Also, the <c><![CDATA[-extra]]></c>
+	      flag causes everything that follows to become plain arguments.</p>
+	  </item>
+	</list>
+	<p><em>Examples:</em></p>
+	<pre>
 % <input>erl +W w -sname arnie +R 9 -s my_init -extra +bertie</input>
 (arnie@host)1> <input>init:get_argument(sname).</input>
 {ok,[["arnie"]]}
 (arnie@host)2> <input>init:get_plain_arguments().</input>
 ["+bertie"]</pre>
-        <p>Here <c><![CDATA[+W w]]></c> and <c><![CDATA[+R 9]]></c> are emulator flags.
-          <c><![CDATA[-s my_init]]></c> is an init flag, interpreted by <c><![CDATA[init]]></c>.
-          <c><![CDATA[-sname arnie]]></c> is a user flag, stored by <c><![CDATA[init]]></c>.
-          It is read by Kernel and will cause the Erlang runtime system
-          to become distributed. Finally, everything after <c><![CDATA[-extra]]></c>
-          (that is, <c><![CDATA[+bertie]]></c>) is considered as plain arguments.</p>
-        <pre>
+        <p>Here <c><![CDATA[+W w]]></c> and <c><![CDATA[+R 9]]></c> are
+	  emulator flags. <c><![CDATA[-s my_init]]></c> is an init flag,
+	  interpreted by <c><![CDATA[init]]></c>.
+	  <c><![CDATA[-sname arnie]]></c> is a user flag, stored by
+	  <c><![CDATA[init]]></c>. It is read by <c>Kernel</c> and causes the
+	  Erlang runtime system to become distributed. Finally, everything after
+	  <c><![CDATA[-extra]]></c> (that is, <c><![CDATA[+bertie]]></c>) is
+	  considered as plain arguments.</p>
+	<pre>
 % <input>erl -myflag 1</input>
 1> <input>init:get_argument(myflag).</input>
 {ok,[["1"]]}
 2> <input>init:get_plain_arguments().</input>
 []</pre>
-        <p>Here the user flag <c><![CDATA[-myflag 1]]></c> is passed to and stored
-          by the <c><![CDATA[init]]></c> process. It is a user defined flag,
-          presumably used by some user defined application.</p>
+        <p>Here the user flag <c><![CDATA[-myflag 1]]></c> is passed to and
+	  stored by the <c><![CDATA[init]]></c> process. It is a user-defined
+	  flag, presumably used by some user-defined application.</p>
       </desc>
     </func>
   </funcs>
@@ -117,50 +123,54 @@
   <section>
     <marker id="init_flags"></marker>
     <title>Flags</title>
-    <p>In the following list, init flags are marked (init flag).
+    <p>In the following list, init flags are marked "(init flag)".
       Unless otherwise specified, all other flags are user flags, for
       which the values can be retrieved by calling
-      <c><![CDATA[init:get_argument/1]]></c>. Note that the list of user flags is
-      not exhaustive, there may be additional, application specific
-      flags which instead are documented in the corresponding
+      <c><![CDATA[init:get_argument/1]]></c>. Notice that the list of user
+      flags is not exhaustive, there can be more application-specific
+      flags that instead are doscribed in the corresponding
       application documentation.</p>
     <taglist>
-      <tag><c><![CDATA[--]]></c>(init flag)</tag>
+      <tag><c><![CDATA[--]]></c> (init flag)</tag>
       <item>
         <p>Everything following <c><![CDATA[--]]></c> up to the next flag
-          (<c><![CDATA[-flag]]></c> or <c><![CDATA[+flag]]></c>) is considered plain arguments
-          and can be retrieved using <c><![CDATA[init:get_plain_arguments/0]]></c>.</p>
+          (<c><![CDATA[-flag]]></c> or <c><![CDATA[+flag]]></c>) is considered
+          plain arguments and can be retrieved using
+          <c><![CDATA[init:get_plain_arguments/0]]></c>.</p>
       </item>
       <tag><c><![CDATA[-Application Par Val]]></c></tag>
       <item>
-        <p>Sets the application configuration parameter <c><![CDATA[Par]]></c> to
-          the value <c><![CDATA[Val]]></c> for the application <c><![CDATA[Application]]></c>,
-          see <seealso marker="kernel:app">app(4)</seealso> and
-          <seealso marker="kernel:application">application(3)</seealso>.</p>
+        <p>Sets the application configuration parameter <c><![CDATA[Par]]></c>
+          to the value <c><![CDATA[Val]]></c> for the application
+          <c><![CDATA[Application]]></c>; see
+          <seealso marker="kernel:app"><c>kernel:app(4)</c></seealso> and
+          <seealso marker="kernel:application">
+          <c>kernel:application(3)</c></seealso>.</p>
       </item>
       <tag><marker id="args_file"/><c><![CDATA[-args_file FileName]]></c></tag>
       <item>
-        <p>Command line arguments are read from the file <c><![CDATA[FileName]]></c>.
-          The arguments read from the file replace the
-          '<c><![CDATA[-args_file FileName]]></c>' flag on the resulting command line.</p>
-        <p>The file <c><![CDATA[FileName]]></c> should be a plain text file and may
-          contain comments and command line arguments. A comment begins
-          with a # character and continues until next end of line character.
-          Backslash (\\) is used as quoting character. All command line
-          arguments accepted by <c><![CDATA[erl]]></c> are allowed, also the
-          <c><![CDATA[-args_file FileName]]></c> flag. Be careful not to cause circular
-          dependencies between files containing the <c><![CDATA[-args_file]]></c> flag,
-          though.</p>
-        <p>The <c><![CDATA[-extra]]></c> flag is treated specially. Its scope ends
-          at the end of the file. Arguments following an <c><![CDATA[-extra]]></c>
-          flag are moved on the command line into the <c><![CDATA[-extra]]></c> section,
-          i.e. the end of the command line following after an <c><![CDATA[-extra]]></c>
-          flag.</p>
+        <p>Command-line arguments are read from the file
+          <c><![CDATA[FileName]]></c>. The arguments read from the file replace
+          flag '<c><![CDATA[-args_file FileName]]></c>' on the resulting
+          command line.</p>
+        <p>The file <c><![CDATA[FileName]]></c> is to be a plain text file and
+          can contain comments and command-line arguments. A comment begins
+          with a <c>#</c> character and continues until the next end of line
+          character. Backslash (\\) is used as quoting character. All
+          command-line arguments accepted by <c><![CDATA[erl]]></c> are allowed,
+          also flag <c><![CDATA[-args_file FileName]]></c>. Be careful not to
+          cause circular dependencies between files containing flag
+          <c><![CDATA[-args_file]]></c>, though.</p>
+        <p>The flag <c><![CDATA[-extra]]></c> is treated in special way. Its
+          scope ends at the end of the file. Arguments following an
+          <c><![CDATA[-extra]]></c> flag are moved on the command line into the
+          <c><![CDATA[-extra]]></c> section, that is, the end of the command
+          line following after an <c><![CDATA[-extra]]></c> flag.</p>
       </item>
       <tag><c><![CDATA[-async_shell_start]]></c></tag>
       <item>
         <p>The initial Erlang shell does not read user input until
-          the system boot procedure has been completed (Erlang 5.4 and
+          the system boot procedure has been completed (Erlang/OTP 5.4 and
           later). This flag disables the start synchronization feature
           and lets the shell start in parallel with the rest of
           the system.</p>
@@ -168,52 +178,56 @@
       <tag><c><![CDATA[-boot File]]></c></tag>
       <item>
         <p>Specifies the name of the boot file, <c><![CDATA[File.boot]]></c>,
-          which is used to start the system. See
-          <seealso marker="init">init(3)</seealso>. Unless
+          which is used to start the system; see
+          <seealso marker="init"><c>init(3)</c></seealso>. Unless
           <c><![CDATA[File]]></c> contains an absolute path, the system searches
-          for <c><![CDATA[File.boot]]></c> in the current and <c><![CDATA[$ROOT/bin]]></c>
-          directories.</p>
+          for <c><![CDATA[File.boot]]></c> in the current and 
+          <c><![CDATA[$ROOT/bin]]></c> directories.</p>
         <p>Defaults to <c><![CDATA[$ROOT/bin/start.boot]]></c>.</p>
       </item>
       <tag><c><![CDATA[-boot_var Var Dir]]></c></tag>
       <item>
-        <p>If the boot script contains a path variable <c><![CDATA[Var]]></c> other
-          than <c><![CDATA[$ROOT]]></c>, this variable is expanded to <c><![CDATA[Dir]]></c>.
-          Used when applications are installed in another directory
-          than <c><![CDATA[$ROOT/lib]]></c>, see
-          <seealso marker="sasl:systools#make_script/1">systools:make_script/1,2</seealso>.</p>
+        <p>If the boot script contains a path variable <c><![CDATA[Var]]></c>
+          other than <c><![CDATA[$ROOT]]></c>, this variable is expanded to
+          <c><![CDATA[Dir]]></c>. Used when applications are installed in
+          another directory than <c><![CDATA[$ROOT/lib]]></c>; see
+          <seealso marker="sasl:systools#make_script/1">
+          <c>systools:make_script/1,2</c></seealso> in <c>SASL</c>.</p>
       </item>
       <tag><c><![CDATA[-code_path_cache]]></c></tag>
       <item>
-        <p>Enables the code path cache of the code server, see
-          <seealso marker="kernel:code">code(3)</seealso>.</p>
+        <p>Enables the code path cache of the code server; see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-compile Mod1 Mod2 ...]]></c></tag>
       <item>
         <p>Compiles the specified modules and then terminates (with
           non-zero exit code if the compilation of some file did not
-          succeed). Implies <c><![CDATA[-noinput]]></c>. Not recommended - use
-          <seealso marker="erlc">erlc</seealso> instead.</p>
+          succeed). Implies <c><![CDATA[-noinput]]></c>.</p>
+        <p>Not recommended; use <seealso marker="erlc"><c>erlc</c></seealso>
+          instead.</p>
       </item>
       <tag><c><![CDATA[-config Config]]></c></tag>
       <item>
         <p>Specifies the name of a configuration file,
           <c><![CDATA[Config.config]]></c>, which is used to configure
-          applications. See
-          <seealso marker="kernel:app">app(4)</seealso> and
-          <seealso marker="kernel:application">application(3)</seealso>.</p>
+          applications; see
+          <seealso marker="kernel:app"><c>kernel:app(4)</c></seealso> and
+          <seealso marker="kernel:application">
+          <c>kernel:application(3)</c></seealso>.</p>
       </item>
       <tag><marker id="connect_all"/><c><![CDATA[-connect_all false]]></c></tag>
       <item>
-        <p>If this flag is present, <c><![CDATA[global]]></c> will not maintain a
-          fully connected network of distributed Erlang nodes, and then
-          global name registration cannot be used. See
-          <seealso marker="kernel:global">global(3)</seealso>.</p>
+        <p>If this flag is present, <c><![CDATA[global]]></c> does not maintain
+          a fully connected network of distributed Erlang nodes, and then
+          global name registration cannot be used; see
+          <seealso marker="kernel:global"><c>kernel:global(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-cookie Cookie]]></c></tag>
       <item>
         <p>Obsolete flag without any effect and common misspelling for
-          <c><![CDATA[-setcookie]]></c>. Use <c><![CDATA[-setcookie]]></c> instead.</p>
+          <c><![CDATA[-setcookie]]></c>. Use <c><![CDATA[-setcookie]]></c>
+          instead.</p>
       </item>
       <tag><c><![CDATA[-detached]]></c></tag>
       <item>
@@ -223,8 +237,7 @@
       </item>
       <tag><c><![CDATA[-emu_args]]></c></tag>
       <item>
-        <p>Useful for debugging. Prints out the actual arguments
-          sent to the emulator.</p>
+        <p>Useful for debugging. Prints the arguments sent to the emulator.</p>
       </item>
       <tag><c><![CDATA[-env Variable Value]]></c></tag>
       <item>
@@ -234,14 +247,16 @@
         <pre>
 % <input>erl -env DISPLAY gin:0</input></pre>
         <p>In this example, an Erlang runtime system is started with
-          the <c><![CDATA[DISPLAY]]></c> environment variable set to <c><![CDATA[gin:0]]></c>.</p>
+          environment variable <c><![CDATA[DISPLAY]]></c> set to
+          <c><![CDATA[gin:0]]></c>.</p>
       </item>
-      <tag><c><![CDATA[-eval Expr]]></c>(init flag)</tag>
+      <tag><c><![CDATA[-eval Expr]]></c> (init flag)</tag>
       <item>
-        <p>Makes <c><![CDATA[init]]></c> evaluate the expression <c><![CDATA[Expr]]></c>, see
-          <seealso marker="init">init(3)</seealso>.</p>
+        <p>Makes <c><![CDATA[init]]></c> evaluate the expression
+          <c><![CDATA[Expr]]></c>; see
+          <seealso marker="init"><c>init(3)</c></seealso>.</p>
       </item>
-      <tag><c><![CDATA[-extra]]></c>(init flag)</tag>
+      <tag><c><![CDATA[-extra]]></c> (init flag)</tag>
       <item>
         <p>Everything following <c><![CDATA[-extra]]></c> is considered plain
           arguments and can be retrieved using
@@ -249,8 +264,9 @@
       </item>
       <tag><c><![CDATA[-heart]]></c></tag>
       <item>
-        <p>Starts heart beat monitoring of the Erlang runtime system.
-          See <seealso marker="kernel:heart">heart(3)</seealso>.</p>
+        <p>Starts heartbeat monitoring of the Erlang runtime system;
+          see <seealso marker="kernel:heart">
+          <c>kernel:heart(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-hidden]]></c></tag>
       <item>
@@ -258,91 +274,99 @@
           run as a distributed node. Hidden nodes always establish
           hidden connections to all other nodes except for nodes in the
           same global group. Hidden connections are not published on
-          either of the connected nodes, i.e. neither of the connected
-          nodes are part of the result from <c><![CDATA[nodes/0]]></c> on the other
-          node. See also hidden global groups,
-          <seealso marker="kernel:global_group">global_group(3)</seealso>.</p>
+          any of the connected nodes, that is, none of the connected
+          nodes are part of the result from <c><![CDATA[nodes/0]]></c> on the
+          other node. See also hidden global groups;
+          <seealso marker="kernel:global_group">
+          <c>kernel:global_group(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-hosts Hosts]]></c></tag>
       <item>
-        <p>Specifies the IP addresses for the hosts on which Erlang
-          boot servers are running, see
-          <seealso marker="kernel:erl_boot_server">erl_boot_server(3)</seealso>.
-          This flag is mandatory if the <c><![CDATA[-loader inet]]></c> flag is
-          present.</p>
-        <p>The IP addresses must be given in the standard form (four
-          decimal numbers separated by periods, for example
-          <c><![CDATA["150.236.20.74"]]></c>. Hosts names are not acceptable, but
-          a broadcast address (preferably limited to the local network)
+        <p>Specifies the IP addresses for the hosts on which Erlang boot servers
+          are running, see <seealso marker="kernel:erl_boot_server">
+          <c>kernel:erl_boot_server(3)</c></seealso>. This flag
+          is mandatory if flag <c><![CDATA[-loader inet]]></c> is present.</p>
+        <p>The IP addresses must be specified in the standard form (four
+          decimal numbers separated by periods, for example,
+          <c><![CDATA["150.236.20.74"]]></c>. Hosts names are not acceptable,
+          but a broadcast address (preferably limited to the local network)
           is.</p>
       </item>
       <tag><c><![CDATA[-id Id]]></c></tag>
       <item>
         <p>Specifies the identity of the Erlang runtime system. If it is
           run as a distributed node, <c><![CDATA[Id]]></c> must be identical to
-          the name supplied together with the <c><![CDATA[-sname]]></c> or
-          <c><![CDATA[-name]]></c> flag.</p>
+          the name supplied together with flag <c><![CDATA[-sname]]></c> or
+          <c><![CDATA[-name]]></c>.</p>
       </item>
       <tag><c><![CDATA[-init_debug]]></c></tag>
       <item>
         <p>Makes <c><![CDATA[init]]></c> write some debug information while
           interpreting the boot script.</p>
       </item>
-      <tag><marker id="instr"/><c><![CDATA[-instr]]></c>(emulator flag)</tag>
+      <tag><marker id="instr"/><c><![CDATA[-instr]]></c> (emulator flag)</tag>
       <item>
         <p>Selects an instrumented Erlang runtime system (virtual
           machine) to run, instead of the ordinary one. When running an
           instrumented runtime system, some resource usage data can be
-          obtained and analysed using the module <c><![CDATA[instrument]]></c>.
+          obtained and analyzed using the <c><![CDATA[instrument]]></c> module.
           Functionally, it behaves exactly like an ordinary Erlang
           runtime system.</p>
       </item>
       <tag><c><![CDATA[-loader Loader]]></c></tag>
       <item>
-        <p>Specifies the method used by <c><![CDATA[erl_prim_loader]]></c> to load
-          Erlang modules into the system. See
-          <seealso marker="erl_prim_loader">erl_prim_loader(3)</seealso>.
-          Two <c><![CDATA[Loader]]></c> methods are supported, <c><![CDATA[efile]]></c> and
-          <c><![CDATA[inet]]></c>. <c><![CDATA[efile]]></c> means use the local file system,
-          this is the default. <c><![CDATA[inet]]></c> means use a boot server on
-          another machine, and the <c><![CDATA[-id]]></c>, <c><![CDATA[-hosts]]></c> and
-          <c><![CDATA[-setcookie]]></c> flags must be specified as well. If
-          <c><![CDATA[Loader]]></c> is something else, the user supplied
+        <p>Specifies the method used by <c><![CDATA[erl_prim_loader]]></c> to
+          load Erlang modules into the system; see
+          <seealso marker="erl_prim_loader"><c>erl_prim_loader(3)</c></seealso>.
+          Two <c><![CDATA[Loader]]></c> methods are supported:</p>
+        <list type="bulleted">
+          <item>
+            <p><c><![CDATA[efile]]></c>, which means use the local file system,
+              this is the default.</p>
+          </item>
+          <item>
+            <p><c><![CDATA[inet]]></c>, which means use a boot server on
+              another machine. The flags <c><![CDATA[-id]]></c>,
+              <c><![CDATA[-hosts]]></c> and <c><![CDATA[-setcookie]]></c> must
+              also be specified.</p>
+          </item>
+        </list>
+        <p>If <c><![CDATA[Loader]]></c> is something else, the user-supplied
           <c><![CDATA[Loader]]></c> port program is started.</p>
       </item>
       <tag><c><![CDATA[-make]]></c></tag>
       <item>
-        <p>Makes the Erlang runtime system invoke <c><![CDATA[make:all()]]></c> in
-          the current working directory and then terminate. See
-          <seealso marker="tools:make">make(3)</seealso>. Implies
+        <p>Makes the Erlang runtime system invoke <c><![CDATA[make:all()]]></c>
+          in the current working directory and then terminate; see
+          <seealso marker="tools:make"><c>tools:make(3)</c></seealso>. Implies
           <c><![CDATA[-noinput]]></c>.</p>
       </item>
       <tag><c><![CDATA[-man Module]]></c></tag>
       <item>
-        <p>Displays the manual page for the Erlang module <c><![CDATA[Module]]></c>.
-          Only supported on Unix.</p>
+        <p>Displays the manual page for the Erlang module
+          <c><![CDATA[Module]]></c>. Only supported on Unix.</p>
       </item>
       <tag><c><![CDATA[-mode interactive | embedded]]></c></tag>
       <item>
-        <p>Indicates if the system should load code dynamically
-          (<c><![CDATA[interactive]]></c>), or if all code should be loaded
-          during system initialization (<c><![CDATA[embedded]]></c>), see
-          <seealso marker="kernel:code">code(3)</seealso>. Defaults to
-          <c><![CDATA[interactive]]></c>.</p>
+        <p>Indicates if the system is to load code dynamically
+          (<c><![CDATA[interactive]]></c>), or if all code is to be loaded
+          during system initialization (<c><![CDATA[embedded]]></c>); see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.
+          Defaults to <c><![CDATA[interactive]]></c>.</p>
       </item>
       <tag><c><![CDATA[-name Name]]></c></tag>
       <item>
         <p>Makes the Erlang runtime system into a distributed node.
           This flag invokes all network servers necessary for a node to
-          become distributed. See
-          <seealso marker="kernel:net_kernel">net_kernel(3)</seealso>.
-          It is also ensured that <c><![CDATA[epmd]]></c> runs on the current host
-          before Erlang is started. See
-          <seealso marker="epmd">epmd(1)</seealso> and the
+          become distributed; see <seealso marker="kernel:net_kernel">
+          <c>kernel:net_kernel(3)</c></seealso>. It is also ensured that
+          <c><![CDATA[epmd]]></c> runs on the current host before Erlang is
+          started; see <seealso marker="epmd"><c>epmd(1)</c></seealso>.and the
           <seealso marker="#start_epmd"><c>-start_epmd</c></seealso> option.</p>
-        <p>The name of the node will be <c><![CDATA[Name@Host]]></c>, where
-          <c><![CDATA[Host]]></c> is the fully qualified host name of the current
-          host. For short names, use the <c><![CDATA[-sname]]></c> flag instead.</p>
+        <p>The node name will be <c><![CDATA[Name@Host]]></c>, where
+          <c><![CDATA[Host]]></c> is the fully qualified host name of the
+          current host. For short names, use flag <c><![CDATA[-sname]]></c>
+          instead.</p>
       </item>
       <tag><c><![CDATA[-noinput]]></c></tag>
       <item>
@@ -353,115 +377,111 @@
       <item>
         <p>Starts an Erlang runtime system with no shell. This flag
           makes it possible to have the Erlang runtime system as a
-          component in a series of UNIX pipes.</p>
+          component in a series of Unix pipes.</p>
       </item>
       <tag><c><![CDATA[-nostick]]></c></tag>
       <item>
         <p>Disables the sticky directory facility of the Erlang code
-          server, see
-          <seealso marker="kernel:code">code(3)</seealso>.</p>
+          server; see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-oldshell]]></c></tag>
       <item>
-        <p>Invokes the old Erlang shell from Erlang 3.3. The old shell
+        <p>Invokes the old Erlang shell from Erlang/OTP 3.3. The old shell
           can still be used.</p>
       </item>
       <tag><c><![CDATA[-pa Dir1 Dir2 ...]]></c></tag>
       <item>
         <p>Adds the specified directories to the beginning of the code
-          path, similar to <c><![CDATA[code:add_pathsa/1]]></c>. See
-          <seealso marker="kernel:code">code(3)</seealso>.
+          path, similar to <c><![CDATA[code:add_pathsa/1]]></c>; see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.
 	  As an alternative to <c>-pa</c>, if several directories are
 	  to be prepended to the code path and the directories have a
-	  common parent directory, that parent directory could be
-	  specified in the <c>ERL_LIBS</c> environment variable.
-	  See <seealso marker="kernel:code">code(3)</seealso>.</p>
+	  common parent directory, that parent directory can be
+	  specified in environment variable <c>ERL_LIBS</c>; see
+	  <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-pz Dir1 Dir2 ...]]></c></tag>
       <item>
         <p>Adds the specified directories to the end of the code path,
-          similar to <c><![CDATA[code:add_pathsz/1]]></c>. See
-          <seealso marker="kernel:code">code(3)</seealso>.</p>
+          similar to <c><![CDATA[code:add_pathsz/1]]></c>; see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-path Dir1 Dir2 ...]]></c></tag>
       <item>
-        <p>Replaces the path specified in the boot script. See
-          <seealso marker="sasl:script">script(4)</seealso>.</p>
+        <p>Replaces the path specified in the boot script; see
+          <seealso marker="sasl:script"><c>sasl:script(4)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-proto_dist Proto]]></c></tag>
       <item>
-        <p>Specify a protocol for Erlang distribution.</p>
-	    <taglist>
-	      <tag><c>inet_tcp</c></tag>
-              <item>
-                  <p>TCP over IPv4 (the default)</p>
-              </item>
-	      <tag><c>inet_tls</c></tag>
-              <item>
-                  <p>distribution over TLS/SSL</p>
-              </item>
-	      <tag><c>inet6_tcp</c></tag>
-              <item>
-                  <p>TCP over IPv6</p>
-              </item>
+        <p>Specifies a protocol for Erlang distribution:</p>
+        <taglist>
+          <tag><c>inet_tcp</c></tag>
+          <item>TCP over IPv4 (the default)</item>
+          <tag><c>inet_tls</c></tag>
+          <item>Distribution over TLS/SSL</item>
+          <tag><c>inet6_tcp</c></tag>
+          <item>TCP over IPv6</item>
         </taglist>
         <p>For example, to start up IPv6 distributed nodes:</p>
 <pre>
-% <input>erl -name [email protected] -proto_dist inet6_tcp</input>
-</pre>
+% <input>erl -name [email protected] -proto_dist inet6_tcp</input></pre>
       </item>
       <tag><c><![CDATA[-remsh Node]]></c></tag>
       <item>
-        <p>Starts Erlang with a remote shell connected to <c><![CDATA[Node]]></c>.</p>
+        <p>Starts Erlang with a remote shell connected to
+          <c><![CDATA[Node]]></c>.</p>
       </item>
       <tag><c><![CDATA[-rsh Program]]></c></tag>
       <item>
-        <p>Specifies an alternative to <c><![CDATA[rsh]]></c> for starting a slave
-          node on a remote host. See
-          <seealso marker="stdlib:slave">slave(3)</seealso>.</p>
+        <p>Specifies an alternative to <c><![CDATA[rsh]]></c> for starting a
+          slave node on a remote host; see
+          <seealso marker="stdlib:slave"><c>stdlib:slave(3)</c></seealso>.</p>
       </item>
-      <tag><c><![CDATA[-run Mod [Func [Arg1, Arg2, ...]]]]></c>(init flag)</tag>
+      <tag><c><![CDATA[-run Mod [Func [Arg1, Arg2, ...]]]]></c> (init
+        flag)</tag>
       <item>
-        <p>Makes <c><![CDATA[init]]></c> call the specified function. <c><![CDATA[Func]]></c>
-          defaults to <c><![CDATA[start]]></c>. If no arguments are provided,
-          the function is assumed to be of arity 0. Otherwise it is
-          assumed to be of arity 1, taking the list
-          <c><![CDATA[[Arg1,Arg2,...]]]></c> as argument. All arguments are passed
-          as strings. See
-          <seealso marker="init">init(3)</seealso>.</p>
+        <p>Makes <c><![CDATA[init]]></c> call the specified function.
+          <c><![CDATA[Func]]></c> defaults to <c><![CDATA[start]]></c>.
+          If no arguments are provided, the function is assumed to be of
+          arity 0. Otherwise it is assumed to be of arity 1, taking the list
+          <c><![CDATA[[Arg1,Arg2,...]]]></c> as argument. All arguments are
+          passed as strings. See <seealso marker="init">
+          <c>init(3)</c></seealso>.</p>
       </item>
-      <tag><c><![CDATA[-s Mod [Func [Arg1, Arg2, ...]]]]></c>(init flag)</tag>
+      <tag><c><![CDATA[-s Mod [Func [Arg1, Arg2, ...]]]]></c> (init flag)</tag>
       <item>
-        <p>Makes <c><![CDATA[init]]></c> call the specified function. <c><![CDATA[Func]]></c>
-          defaults to <c><![CDATA[start]]></c>. If no arguments are provided,
-          the function is assumed to be of arity 0. Otherwise it is
-          assumed to be of arity 1, taking the list
-          <c><![CDATA[[Arg1,Arg2,...]]]></c> as argument. All arguments are passed
-          as atoms. See
-          <seealso marker="init">init(3)</seealso>.</p>
+        <p>Makes <c><![CDATA[init]]></c> call the specified function.
+          <c><![CDATA[Func]]></c> defaults to <c><![CDATA[start]]></c>.
+          If no arguments are provided, the function is assumed to be of
+          arity 0. Otherwise it is assumed to be of arity 1, taking the list
+          <c><![CDATA[[Arg1,Arg2,...]]]></c> as argument. All arguments are
+          passed as atoms. See <seealso marker="init">
+          <c>init(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-setcookie Cookie]]></c></tag>
       <item>
-        <p>Sets the magic cookie of the node to <c><![CDATA[Cookie]]></c>, see
-          <seealso marker="erlang#set_cookie/2">erlang:set_cookie/2</seealso>.</p>
+        <p>Sets the magic cookie of the node to <c><![CDATA[Cookie]]></c>; see
+          <seealso marker="erlang#set_cookie/2">
+          <c>erlang:set_cookie/2</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[-shutdown_time Time]]></c></tag>
       <item>
         <p>Specifies how long time (in milliseconds) the <c><![CDATA[init]]></c>
           process is allowed to spend shutting down the system. If
-          <c><![CDATA[Time]]></c> ms have elapsed, all processes still existing are
-          killed. Defaults to <c><![CDATA[infinity]]></c>.</p>
+          <c><![CDATA[Time]]></c> milliseconds have elapsed, all processes still
+          existing are killed. Defaults to <c><![CDATA[infinity]]></c>.</p>
       </item>
       <tag><c><![CDATA[-sname Name]]></c></tag>
       <item>
-        <p>Makes the Erlang runtime system into a distributed node,
-          similar to <c><![CDATA[-name]]></c>, but the host name portion of the node
+        <p>Makes the Erlang runtime system into a distributed node, similar to
+          <c><![CDATA[-name]]></c>, but the host name portion of the node
           name <c><![CDATA[Name@Host]]></c> will be the short name, not fully
           qualified.</p>
         <p>This is sometimes the only way to run distributed Erlang if
-          the DNS (Domain Name System) is not running. There can be no
-          communication between nodes running with the <c><![CDATA[-sname]]></c>
-          flag and those running with the <c><![CDATA[-name]]></c> flag, as node
+          the Domain Name System (DNS) is not running. No communication can
+          exist between nodes running with flag <c><![CDATA[-sname]]></c>
+          and those running with flag <c><![CDATA[-name]]></c>, as node
           names must be unique in distributed Erlang systems.</p>
       </item>
       <tag><marker id="start_epmd"/><c>-start_epmd true | false</c></tag>
@@ -481,19 +501,21 @@
       </item>
       <tag><marker id="smp"/><c><![CDATA[-smp [enable|auto|disable]]]></c></tag>
       <item>
-        <p><c>-smp enable</c> and <c>-smp</c> starts the Erlang runtime
-	  system with SMP support enabled. This may fail if no runtime
+        <p><c>-smp enable</c> and <c>-smp</c> start the Erlang runtime
+	  system with SMP support enabled. This can fail if no runtime
 	  system with SMP support is available. <c>-smp auto</c> starts
 	  the Erlang runtime system with SMP support enabled if it is
-	  available and more than one logical processor are detected.
+	  available and more than one logical processor is detected.
 	  <c>-smp disable</c> starts a runtime system without SMP support.</p>
-        <p><em>NOTE</em>: The runtime system with SMP support will not
-          be available on all supported platforms. See also the
-          <seealso marker="#+S">+S</seealso> flag.</p>
+        <note>
+          <p>The runtime system with SMP support is not available on all
+            supported platforms. See also flag
+            <seealso marker="#+S"><c>+S</c></seealso>.</p>
+        </note>
       </item>
-      <tag><c><![CDATA[-version]]></c>(emulator flag)</tag>
+      <tag><c><![CDATA[-version]]></c> (emulator flag)</tag>
       <item>
-        <p>Makes the emulator print out its version number. The same
+        <p>Makes the emulator print its version number. The same
           as <c><![CDATA[erl +V]]></c>.</p>
       </item>
     </taglist>
@@ -505,133 +527,169 @@
     <p><c><![CDATA[erl]]></c> invokes the code for the Erlang emulator (virtual
       machine), which supports the following flags:</p>
     <taglist>
-      <tag><marker id="async_thread_stack_size"/><c><![CDATA[+a size]]></c></tag>
+      <tag><marker id="async_thread_stack_size"/>
+        <c><![CDATA[+a size]]></c></tag>
       <item>
         <p>Suggested stack size, in kilowords, for threads in the
-          async-thread pool. Valid range is 16-8192 kilowords. The
-          default suggested stack size is 16 kilowords, i.e, 64
+          async thread pool. Valid range is 16-8192 kilowords. The
+          default suggested stack size is 16 kilowords, that is, 64
           kilobyte on 32-bit architectures. This small default size
-          has been chosen since the amount of async-threads might
-          be quite large. The default size is enough for drivers
-          delivered with Erlang/OTP, but might not be sufficiently
-          large for other dynamically linked in drivers that use the
-          <seealso marker="erl_driver#driver_async">driver_async()</seealso>
-          functionality. Note that the value passed is only a
-          suggestion, and it might even be ignored on some
-          platforms.</p>
+          has been chosen because the number of async threads can
+          be large. The default size is enough for drivers
+          delivered with Erlang/OTP, but might not be large
+          enough for other dynamically linked-in drivers that use the
+          <seealso marker="erl_driver#driver_async">
+          <c>driver_async()</c></seealso> functionality.
+          Notice that the value passed is only a suggestion,
+          and it can even be ignored on some platforms.</p>
       </item>
       <tag><marker id="async_thread_pool_size"/><c><![CDATA[+A size]]></c></tag>
       <item>
-        <p>Sets the number of threads in async thread pool, valid range
-          is 0-1024. If thread support is available, the default is 10.</p>
+        <p>Sets the number of threads in async thread pool. Valid range
+          is 0-1024. Defaults to 10 if thread support is available.</p>
       </item>
       <tag><c><![CDATA[+B [c | d | i]]]></c></tag>
       <item>
-        <p>The <c><![CDATA[c]]></c> option makes <c><![CDATA[Ctrl-C]]></c> interrupt the current
-          shell instead of invoking the emulator break handler.
-          The <c><![CDATA[d]]></c> option (same as specifying <c><![CDATA[+B]]></c> without an
-          extra option) disables the break handler. The <c><![CDATA[i]]></c> option
-          makes the emulator ignore any break signal.</p>
-        <p>If the <c><![CDATA[c]]></c> option is used with <c><![CDATA[oldshell]]></c> on Unix,
-          <c><![CDATA[Ctrl-C]]></c> will restart the shell process rather than
-          interrupt it.</p>
-        <p>Note that on Windows, this flag is only applicable for 
-          <c><![CDATA[werl]]></c>, not <c><![CDATA[erl]]></c> (<c><![CDATA[oldshell]]></c>). Note also that
-          <c><![CDATA[Ctrl-Break]]></c> is used instead of <c><![CDATA[Ctrl-C]]></c> on Windows.</p>
+        <p>Option <c><![CDATA[c]]></c> makes <c><![CDATA[Ctrl-C]]></c>
+          interrupt the current shell instead of invoking the emulator break
+          handler. Option <c><![CDATA[d]]></c> (same as specifying
+          <c><![CDATA[+B]]></c> without an extra option) disables the break
+          handler. Option <c><![CDATA[i]]></c> makes the emulator ignore any
+          break signal.</p>
+        <p>If option <c><![CDATA[c]]></c> is used with
+          <c><![CDATA[oldshell]]></c> on Unix, <c><![CDATA[Ctrl-C]]></c> will
+          restart the shell process rather than interrupt it.</p>
+        <p>Notice that on Windows, this flag is only applicable for
+          <c><![CDATA[werl]]></c>, not <c><![CDATA[erl]]></c>
+          (<c><![CDATA[oldshell]]></c>). Notice also that
+          <c><![CDATA[Ctrl-Break]]></c> is used instead of
+          <c><![CDATA[Ctrl-C]]></c> on Windows.</p>
       </item>
       <tag><marker id="+c"/><c><![CDATA[+c true | false]]></c></tag>
       <item>
-        <p>Enable or disable
-	<seealso marker="time_correction#Time_Correction">time correction</seealso>:</p>
+        <p>Enables or disables
+          <seealso marker="time_correction#Time_Correction">time
+          correction</seealso>:</p>
 	<taglist>
 	  <tag><c>true</c></tag>
-	  <item><p>Enable time correction. This is the default if
-	  time correction is supported on the specific platform.</p></item>
-
-	  <tag><c>false</c></tag>
-	  <item><p>Disable time correction.</p></item>
-	</taglist>
-	<p>For backwards compatibility, the boolean value can be omitted.
-	This is interpreted as <c>+c false</c>.
-	</p>
-      </item>
-      <tag><marker id="+C_"/><c><![CDATA[+C no_time_warp | single_time_warp | multi_time_warp]]></c></tag>
-      <item>
-        <p>Set
-	<seealso marker="time_correction#Time_Warp_Modes">time warp mode</seealso>:
-	</p>
-	<taglist>
-	  <tag><c>no_time_warp</c></tag>
-	  <item><p><seealso marker="time_correction#No_Time_Warp_Mode">No Time Warp Mode</seealso> (the default)</p></item>
-	  <tag><c>single_time_warp</c></tag>
-	  <item><p><seealso marker="time_correction#Single_Time_Warp_Mode">Single Time Warp Mode</seealso></p></item>
-	  <tag><c>multi_time_warp</c></tag>
-	  <item><p><seealso marker="time_correction#Multi_Time_Warp_Mode">Multi Time Warp Mode</seealso></p></item>
-	</taglist>
+          <item>Enables time correction. This is the default if
+            time correction is supported on the specific platform.</item>
+          <tag><c>false</c></tag>
+          <item>Disables time correction.</item>
+          </taglist>
+        <p>For backward compatibility, the boolean value can be omitted.
+          This is interpreted as <c>+c false</c>.</p>
+      </item>
+      <tag><marker id="+C_"/><c><![CDATA[+C no_t<seealso marker="erlang:now/0">erlang:now()</seealso>ime_warp | single_time_warp |
+        multi_time_warp]]></c></tag>
+      <item>
+        <p>Sets <seealso marker="time_correction#Time_Warp_Modes">time warp
+          mode</seealso>:</p>
+        <taglist>
+        <tag><c>no_time_warp</c></tag>
+          <item><seealso marker="time_correction#No_Time_Warp_Mode">
+            No time warp mode</seealso> (the default)</item>
+          <tag><c>single_time_warp</c></tag>
+          <item><seealso marker="time_correction#Single_Time_Warp_Mode">
+            Single time warp mode</seealso></item>
+          <tag><c>multi_time_warp</c></tag>
+          <item><seealso marker="time_correction#Multi_Time_Warp_Mode">
+            Multi-time warp mode</seealso></item>
+      </taglist>
       </item>
       <tag><c><![CDATA[+d]]></c></tag>
       <item>
         <p>If the emulator detects an internal error (or runs out of memory),
-	it will by default generate both a crash dump and a core dump.
-	The core dump will, however, not be very useful since the content
-	of process heaps is destroyed by the crash dump generation.</p>
-
-	<p>The <c>+d</c> option instructs the emulator to only produce a
-	core dump and no crash dump if an internal error is detected.</p>
-
-	<p>Calling <c>erlang:halt/1</c> with a string argument will still
-	produce a crash dump. On Unix systems, sending an emulator process
-	a SIGUSR1 signal will also force a crash dump.</p>
+          it, by default, generates both a crash dump and a core dump.
+          The core dump is, however, not very useful as the content
+          of process heaps is destroyed by the crash dump generation.</p>
+        <p>Option <c>+d</c> instructs the emulator to produce only a
+          core dump and no crash dump if an internal error is detected.</p>
+        <p>Calling <seealso marker="erlang:halt/1">
+          <c>erlang:halt/1</c></seealso> with a string argument still
+          produces a crash dump. On Unix systems, sending an emulator process
+          a <c>SIGUSR1</c> signal also forces a crash dump.</p>
       </item>
       <tag><marker id="+e"/><c><![CDATA[+e Number]]></c></tag>
       <item>
-        <p>Set max number of ETS tables.</p>
+        <p>Sets the maximum number of <c>ets</c> tables.</p>
       </item>
       <tag><c><![CDATA[+ec]]></c></tag>
       <item>
-        <p>Force the <c>compressed</c> option on all ETS tables.
-              Only intended for test and evaluation.</p>
+        <p>Forces option <c>compressed</c> on all <c>ets</c> tables.
+          Only intended for test and evaluation.</p>
       </item>
-      <tag><marker id="file_name_encoding"></marker><c><![CDATA[+fnl]]></c></tag>
+      <tag><marker id="file_name_encoding"></marker>
+        <c><![CDATA[+fnl]]></c></tag>
       <item>
-        <p>The VM works with file names as if they are encoded using the ISO-latin-1 encoding, disallowing Unicode characters with codepoints beyond 255.</p>
-	<p>See <seealso marker="stdlib:unicode_usage#unicode_file_names">STDLIB User's Guide</seealso> for more infomation about unicode file names. Note that this value also applies to command-line parameters and environment variables (see <seealso marker="stdlib:unicode_usage#unicode_in_environment_and_parameters">STDLIB User's Guide</seealso>).</p>
+        <p>The virtual machine works with filenames as if they are encoded
+          using the ISO Latin-1 encoding, disallowing Unicode characters with
+          code points &gt; 255.</p>
+        <p>For more information about Unicode filenames, see section
+          <seealso marker="stdlib:unicode_usage#unicode_file_names">Unicode
+          Filenames</seealso> in the <c>STDLIB</c> User's Guide. Notice that
+          this value also applies to command-line parameters and environment
+          variables (see section <seealso
+          marker="stdlib:unicode_usage#unicode_in_environment_and_parameters">
+          Unicode in Enviroment and Parameters</seealso> in the <c>STDLIB</c>
+          User's Guide).</p>
       </item>
       <tag><c><![CDATA[+fnu[{w|i|e}]]]></c></tag>
       <item>
-        <p>The VM works with file names as if they are encoded using
-        UTF-8 (or some other system specific Unicode encoding). This
-        is the default on operating systems that enforce Unicode
-        encoding, i.e. Windows and MacOS X.</p>
-	<p>The <c>+fnu</c> switch can be followed by <c>w</c>,
-	<c>i</c>, or <c>e</c> to control the way wrongly encoded file
-	names are to be reported. <c>w</c> means that a warning is
-	sent to the <c>error_logger</c> whenever a wrongly encoded
-	file name is "skipped" in directory listings, <c>i</c> means
-	that those wrongly encoded file names are silently ignored and
-	<c>e</c> means that the API function will return an error
-	whenever a wrongly encoded file (or directory) name is
-	encountered. <c>w</c> is the default. Note that
-	<c>file:read_link/1</c> will always return an error if the
-	link points to an invalid file name.</p>
-	<p>See <seealso marker="stdlib:unicode_usage#unicode_file_names">STDLIB User's Guide</seealso> for more infomation about unicode file names. Note that this value also applies to command-line parameters and environment variables (see <seealso marker="stdlib:unicode_usage#unicode_in_environment_and_parameters">STDLIB User's Guide</seealso>).</p>
+        <p>The virtual machine works with filenames as if they are encoded
+          using UTF-8 (or some other system-specific Unicode encoding). This is
+          the default on operating systems that enforce Unicode encoding, that
+          is, Windows and MacOS X.</p>
+        <p>The <c>+fnu</c> switch can be followed by <c>w</c>, <c>i</c>, or
+          <c>e</c> to control how wrongly encoded filenames are to be
+          reported:</p>
+        <list type="bulleted">
+          <item>
+            <p><c>w</c> means that a warning is sent to the <c>error_logger</c>
+              whenever a wrongly encoded filename is "skipped" in directory
+              listings. This is the default.</p>
+          </item>
+          <item>
+            <p><c>i</c> means that those wrongly encoded filenames are silently
+              ignored.</p>
+          </item>
+          <item>
+            <p><c>e</c> means that the API function returns an error whenever a
+              wrongly encoded filename (or directory name) is encountered.</p>
+          </item>
+        </list>
+        <p>Notice that <seealso marker="kernel:file#read_link/1">
+          <c>file:read_link/1</c></seealso> always returns an error if the link
+          points to an invalid filename.</p>
+        <p>For more information about Unicode filenames, see section
+          <seealso marker="stdlib:unicode_usage#unicode_file_names">Unicode
+          Filenames</seealso> in the <c>STDLIB</c> User's Guide. Notice that
+          this value also applies to command-line parameters and environment
+          variables (see section <seealso
+          marker="stdlib:unicode_usage#unicode_in_environment_and_parameters">
+          Unicode in Enviroment and Parameters</seealso> in the <c>STDLIB</c>
+          User's Guide).</p>
       </item>
       <tag><c><![CDATA[+fna[{w|i|e}]]]></c></tag>
       <item>
         <p>Selection between <c>+fnl</c> and <c>+fnu</c> is done based
-        on the current locale settings in the OS, meaning that if you
-        have set your terminal for UTF-8 encoding, the filesystem is
-        expected to use the same encoding for file names. This is
-        default on all operating systems except MacOS X and
-        Windows.</p>
-	<p>The <c>+fna</c> switch can be followed by <c>w</c>,
-	<c>i</c>, or <c>e</c>. This will have effect if the locale
-	settings cause the behavior of <c>+fnu</c> to be selected.
-	See the description of <c>+fnu</c> above. If the locale
-	settings cause the behavior of <c>+fnl</c> to be selected,
-	then <c>w</c>, <c>i</c>, or <c>e</c> will not have any
-	effect.</p>
-	<p>See <seealso marker="stdlib:unicode_usage#unicode_file_names">STDLIB User's Guide</seealso> for more infomation about unicode file names. Note that this value also applies to command-line parameters and environment variables (see <seealso marker="stdlib:unicode_usage#unicode_in_environment_and_parameters">STDLIB User's Guide</seealso>).</p>
+          on the current locale settings in the OS. This means that if you
+          have set your terminal for UTF-8 encoding, the filesystem is
+          expected to use the same encoding for filenames. This is
+          default on all operating systems, except MacOS X and Windows.</p>
+        <p>The <c>+fna</c> switch can be followed by <c>w</c>, <c>i</c>, or
+          <c>e</c>. This has effect if the locale settings cause the behavior
+          of <c>+fnu</c> to be selected; see the description of <c>+fnu</c>
+          above. If the locale settings cause the behavior of <c>+fnl</c> to be
+          selected, then <c>w</c>, <c>i</c>, or <c>e</c> have no effect.</p>
+        <p>For more information about Unicode filenames, see section
+          <seealso marker="stdlib:unicode_usage#unicode_file_names">Unicode
+          Filenames</seealso> in the <c>STDLIB</c> User's Guide. Notice that
+          this value also applies to command-line parameters and environment
+          variables (see section <seealso
+          marker="stdlib:unicode_usage#unicode_in_environment_and_parameters">
+          Unicode in Enviroment and Parameters</seealso> in the <c>STDLIB</c>
+          User's Guide).</p>
       </item>
       <tag><c><![CDATA[+hms Size]]></c></tag>
       <item>
@@ -646,26 +704,24 @@
       <tag><marker id="+hmax"/><c><![CDATA[+hmax Size]]></c></tag>
       <item>
         <p>Sets the default maximum heap size of processes to the size
-          <c><![CDATA[Size]]></c>. If <c>+hmax</c> is not given, the default is <c>0</c>
-          which means that no maximum heap size is used.
-          For more information, see the documentation of
+          <c><![CDATA[Size]]></c>. Defaults to <c>0</c>, which means that no
+          maximum heap size is used. For more information, see
           <seealso marker="erlang#process_flag_max_heap_size">
-            <c>process_flag(max_heap_size, MaxHeapSize)</c></seealso>.</p>
+          <c>process_flag(max_heap_size, MaxHeapSize)</c></seealso>.</p>
       </item>
       <tag><marker id="+hmaxel"/><c><![CDATA[+hmaxel true|false]]></c></tag>
       <item>
-        <p>Sets whether to send an error logger message for processes that reach
-        the maximum heap size or not. If <c>+hmaxel</c> is not given, the default is <c>true</c>.
-        For more information, see the documentation of
-        <seealso marker="erlang#process_flag_max_heap_size">
+        <p>Sets whether to send an error logger message or not for processes
+          reaching the maximum heap size. Defaults to <c>true</c>.
+          For more information, see
+          <seealso marker="erlang#process_flag_max_heap_size">
           <c>process_flag(max_heap_size, MaxHeapSize)</c></seealso>.</p>
       </item>
       <tag><marker id="+hmaxk"/><c><![CDATA[+hmaxk true|false]]></c></tag>
       <item>
-        <p>Sets whether to kill processes that reach the maximum heap size or not. If
-        <c>+hmaxk</c> is not given, the default is <c>true</c>. For more information,
-	see the documentation of
-        <seealso marker="erlang#process_flag_max_heap_size">
+        <p>Sets whether to kill processes reaching the maximum heap size or not.
+          Default to <c>true</c>. For more information, see
+          <seealso marker="erlang#process_flag_max_heap_size">
           <c>process_flag(max_heap_size, MaxHeapSize)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[+hpds Size]]></c></tag>
@@ -674,304 +730,231 @@
           <c><![CDATA[Size]]></c>.</p>
       </item>
       <tag><marker id="+hmqd"/><c>+hmqd off_heap|on_heap</c></tag>
-      <item><p>
-	Sets the default value for the process flag
-	<c>message_queue_data</c>. If <c>+hmqd</c> is not
-	passed, <c>on_heap</c> will be the default. For more information,
-	see the documentation of
-        <seealso marker="erlang#process_flag_message_queue_data"><c>process_flag(message_queue_data,
-	MQD)</c></seealso>.
-      </p></item>
+      <item>
+        <p>Sets the default value for process flag <c>message_queue_data</c>.
+          Defaults to <c>on_heap</c>. If <c>+hmqd</c> is not
+	  passed, <c>on_heap</c> will be the default. For more information, see
+          <seealso marker="erlang#process_flag_message_queue_data">
+          <c>process_flag(message_queue_data, MQD)</c></seealso>.</p>
+      </item>
       <tag><c><![CDATA[+K true | false]]></c></tag>
       <item>
-        <p>Enables or disables the kernel poll functionality if
-          the emulator supports it. Default is <c><![CDATA[false]]></c> (disabled).
-          If the emulator does not support kernel poll, and
-          the <c><![CDATA[+K]]></c> flag is passed to the emulator, a warning is
+        <p>Enables or disables the kernel poll functionality if supported by
+          the emulator. Defaults to <c><![CDATA[false]]></c> (disabled).
+          If the emulator does not support kernel poll, and flag
+          <c><![CDATA[+K]]></c> is passed to the emulator, a warning is
           issued at startup.</p>
       </item>
       <tag><c><![CDATA[+l]]></c></tag>
       <item>
-        <p>Enables auto load tracing, displaying info while loading
+        <p>Enables autoload tracing, displaying information while loading
           code.</p>
       </item>
       <tag><c><![CDATA[+L]]></c></tag>
       <item>
-        <p>Don't load information about source file names and line numbers.
-	  This will save some memory, but exceptions will not contain
-	  information about the file names and line numbers.
-          </p>
+        <p>Prevents loading information about source filenames and line
+          numbers. This saves some memory, but exceptions do not contain
+          information about the filenames and line numbers.</p>
       </item>
       <tag><marker id="erts_alloc"/><c><![CDATA[+MFlag Value]]></c></tag>
       <item>
-        <p>Memory allocator specific flags, see
-          <seealso marker="erts_alloc">erts_alloc(3)</seealso> for
-          further information.</p>
-      </item>
-      <tag><marker id="+n"/><c><![CDATA[+n Behavior]]></c></tag>
-      <item>
-	<p>Control behavior of signals to ports.</p>
-	<p>As of OTP-R16 signals to ports are truly asynchronously
-	   delivered. Note that signals always have been documented as
-	   asynchronous. The underlying implementation has, however,
-	   previously delivered these signals synchronously. Correctly
-	   written Erlang programs should be able to handle this without
-	   any issues. Bugs in existing Erlang programs that make false
-	   assumptions about signals to ports may, however, be tricky to
-	   find. This switch has been introduced in order to at least
-	   make it easier to compare behaviors during a transition period.
-	   Note that <em>this flag is deprecated</em> as of its
-	   introduction, and is scheduled for removal in OTP-R17.
-	   <c>Behavior</c> should be one of the following characters:</p>
-	   <taglist>
-	     <tag><c>d</c></tag>
-	     <item>The default. Asynchronous signals. A process that sends
-	     a signal to a port may continue execution before the signal
-	     has been delivered to the port.</item>
-	     <tag><c>s</c></tag>
-	     <item>Synchronous signals. A processes that sends a signal
-	     to a port will not continue execution until the signal has
-	     been delivered. Should <em>only</em> be used for testing and
-	     debugging.</item>
-	     <tag><c>a</c></tag>
-	     <item>Asynchronous signals. As the default, but a processes
-	     that sends a signal will even more frequently continue
-	     execution before the signal has been delivered to the
-	     port. Should <em>only</em> be used for testing and
-	     debugging.</item>
-	   </taglist>
-      </item>
-      <tag><marker id="+pc"/><marker id="printable_character_range"/><c><![CDATA[+pc Range]]></c></tag>
-      <item>
-	<p>Sets the range of characters that the system will consider printable in heuristic detection of strings. This typically affects the shell, debugger and io:format functions (when ~tp is used in the format string).</p> 
-	<p>Currently two values for the <c>Range</c> are supported:</p>
-	<taglist>
-	  <tag><c>latin1</c></tag> <item>The default. Only characters
-	  in the ISO-latin-1 range can be considered printable, which means
-	  that a character with a code point &gt; 255 will never be
-	  considered printable and that lists containing such
-	  characters will be displayed as lists of integers rather
-	  than text strings by tools.</item>
-	  <tag><c>unicode</c></tag>
-	  <item>All printable Unicode characters are considered when
-	  determining if a list of integers is to be displayed in
-	  string syntax. This may give unexpected results if for
-	  example your font does not cover all Unicode
-	  characters.</item>
-	</taglist>
-	<p>Se also <seealso marker="stdlib:io#printable_range/0">
-	io:printable_range/0</seealso>.</p>
-      </item>
-      <tag><marker id="+P"/><marker id="max_processes"/><c><![CDATA[+P Number|legacy]]></c></tag>
-      <item>
-	<p>Sets the maximum number of simultaneously existing processes for this
-          system if a <c>Number</c> is passed as value. Valid range for
-	<c>Number</c> is <c>[1024-134217727]</c></p>
-	<p><em>NOTE</em>: The actual maximum chosen may be much larger than
-	the <c>Number</c> passed. Currently the runtime system often,
-	but not always, chooses a value that is a power of 2. This might,
-	however, be changed in the future. The actual value chosen can be
-	checked by calling
-	<seealso marker="erlang#system_info_process_limit">erlang:system_info(process_limit)</seealso>.</p>
-	<p>The default value is <c>262144</c></p>
-	<p>If <c>legacy</c> is passed as value, the legacy algorithm for
-	allocation of process identifiers will be used. Using the legacy
-	algorithm, identifiers will be allocated in a strictly increasing
-	fashion until largest possible identifier has been reached. Note that
-	this algorithm suffers from performance issues and can under certain
-	circumstances be extremely expensive. The legacy algoritm is deprecated,
-	and the <c>legacy</c> option is scheduled for removal in OTP-R18.</p>
-      </item>
-      <tag><marker id="+Q"/><marker id="max_ports"/><c><![CDATA[+Q Number|legacy]]></c></tag>
-      <item>
-	<p>Sets the maximum number of simultaneously existing ports for this
-          system if a Number is passed as value. Valid range for <c>Number</c>
-	is <c>[1024-134217727]</c></p>
-	<p><em>NOTE</em>: The actual maximum chosen may be much larger than
-	the actual <c>Number</c> passed. Currently the runtime system often,
-	but not always, chooses a value that is a power of 2. This might,
-	however, be changed in the future. The actual value chosen can be
-	checked by calling
-	<seealso marker="erlang#system_info_port_limit">erlang:system_info(port_limit)</seealso>.</p>
-	<p>The default value used is normally <c>65536</c>. However, if
-	the runtime system is able to determine maximum amount of file
-	descriptors that it is allowed to open and this value is larger
-	than <c>65536</c>, the chosen value will increased to a value
-	larger or equal to the maximum amount of file descriptors that
-	can be opened.</p>
-	<p>On Windows the default value is set to <c>8196</c> because the 
-	normal OS limitations are set higher than most machines can handle.</p>
-	<p>Previously the environment variable <c>ERL_MAX_PORTS</c> was used
-	for setting the maximum number of simultaneously existing ports. This
-	environment variable is deprecated, and scheduled for removal in
-	OTP-R17, but can still be used.</p>
-	<p>If <c>legacy</c> is passed as value, the legacy algorithm for
-	allocation of port identifiers will be used. Using the legacy
-	algorithm, identifiers will be allocated in a strictly increasing
-	fashion until largest possible identifier has been reached. Note that
-	this algorithm suffers from performance issues and can under certain
-	circumstances be extremely expensive. The legacy algoritm is deprecated,
-	and the <c>legacy</c> option is scheduled for removal in OTP-R18.</p>
+        <p>Memory allocator-specific flags. For more information, see
+          <seealso marker="erts_alloc"><c>erts_alloc(3)</c></seealso>.</p>
+      </item>
+      <tag><marker id="+pc"/><marker id="printable_character_range"/>
+        <c><![CDATA[+pc Range]]></c></tag>
+      <item>
+        <p>Sets the range of characters that the system considers printable in
+          heuristic detection of strings. This typically affects the shell,
+          debugger, and <c>io:format</c> functions (when <c>~tp</c> is used in
+          the format string).</p> 
+        <p>Two values are supported for <c>Range</c>:</p>
+        <taglist>
+          <tag><c>latin1</c></tag>
+          <item>The default. Only characters in the ISO Latin-1 range can be
+            considered printable. This means that a character with a code point
+            &gt; 255 is never considered printable and that lists containing
+            such characters are displayed as lists of integers rather than text
+            strings by tools.</item>
+          <tag><c>unicode</c></tag>
+          <item>All printable Unicode characters are considered when
+            determining if a list of integers is to be displayed in
+            string syntax. This can give unexpected results if, for
+            example, your font does not cover all Unicode characters.</item>
+        </taglist>
+        <p>See also <seealso marker="stdlib:io#printable_range/0">
+          <c>io:printable_range/0</c></seealso> in <c>STDLIB</c>.</p>
       </item>
       <tag><marker id="compat_rel"/><c><![CDATA[+R ReleaseNumber]]></c></tag>
       <item>
         <p>Sets the compatibility mode.</p>
-        <p>The distribution mechanism is not backwards compatible by
-          default. This flags sets the emulator in compatibility mode
+        <p>The distribution mechanism is not backward compatible by
+          default. This flag sets the emulator in compatibility mode
           with an earlier Erlang/OTP release <c><![CDATA[ReleaseNumber]]></c>.
           The release number must be in the range
           <c><![CDATA[<current release>-2..<current release>]]></c>. This
-	  limits the emulator, making it possible for it to communicate
-	  with Erlang nodes (as well as C- and Java nodes) running that
-	earlier release.</p>
-        <p>Note: Make sure all nodes (Erlang-,  C-, and Java nodes) of
-          a distributed Erlang system is of the same Erlang/OTP release,
-          or from two different Erlang/OTP releases X and Y, where
-          <em>all</em> Y nodes have compatibility mode X.</p>
+          limits the emulator, making it possible for it to communicate
+          with Erlang nodes (as well as C- and Java nodes) running that
+          earlier release.</p>
+        <note>
+          <p>Ensure that all nodes (Erlang-,  C-, and Java nodes) of
+            a distributed Erlang system is of the same Erlang/OTP release,
+            or from two different Erlang/OTP releases X and Y, where
+            <em>all</em> Y nodes have compatibility mode X.</p>
+        </note>
       </item>
       <tag><c><![CDATA[+r]]></c></tag>
       <item>
-        <p>Force ets memory block to be moved on realloc.</p>
+        <p>Forces <c>ets</c> memory block to be moved on realloc.</p>
       </item>
       <tag><marker id="+rg"/><c><![CDATA[+rg ReaderGroupsLimit]]></c></tag>
       <item>
-        <p>Limits the amount of reader groups used by read/write locks
-	   optimized for read operations in the Erlang runtime system. By
-	   default the reader groups limit equals 64.</p>
-	<p>When the amount of schedulers is less than or equal to the reader
-	   groups limit, each scheduler has its own reader group. When the
-	   amount of schedulers is larger than the reader groups limit,
-	   schedulers share reader groups. Shared reader groups degrades
-	   read lock and read unlock performance while a large amount of
-	   reader groups degrades write lock performance, so the limit is a
-	   tradeoff between performance for read operations and performance
-	   for write operations. Each reader group currently consumes 64 byte
-	   in each read/write lock. Also note that a runtime system using
-	   shared reader groups benefits from <seealso marker="#+sbt">binding
-	   schedulers to logical processors</seealso>, since the reader groups
-	   are distributed better between schedulers.</p>
-      </item>
-      <tag><marker id="+S"/><c><![CDATA[+S Schedulers:SchedulerOnline]]></c></tag>
-      <item>
-        <p>Sets the number of scheduler threads to create and scheduler
-	  threads to set online when SMP support has been enabled. The maximum for
-	  both values is 1024. If the Erlang runtime system is able to determine the
-	  amount of logical processors configured and logical processors available,
-	  <c>Schedulers</c> will default to logical processors configured, and
-	  <c>SchedulersOnline</c> will default to logical processors available;
-	  otherwise, the default values will be 1. <c>Schedulers</c> may be omitted
-	  if <c>:SchedulerOnline</c> is not and vice versa. The number of schedulers
-	  online can be changed at run time via
-	  <seealso marker="erlang#system_flag_schedulers_online">erlang:system_flag(schedulers_online, SchedulersOnline)</seealso>.
-	</p>
-	<p>If <c>Schedulers</c> or <c>SchedulersOnline</c> is specified as a
-	  negative number, the value is subtracted from the default number of
-	  logical processors configured or logical processors available, respectively.
-	</p>
-	<p>Specifying the value 0 for <c>Schedulers</c> or <c>SchedulersOnline</c>
-	  resets the number of scheduler threads or scheduler threads online respectively
-	  to its default value.
-	</p>
-        <p>This option is ignored if the emulator doesn't have
-          SMP support enabled (see the <seealso marker="#smp">-smp</seealso>
-          flag).</p>
-      </item>
-      <tag><marker id="+SP"/><c><![CDATA[+SP SchedulersPercentage:SchedulersOnlinePercentage]]></c></tag>
-      <item>
-        <p>Similar to <seealso marker="#+S">+S</seealso> but uses percentages to set the
-	  number of scheduler threads to create, based on logical processors configured,
-	  and scheduler threads to set online, based on logical processors available, when
-	  SMP support has been enabled. Specified values must be greater than 0. For example,
-	  <c>+SP 50:25</c> sets the number of scheduler threads to 50% of the logical processors
-	  configured and the number of scheduler threads online to 25% of the logical processors available.
-	  <c>SchedulersPercentage</c> may be omitted if <c>:SchedulersOnlinePercentage</c> is
-	  not and vice versa. The number of schedulers online can be changed at run time via
-	  <seealso marker="erlang#system_flag_schedulers_online">erlang:system_flag(schedulers_online, SchedulersOnline)</seealso>.
-	</p>
-	<p>This option interacts with <seealso marker="#+S">+S</seealso> settings.
-	  For example, on a system with 8 logical cores configured and 8 logical cores
-	  available, the combination of the options <c>+S 4:4 +SP 50:25</c> (in either order)
-	  results in 2 scheduler threads (50% of 4) and 1 scheduler thread online (25% of 4).
-	</p>
-        <p>This option is ignored if the emulator doesn't have
-          SMP support enabled (see the <seealso marker="#smp">-smp</seealso>
-          flag).</p>
-      </item>
-      <tag><marker id="+SDcpu"/><c><![CDATA[+SDcpu DirtyCPUSchedulers:DirtyCPUSchedulersOnline]]></c></tag>
-      <item>
-          <p>Sets the number of dirty CPU scheduler threads to create and dirty
-            CPU scheduler threads to set online when threading support has been
-            enabled. The maximum for both values is 1024, and each value is further
-            limited by the settings for normal schedulers: the number of dirty CPU
-            scheduler threads created cannot exceed the number of normal scheduler
-            threads created, and the number of dirty CPU scheduler threads online
-            cannot exceed the number of normal scheduler threads online (see the
-            <seealso marker="#+S">+S</seealso> and <seealso marker="#+SP">+SP</seealso>
-            flags for more details). By default, the number of dirty CPU scheduler
-            threads created equals the number of normal scheduler threads created,
-            and the number of dirty CPU scheduler threads online equals the number
-            of normal scheduler threads online. <c>DirtyCPUSchedulers</c> may be
-            omitted if <c>:DirtyCPUSchedulersOnline</c> is not and vice versa. The
-            number of dirty CPU schedulers online can be changed at run time via
-            <seealso marker="erlang#system_flag_dirty_cpu_schedulers_online">erlang:system_flag(dirty_cpu_schedulers_online, DirtyCPUSchedulersOnline)</seealso>.
-          </p>
-	  <p>
-	    The amount of dirty CPU schedulers is limited by the amount of
-	    normal schedulers in order to limit the effect on processes
-	    executing on ordinary schedulers. If the amount of dirty CPU
-	    schedulers was allowed to be unlimited, dirty CPU bound jobs would
-	    potentially starve normal jobs.
-	  </p>
-          <p>This option is ignored if the emulator doesn't have threading support
-            enabled. Currently, <em>this option is experimental</em> and is supported only
-            if the emulator was configured and built with support for dirty schedulers
-            enabled (it's disabled by default).
-          </p>
-      </item>
-      <tag><marker id="+SDPcpu"/><c><![CDATA[+SDPcpu DirtyCPUSchedulersPercentage:DirtyCPUSchedulersOnlinePercentage]]></c></tag>
-      <item>
-          <p>Similar to <seealso marker="#+SDcpu">+SDcpu</seealso> but uses percentages to set the
-            number of dirty CPU scheduler threads to create and number of dirty CPU scheduler threads
-            to set online when threading support has been enabled. Specified values must be greater
-            than 0. For example, <c>+SDPcpu 50:25</c> sets the number of dirty CPU scheduler threads
-            to 50% of the logical processors configured and the number of dirty CPU scheduler threads
-            online to 25% of the logical processors available. <c>DirtyCPUSchedulersPercentage</c> may
-            be omitted if <c>:DirtyCPUSchedulersOnlinePercentage</c> is not and vice versa. The
-            number of dirty CPU schedulers online can be changed at run time via
-            <seealso marker="erlang#system_flag_dirty_cpu_schedulers_online">erlang:system_flag(dirty_cpu_schedulers_online, DirtyCPUSchedulersOnline)</seealso>.
-          </p>
-          <p>This option interacts with <seealso marker="#+SDcpu">+SDcpu</seealso> settings.
-            For example, on a system with 8 logical cores configured and 8 logical cores available,
-            the combination of the options <c>+SDcpu 4:4 +SDPcpu 50:25</c> (in either order) results
-            in 2 dirty CPU scheduler threads (50% of 4) and 1 dirty CPU scheduler thread online (25% of 4).
-          </p>
-          <p>This option is ignored if the emulator doesn't have threading support
-            enabled. Currently, <em>this option is experimental</em> and is supported only
-            if the emulator was configured and built with support for dirty schedulers
-            enabled (it's disabled by default).
-          </p>
+        <p>Limits the number of reader groups used by read/write locks
+          optimized for read operations in the Erlang runtime system. By
+          default the reader groups limit is 64.</p>
+        <p>When the number of schedulers is less than or equal to the reader
+          groups limit, each scheduler has its own reader group. When the
+          number of schedulers is larger than the reader groups limit,
+          schedulers share reader groups. Shared reader groups degrade
+          read lock and read unlock performance while many
+          reader groups degrade write lock performance. So, the limit is a
+          tradeoff between performance for read operations and performance
+          for write operations. Each reader group consumes 64 byte
+          in each read/write lock.</p>
+        <p>Notice that a runtime system using shared reader groups benefits from
+          <seealso marker="#+sbt">binding schedulers to logical
+          processors</seealso>, as the reader groups are distributed better
+          between schedulers.</p>
+      </item>
+      <tag><marker id="+S"/>
+        <c><![CDATA[+S Schedulers:SchedulerOnline]]></c></tag>
+      <item>
+        <p>Sets the number of scheduler threads to create and scheduler threads
+          to set online when SMP support has been enabled. The maximum for both
+          values is 1024. If the Erlang runtime system is able to determine the
+          number of logical processors configured and logical processors
+          available, <c>Schedulers</c> defaults to logical processors
+          configured, and <c>SchedulersOnline</c> defaults to logical processors
+          available; otherwise the default values are 1. <c>Schedulers</c> can
+          be omitted if <c>:SchedulerOnline</c> is not and conversely. The
+          number of schedulers online can be changed at runtime through
+          <seealso marker="erlang#system_flag_schedulers_online">
+          <c>erlang:system_flag(schedulers_online,
+          SchedulersOnline)</c></seealso>.</p>
+        <p>If <c>Schedulers</c> or <c>SchedulersOnline</c> is specified as a
+          negative number, the value is subtracted from the default number of
+          logical processors configured or logical processors available,
+          respectively.</p>
+        <p>Specifying value <c>0</c> for <c>Schedulers</c> or
+          <c>SchedulersOnline</c> resets the number of scheduler threads or
+          scheduler threads online, respectively, to its default value.</p>
+        <p>This option is ignored if the emulator does not have SMP support
+          enabled (see flag <seealso marker="#smp"><c>-smp</c></seealso>).</p>
+      </item>
+      <tag><marker id="+SP"/><c><![CDATA[+SP
+        SchedulersPercentage:SchedulersOnlinePercentage]]></c></tag>
+      <item>
+        <p>Similar to <seealso marker="#+S"><c>+S</c></seealso> but uses
+          percentages to set the number of scheduler threads to create, based
+          on logical processors configured, and scheduler threads to set online,
+          based on logical processors available, when SMP support has been
+          enabled. Specified values must be &gt; 0. For example,
+          <c>+SP 50:25</c> sets the number of scheduler threads to 50% of the
+          logical processors configured, and the number of scheduler threads
+          online to 25% of the logical processors available.
+          <c>SchedulersPercentage</c> can be omitted if
+          <c>:SchedulersOnlinePercentage</c> is not and conversely. The number
+          of schedulers online can be changed at runtime through
+          <seealso marker="erlang#system_flag_schedulers_online">
+          <c>erlang:system_flag(schedulers_online,
+          SchedulersOnline)</c></seealso>.</p>
+        <p>This option interacts with <seealso marker="#+S"><c>+S</c></seealso>
+          settings. For example, on a system with 8 logical cores configured
+          and 8 logical cores available, the combination of the options
+          <c>+S 4:4 +SP 50:25</c> (in either order) results in 2 scheduler
+          threads (50% of 4) and 1 scheduler thread online (25% of 4).</p>
+        <p>This option is ignored if the emulator does not have SMP support
+          enabled (see flag <seealso marker="#smp"><c>-smp</c></seealso>).</p>
+      </item>
+      <tag><marker id="+SDcpu"/><c><![CDATA[+SDcpu
+        DirtyCPUSchedulers:DirtyCPUSchedulersOnline]]></c></tag>
+      <item>
+        <p>Sets the number of dirty CPU scheduler threads to create and dirty
+          CPU scheduler threads to set online when threading support has been
+          enabled. The maximum for both values is 1024, and each value is
+          further limited by the settings for normal schedulers:</p>
+        <list type="bulleted">
+          <item>The number of dirty CPU scheduler threads created cannot exceed
+            the number of normal scheduler threads created.</item>
+          <item>The number of dirty CPU scheduler threads online cannot exceed
+            the number of normal scheduler threads online.</item>
+        </list>
+        <p>For details, see the <seealso marker="#+S"><c>+S</c></seealso> and
+          <seealso marker="#+SP"><c>+SP</c></seealso>. By default, the number
+          of dirty CPU scheduler threads created equals the number of normal
+          scheduler threads created, and the number of dirty CPU scheduler
+          threads online equals the number of normal scheduler threads online.
+          <c>DirtyCPUSchedulers</c> can be omitted if
+          <c>:DirtyCPUSchedulersOnline</c> is not and conversely. The number of
+          dirty CPU schedulers online can be changed at runtime through
+          <seealso marker="erlang#system_flag_dirty_cpu_schedulers_online">
+          <c>erlang:system_flag(dirty_cpu_schedulers_online,
+          DirtyCPUSchedulersOnline)</c></seealso>.</p>
+	<p>The amount of dirty CPU schedulers is limited by the amount of
+	  normal schedulers in order to limit the effect on processes
+	  executing on ordinary schedulers. If the amount of dirty CPU
+	  schedulers was allowed to be unlimited, dirty CPU bound jobs would
+	  potentially starve normal jobs.</p>
+        <p>This option is ignored if the emulator does not have threading
+          support enabled. <em>This option is experimental</em> and
+          is supported only if the emulator was configured and built with
+          support for dirty schedulers enabled (it is disabled by default).</p>
+      </item>
+      <tag><marker id="+SDPcpu"/><c><![CDATA[+SDPcpu
+        DirtyCPUSchedulersPercentage:DirtyCPUSchedulersOnlinePercentage]]></c></tag>
+      <item>
+        <p>Similar to <seealso marker="#+SDcpu"><c>+SDcpu</c></seealso> but
+          uses percentages to set the number of dirty CPU scheduler threads to
+          create and the number of dirty CPU scheduler threads to set online
+          when threading support has been enabled. Specified values must be
+          &gt; 0. For example, <c>+SDPcpu 50:25</c> sets the number of dirty
+          CPU scheduler threads to 50% of the logical processors configured
+          and the number of dirty CPU scheduler threads online to 25% of the
+          logical processors available. <c>DirtyCPUSchedulersPercentage</c> can
+          be omitted if <c>:DirtyCPUSchedulersOnlinePercentage</c> is not and
+          conversely. The number of dirty CPU schedulers online can be changed
+          at runtime through
+          <seealso marker="erlang#system_flag_dirty_cpu_schedulers_online">
+          <c>erlang:system_flag(dirty_cpu_schedulers_online,
+          DirtyCPUSchedulersOnline)</c></seealso>.</p>
+        <p>This option interacts with <seealso
+          marker="#+SDcpu"><c>+SDcpu</c></seealso> settings. For example, on a
+          system with 8 logical cores configured and 8 logical cores available,
+          the combination of the options <c>+SDcpu 4:4 +SDPcpu 50:25</c> (in
+          either order) results in 2 dirty CPU scheduler threads (50% of 4) and
+          1 dirty CPU scheduler thread online (25% of 4).</p>
+        <p>This option is ignored if the emulator does not have threading
+          support enabled. <em>This option is experimental</em> and
+          is supported only if the emulator was configured and built with
+          support for dirty schedulers enabled (it is disabled by default).</p>
       </item>
       <tag><marker id="+SDio"/><c><![CDATA[+SDio DirtyIOSchedulers]]></c></tag>
       <item>
-          <p>Sets the number of dirty I/O scheduler threads to create when threading
-            support has been enabled. The valid range is 0-1024. By default, the number
-            of dirty I/O scheduler threads created is 10, same as the default number of
-            threads in the <seealso marker="#async_thread_pool_size">async thread pool
-            </seealso>.
-          </p>
-	  <p>
-	    The amount of dirty IO schedulers is not limited by the amount of
-	    normal schedulers <seealso marker="#+SDcpu">like the amount of
-	    dirty CPU schedulers</seealso>. This since only I/O bound work is
-	    expected to execute on dirty I/O schedulers. If the user should schedule CPU
-	    bound jobs on dirty I/O schedulers, these jobs might starve ordinary
-	    jobs executing on ordinary schedulers.
-	  </p>
-          <p>This option is ignored if the emulator doesn't have threading support
-            enabled. Currently, <em>this option is experimental</em> and is supported only
-            if the emulator was configured and built with support for dirty schedulers
-            enabled (it's disabled by default).
-          </p>
+        <p>Sets the number of dirty I/O scheduler threads to create when
+          threading support has been enabled. Valid range is 0-1024. By
+          default, the number of dirty I/O scheduler threads created is 10,
+          same as the default number of threads in the <seealso
+          marker="#async_thread_pool_size">async thread pool</seealso>.</p>
+	<p>The amount of dirty IO schedulers is not limited by the amount of
+	  normal schedulers <seealso marker="#+SDcpu">like the amount of
+	  dirty CPU schedulers</seealso>. This since only I/O bound work is
+	  expected to execute on dirty I/O schedulers. If the user should schedule CPU
+	  bound jobs on dirty I/O schedulers, these jobs might starve ordinary
+	  jobs executing on ordinary schedulers.</p>
+        <p>This option is ignored if the emulator does not have threading
+          support enabled. <em>This option is experimental</em> and
+          is supported only if the emulator was configured and built with
+          support for dirty schedulers enabled (it is disabled by default).</p>
       </item>
       <tag><c><![CDATA[+sFlag Value]]></c></tag>
       <item>
@@ -979,238 +962,237 @@
         <taglist>
           <tag><marker id="+sbt"/><c>+sbt BindType</c></tag>
           <item>
-            <p>Set scheduler bind type.</p>
-	    <p>Schedulers can also be bound using the
-	    <seealso marker="#+stbt">+stbt</seealso> flag. The only difference
-	    between these two flags is how the following errors are handled:</p>
-	    <list>
-	      <item>Binding of schedulers is not supported on the specific
-	      platform.</item>
-	      <item>No available CPU topology. That is the runtime system
-	      was not able to automatically detected the CPU topology, and
-	      no <seealso marker="#+sct">user defined CPU topology</seealso>
-	      was set.</item>
-	    </list>
-	    <p>If any of these errors occur when <c>+sbt</c> has been passed,
-	    the runtime system will print an error message, and refuse to
-	    start. If any of these errors occur when <c>+stbt</c> has been
-	    passed, the runtime system will silently ignore the error, and
-	    start up using unbound schedulers.</p>
-	    <p>Currently valid <c>BindType</c>s:
-	    </p>
-	    <taglist>
-	      <tag><c>u</c></tag>
-              <item>
-                <p><c>unbound</c> - Schedulers will not be bound to logical
-		processors, i.e., the operating system decides where the
-		scheduler threads execute, and when to migrate them. This is
-		the default.</p>
+            <p>Sets scheduler bind type.</p>
+            <p>Schedulers can also be bound using flag
+              <seealso marker="#+stbt"><c>+stbt</c></seealso>. The only
+              difference between these two flags is how the following errors
+              are handled:</p>
+            <list type="bulleted">
+              <item>Binding of schedulers is not supported on the specific
+                platform.</item>
+              <item>No available CPU topology. That is, the runtime system was
+                not able to detect the CPU topology automatically, and no
+                <seealso marker="#+sct">user-defined CPU topology</seealso>
+                was set.</item>
+            </list>
+            <p>If any of these errors occur when <c>+sbt</c> has been passed,
+              the runtime system prints an error message, and refuses to
+              start. If any of these errors occur when <c>+stbt</c> has been
+              passed, the runtime system silently ignores the error, and
+              start up using unbound schedulers.</p>
+            <p>Valid <c>BindType</c>s:</p>
+            <taglist>
+              <tag><c>u</c></tag>
+              <item><c>unbound</c> - Schedulers are not bound to logical
+                processors, that is, the operating system decides where the
+                scheduler threads execute, and when to migrate them. This is
+                the default.
               </item>
-	      <tag><c>ns</c></tag>
-              <item>
-                <p><c>no_spread</c> - Schedulers with close scheduler
-		identifiers will be bound as close as possible in hardware.</p>
+              <tag><c>ns</c></tag>
+              <item><c>no_spread</c> - Schedulers with close scheduler
+                identifiers are bound as close as possible in hardware.
               </item>
-	      <tag><c>ts</c></tag>
-              <item>
-                <p><c>thread_spread</c> - Thread refers to hardware threads
-		(e.g. Intel's hyper-threads). Schedulers with low scheduler
-		identifiers, will be bound to the first hardware thread of
-		each core, then schedulers with higher scheduler identifiers
-		will be bound to the second hardware thread of each core,
-		etc.</p>
+              <tag><c>ts</c></tag>
+              <item><c>thread_spread</c> - Thread refers to hardware threads
+                (such as Intel's hyper-threads). Schedulers with low scheduler
+                identifiers, are bound to the first hardware thread of
+                each core, then schedulers with higher scheduler identifiers
+                are bound to the second hardware thread of each core,and so on.
               </item>
-	      <tag><c>ps</c></tag>
-              <item>
-                <p><c>processor_spread</c> - Schedulers will be spread like
-		<c>thread_spread</c>, but also over physical processor chips.</p>
+              <tag><c>ps</c></tag>
+              <item><c>processor_spread</c> - Schedulers are spread like
+                <c>thread_spread</c>, but also over physical processor chips.
               </item>
-	      <tag><c>s</c></tag>
-              <item>
-                <p><c>spread</c> - Schedulers will be spread as much as
-		possible.</p>
+              <tag><c>s</c></tag>
+              <item><c>spread</c> - Schedulers are spread as much as possible.
               </item>
-	      <tag><c>nnts</c></tag>
-              <item>
-                <p><c>no_node_thread_spread</c> - Like <c>thread_spread</c>,
-		but if multiple NUMA (Non-Uniform Memory Access) nodes exists,
-		schedulers will be spread over one NUMA node at a time,
-		i.e., all logical processors of one NUMA node will be bound
-		to schedulers in sequence.</p>
+              <tag><c>nnts</c></tag>
+              <item><c>no_node_thread_spread</c> - Like <c>thread_spread</c>,
+                but if multiple Non-Uniform Memory Access (NUMA) nodes exist,
+                schedulers are spread over one NUMA node at a time,
+                that is, all logical processors of one NUMA node are bound
+                to schedulers in sequence.
               </item>
-	      <tag><c>nnps</c></tag>
-              <item>
-                <p><c>no_node_processor_spread</c> - Like
-		<c>processor_spread</c>, but if multiple NUMA nodes exists,
-		schedulers will be spread over one NUMA node at a time, i.e.,
-		all logical processors of one NUMA node will be bound to
-		schedulers in sequence.</p>
+              <tag><c>nnps</c></tag>
+              <item><c>no_node_processor_spread</c> - Like
+                <c>processor_spread</c>, but if multiple NUMA nodes exist,
+                schedulers are spread over one NUMA node at a time, that is,
+                all logical processors of one NUMA node are bound to
+                schedulers in sequence.
               </item>
-	      <tag><c>tnnps</c></tag>
-              <item>
-                <p><c>thread_no_node_processor_spread</c> - A combination of
-		<c>thread_spread</c>, and <c>no_node_processor_spread</c>.
-		Schedulers will be spread over hardware threads across NUMA
-		nodes, but schedulers will only be spread over processors
-		internally in one NUMA node at a time.</p>
+              <tag><c>tnnps</c></tag>
+              <item><c>thread_no_node_processor_spread</c> - A combination of
+                <c>thread_spread</c>, and <c>no_node_processor_spread</c>.
+                Schedulers are spread over hardware threads across NUMA
+                nodes, but schedulers are only spread over processors
+                internally in one NUMA node at a time.
               </item>
-	      <tag><c>db</c></tag>
-              <item>
-                <p><c>default_bind</c> - Binds schedulers the default way.
-		Currently the default is <c>thread_no_node_processor_spread</c>
-		(which might change in the future).</p>
+              <tag><c>db</c></tag>
+              <item><c>default_bind</c> - Binds schedulers the default way.
+                Defaults to <c>thread_no_node_processor_spread</c>
+                (which can change in the future).
               </item>
-	    </taglist>
-	    <p>Binding of schedulers is currently only supported on newer
-	       Linux, Solaris, FreeBSD, and Windows systems.</p>
-	    <p>If no CPU topology is available when the <c>+sbt</c> flag
-	       is processed and <c>BindType</c> is any other type than
-	       <c>u</c>, the runtime system will fail to start. CPU
-	       topology can be defined using the
-	       <seealso marker="#+sct">+sct</seealso> flag. Note
-	       that the <c>+sct</c> flag may have to be passed before the
-	       <c>+sbt</c> flag on the command line (in case no CPU topology
-	       has been automatically detected).</p>
-            <p>The runtime system will by default <em>not</em> bind schedulers
-	       to logical processors.
-	    </p>
-	    <p><em>NOTE:</em> If the Erlang runtime system is the only operating system
-	       process that binds threads to logical processors, this
-	       improves the performance of the runtime system. However,
-	       if other operating system processes (as for example
-	       another Erlang runtime system) also bind threads to
-	       logical processors, there might be a performance penalty
-	       instead. In some cases this performance penalty might be
-	       severe. If this is the case, you are advised to not
-	       bind the schedulers.</p>
+            </taglist>
+            <p>Binding of schedulers is only supported on newer
+              Linux, Solaris, FreeBSD, and Windows systems.</p>
+            <p>If no CPU topology is available when flag <c>+sbt</c>
+              is processed and <c>BindType</c> is any other type than
+              <c>u</c>, the runtime system fails to start. CPU
+              topology can be defined using flag
+              <seealso marker="#+sct"><c>+sct</c></seealso>. Notice
+              that flag <c>+sct</c> can have to be passed before flag
+              <c>+sbt</c> on the command line (if no CPU topology
+              has been automatically detected).</p>
+            <p>The runtime system does by default <em>not</em> bind schedulers
+              to logical processors.</p>
+            <note>
+              <p>If the Erlang runtime system is the only operating system
+                process that binds threads to logical processors, this
+                improves the performance of the runtime system. However,
+                if other operating system processes (for example
+                another Erlang runtime system) also bind threads to
+                logical processors, there can be a performance penalty
+                instead. This performance penalty can sometimes be
+                severe. If so, you are advised not to
+                bind the schedulers.</p>
+            </note>
             <p>How schedulers are bound matters. For example, in
-	       situations when there are fewer running processes than
-	       schedulers online, the runtime system tries to migrate
-	       processes to schedulers with low scheduler identifiers.
-	       The more the schedulers are spread over the hardware,
-	       the more resources will be available to the runtime
-	       system in such situations.
-	    </p>
-	    <p>
-	       <em>NOTE:</em> If a scheduler fails to bind, this
-	       will often be silently ignored. This since it isn't always
-	       possible to verify valid logical processor identifiers. If
-	       an error is reported, it will be reported to the
-	       <c>error_logger</c>. If you want to verify that the
-	       schedulers actually have bound as requested, call
-	       <seealso marker="erlang#system_info_scheduler_bindings">erlang:system_info(scheduler_bindings)</seealso>.
-	    </p>
+              situations when there are fewer running processes than
+              schedulers online, the runtime system tries to migrate
+              processes to schedulers with low scheduler identifiers.
+              The more the schedulers are spread over the hardware,
+              the more resources are available to the runtime
+              system in such situations.</p>
+            <note>
+              <p>If a scheduler fails to bind, this is
+                often silently ignored, as it is not always
+                possible to verify valid logical processor identifiers. If
+                an error is reported, it is reported to the
+                <c>error_logger</c>. If you want to verify that the
+                schedulers have bound as requested, call
+                <seealso marker="erlang#system_info_scheduler_bindings">
+                <c>erlang:system_info(scheduler_bindings)</c></seealso>.</p>
+            </note>
           </item>
-	  <tag><marker id="+sbwt"/><c>+sbwt none|very_short|short|medium|long|very_long</c></tag>
-	  <item>
-             <p>Set scheduler busy wait threshold. Default is <c>medium</c>.
-	        The threshold determines how long schedulers should busy
-		wait when running out of work before going to sleep.
-	     </p>
-             <p><em>NOTE:</em> This flag may be removed or changed at any time
-	        without prior notice.
-	     </p>
-	  </item>
-          <tag><marker id="+scl"/><c>+scl true|false</c></tag>
+          <tag><marker id="+sbwt"/>
+            <c>+sbwt none|very_short|short|medium|long|very_long</c></tag>
+          <item>
+            <p>Sets scheduler busy wait threshold. Defaults to <c>medium</c>.
+              The threshold determines how long schedulers are to busy
+              wait when running out of work before going to sleep.</p>
+            <note>
+              <p>This flag can be removed or changed at any time
+                without prior notice.</p>
+            </note>
+          </item>
+<tag><marker id="+scl"/><c>+scl true|false</c></tag>
           <item>
-	    <p>Enable or disable scheduler compaction of load. By default
-	    scheduler compaction of load is enabled. When enabled, load
-	    balancing will strive for a load distribution which causes
-	    as many scheduler threads as possible to be fully loaded (i.e.,
-	    not run out of work). This is accomplished by migrating load
-	    (e.g. runnable processes) into a smaller set of schedulers
-	    when schedulers frequently run out of work. When disabled,
-	    the frequency with which schedulers run out of work will
-	    not be taken into account by the load balancing logic.
-	    <br/>&nbsp;&nbsp;<c>+scl false</c> is similar to
-	    <seealso marker="#+sub">+sub true</seealso> with the difference
-	    that <c>+sub true</c> also will balance scheduler utilization
-	    between schedulers.
-	    </p>
+            <p>Enables or disables scheduler compaction of load. By default
+              scheduler compaction of load is enabled. When enabled, load
+              balancing strives for a load distribution, which causes
+              as many scheduler threads as possible to be fully loaded (that is,
+              not run out of work). This is accomplished by migrating load
+              (for example, runnable processes) into a smaller set of schedulers
+              when schedulers frequently run out of work. When disabled,
+              the frequency with which schedulers run out of work is
+              not taken into account by the load balancing logic.</p>
+            <p><c>+scl false</c> is similar to
+              <seealso marker="#+sub"><c>+sub true</c></seealso>, but
+              <c>+sub true</c> also balances scheduler utilization
+              between schedulers.</p>
           </item>
           <tag><marker id="+sct"/><c>+sct CpuTopology</c></tag>
           <item>
             <list type="bulleted">
-              <item><c><![CDATA[<Id> = integer(); when 0 =< <Id> =< 65535]]></c></item>
+              <item><c><![CDATA[<Id> = integer(); when 0 =< <Id> =< 65535]]></c>
+              </item>
               <item><c><![CDATA[<IdRange> = <Id>-<Id>]]></c></item>
               <item><c><![CDATA[<IdOrIdRange> = <Id> | <IdRange>]]></c></item>
-              <item><c><![CDATA[<IdList> = <IdOrIdRange>,<IdOrIdRange> | <IdOrIdRange>]]></c></item>
+              <item><c><![CDATA[<IdList> = <IdOrIdRange>,<IdOrIdRange> |
+                <IdOrIdRange>]]></c></item>
               <item><c><![CDATA[<LogicalIds> = L<IdList>]]></c></item>
-              <item><c><![CDATA[<ThreadIds> = T<IdList> | t<IdList>]]></c></item>
+              <item><c><![CDATA[<ThreadIds> = T<IdList> | t<IdList>]]></c>
+              </item>
               <item><c><![CDATA[<CoreIds> = C<IdList> | c<IdList>]]></c></item>
-              <item><c><![CDATA[<ProcessorIds> = P<IdList> | p<IdList>]]></c></item>
+              <item><c><![CDATA[<ProcessorIds> = P<IdList> | p<IdList>]]></c>
+              </item>
               <item><c><![CDATA[<NodeIds> = N<IdList> | n<IdList>]]></c></item>
-              <item><c><![CDATA[<IdDefs> = <LogicalIds><ThreadIds><CoreIds><ProcessorIds><NodeIds> | <LogicalIds><ThreadIds><CoreIds><NodeIds><ProcessorIds>]]></c></item>
-              <item><c><![CDATA[CpuTopology = <IdDefs>:<IdDefs> | <IdDefs>]]></c></item>
+              <item><c><![CDATA[<IdDefs> =
+                <LogicalIds><ThreadIds><CoreIds><ProcessorIds><NodeIds> |
+                <LogicalIds><ThreadIds><CoreIds><NodeIds><ProcessorIds>]]></c>
+              </item>
+              <item><c><![CDATA[CpuTopology = <IdDefs>:<IdDefs> |
+                <IdDefs>]]></c></item>
+            </list>
+            <p>Sets a user-defined CPU topology. The user-defined
+              CPU topology overrides any automatically detected
+              CPU topology. The CPU topology is used when
+              <seealso marker="#+sbt">binding schedulers to logical
+              processors</seealso>.</p>
+            <p>Uppercase letters signify real identifiers and lowercase
+	      letters signify fake identifiers only used for description
+              of the topology. Identifiers passed as real identifiers can
+              be used by the runtime system when trying to access specific
+              hardware; if they are incorrect the behavior is
+              undefined. Faked logical CPU identifiers are not accepted,
+              as there is no point in defining the CPU topology without
+              real logical CPU identifiers. Thread, core, processor, and
+              node identifiers can be omitted. If omitted, the thread ID
+              defaults to <c>t0</c>, the core ID defaults to <c>c0</c>,
+              the processor ID defaults to <c>p0</c>, and the node ID is
+              left undefined. Either each logical processor must 
+              belong to only one NUMA node, or no logical
+              processors must belong to any NUMA nodes.</p>
+            <p>Both increasing and decreasing <c><![CDATA[<IdRange>]]></c>s
+              are allowed.</p>
+            <p>NUMA node identifiers are system wide. That is, each NUMA
+              node on the system must have a unique identifier. Processor
+              identifiers are also system wide. Core identifiers are
+              processor wide. Thread identifiers are core wide.</p>
+            <p>The order of the identifier types implies the hierarchy of the
+              CPU topology. The valid orders are as follows:</p>
+            <list type="bulleted">
+              <item>
+                <p><c><![CDATA[<LogicalIds><ThreadIds><CoreIds><ProcessorIds><NodeIds>]]></c>,
+                  that is, thread is part of a core that is part of a processor,
+                  which is part of a NUMA node.</p>
+              </item>
+              <item>
+                <p><c><![CDATA[<LogicalIds><ThreadIds><CoreIds><NodeIds><ProcessorIds>]]></c>,
+                  that is, thread is part of a core that is part of a NUMA node,
+                  which is part of a processor.</p>
+              </item>
+            </list>
+            <p>A CPU topology can consist of both processor external, and
+              processor internal NUMA nodes as long as each logical processor
+              belongs to only one NUMA node. If
+              <c><![CDATA[<ProcessorIds>]]></c> is omitted, its default position
+              is before <c><![CDATA[<NodeIds>]]></c>. That is, the default is
+              processor external NUMA nodes.</p>
+            <p>If a list of identifiers is used in an
+              <c><![CDATA[<IdDefs>]]></c>:</p>
+            <list type="bulleted">
+              <item><c><![CDATA[<LogicalIds>]]></c> must be a list
+                of identifiers.</item>
+              <item>At least one other identifier type besides
+                <c><![CDATA[<LogicalIds>]]></c> must also have a
+                list of identifiers.</item>
+              <item>All lists of identifiers must produce the
+                same number of identifiers.</item>
             </list>
-            <p>Set a user defined CPU topology. The user defined
-	       CPU topology will override any automatically detected
-	       CPU topology. The CPU topology is used when
-	       <seealso marker="#+sbt">binding schedulers to logical
-	       processors</seealso>.
-	    </p>
-            <p>Upper-case letters signify real identifiers and lower-case
-	       letters signify fake identifiers only used for description
-	       of the topology. Identifiers passed as real identifiers may
-	       be used by the runtime system when trying to access specific
-	       hardware and if they are not correct the behavior is
-	       undefined. Faked logical CPU identifiers are not accepted
-	       since there is no point in defining the CPU topology without
-	       real logical CPU identifiers. Thread, core, processor, and
-	       node identifiers may be left out. If left out, thread id
-	       defaults to <c>t0</c>, core id defaults to <c>c0</c>,
-	       processor id defaults to <c>p0</c>, and node id will
-	       be left undefined. Either each logical processor must 
-	       belong to one and only one NUMA node, or no logical
-	       processors must belong to any NUMA nodes. 
-	     </p>
-	     <p>Both increasing and decreasing <c><![CDATA[<IdRange>]]></c>s
-	        are allowed.</p>
-	     <p>NUMA node identifiers are system wide. That is, each NUMA
-	        node on the system have to have a unique identifier. Processor
-		identifiers are also system wide. Core identifiers are
-		processor wide. Thread identifiers are core wide.</p>
-	     <p>The order of the identifier types imply the hierarchy of the
-	        CPU topology. Valid orders are either
-		<c><![CDATA[<LogicalIds><ThreadIds><CoreIds><ProcessorIds><NodeIds>]]></c>,
-		or
-		<c><![CDATA[<LogicalIds><ThreadIds><CoreIds><NodeIds><ProcessorIds>]]></c>.
-		That is, thread is part of a core which is part of a processor
-		which is part of a NUMA node, or thread is part of a core which
-		is part of a NUMA node which is part of a processor. A cpu
-		topology can consist of both processor external, and processor
-		internal NUMA nodes as long as each logical processor belongs
-		to one and only one NUMA node. If <c><![CDATA[<ProcessorIds>]]></c>
-		is left out, its default position will be before
-		<c><![CDATA[<NodeIds>]]></c>. That is, the default is
-		processor external NUMA nodes.
-	     </p>
-	     <p>If a list of identifiers is used in an
-	        <c><![CDATA[<IdDefs>]]></c>:</p>
-             <list type="bulleted">
-	       <item><c><![CDATA[<LogicalIds>]]></c> have to be a list
-	             of identifiers.</item>
-	       <item>At least one other identifier type apart from
-		     <c><![CDATA[<LogicalIds>]]></c> also have to have a
-		     list of identifiers.</item>
-	       <item>All lists of identifiers have to produce the
-	             same amount of identifiers.</item>
-             </list>
-	     <p>A simple example. A single quad core processor may be
-	        described this way:</p>
+            <p>A simple example. A single quad core processor can be
+              described as follows:</p>
 <pre>
 % <input>erl +sct L0-3c0-3</input>
 1> <input>erlang:system_info(cpu_topology).</input>
 [{processor,[{core,{logical,0}},
              {core,{logical,1}},
              {core,{logical,2}},
-             {core,{logical,3}}]}]
-</pre>
-	     <p>A little more complicated example. Two quad core
-	        processors. Each processor in its own NUMA node.
-		The ordering of logical processors is a little weird.
-		This in order to give a better example of identifier
-		lists:</p>
+             {core,{logical,3}}]}]</pre>
+            <p>A more complicated example with two quad core
+              processors, each processor in its own NUMA node.
+              The ordering of logical processors is a bit weird.
+              This to give a better example of identifier lists:</p>
 <pre>
 % <input>erl +sct L0-1,3-2c0-3p0N0:L7,4,6-5c0-3p1N1</input>
 1> <input>erlang:system_info(cpu_topology).</input>
@@ -1221,239 +1203,247 @@
  {node,[{processor,[{core,{logical,7}},
                     {core,{logical,4}},
                     {core,{logical,6}},
-                    {core,{logical,5}}]}]}]
-</pre>
-	     <p>As long as real identifiers are correct it is okay
-	        to pass a CPU topology that is not a correct
-		description of the CPU topology. When used with
-		care this can actually be very useful. This in
-		order to trick the emulator to bind its schedulers
-		as you want. For example, if you want to run multiple
-		Erlang runtime systems on the same machine, you
-		want to reduce the amount of schedulers used and
-		manipulate the CPU topology so that they bind to
-		different logical CPUs. An example, with two Erlang
-		runtime systems on a quad core machine:</p>
+                    {core,{logical,5}}]}]}]</pre>
+            <p>As long as real identifiers are correct, it is OK
+              to pass a CPU topology that is not a correct
+              description of the CPU topology. When used with
+              care this can be very useful. This
+              to trick the emulator to bind its schedulers
+              as you want. For example, if you want to run multiple
+              Erlang runtime systems on the same machine, you
+              want to reduce the number of schedulers used and
+              manipulate the CPU topology so that they bind to
+              different logical CPUs. An example, with two Erlang
+              runtime systems on a quad core machine:</p>
 <pre>
 % <input>erl +sct L0-3c0-3 +sbt db +S3:2 -detached -noinput -noshell -sname one</input>
-% <input>erl +sct L3-0c0-3 +sbt db +S3:2 -detached -noinput -noshell -sname two</input>
-</pre>
-	     <p>In this example each runtime system have two
-	        schedulers each online, and all schedulers online
-		will run on different cores. If we change to one
-		scheduler online on one runtime system, and three
-		schedulers online on the other, all schedulers
-		online will still run on different cores.</p>
-	     <p>Note that a faked CPU topology that does not reflect
-	        how the real CPU topology looks like is likely to
-		decrease the performance of the runtime system.</p>
-	    <p>For more information, see
-	    <seealso marker="erlang#system_info_cpu_topology">erlang:system_info(cpu_topology)</seealso>.</p>
+% <input>erl +sct L3-0c0-3 +sbt db +S3:2 -detached -noinput -noshell -sname two</input></pre>
+            <p>In this example, each runtime system have two
+              schedulers each online, and all schedulers online
+              will run on different cores. If we change to one
+              scheduler online on one runtime system, and three
+              schedulers online on the other, all schedulers
+              online will still run on different cores.</p>
+            <p>Notice that a faked CPU topology that does not reflect
+              how the real CPU topology looks like is likely to
+              decrease the performance of the runtime system.</p>
+            <p>For more information, see
+              <seealso marker="erlang#system_info_cpu_topology">
+              <c>erlang:system_info(cpu_topology)</c></seealso>.</p>
           </item>
           <tag><marker id="+secio"/><c>+secio true|false</c></tag>
           <item>
-	    <p>Enable or disable eager check I/O scheduling. The default
-	    is currently <c>true</c>. The default was changed from <c>false</c>
-	    to <c>true</c> as of erts version 7.0. The behaviour before this
-	    flag was introduced corresponds to <c>+secio false</c>.</p>
-	    <p>The flag effects when schedulers will check for I/O
-	    operations possible to execute, and when such I/O operations
-	    will execute. As the name of the parameter implies,
-	    schedulers will be more eager to check for I/O when
-	    <c>true</c> is passed. This however also implies that
-	    execution of outstanding I/O operation will not be
-	    prioritized to the same extent as when <c>false</c> is
-	    passed.</p>
-	    <p><seealso marker="erlang#system_info_eager_check_io"><c>erlang:system_info(eager_check_io)</c></seealso>
-	    returns the value of this parameter used when starting the VM.</p>
+            <p>Enables or disables eager check I/O scheduling. Defaults
+              to <c>true</c>. The default was changed from <c>false</c>
+              as from <c>ERTS</c> 7.0. The behavior before this
+              flag was introduced corresponds to <c>+secio false</c>.</p>
+            <p>The flag effects when schedulers will check for I/O
+              operations possible to execute, and when such I/O operations
+              will execute. As the parameter name implies,
+              schedulers are more eager to check for I/O when
+              <c>true</c> is passed. This, however, also implies that
+              execution of outstanding I/O operation is not
+              prioritized to the same extent as when <c>false</c> is
+              passed.</p>
+            <p><seealso marker="erlang#system_info_eager_check_io">
+              <c>erlang:system_info(eager_check_io)</c></seealso>
+              returns the value of this parameter used when starting
+              the virtual machine.</p>
           </item>
           <tag><marker id="+sfwi"/><c>+sfwi Interval</c></tag>
           <item>
-            <p>Set scheduler forced wakeup interval. All run queues will
-	    be scanned each <c>Interval</c> milliseconds. While there are
-	    sleeping schedulers in the system, one scheduler will be woken
-	    for each non-empty run queue found. An <c>Interval</c> of zero
-	    disables this feature, which also is the default.
-	    </p>
-	    <p>This feature has been introduced as a temporary workaround
-	    for long-executing native code, and native code that does not
-	    bump reductions properly in OTP. When these bugs have be fixed
-	    the <c>+sfwi</c> flag will be removed.
-	    </p>
-	  </item>
+            <p>Sets scheduler-forced wakeup interval. All run queues are
+              scanned each <c>Interval</c> milliseconds. While there are
+              sleeping schedulers in the system, one scheduler is woken
+              for each non-empty run queue found. <c>Interval</c> default
+              to <c>0</c>, meaning this feature is disabled.</p>
+            <note>
+              <p>This feature has been introduced as a temporary workaround
+                for long-executing native code, and native code that does not
+                bump reductions properly in OTP. When these bugs have be fixed,
+                this flag will be removed.</p>
+            </note>
+          </item>
+          <tag><marker id="+spp"/><c>+spp Bool</c></tag>
+          <item>
+            <p>Sets default scheduler hint for port parallelism. If set to
+              <c>true</c>, the virtual machine schedules port tasks when it
+              improves parallelism in the system. If set to <c>false</c>, the
+              virtual machine tries to perform port tasks immediately,
+              improving latency at the expense of parallelism. Default to
+              <c>false</c>. The default used can be inspected in runtime by
+              calling <seealso marker="erlang#system_info_port_parallelism">
+              <c>erlang:system_info(port_parallelism)</c></seealso>.
+              The default can be overridden on port creation by passing option
+              <seealso marker="erlang#open_port_parallelism">
+              <c>parallelism</c></seealso> to
+              <seealso marker="erlang#open_port/2">
+              <c>erlang:open_port/2</c></seealso></p>.
+          </item>
+          <tag><marker id="sched_thread_stack_size"/>
+            <c><![CDATA[+sss size]]></c></tag>
+          <item>
+            <p>Suggested stack size, in kilowords, for scheduler threads.
+              Valid range is 4-8192 kilowords. The default stack size is
+              OS-dependent.</p>
+          </item>
           <tag><marker id="+stbt"/><c>+stbt BindType</c></tag>
           <item>
-            <p>Try to set scheduler bind type. The same as the
-	    <seealso marker="#+sbt">+sbt</seealso> flag with the exception of
-	    how some errors are handled. For more information, see the
-	    documentation of the <seealso marker="#+sbt">+sbt</seealso> flag.
-	    </p>
-	  </item>
+            <p>Tries to set the scheduler bind type. The same as flag
+              <seealso marker="#+sbt"><c>+sbt</c></seealso> except
+              how some errors are handled. For more information, see
+              <seealso marker="#+sbt"><c>+sbt</c></seealso>.</p>
+          </item>
           <tag><marker id="+sub"/><c>+sub true|false</c></tag>
           <item>
-	    <p>Enable or disable
-	    <seealso marker="erts:erlang#statistics_scheduler_wall_time">scheduler
-	    utilization</seealso> balancing of load. By default scheduler
-	    utilization balancing is disabled and instead scheduler
-	    compaction of load is enabled which will strive for a load
-	    distribution which causes as many scheduler threads as possible
-	    to be fully loaded (i.e., not run out of work). When scheduler
-	    utilization balancing is enabled the system will instead try to
-	    balance scheduler utilization between schedulers. That is,
-	    strive for equal scheduler utilization on all schedulers.
-	    <br/>&nbsp;&nbsp;&nbsp;<c>+sub true</c> is only supported on
-      systems where the runtime system detects and uses a monotonically
-	    increasing high resolution clock. On other systems, the runtime
-	    system will fail to start.
-	    <br/>&nbsp;&nbsp;&nbsp;<c>+sub true</c> implies
-	    <seealso marker="#+scl">+scl false</seealso>. The difference
-	    between <c>+sub true</c> and <c>+scl false</c> is that
-	    <c>+scl false</c> will not try to balance the scheduler
-	    utilization.
-	    </p>
+            <p>Enables or disables
+              <seealso marker="erts:erlang#statistics_scheduler_wall_time">
+              scheduler utilization</seealso> balancing of load. By default
+              scheduler utilization balancing is disabled and instead scheduler
+              compaction of load is enabled, which strives for a load
+              distribution that causes as many scheduler threads as possible
+              to be fully loaded (that is, not run out of work). When scheduler
+              utilization balancing is enabled, the system instead tries to
+              balance scheduler utilization between schedulers. That is,
+              strive for equal scheduler utilization on all schedulers.</p>
+            <p><c>+sub true</c> is only supported on systems where the runtime
+              system detects and uses a monotonically increasing high-resolution
+              clock. On other systems, the runtime system fails to start.</p>
+            <p><c>+sub true</c> implies <seealso marker="#+scl">
+              <c>+scl false</c></seealso>. The difference between
+              <c>+sub true</c> and <c>+scl false</c> is that <c>+scl false</c>
+              does not try to balance the scheduler utilization.</p>
           </item>
-	  <tag><marker id="+swct"/><c>+swct very_eager|eager|medium|lazy|very_lazy</c></tag>
-	  <item>
-             <p>
-	       Set scheduler wake cleanup threshold. Default is <c>medium</c>.
-	       This flag controls how eager schedulers should be requesting
-	       wake up due to certain cleanup operations. When a lazy setting
-	       is used, more outstanding cleanup operations can be left undone
-	       while a scheduler is idling. When an eager setting is used,
-	       schedulers will more frequently be woken, potentially increasing
-	       CPU-utilization.
-	     </p>
-             <p><em>NOTE:</em> This flag may be removed or changed at any time without prior notice.
-	     </p>
-	  </item>
-	  <tag><marker id="+sws"/><c>+sws default|legacy</c></tag>
-	  <item>
-             <p>
-	       Set scheduler wakeup strategy. Default strategy changed in erts-5.10/OTP-R16A. This strategy was previously known as <c>proposal</c> in OTP-R15. The <c>legacy</c> strategy was used as default from R13 up to and including R15.
-	     </p>
-             <p><em>NOTE:</em> This flag may be removed or changed at any time without prior notice.
-	     </p>
-	  </item>
-	  <tag><marker id="+swt"/><c>+swt very_low|low|medium|high|very_high</c></tag>
-	  <item>
-             <p>Set scheduler wakeup threshold. Default is <c>medium</c>.
-	        The threshold determines when to wake up sleeping schedulers
-		when more work than can be handled by currently awake schedulers
-		exist. A low threshold will cause earlier wakeups, and a high
-		threshold will cause later wakeups. Early wakeups will
-		distribute work over multiple schedulers faster, but work will
-		more easily bounce between schedulers.
-	     </p>
-             <p><em>NOTE:</em> This flag may be removed or changed at any time
-	        without prior notice.
-	     </p>
-	  </item>
-          <tag><marker id="+spp"/><c>+spp Bool</c></tag>
+          <tag><marker id="+swct"/>
+            <c>+swct very_eager|eager|medium|lazy|very_lazy</c></tag>
           <item>
-	    <p>Set default scheduler hint for port parallelism. If set to
-	    <c>true</c>, the VM will schedule port tasks when doing so will
-	    improve parallelism in the system. If set to <c>false</c>, the VM
-	    will try to perform port tasks immediately, improving latency at the
-	    expense of parallelism. If this flag has not been passed, the
-	    default scheduler hint for port parallelism is currently
-	    <c>false</c>. The default used can be inspected in runtime by
-	    calling <seealso
-	    marker="erlang#system_info_port_parallelism">erlang:system_info(port_parallelism)</seealso>.
-	    The default can be overriden on port creation by passing the
-	    <seealso marker="erlang#open_port_parallelism">parallelism</seealso>
-	    option to <seealso
-	    marker="erlang#open_port/2">open_port/2</seealso></p>.
-	  </item>
-	  <tag><marker id="sched_thread_stack_size"/><c><![CDATA[+sss size]]></c></tag>
-	  <item>
-	    <p>Suggested stack size, in kilowords, for scheduler threads.
-            Valid range is 4-8192 kilowords. The default stack size
-            is OS dependent.</p>
-	  </item>
+            <p>Sets scheduler wake cleanup threshold. Defaults to <c>medium</c>.
+              Controls how eager schedulers are to be requesting
+              wakeup because of certain cleanup operations. When a lazy setting
+              is used, more outstanding cleanup operations can be left undone
+              while a scheduler is idling. When an eager setting is used,
+              schedulers are more frequently woken, potentially increasing
+              CPU-utilization.</p>
+            <note>
+              <p>This flag can be removed or changed at any time without prior
+                notice.</p>
+            </note>
+          </item>
+          <tag><marker id="+sws"/><c>+sws default|legacy</c></tag>
+          <item>
+            <p>Sets scheduler wakeup strategy. Default strategy changed in
+              <c>ERTS</c> 5.10 (Erlang/OTP R16A). This strategy was known as
+              <c>proposal</c> in Erlang/OTP R15. The <c>legacy</c> strategy
+              was used as default from R13 up to and including R15.</p>
+            <note>
+              <p>This flag can be removed or changed at any time without prior
+                notice.</p>
+            </note>
+          </item>
+          <tag><marker id="+swt"/>
+            <c>+swt very_low|low|medium|high|very_high</c></tag>
+          <item>
+            <p>Sets scheduler wakeup threshold. Defaults to <c>medium</c>.
+              The threshold determines when to wake up sleeping schedulers
+              when more work than can be handled by currently awake schedulers
+              exists. A low threshold causes earlier wakeups, and a high
+              threshold causes later wakeups. Early wakeups distribute work
+              over multiple schedulers faster, but work does more easily bounce
+              between schedulers.</p>
+            <note>
+              <p>This flag can be removed or changed at any time without prior
+                notice.</p>
+            </note>
+          </item>
         </taglist>
       </item>
       <tag><marker id="+t"/><c><![CDATA[+t size]]></c></tag>
       <item>
-        <p>Set the maximum number of atoms the VM can handle. Default is 1048576.</p>
+        <p>Sets the maximum number of atoms the virtual machine can handle.
+          Defaults to 1,048,576.</p>
       </item>
       <tag><marker id="+T"/><c><![CDATA[+T Level]]></c></tag>
       <item>
-        <p>Enables modified timing and sets the modified timing level.
-          Currently valid range is 0-9. The timing of the runtime system
-          will change. A high level usually means a greater change than
-          a low level. Changing the timing can be very useful for finding
-          timing related bugs.</p>
-        <p>Currently, modified timing affects the following:</p>
+        <p>Enables modified timing and sets the modified timing level. Valid
+          range is 0-9. The timing of the runtime system is changed. A high
+          level usually means a greater change than a low level. Changing the
+          timing can be very useful for finding timing-related bugs.</p>
+        <p>Modified timing affects the following:</p>
         <taglist>
           <tag>Process spawning</tag>
-          <item>
-            <p>A process calling <c><![CDATA[spawn]]></c>, <c><![CDATA[spawn_link]]></c>,
-              <c><![CDATA[spawn_monitor]]></c>, or <c><![CDATA[spawn_opt]]></c> will be scheduled
-              out immediately after completing the call. When higher modified
-              timing levels are used, the caller will also sleep for a while
-              after being scheduled out.</p>
+          <item>A process calling <c><![CDATA[spawn]]></c>,
+            <c><![CDATA[spawn_link]]></c>, <c><![CDATA[spawn_monitor]]></c>,
+            or <c><![CDATA[spawn_opt]]></c> is scheduled out immediately
+            after completing the call. When higher modified timing levels are
+            used, the caller also sleeps for a while after it is scheduled out.
           </item>
           <tag>Context reductions</tag>
-          <item>The amount of reductions a process is a allowed to
-           use before being scheduled out is increased or reduced.</item>
+          <item>The number of reductions a process is allowed to use before it
+            is scheduled out is increased or reduced.
+          </item>
           <tag>Input reductions</tag>
-          <item>The amount of reductions performed before checking I/O
-           is increased or reduced.</item>
+          <item>The number of reductions performed before checking I/O is
+            increased or reduced.
+          </item>
         </taglist>
-        <p><em>NOTE:</em> Performance will suffer when modified timing
-          is enabled. This flag is <em>only</em> intended for testing and
-          debugging. Also note that <c><![CDATA[return_to]]></c> and <c><![CDATA[return_from]]></c>
-          trace messages will be lost when tracing on the spawn BIFs. This
-          flag may be removed or changed at any time without prior notice.</p>
-      </item>
-      <tag><c><![CDATA[+V]]></c></tag>
-      <item>
-        <p>Makes the emulator print out its version number.</p>
+        <note>
+          <p>Performance suffers when modified timing is enabled. This flag is
+            <em>only</em> intended for testing and debugging.</p>
+          <p><c><![CDATA[return_to]]></c> and <c><![CDATA[return_from]]></c>
+            trace messages are lost when tracing on the spawn BIFs.</p>
+          <p>This flag can be removed or changed at any time without prior
+            notice.</p>
+        </note>
       </item>
       <tag><c><![CDATA[+v]]></c></tag>
       <item>
         <p>Verbose.</p>
       </item>
+      <tag><c><![CDATA[+V]]></c></tag>
+      <item>
+        <p>Makes the emulator print its version number.</p>
+      </item>
       <tag><c><![CDATA[+W w | i | e]]></c></tag>
       <item>
-        <p>Sets the mapping of warning messages for <c><![CDATA[error_logger]]></c>.
-          Messages sent to the error logger using one of the warning
-          routines can be mapped either to errors (<c><![CDATA[+W e]]></c>),
-          warnings (<c><![CDATA[+W w]]></c>), or info reports
-          (<c><![CDATA[+W i]]></c>). The default is warnings.
+        <p>Sets the mapping of warning messages for
+          <c><![CDATA[error_logger]]></c>. Messages sent to the error logger
+          using one of the warning routines can be mapped to errors
+          (<c><![CDATA[+W e]]></c>), warnings (<c><![CDATA[+W w]]></c>), or
+          information reports (<c><![CDATA[+W i]]></c>). Defaults to warnings.
           The current mapping can be retrieved using
-          <c><![CDATA[error_logger:warning_map/0]]></c>. See
-          <seealso marker="kernel:error_logger#warning_map/0">error_logger(3)</seealso>
-          for further information.</p>
+          <c><![CDATA[error_logger:warning_map/0]]></c>. For more information,
+          see <seealso marker="kernel:error_logger#warning_map/0">
+          <c>error_logger:warning_map/0</c></seealso> in <c>Kernel</c>.</p>
       </item>
       <tag><c><![CDATA[+zFlag Value]]></c></tag>
       <item>
-        <p>Miscellaneous flags.</p>
+        <p>Miscellaneous flags:</p>
         <taglist>
           <tag><marker id="+zdbbl"/><c>+zdbbl size</c></tag>
           <item>
-            <p>Set the distribution buffer busy limit
-	    (<seealso marker="erlang#system_info_dist_buf_busy_limit">dist_buf_busy_limit</seealso>)
-	    in kilobytes. Valid range is 1-2097151. Default is 1024.</p>
-            <p>A larger buffer limit will allow processes to buffer
-            more outgoing messages over the distribution. When the
-            buffer limit has been reached, sending processes will be
-            suspended until the buffer size has shrunk. The buffer
-            limit is per distribution channel. A higher limit will
-            give lower latency and higher throughput at the expense
-            of higher memory usage.</p>
+            <p>Sets the distribution buffer busy limit
+              (<seealso marker="erlang#system_info_dist_buf_busy_limit">
+              <c>dist_buf_busy_limit</c></seealso>)
+              in kilobytes. Valid range is 1-2097151. Defaults to 1024.</p>
+            <p>A larger buffer limit allows processes to buffer
+              more outgoing messages over the distribution. When the
+              buffer limit has been reached, sending processes will be
+              suspended until the buffer size has shrunk. The buffer
+              limit is per distribution channel. A higher limit
+              gives lower latency and higher throughput at the expense
+              of higher memory use.</p>
           </item>
           <tag><marker id="+zdntgc"/><c>+zdntgc time</c></tag>
           <item>
-            <p>Set the delayed node table garbage collection time
-	    (<seealso marker="erlang#system_info_delayed_node_table_gc">delayed_node_table_gc</seealso>)
-	    in seconds. Valid values are either <c>infinity</c> or
-	    an integer in the range [0-100000000]. Default is 60.</p>
-            <p>Node table entries that are not referred will linger
-	    in the table for at least the amount of time that this
-	    parameter determines. The lingering prevents repeated
-	    deletions and insertions in the tables from occurring.
-	    </p>
+            <p>Sets the delayed node table garbage collection time
+              (<seealso marker="erlang#system_info_delayed_node_table_gc">
+              <c>delayed_node_table_gc</c></seealso>)
+              in seconds. Valid values are either <c>infinity</c> or
+              an integer in the range 0-100000000. Defaults to 60.</p>
+            <p>Node table entries that are not referred linger
+              in the table for at least the amount of time that this
+              parameter determines. The lingering prevents repeated
+              deletions and insertions in the tables from occurring.</p>
           </item>
         </taglist>
       </item>
@@ -1462,104 +1452,95 @@
 
   <section>
     <marker id="environment_variables"></marker>
-    <title>Environment variables</title>
+    <title>Environment Variables</title>
     <taglist>
       <tag><c><![CDATA[ERL_CRASH_DUMP]]></c></tag>
       <item>
         <p>If the emulator needs to write a crash dump, the value of this
-          variable will be the file name of the crash dump file.
-          If the variable is not set, the name of the crash dump file will
-          be <c><![CDATA[erl_crash.dump]]></c> in the current directory.</p>
+          variable is the filename of the crash dump file.
+          If the variable is not set, the name of the crash dump file is
+          <c><![CDATA[erl_crash.dump]]></c> in the current directory.</p>
       </item>
       <tag><c><![CDATA[ERL_CRASH_DUMP_NICE]]></c></tag>
       <item>
-        <p><em>Unix systems</em>: If the emulator needs to write a crash dump,
-          it will use the value of this variable to set the nice value
-          for the process, thus lowering its priority. The allowable range is
-          1 through 39 (higher values will be replaced with 39). The highest
-          value, 39, will give the process the lowest priority.</p>
+      <p><em>Unix systems</em>: If the emulator needs to write a crash dump,
+        it uses the value of this variable to set the nice value
+        for the process, thus lowering its priority. Valid range is
+        1-39 (higher values are replaced with 39). The highest
+        value, 39, gives the process the lowest priority.</p>
       </item>
       <tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS]]></c></tag>
       <item>
-        <p><em>Unix systems</em>: This variable gives the number of seconds that
-          the emulator will be allowed to spend writing a crash dump. When
-          the given number of seconds have elapsed, the emulator will be
-          terminated by a SIGALRM signal.</p>
-
-	  <p> If the environment variable is <em>not</em> set or it is set to zero seconds, <c><![CDATA[ERL_CRASH_DUMP_SECONDS=0]]></c>,
-		  the runtime system will not even attempt to write the crash dump file. It will just terminate.
-	  </p>
-	  <p> If the environment variable is set to negative valie, e.g. <c><![CDATA[ERL_CRASH_DUMP_SECONDS=-1]]></c>,
-		  the runtime system will wait indefinitely for the crash dump file to be written.
-	  </p>
-	  <p> This environment variable is used in conjuction with
-		  <seealso marker="kernel:heart"><c>heart</c></seealso> if <c>heart</c> is running:
-	  </p>
-	  <taglist>
-		  <tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS=0]]></c></tag>
-		  <item><p>
-				  Suppresses the writing a crash dump file entirely,
-				  thus rebooting the runtime system immediately.
-				  This is the same as not setting the environment variable.
-			  </p>
-		  </item>
-		  <tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS=-1]]></c></tag>
-		  <item><p>Setting the environment variable to a negative value will cause the
-				  termination of the runtime system to wait until the crash dump file
-				  has been completly written.
-			  </p>
-		  </item>
-		  <tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS=S]]></c></tag>
-		  <item><p>
-				  Will wait for <c>S</c> seconds to complete the crash dump file and
-				  then terminate the runtime system.
-			  </p>
-		  </item>
-	  </taglist>
+        <p><em>Unix systems</em>: This variable gives the number of seconds
+          that the emulator is allowed to spend writing a crash dump. When the
+          given number of seconds have elapsed, the emulator is terminated by a
+          <c>SIGALRM</c> signal.</p>
+        <p>If the variable is <em>not</em> set or set to <c>0</c> seconds
+          (<c><![CDATA[ERL_CRASH_DUMP_SECONDS=0]]></c>), the runtime system does
+          not even attempt to write the crash dump file. It only terminates.</p>
+        <p>If the variable is set to negative value, such as
+          <c><![CDATA[ERL_CRASH_DUMP_SECONDS=-1]]></c>, the runtime system
+          waits indefinitely for the crash dump file to be written.</p>
+        <p>This variable is used with <seealso marker="kernel:heart">
+          <c>kernel:heart</c></seealso> if <c>heart</c> is running:</p>
+        <taglist>
+          <tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS=0]]></c></tag>
+          <item>Suppresses the writing a crash dump file entirely, thus
+            rebooting the runtime system immediately. This is the same as not
+            setting the environment variable.
+          </item>
+          <tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS=-1]]></c></tag>
+          <item>Setting the environment variable to a negative value causes the
+            termination of the runtime system to wait until the crash dump file
+            has been completly written.
+          </item>
+          <tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS=S]]></c></tag>
+          <item>Waits for <c>S</c> seconds to complete the crash dump file and
+            then terminates the runtime system.
+          </item>
+        </taglist>
       </item>
       <tag><marker id="ERL_AFLAGS"/><c><![CDATA[ERL_AFLAGS]]></c></tag>
       <item>
-        <p>The content of this environment variable will be added to the
-          beginning of the command line for <c><![CDATA[erl]]></c>.</p>
-        <p>The <c><![CDATA[-extra]]></c> flag is treated specially. Its scope ends
-          at the end of the environment variable content. Arguments
-          following an <c><![CDATA[-extra]]></c> flag are moved on the command line into
-          the <c><![CDATA[-extra]]></c> section, i.e. the end of the command line
-          following after an <c><![CDATA[-extra]]></c> flag.</p>
-      </item>
-      <tag><marker id="ERL_ZFLAGS"/><c><![CDATA[ERL_ZFLAGS]]></c> and <marker id="ERL_FLAGS"/><c><![CDATA[ERL_FLAGS]]></c></tag>
-      <item>
-        <p>The content of these environment variables will be added to the
-          end of the command line for <c><![CDATA[erl]]></c>.</p>
-        <p>The <c><![CDATA[-extra]]></c> flag is treated specially. Its scope ends
-          at the end of the environment variable content. Arguments
-          following an <c><![CDATA[-extra]]></c> flag are moved on the command line into
-          the <c><![CDATA[-extra]]></c> section, i.e. the end of the command line
-          following after an <c><![CDATA[-extra]]></c> flag.</p>
+        <p>The content of this variable is added to the beginning of the
+          command line for <c><![CDATA[erl]]></c>.</p>
+        <p>Flag <c><![CDATA[-extra]]></c> is treated in a special way. Its
+          scope ends at the end of the environment variable content. Arguments
+          following an <c><![CDATA[-extra]]></c> flag are moved on the command
+          line into section <c><![CDATA[-extra]]></c>, that is, the end of the
+          command line following an <c><![CDATA[-extra]]></c> flag.</p>
+      </item>
+      <tag><marker id="ERL_ZFLAGS"/><c><![CDATA[ERL_ZFLAGS]]></c> and
+        <marker id="ERL_FLAGS"/><c><![CDATA[ERL_FLAGS]]></c></tag>
+      <item>
+        <p>The content of these variables are added to the end of the command
+          line for <c><![CDATA[erl]]></c>.</p>
+        <p>Flag <c><![CDATA[-extra]]></c> is treated in a special way. Its
+          scope ends at the end of the environment variable content. Arguments
+          following an <c><![CDATA[-extra]]></c> flag are moved on the command
+          line into section <c><![CDATA[-extra]]></c>, that is, the end of the
+          command line following an <c><![CDATA[-extra]]></c> flag.</p>
       </item>
       <tag><c><![CDATA[ERL_LIBS]]></c></tag>
       <item>
-        <p>This environment variable contains a list of additional library
-	  directories that the code server will search for applications and
-	  add to the code path.
-  	  See <seealso marker="kernel:code">code(3)</seealso>.</p>
+        <p>Contains a list of additional library directories that the code
+          server searches for applications and adds to the code path; see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </item>
       <tag><c><![CDATA[ERL_EPMD_ADDRESS]]></c></tag>
       <item>
-        <p>This environment variable may be set to a comma-separated
-          list of IP addresses, in which case the
-          <seealso marker="epmd">epmd</seealso> daemon
-          will listen only on the specified address(es) and on the
-          loopback address (which is implicitly added to the list if it
-          has not been specified).</p>
+        <p>Can be set to a comma-separated list of IP addresses, in which case
+          the <seealso marker="epmd"><c>epmd</c></seealso> daemon listens only
+          on the specified address(es) and on the loopback address (which is
+          implicitly added to the list if it has not been specified).</p>
       </item>
       <tag><c><![CDATA[ERL_EPMD_PORT]]></c></tag>
       <item>
-        <p>This environment variable can contain the port number to use when
-          communicating with <seealso marker="epmd">epmd</seealso>. The default
-          port will work fine in most cases. A different port can be specified
+        <p>Can contain the port number to use when communicating with
+          <seealso marker="epmd"><c>epmd</c></seealso>. The default port works
+          fine in most cases. A different port can be specified
           to allow nodes of independent clusters to co-exist on the same host.
-          All nodes in a cluster must use the same epmd port number.</p>
+          All nodes in a cluster must use the same <c>epmd</c> port number.</p>
       </item>
     </taglist>
   </section>
@@ -1567,59 +1548,64 @@
   <section>
     <marker id="configuration"></marker>
     <title>Configuration</title>
-    <p>The standard Erlang/OTP system can be re-configured to change the default
-       behavior on start-up.</p>
+    <p>The standard Erlang/OTP system can be reconfigured to change the default
+      behavior on startup.</p>
     <taglist>
-       <tag>The .erlang Start-up File</tag>
-       <item>
-         <p>When Erlang/OTP is started, the system searches for a file named .erlang
-            in the directory where Erlang/OTP is started. If not found, the user's home
-            directory is searched for an .erlang file.</p>
-         <p>If an .erlang file is found, it is assumed to contain valid Erlang expressions.
-            These expressions are evaluated as if they were input to the shell.</p>
-         <p>A typical .erlang file contains a set of search paths, for example:</p>
-    <code type="none"><![CDATA[
-        io:format("executing user profile in HOME/.erlang\n",[]).
-        code:add_path("/home/calvin/test/ebin").
-        code:add_path("/home/hobbes/bigappl-1.2/ebin").
-        io:format(".erlang rc finished\n",[]).
-    ]]></code>
-       </item>
-       <tag>user_default and shell_default</tag>
-       <item>
-         <p>Functions in the shell which are not prefixed by a module name are assumed
-           to be functional objects (Funs), built-in functions (BIFs), or belong to the
-           module user_default or shell_default.</p>
-         <p>To include private shell commands, define them in a module user_default and
-           add the following argument as the first line in the .erlang file.</p>
+      <tag>The <c>.erlang</c> startup file</tag>
+      <item>
+        <p>When Erlang/OTP is started, the system searches for a file named
+          <c>.erlang</c> in the directory where Erlang/OTP is started. If not
+          found, the user's home directory is searched for an <c>.erlang</c>
+          file.</p>
+        <p>If an <c>.erlang</c> file is found, it is assumed to contain valid
+          Erlang expressions. These expressions are evaluated as if they were
+          input to the shell.</p>
+        <p>A typical <c>.erlang</c> file contains a set of search paths, for
+          example:</p>
     <code type="none"><![CDATA[
-         code:load_abs("..../user_default").
-    ]]></code>
-       </item>
-       <tag>erl</tag>
-       <item>
-         <p>If the contents of .erlang are changed and a private version of
-           user_default is defined, it is possible to customize the Erlang/OTP environment.
-           More powerful changes can be made by supplying command line arguments in the
-           start-up script erl. Refer to erl(1) and <seealso marker="init">init(3)</seealso>
-           for further information.</p>
-       </item>
+io:format("executing user profile in HOME/.erlang\n",[]).
+code:add_path("/home/calvin/test/ebin").
+code:add_path("/home/hobbes/bigappl-1.2/ebin").
+io:format(".erlang rc finished\n",[]).    ]]></code>
+      </item>
+      <tag>user_default and shell_default</tag>
+      <item>
+        <p>Functions in the shell that are not prefixed by a module name are
+          assumed to be functional objects (funs), built-in functions (BIFs),
+          or belong to the module <c>user_default</c> or
+          <c>shell_default</c>.</p>
+        <p>To include private shell commands, define them in a module
+          <c>user_default</c> and add the following argument as the first line
+          in the <c>.erlang</c> file:</p>
+        <code type="none"><![CDATA[
+code:load_abs("..../user_default").    ]]></code>
+      </item>
+      <tag>erl</tag>
+      <item>
+        <p>If the contents of <c>.erlang</c> are changed and a private version
+          of <c>user_default</c> is defined, the Erlang/OTP environment can be
+          customized. More powerful changes can be made by supplying
+          command-line arguments in the startup script <c>erl</c>. For more
+          information, see <seealso marker="init"><c>init(3)</c></seealso>.</p>
+      </item>
     </taglist>
   </section>
 
-   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="init">init(3)</seealso>,
-      <seealso marker="erl_prim_loader">erl_prim_loader(3)</seealso>,
-      <seealso marker="kernel:erl_boot_server">erl_boot_server(3)</seealso>,
-      <seealso marker="kernel:code">code(3)</seealso>,
-      <seealso marker="kernel:application">application(3)</seealso>,
-      <seealso marker="kernel:heart">heart(3)</seealso>,
-      <seealso marker="kernel:net_kernel">net_kernel(3)</seealso>,
-      <seealso marker="kernel:auth">auth(3)</seealso>,
-      <seealso marker="tools:make">make(3)</seealso>,
-      <seealso marker="epmd">epmd(1)</seealso>,
-      <seealso marker="erts_alloc">erts_alloc(3)</seealso></p>
+  <section>
+    <title>See Also</title>
+    <p><seealso marker="epmd"><c>epmd(1)</c></seealso>,
+      <seealso marker="erl_prim_loader"><c>erl_prim_loader(3)</c></seealso>,
+      <seealso marker="erts_alloc"><c>erts_alloc(3)</c></seealso>,
+      <seealso marker="init"><c>init(3)</c></seealso>,
+      <seealso marker="kernel:application">
+        <c>kernel:application(3)</c></seealso>,
+      <seealso marker="kernel:auth"><c>kernel:auth(3)</c></seealso>,
+      <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>,
+      <seealso marker="kernel:erl_boot_server">
+        <c>kernel:erl_boot_server(3)</c></seealso>,
+      <seealso marker="kernel:heart"><c>kernel:heart(3)</c></seealso>,
+      <seealso marker="kernel:net_kernel"><c>kernel:net_kernel(3)</c></seealso>,
+      <seealso marker="tools:make"><c>tools:make(3)</c></seealso></p>
   </section>
 </comref>
 
diff --git a/erts/doc/src/erl_dist_protocol.xml b/erts/doc/src/erl_dist_protocol.xml
index 25f601a235..f1979ac23f 100644
--- a/erts/doc/src/erl_dist_protocol.xml
+++ b/erts/doc/src/erl_dist_protocol.xml
@@ -32,1061 +32,989 @@
     <file>erl_dist_protocol.xml</file>
   </header>
 
-<p>
-The description here is far from complete and will therefore be further
-refined in upcoming releases.
-
-The protocols both from Erlang nodes towards
-EPMD (Erlang Port Mapper Daemon) and between Erlang nodes, however, are
-stable since many years.
-</p>
-
-<p>The distribution protocol can be divided into four (4) parts:</p>
-<list>
-  <item>
-    <p>
-      1. Low level socket connection.
-    </p>
-  </item>
-  <item>
-    2. Handshake, interchange node name and authenticate.
-  </item>
-  <item>
-    3. Authentication (done by net_kernel).
-  </item>
-  <item>
-    4. Connected. 
-  </item>
-</list>
-<p>
-  A node fetches the Port number of another node through the EPMD (at the
-  other host) in order to initiate a connection request.
-</p>
-<p>
-For each host where a distributed Erlang node is running there should also
-be an EPMD running. The EPMD can be started explicitly or automatically
-as a result of the Erlang node startup.
-</p>
-<p>
-By default EPMD listens on port 4369.
-</p>
-<p>
-  3 and 4 are performed at the same level but the net_kernel disconnects the
-  other node if it communicates using an invalid cookie (after one (1) second).
-</p>
-
-<p>The integers in all multi-byte fields are in big-endian order.</p>
+  <p>This description is far from complete. It will be updated if the
+    protocol is updated. However, the protocols, both from Erlang
+    nodes to the Erlang Port Mapper Daemon (EPMD) and between Erlang nodes
+    are stable since many years.</p>
+
+  <p>The distribution protocol can be divided into four parts:</p>
+
+  <list type="bulleted">
+    <item>
+      <p>Low-level socket connection (1)</p>
+    </item>
+    <item>
+      <p>Handshake, interchange node name, and authenticate (2)</p>
+    </item>
+    <item>
+      <p>Authentication (done by <seealso marker="kernel:net_kernel">
+        <c>kernel:net_kernel</c></seealso>) (3)</p>
+    </item>
+    <item>
+      <p>Connected (4)</p> 
+    </item>
+  </list>
+
+  <p>A node fetches the port number of another node through the EPMD (at the
+    other host) to initiate a connection request.</p>
+
+  <p>For each host, where a distributed Erlang node is running, also an EPMD
+    is to be running. The EPMD can be started explicitly or automatically
+    as a result of the Erlang node startup.</p>
+
+  <p>By default the EPMD listens on port 4369.</p>
+
+  <p>(3) and (4) above are performed at the same level but the <c>net_kernel</c>
+    disconnects the other node if it communicates using an invalid cookie (after
+    1 second).</p>
+
+  <p>The integers in all multibyte fields are in big-endian order.</p>
 
   <section>
     <title>EPMD Protocol</title>
-    <p>
-      The requests served by the EPMD (Erlang Port Mapper Daemon) are 
-      summarized in the figure below.
-    </p>
-
-      <image file="erl_ext_fig.gif">
-	<icaption>
-	  Summary of EPMD requests. 
-	</icaption>
-      </image>
-      <p>
-	Each request <c>*_REQ</c> is preceded by a two-byte length field. 
-	Thus, the overall request format is:
-      </p>
+    <p>The requests served by the EPMD are summarized in the following
+      figure.</p>
+
+    <image file="erl_ext_fig.gif">
+      <icaption>Summary of EPMD Requests</icaption>
+    </image>
+
+    <p>Each request <c>*_REQ</c> is preceded by a 2 byte length field.
+      Thus, the overall request format is as follows:</p>
+
+    <table align="left">
+      <row>
+        <cell align="center">2</cell>
+        <cell align="center">n</cell>
+      </row>
+      <row>
+        <cell align="center"><c>Length</c></cell>
+        <cell align="center"><c>Request</c></cell>
+      </row>
+      <tcaption>Request Format</tcaption>
+    </table>
+
+    <section>
+      <title>Register a Node in EPMD</title>
+      <p>When a distributed node is started it registers itself in the EPMD.
+        The message <c>ALIVE2_REQ</c> described below is sent from the node to
+        the EPMD. The response from the EPMD is <c>ALIVE2_RESP</c>.</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">2</cell>
+          <cell align="center">1</cell>
+          <cell align="center">1</cell>
+          <cell align="center">2</cell>
+          <cell align="center">2</cell>
+          <cell align="center">2</cell>
+          <cell align="center">Nlen</cell>
+          <cell align="center">2</cell>
+          <cell align="center">Elen</cell>
+        </row>
+        <row>
+          <cell align="center"><c>120</c></cell>
+          <cell align="center"><c>PortNo</c></cell>
+          <cell align="center"><c>NodeType</c></cell>
+          <cell align="center"><c>Protocol</c></cell>
+          <cell align="center"><c>HighestVersion</c></cell>
+          <cell align="center"><c>LowestVersion</c></cell>
+          <cell align="center"><c>Nlen</c></cell>
+          <cell align="center"><c>NodeName</c></cell>
+          <cell align="center"><c>Elen</c></cell>
+          <cell align="center"><c>Extra</c></cell>
+        </row>
+        <tcaption>ALIVE2_REQ (120)</tcaption>
+      </table>
+
+      <taglist>
+        <tag><c>PortNo</c></tag>
+        <item>
+          <p>The port number on which the node accept connection requests.</p>
+        </item>
+        <tag><c>NodeType</c></tag>
+        <item>
+          <p>77 = normal Erlang node, 72 = hidden node (C-node), ...</p>
+        </item>
+        <tag><c>Protocol</c></tag>
+        <item>
+          <p>0 = TCP/IPv4, ...</p>
+        </item>
+        <tag><c>HighestVersion</c></tag>
+        <item>
+          <p>The highest distribution version that this node can handle.
+            The value in Erlang/OTP R6B and later is 5.</p>
+        </item>
+        <tag><c>LowestVersion</c></tag>
+        <item>
+          <p>The lowest distribution version that this node can handle.
+            The value in Erlang/OTP R6B and later is 5.</p>
+        </item>
+        <tag><c>Nlen</c></tag>
+        <item>
+          <p>The length (in bytes) of field <c>NodeName</c>.</p>
+        </item>
+        <tag><c>NodeName</c></tag>
+        <item>
+          <p>The node name as an UTF-8 encoded string of <c>Nlen</c> bytes.</p>
+        </item>
+        <tag><c>Elen</c></tag>
+        <item>
+          <p>The length of field <c>Extra</c>.</p>
+        </item>
+        <tag><c>Extra</c></tag>
+        <item>
+          <p>Extra field of <c>Elen</c> bytes.</p>
+        </item>
+      </taglist>
+
+      <p>The connection created to the EPMD must be kept as long as the
+        node is a distributed node. When the connection is closed,
+        the node is automatically unregistered from the EPMD.</p>
+
+      <p>The response message <c>ALIVE2_RESP</c> is as follows:</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">1</cell>
+          <cell align="center">2</cell>
+        </row>
+        <row>
+          <cell align="center"><c>121</c></cell>
+          <cell align="center"><c>Result</c></cell>
+          <cell align="center"><c>Creation</c></cell>
+        </row>
+        <tcaption>ALIVE2_RESP (121)</tcaption>
+      </table>
+
+      <p>Result = 0 -> ok, result &gt; 0 -> error.</p>
+    </section>
+
+    <section>
+      <title>Unregister a Node from EPMD</title>
+      <p>A node unregisters itself from the EPMD by closing the TCP
+        connection to EPMD established when the node was registered.</p>
+    </section>
+
+    <section>
+      <title>Get the Distribution Port of Another Node</title>
+      <p>When one node wants to connect to another node it starts with
+        a <c>PORT_PLEASE2_REQ</c> request to the EPMD on the host where the
+        node resides to get the distribution port that the node listens to.</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">N</cell>
+        </row>
+        <row>
+          <cell align="center"><c>122</c></cell>
+          <cell align="center"><c>NodeName</c></cell>
+        </row>
+        <tcaption>PORT_PLEASE2_REQ (122)</tcaption>
+      </table>
+
+      <p>where N = <c>Length</c> - 1.</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">1</cell>
+        </row>
+        <row>
+          <cell align="center"><c>119</c></cell>
+          <cell align="center"><c>Result</c></cell>
+        </row>
+        <tcaption>PORT2_RESP (119) Response Indicating Error, Result &gt; 0
+        </tcaption>
+      </table>
+
+      <p>or</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">1</cell>
+          <cell align="center">2</cell>
+          <cell align="center">1</cell>
+          <cell align="center">1</cell>
+          <cell align="center">2</cell>
+          <cell align="center">2</cell>
+          <cell align="center">2</cell>
+          <cell align="center">Nlen</cell>
+          <cell align="center">2</cell>
+          <cell align="center">Elen</cell>
+        </row>
+        <row>
+          <cell align="center"><c>119</c></cell>
+          <cell align="center"><c>Result</c></cell>
+          <cell align="center"><c>PortNo</c></cell>
+          <cell align="center"><c>NodeType</c></cell>
+          <cell align="center"><c>Protocol</c></cell>
+          <cell align="center"><c>HighestVersion</c></cell>
+          <cell align="center"><c>LowestVersion</c></cell>
+          <cell align="center"><c>Nlen</c></cell>
+          <cell align="center"><c>NodeName</c></cell>
+          <cell align="center"><c>Elen</c></cell>
+          <cell align="center">><c>Extra</c></cell>
+        </row>
+        <tcaption>PORT2_RESP, Result = 0</tcaption>
+      </table>
+
+      <p>If <c>Result</c> &gt; 0, the packet only consists of
+        <c>[119, Result]</c>.</p>
+
+      <p>The EPMD closes the socket when it has sent the information.</p>
+    </section>
+
+    <section>
+      <title>Get All Registered Names from EPMD</title>
+      <p>This request is used through the Erlang function
+        <seealso marker="kernel:net_adm#names/1,2">
+        <c>net_adm:names/1,2</c></seealso>. A TCP connection is opened
+        to the  EPMD and this request is sent.</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+        </row>
+        <row>
+          <cell align="center"><c>110</c></cell>
+        </row>
+        <tcaption>NAMES_REQ (110)</tcaption>
+      </table>	
+
+      <p>The response for a <c>NAMES_REQ</c> is as follows:</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">4</cell>
+          <cell align="center">&nbsp;</cell>
+        </row>
+        <row>
+          <cell align="center"><c>EPMDPortNo</c></cell>
+          <cell align="center"><c>NodeInfo*</c></cell>
+        </row>
+        <tcaption>NAMES_RESP</tcaption>
+      </table>
+
+      <p><c>NodeInfo</c> is a string written for each active node.
+        When all <c>NodeInfo</c> has been written the connection is
+        closed by the EPMD.</p>
+
+      <p><c>NodeInfo</c> is, as expressed in Erlang:</p>
+
+      <code>
+io:format("name ~ts at port ~p~n", [NodeName, Port]).</code>
+    </section>
+
+    <section>
+      <title>Dump All Data from EPMD</title>
+      <p>This request is not really used, it is to be regarded as a debug
+        feature.</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+        </row>
+        <row>
+          <cell align="center"><c>100</c></cell>
+        </row>
+        <tcaption>DUMP_REQ</tcaption>
+      </table>
+
+      <p>The response for a <c>DUMP_REQ</c> is as follows:</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">4</cell>
+          <cell align="center">&nbsp;</cell>
+        </row>
+        <row>
+          <cell align="center"><c>EPMDPortNo</c></cell>
+          <cell align="center"><c>NodeInfo*</c></cell>
+        </row>
+        <tcaption>DUMP_RESP</tcaption>
+      </table>
+
+      <p><c>NodeInfo</c> is a string written for each node kept in the EPMD.
+        When all <c>NodeInfo</c> has been written the connection is
+        closed by the EPMD.</p>
+
+      <p><c>NodeInfo</c> is, as expressed in Erlang:</p>
+
+      <code>
+io:format("active name     ~ts at port ~p, fd = ~p~n",
+          [NodeName, Port, Fd]).</code>
+
+      <p>or</p>
+
+      <code>
+io:format("old/unused name ~ts at port ~p, fd = ~p ~n",
+          [NodeName, Port, Fd]).</code>
+    </section>
+
+    <section>
+      <title>Kill EPMD</title>
+      <p>This request kills the running EPMD. It is almost never used.</p>
+
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+        </row>
+        <row>
+          <cell align="center"><c>107</c></cell>
+        </row>
+        <tcaption>KILL_REQ</tcaption>
+      </table>
+
+      <p>The response for a <c>KILL_REQ</c> is as follows:</p>
 
       <table align="left">
-	<row>
-	  <cell align="center">2</cell>
-	  <cell align="center">n</cell>
-	</row>
-	<row>
-	  <cell align="center">Length</cell>
-	  <cell align="center">Request</cell>
-	</row>
-      <tcaption></tcaption></table>
-
-      <section>
-	<title>Register a node in the EPMD</title>
-	<p>
-	  When a distributed node is started it registers itself in EPMD.
-	  The message ALIVE2_REQ described below is sent from the node towards
-	  EPMD. The response from EPMD is ALIVE2_RESP.
-	</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">1</cell>
-	    <cell align="center">2</cell>
-	    <cell align="center">1</cell>
-	    <cell align="center">1</cell>
-	    <cell align="center">2</cell>
-	    <cell align="center">2</cell>
-	    <cell align="center">2</cell>
-	    <cell align="center">Nlen</cell>
-	    <cell align="center">2</cell>
-	    <cell align="center">Elen</cell>
-	  </row>
-	  <row>
-	    <cell align="center">120</cell>
-	    <cell align="center">PortNo</cell>
-	    <cell align="center">NodeType</cell>
-	    <cell align="center">Protocol</cell>
-	    <cell align="center">HighestVersion</cell>
-	    <cell align="center">LowestVersion</cell>
-	    <cell align="center">Nlen</cell>
-	    <cell align="center">NodeName</cell>
-	    <cell align="center">Elen</cell>
-	    <cell align="center">Extra</cell>
-	  </row>
-	<tcaption>ALIVE2_REQ (120)</tcaption></table>
-	  <taglist>
-	    <tag><c>PortNo</c></tag>
-	    <item>
-	      The port number on which the node accept connection requests.
-	    </item>
-	    <tag><c>NodeType</c></tag>
-	    <item>
-	      77 = normal Erlang node, 72 = hidden node (C-node),...
-	    </item>
-	    <tag><c>Protocol</c></tag>
-	    <item>
-	      0 = tcp/ip-v4, ...
-	    </item>
-	    <tag><c>HighestVersion</c></tag>
-	    <item>
-	      The highest distribution version that this node can handle.
-	      The value in R6B and later is 5.
-	    </item>
-	    <tag><c>LowestVersion</c></tag>
-	    <item>
-	      The lowest distribution version that this node can handle.
-	      The value in R6B and later is 5.
-	    </item>
-	    <tag><c>Nlen</c></tag>
-	    <item>
-	      The length (in bytes) of the <c>NodeName</c> field.
-	    </item>
-	    <tag><c>NodeName</c></tag>
-	    <item>
-	      The NodeName as an UTF-8 encoded string of
-	      <c>Nlen</c> bytes.
-	    </item>
-	    <tag><c>Elen</c></tag>
-	    <item>
-	      The length of the <c>Extra</c> field.
-	    </item>
-	    <tag><c>Extra</c></tag>
-	    <item>
-	      Extra field of <c>Elen</c> bytes.
-	    </item>
-	  </taglist>
-	<p>
-	  The connection created to the EPMD must be kept as long as the
-	  node is a distributed node. When the connection is closed
-	  the node is automatically unregistered from the EPMD.
-	</p>
-	<p>
-	  The response message ALIVE2_RESP is described below.
-	</p>
-
-	<table align="left">
-	  <row>
-	    <cell align="center">1</cell>
-	    <cell align="center">1</cell>
-	    <cell align="center">2</cell>
-	  </row>
-	  <row>
-	    <cell align="center">121</cell>
-	    <cell align="center">Result</cell>
-	    <cell align="center">Creation</cell>
-	  </row>
-	<tcaption>ALIVE2_RESP (121)</tcaption></table>
-	<p>
-	  Result = 0 -> ok, Result > 0 -> error
-	</p>
-      </section>
-
-      <section>
-	<title>Unregister a node from the EPMD</title>
-	<p>
-	  A node unregisters itself from the EPMD by simply closing the
-	  TCP connection towards EPMD established when the node was registered.
-	</p>
-      </section>
-
-      <section>
-	<title>Get the distribution port of another node</title>
-	<p>
-	  When one node wants to connect to another node it starts with
-	  a PORT_PLEASE2_REQ request towards EPMD on the host where the 
-	  node resides in order to get the distribution port that the node 
-	  listens to.
-	</p>
-
-	<table align="left">
-	<row>
-	  <cell align="center">1</cell>
-	  <cell align="center">N</cell>
-	</row>
-	<row>
-	  <cell align="center">122</cell>
-	  <cell align="center">NodeName</cell>
-	</row>
-      <tcaption>PORT_PLEASE2_REQ (122)</tcaption></table>
-      <p>
-	where N = Length - 1
-      </p>
-
-      <p>
-      </p>
+        <row>
+          <cell align="center">2</cell>
+        </row>
+        <row>
+          <cell align="center"><c>OKString</c></cell>
+        </row>
+        <tcaption>KILL_RESP</tcaption>
+      </table>
+
+      <p>where <c>OKString</c> is "OK".</p>
+    </section>
+
+    <section>
+      <title>STOP_REQ  (Not Used)</title>
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">n</cell>
+        </row>
+        <row>
+          <cell align="center"><c>115</c></cell>
+          <cell align="center"><c>NodeName</c></cell>
+        </row>
+        <tcaption>STOP_REQ</tcaption>
+      </table>
+
+      <p>where n = <c>Length</c> - 1.</p>
+
+      <p>The current implementation of Erlang does not care if the connection
+        to the EPMD is broken.</p>
+
+      <p>The response for a <c>STOP_REQ</c> is as follows:</p>
+
       <table align="left">
-	<row>
-	  <cell align="center">1</cell>
-	  <cell align="center">1</cell>
-	</row>
-	<row>
-	  <cell align="center">119</cell>
-	  <cell align="center">Result</cell>
-	</row>
-	<tcaption>
-	  PORT2_RESP (119) response indicating error, Result > 0.
-	</tcaption>
+        <row>
+          <cell align="center">7</cell>
+        </row>
+        <row>
+          <cell align="center"><c>OKString</c></cell>
+        </row>
+        <tcaption>STOP_RESP</tcaption>
       </table>
-      <p>Or</p>
+
+      <p>where <c>OKString</c> is "STOPPED".</p>
+
+      <p>A negative response can look as follows:</p>
+
       <table align="left">
-	<row>
-	  <cell align="center">1</cell>
-	  <cell align="center">1</cell>
-	  <cell align="center">2</cell>
-	  <cell align="center">1</cell>
-	  <cell align="center">1</cell>
-	  <cell align="center">2</cell>
-	  <cell align="center">2</cell>
-	  <cell align="center">2</cell>
-	  <cell align="center">Nlen</cell>
-	  <cell align="center">2</cell>
-	  <cell align="center">Elen</cell>
-	</row>
-	<row>
-	  <cell align="center">119</cell>
-	  <cell align="center">Result</cell>
-	  <cell align="center">PortNo</cell>
-	  <cell align="center">NodeType</cell>
-	  <cell align="center">Protocol</cell>
-	  <cell align="center">HighestVersion</cell>
-	  <cell align="center">LowestVersion</cell>
-	  <cell align="center">Nlen</cell>
-	  <cell align="center">NodeName</cell>
-	  <cell align="center">Elen</cell>
-	  <cell align="center">Extra</cell>
-	</row>
-      <tcaption>PORT2_RESP when Result = 0.</tcaption></table>
-<p>
-If Result > 0, the packet only consists of [119, Result].
-</p>
-
-        <p>EPMD will close the socket as soon as it has sent the information.</p>
-      </section>
-
-      <section>
-	<title>Get all registered names from EPMD</title>
-	<p>
-	  This request is used via the Erlang function 
-	  <c>net_adm:names/1,2</c>. A TCP connection is opened
-	  towards EPMD and this request is sent.
-	</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">1</cell>
-	  </row>
-	  <row>
-	    <cell align="center">110</cell>
-	  </row>
-	<tcaption>NAMES_REQ (110)</tcaption></table>
-	
-
-	<p>The response for a <c>NAMES_REQ</c> looks like this:</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">4</cell>
-	    <cell align="center">&nbsp;</cell>
-	  </row>
-	  <row>
-	    <cell align="center">EPMDPortNo</cell>
-	    <cell align="center">NodeInfo*</cell>
-	  </row>
-	<tcaption>NAMES_RESP</tcaption></table>
-	<p>
-	  NodeInfo is a string written for each active node.
-	  When all NodeInfo has been written the connection is
-	  closed by EPMD.
-	</p>
-	<p>
-	  NodeInfo is, as expressed in Erlang:
-	</p>
-	<code>
-	io:format("name ~ts at port ~p~n", [NodeName, Port]).
-	</code>
-      </section>
-
-
-      <section>
-	<title>Dump all data from EPMD</title>
-	<p>
-	  This request is not really used, it should be regarded as a debug
-	  feature.
-	</p>
-	<table align="left">
-	  <row>
-	  <cell align="center">1</cell>
-	  </row>
-	  <row>
-	    <cell align="center">100</cell>
-	  </row>
-	<tcaption>DUMP_REQ</tcaption></table>
-
-	<p>The response for a <c>DUMP_REQ</c> looks like this:</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">4</cell>
-	    <cell align="center">&nbsp;</cell>
-	  </row>
-	  <row>
-	    <cell align="center">EPMDPortNo</cell>
-	    <cell align="center">NodeInfo*</cell>
-	  </row>
-	<tcaption>DUMP_RESP</tcaption></table>
-	<p>
-	  NodeInfo is a string written for each node kept in EPMD.
-	  When all NodeInfo has been written the connection is
-	  closed by EPMD.
-	</p>
-	<p>
-	  NodeInfo is, as expressed in Erlang:
-	</p>
-	<code>
-	io:format("active name     ~ts at port ~p, fd = ~p~n",
-	          [NodeName, Port, Fd]).
-	</code>
-	<p>
-	  or
-	</p>
-	<code>
-	io:format("old/unused name ~ts at port ~p, fd = ~p ~n",
-	          [NodeName, Port, Fd]).
-	</code>
-
-      </section>
-
-      <section>
-	<title>Kill the EPMD</title>
-	<p>
-	  This request will kill the running EPMD. It is almost never used.
-	</p>
-	<table align="left">
-	  <row>
-	  <cell align="center">1</cell>
-	  </row>
-	  <row>
-	    <cell align="center">107</cell>
-	  </row>
-	<tcaption>KILL_REQ</tcaption></table>
-
-	<p>The response fo a <c>KILL_REQ</c> looks like this:</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">2</cell>
-	  </row>
-	  <row>
-	    <cell align="center">OKString</cell>
-	  </row>
-	<tcaption>KILL_RESP</tcaption></table>
-	<p>
-	  where <c>OKString</c> is "OK".
-	</p>
-      </section>
-
-      <section>
-	<title>STOP_REQ  (Not Used)</title>
-	<p></p>
-	<table align="left">
-	  <row>
-	    <cell align="center">1</cell>
-	    <cell align="center">n</cell>
-	  </row>
-	  <row>
-	    <cell align="center">115</cell>
-	    <cell align="center">NodeName</cell>
-	  </row>
-	<tcaption>STOP_REQ</tcaption></table>
-	<p>
-	  where n = Length - 1
-	</p>
-	<p>
-	  The current implementation of Erlang does not care if the connection
-	  to the EPMD is broken.
-	</p>
-	<p>The response for a <c>STOP_REQ</c> looks like this.</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">7</cell>
-	  </row>
-	  <row>
-	    <cell align="center">OKString</cell>
-	  </row>
-	<tcaption>STOP_RESP</tcaption></table>
-	<p>
-	  where OKString is "STOPPED".
-	</p>
-	<p>A negative response can look like this.</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">7</cell>
-	  </row>
-	  <row>
-	    <cell align="center">NOKString</cell>
-	  </row>
-	<tcaption>STOP_NOTOK_RESP</tcaption></table>
-	<p>
-	  where NOKString is "NOEXIST".
-	</p>
-      </section>
+        <row>
+          <cell align="center">7</cell>
+        </row>
+        <row>
+          <cell align="center"><c>NOKString</c></cell>
+        </row>
+        <tcaption>STOP_NOTOK_RESP</tcaption>
+      </table>
+
+      <p>where <c>NOKString</c> is "NOEXIST".</p>
+    </section>
 <!--
-      <section>
-	<title>ALIVE_REQ (97)</title>
-	<p></p>
-
-	<table align="left">
-	  <row>
-	    <cell align="center">1</cell>
-	    <cell align="center">2</cell>
-	    <cell align="center">n</cell>
-	  </row>
-	  <row>
-	    <cell align="center">97</cell>
-	    <cell align="center">PortNo</cell>
-	    <cell align="center">NodeName</cell>
-	  </row>
-	<tcaption></tcaption></table>
-
-	<p>
-	  where n = Length - 3
-	</p>
-	<p>
-	  The connection created to the EPMD must be kept until the node is
-	  not a distributed node any longer.
-	</p>
-      </section>
-
-      <section>
-	<title>ALIVE_OK_RESP (89)</title>
-	<p></p>
-	<table align="left">
-	  <row>
-	    <cell align="center">1</cell>
-	    <cell align="center">2</cell>
-	  </row>
-	  <row>
-	    <cell align="center">89</cell>
-	    <cell align="center">Creation</cell>
-	  </row>
-	<tcaption></tcaption></table>
-      </section>
-
-
-      <section>
-	<title>ALIVE_NOTOK_RESP  ()</title>
-	<p>
-	  EPMD closed the connection.
-	</p>
-      </section>
-
-      <section>
-	<title>PORT_PLEASE_REQ   (112)</title>
-	<p></p>
+    <section>
+      <title>ALIVE_REQ (97)</title>
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">2</cell>
+          <cell align="center">n</cell>
+        </row>
+        <row>
+          <cell align="center"><c>97</c></cell>
+          <cell align="center"><c>PortNo</c></cell>
+          <cell align="center"><c>NodeName</c></cell>
+        </row>
+        <tcaption></tcaption>
+      </table>
+
+      <p>where n = <c>Length</c> - 3.</p>
+
+      <p>The connection created to the EPMD must be kept until the node is
+        not a distributed node any longer.</p>
+    </section>
+
+    <section>
+      <title>ALIVE_OK_RESP (89)</title>
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">2</cell>
+        </row>
+        <row>
+          <cell align="center"><c>89</c></cell>
+          <cell align="center"><c>Creation</c></cell>
+        </row>
+        <tcaption></tcaption>
+      </table>
+    </section>
+
+    <section>
+      <title>ALIVE_NOTOK_RESP ()</title>
+      <p>The EPMD closed the connection.</p>
+    </section>
+
+    <section>
+      <title>PORT_PLEASE_REQ (112)</title>
       <table align="left">
-	<row>
-	  <cell align="center">1</cell>
-	  <cell align="center">n</cell>
-	</row>
-	<row>
-	  <cell align="center">112</cell>
-	  <cell align="center">NodeName</cell>
-	</row>
-      <tcaption></tcaption></table>
-      <p>
-	where n = Length - 1
-      </p>
-      </section>
-
-      <section>
-	<title>PORT_OK_RESP ()</title>
-	<p></p>
-	<table align="left">
-	  <row>
-	    <cell align="center">2</cell>
-	  </row>
-	  <row>
-	    <cell align="center">PortNo</cell>
-	  </row>
-	<tcaption></tcaption></table>
-
-      </section>
-
-      <section>
-	<title>PORT_NOTOK_RESP ()</title>
-	<p>
-	  EPMD closed the connection.
-	</p>
-      </section>
-
-
-      <section>
-	<title>PORT_NOTOK_RESP ()</title>
-	<p>
-	  EPMD closed the connection.
-	</p>
-      </section>
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">n</cell>
+        </row>
+        <row>
+          <cell align="center"><c>112</c></cell>
+          <cell align="center"><c>NodeName</c></cell>
+        </row>
+        <tcaption></tcaption>
+      </table>
+
+      <p>where n = <c>Length</c> - 1.</p>
+    </section>
+
+    <section>
+      <title>PORT_OK_RESP ()</title>
+      <table align="left">
+        <row>
+          <cell align="center">2</cell>
+        </row>
+        <row>
+          <cell align="center"><c>PortNo</c></cell>
+        </row>
+        <tcaption></tcaption>
+      </table>
+    </section>
+
+    <section>
+      <title>PORT_NOTOK_RESP ()</title>
+      <p>The EPMD closed the connection.</p>
+    </section>
+
+    <section>
+      <title>PORT_NOTOK_RESP ()</title>
+      <p>The EPMD closed the connection.</p>
+    </section>
 -->
+  </section>
 
+  <section>
+    <marker id="distribution_handshake"/>
+    <title>Distribution Handshake</title>
+    <p>This section describes the distribution handshake protocol introduced
+      in Erlang/OTP R6. This description was previously located in
+      <c>$ERL_TOP/lib/kernel/internal_doc/distribution_handshake.txt</c> and
+      has more or less been copied and "formatted" here. It has been almost
+      unchanged since 1999, but the handshake has not changed much since then
+      either.</p>
+
+    <section>
+      <title>General</title>
+      <p>The TCP/IP distribution uses a handshake that expects a
+        connection-based protocol, that is, the protocol does not include any
+        authentication after the handshake procedure.</p>
+
+      <p>This is not entirely safe, as it is vulnerable against takeover
+        attacks, but it is a tradeoff between fair safety and performance.</p>
+
+      <p>The cookies are never sent in cleartext and the handshake procedure
+        expects the client (called <c>A</c>) to be the first one to prove that
+        it can generate a sufficient digest. The digest is generated with the
+        MD5 message digest algorithm and the challenges are expected to be
+        random numbers.</p>
+    </section>
+
+    <section>
+      <title>Definitions</title>
+      <p>A challenge is a 32-bit integer in big-endian order. Below the function
+        <c>gen_challenge()</c> returns a random 32-bit integer used as a
+        challenge.</p>
+
+      <p>A digest is a (16 bytes) MD5 hash of the challenge (as text)
+        concatenated with the cookie (as text). Below, the function
+        <c>gen_digest(Challenge, Cookie)</c> generates a digest as described
+        above.</p>
+
+      <p>An <c>out_cookie</c> is the cookie used in outgoing communication to a
+        certain node, so that <c>A</c>'s <c>out_cookie</c> for <c>B</c> is to
+        correspond with <c>B</c>'s <c>in_cookie</c> for <c>A</c> and conversely.
+        <c>A</c>'s <c>out_cookie</c> for <c>B</c> and <c>A</c>'s
+        <c>in_cookie</c> for <c>B</c> need <em>not</em> be the same. Below the
+        function <c>out_cookie(Node)</c> returns the current node's
+        <c>out_cookie</c> for <c>Node</c>.</p>
+
+      <p>An <c>in_cookie</c> is the cookie expected to be used by another node
+        when communicating with us, so that <c>A</c>'s <c>in_cookie</c> for
+        <c>B</c> corresponds with <c>B</c>'s <c>out_cookie</c> for <c>A</c>.
+        Below the function <c>in_cookie(Node)</c> returns the current node's
+        <c>in_cookie</c> for <c>Node</c>.</p>
+
+      <p>The cookies are text strings that can be viewed as passwords.</p>
+
+      <p>Every message in the handshake starts with a 16-bit big-endian integer,
+        which contains the message length (not counting the two initial bytes).
+        In Erlang this corresponds to option <c>{packet, 2}</c> in
+        <seealso marker="kernel:gen_tcp"><c>kernel:gen_tcp</c></seealso>.
+        Notice that after the handshake, the distribution switches to 4 byte
+        packet headers.</p>
     </section>
-      <section>
-	<title>Distribution Handshake</title>
-	  <p>
-            <marker id="distribution_handshake"/>
-	    This section describes the distribution handshake protocol
-	    introduced in the OTP-R6 release of Erlang/OTP. This
-	    description was previously located in
-	    <c>$ERL_TOP/lib/kernel/internal_doc/distribution_handshake.txt</c>,
-	    and has more or less been copied and "formatted" here. It has been
-	    more or less unchanged since the year 1999, but the handshake
-	    should not have changed much since then either.
-	  </p>
-	<section>
-	  <title>General</title>
-	  <p>
-	    The TCP/IP distribution uses a handshake which expects a
-	    connection based protocol, i.e. the protocol does not include
-	    any authentication after the handshake procedure.
-	  </p>
-	  <p>
-	    This is not entirely safe, as it is vulnerable against takeover
-	    attacks, but it is a tradeoff between fair safety and performance.
-	  </p>
-	  <p>
-	    The cookies are never sent in cleartext and the handshake procedure
-	    expects the client (called A) to be the first one to prove that it can 
-	    generate a sufficient digest. The digest is generated with the 
-	    MD5 message digest algorithm and the challenges are expected to be very
-	    random numbers.
-	  </p>
-	</section>
-	<section>
-	  <title>Definitions</title>
-	  <p>
-	    A challenge is a 32 bit integer number in big endian order. Below the function
-	    <c>gen_challenge()</c> returns a random 32 bit integer used as a challenge.
-	  </p>
-	  <p>
-	    A digest is a (16 bytes) MD5 hash of the Challenge (as text) concatenated
-	    with the cookie (as text). Below, the function <c>gen_digest(Challenge, Cookie)</c>
-	    generates a digest as described above.
-	  </p>
-	  <p>
-	    An out_cookie is the cookie used in outgoing communication to a certain node,
-	    so that A's out_cookie for B should correspond with B's in_cookie for A and 
-	    the other way around. A's out_cookie for B and A's in_cookie for B need <em>NOT</em>
-	    be the same. Below the function <c>out_cookie(Node)</c> returns the current
-	    node's out_cookie for <c>Node</c>.
-	  </p>
-	  <p>
-	    An in_cookie is the cookie expected to be used by another node when 
-	    communicating with us, so that A's in_cookie for B corresponds with B's 
-	    out_cookie for A. Below the function <c>in_cookie(Node)</c> returns the current
-	    node's <c>in_cookie</c> for <c>Node</c>.
-	  </p>
-	  <p>
-	    The cookies are text strings that can be viewed as passwords.
-	  </p>
-	  <p>
-	    Every message in the handshake starts with a 16 bit big endian integer 
-	    which contains the length of the message (not counting the two initial bytes).
-	    In erlang this corresponds to the <c>gen_tcp</c> option <c>{packet, 2}</c>. Note that after 
-	    the handshake, the distribution switches to 4 byte packet headers.
-	  </p>
-
-	</section>
-	<section>
-	  <title>The Handshake in Detail</title>
-	  <p>
-	    Imagine two nodes, node A, which initiates the handshake and node B, which
-	    accepts the connection.
-	  </p>
-	  <taglist>
-	    <tag>1) connect/accept</tag>
-	    <item><p>A connects to B via TCP/IP and B accepts the connection.</p></item>
-	    <tag>2) send_name/receive_name</tag>
-	    <item><p>A sends an initial identification to B. B receives the message.
-	    The message looks like this (every "square" being one byte and the packet
-	    header removed):
-	  </p>
-<pre>
+
+    <section>
+      <title>The Handshake in Detail</title>
+      <p>Imagine two nodes, <c>A</c> that initiates the handshake and <c>B</c>
+        that accepts the connection.</p>
+
+      <taglist>
+      <tag>1) connect/accept</tag>
+        <item>
+          <p><c>A</c> connects to <c>B</c> through TCP/IP and <c>B</c> accepts
+            the connection.</p>
+        </item>
+        <tag>2) <c>send_name</c>/<c>receive_name</c></tag>
+        <item>
+          <p><c>A</c> sends an initial identification to <c>B</c>, which
+            receives the message. The message looks as follows (every "square"
+            is one byte and the packet header is removed):</p>
+          <pre>
 +---+--------+--------+-----+-----+-----+-----+-----+-----+-...-+-----+
 |'n'|Version0|Version1|Flag0|Flag1|Flag2|Flag3|Name0|Name1| ... |NameN|
-+---+--------+--------+-----+-----+-----+-----+-----+-----+-... +-----+
-</pre>
-	  <p>
-	    The 'n' is just a message tag.
-	    Version0 and Version1 is the distribution version selected by node A,
-            based on information from EPMD. (16 bit big endian)
-	    Flag0 ... Flag3 are capability flags, the capabilities defined in
-	    <c>$ERL_TOP/lib/kernel/include/dist.hrl</c>.
-            (32 bit big endian)
-	    Name0 ... NameN is the full nodename of A, as a string of bytes (the
-	    packet length denotes how long it is).
-	  </p></item>
-	  <tag>3) recv_status/send_status</tag>
-	  <item><p>B sends a status message to A, which indicates
-	    if the connection is allowed. The following status codes are defined:</p>
-	    <taglist>
-	      <tag><c>ok</c></tag>
-	      <item>The handshake will continue.</item>
-	      <tag><c>ok_simultaneous</c></tag>
-	      <item>The handshake will continue, but A is informed that B
-              has another ongoing connection attempt that will be
-	      shut down (simultaneous connect where A's name is 
-	      greater than B's name, compared literally).</item>
-	      <tag><c>nok</c></tag>
-	      <item>The handshake will not continue, as B already has an ongoing handshake
-	      which it itself has initiated. (simultaneous connect where B's name is 
-	      greater than A's).</item>
-	      <tag><c>not_allowed</c></tag>
-	      <item>The connection is disallowed for some (unspecified) security 
-              reason.</item>
-	      <tag><c>alive</c></tag>
-	      <item>A connection to the node is already active, which either means
-	      that node A is confused or that the TCP connection breakdown
-	      of a previous node with this name has not yet reached node B.
-	      See 3B below.</item>
-	    </taglist>
-	    <p>This is the format of the status message:</p>
-<pre>
++---+--------+--------+-----+-----+-----+-----+-----+-----+-... +-----+</pre>
+           <p>'n' is the message tag. 'Version0' and 'Version1' is the
+             distribution version selected by <c>A</c>, based on information
+             from the EPMD. (16-bit big-endian) 'Flag0' ... 'Flag3' are
+             capability flags, the capabilities are defined in
+             <c>$ERL_TOP/lib/kernel/include/dist.hrl</c>. (32-bit big-endian)
+             'Name0' ... 'NameN' is the full node name of <c>A</c>, as a string
+             of bytes (the packet length denotes how long it is).</p>
+        </item>
+        <tag>3) <c>recv_status</c>/<c>send_status</c></tag>
+        <item>
+          <p><c>B</c> sends a status message to <c>A</c>, which indicates if the
+            connection is allowed. The following status codes are defined:</p>
+          <taglist>
+            <tag><c>ok</c></tag>
+            <item>
+              <p>The handshake will continue.</p>
+            </item>
+            <tag><c>ok_simultaneous</c></tag>
+            <item>
+              <p>The handshake will continue, but <c>A</c> is informed that
+                <c>B</c> has another ongoing connection attempt that will be
+                shut down (simultaneous connect where <c>A</c>'s name is
+                greater than <c>B</c>'s name, compared literally).</p>
+            </item>
+            <tag><c>nok</c></tag>
+            <item>
+              <p>The handshake will not continue, as <c>B</c> already has an
+                ongoing handshake, which it itself has initiated (simultaneous
+                connect where <c>B</c>'s name is greater than <c>A</c>'s).</p>
+            </item>
+            <tag><c>not_allowed</c></tag>
+            <item>
+              <p>The connection is disallowed for some (unspecified) security
+                reason.</p>
+            </item>
+            <tag><c>alive</c></tag>
+            <item>
+              <p>A connection to the node is already active, which either means
+                that node <c>A</c> is confused or that the TCP connection
+                breakdown of a previous node with this name has not yet reached
+                node <c>B</c>. See step 3B below.</p>
+            </item>
+          </taglist>
+          <p>The format of the status message is as follows:</p>
+          <pre>
 +---+-------+-------+-...-+-------+
 |'s'|Status0|Status1| ... |StatusN|
-+---+-------+-------+-...-+-------+
-</pre>
-	    <p>
-	      's' is the message tag Status0 ... StatusN is the status as a string (not terminated)
-	    </p>
-	  </item>
-	  <tag>3B) send_status/recv_status</tag>
-	  <item><p>If status was 'alive', node A will answer with
-	  another status message containing either 'true' which means that the
-	  connection should continue (The old connection from this node is broken), or
-	  <c>'false'</c>, which simply means that the connection should be closed, the 
-	  connection attempt was a mistake.</p></item>
-	  <tag>4) recv_challenge/send_challenge</tag>
-	  <item><p>If the status was <c>ok</c> or <c>ok_simultaneous</c>,
-	  The handshake continues with B sending A another message, the challenge.
-	  The challenge contains the same type of information as the "name" message 
-	  initially sent from A to B, with the addition of a 32 bit challenge:</p>
-<pre>
++---+-------+-------+-...-+-------+</pre>
+          <p>'s' is the message tag. 'Status0' ... 'StatusN' is the status as a
+            string (not terminated).</p>
+        </item>
+        <tag>3B) <c>send_status</c>/<c>recv_status</c></tag>
+        <item>
+          <p>If status was <c>alive</c>, node <c>A</c> answers with another
+            status message containing either <c>true</c>, which means that the
+            connection is to continue (the old connection from this node is
+            broken), or <c>false</c>, which means that the connection is to be
+            closed (the connection attempt was a mistake.</p>
+        </item>
+        <tag>4) <c>recv_challenge</c>/<c>send_challenge</c></tag>
+        <item>
+          <p>If the status was <c>ok</c> or <c>ok_simultaneous</c>, the
+            handshake continues with <c>B</c> sending <c>A</c> another message,
+            the challenge. The challenge contains the same type of information
+            as the "name" message initially sent from <c>A</c> to <c>B</c>, plus
+            a 32-bit challenge:</p>
+          <pre>
 +---+--------+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
 |'n'|Version0|Version1|Flag0|Flag1|Flag2|Flag3|Chal0|Chal1|Chal2|Chal3|Name0|Name1| ... |NameN|
-+---+--------+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-... +-----+
-</pre>
-          <p>
-	    Where Chal0 ... Chal3 is the challenge as a 32 bit big endian integer
-	    and the other fields are B's version, flags and full nodename.
-	  </p></item>
-	  <tag>5) send_challenge_reply/recv_challenge_reply</tag>
-	  <item><p>Now A has generated a digest and its own challenge. Those are
-	  sent together in a package to B:</p>
-<pre>
++---+--------+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-... +-----+</pre>
+          <p>'Chal0' ... 'Chal3' is the challenge as a 32-bit big-endian integer
+            and the other fields are <c>B</c>'s version, flags, and full node
+            name.</p>
+        </item>
+        <tag>5) <c>send_challenge_reply</c>/<c>recv_challenge_reply</c></tag>
+        <item>
+          <p>Now <c>A</c> has generated a digest and its own challenge. Those
+            are sent together in a package to <c>B</c>:</p>
+          <pre>
 +---+-----+-----+-----+-----+-----+-----+-----+-----+-...-+------+
 |'r'|Chal0|Chal1|Chal2|Chal3|Dige0|Dige1|Dige2|Dige3| ... |Dige15|
-+---+-----+-----+-----+-----+-----+-----+-----+-----+-...-+------+
-</pre>
-          <p>
-	    Where 'r' is the tag, Chal0 ... Chal3 is A's challenge for B to handle and
-	    Dige0 ... Dige15 is the digest that A constructed from the challenge B sent
-	    in the previous step.
-	  </p></item>
-	  <tag>6) recv_challenge_ack/send_challenge_ack</tag>
-	  <item><p>B checks that the digest received from A is correct and generates a
-	  digest from the challenge received from  A. The digest is then sent to A. The
-	  message looks like this:</p>
-<pre>
++---+-----+-----+-----+-----+-----+-----+-----+-----+-...-+------+</pre>
+          <p>'r' is the tag. 'Chal0' ... 'Chal3' is <c>A</c>'s challenge for
+            <c>B</c> to handle. 'Dige0' ... 'Dige15' is the digest that <c>A</c>
+            constructed from the challenge <c>B</c> sent in the previous
+            step.</p>
+        </item>
+        <tag>6) <c>recv_challenge_ack</c>/<c>send_challenge_ack</c></tag>
+        <item>
+          <p><c>B</c> checks that the digest received from <c>A</c> is correct
+            and generates a digest from the challenge received from <c>A</c>.
+            The digest is then sent to <c>A</c>. The message is as follows:</p>
+          <pre>
 +---+-----+-----+-----+-----+-...-+------+
 |'a'|Dige0|Dige1|Dige2|Dige3| ... |Dige15|
-+---+-----+-----+-----+-----+-...-+------+
-</pre>
-          <p>
-	    Where 'a' is the tag and Dige0 ... Dige15 is the digest calculated by B
-	    for A's challenge.</p></item>
-	  <tag>7)</tag>
-	  <item><p>A checks the digest from B and the connection is up.</p></item>
-	</taglist>
-	</section>
-	<section>
-	  <title>Semigraphic View</title>
-<pre>
-A (initiator)						B (acceptor)
-
-TCP connect -----------------------------------------&gt;	
-							TCP accept
-
-send_name   -----------------------------------------&gt;
-							recv_name
-
-	    &lt;----------------------------------------	send_status
++---+-----+-----+-----+-----+-...-+------+</pre>
+          <p>'a' is the tag. 'Dige0' ... 'Dige15' is the digest calculated by
+            <c>B</c> for <c>A</c>'s challenge.</p>
+        </item>
+        <tag>7) check</tag>
+        <item>
+          <p><c>A</c> checks the digest from <c>B</c> and the connection is
+            up.</p>
+        </item>
+      </taglist>
+    </section>
+
+    <section>
+      <title>Semigraphic View</title>
+      <pre>
+A (initiator)                                      B (acceptor)
+
+TCP connect ------------------------------------&gt;
+                                                   TCP accept
+
+send_name --------------------------------------&gt;
+                                                   recv_name
+
+&lt;---------------------------------------------- send_status
 recv_status
 (if status was 'alive'
- send_status - - - - - - - - - - - - - - - - - - - -&gt;
-							recv_status)
-							ChB = gen_challenge()
-		          (ChB)
-	    &lt;----------------------------------------	send_challenge
+ send_status - - - - - - - - - - - - - - - - - -&gt;
+                                                   recv_status)
+                                                   ChB = gen_challenge()
+                          (ChB)
+&lt;---------------------------------------------- send_challenge
 recv_challenge
-
 ChA = gen_challenge(),
 OCA = out_cookie(B),
 DiA = gen_digest(ChB,OCA)
-			  (ChA, DiA)
-send_challenge_reply --------------------------------&gt;
-							recv_challenge_reply
-							ICB = in_cookie(A),
-							check:
-							DiA == gen_digest
-								(ChB, ICB) ?
-							- if OK:
-	    						 OCB = out_cookie(A),
-							 DiB = gen_digest
-			(DiB)					(ChA, OCB)
-	    &lt;-----------------------------------------	 send_challenge_ack
-recv_challenge_ack					 DONE
-ICA = in_cookie(B),                                     - else
-check:                                                   CLOSE
-DiB == gen_digest(ChA,ICA) ?
-- if OK
+                          (ChA, DiA)
+send_challenge_reply ---------------------------&gt;
+                                                   recv_challenge_reply
+                                                   ICB = in_cookie(A),
+                                                   check:
+                                                   DiA == gen_digest (ChB, ICB)?
+                                                   - if OK:
+                                                    OCB = out_cookie(A),
+                                                    DiB = gen_digest (ChA, OCB)
+                          (DiB)
+&lt;----------------------------------------------- send_challenge_ack
+recv_challenge_ack                                  DONE
+ICA = in_cookie(B),                                - else:
+check:                                              CLOSE
+DiB == gen_digest(ChA,ICA)?
+- if OK:
  DONE
-- else
- CLOSE
-</pre>
-	</section>
-	<marker id="dflags"/>
-	<section>
-	  <title>The Currently Defined Distribution Flags</title>
-	  <p>
-	    Currently (OTP-R16) the following capability flags are defined:
-	  </p>
-<pre>
-%% The node should be published and part of the global namespace
--define(DFLAG_PUBLISHED,1).
-
-%% The node implements an atom cache (obsolete)
--define(DFLAG_ATOM_CACHE,2).
-
-%% The node implements extended (3 * 32 bits) references. This is
-%% required today. If not present connection will be refused.
--define(DFLAG_EXTENDED_REFERENCES,4).
-
-%% The node implements distributed process monitoring.
--define(DFLAG_DIST_MONITOR,8).
-
-%% The node uses separate tag for fun's (lambdas) in the distribution protocol.
--define(DFLAG_FUN_TAGS,16#10).
-
-%% The node implements distributed named process monitoring.
--define(DFLAG_DIST_MONITOR_NAME,16#20).
-
-%% The (hidden) node implements atom cache (obsolete)
--define(DFLAG_HIDDEN_ATOM_CACHE,16#40).
-
-%% The node understand new fun-tags
--define(DFLAG_NEW_FUN_TAGS,16#80).
-
-%% The node is capable of handling extended pids and ports. This is
-%% required today. If not present connection will be refused.
--define(DFLAG_EXTENDED_PIDS_PORTS,16#100).
-
-%%
--define(DFLAG_EXPORT_PTR_TAG,16#200).
-
-%%
--define(DFLAG_BIT_BINARIES,16#400).
-
-%% The node understands new float format
--define(DFLAG_NEW_FLOATS,16#800).
-
-%%
--define(DFLAG_UNICODE_IO,16#1000).
-
-%% The node implements atom cache in distribution header.
--define(DFLAG_DIST_HDR_ATOM_CACHE,16#2000).
-
-%% The node understand the SMALL_ATOM_EXT tag
--define(DFLAG_SMALL_ATOM_TAGS, 16#4000).
-
-%% The node understand UTF-8 encoded atoms
--define(DFLAG_UTF8_ATOMS, 16#10000).
-
-</pre>
-	</section>
-      </section>
-
-      <section>
-        <marker id="connected_nodes"/>
-	<title>Protocol between connected nodes</title>
-	<p>
-	  As of erts version 5.7.2 the runtime system passes a distribution
-	  flag in the handshake stage that enables the use of a
-	  <seealso marker="erl_ext_dist#distribution_header">distribution
-	  header</seealso> on all messages passed. Messages passed between
-	  nodes are in this case on the following format:
-	</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">4</cell>
-	    <cell align="center">d</cell>
-	    <cell align="center">n</cell>
-	    <cell align="center">m</cell>
-	  </row>
-	  <row>
-	    <cell align="center"><c>Length</c></cell>
-	    <cell align="center"><c>DistributionHeader</c></cell>
-	    <cell align="center"><c>ControlMessage</c></cell>
-	    <cell align="center"><c>Message</c></cell>
-	  </row>
-	<tcaption></tcaption></table>
-	<p>
-	  where:
-	</p>
-	<p>
-	  <c>Length</c> is equal to d + n + m
-	</p>
-	<p>
-	  <c>ControlMessage</c> is a tuple passed using the external format of
-	  Erlang.
-	</p>
-	<p>
-	  <c>Message</c> is the message sent to another node using the '!'
-	  (in external format). Note that <c>Message</c> is only passed in
-	  combination with a <c>ControlMessage</c> encoding a send ('!').
-	</p>
-	<p>
-	  Also note that <seealso marker="erl_ext_dist#overall_format">the
-	  version number is omitted from the terms that follow a
-	  distribution header</seealso>.
-	</p>
-	<p>
-	  Nodes with an erts version less than 5.7.2 does not pass the
-	  distribution flag that enables the distribution header. Messages
-	  passed between nodes are in this case on the following format:
-	</p>
-	<table align="left">
-	  <row>
-	    <cell align="center">4</cell>
-	    <cell align="center">1</cell>
-	    <cell align="center">n</cell>
-	    <cell align="center">m</cell>
-	  </row>
-	  <row>
-	    <cell align="center"><c>Length</c></cell>
-	    <cell align="center"><c>Type</c></cell>
-	    <cell align="center"><c>ControlMessage</c></cell>
-	    <cell align="center"><c>Message</c></cell>
-	  </row>
-	<tcaption></tcaption></table>
-	<p>
-	  where:
-	</p>
-	<p>
-	  <c>Length</c> is equal to 1 + n + m
-  	</p>
-	<p>
-	  Type is: 112 (pass through)
-	</p>
-	<p>
-	  <c>ControlMessage</c> is a tuple passed using the external format of
-	  Erlang.
-	</p>
-	<p>
-	  <c>Message</c> is the message sent to another node using the '!'
-	  (in external format).  Note that <c>Message</c> is only passed in
-	  combination with a <c>ControlMessage</c> encoding a send ('!').
-	</p>
-	<p>
-	  The <c>ControlMessage</c> is a tuple, where the first element
-	  indicates which distributed operation it encodes.
-	</p>
-	<taglist>
-	  <tag><c>LINK</c></tag>
-	  <item>
-	    <p>
-	      <c>{1, FromPid, ToPid}</c>
-	    </p>
-	  </item>
-	  
-	  <tag><c>SEND</c></tag>
-	  <item>
-	    <p>
-	      <c>{2, Unused, ToPid}</c>
-	    </p>
-	    <p>
-	    <em>Note</em> followed by <c>Message</c>
-	    </p>
-	    <p>
-	      <c>Unused</c> is kept for backward compatibility
-	    </p>
-	  </item>
-
-	  <tag><c>EXIT</c></tag>
-	  <item>
-	    <p>
-	      <c>{3, FromPid, ToPid, Reason}</c>
-	    </p>
-	  </item>
-	  
-	  <tag><c>UNLINK</c></tag>
-	  <item>
-	    <p>
-	      <c>{4, FromPid, ToPid}</c>
-	    </p>
-	  </item>
-	  
-	  <tag><c>NODE_LINK</c></tag>
-	  <item>
-	    <p>
-	      <c>{5}</c>
-	    </p>
-	  </item>
-	  
-	  <tag><c>REG_SEND</c></tag>
-	  <item>
-	    <p>
-	      <c>{6, FromPid, Unused, ToName}</c>
-	    </p>
-	    <p>
-	    <em>Note</em> followed by <c>Message</c>
-	    </p>
-	    <p>
-	      <c>Unused</c> is kept for backward compatibility
-	    </p>
-	  </item>
-
-	  <tag><c>GROUP_LEADER</c></tag>
-	  <item>
-	    <p>
-	      <c>{7, FromPid, ToPid}</c>
-	    </p>
-	  </item>
-	
-	  <tag><c>EXIT2</c></tag>
-	  <item>
-	    <p>
-	      <c>{8, FromPid, ToPid, Reason}</c>
-	    </p>
-	  </item>
-	</taglist>
-      </section>
-
-  
-    <section>
-      <title>New Ctrlmessages for distrvsn = 1 (OTP R4)</title>
-      <taglist>
-	<tag><c>SEND_TT</c></tag>
-	<item>
-	<p>
-	  <c>{12, Unused, ToPid, TraceToken}</c>
-	</p>
-	<p>
-	<em>Note</em> followed by <c>Message</c>
-	</p>
-	<p>
-	  <c>Unused</c> is kept for backward compatibility
-	</p>
-	</item>
-
-	<tag><c>EXIT_TT</c></tag>
-	<item>
-	<p>
-	  <c>{13, FromPid, ToPid, TraceToken, Reason}</c>	  
-	</p>
-	</item>
-      
-	<tag><c>REG_SEND_TT</c></tag>
-	<item>
-	<p>
-	  <c>{16, FromPid, Unused, ToName, TraceToken}</c>
-	</p>
-	<p>
-	<em>Note</em> followed by <c>Message</c>
-	</p>
-	<p>
-	  <c>Unused</c> is kept for backward compatibility
-	</p>
-	</item>
-      
-	<tag><c>EXIT2_TT</c></tag>
-	<item>
-	<p>
-	  <c>{18, FromPid, ToPid, TraceToken, Reason}</c>
-	</p>
-	</item>
-      </taglist>
-    </section>
-    
-    <section>
-      <title>New Ctrlmessages for distrvsn = 2</title>
-      <p>
-	distrvsn 2 was never used.
-      </p>
-    </section>
-    
-    <section>
-      <title>New Ctrlmessages for distrvsn = 3 (OTP R5C)</title>
-      <p>
-	None, but the version number was increased anyway.
-      </p>
+- else:
+ CLOSE</pre>
     </section>
 
     <section>
-      <title>New Ctrlmessages for distrvsn = 4 (OTP R6)</title>
-      <p>
-	These are only recognized by Erlang nodes, not by hidden nodes.
-      </p>
+      <marker id="dflags"/>
+      <title>Distribution Flags</title>
+      <p>The following capability flags are defined:</p>
       <taglist>
-	<tag><c>MONITOR_P</c></tag>
-	<item>
-	<p>
-	  <c>{19, FromPid, ToProc, Ref}</c>
-	  
-	  <c>FromPid</c> = monitoring process
-	  <c>ToProc</c> = monitored process pid or name (atom)
-	</p>
-	</item>
-      
-	<tag><c>DEMONITOR_P</c></tag>
-	<item>
-	<p>
-	  <c>{20, FromPid, ToProc, Ref}</c>
-	  We include the FromPid just in case we want to trace this.
-	  
-	  <c>FromPid</c> = monitoring process
-	  <c>ToProc</c> = monitored process pid or name (atom)
-	</p>
-	</item>
-
-	<tag><c>MONITOR_P_EXIT</c></tag>
-	<item>
-	<p>
-	  <c>{21, FromProc, ToPid, Ref, Reason}</c>
-	  
-	  <c>FromProc</c> = monitored process pid or name (atom)
-	  <c>ToPid</c> = monitoring process
-	  <c>Reason</c> = exit reason for the monitored process
-	</p>
-	</item>
+        <tag><c>-define(DFLAG_PUBLISHED,1).</c></tag>
+        <item>
+          <p>The node is to be published and part of the global namespace.</p>
+        </item>
+        <tag><c>-define(DFLAG_ATOM_CACHE,2).</c></tag>
+        <item>
+          <p>The node implements an atom cache (obsolete).</p>
+        </item>
+        <tag><c>-define(DFLAG_EXTENDED_REFERENCES,4).</c></tag>
+        <item>
+          <p>The node implements extended (3 &times; 32 bits) references. This
+            is required today. If not present, the  connection is refused.</p>
+        </item>
+        <tag><c>-define(DFLAG_DIST_MONITOR,8).</c></tag>
+        <item>
+          <p>The node implements distributed process monitoring.</p>
+        </item>
+        <tag><c>-define(DFLAG_FUN_TAGS,16#10).</c></tag>
+        <item>
+          <p>The node uses separate tag for funs (lambdas) in the distribution
+            protocol.</p>
+        </item>
+        <tag><c>-define(DFLAG_DIST_MONITOR_NAME,16#20).</c></tag>
+        <item>
+          <p>The node implements distributed named process monitoring.</p>
+        </item>
+        <tag><c>-define(DFLAG_HIDDEN_ATOM_CACHE,16#40).</c></tag>
+        <item>
+          <p>The (hidden) node implements atom cache (obsolete).</p>
+        </item>
+        <tag><c>-define(DFLAG_NEW_FUN_TAGS,16#80).</c></tag>
+        <item>
+          <p>The node understand new fun tags.</p>
+        </item>
+        <tag><c>-define(DFLAG_EXTENDED_PIDS_PORTS,16#100).</c></tag>
+        <item>
+          <p>The node can handle extended pids and ports. This is required
+            today. If not present, the connection is refused.</p>
+        </item>
+        <tag><c>-define(DFLAG_EXPORT_PTR_TAG,16#200).</c></tag>
+        <item>
+        </item>
+        <tag><c>-define(DFLAG_BIT_BINARIES,16#400).</c></tag>
+        <item>
+        </item>
+        <tag><c>-define(DFLAG_NEW_FLOATS,16#800).</c></tag>
+        <item>
+          <p>The node understands new float format.</p>
+        </item>
+        <tag><c>-define(DFLAG_UNICODE_IO,16#1000).</c></tag>
+        <item>
+        </item>
+        <tag><c>-define(DFLAG_DIST_HDR_ATOM_CACHE,16#2000).</c></tag>
+        <item>
+          <p>The node implements atom cache in distribution header.</p>
+        </item>
+        <tag><c>-define(DFLAG_SMALL_ATOM_TAGS, 16#4000).</c></tag>
+        <item>
+          <p>The node understand the <c>SMALL_ATOM_EXT</c> tag.</p>
+        </item>
+        <tag><c>-define(DFLAG_UTF8_ATOMS, 16#10000).</c></tag>
+        <item>
+          <p>The node understand UTF-8 encoded atoms.</p>
+        </item>
       </taglist>
     </section>
-  </chapter>
+  </section>
+
+  <section>
+    <marker id="connected_nodes"/>
+    <title>Protocol between Connected Nodes</title>
+    <p>As from <c>ERTS</c> 5.7.2 the runtime system passes a distribution flag
+      in the handshake stage that enables the use of a
+      <seealso marker="erl_ext_dist#distribution_header">distribution header
+      </seealso> on all messages passed. Messages passed between nodes have in
+      this case the following format:</p>
+
+    <table align="left">
+      <row>
+        <cell align="center">4</cell>
+        <cell align="center">d</cell>
+        <cell align="center">n</cell>
+        <cell align="center">m</cell>
+      </row>
+      <row>
+        <cell align="center"><c>Length</c></cell>
+        <cell align="center"><c>DistributionHeader</c></cell>
+        <cell align="center"><c>ControlMessage</c></cell>
+        <cell align="center"><c>Message</c></cell>
+      </row>
+      <tcaption>Format of Messages Passed between Nodes (as from ERTS 5.7.2)
+      </tcaption>
+    </table>
+
+    <taglist>
+      <tag><c>Length</c></tag>
+      <item>
+        <p>Equal to d + n + m.</p>
+      </item>
+      <tag><c>ControlMessage</c></tag>
+      <item>
+        <p>A tuple passed using the external format of Erlang.</p>
+      </item>
+      <tag><c>Message</c></tag>
+      <item>
+        <p>The message sent to another node using the '!' (in external format).
+          Notice that <c>Message</c> is only passed in combination with a
+          <c>ControlMessage</c> encoding a send ('!').</p>
+      </item>
+    </taglist>
+
+    <p>Notice that <seealso marker="erl_ext_dist#overall_format">the version
+      number is omitted from the terms that follow a distribution header
+      </seealso>.</p>
+
+    <p>Nodes with an <c>ERTS</c> version earlier than 5.7.2 does not pass the
+      distribution flag that enables the distribution header. Messages passed
+      between nodes have in this case the following format:</p>
+
+    <table align="left">
+      <row>
+        <cell align="center">4</cell>
+        <cell align="center">1</cell>
+        <cell align="center">n</cell>
+        <cell align="center">m</cell>
+      </row>
+      <row>
+        <cell align="center"><c>Length</c></cell>
+        <cell align="center"><c>Type</c></cell>
+        <cell align="center"><c>ControlMessage</c></cell>
+        <cell align="center"><c>Message</c></cell>
+      </row>
+      <tcaption>Format of Messages Passed between Nodes (before ERTS 5.7.2)
+      </tcaption>
+    </table>
+
+    <taglist>
+      <tag><c>Length</c></tag>
+      <item>
+        <p>Equal to 1 + n + m.</p>
+      </item>
+      <tag><c>Type</c></tag>
+      <item>
+        <p>Equal to <c>112</c> (pass through).</p>
+      </item>
+      <tag><c>ControlMessage</c></tag>
+      <item>
+        <p>A tuple passed using the external format of Erlang.</p>
+      </item>
+      <tag><c>Message</c></tag>
+      <item>
+        <p>The message sent to another node using the '!' (in external format).
+          Notice that <c>Message</c> is only passed in combination with a
+          <c>ControlMessage</c> encoding a send ('!').</p>
+      </item>
+    </taglist>
+
+    <p>The <c>ControlMessage</c> is a tuple, where the first element indicates
+      which distributed operation it encodes:</p>
+
+    <taglist>
+      <tag><c>LINK</c></tag>
+      <item>
+        <p><c>{1, FromPid, ToPid}</c></p>
+      </item>
+      <tag><c>SEND</c></tag>
+      <item>
+        <p><c>{2, Unused, ToPid}</c></p>
+        <p>Followed by <c>Message</c>.</p>
+        <p><c>Unused</c> is kept for backward compatibility.</p>
+      </item>
+      <tag><c>EXIT</c></tag>
+      <item>
+        <p><c>{3, FromPid, ToPid, Reason}</c></p>
+      </item>
+      <tag><c>UNLINK</c></tag>
+      <item>
+        <p><c>{4, FromPid, ToPid}</c></p>
+      </item>
+      <tag><c>NODE_LINK</c></tag>
+      <item>
+        <p><c>{5}</c></p>
+      </item>
+      <tag><c>REG_SEND</c></tag>
+      <item>
+        <p><c>{6, FromPid, Unused, ToName}</c></p>
+        <p>Followed by <c>Message</c>.</p>
+        <p><c>Unused</c> is kept for backward compatibility.</p>
+      </item>
+      <tag><c>GROUP_LEADER</c></tag>
+      <item>
+        <p><c>{7, FromPid, ToPid}</c></p>
+      </item>	
+      <tag><c>EXIT2</c></tag>
+      <item>
+        <p><c>{8, FromPid, ToPid, Reason}</c></p>
+      </item>
+    </taglist>
+  </section>
+
+  <section>
+    <title>New Ctrlmessages for distrvsn = 1 (Erlang/OTP R4)</title>
+    <taglist>
+      <tag><c>SEND_TT</c></tag>
+      <item>
+        <p><c>{12, Unused, ToPid, TraceToken}</c></p>
+        <p>Followed by <c>Message</c>.</p>
+        <p><c>Unused</c> is kept for backward compatibility.</p>
+      </item>
+      <tag><c>EXIT_TT</c></tag>
+      <item>
+        <p><c>{13, FromPid, ToPid, TraceToken, Reason}</c></p>
+      </item>
+      <tag><c>REG_SEND_TT</c></tag>
+      <item>
+        <p><c>{16, FromPid, Unused, ToName, TraceToken}</c></p>
+        <p>Followed by <c>Message</c>.</p>
+        <p><c>Unused</c> is kept for backward compatibility.</p>
+      </item>      
+      <tag><c>EXIT2_TT</c></tag>
+      <item>
+        <p><c>{18, FromPid, ToPid, TraceToken, Reason}</c></p>
+      </item>
+    </taglist>
+  </section>
+
+  <section>
+    <title>New Ctrlmessages for distrvsn = 2</title>
+    <p><c>distrvsn</c> 2 was never used.</p>
+  </section>
+
+  <section>
+    <title>New Ctrlmessages for distrvsn = 3 (Erlang/OTP R5C)</title>
+    <p>None, but the version number was increased anyway.</p>
+  </section>
+
+  <section>
+    <title>New Ctrlmessages for distrvsn = 4 (Erlang/OTP R6)</title>
+    <p>These are only recognized by Erlang nodes, not by hidden nodes.</p>
+
+    <taglist>
+      <tag><c>MONITOR_P</c></tag>
+      <item>
+        <p><c>{19, FromPid, ToProc, Ref}</c>, where
+          <c>FromPid</c> = monitoring process and
+          <c>ToProc</c> = monitored process pid or name (atom)</p>
+      </item>
+      <tag><c>DEMONITOR_P</c></tag>
+      <item>
+        <p><c>{20, FromPid, ToProc, Ref}</c>, where
+          <c>FromPid</c> = monitoring process and
+          <c>ToProc</c> = monitored process pid or name (atom)</p>
+        <p>We include <c>FromPid</c> just in case we want to trace this.</p>
+      </item>
+      <tag><c>MONITOR_P_EXIT</c></tag>
+      <item>
+        <p><c>{21, FromProc, ToPid, Ref, Reason}</c>, where
+          <c>FromProc</c> = monitored process pid or name (atom),
+          <c>ToPid</c> = monitoring process, and
+          <c>Reason</c> = exit reason for the monitored process</p>
+      </item>
+    </taglist>
+  </section>
+</chapter>
diff --git a/erts/doc/src/erl_driver.xml b/erts/doc/src/erl_driver.xml
index d8116d4650..69c3375858 100644
--- a/erts/doc/src/erl_driver.xml
+++ b/erts/doc/src/erl_driver.xml
@@ -21,7 +21,6 @@
       limitations under the License.
 
     </legalnotice>
-
     <title>erl_driver</title>
     <prepared>Jakob Cederlund</prepared>
     <responsible>Jakob Cederlund</responsible>
@@ -33,519 +32,546 @@
     <file>erl_driver.xml</file>
   </header>
   <lib>erl_driver</lib>
-  <libsummary>API functions for an Erlang driver</libsummary>
+  <libsummary>API functions for an Erlang driver.</libsummary>
   <description>
     <p>An Erlang driver is a library containing a set of native driver
-      callback functions that the Erlang VM calls when certain
-      events occur. There may be multiple instances of a driver, each
+      callback functions that the Erlang Virtual Machine calls when certain
+      events occur. There can be multiple instances of a driver, each
       instance is associated with an Erlang port.</p>
+
     <marker id="WARNING"/>
-      <warning><p><em>Use this functionality with extreme care!</em></p>
+    <warning>
+      <p><em>Use this functionality with extreme care.</em></p>
       <p>A driver callback is executed as a direct extension of the
-      native code of the VM. Execution is not made in a safe environment.
-      The VM can <em>not</em> provide the same services as provided when
-      executing Erlang code, such as preemptive scheduling or memory
-      protection. If the driver callback function doesn't behave well,
-      the whole VM will misbehave.</p>
-      <list>
-	<item><p>A driver callback that crash will crash the whole VM.</p></item>
-	<item><p>An erroneously implemented driver callback might cause
-	a VM internal state inconsistency which may cause a crash of the VM,
-	or miscellaneous misbehaviors of the VM at any point after the call
-	to the driver callback.</p></item>
-	<item><p>A driver callback that do <seealso marker="#lengthy_work">lengthy
-	work</seealso> before returning will degrade responsiveness of the VM,
-	and may cause miscellaneous strange behaviors. Such strange behaviors
-	include, but are not limited to, extreme memory usage, and bad load
-	balancing between schedulers. Strange behaviors that might occur due
-	to lengthy work may also vary between OTP releases.</p></item>
+        native code of the VM. Execution is not made in a safe environment.
+        The VM <em>cannot</em> provide the same services as provided when
+        executing Erlang code, such as pre-emptive scheduling or memory
+        protection. If the driver callback function does not behave well,
+        the whole VM will misbehave.</p>
+      <list type="bulleted">
+        <item>
+          <p>A driver callback that crash will crash the whole VM.</p>
+        </item>
+        <item>
+          <p>An erroneously implemented driver callback can cause a VM
+            internal state inconsistency, which can cause a crash of the VM,
+            or miscellaneous misbehaviors of the VM at any point after the
+            call to the driver callback.</p>
+        </item>
+        <item>
+          <p>A driver callback doing
+            <seealso marker="#lengthy_work">lengthy work</seealso> before
+            returning degrades responsiveness of the VM and can cause
+            miscellaneous strange behaviors. Such strange behaviors
+            include, but are not limited to, extreme memory usage and bad
+            load balancing between schedulers. Strange behaviors that can
+            occur because of lengthy work can also vary between Erlang/OTP
+            releases.</p>
+        </item>
       </list>
-      </warning>
-    <p>As of erts version 5.5.3 the driver interface has been extended
-      (see <seealso marker="driver_entry#extended_marker">extended marker</seealso>).
-      The extended interface introduce
+    </warning>
+
+    <p>As from <c>ERTS</c> 5.5.3 the driver interface has been extended
+      (see <seealso marker="driver_entry#extended_marker">
+      <c>extended marker</c></seealso>). The extended interface introduces
       <seealso marker="#version_management">version management</seealso>,
-      the possibility to pass capability flags
-      (see <seealso marker="driver_entry#driver_flags">driver flags</seealso>)
-      to the runtime system at driver initialization, and some new
-      driver API functions.      </p>
+      the possibility to pass capability flags (see
+      <seealso marker="driver_entry#driver_flags">
+      <c>driver_flags</c></seealso>) to the runtime system at driver
+      initialization, and some new driver API functions.</p>
+
     <note>
-      <p>As of erts version 5.9 old drivers have to be recompiled
-      and have to use the extended interface. They also have to be
-      adjusted to the
-      <seealso marker="#rewrites_for_64_bits">64-bit capable driver interface.
-      </seealso>
-      </p>
+      <p>As from <c>ERTS</c> 5.9 old drivers must be recompiled
+        and use the extended interface. They must also be adjusted to the
+        <seealso marker="#rewrites_for_64_bits">
+        64-bit capable driver interface</seealso>.</p>
     </note>
+
     <p>The driver calls back to the emulator, using the API
       functions declared in <c>erl_driver.h</c>. They are used for
-      outputting data from the driver, using timers, etc.</p>
+      outputting data from the driver, using timers, and so on.</p>
+
     <p>Each driver instance is associated with a port. Every port
       has a port owner process. Communication with the port is normally
       done through the port owner process. Most of the functions take
       the <c>port</c> handle as an argument. This identifies the driver
-      instance. Note that this port handle must be stored by the driver,
+      instance. Notice that this port handle must be stored by the driver,
       it is not given when the driver is called from the emulator (see
-      <seealso marker="driver_entry#emulator">driver_entry</seealso>).</p>
+      <seealso marker="driver_entry#emulator">
+      <c>driver_entry</c></seealso>).</p>
+
     <p>Some of the functions take a parameter of type
-      <c>ErlDrvBinary</c>, a driver binary. It should be both
+      <c>ErlDrvBinary</c>, a driver binary. It is to be both
       allocated and freed by the caller. Using a binary directly avoids
       one extra copying of data.</p>
+
     <p>Many of the output functions have a "header buffer", with
       <c>hbuf</c> and <c>hlen</c> parameters. This buffer is sent as a
       list before the binary (or list, depending on port mode) that is
       sent. This is convenient when matching on messages received from
-      the port. (Although in the latest versions of Erlang, there is
-      the binary syntax, that enables you to match on the beginning of
+      the port. (Although in the latest Erlang versions there is
+      the binary syntax, which enables you to match on the beginning of
       a binary.)
-            <marker id="smp_support"></marker>
-</p>
+
+    <marker id="smp_support"></marker></p>
     <p>In the runtime system with SMP support, drivers are locked either
       on driver level or port level (driver instance level). By default
-      driver level locking will be used, i.e., only one emulator thread
+      driver level locking will be used, that is, only one emulator thread
       will execute code in the driver at a time. If port level locking
-      is used, multiple emulator threads may execute code in the driver
-      at the same time. There will only be one thread at a time calling
-      driver call-backs corresponding to the same port, though. In order
-      to enable port level locking set the <c>ERL_DRV_FLAG_USE_PORT_LOCKING</c>
+      is used, multiple emulator threads can execute code in the driver
+      at the same time. Only one thread at a time will call
+      driver callbacks corresponding to the same port, though.
+      To enable port level locking, set the <c>ERL_DRV_FLAG_USE_PORT_LOCKING</c>
       <seealso marker="driver_entry#driver_flags">driver flag</seealso> in
-      the <seealso marker="driver_entry">driver_entry</seealso>
-      used by the driver. When port level locking is used it is the
-      responsibility of the driver writer to synchronize all accesses
+      the <seealso marker="driver_entry"><c>driver_entry</c></seealso>
+      used by the driver. When port level locking is used,
+      the driver writer is responsible for synchronizing all accesses
       to data shared by the ports (driver instances).</p>
+
     <p>Most drivers written before the runtime system with SMP
-      support existed will be able to run in the runtime system
-      with SMP support without being rewritten if driver
+      support existed can run in the runtime system
+      with SMP support, without being rewritten, if driver
       level locking is used.</p>
+
     <note>
       <p>It is assumed that drivers do not access other drivers. If
-        drivers should access each other they have to provide their own
-        mechanism for thread safe synchronization. Such "inter driver
+        drivers access each other, they must provide their own
+        mechanism for thread-safe synchronization. Such "inter-driver
         communication" is strongly discouraged.</p>
     </note>
+
     <p>Previously, in the runtime system without SMP support,
-      specific driver call-backs were always called from the same
+      specific driver callbacks were always called from the same
       thread. This is <em>not</em> the case in the runtime system
       with SMP support. Regardless of locking scheme used, calls
-      to driver call-backs may be made from different threads, e.g.,
-      two consecutive calls to exactly the same call-back for exactly
-      the same port may be made from two different threads. This
-      will for <em>most</em> drivers not be a problem, but it might.
-      Drivers that depend on all call-backs being called in the
-      same thread, <em>have</em> to be rewritten before being used
+      to driver callbacks can be made from different threads. For example,
+      two consecutive calls to exactly the same callback for exactly
+      the same port can be made from two different threads. This
+      is for <em>most</em> drivers not a problem, but it can be.
+      Drivers that depend on all callbacks that are called in the
+      same thread, <em>must</em> be rewritten before they are used
       in the runtime system with SMP support.</p>
+
     <note>
       <p>Regardless of locking scheme used, calls to driver
-        call-backs may be made from different threads.</p>
+        callbacks can be made from different threads.</p>
     </note>
-    <p>Most functions in this API are <em>not</em> thread-safe, i.e.,
-      they may <em>not</em> be called from an arbitrary thread. Functions
-      that are not documented as thread-safe may only be called from
-      driver call-backs or function calls descending from a driver
-      call-back call. Note that driver call-backs may be called from
+
+    <p>Most functions in this API are <em>not</em> thread-safe, that is,
+      they <em>cannot</em> be called from any thread. Functions
+      that are not documented as thread-safe can only be called from
+      driver callbacks or function calls descending from a driver
+      callback call. Notice that driver callbacks can be called from
       different threads. This, however, is not a problem for any
-      function in this API, since the emulator has control over
+      function in this API, as the emulator has control over
       these threads.</p>
+
     <warning>
-      <p>Functions not explicitly documented as thread safe are
-        <em>not</em> thread safe. Also note that some functions
-        are <em>only</em> thread safe when used in a runtime
+      <p>Functions not explicitly documented as thread-safe are
+        <em>not</em> thread safe. Also notice that some functions
+        are <em>only</em> thread-safe when used in a runtime
         system with SMP support.</p>
-      <p>A function not explicitly documented as thread safe may at
-         some point in time have a thread safe implementation in the
-	 runtime system. Such an implementation may however change to
-	 a thread <em>unsafe</em> implementation at any time <em>without
-	 any notice</em> at all.
-      </p>
-      <p><em>Only use functions explicitly documented as thread safe
-         from arbitrary threads.</em></p>
+      <p>A function not explicitly documented as thread-safe can, at
+        some point in time, have a thread-safe implementation in the
+        runtime system. Such an implementation can however change to
+        a thread <em>unsafe</em> implementation at any time <em>without
+        any notice</em>.</p>
+      <p><em>Only use functions explicitly documented as thread-safe
+        from arbitrary threads.</em></p>
     </warning>
-     <p><marker id="lengthy_work"/>
-     As mentioned in the <seealso marker="#WARNING">warning</seealso> text at
-     the beginning of this document it is of vital importance that a driver callback
-     does return relatively fast. It is hard to give an exact maximum amount
-     of time that a driver callback is allowed to work, but as a rule of thumb
-     a well behaving driver callback should return before a millisecond has
-     passed. This can be achieved using different approaches.
-     If you have full control over the code that are to execute in the driver
-     callback, the best approach is to divide the work into multiple chunks of
-     work and trigger multiple calls to the
-     <seealso marker="driver_entry#timeout">timeout callback</seealso> using
-     zero timeouts. The
-     <seealso marker="#erl_drv_consume_timeslice"><c>erl_drv_consume_timeslice()</c></seealso>
-     function can be useful in order to determine when to trigger such
-     timeout callback calls. It might, however, not always be possible to
-     implement it this way, e.g. when calling third party libraries. In this
-     case you typically want to dispatch the work to another thread.
-     Information about thread primitives can be found below.</p>
+
+    <p><marker id="lengthy_work"/>
+      As mentioned in the <seealso marker="#WARNING">warning</seealso> text at
+      the beginning of this section, it is of vital importance that a driver
+      callback returns relatively fast. It is difficult to give an exact
+      maximum amount of time that a driver callback is allowed to work, but
+      usually a well-behaving driver callback is to return within 1 millisecond.
+      This can be achieved using different approaches.
+      If you have full control over the code to execute in the driver
+      callback, the best approach is to divide the work into multiple chunks of
+      work, and trigger multiple calls to the
+      <seealso marker="driver_entry#timeout">time-out callback</seealso> using
+      zero time-outs. Function <seealso marker="#erl_drv_consume_timeslice">
+      <c>erl_drv_consume_timeslice</c></seealso> can be useful to
+      determine when to trigger such time-out callback calls. However, sometimes
+      it cannot be implemented this way, for example when calling
+      third-party libraries. In this case, you typically want to dispatch the
+      work to another thread. Information about thread primitives is provided
+      below.</p>
   </description>
 
   <section>
-    <title>FUNCTIONALITY</title>
+    <title>Functionality</title>
     <p>All functions that a driver needs to do with Erlang are
-      performed through driver API functions. There are functions
+      performed through driver API functions. Functions exist
       for the following functionality:</p>
+
     <taglist>
       <tag>Timer functions</tag>
-      <item>Timer functions are used to control the timer that a driver
-       may use. The timer will have the emulator call the
-       <seealso marker="driver_entry#timeout">timeout</seealso> entry
-       function after a specified time. Only one timer is available
-       for each driver instance.</item>
+      <item>
+        <p>Control the timer that a driver can use. The timer has the
+          emulator call the <seealso marker="driver_entry#timeout">
+          <c>timeout</c></seealso> entry function after a specified time.
+          Only one timer is available for each driver instance.</p>
+      </item>
       <tag>Queue handling</tag>
       <item>
         <p>Every driver instance has an associated queue. This queue is a
-          <c>SysIOVec</c> that works as a buffer. It's mostly used for
-          the driver to buffer data that should be written to a device,
+          <c>SysIOVec</c>, which works as a buffer. It is mostly used for
+          the driver to buffer data that is to be written to a device,
           it is a byte stream. If the port owner process closes the
-          driver, and the queue is not empty, the driver will not be
+          driver, and the queue is not empty, the driver is not
           closed. This enables the driver to flush its buffers before
           closing.</p>
-        <p>The queue can be manipulated from arbitrary threads if
-          a port data lock is used. See documentation of the
-          <seealso marker="#ErlDrvPDL">ErlDrvPDL</seealso> type for
-          more information.</p>
+        <p>The queue can be manipulated from any threads if
+          a port data lock is used. For more information, see
+          <seealso marker="#ErlDrvPDL"><c>ErlDrvPDL</c></seealso>.</p>
       </item>
       <tag>Output functions</tag>
-      <item>With the output functions, the driver sends data back to
-       the emulator. They will be received as messages by the port owner
-       process, see <c>open_port/2</c>. The vector function and the
-       function taking a driver binary are faster, because they avoid
-       copying the data buffer. There is also a fast way of sending
-       terms from the driver, without going through the binary term
-       format.</item>
+      <item>
+        <p>With these functions, the driver sends data back to the emulator.
+          The data is received as messages by the port owner process, see
+          <seealso marker="erlang:open_port/2">
+          <c>erlang:open_port/2</c></seealso>. The vector function and the
+          function taking a driver binary are faster, as they avoid
+          copying the data buffer. There is also a fast way of sending
+          terms from the driver, without going through the binary term
+          format.</p></item>
       <tag>Failure</tag>
-      <item>The driver can exit and signal errors up to Erlang. This is
-       only for severe errors, when the driver can't possibly keep
-       open.</item>
+      <item>
+        <p>The driver can exit and signal errors up to Erlang. This is
+          only for severe errors, when the driver cannot possibly keep
+          open.</p>
+      </item>
       <tag>Asynchronous calls</tag>
-      <item>The latest Erlang versions (R7B and later) has provision for
-       asynchronous function calls, using a thread pool provided by
-       Erlang. There is also a select call, that can be used for
-       asynchronous drivers.</item>
+      <item>
+        <p>Erlang/OTP R7B and later versions have provision for
+          asynchronous function calls, using a thread pool provided by
+          Erlang. There is also a select call, which can be used for
+          asynchronous drivers.</p>
+      </item>
       <tag><marker id="multi_threading"/>Multi-threading</tag>
       <item>
-      <p>A POSIX thread like API for multi-threading is provided. The
-         Erlang driver thread API only provide a subset of the functionality
-	 provided by the POSIX thread API. The subset provided is
-	 more or less the basic functionality needed for multi-threaded
-	 programming:
-      </p>
-      <list>
-	 <item><seealso marker="#ErlDrvTid">Threads</seealso></item>
-	 <item><seealso marker="#ErlDrvMutex">Mutexes</seealso></item>
-	 <item><seealso marker="#ErlDrvCond">Condition variables</seealso></item>
-	 <item><seealso marker="#ErlDrvRWLock">Read/Write locks</seealso></item>
-	 <item><seealso marker="#ErlDrvTSDKey">Thread specific data</seealso></item>
-      </list>
-      <p>The Erlang driver thread API can be used in conjunction with
-         the POSIX thread API on UN-ices and with the Windows native thread
-	 API on Windows. The Erlang driver thread API has the advantage of
-	 being portable, but there might exist situations where you want to
-	 use functionality from the POSIX thread API or the Windows
-	 native thread API.
-      </p>
-      <p>The Erlang driver thread API only returns error codes when it is
-         reasonable to recover from an error condition. If it isn't reasonable
-	 to recover from an error condition, the whole runtime system is
-	 terminated. For example, if a create mutex operation fails, an error
-	 code is returned, but if a lock operation on a mutex fails, the
-	 whole runtime system is terminated.
-      </p>
-      <p>Note that there exists no "condition variable wait with timeout" in
-         the Erlang driver thread API. This is due to issues with
-	 <c>pthread_cond_timedwait()</c>. When the system clock suddenly
-	 is changed, it isn't always guaranteed that you will wake up from
-	 the call as expected. An Erlang runtime system has to be able to
-	 cope with sudden changes of the system clock. Therefore, we have
-	 omitted it from the Erlang driver thread API. In the Erlang driver
-	 case, timeouts can and should be handled with the timer functionality
-	 of the Erlang driver API.
-      </p>
-      <p>In order for the Erlang driver thread API to function, thread
-         support has to be enabled in the runtime system. An Erlang driver
-	 can check if thread support is enabled by use of
-	 <seealso marker="#driver_system_info">driver_system_info()</seealso>.
-	 Note that some functions in the Erlang driver API are thread-safe
-	 only when the runtime system has SMP support, also this
-	 information can be retrieved via
-	 <seealso marker="#driver_system_info">driver_system_info()</seealso>.
-	 Also note that a lot of functions in the Erlang driver API are
-	 <em>not</em> thread-safe regardless of whether SMP support is
-	 enabled or not. If a function isn't documented as thread-safe it
-	 is <em>not</em> thread-safe.
-      </p>
-      <p><em>NOTE</em>: When executing in an emulator thread, it is
-         <em>very important</em> that you unlock <em>all</em> locks you
-	 have locked before letting the thread out of your control;
-	 otherwise, you are <em>very likely</em> to deadlock the whole
-	 emulator. If you need to use thread specific data in an emulator
-	 thread, only have the thread specific data set while the thread is
-	 under your control, and clear the thread specific data before
-	 you let the thread out of your control.
-      </p>
-      <p>In the future there will probably be debug functionality
-         integrated with the Erlang driver thread API. All functions
-	 that create entities take a <c>name</c> argument. Currently
-	 the <c>name</c> argument is unused, but it will be used when
-	 the debug functionality has been implemented. If you name all
-	 entities created well, the debug functionality will be able
-	 to give you better error reports.
-      </p>
+        <p>A POSIX thread like API for multi-threading is provided. The
+          Erlang driver thread API only provides a subset of the functionality
+          provided by the POSIX thread API. The subset provided is
+          more or less the basic functionality needed for multi-threaded
+          programming:</p>
+        <list>
+          <item><seealso marker="#ErlDrvTid">Threads</seealso></item>
+          <item><seealso marker="#ErlDrvMutex">Mutexes</seealso></item>
+          <item><seealso marker="#ErlDrvCond">
+            Condition variables</seealso></item>
+          <item><seealso marker="#ErlDrvRWLock">
+            Read/write locks</seealso></item>
+          <item><seealso marker="#ErlDrvTSDKey">
+           Thread-specific data</seealso></item>
+        </list>
+        <p>The Erlang driver thread API can be used in conjunction with
+          the POSIX thread API on UN-ices and with the Windows native thread
+          API on Windows. The Erlang driver thread API has the advantage of
+          being portable, but there can exist situations where you want to
+          use functionality from the POSIX thread API or the Windows
+          native thread API.</p>
+        <p>The Erlang driver thread API only returns error codes when it is
+          reasonable to recover from an error condition. If it is not reasonable
+          to recover from an error condition, the whole runtime system is
+          terminated. For example, if a create mutex operation fails, an error
+          code is returned, but if a lock operation on a mutex fails, the
+          whole runtime system is terminated.</p>
+        <p>Notice that there is no "condition variable wait with time-out" in
+          the Erlang driver thread API. This because of issues with
+          <c>pthread_cond_timedwait</c>. When the system clock suddenly
+          is changed, it is not always guaranteed that you will wake up from
+          the call as expected. An Erlang runtime system must be able to
+          cope with sudden changes of the system clock. Therefore, we have
+          omitted it from the Erlang driver thread API. In the Erlang driver
+          case, time-outs can and are to be handled with the timer functionality
+          of the Erlang driver API.</p>
+        <p>In order for the Erlang driver thread API to function, thread
+          support must be enabled in the runtime system. An Erlang driver
+          can check if thread support is enabled by use of
+          <seealso marker="#driver_system_info">
+          <c>driver_system_info</c></seealso>.
+          Notice that some functions in the Erlang driver API are thread-safe
+          only when the runtime system has SMP support, also this
+          information can be retrieved through
+          <seealso marker="#driver_system_info">
+          <c>driver_system_info</c></seealso>.
+          Also notice that many functions in the Erlang driver API are
+          <em>not</em> thread-safe, regardless of whether SMP support is
+          enabled or not. If a function is not documented as thread-safe, it
+          is <em>not</em> thread-safe.</p>
+        <note>
+          <p>When executing in an emulator thread, it is
+            <em>very important</em> that you unlock <em>all</em> locks you
+            have locked before letting the thread out of your control;
+            otherwise you are <em>very likely</em> to deadlock the whole
+            emulator.</p>
+          <p>If you need to use thread-specific data in an emulator
+            thread, only have the thread-specific data set while the thread is
+            under your control, and clear the thread-specific data before
+            you let the thread out of your control.</p>
+        </note>
+        <p>In the future, debug functionality will probably be
+          integrated with the Erlang driver thread API. All functions
+          that create entities take a <c>name</c> argument. Currently
+          the <c>name</c> argument is unused, but it will be used when
+          the debug functionality is implemented. If you name all
+          entities created well, the debug functionality will be able
+          to give you better error reports.</p>
+      </item>
+      <tag>Adding/removing drivers</tag>
+      <item>
+        <p>A driver can add and later remove drivers.</p>
       </item>
-      <tag>Adding / removing drivers</tag>
-      <item><p>A driver can add and later remove drivers.</p></item>
       <tag>Monitoring processes</tag>
-      <item><p>A driver can monitor a process that does not own a port.</p></item>
+      <item>
+        <p>A driver can monitor a process that does not own a port.</p>
+      </item>
       <tag><marker id="version_management"/>Version management</tag>
       <item>
         <p>Version management is enabled for drivers that have set the
-          <seealso marker="driver_entry#extended_marker">extended_marker</seealso>
-          field of their
-          <seealso marker="driver_entry">driver_entry</seealso>
-          to <c>ERL_DRV_EXTENDED_MARKER</c>. <c>erl_driver.h</c> defines
-          <c>ERL_DRV_EXTENDED_MARKER</c>,
-          <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c>, and
-          <c>ERL_DRV_EXTENDED_MINOR_VERSION</c>.
-          <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c> will be incremented when
-          driver incompatible changes are made to the Erlang runtime
-          system. Normally it will suffice to recompile drivers when the
-          <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c> has changed, but it
-          could, under rare circumstances, mean that drivers have to
-          be slightly modified. If so, this will of course be documented.
-          <c>ERL_DRV_EXTENDED_MINOR_VERSION</c> will be incremented when
-          new features are added. The runtime system uses the minor version
-          of the driver to determine what features to use.
-          The runtime system will normally refuse to load a driver if the major
+          <seealso marker="driver_entry#extended_marker">
+          <c>extended_marker</c></seealso> field of their
+          <seealso marker="driver_entry"><c>driver_entry</c></seealso>
+          to <c>ERL_DRV_EXTENDED_MARKER</c>. <c>erl_driver.h</c> defines:</p>
+        <list type="bulleted">
+          <item>
+            <p><c>ERL_DRV_EXTENDED_MARKER</c></p>
+          </item>
+          <item>
+            <p><c>ERL_DRV_EXTENDED_MAJOR_VERSION</c>, which is incremented when
+              driver incompatible changes are made to the Erlang runtime
+              system. Normally it suffices to recompile drivers when
+              <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c> has changed, but it
+              can, under rare circumstances, mean that drivers must
+              be slightly modified. If so, this will of course be
+              documented.</p>
+          </item>
+          <item>
+            <p><c>ERL_DRV_EXTENDED_MINOR_VERSION</c>, which is incremented when
+              new features are added. The runtime system uses the minor version
+              of the driver to determine what features to use.</p>
+          </item>
+        </list>
+        <p>The runtime system normally refuses to load a driver if the major
           versions differ, or if the major versions are equal and the
           minor version used by the driver is greater than the one used
           by the runtime system. Old drivers with lower major versions
-	  will however be allowed after a bump of the major version during
-	  a transition period of two major releases. Such old drivers might
-	  however fail if deprecated features are used.</p>
-	<p>The emulator will refuse to load a driver that does not use
-	  the extended driver interface,
-	  to allow for 64-bit capable drivers,
-	  since incompatible type changes for the callbacks
-	  <seealso marker="driver_entry#output">output</seealso>,
-	  <seealso marker="driver_entry#control">control</seealso> and
-	  <seealso marker="driver_entry#call">call</seealso>
-	  were introduced in release R15B. A driver written
-	  with the old types would compile with warnings and when
-	  called return garbage sizes to the emulator causing it
-	  to read random memory and create huge incorrect result blobs.</p>
-	<p>Therefore it is not enough to just recompile drivers written with
-	  version management for pre-R15B types; the types have to be changed
-	  in the driver suggesting other rewrites especially regarding
-	  size variables. Investigate all warnings when recompiling!</p>
-	<p>Also, the API driver functions <c>driver_output*</c>,
-	  <c>driver_vec_to_buf</c>, <c>driver_alloc/realloc*</c>
-	  and the <c>driver_*</c> queue functions were changed to have
-	  larger length arguments and return values. This is a
-	  lesser problem since code that passes smaller types
-	  will get them auto converted in the calls and as long as
-	  the driver does not handle sizes that overflow an <c>int</c>
-	  all will work as before.</p>
+          are however allowed after a bump of the major version during
+          a transition period of two major releases. Such old drivers can,
+          however, fail if deprecated features are used.</p>
+        <p>The emulator refuses to load a driver that does not use
+          the extended driver interface, to allow for 64-bit capable drivers,
+          as incompatible type changes for the callbacks
+          <seealso marker="driver_entry#output"><c>output</c></seealso>,
+          <seealso marker="driver_entry#control"><c>control</c></seealso>, and
+          <seealso marker="driver_entry#call"><c>call</c></seealso>
+          were introduced in Erlang/OTP R15B. A driver written
+          with the old types would compile with warnings and when
+          called return garbage sizes to the emulator, causing it
+          to read random memory and create huge incorrect result blobs.</p>
+        <p>Therefore it is not enough to only recompile drivers written with
+          version management for pre R15B types; the types must be changed
+          in the driver suggesting other rewrites, especially regarding size
+          variables. <em>Investigate all warnings when recompiling.</em></p>
+        <p>Also, the API driver functions <c>driver_output*</c> and
+          <c>driver_vec_to_buf</c>, <c>driver_alloc/realloc*</c>, and the
+          <c>driver_*</c> queue functions were changed to have
+          larger length arguments and return values. This is a
+          lesser problem, as code that passes smaller types
+          gets them auto-converted in the calls, and as long as
+          the driver does not handle sizes that overflow an <c>int</c>,
+          all will work as before.</p>
       </item>
-      <tag><marker id="time_measurement"/>Time Measurement</tag>
-      <item><p>Support for time measurement in drivers:</p>
-      <list>
-	<item><seealso marker="#ErlDrvTime"><c>ErlDrvTime</c></seealso></item>
-	<item><seealso marker="#ErlDrvTimeUnit"><c>ErlDrvTimeUnit</c></seealso></item>
-	<item><seealso marker="#erl_drv_monotonic_time"><c>erl_drv_monotonic_time()</c></seealso></item>
-	<item><seealso marker="#erl_drv_time_offset"><c>erl_drv_time_offset()</c></seealso></item>
-	<item><seealso marker="#erl_drv_convert_time_unit"><c>erl_drv_convert_time_unit()</c></seealso></item>
-      </list>
+      <tag><marker id="time_measurement"/>Time measurement</tag>
+      <item>
+        <p>Support for time measurement in drivers:</p>
+        <list type="bulleted">
+          <item><seealso marker="#ErlDrvTime">
+            <c>ErlDrvTime</c></seealso></item>
+          <item><seealso marker="#ErlDrvTimeUnit">
+            <c>ErlDrvTimeUnit</c></seealso></item>
+          <item><seealso marker="#erl_drv_monotonic_time">
+            <c>erl_drv_monotonic_time</c></seealso></item>
+          <item><seealso marker="#erl_drv_time_offset">
+            <c>erl_drv_time_offset</c></seealso></item>
+          <item><seealso marker="#erl_drv_convert_time_unit">
+            <c>erl_drv_convert_time_unit</c></seealso></item>
+        </list>
       </item>
     </taglist>
   </section>
 
   <section>
     <marker id="rewrites_for_64_bits"/>
-    <title>
-      REWRITES FOR 64-BIT DRIVER INTERFACE
-    </title>
-    <p>
-      For erts-5.9 two new integer types
-      <seealso marker="#ErlDrvSizeT">ErlDrvSizeT</seealso> and
-      <seealso marker="#ErlDrvSSizeT">ErlDrvSSizeT</seealso>
-      were introduced that can hold 64-bit sizes if necessary.
-    </p>
-    <p>
-      To not update a driver and just recompile it probably works
+    <title>Rewrites for 64-Bit Driver Interface</title>
+    <p><c>ERTS</c> 5.9 introduced two new integer types,
+      <seealso marker="#ErlDrvSizeT"><c>ErlDrvSizeT</c></seealso> and
+      <seealso marker="#ErlDrvSSizeT"><c>ErlDrvSSizeT</c></seealso>,
+      which can hold 64-bit sizes if necessary.</p>
+
+    <p>To not update a driver and only recompile, it probably works
       when building for a 32-bit machine creating a false sense of security.
       Hopefully that will generate many important warnings.
-      But when recompiling the same driver later on for a 64-bit machine
+      But when recompiling the same driver later on for a 64-bit machine,
       there <em>will</em> be warnings and almost certainly crashes.
-      So it is a BAD idea to postpone updating the driver and
-      not fixing the warnings!
-    </p>
-    <p>
-      When recompiling with <c>gcc</c> use the <c>-Wstrict-prototypes</c>
-      flag to get better warnings. Try to find a similar flag if you
-      are using some other compiler.
-    </p>
-    <p>
-      Here follows a checklist for rewriting a pre erts-5.9 driver,
-      most important first.
-    </p>
+      So it is a <em>bad</em> idea to postpone updating the driver and
+      not fixing the warnings.</p>
+
+    <p>When recompiling with <c>gcc</c>, use flag <c>-Wstrict-prototypes</c>
+      to get better warnings. Try to find a similar flag if you use
+      another compiler.</p>
+
+    <p>The following is a checklist for rewriting a pre <c>ERTS</c> 5.9 driver,
+      most important first:</p>
+
     <taglist>
       <tag>Return types for driver callbacks</tag>
       <item>
-	<p>
-	  Rewrite driver callback
+	<p>Rrewrite driver callback
 	  <seealso marker="driver_entry#control"><c>control</c></seealso>
-	  to use return type <c>ErlDrvSSizeT</c> instead of <c>int</c>.
-	</p>
-	<p>
-	  Rewrite driver callback
+	  to use return type <c>ErlDrvSSizeT</c> instead of <c>int</c>.</p>
+	<p>Rewrite driver callback
 	  <seealso marker="driver_entry#call"><c>call</c></seealso>
-	  to use return type <c>ErlDrvSSizeT</c> instead of <c>int</c>.
-	</p>
+	  to use return type <c>ErlDrvSSizeT</c> instead of <c>int</c>.</p>
 	<note>
-	  <p>
-	    These changes are essential to not crash the emulator
+	  <p>These changes are essential not to crash the emulator
 	    or worse cause malfunction.
-	    Without them a driver may return garbage in the high 32 bits
-	    to the emulator causing it to build a huge result from random
-	    bytes either crashing on memory allocation or succeeding with
-	    a random result from the driver call.
-	  </p>
+	    Without them a driver can return garbage in the high 32 bits
+	    to the emulator, causing it to build a huge result from random
+	    bytes, either crashing on memory allocation or succeeding with
+	    a random result from the driver call.</p>
 	</note>
       </item>
       <tag>Arguments to driver callbacks</tag>
       <item>
-	<p>
-	  Driver callback
+	<p>Driver callback
 	  <seealso marker="driver_entry#output"><c>output</c></seealso>
 	  now gets <c>ErlDrvSizeT</c> as 3rd argument instead
-	  of previously <c>int</c>.
-	</p>
-	<p>
-	  Driver callback
+	  of previously <c>int</c>.</p>
+	<p>Driver callback
 	  <seealso marker="driver_entry#control"><c>control</c></seealso>
 	  now gets <c>ErlDrvSizeT</c> as 4th and 6th arguments instead
-	  of previously <c>int</c>.
-	</p>
-	<p>
-	  Driver callback
+	  of previously <c>int</c>.</p>
+	<p>Driver callback
 	  <seealso marker="driver_entry#call"><c>call</c></seealso>
 	  now gets <c>ErlDrvSizeT</c> as 4th and 6th arguments instead
-	  of previously <c>int</c>.
-	</p>
-	<p>
-	  Sane compiler's calling conventions probably make these changes
+	  of previously <c>int</c>.</p>
+	<p>Sane compiler's calling conventions probably make these changes
 	  necessary only for a driver to handle data chunks that require
-	  64-bit size fields (mostly larger than 2 GB since that is what
+	  64-bit size fields (mostly larger than 2 GB, as that is what
 	  an <c>int</c> of 32 bits can hold). But it is possible to think
 	  of non-sane calling conventions that would make the driver
-	  callbacks mix up the arguments causing malfunction.
-	</p>
+	  callbacks mix up the arguments causing malfunction.</p>
 	<note>
-	  <p>
-	    The argument type change is from signed to unsigned which
-	    may cause problems for e.g. loop termination conditions or
-	    error conditions if you just change the types all over the place.
-	  </p>
+	  <p>The argument type change is from signed to unsigned. This
+	    can cause problems for, for example, loop termination conditions or
+	    error conditions if you only change the types all over the place.
+          </p>
 	</note>
       </item>
       <tag>Larger <c>size</c> field in <c>ErlIOVec</c></tag>
       <item>
-	<p>
-	  The <c>size</c> field in
+	<p>The <c>size</c> field in
 	  <seealso marker="#ErlIOVec"><c>ErlIOVec</c></seealso>
 	  has been changed to <c>ErlDrvSizeT</c> from <c>int</c>.
-	  Check all code that use that field.
-	</p>
-	<p>
-	  Automatic type casting probably makes these changes necessary only
-	  for a driver that encounters sizes larger than 32 bits.
-	</p>
+	  Check all code that use that field.</p>
+	<p>Automatic type-casting probably makes these changes necessary only
+	  for a driver that encounters sizes &gt; 32 bits.</p>
 	<note>
-	  <p>
-	    The <c>size</c> field changed from signed to unsigned which
-	    may cause problems for e.g. loop termination conditions or
-	    error conditions if you just change the types all over the place.
-	  </p>
+	  <p>The <c>size</c> field changed from signed to unsigned. This
+	    can cause problems for, for example, loop termination conditions or
+	    error conditions if you only change the types all over the place.
+          </p>
 	</note>
       </item>
       <tag>Arguments and return values in the driver API</tag>
       <item>
-	<p>
-	  Many driver API functions have changed argument type
+	<p>Many driver API functions have changed argument type
 	  and/or return value to <c>ErlDrvSizeT</c> from mostly <c>int</c>.
-	  Automatic type casting probably makes these changes necessary only
-	  for a driver that encounters sizes larger than 32 bits.
-	</p>
+	  Automatic type-casting probably makes these changes necessary only
+	  for a driver that encounters sizes &gt; 32 bits.</p>
 	<taglist>
-	  <tag><seealso marker="#driver_output">driver_output</seealso></tag>
+	  <tag><seealso marker="#driver_output">
+            <c>driver_output</c></seealso></tag>
 	  <item>3rd argument</item>
-	  <tag><seealso marker="#driver_output2">driver_output2</seealso></tag>
+	  <tag><seealso marker="#driver_output2">
+            <c>driver_output2</c></seealso></tag>
 	  <item>3rd and 5th arguments</item>
-	  <tag>
-	  <seealso marker="#driver_output_binary">driver_output_binary</seealso>
-	  </tag>
-	  <item>3rd 5th and 6th arguments</item>
-	  <tag><seealso marker="#driver_outputv">driver_outputv</seealso></tag>
+	  <tag><seealso marker="#driver_output_binary">
+            <c>driver_output_binary</c></seealso></tag>
+	  <item>3rd, 5th, and 6th arguments</item>
+	  <tag><seealso marker="#driver_outputv">
+            <c>driver_outputv</c></seealso></tag>
 	  <item>3rd and 5th arguments</item>
-	  <tag>
-	  <seealso marker="#driver_vec_to_buf">driver_vec_to_buf</seealso>
-	  </tag>
+	  <tag><seealso marker="#driver_vec_to_buf">
+            <c>driver_vec_to_buf</c></seealso></tag>
 	  <item>3rd argument and return value</item>
-	  <tag><seealso marker="#driver_alloc">driver_alloc</seealso></tag>
+	  <tag><seealso marker="#driver_alloc">
+            <c>driver_alloc</c></seealso></tag>
 	  <item>1st argument</item>
-	  <tag><seealso marker="#driver_realloc">driver_realloc</seealso></tag>
+	  <tag><seealso marker="#driver_realloc">
+            <c>driver_realloc</c></seealso></tag>
 	  <item>2nd argument</item>
-	  <tag>
-	  <seealso marker="#driver_alloc_binary">driver_alloc_binary</seealso>
-	  </tag>
+	  <tag><seealso marker="#driver_alloc_binary">
+            <c>driver_alloc_binary</c></seealso></tag>
 	  <item>1st argument</item>
-	  <tag>
-	  <seealso marker="#driver_realloc_binary">driver_realloc_binary</seealso>
-	  </tag>
+	  <tag><seealso marker="#driver_realloc_binary">
+            <c>driver_realloc_binary</c></seealso></tag>
 	  <item>2nd argument</item>
-	  <tag><seealso marker="#driver_enq">driver_enq</seealso></tag>
+	  <tag><seealso marker="#driver_enq">
+            <c>driver_enq</c></seealso></tag>
 	  <item>3rd argument</item>
-	  <tag><seealso marker="#driver_pushq">driver_pushq</seealso></tag>
+	  <tag><seealso marker="#driver_pushq">
+            <c>driver_pushq</c></seealso></tag>
 	  <item>3rd argument</item>
-	  <tag><seealso marker="#driver_deq">driver_deq</seealso></tag>
+	  <tag><seealso marker="#driver_deq">
+            <c>driver_deq</c></seealso></tag>
 	  <item>2nd argument and return value</item>
-	  <tag><seealso marker="#driver_sizeq">driver_sizeq</seealso></tag>
-	  <item>return value</item>
-	  <tag><seealso marker="#driver_enq_bin">driver_enq_bin</seealso></tag>
-	  <item>3rd and 4th argument</item>
-	  <tag><seealso marker="#driver_pushq_bin">driver_pushq_bin</seealso></tag>
-	  <item>3rd and 4th argument</item>
-	  <tag><seealso marker="#driver_enqv">driver_enqv</seealso></tag>
+	  <tag><seealso marker="#driver_sizeq">
+            <c>driver_sizeq</c></seealso></tag>
+	  <item>Return value</item>
+	  <tag><seealso marker="#driver_enq_bin">
+            <c>driver_enq_bin</c></seealso></tag>
+	  <item>3rd and 4th arguments</item>
+	  <tag><seealso marker="#driver_pushq_bin">
+            <c>driver_pushq_bin</c></seealso></tag>
+	  <item>3rd and 4th arguments</item>
+	  <tag><seealso marker="#driver_enqv">
+            <c>driver_enqv</c></seealso></tag>
 	  <item>3rd argument</item>
-	  <tag><seealso marker="#driver_pushqv">driver_pushqv</seealso></tag>
+	  <tag><seealso marker="#driver_pushqv">
+            <c>driver_pushqv</c></seealso></tag>
 	  <item>3rd argument</item>
-	  <tag><seealso marker="#driver_peekqv">driver_peekqv</seealso></tag>
-	  <item>return value</item>
+	  <tag><seealso marker="#driver_peekqv">
+            <c>driver_peekqv</c></seealso></tag>
+	  <item>Return value</item>
 	</taglist>
 	<note>
-	  <p>
-	    This is a change from signed to unsigned which
-	    may cause problems for e.g. loop termination conditions and
-	    error conditions if you just change the types all over the place.
-	  </p>
+	  <p>This is a change from signed to unsigned. This can cause
+	    problems for, for example, loop termination conditions and error
+	    conditions if you only change the types all over the place.</p>
 	</note>
       </item>
     </taglist>
   </section>
 
   <section>
-    <title>DATA TYPES</title>
-
+    <title>Data Types</title>
     <taglist>
-      <tag><marker id="ErlDrvSizeT"/>ErlDrvSizeT</tag>
-      <item><p>An unsigned integer type to be used as <c>size_t</c></p></item>
-      <tag><marker id="ErlDrvSSizeT"/>ErlDrvSSizeT</tag>
-      <item><p>A signed integer type the size of <c>ErlDrvSizeT</c></p></item>
-      <tag><marker id="ErlDrvSysInfo"/>ErlDrvSysInfo</tag>
+      <tag><marker id="ErlDrvSizeT"/><c>ErlDrvSizeT</c></tag>
+      <item>
+        <p>An unsigned integer type to be used as <c>size_t</c>.</p>
+      </item>
+      <tag><marker id="ErlDrvSSizeT"/><c>ErlDrvSSizeT</c></tag>
       <item>
-      <p/>
-      <code type="none">
+        <p>A signed integer type, the size of <c>ErlDrvSizeT</c>.</p>
+      </item>
+      <tag><marker id="ErlDrvSysInfo"/><c>ErlDrvSysInfo</c></tag>
+      <item>
+        <code type="none">
 typedef struct ErlDrvSysInfo {
    int driver_major_version;
    int driver_minor_version;
@@ -558,390 +584,422 @@ typedef struct ErlDrvSysInfo {
    int nif_major_version;
    int nif_minor_version;
    int dirty_scheduler_support;
-} ErlDrvSysInfo;
-      </code>
-
-      <p>
-        The <c>ErlDrvSysInfo</c> structure is used for storage of
-        information about the Erlang runtime system.
-        <seealso marker="#driver_system_info">driver_system_info()</seealso>
-        will write the system information when passed a reference to
-        a <c>ErlDrvSysInfo</c> structure. A description of the
-        fields in the structure follows:
-      </p>
-      <taglist>
-        <tag><c>driver_major_version</c></tag>
-        <item>The value of
-          <seealso marker="#version_management">ERL_DRV_EXTENDED_MAJOR_VERSION</seealso>
-           when the runtime system was compiled. This value is the same
-           as the value of
-          <seealso marker="#version_management">ERL_DRV_EXTENDED_MAJOR_VERSION</seealso>
-           used when compiling the driver; otherwise, the runtime system
-           would have refused to load the driver.
-        </item>
-        <tag><c>driver_minor_version</c></tag>
-        <item>The value of
-          <seealso marker="#version_management">ERL_DRV_EXTENDED_MINOR_VERSION</seealso>
-           when the runtime system was compiled. This value might differ
-           from the value of
-          <seealso marker="#version_management">ERL_DRV_EXTENDED_MINOR_VERSION</seealso>
-           used when compiling the driver.
-        </item>
-        <tag><c>erts_version</c></tag>
-        <item>A string containing the version number of the runtime system
-           (the same as returned by
-          <seealso marker="erlang#system_info_version">erlang:system_info(version)</seealso>).
-        </item>
-        <tag><c>otp_release</c></tag>
-        <item>A string containing the OTP release number
-           (the same as returned by
-          <seealso marker="erlang#system_info_otp_release">erlang:system_info(otp_release)</seealso>).
-        </item>
-        <tag><c>thread_support</c></tag>
-        <item>A value <c>!= 0</c> if the runtime system has thread support;
-           otherwise, <c>0</c>.
-        </item>
-        <tag><c>smp_support</c></tag>
-        <item>A value <c>!= 0</c> if the runtime system has SMP support;
-           otherwise, <c>0</c>.
-        </item>
-        <tag><c>async_threads</c></tag>
-        <item>The number of async threads in the async thread pool used
-           by <seealso marker="#driver_async">driver_async()</seealso>
-           (the same as returned by
-          <seealso marker="erlang#system_info_thread_pool_size">erlang:system_info(thread_pool_size)</seealso>).
-        </item>
-        <tag><c>scheduler_threads</c></tag>
-        <item>The number of scheduler threads used by the runtime system
-           (the same as returned by
-          <seealso marker="erlang#system_info_schedulers">erlang:system_info(schedulers)</seealso>).
-        </item>
-        <tag><c>nif_major_version</c></tag>
-        <item>The value of <c>ERL_NIF_MAJOR_VERSION</c> when the runtime system was compiled.
-        </item>
-        <tag><c>nif_minor_version</c></tag>
-        <item>The value of <c>ERL_NIF_MINOR_VERSION</c> when the runtime system was compiled.
-        </item>
-        <tag><c>dirty_scheduler_support</c></tag>
-        <item>A value <c>!= 0</c> if the runtime system has support for dirty scheduler threads;
-	  otherwise <c>0</c>.
-        </item>
+} ErlDrvSysInfo;</code>
+        <p>The <c>ErlDrvSysInfo</c> structure is used for storage of
+          information about the Erlang runtime system.
+          <seealso marker="#driver_system_info">
+          <c>driver_system_info</c></seealso>
+          writes the system information when passed a reference to
+          a <c>ErlDrvSysInfo</c> structure. The fields in the structure
+          are as follows:</p>
+        <taglist>
+          <tag><c>driver_major_version</c></tag>
+          <item>
+            <p>The value of <seealso marker="#version_management">
+              <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c></seealso>
+              when the runtime system was compiled. This value is the same
+              as the value of <seealso marker="#version_management">
+              <c>ERL_DRV_EXTENDED_MAJOR_VERSION</c></seealso>
+              used when compiling the driver; otherwise the runtime system
+              would have refused to load the driver.</p>
+          </item>
+          <tag><c>driver_minor_version</c></tag>
+          <item>
+            <p>The value of <seealso marker="#version_management">
+              <c>ERL_DRV_EXTENDED_MINOR_VERSION</c></seealso>
+              when the runtime system was compiled. This value can differ
+              from the value of <seealso marker="#version_management">
+              <c>ERL_DRV_EXTENDED_MINOR_VERSION</c></seealso>
+              used when compiling the driver.</p>
+          </item>
+          <tag><c>erts_version</c></tag>
+          <item>
+            <p>A string containing the version number of the runtime system
+              (the same as returned by
+              <seealso marker="erlang#system_info_version">
+              <c>erlang:system_info(version)</c></seealso>).</p>
+          </item>
+          <tag><c>otp_release</c></tag>
+          <item>
+            <p>A string containing the OTP release number
+              (the same as returned by
+              <seealso marker="erlang#system_info_otp_release">
+              <c>erlang:system_info(otp_release)</c></seealso>).</p>
+          </item>
+          <tag><c>thread_support</c></tag>
+          <item>
+            <p>A value <c>!= 0</c> if the runtime system has thread support;
+              otherwise <c>0</c>.</p>
+          </item>
+          <tag><c>smp_support</c></tag>
+          <item>
+            <p>A value <c>!= 0</c> if the runtime system has SMP support;
+              otherwise <c>0</c>.</p>
+          </item>
+          <tag><c>async_threads</c></tag>
+          <item>
+            <p>The number of async threads in the async thread pool used by
+              <seealso marker="#driver_async"><c>driver_async</c></seealso>
+              (the same as returned by
+              <seealso marker="erlang#system_info_thread_pool_size">
+              <c>erlang:system_info(thread_pool_size)</c></seealso>).</p>
+          </item>
+          <tag><c>scheduler_threads</c></tag>
+          <item>
+            <p>The number of scheduler threads used by the runtime system
+              (the same as returned by
+              <seealso marker="erlang#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso>).</p>
+          </item>
+          <tag><c>nif_major_version</c></tag>
+          <item>
+            <p>The value of <c>ERL_NIF_MAJOR_VERSION</c> when the runtime
+              system was compiled.</p>
+          </item>
+          <tag><c>nif_minor_version</c></tag>
+            <item>
+              <p>The value of <c>ERL_NIF_MINOR_VERSION</c> when the runtime
+                system was compiled.</p>
+          </item>
+          <tag><c>dirty_scheduler_support</c></tag>
+          <item>
+            <p>A value <c>!= 0</c> if the runtime system has support for dirty
+              scheduler threads; otherwise <c>0</c>.</p>
+          </item>
         </taglist>
       </item>
-      <tag><marker id="ErlDrvBinary"/>ErlDrvBinary</tag>
+      <tag><marker id="ErlDrvBinary"/><c>ErlDrvBinary</c></tag>
       <item>
-      <p/>
-      <code type="none">
+        <code type="none">
 typedef struct ErlDrvBinary {
    ErlDrvSint orig_size;
    char orig_bytes[];
-} ErlDrvBinary;
-</code>
+} ErlDrvBinary;</code>
         <p>The <c>ErlDrvBinary</c> structure is a binary, as sent
           between the emulator and the driver. All binaries are
           reference counted; when <c>driver_binary_free</c> is called,
           the reference count is decremented, when it reaches zero,
-          the binary is deallocated. The <c>orig_size</c> is the size
-          of the binary, and <c>orig_bytes</c> is the buffer. The
-          <c>ErlDrvBinary</c> does not have a fixed size, its size is
+          the binary is deallocated. <c>orig_size</c> is the binary size
+          and <c>orig_bytes</c> is the buffer.
+          <c>ErlDrvBinary</c> has not a fixed size, its size is
           <c>orig_size + 2 * sizeof(int)</c>.</p>
         <note>
           <p>The <c>refc</c> field has been removed. The reference count of
             an <c>ErlDrvBinary</c> is now stored elsewhere. The
-            reference count of an <c>ErlDrvBinary</c> can be accessed via
-            <seealso marker="#driver_binary_get_refc">driver_binary_get_refc()</seealso>,
-            <seealso marker="#driver_binary_inc_refc">driver_binary_inc_refc()</seealso>,
-            and
-            <seealso marker="#driver_binary_dec_refc">driver_binary_dec_refc()</seealso>.</p>
+            reference count of an <c>ErlDrvBinary</c> can be accessed through
+            <seealso marker="#driver_binary_get_refc">
+            <c>driver_binary_get_refc</c></seealso>,
+            <seealso marker="#driver_binary_inc_refc">
+            <c>driver_binary_inc_refc</c></seealso>, and
+            <seealso marker="#driver_binary_dec_refc">
+            <c>driver_binary_dec_refc</c></seealso>.</p>
         </note>
         <p>Some driver calls, such as <c>driver_enq_binary</c>,
           increment the driver reference count, and others, such as
           <c>driver_deq</c> decrement it.</p>
-        <p>Using a driver binary instead of a normal buffer, is often
-          faster, since the emulator doesn't need to copy the data,
+        <p>Using a driver binary instead of a normal buffer is often
+          faster, as the emulator needs not to copy the data,
           only the pointer is used.</p>
         <p>A driver binary allocated in the driver, with
-          <c>driver_alloc_binary</c>, should be freed in the driver (unless otherwise stated),
-          with <c>driver_free_binary</c>. (Note that this doesn't
+          <c>driver_alloc_binary</c>, is to be freed in the driver
+          (unless otherwise stated)
+          with <c>driver_free_binary</c>. (Notice that this does not
           necessarily deallocate it, if the driver is still referred
           in the emulator, the ref-count will not go to zero.)</p>
         <p>Driver binaries are used in the <c>driver_output2</c> and
           <c>driver_outputv</c> calls, and in the queue. Also the
-          driver call-back <seealso marker="driver_entry#outputv">outputv</seealso> uses driver
-          binaries.</p>
-        <p>If the driver for some reason or another, wants to keep a
-          driver binary around, in a static variable for instance, the
-          reference count should be incremented,
-          and the binary can later be freed in the <seealso marker="driver_entry#stop">stop</seealso> call-back, with
-          <c>driver_free_binary</c>.</p>
-        <p>Note that since a driver binary is shared by the driver and
-          the emulator, a binary received from the emulator or sent to
-          the emulator, must not be changed by the driver.</p>
-        <p>Since erts version 5.5 (OTP release R11B), orig_bytes is
+          driver callback <seealso marker="driver_entry#outputv">
+          <c>outputv</c></seealso> uses driver binaries.</p>
+        <p>If the driver for some reason wants to keep a
+          driver binary around, for example in a static variable, the
+          reference count is to be incremented, and the binary can later
+          be freed in the <seealso marker="driver_entry#stop">
+          <c>stop</c></seealso> callback, with <c>driver_free_binary</c>.</p>
+        <p>Notice that as a driver binary is shared by the driver and
+          the emulator. A binary received from the emulator or sent to
+          the emulator must not be changed by the driver.</p>
+        <p>Since <c>ERTS</c> 5.5 (Erlang/OTP R11B), <c>orig_bytes</c> is
           guaranteed to be properly aligned for storage of an array of
           doubles (usually 8-byte aligned).</p>
       </item>
-      <tag>ErlDrvData</tag>
+      <tag><c>ErlDrvData</c></tag>
       <item>
-        <p>The <c>ErlDrvData</c> is a handle to driver-specific data,
-          passed to the driver call-backs. It is a pointer, and is
+        <p>A handle to driver-specific data,
+          passed to the driver callbacks. It is a pointer, and is
           most often type cast to a specific pointer in the driver.</p>
       </item>
-      <tag>SysIOVec</tag>
+      <tag><c>SysIOVec</c></tag>
       <item>
-        <p>This is a system I/O vector, as used by <c>writev</c> on
-          unix and <c>WSASend</c> on Win32. It is used in
+        <p>A system I/O vector, as used by <c>writev</c> on
+          Unix and <c>WSASend</c> on Win32. It is used in
           <c>ErlIOVec</c>.</p>
       </item>
-      <tag><marker id="ErlIOVec"/>ErlIOVec</tag>
+      <tag><marker id="ErlIOVec"/><c>ErlIOVec</c></tag>
       <item>
-      <p/>
-      <code type="none">
+        <code type="none">
 typedef struct ErlIOVec {
   int vsize;
   ErlDrvSizeT size;
   SysIOVec* iov;
   ErlDrvBinary** binv;
-} ErlIOVec;
-</code>
-        <p>The I/O vector used by the emulator and drivers, is a list
+} ErlIOVec;</code>
+        <p>The I/O vector used by the emulator and drivers is a list
           of binaries, with a <c>SysIOVec</c> pointing to the buffers
           of the binaries. It is used in <c>driver_outputv</c> and the
-          <seealso marker="driver_entry#outputv">outputv</seealso>
-          driver call-back. Also, the driver queue is an
+          <seealso marker="driver_entry#outputv"><c>outputv</c></seealso>
+          driver callback. Also, the driver queue is an
           <c>ErlIOVec</c>.</p>
       </item>
-
-      <tag>ErlDrvMonitor</tag>
+      <tag><c>ErlDrvMonitor</c></tag>
       <item>
         <p>When a driver creates a monitor for a process, a
           <c>ErlDrvMonitor</c> is filled in. This is an opaque
-          data-type which can be assigned to but not compared without
-          using the supplied compare function (i.e. it behaves like a struct).</p>
-        <p>The driver writer should provide the memory for storing the
-          monitor when calling <seealso marker="#driver_monitor_process">driver_monitor_process</seealso>. The
+          data type that can be assigned to, but not compared without
+          using the supplied compare function (that is, it behaves like
+          a struct).</p>
+        <p>The driver writer is to provide the memory for storing the
+          monitor when calling <seealso marker="#driver_monitor_process">
+          <c>driver_monitor_process</c></seealso>. The
           address of the data is not stored outside of the driver, so
-          the <c>ErlDrvMonitor</c> can be used as any other datum, it
-          can be copied, moved in memory, forgotten etc.</p>
+          <c>ErlDrvMonitor</c> can be used as any other data, it
+          can be copied, moved in memory, forgotten, and so on.</p>
       </item>
-      <tag><marker id="ErlDrvNowData"/>ErlDrvNowData</tag>
+      <tag><marker id="ErlDrvNowData"/><c>ErlDrvNowData</c></tag>
       <item>
-        <p>The <c>ErlDrvNowData</c> structure holds a timestamp
+        <p>The <c>ErlDrvNowData</c> structure holds a time stamp
           consisting of three values measured from some arbitrary
           point in the past. The three structure members are:</p>
         <taglist>
-          <tag>megasecs</tag>
+          <tag><c>megasecs</c></tag>
           <item>The number of whole megaseconds elapsed since the arbitrary
-           point in time</item>
-          <tag>secs</tag>
+            point in time</item>
+          <tag><c>secs</c></tag>
           <item>The number of whole seconds elapsed since the arbitrary
-           point in time</item>
-          <tag>microsecs</tag>
+            point in time</item>
+          <tag><c>microsecs</c></tag>
           <item>The number of whole microseconds elapsed since the arbitrary
-           point in time</item>
+            point in time</item>
         </taglist>
       </item>
-      <tag><marker id="ErlDrvPDL"/>ErlDrvPDL</tag>
+      <tag><marker id="ErlDrvPDL"/><c>ErlDrvPDL</c></tag>
       <item>
-        <p>If certain port specific data have to be accessed from other
-          threads than those calling the driver call-backs, a port data lock
-          can be used in order to synchronize the operations on the data.
-          Currently, the only port specific data that the emulator
+        <p>If certain port-specific data must be accessed from other
+          threads than those calling the driver callbacks, a port data lock
+          can be used to synchronize the operations on the data.
+          Currently, the only port-specific data that the emulator
           associates with the port data lock is the driver queue.</p>
-        <p>Normally a driver instance does not have a port data lock. If
-          the driver instance wants to use a port data lock, it has to
+        <p>Normally a driver instance has no port data lock. If
+          the driver instance wants to use a port data lock, it must
           create the port data lock by calling
-          <seealso marker="#driver_pdl_create">driver_pdl_create()</seealso>.
-          <em>NOTE</em>: Once the port data lock has been created, every
-          access to data associated with the port data lock has to be done
-          while having the port data lock locked. The port data lock is
-          locked, and unlocked, respectively, by use of
-          <seealso marker="#driver_pdl_lock">driver_pdl_lock()</seealso>, and
-          <seealso marker="#driver_pdl_unlock">driver_pdl_unlock()</seealso>.</p>
+          <seealso marker="#driver_pdl_create">
+          <c>driver_pdl_create</c></seealso>.</p>
+        <note>
+          <p>Once the port data lock has been created, every
+            access to data associated with the port data lock must be done
+            while the port data lock is locked. The port data lock is
+            locked and unlocked by
+            <seealso marker="#driver_pdl_lock">
+            <c>driver_pdl_lock</c></seealso>, and
+            <seealso marker="#driver_pdl_unlock">
+            <c>driver_pdl_unlock</c></seealso>, respectively.</p>
+        </note>
         <p>A port data lock is reference counted, and when the reference
-          count reaches zero, it will be destroyed. The emulator will at
-          least increment the reference count once when the lock is
-          created and decrement it once when the port associated with
-          the lock terminates. The emulator will also increment the
-          reference count when an async job is enqueued and decrement
-          it after an async job has been invoked. Besides
-          this, it is the responsibility of the driver to ensure that
+          count reaches zero, it is destroyed. The emulator at
+          least increments the reference count once when the lock is
+          created and decrements it once the port associated with
+          the lock terminates. The emulator also increments the
+          reference count when an async job is enqueued and decrements
+          it when an async job has been invoked.
+          Also, the driver is responsible for ensuring that
           the reference count does not reach zero before the last use
           of the lock by the driver has been made. The reference count
-          can be read, incremented, and decremented, respectively, by
-          use of
-          <seealso marker="#driver_pdl_get_refc">driver_pdl_get_refc()</seealso>,
-          <seealso marker="#driver_pdl_inc_refc">driver_pdl_inc_refc()</seealso>, and
-          <seealso marker="#driver_pdl_dec_refc">driver_pdl_dec_refc()</seealso>.</p>
+          can be read, incremented, and decremented by
+          <seealso marker="#driver_pdl_get_refc">
+          <c>driver_pdl_get_refc</c></seealso>,
+          <seealso marker="#driver_pdl_inc_refc">
+          <c>driver_pdl_inc_refc</c></seealso>, and
+          <seealso marker="#driver_pdl_dec_refc">
+          <c>driver_pdl_dec_refc</c></seealso>, respectively.</p>
       </item>
-
-      <tag><marker id="ErlDrvTid"/>ErlDrvTid</tag>
+      <tag><marker id="ErlDrvTid"/><c>ErlDrvTid</c></tag>
       <item>
         <p>Thread identifier.</p>
-	<p>See also:
-	   <seealso marker="#erl_drv_thread_create">erl_drv_thread_create()</seealso>,
-	   <seealso marker="#erl_drv_thread_exit">erl_drv_thread_exit()</seealso>,
-	   <seealso marker="#erl_drv_thread_join">erl_drv_thread_join()</seealso>,
-	   <seealso marker="#erl_drv_thread_self">erl_drv_thread_self()</seealso>,
-	   and
-	   <seealso marker="#erl_drv_equal_tids">erl_drv_equal_tids()</seealso>.
-	</p>
+	<p>See also <seealso marker="#erl_drv_thread_create">
+           <c>erl_drv_thread_create</c></seealso>,
+	   <seealso marker="#erl_drv_thread_exit">
+           <c>erl_drv_thread_exit</c></seealso>,
+	   <seealso marker="#erl_drv_thread_join">
+           <c>erl_drv_thread_join</c></seealso>,
+	   <seealso marker="#erl_drv_thread_self">
+           <c>erl_drv_thread_self</c></seealso>, and
+	   <seealso marker="#erl_drv_equal_tids">
+           <c>erl_drv_equal_tids</c></seealso>.</p>
       </item>
-      <tag><marker id="ErlDrvThreadOpts"/>ErlDrvThreadOpts</tag>
+      <tag><marker id="ErlDrvThreadOpts"/><c>ErlDrvThreadOpts</c></tag>
       <item>
-      <p/>
-      <code type="none">
-	int suggested_stack_size;
-      </code>
+        <code type="none">
+int suggested_stack_size;</code>
         <p>Thread options structure passed to
-	   <seealso marker="#erl_drv_thread_create">erl_drv_thread_create()</seealso>.
-	   Currently the following fields exist:
-	</p>
+	  <seealso marker="#erl_drv_thread_create">
+            <c>erl_drv_thread_create</c></seealso>.
+	    The following fields exists:</p>
         <taglist>
-          <tag>suggested_stack_size</tag>
-          <item>A suggestion, in kilo-words, on how large a stack to use. A value less
-	        than zero means default size.
+          <tag><c>suggested_stack_size</c></tag>
+          <item>A suggestion, in kilowords, on how large a stack to use.
+            A value &lt; 0 means default size.
 	  </item>
         </taglist>
-	<p>See also:
-	   <seealso marker="#erl_drv_thread_opts_create">erl_drv_thread_opts_create()</seealso>,
-	   <seealso marker="#erl_drv_thread_opts_destroy">erl_drv_thread_opts_destroy()</seealso>,
-	   and
-	   <seealso marker="#erl_drv_thread_create">erl_drv_thread_create()</seealso>.
-	</p>
+	<p>See also <seealso marker="#erl_drv_thread_opts_create">
+	  <c>erl_drv_thread_opts_create</c></seealso>,
+	  <seealso marker="#erl_drv_thread_opts_destroy">
+	  <c>erl_drv_thread_opts_destroy</c></seealso>, and
+	  <seealso marker="#erl_drv_thread_create">
+	  <c>erl_drv_thread_create</c></seealso>.</p>
       </item>
-
-      <tag><marker id="ErlDrvMutex"/>ErlDrvMutex</tag>
+      <tag><marker id="ErlDrvMutex"/><c>ErlDrvMutex</c></tag>
       <item>
         <p>Mutual exclusion lock. Used for synchronizing access to shared data.
-	   Only one thread at a time can lock a mutex.
-	</p>
-	<p>See also:
-	   <seealso marker="#erl_drv_mutex_create">erl_drv_mutex_create()</seealso>,
-	   <seealso marker="#erl_drv_mutex_destroy">erl_drv_mutex_destroy()</seealso>,
-	   <seealso marker="#erl_drv_mutex_lock">erl_drv_mutex_lock()</seealso>,
-	   <seealso marker="#erl_drv_mutex_trylock">erl_drv_mutex_trylock()</seealso>,
-	   and
-	   <seealso marker="#erl_drv_mutex_unlock">erl_drv_mutex_unlock()</seealso>.
-	</p>
+	   Only one thread at a time can lock a mutex.</p>
+	<p>See also <seealso marker="#erl_drv_mutex_create">
+          <c>erl_drv_mutex_create</c></seealso>,
+	  <seealso marker="#erl_drv_mutex_destroy">
+	  <c>erl_drv_mutex_destroy</c></seealso>,
+	  <seealso marker="#erl_drv_mutex_lock">
+	  <c>erl_drv_mutex_lock</c></seealso>,
+	  <seealso marker="#erl_drv_mutex_trylock">
+	  <c>erl_drv_mutex_trylock</c></seealso>, and
+	  <seealso marker="#erl_drv_mutex_unlock">
+	  <c>erl_drv_mutex_unlock</c></seealso>.</p>
       </item>
-      <tag><marker id="ErlDrvCond"/>ErlDrvCond</tag>
+      <tag><marker id="ErlDrvCond"/><c>ErlDrvCond</c></tag>
       <item>
-        <p>Condition variable. Used when threads need to wait for a specific
-	   condition to appear before continuing execution. Condition variables
-	   need to be used with associated mutexes.
-	</p>
-	<p>See also:
-	   <seealso marker="#erl_drv_cond_create">erl_drv_cond_create()</seealso>,
-	   <seealso marker="#erl_drv_cond_destroy">erl_drv_cond_destroy()</seealso>,
-	   <seealso marker="#erl_drv_cond_signal">erl_drv_cond_signal()</seealso>,
-	   <seealso marker="#erl_drv_cond_broadcast">erl_drv_cond_broadcast()</seealso>,
-	   and
-	   <seealso marker="#erl_drv_cond_wait">erl_drv_cond_wait()</seealso>.
-	</p>
+        <p>Condition variable. Used when threads must wait for a specific
+	  condition to appear before continuing execution. Condition variables
+	  must be used with associated mutexes.</p>
+	<p>See also <seealso marker="#erl_drv_cond_create">
+	  <c>erl_drv_cond_create</c></seealso>,
+	  <seealso marker="#erl_drv_cond_destroy">
+	  <c>erl_drv_cond_destroy</c></seealso>,
+	  <seealso marker="#erl_drv_cond_signal">
+	  <c>erl_drv_cond_signal</c></seealso>,
+	  <seealso marker="#erl_drv_cond_broadcast">
+	  <c>erl_drv_cond_broadcast</c></seealso>, and
+	  <seealso marker="#erl_drv_cond_wait">
+	  <c>erl_drv_cond_wait</c></seealso>.</p>
       </item>
-      <tag><marker id="ErlDrvRWLock"/>ErlDrvRWLock</tag>
+      <tag><marker id="ErlDrvRWLock"/><c>ErlDrvRWLock</c></tag>
       <item>
         <p>Read/write lock. Used to allow multiple threads to read shared data
-	   while only allowing one thread to write the same data. Multiple threads
-	   can read lock an rwlock at the same time, while only one thread can
-	   read/write lock an rwlock at a time.
-	</p>
-	<p>See also:
-	   <seealso marker="#erl_drv_rwlock_create">erl_drv_rwlock_create()</seealso>,
-	   <seealso marker="#erl_drv_rwlock_destroy">erl_drv_rwlock_destroy()</seealso>,
-	   <seealso marker="#erl_drv_rwlock_rlock">erl_drv_rwlock_rlock()</seealso>,
-	   <seealso marker="#erl_drv_rwlock_tryrlock">erl_drv_rwlock_tryrlock()</seealso>,
-	   <seealso marker="#erl_drv_rwlock_runlock">erl_drv_rwlock_runlock()</seealso>,
-	   <seealso marker="#erl_drv_rwlock_rwlock">erl_drv_rwlock_rwlock()</seealso>,
-	   <seealso marker="#erl_drv_rwlock_tryrwlock">erl_drv_rwlock_tryrwlock()</seealso>,
-	   and
-	   <seealso marker="#erl_drv_rwlock_rwunlock">erl_drv_rwlock_rwunlock()</seealso>.
-	</p>
+	  while only allowing one thread to write the same data. Multiple
+	  threads can read lock an rwlock at the same time, while only
+	  one thread can read/write lock an rwlock at a time.</p>
+	<p>See also <seealso marker="#erl_drv_rwlock_create">
+	  <c>erl_drv_rwlock_create</c></seealso>,
+	  <seealso marker="#erl_drv_rwlock_destroy">
+	  <c>erl_drv_rwlock_destroy</c></seealso>,
+	  <seealso marker="#erl_drv_rwlock_rlock">
+	  <c>erl_drv_rwlock_rlock</c></seealso>,
+	  <seealso marker="#erl_drv_rwlock_tryrlock">
+	  <c>erl_drv_rwlock_tryrlock</c></seealso>,
+	  <seealso marker="#erl_drv_rwlock_runlock">
+	  <c>erl_drv_rwlock_runlock</c></seealso>,
+	  <seealso marker="#erl_drv_rwlock_rwlock">
+	  <c>erl_drv_rwlock_rwlock</c></seealso>,
+	  <seealso marker="#erl_drv_rwlock_tryrwlock">
+	  <c>erl_drv_rwlock_tryrwlock</c></seealso>, and
+	  <seealso marker="#erl_drv_rwlock_rwunlock">
+	  <c>erl_drv_rwlock_rwunlock</c></seealso>.</p>
       </item>
-      <tag><marker id="ErlDrvTSDKey"/>ErlDrvTSDKey</tag>
+      <tag><marker id="ErlDrvTSDKey"/><c>ErlDrvTSDKey</c></tag>
       <item>
-        <p>Key which thread specific data can be associated with.</p>
-	<p>See also:
-	   <seealso marker="#erl_drv_tsd_key_create">erl_drv_tsd_key_create()</seealso>,
-	   <seealso marker="#erl_drv_tsd_key_destroy">erl_drv_tsd_key_destroy()</seealso>,
-	   <seealso marker="#erl_drv_tsd_set">erl_drv_tsd_set()</seealso>,
-	   and
-	   <seealso marker="#erl_drv_tsd_get">erl_drv_tsd_get()</seealso>.
-	</p>
+        <p>Key that thread-specific data can be associated with.</p>
+	<p>See also <seealso marker="#erl_drv_tsd_key_create">
+	  <c>erl_drv_tsd_key_create</c></seealso>,
+	  <seealso marker="#erl_drv_tsd_key_destroy">
+	  <c>erl_drv_tsd_key_destroy</c></seealso>,
+	  <seealso marker="#erl_drv_tsd_set">
+	  <c>erl_drv_tsd_set</c></seealso>, and
+	  <seealso marker="#erl_drv_tsd_get">
+	  <c>erl_drv_tsd_get</c></seealso>.</p>
       </item>
-      <tag><marker id="ErlDrvTime"/>ErlDrvTime</tag>
+      <tag><marker id="ErlDrvTime"/><c>ErlDrvTime</c></tag>
       <item>
-        <p>A signed 64-bit integer type for representation of time.</p>
+        <p>A signed 64-bit integer type for time representation.</p>
       </item>
-      <tag><marker id="ErlDrvTimeUnit"/>ErlDrvTimeUnit</tag>
+      <tag><marker id="ErlDrvTimeUnit"/><c>ErlDrvTimeUnit</c></tag>
       <item>
         <p>An enumeration of time units supported by the driver API:</p>
-	<taglist>
+        <taglist>
 	  <tag><c>ERL_DRV_SEC</c></tag>
-	  <item><p>Seconds</p></item>
+	  <item>Seconds</item>
 	  <tag><c>ERL_DRV_MSEC</c></tag>
-	  <item><p>Milliseconds</p></item>
+	  <item>Milliseconds</item>
 	  <tag><c>ERL_DRV_USEC</c></tag>
-	  <item><p>Microseconds</p></item>
+	  <item>Microseconds</item>
 	  <tag><c>ERL_DRV_NSEC</c></tag>
-	  <item><p>Nanoseconds</p></item>
-	</taglist>
+	  <item>Nanoseconds</item>
+        </taglist>
       </item>
-     </taglist>
-   </section>
+    </taglist>
+  </section>
 
   <funcs>
     <func>
-      <name><ret>void</ret><nametext>add_driver_entry(ErlDrvEntry *de)</nametext></name>
-      <fsummary>Add a driver entry</fsummary>
+      <name><ret>void</ret><nametext>add_driver_entry(ErlDrvEntry
+        *de)</nametext></name>
+      <fsummary>Add a driver entry.</fsummary>
       <desc>
         <marker id="add_driver_entry"></marker>
-        <p>This function adds a driver entry to the list of drivers
-          known by Erlang. The <seealso marker="driver_entry#init">init</seealso> function of the <c>de</c>
-          parameter is called.</p>
+        <p>Adds a driver entry to the list of drivers known by Erlang.
+          The <seealso marker="driver_entry#init"><c>init</c></seealso>
+          function of parameter <c>de</c> is called.</p>
         <note>
           <p>To use this function for adding drivers residing in
             dynamically loaded code is dangerous. If the driver code
             for the added driver resides in the same dynamically
-            loaded module (i.e. <c>.so</c> file) as a normal
+            loaded module (that is, <c>.so</c> file) as a normal
             dynamically loaded driver (loaded with the <c>erl_ddll</c>
-            interface), the caller should call <seealso marker="#driver_lock_driver">driver_lock_driver</seealso> before
+            interface), the caller is to call
+            <seealso marker="#driver_lock_driver">
+            <c>driver_lock_driver</c></seealso> before
             adding driver entries.</p>
-          <p>Use of this function is generally deprecated.</p>
+          <p><em>Use of this function is generally deprecated.</em></p>
         </note>
       </desc>
     </func>
 
     <func>
-      <name><ret>void *</ret><nametext>driver_alloc(ErlDrvSizeT size)</nametext></name>
-      <fsummary>Allocate memory</fsummary>
+      <name><ret>void *</ret>
+        <nametext>driver_alloc(ErlDrvSizeT size)</nametext></name>
+      <fsummary>Allocate memory.</fsummary>
       <desc>
         <marker id="driver_alloc"></marker>
-        <p>This function allocates a memory block of the size specified
-          in <c>size</c>, and returns it. This only fails on out of
-          memory, in that case <c>NULL</c> is returned. (This is most
+        <p>Allocates a memory block of the size specified
+          in <c>size</c>, and returns it. This fails only on out of
+          memory, in which case <c>NULL</c> is returned. (This is most
           often a wrapper for <c>malloc</c>).</p>
         <p>Memory allocated must be explicitly freed with a corresponding
-           call to <c>driver_free</c> (unless otherwise stated).</p>
+          call to <c>driver_free</c> (unless otherwise stated).</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvBinary *</ret><nametext>driver_alloc_binary(ErlDrvSizeT size)</nametext></name>
-      <fsummary>Allocate a driver binary</fsummary>
+      <name><ret>ErlDrvBinary *</ret>
+        <nametext>driver_alloc_binary(ErlDrvSizeT size)</nametext></name>
+      <fsummary>Allocate a driver binary.</fsummary>
       <desc>
         <marker id="driver_alloc_binary"></marker>
-        <p>This function allocates a driver binary with a memory block
+        <p>Allocates a driver binary with a memory block
           of at least <c>size</c> bytes, and returns a pointer to it,
-          or NULL on failure (out of memory). When a driver binary has
-          been sent to the emulator, it must not be altered. Every
-          allocated binary should be freed by a corresponding call to
-          <c>driver_free_binary</c> (unless otherwise stated).</p>
-        <p>Note that a driver binary has an internal reference counter,
-          this means that calling <c>driver_free_binary</c> it may not
-          actually dispose of it. If it's sent to the emulator, it may
+          or <c>NULL</c> on failure (out of memory). When a driver binary has
+          been sent to the emulator, it must not be changed. Every
+          allocated binary is to be freed by a corresponding call to
+          <seealso marker="#driver_free_binary">
+          <c>driver_free_binary</c></seealso> (unless otherwise stated).</p>
+        <p>Notice that a driver binary has an internal reference counter.
+          This means that calling <c>driver_free_binary</c>, it may not
+          actually dispose of it. If it is sent to the emulator, it can
           be referenced there.</p>
         <p>The driver binary has a field, <c>orig_bytes</c>, which
           marks the start of the data in the binary.</p>
@@ -950,94 +1008,97 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>long</ret><nametext>driver_async (ErlDrvPort port, unsigned int* key, void (*async_invoke)(void*), void* async_data, void (*async_free)(void*))</nametext></name>
-      <fsummary>Perform an asynchronous call within a driver</fsummary>
+      <name><ret>long</ret><nametext>driver_async (ErlDrvPort port, unsigned
+        int* key, void (*async_invoke)(void*), void* async_data, void
+        (*async_free)(void*))</nametext></name>
+      <fsummary>Perform an asynchronous call within a driver.</fsummary>
       <desc>
         <marker id="driver_async"></marker>
-        <p>This function performs an asynchronous call. The function
+        <p>Performs an asynchronous call. The function
           <c>async_invoke</c> is invoked in a thread separate from the
           emulator thread. This enables the driver to perform
           time-consuming, blocking operations without blocking the
           emulator.</p>
-        <p>The async thread pool size can be set with the
-          <seealso marker="erl#async_thread_pool_size">+A</seealso>
-          command line argument of <seealso marker="erl">erl(1)</seealso>.
-          If no async thread pool is available, the call is made
-          synchronously in the thread calling <c>driver_async()</c>. The
+        <p>The async thread pool size can be set with command-line argument
+          <seealso marker="erl#async_thread_pool_size"><c>+A</c></seealso>
+          in <seealso marker="erl"><c>erl(1)</c></seealso>.
+          If an async thread pool is unavailable, the call is made
+          synchronously in the thread calling <c>driver_async</c>. The
           current number of async threads in the async thread pool can be
-          retrieved via
-          <seealso marker="#driver_system_info">driver_system_info()</seealso>.</p>
-        <p>If there is a thread pool available, a thread will be
-          used. If the <c>key</c> argument is null, the threads from the
+          retrieved through <seealso marker="#driver_system_info">
+          <c>driver_system_info</c></seealso>.</p>
+        <p>If a thread pool is available, a thread is used.
+          If argument <c>key</c> is <c>NULL</c>, the threads from the
           pool are used in a round-robin way, each call to
-          <c>driver_async</c> uses the next thread in the pool. With the
-          <c>key</c> argument set, this behaviour is changed. The two
+          <c>driver_async</c> uses the next thread in the pool. With
+          argument <c>key</c> set, this behavior is changed. The two
           same values of <c>*key</c> always get the same thread.</p>
-        <p>To make sure that a driver instance always uses the same
+        <p>To ensure that a driver instance always uses the same
           thread, the following call can be used:</p>
-        <p></p>
         <code type="none"><![CDATA[
-    unsigned int myKey = driver_async_port_key(myPort);
+unsigned int myKey = driver_async_port_key(myPort);
 
-    r = driver_async(myPort, &myKey, myData, myFunc);
-        ]]></code>
+r = driver_async(myPort, &myKey, myData, myFunc);    ]]></code>
         <p>It is enough to initialize <c>myKey</c> once for each
-        driver instance.</p>
-        <p>If a thread is already working, the calls will be
+          driver instance.</p>
+        <p>If a thread is already working, the calls are
           queued up and executed in order. Using the same thread for
-          each driver instance ensures that the calls will be made in
-          sequence.</p>
+          each driver instance ensures that the calls are made in sequence.</p>
         <p>The <c>async_data</c> is the argument to the functions
-          <c>async_invoke</c> and <c>async_free</c>. It's typically a
-          pointer to a structure that contains a pipe or event that
+          <c>async_invoke</c> and <c>async_free</c>. It is typically a
+          pointer to a structure containing a pipe or event that
           can be used to signal that the async operation completed.
-          The data should be freed in <c>async_free</c>.</p>
-        <p>When the async operation is done, <seealso marker="driver_entry#ready_async">ready_async</seealso> driver
-          entry function is called. If <c>ready_async</c> is null in
+          The data is to be freed in <c>async_free</c>.</p>
+        <p>When the async operation is done,
+          <seealso marker="driver_entry#ready_async">
+          <c>ready_async</c></seealso> driver
+          entry function is called. If <c>ready_async</c> is <c>NULL</c> in
           the driver entry, the <c>async_free</c> function is called
           instead.</p>
-        <p>The return value is -1 if the <c>driver_async</c> call
+        <p>The return value is <c>-1</c> if the <c>driver_async</c> call
           fails.</p>
         <note>
-          <p>As of erts version 5.5.4.3 the default stack size for
+          <p>As from <c>ERTS</c> 5.5.4.3 the default stack size for
             threads in the async-thread pool is 16 kilowords,
-            i.e., 64 kilobyte on 32-bit architectures.
-            This small default size has been chosen since the
-            amount of async-threads might be quite large. The
+            that is, 64 kilobyte on 32-bit architectures.
+            This small default size has been chosen because the
+            amount of async-threads can be quite large. The
             default stack size is enough for drivers delivered
-            with Erlang/OTP, but might not be sufficiently large
-            for other dynamically linked in drivers that use the
-            driver_async() functionality. A suggested stack size
+            with Erlang/OTP, but is possibly not sufficiently large
+            for other dynamically linked-in drivers that use the
+            <c>driver_async</c> functionality. A suggested stack size
             for threads in the async-thread pool can be configured
-            via the
-            <seealso marker="erl#async_thread_stack_size">+a</seealso>
-            command line argument of
-            <seealso marker="erl">erl(1)</seealso>.</p>
+            through command-line argument
+            <seealso marker="erl#async_thread_stack_size"><c>+a</c></seealso>
+            in <seealso marker="erl"><c>erl(1)</c></seealso>.</p>
         </note>
       </desc>
     </func>
-<func>
-      <name><ret>unsigned int</ret><nametext>driver_async_port_key (ErlDrvPort port)</nametext></name>
-      <fsummary>Calculate an async key from an ErlDrvPort</fsummary>
+
+    <func>
+      <name><ret>unsigned int</ret><nametext>driver_async_port_key (ErlDrvPort
+        port)</nametext></name>
+      <fsummary>Calculate an async key from an ErlDrvPort.</fsummary>
       <desc>
         <marker id="driver_async_port_key"></marker>
-        <p>This function calculates a key for later use in <seealso
-        marker="#driver_async">driver_async()</seealso>. The keys are
-        evenly distributed so that a fair mapping between port id's
-        and async thread id's is achieved.</p>
-	<note>
-	<p>Before OTP-R16, the actual port id could be used as a key
-	with proper casting, but after the rewrite of the port
-	subsystem, this is no longer the case. With this function, you
-	can achieve the same distribution based on port id's as before
-	OTP-R16.</p>
-	</note>
+        <p>Calculates a key for later use in <seealso
+          marker="#driver_async"><c>driver_async</c></seealso>. The keys are
+          evenly distributed so that a fair mapping between port IDs
+          and async thread IDs is achieved.</p>
+        <note>
+          <p>Before Erlang/OTP R16, the port ID could be used as a key
+            with proper casting, but after the rewrite of the port
+            subsystem, this is no longer the case. With this function, you
+            can achieve the same distribution based on port IDs as before
+            Erlang/OTP R16.</p>
+        </note>
       </desc>
     </func>
 
     <func>
-      <name><ret>long</ret><nametext>driver_binary_dec_refc(ErlDrvBinary *bin)</nametext></name>
-      <fsummary>Decrement the reference count of a driver binary</fsummary>
+      <name><ret>long</ret>
+        <nametext>driver_binary_dec_refc(ErlDrvBinary *bin)</nametext></name>
+      <fsummary>Decrement the reference count of a driver binary.</fsummary>
       <desc>
         <marker id="driver_binary_dec_refc"></marker>
         <p>Decrements the reference count on <c>bin</c> and returns
@@ -1045,31 +1106,33 @@ typedef struct ErlIOVec {
         <p>This function is only thread-safe when the emulator with SMP
           support is used.</p>
         <note>
-          <p>You should normally decrement the reference count of a
-            driver binary by calling
-            <seealso marker="#driver_free_binary">driver_free_binary()</seealso>.
-            <c>driver_binary_dec_refc()</c> does <em>not</em> free
+          <p>The reference count of driver binary is normally to be decremented
+            by calling <seealso marker="#driver_free_binary">
+            <c>driver_free_binary</c></seealso>.</p>
+          <p><c>driver_binary_dec_refc</c> does <em>not</em> free
             the binary if the reference count reaches zero. <em>Only</em>
-            use <c>driver_binary_dec_refc()</c> when you are sure
+            use <c>driver_binary_dec_refc</c> when you are sure
             <em>not</em> to reach a reference count of zero.</p>
         </note>
       </desc>
     </func>
 
     <func>
-      <name><ret>long</ret><nametext>driver_binary_get_refc(ErlDrvBinary *bin)</nametext></name>
-      <fsummary>Get the reference count of a driver binary</fsummary>
+      <name><ret>long</ret>
+        <nametext>driver_binary_get_refc(ErlDrvBinary *bin)</nametext></name>
+      <fsummary>Get the reference count of a driver binary.</fsummary>
       <desc>
         <marker id="driver_binary_get_refc"></marker>
-        <p>Returns current reference count on <c>bin</c>.</p>
+        <p>Returns the current reference count on <c>bin</c>.</p>
         <p>This function is only thread-safe when the emulator with SMP
           support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>long</ret><nametext>driver_binary_inc_refc(ErlDrvBinary *bin)</nametext></name>
-      <fsummary>Increment the reference count of a driver binary</fsummary>
+      <name><ret>long</ret>
+        <nametext>driver_binary_inc_refc(ErlDrvBinary *bin)</nametext></name>
+      <fsummary>Increment the reference count of a driver binary.</fsummary>
       <desc>
         <marker id="driver_binary_inc_refc"></marker>
         <p>Increments the reference count on <c>bin</c> and returns
@@ -1080,143 +1143,158 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>ErlDrvTermData</ret><nametext>driver_caller(ErlDrvPort port)</nametext></name>
-      <fsummary>Return the process making the driver call</fsummary>
+      <name><ret>ErlDrvTermData</ret><nametext>driver_caller(ErlDrvPort
+        port)</nametext></name>
+      <fsummary>Return the process making the driver call.</fsummary>
       <desc>
         <marker id="driver_caller"></marker>
-        <p>This function returns the process id of the process that
-	  made the current call to the driver. The process id can be
-	  used with <c>driver_send_term</c> to send back data to the
-	  caller. <c>driver_caller()</c> only returns valid data
-	  when currently executing in one of the following driver
-	  callbacks:</p>
-	  <taglist>
-	    <tag><seealso marker="driver_entry#start">start</seealso></tag>
-            <item>Called from <c>open_port/2</c>.</item>
-	    <tag><seealso marker="driver_entry#output">output</seealso></tag>
-            <item>Called from <c>erlang:send/2</c>, and
-	          <c>erlang:port_command/2</c></item>
-	    <tag><seealso marker="driver_entry#outputv">outputv</seealso></tag>
-            <item>Called from <c>erlang:send/2</c>, and
-	          <c>erlang:port_command/2</c></item>
-	    <tag><seealso marker="driver_entry#control">control</seealso></tag>
-            <item>Called from <c>erlang:port_control/3</c></item>
-	    <tag><seealso marker="driver_entry#call">call</seealso></tag>
-            <item>Called from <c>erlang:port_call/3</c></item>
-	  </taglist>
-        <p>Note that this function is <em>not</em> thread-safe, not
+        <p>Returns the process ID of the process that
+          made the current call to the driver. The process ID can be used with
+          <seealso marker="#driver_send_term"><c>driver_send_term</c></seealso>
+          to send back data to the caller.
+          <c>driver_caller</c> only returns valid data
+          when currently executing in one of the following driver callbacks:</p>
+        <taglist>
+          <tag><seealso marker="driver_entry#start">
+            <c>start</c></seealso></tag>
+          <item>Called from <seealso marker="erlang:open_port/2">
+            <c>erlang:open_port/2</c></seealso>.</item>
+          <tag><seealso marker="driver_entry#output">
+            <c>output</c></seealso></tag>
+          <item>Called from <seealso marker="erlang:send/2">
+            <c>erlang:send/2</c></seealso> and
+            <seealso marker="erlang:port_command/2">
+            <c>erlang:port_command/2</c></seealso>.</item>
+          <tag><seealso marker="driver_entry#outputv">
+            <c>outputv</c></seealso></tag>
+          <item>Called from <seealso marker="erlang:send/2">
+            <c>erlang:send/2</c></seealso> and
+            <seealso marker="erlang:port_command/2">
+            <c>erlang:port_command/2</c></seealso>.</item>
+          <tag><seealso marker="driver_entry#control">
+            <c>control</c></seealso></tag>
+          <item>Called from <seealso marker="erlang:port_control/3">
+            <c>erlang:port_control/3</c></seealso>.</item>
+          <tag><seealso marker="driver_entry#call">
+            <c>call</c></seealso></tag>
+          <item>Called from <seealso marker="erlang:port_call/3">
+            <c>erlang:port_call/3</c></seealso>.</item>
+        </taglist>
+        <p>Notice that this function is <em>not</em> thread-safe, not
           even when the emulator with SMP support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_cancel_timer(ErlDrvPort port)</nametext></name>
-      <fsummary>Cancel a previously set timer</fsummary>
+      <name><ret>int</ret>
+        <nametext>driver_cancel_timer(ErlDrvPort port)</nametext></name>
+      <fsummary>Cancel a previously set timer.</fsummary>
       <desc>
         <marker id="driver_cancel_timer"></marker>
-        <p>This function cancels a timer set with
-          <c>driver_set_timer</c>.</p>
-        <p>The return value is 0.</p>
+        <p>Cancels a timer set with
+          <seealso marker="#driver_set_timer">
+          <c>driver_set_timer</c></seealso>.</p>
+        <p>The return value is <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_compare_monitors(const ErlDrvMonitor *monitor1, const ErlDrvMonitor *monitor2)</nametext></name>
-      <fsummary>Compare two monitors</fsummary>
+      <name><ret>int</ret><nametext>driver_compare_monitors(const ErlDrvMonitor
+        *monitor1, const ErlDrvMonitor *monitor2)</nametext></name>
+      <fsummary>Compare two monitors.</fsummary>
       <desc>
         <marker id="driver_compare_monitors"></marker>
-        <p>This function is used to compare two <c>ErlDrvMonitor</c>s. It
-          can also be used to imply some artificial order on monitors,
+        <p>Compares two <c>ErlDrvMonitor</c>s.
+          Can also be used to imply some artificial order on monitors,
           for whatever reason.</p>
-        <p>The function returns 0 if <c>monitor1</c> and
-          <c>monitor2</c> are equal, &lt; 0 if <c>monitor1</c> is less
-          than <c>monitor2</c> and &gt; 0 if <c>monitor1</c> is greater
-          than <c>monitor2</c>.</p>
+        <p>Returns <c>0</c> if <c>monitor1</c> and <c>monitor2</c> are equal,
+          &lt; <c>0</c> if <c>monitor1</c> &lt; <c>monitor2</c>, and
+          &gt; <c>0</c> if <c>monitor1</c> &gt; <c>monitor2</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvTermData</ret><nametext>driver_connected(ErlDrvPort port)</nametext></name>
-      <fsummary>Return the port owner process</fsummary>
+      <name><ret>ErlDrvTermData</ret><nametext>driver_connected(ErlDrvPort
+        port)</nametext></name>
+      <fsummary>Return the port owner process.</fsummary>
       <desc>
         <marker id="driver_connected"></marker>
-        <p>This function returns the port owner process.</p>
-        <p>Note that this function is <em>not</em> thread-safe, not
+        <p>Returns the port owner process.</p>
+        <p>Notice that this function is <em>not</em> thread-safe, not
           even when the emulator with SMP support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvPort</ret><nametext>driver_create_port(ErlDrvPort port, ErlDrvTermData owner_pid, char* name, ErlDrvData drv_data)</nametext></name>
-      <fsummary>Create a new port (driver instance)</fsummary>
+      <name><ret>ErlDrvPort</ret><nametext>driver_create_port(ErlDrvPort port,
+        ErlDrvTermData owner_pid, char* name,
+        ErlDrvData drv_data)</nametext></name>
+      <fsummary>Create a new port (driver instance).</fsummary>
       <desc>
-        <p>This function creates a new port executing the same driver
-          code as the port creating the new port.
-          A short description of the arguments:</p>
+        <p>Creates a new port executing the same driver
+          code as the port creating the new port.</p>
         <taglist>
           <tag><c>port</c></tag>
           <item>The port handle of the port (driver instance) creating
-           the new port.</item>
+            the new port.</item>
           <tag><c>owner_pid</c></tag>
-          <item>The process id of the Erlang process which will be
-           owner of the new port. This process will be linked
-           to the new port. You usually want to use
-          <c>driver_caller(port)</c> as <c>owner_pid</c>.</item>
+          <item>The process ID of the Erlang process to become
+            owner of the new port. This process will be linked
+            to the new port. You usually want to use
+            <c>driver_caller(port)</c> as <c>owner_pid</c>.</item>
           <tag><c>name</c></tag>
           <item>The port name of the new port. You usually want to
-           use the same port name as the driver name
-           (<seealso marker="driver_entry#driver_name">driver_name</seealso>
-           field of the
-          <seealso marker="driver_entry">driver_entry</seealso>).</item>
+            use the same port name as the driver name
+            (<seealso marker="driver_entry#driver_name">
+            <c>driver_name</c></seealso> field of the
+            <seealso marker="driver_entry"><c>driver_entry</c></seealso>).
+          </item>
           <tag><c>drv_data</c></tag>
-          <item>The driver defined handle that will be passed in subsequent
-           calls to driver call-backs. Note, that the
-          <seealso marker="driver_entry#start">driver start call-back</seealso>
-           will not be called for this new driver instance.
-           The driver defined handle is normally created in the
-          <seealso marker="driver_entry#start">driver start call-back</seealso>
-           when a port is created via
-          <seealso marker="erlang#open_port/2">erlang:open_port/2</seealso>. </item>
+          <item>The driver-defined handle that is passed in later
+            calls to driver callbacks. Notice that the
+            <seealso marker="driver_entry#start">driver start
+            callback</seealso> is not called for this new driver instance.
+            The driver-defined handle is normally created in the
+            <seealso marker="driver_entry#start">driver start callback</seealso>
+            when a port is created through
+            <seealso marker="erlang#open_port/2">
+            <c>erlang:open_port/2</c></seealso>.
+          </item>
         </taglist>
-        <p>The caller of <c>driver_create_port()</c> is allowed to
-          manipulate the newly created port when <c>driver_create_port()</c>
+        <p>The caller of <c>driver_create_port</c> is allowed to
+          manipulate the newly created port when <c>driver_create_port</c>
           has returned. When
           <seealso marker="#smp_support">port level locking</seealso>
-          is used, the creating port is, however, only allowed to
+          is used, the creating port is only allowed to
           manipulate the newly created port until the current driver
-          call-back that was called by the emulator returns.</p>
-        <note>
-          <p>When
-            <seealso marker="#smp_support">port level locking</seealso>
-            is used, the creating port is only allowed to manipulate
-            the newly created port until the current driver call-back
-            returns.</p>
-        </note>
+          callback, which was called by the emulator, returns.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_demonitor_process(ErlDrvPort port,  const ErlDrvMonitor *monitor)</nametext></name>
-      <fsummary>Stop monitoring a process from a driver</fsummary>
+      <name><ret>int</ret><nametext>driver_demonitor_process(ErlDrvPort port,
+        const ErlDrvMonitor *monitor)</nametext></name>
+      <fsummary>Stop monitoring a process from a driver.</fsummary>
       <desc>
         <marker id="driver_demonitor_process"></marker>
-        <p>This function cancels a monitor created earlier. </p>
-        <p>The function returns 0 if a monitor was removed and &gt; 0
-          if the monitor did no longer exist.</p>
+        <p>Cancels a monitor created earlier.</p>
+        <p>Returns <c>0</c> if a monitor was removed and &gt; 0 if the monitor
+          no longer exists.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvSizeT</ret><nametext>driver_deq(ErlDrvPort port, ErlDrvSizeT size)</nametext></name>
-      <fsummary>Dequeue data from the head of the driver queue</fsummary>
+      <name><ret>ErlDrvSizeT</ret><nametext>driver_deq(ErlDrvPort port,
+        ErlDrvSizeT size)</nametext></name>
+      <fsummary>Dequeue data from the head of the driver queue.</fsummary>
       <desc>
         <marker id="driver_deq"></marker>
-        <p>This function dequeues data by moving the head pointer
+        <p>Dequeues data by moving the head pointer
           forward in the driver queue by <c>size</c> bytes. The data
-          in the queue will be deallocated.</p>
-        <p>The return value is the number of bytes remaining in the queue
-          or -1 on failure.</p>
-        <p>This function can be called from an arbitrary thread if a
+          in the queue is deallocated.</p>
+        <p>Returns the number of bytes remaining in the queue on success,
+          otherwise <c>-1</c>.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1224,24 +1302,25 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_enq(ErlDrvPort port, char* buf, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Enqueue data in the driver queue</fsummary>
+      <name><ret>int</ret><nametext>driver_enq(ErlDrvPort port, char* buf,
+        ErlDrvSizeT len)</nametext></name>
+      <fsummary>Enqueue data in the driver queue.</fsummary>
       <desc>
         <marker id="driver_enq"></marker>
-        <p>This function enqueues data in the driver queue. The data in
+        <p>Enqueues data in the driver queue. The data in
           <c>buf</c> is copied (<c>len</c> bytes) and placed at the
           end of the driver queue. The driver queue is normally used
           in a FIFO way.</p>
         <p>The driver queue is available to queue output from the
           emulator to the driver (data from the driver to the emulator
-          is queued by the emulator in normal erlang message
-          queues). This can be useful if the driver has to wait for
-          slow devices etc, and wants to yield back to the
-          emulator. The driver queue is implemented as an ErlIOVec.</p>
-        <p>When the queue contains data, the driver won't close, until
+          is queued by the emulator in normal Erlang message
+          queues). This can be useful if the driver must wait for
+          slow devices, and so on, and wants to yield back to the
+          emulator. The driver queue is implemented as an <c>ErlIOVec</c>.</p>
+        <p>When the queue contains data, the driver does not close until
           the queue is empty.</p>
-        <p>The return value is 0.</p>
-        <p>This function can be called from an arbitrary thread if a
+        <p>The return value is <c>0</c>.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1249,34 +1328,39 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_enq_bin(ErlDrvPort port, ErlDrvBinary *bin, ErlDrvSizeT offset, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Enqueue binary in the driver queue</fsummary>
+      <name><ret>int</ret><nametext>driver_enq_bin(ErlDrvPort port,
+        ErlDrvBinary *bin, ErlDrvSizeT offset, ErlDrvSizeT len)</nametext>
+      </name>
+      <fsummary>Enqueue binary in the driver queue.</fsummary>
       <desc>
         <marker id="driver_enq_bin"></marker>
-        <p>This function enqueues a driver binary in the driver
+        <p>Enqueues a driver binary in the driver
           queue. The data in <c>bin</c> at <c>offset</c> with length
           <c>len</c> is placed at the end of the queue. This function
-          is most often faster than <c>driver_enq</c>, because the
-          data doesn't have to be copied.</p>
-        <p>This function can be called from an arbitrary thread if a
+          is most often faster than
+          <seealso marker="#driver_enq"><c>driver_enq</c></seealso>,
+          because no data must be copied.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
-        <p>The return value is 0.</p>
+        <p>The return value is <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_enqv(ErlDrvPort port, ErlIOVec *ev, ErlDrvSizeT skip)</nametext></name>
-      <fsummary>Enqueue vector in the driver queue</fsummary>
+      <name><ret>int</ret><nametext>driver_enqv(ErlDrvPort port, ErlIOVec *ev,
+        ErlDrvSizeT skip)</nametext></name>
+      <fsummary>Enqueue vector in the driver queue.</fsummary>
       <desc>
         <marker id="driver_enqv"></marker>
-        <p>This function enqueues the data in <c>ev</c>, skipping the
+        <p>Enqueues the data in <c>ev</c>, skipping the
           first <c>skip</c> bytes of it, at the end of the driver
-          queue. It is faster than <c>driver_enq</c>, because the data
-          doesn't have to be copied.</p>
-        <p>The return value is 0.</p>
-        <p>This function can be called from an arbitrary thread if a
+          queue. It is faster than
+          <seealso marker="#driver_enq"><c>driver_enq</c></seealso>,
+          because no data must be copied.</p>
+        <p>The return value is <c>0</c>.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1284,283 +1368,320 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_failure_atom(ErlDrvPort port, char *string)</nametext></name>
-      <name><ret>int</ret><nametext>driver_failure_posix(ErlDrvPort port, int error)</nametext></name>
-      <name><ret>int</ret><nametext>driver_failure(ErlDrvPort port, int error)</nametext></name>
-      <fsummary>Fail with error</fsummary>
+      <name><ret>int</ret><nametext>driver_failure(ErlDrvPort port, int
+        error)</nametext></name>
+      <name><ret>int</ret><nametext>driver_failure_atom(ErlDrvPort port, char
+        *string)</nametext></name>
+      <name><ret>int</ret><nametext>driver_failure_posix(ErlDrvPort port, int
+        error)</nametext></name>
+      <fsummary>Fail with error.</fsummary>
       <desc>
         <marker id="driver_failure_atom"></marker>
         <marker id="driver_failure_posix"></marker>
         <marker id="driver_failure"></marker>
-        <p>These functions signal to Erlang that the driver has
-          encountered an error and should be closed. The port is
-          closed and the tuple <c>{'EXIT', error, Err}</c>, is sent to
+        <p>Signals to Erlang that the driver has
+          encountered an error and is to be closed. The port is
+          closed and the tuple <c>{'EXIT', error, Err}</c> is sent to
           the port owner process, where error is an error atom
           (<c>driver_failure_atom</c> and
-          <c>driver_failure_posix</c>), or an integer
+          <c>driver_failure_posix</c>) or an integer
           (<c>driver_failure</c>).</p>
-        <p>The driver should fail only when in severe error situations,
-          when the driver cannot possibly keep open, for instance
+        <p>The driver is to fail only when in severe error situations,
+          when the driver cannot possibly keep open, for example,
           buffer allocation gets out of memory. For normal errors
           it is more appropriate to send error codes with
-          <c>driver_output</c>.</p>
-        <p>The return value is 0.</p>
+          <seealso marker="#driver_output"><c>driver_output</c></seealso>.</p>
+        <p>The return value is <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_failure_eof(ErlDrvPort port)</nametext></name>
-      <fsummary>Fail with EOF</fsummary>
+      <name><ret>int</ret><nametext>driver_failure_eof(ErlDrvPort
+        port)</nametext></name>
+      <fsummary>Fail with EOF.</fsummary>
       <desc>
         <marker id="driver_failure_eof"></marker>
-        <p>This function signals to erlang that the driver has
-          encountered an EOF and should be closed, unless the port was
-          opened with the <c>eof</c> option, in that case eof is sent
-          to the port. Otherwise, the port is closed and an
+        <p>Signals to Erlang that the driver has
+          encountered an EOF and is to be closed, unless the port was
+          opened with option <c>eof</c>, in which case <c>eof</c> is sent
+          to the port. Otherwise the port is closed and an
           <c>'EXIT'</c> message is sent to the port owner process.</p>
-        <p>The return value is 0.</p>
+        <p>The return value is <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret><nametext>driver_free(void *ptr)</nametext></name>
-      <fsummary>Free an allocated memory block</fsummary>
+      <fsummary>Free an allocated memory block.</fsummary>
       <desc>
         <marker id="driver_free"></marker>
-        <p>This function frees the memory pointed to by <c>ptr</c>. The
-          memory should have been allocated with
-          <c>driver_alloc</c>. All allocated memory should be
-          deallocated, just once. There is no garbage collection in
+        <p>Frees the memory pointed to by <c>ptr</c>. The
+          memory is to have been allocated with
+          <c>driver_alloc</c>. All allocated memory is to be
+          deallocated, only once. There is no garbage collection in
           drivers.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>driver_free_binary(ErlDrvBinary *bin)</nametext></name>
-      <fsummary>Free a driver binary</fsummary>
+      <name><ret>void</ret>
+        <nametext>driver_free_binary(ErlDrvBinary *bin)</nametext></name>
+      <fsummary>Free a driver binary.</fsummary>
       <desc>
         <marker id="driver_free_binary"></marker>
-        <p>This function frees a driver binary <c>bin</c>, allocated
-          previously with <c>driver_alloc_binary</c>. Since binaries
-          in Erlang are reference counted, the binary may still be
-          around.</p>
+        <p>Frees a driver binary <c>bin</c>, allocated previously with
+        <seealso marker="#driver_alloc_binary">
+        <c>driver_alloc_binary</c></seealso>. As binaries
+          in Erlang are reference counted, the binary can still be around.</p>
         <p>This function is only thread-safe when the emulator with SMP
           support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvTermData</ret><nametext>driver_get_monitored_process(ErlDrvPort port,  const ErlDrvMonitor *monitor)</nametext></name>
-      <fsummary>Retrieve the process id from a monitor</fsummary>
+      <name><ret>ErlDrvTermData</ret>
+        <nametext>driver_get_monitored_process(ErlDrvPort port, const
+        ErlDrvMonitor *monitor)</nametext></name>
+      <fsummary>Retrieve the process ID from a monitor.</fsummary>
       <desc>
         <marker id="driver_get_monitored_process"></marker>
-        <p>The function returns the process id associated with a living
-          monitor. It can be used in the <c>process_exit</c> call-back to
-          get the process  identification for the exiting process.</p>
-        <p>The function returns <c>driver_term_nil</c> if the monitor
-          no longer exists.</p>
+        <p>Returns the process ID associated with a living
+          monitor. It can be used in the
+          <seealso marker="driver_entry#process_exit">
+          <c>process_exit</c></seealso> callback to
+          get the process identification for the exiting process.</p>
+        <p>Returns <c>driver_term_nil</c> if the monitor no longer exists.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_get_now(ErlDrvNowData *now)</nametext></name>
-      <fsummary>Read a system timestamp</fsummary>
+      <name><ret>int</ret>
+        <nametext>driver_get_now(ErlDrvNowData *now)</nametext></name>
+      <fsummary>Read a system time stamp.</fsummary>
       <desc>
         <marker id="driver_get_now"></marker>
-	<warning><p><em>This function is deprecated! Do not use it!</em>
-	Use <seealso marker="#erl_drv_monotonic_time"><c>erl_drv_monotonic_time()</c></seealso>
-	(perhaps in combination with
-	<seealso marker="#erl_drv_time_offset"><c>erl_drv_time_offset()</c></seealso>)
-	instead.</p></warning>
-        <p>This function reads a timestamp into the memory pointed to by
-          the parameter <c>now</c>. See the description of <seealso marker="#ErlDrvNowData">ErlDrvNowData</seealso> for
-          specification of its fields.  </p>
-        <p>The return value is 0 unless the <c>now</c> pointer is not
-          valid, in which case it is &lt; 0.  </p>
+	<warning>
+          <p><em>This function is deprecated. Do not use it.</em> Use
+            <seealso marker="#erl_drv_monotonic_time">
+            <c>erl_drv_monotonic_time</c></seealso> (perhaps in combination with
+            <seealso marker="#erl_drv_time_offset">
+            <c>erl_drv_time_offset</c></seealso>) instead.</p>
+        </warning>
+        <p>Reads a time stamp into the memory pointed to by
+          parameter <c>now</c>. For information about specific fields, see
+          <seealso marker="#ErlDrvNowData"><c>ErlDrvNowData</c></seealso>.</p>
+        <p>The return value is <c>0</c>, unless the <c>now</c> pointer is
+          invalid, in which case it is &lt; <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_lock_driver(ErlDrvPort port)</nametext></name>
-      <fsummary>Make sure the driver is never unloaded</fsummary>
+      <name><ret>int</ret><nametext>driver_lock_driver(ErlDrvPort
+        port)</nametext></name>
+      <fsummary>Ensure the driver is never unloaded.</fsummary>
       <desc>
         <marker id="driver_lock_driver"></marker>
-        <p>This function locks the driver used by the port <c>port</c>
+        <p>Locks the driver used by the port <c>port</c>
           in memory for the rest of the emulator process'
           lifetime. After this call, the driver behaves as one of Erlang's
-          statically linked in drivers.</p>
+          statically linked-in drivers.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvTermData</ret><nametext>driver_mk_atom(char* string)</nametext></name>
-      <fsummary>Make an atom from a name</fsummary>
+      <name><ret>ErlDrvTermData</ret><nametext>driver_mk_atom(char*
+        string)</nametext></name>
+      <fsummary>Make an atom from a name.</fsummary>
       <desc>
         <marker id="driver_mk_atom"></marker>
-        <p>This function returns an atom given a name
-          <c>string</c>. The atom is created and won't change, so the
-          return value may be saved and reused, which is faster than
+        <p>Returns an atom given a name
+          <c>string</c>. The atom is created and does not change, so the
+          return value can be saved and reused, which is faster than
           looking up the atom several times.</p>
-        <p>Note that this function is <em>not</em> thread-safe, not
+        <p>Notice that this function is <em>not</em> thread-safe, not
           even when the emulator with SMP support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvTermData</ret><nametext>driver_mk_port(ErlDrvPort port)</nametext></name>
-      <fsummary>Make a erlang term port from a port</fsummary>
+      <name><ret>ErlDrvTermData</ret><nametext>driver_mk_port(ErlDrvPort
+        port)</nametext></name>
+      <fsummary>Make an Erlang term port from a port.</fsummary>
       <desc>
         <marker id="driver_mk_port"></marker>
-        <p>This function converts a port handle to the erlang term
-          format, usable in the <seealso marker="#erl_drv_output_term">erl_drv_output_term()</seealso>, and <seealso marker="#erl_drv_send_term">erl_drv_send_term()</seealso> functions.</p>
-        <p>Note that this function is <em>not</em> thread-safe, not
+        <p>Converts a port handle to the Erlang term format, usable in
+          <seealso marker="#erl_drv_output_term">
+          <c>erl_drv_output_term</c></seealso> and 
+          <seealso marker="#erl_drv_send_term">
+          <c>erl_drv_send_term</c></seealso>.</p>
+        <p>Notice that this function is <em>not</em> thread-safe, not
           even when the emulator with SMP support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_monitor_process(ErlDrvPort port,  ErlDrvTermData process,  ErlDrvMonitor *monitor)</nametext></name>
-      <fsummary>Monitor a process from a driver</fsummary>
+      <name><ret>int</ret><nametext>driver_monitor_process(ErlDrvPort port,
+        ErlDrvTermData process, ErlDrvMonitor *monitor)</nametext></name>
+      <fsummary>Monitor a process from a driver.</fsummary>
       <desc>
         <marker id="driver_monitor_process"></marker>
-        <p>Start monitoring a process from a driver. When a process is
-          monitored, a process exit will result in a call to the
-          provided <seealso marker="driver_entry#process_exit">process_exit</seealso> call-back
-          in the <seealso marker="driver_entry">ErlDrvEntry</seealso>
+        <p>Starts monitoring a process from a driver. When a process is
+          monitored, a process exit results in a call to the provided
+          <seealso marker="driver_entry#process_exit">
+          <c>process_exit</c></seealso> callback
+          in the <seealso marker="driver_entry"><c>ErlDrvEntry</c></seealso>
           structure. The <c>ErlDrvMonitor</c> structure is filled in, for later
           removal or compare.</p>
-        <p>The <c>process</c> parameter should be the return value of an
-          earlier call to <seealso marker="#driver_caller">driver_caller</seealso> or <seealso marker="#driver_connected">driver_connected</seealso> call.</p>
-        <p>The function returns 0 on success, &lt; 0 if no call-back is
-          provided and &gt; 0 if the process is no longer alive.</p>
+        <p>Parameter <c>process</c> is to be the return value of an
+          earlier call to <seealso marker="#driver_caller">
+          <c>driver_caller</c></seealso> or
+          <seealso marker="#driver_connected"><c>driver_connected</c></seealso>
+          call.</p>
+        <p>Returns <c>0</c> on success, &lt; 0 if no callback is
+          provided, and &gt; 0 if the process is no longer alive.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_output(ErlDrvPort port, char *buf, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Send data from driver to port owner</fsummary>
+      <name><ret>int</ret><nametext>driver_output(ErlDrvPort port, char *buf,
+        ErlDrvSizeT len)</nametext></name>
+      <fsummary>Send data from driver to port owner.</fsummary>
       <desc>
         <marker id="driver_output"></marker>
-        <p>The <c>driver_output</c> function is used to send data from
-          the driver up to the emulator. The data will be received as
-          terms or binary data, depending on how the driver port was
+        <p>Sends data from the driver up to the emulator. The data is received
+          as terms or binary data, depending on how the driver port was
           opened.</p>
         <p>The data is queued in the port owner process' message
-          queue. Note that this does not yield to the emulator. (Since
-          the driver and the emulator run in the same thread.)</p>
-        <p>The parameter <c>buf</c> points to the data to send, and
+          queue. Notice that this does not yield to the emulator (as
+          the driver and the emulator run in the same thread).</p>
+        <p>Parameter <c>buf</c> points to the data to send, and
           <c>len</c> is the number of bytes.</p>
-        <p>The return value for all output functions is 0. (Unless the
-          driver is used for distribution, in which case it can fail
-          and return -1. For normal use, the output function always
-          returns 0.)</p>
+        <p>The return value for all output functions is <c>0</c> for normal use.
+          If the driver is used for distribution, it can fail and return
+          <c>-1</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_output_binary(ErlDrvPort port, char *hbuf, ErlDrvSizeT hlen, ErlDrvBinary* bin, ErlDrvSizeT offset, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Send data from a driver binary to port owner</fsummary>
+      <name><ret>int</ret><nametext>driver_output_binary(ErlDrvPort port, char
+        *hbuf, ErlDrvSizeT hlen, ErlDrvBinary* bin, ErlDrvSizeT offset,
+        ErlDrvSizeT len)</nametext></name>
+      <fsummary>Send data from a driver binary to port owner.</fsummary>
       <desc>
         <marker id="driver_output_binary"></marker>
-        <p>This function sends data to port owner process from a
-          driver binary, it has a header buffer (<c>hbuf</c>
-          and <c>hlen</c>) just like <c>driver_output2</c>. The
-          <c>hbuf</c> parameter can be <c>NULL</c>.</p>
-        <p>The parameter <c>offset</c> is an offset into the binary and
+        <p>Sends data to a port owner process from a
+          driver binary. It has a header buffer (<c>hbuf</c>
+          and <c>hlen</c>) just like
+          <seealso marker="#driver_output2"><c>driver_output2</c></seealso>.
+          Parameter <c>hbuf</c> can be <c>NULL</c>.</p>
+        <p>Parameter <c>offset</c> is an offset into the binary and
           <c>len</c> is the number of bytes to send.</p>
-        <p>Driver binaries are created with <c>driver_alloc_binary</c>.</p>
+        <p>Driver binaries are created with
+          <seealso marker="#driver_alloc_binary">
+          <c>driver_alloc_binary</c></seealso>.</p>
         <p>The data in the header is sent as a list and the binary as
           an Erlang binary in the tail of the list.</p>
-        <p>E.g. if <c>hlen</c> is 2, then the port owner process will
-          receive <c><![CDATA[[H1, H2 | <<T>>]]]></c>.</p>
-        <p>The return value is 0 for normal use.</p>
-        <p>Note that, using the binary syntax in Erlang, the driver
+        <p>For example, if <c>hlen</c> is <c>2</c>, the port owner process
+          receives <c><![CDATA[[H1, H2 | <<T>>]]]></c>.</p>
+        <p>The return value is <c>0</c> for normal use.</p>
+        <p>Notice that, using the binary syntax in Erlang, the driver
           application can match the header directly from the binary,
-          so the header can be put in the binary, and hlen can be set
-          to 0.</p>
+          so the header can be put in the binary, and <c>hlen</c> can be set
+          to <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_output_term(ErlDrvPort port, ErlDrvTermData* term, int n)</nametext></name>
-      <fsummary>Send term data from driver to port owner</fsummary>
+      <name><ret>int</ret><nametext>driver_output_term(ErlDrvPort port,
+        ErlDrvTermData* term, int n)</nametext></name>
+      <fsummary>Send term data from driver to port owner.</fsummary>
       <desc>
         <marker id="driver_output_term"></marker>
-	<warning><p><c>driver_output_term()</c> is deprecated and will
-	            be removed in the OTP-R17 release. Use
-		    <seealso marker="#erl_drv_send_term">erl_drv_output_term()</seealso>
-		    instead.</p>
-	</warning>
-        <p>The parameters <c>term</c> and <c>n</c> do the same thing
-          as in <seealso marker="#erl_drv_output_term">erl_drv_output_term()</seealso>.</p>
-        <p>Note that this function is <em>not</em> thread-safe, not
+        <warning>
+          <p><em>This function is deprecated.</em>
+            Use <seealso marker="#erl_drv_send_term">
+            <c>erl_drv_output_term</c></seealso>instead.</p>
+        </warning>
+        <p>Parameters <c>term</c> and <c>n</c> work as in
+          <seealso marker="#erl_drv_output_term">
+          <c>erl_drv_output_term</c></seealso>.</p>
+        <p>Notice that this function is <em>not</em> thread-safe, not
           even when the emulator with SMP support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_output2(ErlDrvPort port, char *hbuf, ErlDrvSizeT hlen, char *buf, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Send data and binary data to port owner</fsummary>
+      <name><ret>int</ret><nametext>driver_output2(ErlDrvPort port, char *hbuf,
+        ErlDrvSizeT hlen, char *buf, ErlDrvSizeT len)</nametext></name>
+      <fsummary>Send data and binary data to port owner.</fsummary>
       <desc>
         <marker id="driver_output2"></marker>
-        <p>The <c>driver_output2</c> function first sends <c>hbuf</c>
+        <p>First sends <c>hbuf</c>
           (length in <c>hlen</c>) data as a list, regardless of port
-          settings. Then <c>buf</c> is sent as a binary or list.
-          E.g. if <c>hlen</c> is 3 then the port owner process will
-          receive <c>[H1, H2, H3 | T]</c>.</p>
+          settings. Then sends <c>buf</c> as a binary or list.
+          For example, if <c>hlen</c> is <c>3</c>, the port owner process
+          receives <c>[H1, H2, H3 | T]</c>.</p>
         <p>The point of sending data as a list header, is to facilitate
           matching on the data received.</p>
-        <p>The return value is 0 for normal use.</p>
+        <p>The return value is <c>0</c> for normal use.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_outputv(ErlDrvPort port, char* hbuf, ErlDrvSizeT hlen,  ErlIOVec *ev, ErlDrvSizeT skip)</nametext></name>
-      <fsummary>Send vectorized data to port owner</fsummary>
+      <name><ret>int</ret><nametext>driver_outputv(ErlDrvPort port, char* hbuf,
+        ErlDrvSizeT hlen, ErlIOVec *ev, ErlDrvSizeT skip)</nametext></name>
+      <fsummary>Send vectorized data to port owner.</fsummary>
       <desc>
         <marker id="driver_outputv"></marker>
-        <p>This function sends data from an IO vector, <c>ev</c>, to
+        <p>Sends data from an I/O vector, <c>ev</c>, to
           the port owner process. It has a header buffer (<c>hbuf</c>
-          and <c>hlen</c>), just like <c>driver_output2</c>.</p>
-        <p>The <c>skip</c> parameter is a number of bytes to skip of
+          and <c>hlen</c>), just like <seealso marker="#driver_output2">
+          <c>driver_output2</c></seealso>.</p>
+        <p>Parameter <c>skip</c> is a number of bytes to skip of
           the <c>ev</c> vector from the head.</p>
         <p>You get vectors of <c>ErlIOVec</c> type from the driver
-          queue (see below), and the <seealso marker="driver_entry#outputv">outputv</seealso> driver entry
-          function. You can also make them yourself, if you want to
+          queue (see below), and the
+          <seealso marker="driver_entry#outputv"><c>outputv</c></seealso>
+          driver entry function. You can also make them yourself, if you want to
           send several <c>ErlDrvBinary</c> buffers at once. Often
-          it is faster to use <c>driver_output</c> or
-          <c>driver_output_binary</c>.</p>
-        <p>E.g. if <c>hlen</c> is 2 and <c>ev</c> points to an array of
-          three binaries, the port owner process will receive <c><![CDATA[[H1, H2, <<B1>>, <<B2>> | <<B3>>]]]></c>.</p>
-        <p>The return value is 0 for normal use.</p>
-        <p>The comment for <c>driver_output_binary</c> applies for
-          <c>driver_outputv</c> too.</p>
+          it is faster to use
+          <seealso marker="#driver_output"><c>driver_output</c></seealso> or
+          <seealso marker="#driver_output_binary"></seealso>.</p>
+        <p>For example, if <c>hlen</c> is <c>2</c> and <c>ev</c> points to an
+          array of three binaries, the port owner process receives
+          <c><![CDATA[[H1, H2, <<B1>>, <<B2>> | <<B3>>]]]></c>.</p>
+        <p>The return value is <c>0</c> for normal use.</p>
+        <p>The comment for <c>driver_output_binary</c> also applies for
+          <c>driver_outputv</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvPDL</ret><nametext>driver_pdl_create(ErlDrvPort port)</nametext></name>
-      <fsummary>Create a port data lock</fsummary>
+      <name><ret>ErlDrvPDL</ret>
+        <nametext>driver_pdl_create(ErlDrvPort port)</nametext></name>
+      <fsummary>Create a port data lock.</fsummary>
       <desc>
         <marker id="driver_pdl_create"></marker>
-        <p>This function creates a port data lock associated with
-          the <c>port</c>. <em>NOTE</em>: Once a port data lock has
-          been created, it has to be locked during all operations
-          on the driver queue of the <c>port</c>.</p>
-        <p>On success a newly created port data lock is returned. On
-          failure <c>NULL</c> is returned. <c>driver_pdl_create()</c> will
-          fail if <c>port</c> is invalid or if a port data lock already has
+        <p>Creates a port data lock associated with the <c>port</c>.</p>
+        <note>
+          <p>Once a port data lock has been created, it must be locked during
+            all operations on the driver queue of the <c>port</c>.</p>
+        </note>
+        <p>Returns a newly created port data lock on success,
+          otherwise <c>NULL</c>. The function fails
+          if <c>port</c> is invalid or if a port data lock already has
           been associated with the <c>port</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>long</ret><nametext>driver_pdl_dec_refc(ErlDrvPDL pdl)</nametext></name>
+      <name><ret>long</ret><nametext>driver_pdl_dec_refc(ErlDrvPDL
+        pdl)</nametext></name>
       <fsummary></fsummary>
       <desc>
         <marker id="driver_pdl_dec_refc"></marker>
-        <p>This function decrements the reference count of
+        <p>Decrements the reference count of
           the port data lock passed as argument (<c>pdl</c>).</p>
         <p>The current reference count after the decrement has
           been performed is returned.</p>
@@ -1569,22 +1690,24 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>long</ret><nametext>driver_pdl_get_refc(ErlDrvPDL pdl)</nametext></name>
+      <name><ret>long</ret>
+        <nametext>driver_pdl_get_refc(ErlDrvPDL pdl)</nametext></name>
       <fsummary></fsummary>
       <desc>
         <marker id="driver_pdl_get_refc"></marker>
-        <p>This function returns the current reference count of
+        <p>Returns the current reference count of
           the port data lock passed as argument (<c>pdl</c>).</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>long</ret><nametext>driver_pdl_inc_refc(ErlDrvPDL pdl)</nametext></name>
+      <name><ret>long</ret>
+        <nametext>driver_pdl_inc_refc(ErlDrvPDL pdl)</nametext></name>
       <fsummary></fsummary>
       <desc>
         <marker id="driver_pdl_inc_refc"></marker>
-        <p>This function increments the reference count of
+        <p>Increments the reference count of
           the port data lock passed as argument (<c>pdl</c>).</p>
         <p>The current reference count after the increment has
           been performed is returned.</p>
@@ -1593,41 +1716,42 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>driver_pdl_lock(ErlDrvPDL pdl)</nametext></name>
-      <fsummary>Lock port data lock</fsummary>
+      <name><ret>void</ret>
+        <nametext>driver_pdl_lock(ErlDrvPDL pdl)</nametext></name>
+      <fsummary>Lock port data lock.</fsummary>
       <desc>
         <marker id="driver_pdl_lock"></marker>
-        <p>This function locks the port data lock passed as argument
-          (<c>pdl</c>).</p>
+        <p>Locks the port data lock passed as argument (<c>pdl</c>).</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>driver_pdl_unlock(ErlDrvPDL pdl)</nametext></name>
-      <fsummary>Unlock port data lock</fsummary>
+      <name><ret>void</ret>
+        <nametext>driver_pdl_unlock(ErlDrvPDL pdl)</nametext></name>
+      <fsummary>Unlock port data lock.</fsummary>
       <desc>
         <marker id="driver_pdl_unlock"></marker>
-        <p>This function unlocks the port data lock passed as argument
-          (<c>pdl</c>).</p>
+        <p>Unlocks the port data lock passed as argument (<c>pdl</c>).</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>SysIOVec *</ret><nametext>driver_peekq(ErlDrvPort port, int *vlen)</nametext></name>
-      <fsummary>Get the driver queue as a vector</fsummary>
+      <name><ret>SysIOVec *</ret><nametext>driver_peekq(ErlDrvPort port, int
+        *vlen)</nametext></name>
+      <fsummary>Get the driver queue as a vector.</fsummary>
       <desc>
         <marker id="driver_peekq"></marker>
-        <p>This function retrieves the driver queue as a pointer to an
+        <p>Retrieves the driver queue as a pointer to an
           array of <c>SysIOVec</c>s. It also returns the number of
           elements in <c>vlen</c>. This is one of two ways to get data
           out of the queue.</p>
         <p>Nothing is removed from the queue by this function, that must be done
-          with <c>driver_deq</c>.</p>
+          with <seealso marker="#driver_deq"><c>driver_deq</c></seealso>.</p>
         <p>The returned array is suitable to use with the Unix system
           call <c>writev</c>.</p>
-        <p>This function can be called from an arbitrary thread if a
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1635,22 +1759,19 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>ErlDrvSizeT</ret><nametext>driver_peekqv(ErlDrvPort port, ErlIOVec *ev)</nametext></name>
-      <fsummary>Get the driver queue as an IO vector</fsummary>
+      <name><ret>ErlDrvSizeT</ret><nametext>driver_peekqv(ErlDrvPort port,
+        ErlIOVec *ev)</nametext></name>
+      <fsummary>Get the driver queue as an I/O vector.</fsummary>
       <desc>
         <marker id="driver_peekqv"></marker>
-        <p>
-	  This function retrieves the driver queue into a supplied
+        <p>Retrieves the driver queue into a supplied
 	  <c>ErlIOVec</c> <c>ev</c>. It also returns the queue size.
-	  This is one of two ways to get data out of the queue.
-	</p>
-	<p>
-	  If <c>ev</c> is <c>NULL</c> all ones i.e. <c>-1</c> type cast to
-	  <c>ErlDrvSizeT</c> is returned.
-	</p>
+	  This is one of two ways to get data out of the queue.</p>
+	<p>If <c>ev</c> is <c>NULL</c>, all ones that is <c>-1</c> type cast to
+	  <c>ErlDrvSizeT</c> are returned.</p>
         <p>Nothing is removed from the queue by this function, that must be done
-          with <c>driver_deq</c>.</p>
-        <p>This function can be called from an arbitrary thread if a
+          with <seealso marker="#driver_deq"><c>driver_deq</c></seealso>.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1658,15 +1779,16 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_pushq(ErlDrvPort port, char* buf, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Push data at the head of the driver queue</fsummary>
+      <name><ret>int</ret><nametext>driver_pushq(ErlDrvPort port, char* buf,
+        ErlDrvSizeT len)</nametext></name>
+      <fsummary>Push data at the head of the driver queue.</fsummary>
       <desc>
         <marker id="driver_pushq"></marker>
-        <p>This function puts data at the head of the driver queue. The
+        <p>Puts data at the head of the driver queue. The
           data in <c>buf</c> is copied (<c>len</c> bytes) and placed
           at the beginning of the queue.</p>
-        <p>The return value is 0.</p>
-        <p>This function can be called from an arbitrary thread if a
+        <p>The return value is <c>0</c>.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1674,34 +1796,38 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_pushq_bin(ErlDrvPort port, ErlDrvBinary *bin, ErlDrvSizeT offset, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Push binary at the head of the driver queue</fsummary>
+      <name><ret>int</ret><nametext>driver_pushq_bin(ErlDrvPort port,
+        ErlDrvBinary *bin, ErlDrvSizeT offset, ErlDrvSizeT len)</nametext>
+      </name>
+      <fsummary>Push binary at the head of the driver queue.</fsummary>
       <desc>
         <marker id="driver_pushq_bin"></marker>
-        <p>This function puts data in the binary <c>bin</c>, at
+        <p>Puts data in the binary <c>bin</c>, at
           <c>offset</c> with length <c>len</c> at the head of the
           driver queue. It is most often faster than
-          <c>driver_pushq</c>, because the data doesn't have to be
-          copied.</p>
-        <p>This function can be called from an arbitrary thread if a
+          <seealso marker="#driver_pushq"><c>driver_pushq</c></seealso>,
+          because no data must be copied.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
-        <p>The return value is 0.</p>
+        <p>The return value is <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_pushqv(ErlDrvPort port, ErlIOVec *ev, ErlDrvSizeT skip)</nametext></name>
-      <fsummary>Push vector at the head of the driver queue</fsummary>
+      <name><ret>int</ret><nametext>driver_pushqv(ErlDrvPort port, ErlIOVec
+        *ev, ErlDrvSizeT skip)</nametext></name>
+      <fsummary>Push vector at the head of the driver queue.</fsummary>
       <desc>
         <marker id="driver_pushqv"></marker>
-        <p>This function puts the data in <c>ev</c>, skipping the first
+        <p>Puts the data in <c>ev</c>, skipping the first
           <c>skip</c> bytes of it, at the head of the driver queue.
-          It is faster than <c>driver_pushq</c>, because the data
-          doesn't have to be copied.</p>
-        <p>The return value is 0.</p>
-        <p>This function can be called from an arbitrary thread if a
+          It is faster than
+          <seealso marker="#driver_pushq"><c>driver_pushq</c></seealso>,
+          because no data must be copied.</p>
+        <p>The return value is <c>0</c>.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1709,24 +1835,26 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_read_timer(ErlDrvPort port, unsigned long *time_left)</nametext></name>
-      <fsummary>Read the time left before timeout</fsummary>
+      <name><ret>int</ret><nametext>driver_read_timer(ErlDrvPort port, unsigned
+        long *time_left)</nametext></name>
+      <fsummary>Read the time left before time-out.</fsummary>
       <desc>
         <marker id="driver_read_timer"></marker>
-        <p>This function reads the current time of a timer, and places
+        <p>Reads the current time of a timer, and places
           the result in <c>time_left</c>. This is the time in
-          milliseconds, before the timeout will occur.</p>
-        <p>The return value is 0.</p>
+          milliseconds, before the time-out occurs.</p>
+        <p>The return value is <c>0</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void *</ret><nametext>driver_realloc(void *ptr, ErlDrvSizeT size)</nametext></name>
-      <fsummary>Resize an allocated memory block</fsummary>
+      <name><ret>void *</ret>
+        <nametext>driver_realloc(void *ptr, ErlDrvSizeT size)</nametext></name>
+      <fsummary>Resize an allocated memory block.</fsummary>
       <desc>
         <marker id="driver_realloc"></marker>
-        <p>This function resizes a memory block, either in place, or by
-          allocating a new block, copying the data and freeing the old
+        <p>Resizes a memory block, either in place, or by
+          allocating a new block, copying the data, and freeing the old
           block. A pointer is returned to the reallocated memory. On
           failure (out of memory), <c>NULL</c> is returned. (This is
           most often a wrapper for <c>realloc</c>.)</p>
@@ -1735,120 +1863,132 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>ErlDrvBinary *</ret><nametext>driver_realloc_binary(ErlDrvBinary *bin, ErlDrvSizeT size)</nametext></name>
-      <fsummary>Resize a driver binary</fsummary>
+      <name><ret>ErlDrvBinary *</ret>
+        <nametext>driver_realloc_binary(ErlDrvBinary *bin, ErlDrvSizeT size)
+        </nametext></name>
+      <fsummary>Resize a driver binary.</fsummary>
       <desc>
         <marker id="driver_realloc_binary"></marker>
-        <p>This function resizes a driver binary, while keeping the
-          data. The resized driver binary is returned. On failure (out
-          of memory), <c>NULL</c> is returned.</p>
+        <p>Resizes a driver binary, while keeping the data.</p>
+        <p>Returns the resized driver binary on success. Returns <c>NULL</c>
+          on failure (out of memory).</p>
         <p>This function is only thread-safe when the emulator with SMP
           support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_select(ErlDrvPort port, ErlDrvEvent event, int mode, int on)</nametext></name>
-      <fsummary>Provide an event for having the emulator call the driver</fsummary>
+      <name><ret>int</ret><nametext>driver_select(ErlDrvPort port, ErlDrvEvent
+        event, int mode, int on)</nametext></name>
+      <fsummary>Provides an event for having the emulator call the driver.
+      </fsummary>
       <desc>
         <marker id="driver_select"></marker>
         <p>This function is used by drivers to provide the emulator with
           events to check for. This enables the emulator to call the driver
-          when something has happened asynchronously.</p>
-        <p>The <c>event</c> argument identifies an OS-specific event object.
-          On Unix systems, the functions <c>select</c>/<c>poll</c> are used. The
-          event object must be a socket or pipe (or other object that
+          when something has occurred asynchronously.</p>
+        <p>Parameter <c>event</c> identifies an OS-specific event object.
+          On Unix systems, the functions <c>select</c>/<c>poll</c> are used.
+          The event object must be a socket or pipe (or other object that
           <c>select</c>/<c>poll</c> can use).
-          On windows, the Win32 API function <c>WaitForMultipleObjects</c>
-          is used. This places other restrictions on the event object.
-          Refer to the Win32 SDK documentation.</p>
-        <p>The <c>on</c> parameter should be <c>1</c> for setting events
+          On Windows, the Win32 API function <c>WaitForMultipleObjects</c>
+          is used. This places other restrictions on the event object;
+          see the Win32 SDK documentation.</p>
+        <p>Parameter <c>on</c> is to be <c>1</c> for setting events
           and <c>0</c> for clearing them.</p>
-        <p>The <c>mode</c> argument is a bitwise-or combination of
-          <c>ERL_DRV_READ</c>, <c>ERL_DRV_WRITE</c> and <c>ERL_DRV_USE</c>.
+        <p>Parameter <c>mode</c> is a bitwise OR combination of
+          <c>ERL_DRV_READ</c>, <c>ERL_DRV_WRITE</c>, and <c>ERL_DRV_USE</c>.
           The first two specify whether to wait for read events and/or write
-          events. A fired read event will call
-          <seealso marker="driver_entry#ready_input">ready_input</seealso>
-          while a fired write event will call
-          <seealso marker="driver_entry#ready_output">ready_output</seealso>.
-          </p>
-    <note>
-      <p>Some OS (Windows) do not differentiate between read and write events.
-         The call-back for a fired event then only depends on the value of <c>mode</c>.</p>
-    </note>
-        <p><c>ERL_DRV_USE</c> specifies if we are using the event object or if we want to close it.
-           On an emulator with SMP support, it is not safe to clear all events
-           and then close the event object after <c>driver_select</c> has
-           returned. Another thread may still be using the event object
-           internally. To safely close an event object call
-           <c>driver_select</c> with <c>ERL_DRV_USE</c> and <c>on==0</c>. That
-           will clear all events and then call
-           <seealso marker="driver_entry#stop_select">stop_select</seealso>
-           when it is safe to close the event object.
-           <c>ERL_DRV_USE</c> should be set together with the first event
-           for an event object. It is harmless to set <c>ERL_DRV_USE</c>
-           even though it already has been done. Clearing all events but keeping
-           <c>ERL_DRV_USE</c> set will indicate that we are using the event
-           object and probably will set events for it again.</p>
-    <note>
-      <p>ERL_DRV_USE was added in OTP release R13. Old drivers will still work
-         as before. But it is recommended to update them to use <c>ERL_DRV_USE</c> and
-         <c>stop_select</c> to make sure that event objects are closed in a safe way.</p>
-    </note>
-        <p>The return value is 0 (failure, -1, only if the
-          <c>ready_input</c>/<c>ready_output</c> is
-          <c>NULL</c>).</p>
+          events. A fired read event calls
+          <seealso marker="driver_entry#ready_input">
+          <c>ready_input</c></seealso> and a fired write event calls
+          <seealso marker="driver_entry#ready_output">
+          <c>ready_output</c></seealso>.</p>
+        <note>
+          <p>Some OS (Windows) do not differentiate between read and write
+            events. The callback for a fired event then only depends on the
+            value of <c>mode</c>.</p>
+        </note>
+        <p><c>ERL_DRV_USE</c> specifies if we are using the event object or
+          if we want to close it.
+          On an emulator with SMP support, it is not safe to clear all events
+          and then close the event object after <c>driver_select</c> has
+          returned. Another thread can still be using the event object
+          internally. To safely close an event object, call
+          <c>driver_select</c> with <c>ERL_DRV_USE</c> and <c>on==0</c>, which
+          clears all events. Then call
+          <seealso marker="driver_entry#stop_select">
+          <c>stop_select</c></seealso> when it is safe to close the event
+          object. <c>ERL_DRV_USE</c> is to be set together with the first event
+          for an event object. It is harmless to set <c>ERL_DRV_USE</c>
+          even if it already has been done. Clearing all events but keeping
+          <c>ERL_DRV_USE</c> set indicates that we are using the event
+          object and probably will set events for it again.</p>
+        <note>
+          <p><c>ERL_DRV_USE</c> was added in Erlang/OTP R13. Old drivers still
+            work as before, but it is recommended to update them to use
+            <c>ERL_DRV_USE</c> and <c>stop_select</c> to ensure that event
+            objects are closed in a safe way.</p>
+        </note>
+        <p>The return value is <c>0</c>, unless
+          <c>ready_input</c>/<c>ready_output</c> is <c>NULL</c>, in which case
+          it is <c>-1</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_send_term(ErlDrvPort port, ErlDrvTermData receiver, ErlDrvTermData* term, int n)</nametext></name>
-      <fsummary>Send term data to other process than port owner process</fsummary>
+      <name><ret>int</ret><nametext>driver_send_term(ErlDrvPort port,
+        ErlDrvTermData receiver, ErlDrvTermData* term, int n)</nametext></name>
+      <fsummary>Send term data to other process than port owner process.
+      </fsummary>
       <desc>
         <marker id="driver_send_term"></marker>
-	<warning><p><c>driver_send_term()</c> is deprecated and will
-	            be removed in the OTP-R17 release. Use
-		    <seealso marker="#erl_drv_send_term">erl_drv_send_term()</seealso>
-		    instead.</p>
-		 <p>Also note that parameters of <c>driver_send_term()</c>
-		    cannot be properly checked by the runtime system when
-		    executed by arbitrary threads. This may cause the
-		    <c>driver_send_term()</c> function not to fail when
-		    it should.</p>
-	</warning>
-        <p>The parameters <c>term</c> and <c>n</c> do the same thing
-          as in <seealso marker="#erl_drv_output_term">erl_drv_output_term()</seealso>.</p>
+        <warning>
+          <p><em>This function is deprecated.</em>
+            Use <seealso marker="#erl_drv_send_term">
+            <c>erl_drv_send_term</c></seealso> instead.</p>
+        </warning>
+        <note>
+          <p>The parameters of this function
+            cannot be properly checked by the runtime system when
+            executed by arbitrary threads. This can cause the
+            function not to fail when it should.</p>
+        </note>
+        <p>Parameters <c>term</c> and <c>n</c> work as in
+          <seealso marker="#erl_drv_output_term">
+          <c>erl_drv_output_term</c></seealso>.</p>
         <p>This function is only thread-safe when the emulator with SMP
           support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>driver_set_timer(ErlDrvPort port, unsigned long time)</nametext></name>
-      <fsummary>Set a timer to call the driver</fsummary>
+      <name><ret>int</ret><nametext>driver_set_timer(ErlDrvPort port, unsigned
+        long time)</nametext></name>
+      <fsummary>Set a timer to call the driver.</fsummary>
       <desc>
         <marker id="driver_set_timer"></marker>
-        <p>This function sets a timer on the driver, which will count
-          down and call the driver when it is timed out. The
-          <c>time</c> parameter is the time in milliseconds before the
-          timer expires.</p>
-        <p>When the timer reaches 0 and expires, the driver entry
-          function <seealso marker="driver_entry#timeout">timeout</seealso> is called.</p>
-        <p>Note that there is only one timer on each driver instance;
-          setting a new timer will replace an older one.</p>
-        <p>Return value is 0 (-1 only when the <c>timeout</c> driver
-          function is <c>NULL</c>).</p>
+        <p>Sets a timer on the driver, which will count
+          down and call the driver when it is timed out. Parameter
+          <c>time</c> is the time in milliseconds before the timer expires.</p>
+        <p>When the timer reaches <c>0</c> and expires, the driver entry
+          function <seealso marker="driver_entry#timeout">
+          <c>timeout</c></seealso> is called.</p>
+        <p>Notice that only one timer exists on each driver instance;
+          setting a new timer replaces an older one.</p>
+        <p>Return value is <c>0</c>, unless the <c>timeout</c>
+          driver function is <c>NULL</c>, in which case it is <c>-1</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvSizeT</ret><nametext>driver_sizeq(ErlDrvPort port)</nametext></name>
-      <fsummary>Return the size of the driver queue</fsummary>
+      <name><ret>ErlDrvSizeT</ret>
+        <nametext>driver_sizeq(ErlDrvPort port)</nametext></name>
+      <fsummary>Return the size of the driver queue.</fsummary>
       <desc>
         <marker id="driver_sizeq"></marker>
-        <p>This function returns the number of bytes currently in the
-          driver queue.</p>
-        <p>This function can be called from an arbitrary thread if a
+        <p>Returns the number of bytes currently in the driver queue.</p>
+        <p>This function can be called from any thread if a
           <seealso marker="#ErlDrvPDL">port data lock</seealso>
           associated with the <c>port</c> is locked by the calling
           thread during the call.</p>
@@ -1856,585 +1996,523 @@ typedef struct ErlIOVec {
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>driver_system_info(ErlDrvSysInfo *sys_info_ptr, size_t size)</nametext></name>
-      <fsummary>Get information about the Erlang runtime system</fsummary>
+      <name><ret>void</ret><nametext>driver_system_info(ErlDrvSysInfo
+        *sys_info_ptr, size_t size)</nametext></name>
+      <fsummary>Get information about the Erlang runtime system.</fsummary>
       <desc>
         <marker id="driver_system_info"></marker>
-        <p>This function will write information about the Erlang runtime
-          system into the
-          <seealso marker="#ErlDrvSysInfo">ErlDrvSysInfo</seealso>
+        <p>Writes information about the Erlang runtime system into the
+          <seealso marker="#ErlDrvSysInfo"><c>ErlDrvSysInfo</c></seealso>
           structure referred to by the first argument. The second
-          argument should be the size of the
-          <seealso marker="#ErlDrvSysInfo">ErlDrvSysInfo</seealso>
-          structure, i.e., <c>sizeof(ErlDrvSysInfo)</c>.</p>
-        <p>See the documentation of the
-          <seealso marker="#ErlDrvSysInfo">ErlDrvSysInfo</seealso>
-          structure for information about specific fields.</p>
+          argument is to be the size of the
+          <seealso marker="#ErlDrvSysInfo"><c>ErlDrvSysInfo</c></seealso>
+          structure, that is, <c>sizeof(ErlDrvSysInfo)</c>.</p>
+        <p>For information about specific fields, see
+          <seealso marker="#ErlDrvSysInfo"><c>ErlDrvSysInfo</c></seealso>.</p>
       </desc>
     </func>
-<func>
-      <name><ret>ErlDrvSizeT</ret><nametext>driver_vec_to_buf(ErlIOVec *ev, char *buf, ErlDrvSizeT len)</nametext></name>
-      <fsummary>Collect data segments into a buffer</fsummary>
+
+    <func>
+      <name><ret>ErlDrvSizeT</ret><nametext>driver_vec_to_buf(ErlIOVec *ev,
+        char *buf, ErlDrvSizeT len)</nametext></name>
+      <fsummary>Collect data segments into a buffer.</fsummary>
       <desc>
         <marker id="driver_vec_to_buf"></marker>
-        <p>This function collects several segments of data, referenced
+        <p>Collects several segments of data, referenced
           by <c>ev</c>, by copying them in order to the buffer
           <c>buf</c>, of the size <c>len</c>.</p>
         <p>If the data is to be sent from the driver to the port owner
-          process, it is faster to use <c>driver_outputv</c>.</p>
-        <p>The return value is the space left in the buffer, i.e. if
-          the <c>ev</c> contains less than <c>len</c> bytes it's the
-          difference, and if <c>ev</c> contains <c>len</c> bytes or
-          more, it's 0. This is faster if there is more than one header byte,
-          since the binary syntax can construct integers directly from
+          process, it is faster to use
+          <seealso marker="#driver_outputv"><c>driver_outputv</c></seealso>.</p>
+        <p>The return value is the space left in the buffer, that is, if
+          <c>ev</c> contains less than <c>len</c> bytes it is the
+          difference, and if <c>ev</c> contains <c>len</c> bytes or more,
+          it is <c>0</c>. This is faster if there is more than one header byte,
+          as the binary syntax can construct integers directly from
           the binary.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_busy_msgq_limits(ErlDrvPort port, ErlDrvSizeT *low, ErlDrvSizeT *high)</nametext></name>
-      <fsummary>Set and get limits for busy port message queue</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_busy_msgq_limits(ErlDrvPort port,
+        ErlDrvSizeT *low, ErlDrvSizeT *high)</nametext></name>
+      <fsummary>Set and get limits for busy port message queue.</fsummary>
       <desc>
         <marker id="erl_drv_busy_msgq_limits"></marker>
         <p>Sets and gets limits that will be used for controling the
-	busy state of the port message queue.</p>
-	<p>The port message queue will be set into a busy
-	state when the amount of command data queued on the
-	message	queue reaches the <c>high</c> limit. The port
-	message	queue will be set into a not busy state when the
-	amount of command data queued on the message queue falls
-	below the <c>low</c> limit. Command data is in this
-	context data passed to the port using either
-	<c>Port ! {Owner, {command, Data}}</c>, or
-	<c>port_command/[2,3]</c>. Note that these limits
-	only concerns command data that have not yet reached the
-	port. The <seealso marker="#set_busy_port">busy port</seealso>
-	feature can be used for data that has reached the port.</p>
-
-	<p>Valid limits are values in the range
-	<c>[ERL_DRV_BUSY_MSGQ_LIM_MIN, ERL_DRV_BUSY_MSGQ_LIM_MAX]</c>.
-	Limits will be automatically adjusted to be sane. That is,
-	the system will	adjust values so that the low limit used is
-	lower than or equal to the high limit used. By default the high
-	limit will be 8 kB and the low limit will be 4 kB.</p>
-
-	<p>By passing a pointer to an integer variable containing
-	the value <c>ERL_DRV_BUSY_MSGQ_READ_ONLY</c>, currently used
-	limit will be read and written back to the integer variable.
-	A new limit can be set by passing a pointer to an integer
-	variable containing a valid limit. The passed value will be
-	written to the internal limit. The internal limit will then
-	be adjusted. After this the adjusted limit will be written
-	back to the integer variable from which the new value was
-	read. Values are in bytes.</p>
-
-	<p>The busy message queue feature can be disabled either
-	by setting the <c>ERL_DRV_FLAG_NO_BUSY_MSGQ</c>
-	<seealso marker="driver_entry#driver_flags">driver flag</seealso>
-	in the <seealso marker="driver_entry">driver_entry</seealso>
-	used by the driver, or by calling this function with
-	<c>ERL_DRV_BUSY_MSGQ_DISABLED</c> as a limit (either low or
-	high). When this feature has been disabled it cannot be
-	enabled again. When reading the limits both of them
-	will be <c>ERL_DRV_BUSY_MSGQ_DISABLED</c>, if this
-	feature has been disabled.</p>
-
-	<p>Processes sending command data to the port will be suspended
-	if either the port is busy or if the port message queue is
-	busy. Suspended processes will be resumed when neither the
-	port is busy, nor the port message queue is busy.</p>
-
-	<p>For information about busy port functionality
-	see the documentation of the
-	<seealso marker="#set_busy_port">set_busy_port()</seealso>
-	function.</p>
-      </desc>
-    </func>
-
-    <func>
-      <name><ret>void</ret><nametext>erl_drv_cond_broadcast(ErlDrvCond *cnd)</nametext></name>
-      <fsummary>Broadcast on a condition variable</fsummary>
+          busy state of the port message queue.</p>
+        <p>The port message queue is set into a busy
+          state when the amount of command data queued on the
+          message queue reaches the <c>high</c> limit. The port
+          message queue is set into a not busy state when the
+          amount of command data queued on the message queue falls
+          below the <c>low</c> limit. Command data is in this
+          context data passed to the port using either
+          <c>Port ! {Owner, {command, Data}}</c> or
+          <c>port_command/[2,3]</c>. Notice that these limits
+          only concerns command data that have not yet reached the
+          port. The <seealso marker="#set_busy_port">busy port</seealso>
+          feature can be used for data that has reached the port.</p>
+        <p>Valid limits are values in the range
+          <c>[ERL_DRV_BUSY_MSGQ_LIM_MIN, ERL_DRV_BUSY_MSGQ_LIM_MAX]</c>.
+          Limits are automatically adjusted to be sane. That is,
+          the system adjusts values so that the low limit used is
+          lower than or equal to the high limit used. By default the high
+          limit is 8 kB and the low limit is 4 kB.</p>
+        <p>By passing a pointer to an integer variable containing
+          the value <c>ERL_DRV_BUSY_MSGQ_READ_ONLY</c>, the currently used
+          limit is read and written back to the integer variable.
+          A new limit can be set by passing a pointer to an integer
+          variable containing a valid limit. The passed value is
+          written to the internal limit. The internal limit is then
+          adjusted. After this the adjusted limit is written
+          back to the integer variable from which the new value was
+          read. Values are in bytes.</p>
+        <p>The busy message queue feature can be disabled either
+          by setting the <c>ERL_DRV_FLAG_NO_BUSY_MSGQ</c>
+          <seealso marker="driver_entry#driver_flags">driver flag</seealso>
+          in the <seealso marker="driver_entry"><c>driver_entry</c></seealso>
+          used by the driver, or by calling this function with
+          <c>ERL_DRV_BUSY_MSGQ_DISABLED</c> as a limit (either low or
+          high). When this feature has been disabled, it cannot be
+          enabled again. When reading the limits, both are
+          <c>ERL_DRV_BUSY_MSGQ_DISABLED</c> if this
+          feature has been disabled.</p>
+        <p>Processes sending command data to the port are suspended
+          if either the port is busy or if the port message queue is
+          busy. Suspended processes are resumed when neither the
+          port or the port message queue is busy.</p>
+        <p>For information about busy port functionality, see
+          <seealso marker="#set_busy_port"><c>set_busy_port</c></seealso>.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>void</ret><nametext>erl_drv_cond_broadcast(ErlDrvCond
+        *cnd)</nametext></name>
+      <fsummary>Broadcast on a condition variable.</fsummary>
       <desc>
         <marker id="erl_drv_cond_broadcast"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>cnd</c></tag>
-          <item>A pointer to a condition variable to broadcast on.</item>
-        </taglist>
-        <p>This function broadcasts on a condition variable. That is, if
-	   other threads are waiting on the condition variable being
-	   broadcast on, <em>all</em> of them will be woken.
-	</p>
+        <p>Broadcasts on a condition variable. That is, if
+          other threads are waiting on the condition variable being
+          broadcast on, <em>all</em> of them are woken.</p>
+        <p><c>cnd</c> is a pointer to a condition variable to broadcast on.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvCond *</ret><nametext>erl_drv_cond_create(char *name)</nametext></name>
-      <fsummary>Create a condition variable</fsummary>
+      <name><ret>ErlDrvCond *</ret><nametext>erl_drv_cond_create(char
+        *name)</nametext></name>
+      <fsummary>Create a condition variable.</fsummary>
       <desc>
         <marker id="erl_drv_cond_create"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>name</c></tag>
-          <item>A string identifying the created condition variable. It
-	        will be used to identify the condition variable in planned
-		future debug functionality.
-	  </item>
-        </taglist>
-        <p>This function creates a condition variable and returns a
-	   pointer to it. On failure <c>NULL</c> is returned. The driver
-	   creating the condition variable has the responsibility of
-	   destroying it before the driver is unloaded.</p>
+        <p>Creates a condition variable and returns a pointer to it.</p> 
+        <p><c>name</c> is a string identifying the created condition variable.
+          It is used to identify the condition variable in planned
+          future debug functionality.</p>
+        <p>Returns <c>NULL</c> on failure. The driver
+          creating the condition variable is responsibile for
+          destroying it before the driver is unloaded.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_cond_destroy(ErlDrvCond *cnd)</nametext></name>
-      <fsummary>Destroy a condition variable</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_cond_destroy(ErlDrvCond
+        *cnd)</nametext></name>
+      <fsummary>Destroy a condition variable.</fsummary>
       <desc>
         <marker id="erl_drv_cond_destroy"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>cnd</c></tag>
-          <item>A pointer to a condition variable to destroy.</item>
-        </taglist>
-        <p>This function destroys a condition variable previously
-	   created by
-	   <seealso marker="#erl_drv_cond_create">erl_drv_cond_create()</seealso>.
-	</p>
-      <p>This function is thread-safe.</p>
-      </desc>
-    </func>
-	<func>
-		<name><ret>char *</ret><nametext>erl_drv_cond_name(ErlDrvCond *cnd)</nametext></name>
-		<fsummary>Get name of driver mutex.</fsummary>
-		<desc>
-			<marker id="erl_drv_cnd_name"></marker>
-			<p>Arguments:</p>
-			<taglist>
-				<tag><c>cnd</c></tag>
-				<item>A pointer to an initialized condition.</item>
-			</taglist>
-			<p>
-				Returns a pointer to the name of the condition.
-			</p>
-			<note>
-				<p>This function is intended for debugging purposes only.</p>
-			</note>
-		</desc>
-	</func>
-
-    <func>
-      <name><ret>void</ret><nametext>erl_drv_cond_signal(ErlDrvCond *cnd)</nametext></name>
-      <fsummary>Signal on a condition variable</fsummary>
+        <p>Destroys a condition variable previously created by
+          <seealso marker="#erl_drv_cond_create">
+          <c>erl_drv_cond_create</c></seealso>.</p>
+        <p><c>cnd</c> is a pointer to a condition variable to destroy.</p>
+        <p>This function is thread-safe.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>char *</ret><nametext>erl_drv_cond_name(ErlDrvCond
+        *cnd)</nametext></name>
+      <fsummary>Get name of driver mutex.</fsummary>
+      <desc>
+        <marker id="erl_drv_cnd_name"></marker>
+        <p>Returns a pointer to the name of the condition.</p>
+        <p><c>cnd</c> is a  pointer to an initialized condition.</p>
+        <note>
+          <p>This function is intended for debugging purposes only.</p>
+        </note>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>void</ret><nametext>erl_drv_cond_signal(ErlDrvCond
+        *cnd)</nametext></name>
+      <fsummary>Signal on a condition variable.</fsummary>
       <desc>
         <marker id="erl_drv_cond_signal"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>cnd</c></tag>
-          <item>A pointer to a condition variable to signal on.</item>
-        </taglist>
-        <p>This function signals on a condition variable. That is, if
-	   other threads are waiting on the condition variable being
-	   signaled, <em>one</em> of them will be woken.
-	</p>
+        <p>Signals on a condition variable. That is, if
+          other threads are waiting on the condition variable being
+          signaled, <em>one</em> of them is woken.</p>
+        <p><c>cnd</c> is a pointer to a condition variable to signal on.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_cond_wait(ErlDrvCond *cnd, ErlDrvMutex *mtx)</nametext></name>
-      <fsummary>Wait on a condition variable</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_cond_wait(ErlDrvCond *cnd,
+        ErlDrvMutex *mtx)</nametext></name>
+      <fsummary>Wait on a condition variable.</fsummary>
       <desc>
         <marker id="erl_drv_cond_wait"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>cnd</c></tag>
-          <item>A pointer to a condition variable to wait on.</item>
-          <tag><c>mtx</c></tag>
-          <item>A pointer to a mutex to unlock while waiting.</item>
-          <tag><c></c></tag>
-          <item></item>
-        </taglist>
-        <p>This function waits on a condition variable. The calling
-	   thread is blocked until another thread wakes it by signaling
-	   or broadcasting on the condition variable. Before the calling
-	   thread is blocked it unlocks the mutex passed as argument, and
-	   when the calling thread is woken it locks the same mutex before
-	   returning. That is, the mutex currently has to be locked by
-	   the calling thread when calling this function.
-	</p>
-	<note><p><c>erl_drv_cond_wait()</c> might return even though
-	         no-one has signaled or broadcast on the condition
-		 variable. Code calling <c>erl_drv_cond_wait()</c> should
-		 always be prepared for <c>erl_drv_cond_wait()</c>
-		 returning even though the condition that the thread was
-		 waiting for hasn't occurred. That is, when returning from
-		 <c>erl_drv_cond_wait()</c> always check if the condition
-		 has occurred, and if not call <c>erl_drv_cond_wait()</c>
-		 again.
-	</p></note>
+        <p>Waits on a condition variable. The calling
+          thread is blocked until another thread wakes it by signaling
+          or broadcasting on the condition variable. Before the calling
+          thread is blocked, it unlocks the mutex passed as argument.
+          When the calling thread is woken, it locks the same mutex before
+          returning. That is, the mutex currently must be locked by
+          the calling thread when calling this function.</p>
+        <p><c>cnd</c> is a pointer to a condition variable to wait on.
+          <c>mtx</c> is a pointer to a mutex to unlock while waiting.</p>
+        <note>
+          <p><c>erl_drv_cond_wait</c> can return even if
+            no one has signaled or broadcast on the condition
+            variable. Code calling <c>erl_drv_cond_wait</c> is
+            always to be prepared for <c>erl_drv_cond_wait</c>
+            returning even if the condition that the thread was
+            waiting for has not occurred. That is, when returning from
+            <c>erl_drv_cond_wait</c>, always check if the condition
+            has occurred, and if not call <c>erl_drv_cond_wait</c>  again.</p>
+        </note>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_consume_timeslice(ErlDrvPort port, int percent)</nametext></name>
+      <name><ret>int</ret><nametext>erl_drv_consume_timeslice(ErlDrvPort port,
+        int percent)</nametext></name>
       <fsummary>Give the runtime system a hint about how much CPU time the
-      current driver callback call has consumed</fsummary>
+        current driver callback call has consumed.</fsummary>
       <desc>
         <marker id="erl_drv_consume_timeslice"></marker>
-        <p>Arguments:</p>
+        <p>Gives the runtime system a hint about how much CPU time the current
+          driver callback call has consumed since the last hint, or since the
+          the start of the callback if no previous hint has been given.</p>
         <taglist>
           <tag><c>port</c></tag>
           <item>Port handle of the executing port.</item>
           <tag><c>percent</c></tag>
           <item>Approximate consumed fraction of a full
-	  time-slice in percent.</item>
+            time-slice in percent.</item>
         </taglist>
-	<p>Give the runtime system a hint about how much CPU time the
-	current driver callback call has consumed since last hint, or
-	since the start of the callback if no previous hint has been given.
-	The time is given as a fraction, in percent, of a full time-slice
-	that a port is allowed to execute before it should surrender the
-	CPU to other runnable ports or processes. Valid range is
-	<c>[1, 100]</c>. The scheduling time-slice is not an exact entity,
-	but can usually be approximated to about 1 millisecond.</p>
-
-	<p>Note that it is up to the runtime system to determine if and
-	how to	use this information. Implementations on some platforms
-	may use other means in order to determine the consumed fraction
-	of the time-slice. Lengthy driver callbacks should regardless of
-	this frequently call the <c>erl_drv_consume_timeslice()</c>
-	function in order to determine if it is allowed to continue
-	execution or not.</p>
-
-	<p><c>erl_drv_consume_timeslice()</c> returns a non-zero value
-	if the time-slice has been exhausted, and zero if the callback is
-	allowed to continue execution. If a non-zero value is
-	returned the driver callback should return as soon as possible in
-	order for the port to be able to yield.</p>
-
-	<p>This function is provided to better support co-operative scheduling,
-	improve system responsiveness, and to make it easier to prevent
-	misbehaviors of the VM due to a port monopolizing a scheduler thread.
-	It can be used when dividing length work into a number of repeated
-	driver callback calls without the need to use threads. Also see the
-	important <seealso marker="#WARNING">warning</seealso> text at the
-	beginning of this document.</p>
-      </desc>
-    </func>
-
-	<func>
-	  <name><ret>ErlDrvTime</ret><nametext>erl_drv_convert_time_unit(ErlDrvTime val, ErlDrvTimeUnit from, ErlDrvTimeUnit to)</nametext></name>
-	  <fsummary>Convert time unit of a time value</fsummary>
-	  <desc>
-	    <marker id="erl_drv_convert_time_unit"></marker>
-	    <p>Arguments:</p>
-	    <taglist>
-	      <tag><c>val</c></tag>
-	      <item>Value to convert time unit for.</item>
-	      <tag><c>from</c></tag>
-	      <item>Time unit of <c>val</c>.</item>
-	      <tag><c>to</c></tag>
-	      <item>Time unit of returned value.</item>
-	    </taglist>
-	    <p>Converts the <c>val</c> value of time unit <c>from</c> to
-	    the corresponding value of time unit <c>to</c>. The result is
-	    rounded using the floor function.</p>
-	    <p>Returns <c>ERL_DRV_TIME_ERROR</c> if called with an invalid
-	    time unit argument.</p>
-	    <p>See also:</p>
-	    <list>
-	      <item><seealso marker="#ErlDrvTime"><c>ErlDrvTime</c></seealso></item>
-	      <item><seealso marker="#ErlDrvTimeUnit"><c>ErlDrvTimeUnit</c></seealso></item>
-	    </list>
-	  </desc>
-	</func>
-
-    <func>
-      <name><ret>int</ret><nametext>erl_drv_equal_tids(ErlDrvTid tid1, ErlDrvTid tid2)</nametext></name>
-      <fsummary>Compare thread identifiers for equality</fsummary>
-      <desc>
-        <marker id="erl_drv_equal_tids"></marker>
-        <p>Arguments:</p>
+        <p>The time is specified as a fraction, in percent, of a full time-slice
+          that a port is allowed to execute before it is to surrender the
+          CPU to other runnable ports or processes. Valid range is
+          <c>[1, 100]</c>. The scheduling time-slice is not an exact entity,
+          but can usually be approximated to about 1 millisecond.</p>
+        <p>Notice that it is up to the runtime system to determine if and
+          how to use this information. Implementations on some platforms
+          can use other means to determine the consumed fraction
+          of the time-slice. Lengthy driver callbacks should, regardless of
+          this frequently, call this function to determine if it is allowed
+          to continue execution or not.</p>
+        <p>This function returns a non-zero value
+          if the time-slice has been exhausted, and zero if the callback is
+          allowed to continue execution. If a non-zero value is
+          returned, the driver callback is to return as soon as possible in
+          order for the port to be able to yield.</p>
+        <p>This function is provided to better support co-operative scheduling,
+          improve system responsiveness, and to make it easier to prevent
+          misbehaviors of the VM because of a port monopolizing a scheduler
+          thread. It can be used when dividing lengthy work into some repeated
+          driver callback calls, without the need to use threads.</p>
+        <p>See also the important <seealso marker="#WARNING">warning</seealso>
+          text at the beginning of this manual page.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>ErlDrvTime</ret><nametext>erl_drv_convert_time_unit(ErlDrvTime
+        val, ErlDrvTimeUnit from, ErlDrvTimeUnit to)</nametext></name>
+      <fsummary>Convert time unit of a time value.</fsummary>
+      <desc>
+        <marker id="erl_drv_convert_time_unit"></marker>
+        <p>Converts the <c>val</c> value of time unit <c>from</c> to
+          the corresponding value of time unit <c>to</c>. The result is
+          rounded using the floor function.</p>
         <taglist>
-          <tag><c>tid1</c></tag>
-          <item>A thread identifier.</item>
-          <tag><c>tid2</c></tag>
-          <item>A thread identifier.</item>
+          <tag><c>val</c></tag>
+          <item>Value to convert time unit for.</item>
+          <tag><c>from</c></tag>
+          <item>Time unit of <c>val</c>.</item>
+          <tag><c>to</c></tag>
+          <item>Time unit of returned value.</item>
         </taglist>
-        <p>This function compares two thread identifiers for equality,
-	   and returns <c>0</c> it they aren't equal, and
-	   a value not equal to <c>0</c> if they are equal.</p>
-	<note><p>A Thread identifier may be reused very quickly after
-	         a thread has terminated. Therefore, if a thread
-		 corresponding to one of the involved thread identifiers
-		 has terminated since the thread identifier was saved,
-		 the result of <c>erl_drv_equal_tids()</c> might not give
-		 the expected result.
-	</p></note>
+        <p>Returns <c>ERL_DRV_TIME_ERROR</c> if called with an invalid
+          time unit argument.</p>
+        <p>See also <seealso marker="#ErlDrvTime">
+          <c>ErlDrvTime</c></seealso> and
+          <seealso marker="#ErlDrvTimeUnit">
+          <c>ErlDrvTimeUnit</c></seealso>.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>int</ret><nametext>erl_drv_equal_tids(ErlDrvTid tid1,
+        ErlDrvTid tid2)</nametext></name>
+      <fsummary>Compare thread identifiers for equality.</fsummary>
+      <desc>
+        <marker id="erl_drv_equal_tids"></marker>
+        <p>Compares two thread identifiers, <c>tid1</c> and <c>tid2</c>,
+          for equality.</p>
+        <p>Returns <c>0</c> it they are not equal, and a value not equal to
+          <c>0</c> if they are equal.</p>
+        <note>
+          <p>A thread identifier can be reused very quickly after
+            a thread has terminated. Therefore, if a thread
+            corresponding to one of the involved thread identifiers
+            has terminated since the thread identifier was saved,
+            the result of <c>erl_drv_equal_tids</c> does possibly not give
+            the expected result.</p>
+        </note>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_getenv(const char *key, char *value, size_t *value_size)</nametext></name>
-      <fsummary>Get the value of an environment variable</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_getenv(const char *key, char
+        *value, size_t *value_size)</nametext></name>
+      <fsummary>Get the value of an environment variable.</fsummary>
       <desc>
         <marker id="erl_drv_getenv"></marker>
-        <p>Arguments:</p>
+        <p>Retrieves the value of an environment variable.</p>
         <taglist>
           <tag><c>key</c></tag>
-          <item>A null terminated string containing the
-	        name of the environment variable.</item>
+          <item>A <c>NULL</c>-terminated string containing the
+            name of the environment variable.</item>
           <tag><c>value</c></tag>
           <item>A pointer to an output buffer.</item>
           <tag><c>value_size</c></tag>
-          <item>A pointer to an integer. The integer is both used for
-	        passing input and output sizes (see below).
-		</item>
+          <item>A pointer to an integer. The integer is used both for
+            passing input and output sizes (see below).</item>
         </taglist>
-	<p>This function retrieves the value of an environment variable.
-	When called, <c>*value_size</c> should contain the size of
-	the <c>value</c> buffer. On success <c>0</c> is returned,
-	the value of the environment variable has been written to
-	the <c>value</c> buffer, and <c>*value_size</c> contains the
-	string length (excluding the terminating null character) of
-	the value written to the <c>value</c> buffer. On failure,
-	i.e., no such environment variable was found, a value less than
-	<c>0</c> is returned. When the size of the <c>value</c>
-	buffer is too small, a value greater than <c>0</c> is returned
-	and <c>*value_size</c> has been set to the buffer size needed.
-	</p>
-	<warning><p>Do <em>not</em> use libc's <c>getenv</c> or similar
-	         C library interfaces from a driver.
-	</p></warning>
+        <p>When this function is called, <c>*value_size</c> is to contain the
+          size of the <c>value</c> buffer.</p>
+        <p>On success, <c>0</c> is returned,
+          the value of the environment variable has been written to
+          the <c>value</c> buffer, and <c>*value_size</c> contains the
+          string length (excluding the terminating <c>NULL</c> character) of
+          the value written to the <c>value</c> buffer.</p>
+        <p>On failure, that is, no such environment variable was found,
+          a value &lt; <c>0</c> is returned. When the size of the <c>value</c>
+          buffer is too small, a value &gt; <c>0</c> is returned and
+          <c>*value_size</c> has been set to the buffer size needed.</p>
+        <warning>
+          <p>Do <em>not</em> use libc's <c>getenv</c> or similar C library
+            interfaces from a driver.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_init_ack(ErlDrvPort port, ErlDrvData res)</nametext></name>
-      <fsummary>Acknowledge the start of the port</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_init_ack(ErlDrvPort port,
+        ErlDrvData res)</nametext></name>
+      <fsummary>Acknowledge the start of the port.</fsummary>
       <desc>
         <marker id="erl_drv_init_ack"></marker>
-        <p>Arguments:</p>
+        <p>Acknowledges the start of the port.</p>
         <taglist>
           <tag><c>port</c></tag>
-          <item>The port handle of the port (driver instance) creating
-           doing the acknowledgment.
+          <item>The port handle of the port (driver instance)
+            doing the acknowledgment.
 	  </item>
           <tag><c>res</c></tag>
-          <item>The result of the port initialization. This can be the same values
-          as the return value of <seealso marker="driver_entry#start">start</seealso>,
-          i.e any of the error codes or the ErlDrvData that is to be used for this
-          port.
+          <item>The result of the port initialization. Can be the same
+            values as the return value of <seealso marker="driver_entry#start">
+            <c>start</c></seealso>, that is, any of the error codes or the
+            <c>ErlDrvData</c> that is to be used for this port.
           </item>
         </taglist>
-        <p>
-          When this function is called the initiating erlang:open_port call is
-          returned as if the <seealso marker="driver_entry#start">start</seealso>
-          function had just been called. It can only be used when the
-          <seealso marker="driver_entry#driver_flags">ERL_DRV_FLAG_USE_INIT_ACK</seealso>
-          flag has been set on the linked-in driver.
-        </p>
-      </desc>
-    </func>
-
-	<func>
-	  <name><ret>ErlDrvTime</ret><nametext>erl_drv_monotonic_time(ErlDrvTimeUnit time_unit)</nametext></name>
-	  <fsummary>Get Erlang Monotonic Time</fsummary>
-	  <desc>
-	    <marker id="erl_drv_monotonic_time"></marker>
-	    <p>Arguments:</p>
-	    <taglist>
-	      <tag><c>time_unit</c></tag>
-	      <item>Time unit of returned value.</item>
-	    </taglist>
-	    <p>
-	      Returns
-	      <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	      monotonic time</seealso>. Note that it is not uncommon with
-	      negative values.
-	    </p>
-	    <p>Returns <c>ERL_DRV_TIME_ERROR</c> if called with an invalid
-	    time unit argument, or if called from a thread that is not a
-	    scheduler thread.</p>
-	    <p>See also:</p>
-	    <list>
-	      <item><seealso marker="#ErlDrvTime"><c>ErlDrvTime</c></seealso></item>
-	      <item><seealso marker="#ErlDrvTimeUnit"><c>ErlDrvTimeUnit</c></seealso></item>
-	    </list>
-	  </desc>
-	</func>
-
-    <func>
-      <name><ret>ErlDrvMutex *</ret><nametext>erl_drv_mutex_create(char *name)</nametext></name>
-      <fsummary>Create a mutex</fsummary>
+        <p>When this function is called the initiating <c>erlang:open_port</c>
+          call is returned as if the <seealso marker="driver_entry#start">
+          <c>start</c></seealso> function had just been called. It can only be
+          used when flag <seealso marker="driver_entry#driver_flags">
+          <c>ERL_DRV_FLAG_USE_INIT_ACK</c></seealso>
+          has been set on the linked-in driver.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>ErlDrvTime</ret>
+        <nametext>erl_drv_monotonic_time(ErlDrvTimeUnit time_unit)</nametext>
+      </name>
+      <fsummary>Get Erlang monotonic time.</fsummary>
+      <desc>
+        <marker id="erl_drv_monotonic_time"></marker>
+        <p>Returns <seealso marker="time_correction#Erlang_Monotonic_Time">
+          Erlang monotonic time</seealso>. Notice that negative values are
+          not uncommon.</p>
+        <p><c>time_unit</c> is time unit of returned value.</p>
+        <p>Returns <c>ERL_DRV_TIME_ERROR</c> if called with an invalid
+          time unit argument, or if called from a thread that is not a
+          scheduler thread.</p>
+        <p>See also <seealso marker="#ErlDrvTime"><c>ErlDrvTime</c></seealso>
+          and <seealso marker="#ErlDrvTimeUnit">
+          <c>ErlDrvTimeUnit</c></seealso>.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>ErlDrvMutex *</ret><nametext>erl_drv_mutex_create(char
+        *name)</nametext></name>
+      <fsummary>Create a mutex.</fsummary>
       <desc>
         <marker id="erl_drv_mutex_create"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>name</c></tag>
-          <item>A string identifying the created mutex. It will be used
-	        to identify the mutex in planned future debug functionality.
-	  </item>
-        </taglist>
-        <p>This function creates a mutex and returns a pointer to it. On
-	   failure <c>NULL</c> is returned. The driver creating the mutex
-	   has the responsibility of destroying it before the driver is
-	   unloaded.
-	</p>
+        <p>Creates a mutex and returns a pointer to it.</p>
+        <p><c>name</c> is a string identifying the created mutex. It is used
+          to identify the mutex in planned future debug functionality.</p>
+        <p>Returns <c>NULL</c> on failure. The driver creating the mutex is
+          responsible for destroying it before the driver is unloaded.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_mutex_destroy(ErlDrvMutex *mtx)</nametext></name>
-      <fsummary>Destroy a mutex</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_mutex_destroy(ErlDrvMutex
+        *mtx)</nametext></name>
+      <fsummary>Destroy a mutex.</fsummary>
       <desc>
         <marker id="erl_drv_mutex_destroy"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>mtx</c></tag>
-          <item>A pointer to a mutex to destroy.</item>
-        </taglist>
-        <p>This function destroys a mutex previously created by
-	   <seealso marker="#erl_drv_mutex_create">erl_drv_mutex_create()</seealso>.
-	   The mutex has to be in an unlocked state before being
-	   destroyed.
-	</p>
+        <p>Destroys a mutex previously created by
+          <seealso marker="#erl_drv_mutex_create">
+          <c>erl_drv_mutex_create</c></seealso>.
+          The mutex must be in an unlocked state before it is destroyed.</p>
+        <p><c>mtx</c> is a pointer to a mutex to destroy.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_mutex_lock(ErlDrvMutex *mtx)</nametext></name>
-      <fsummary>Lock a mutex</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_mutex_lock(ErlDrvMutex
+        *mtx)</nametext></name>
+      <fsummary>Lock a mutex.</fsummary>
       <desc>
         <marker id="erl_drv_mutex_lock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>mtx</c></tag>
-          <item>A pointer to a mutex to lock.</item>
-        </taglist>
-        <p>This function locks a mutex. The calling thread will be
-	   blocked until the mutex has been locked. A thread
-	   which currently has locked the mutex may <em>not</em> lock
-	   the same mutex again.
-	</p>
-	<warning><p>If you leave a mutex locked in an emulator thread
-	            when you let the thread out of your control, you will
-		    <em>very likely</em> deadlock the whole emulator.
-	</p></warning>
+        <p>Locks a mutex. The calling thread is blocked until the mutex has
+          been locked. A thread that has currently locked the mutex
+          <em>cannot</em> lock the same mutex again.</p>
+        <p><c>mtx</c> is a pointer to a mutex to lock.</p>
+        <warning>
+          <p>If you leave a mutex locked in an emulator thread
+            when you let the thread out of your control, you will
+            <em>very likely</em> deadlock the whole emulator.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
-	<func>
-		<name><ret>char *</ret><nametext>erl_drv_mutex_name(ErlDrvMutex *mtx)</nametext></name>
-		<fsummary>Get name of driver mutex.</fsummary>
-		<desc>
-			<marker id="erl_drv_mutex_name"></marker>
-			<p>Arguments:</p>
-			<taglist>
-				<tag><c>mtx</c></tag>
-				<item>A pointer to an initialized mutex.</item>
-			</taglist>
-			<p>
-				Returns a pointer to the name of the mutex.
-			</p>
-			<note>
-				<p>This function is intended for debugging purposes only.</p>
-			</note>
-		</desc>
-	</func>
+    <func>
+      <name><ret>char *</ret><nametext>erl_drv_mutex_name(ErlDrvMutex
+        *mtx)</nametext></name>
+      <fsummary>Get name of driver mutex.</fsummary>
+      <desc>
+        <marker id="erl_drv_mutex_name"></marker>
+        <p>Returns a pointer to the mutex name.</p>
+        <p><c>mtx</c> is a pointer to an initialized mutex.</p>
+        <note>
+          <p>This function is intended for debugging purposes only.</p>
+        </note>
+      </desc>
+    </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_mutex_trylock(ErlDrvMutex *mtx)</nametext></name>
-      <fsummary>Try lock a mutex</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_mutex_trylock(ErlDrvMutex
+        *mtx)</nametext></name>
+      <fsummary>Try lock a mutex.</fsummary>
       <desc>
         <marker id="erl_drv_mutex_trylock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>mtx</c></tag>
-          <item>A pointer to a mutex to try to lock.</item>
-        </taglist>
-        <p>This function tries to lock a mutex. If successful <c>0</c>,
-	   is returned; otherwise, <c>EBUSY</c> is returned. A thread
-	   which currently has locked the mutex may <em>not</em> try to
-	   lock the same mutex again.
-	</p>
-	<warning><p>If you leave a mutex locked in an emulator thread
-	            when you let the thread out of your control, you will
-		    <em>very likely</em> deadlock the whole emulator.
-	</p></warning>
+        <p>Tries to lock a mutex. A thred that has currently locked the mutex
+          <em>cannot</em> try to lock the same mutex again.</p>
+        <p><c>mtx</c> is a pointer to a mutex to try to lock.</p>
+        <p>Returns <c>0</c> on success, otherwise <c>EBUSY</c>.</p>
+        <warning>
+          <p>If you leave a mutex locked in an emulator thread
+            when you let the thread out of your control, you will
+            <em>very likely</em> deadlock the whole emulator.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_mutex_unlock(ErlDrvMutex *mtx)</nametext></name>
-      <fsummary>Unlock a mutex</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_mutex_unlock(ErlDrvMutex
+        *mtx)</nametext></name>
+      <fsummary>Unlock a mutex.</fsummary>
       <desc>
         <marker id="erl_drv_mutex_unlock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>mtx</c></tag>
-          <item>A pointer to a mutex to unlock.</item>
-        </taglist>
-        <p>This function unlocks a mutex. The mutex currently has to be
-	   locked by the calling thread.
-	</p>
+        <p>Unlocks a mutex. The mutex currently must be
+          locked by the calling thread.</p>
+        <p><c>mtx</c> is a pointer to a mutex to unlock.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_output_term(ErlDrvTermData port, ErlDrvTermData* term, int n)</nametext></name>
-      <fsummary>Send term data from driver to port owner</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_output_term(ErlDrvTermData port,
+        ErlDrvTermData* term, int n)</nametext></name>
+      <fsummary>Send term data from driver to port owner.</fsummary>
       <desc>
         <marker id="erl_drv_output_term"></marker>
-        <p>This functions sends data in the special driver term
+        <p>Sends data in the special driver term
           format to the port owner process. This is a fast way to
-	  deliver term data from a driver. It also needs no binary
-	  conversion, so the port owner process receives data as
-	  normal Erlang terms. The
-	  <seealso marker="#erl_drv_send_term">erl_drv_send_term()</seealso>
-	  functions can be used for sending to any arbitrary process
-	  on the local node.</p>
-	<note><p>Note that the <c>port</c> parameter is <em>not</em>
-	  an ordinary port handle, but a port handle converted using
-	  <c>driver_mk_port()</c>.</p></note>
-        <p>The <c>term</c> parameter points to an array of
-          <c>ErlDrvTermData</c>, with <c>n</c> elements. This array
+          deliver term data from a driver. It needs no binary
+          conversion, so the port owner process receives data as
+          normal Erlang terms. The <seealso marker="#erl_drv_send_term">
+          <c>erl_drv_send_term</c></seealso>
+          functions can be used for sending to any process
+          on the local node.</p>
+        <note>
+          <p>Parameter <c>port</c> is <em>not</em>
+            an ordinary port handle, but a port handle converted using
+            <seealso marker="#driver_mk_port">
+            <c>driver_mk_port</c></seealso>.</p>
+        </note>
+        <p>Parameter <c>term</c> points to an array of
+          <c>ErlDrvTermData</c> with <c>n</c> elements. This array
           contains terms described in the driver term format. Every
-          term consists of one to four elements in the array. The
-          term first has a term type, and then arguments. The
-	  <c>port</c> parameter specifies the sending port.</p>
-        <p>Tuples, maps and lists (with the exception of strings, see below),
+          term consists of 1-4 elements in the array. The
+          first term has a term type and then arguments.
+          Parameter <c>port</c> specifies the sending port.</p>
+        <p>Tuples, maps, and lists (except strings, see below)
           are built in reverse polish notation, so that to build a
-          tuple, the elements are given first, and then the tuple
+          tuple, the elements are specified first, and then the tuple
           term, with a count. Likewise for lists and maps.</p>
-        <p>A tuple must be specified with the number of elements. (The
-          elements precede the <c>ERL_DRV_TUPLE</c> term.)</p>
-        <p>A list must be specified with the number of elements,
-          including the tail, which is the last term preceding
-          <c>ERL_DRV_LIST</c>.</p>
-        <p>A map must be specified with the number of key-value pairs <c>N</c>.
-	  The key-value pairs must precede the <c>ERL_DRV_MAP</c> in this order:
-	  <c>key1,value1,key2,value2,...,keyN,valueN</c>.
-	  Duplicate keys are not allowed.</p>
+        <list type="bulleted">
+          <item>
+            <p>A tuple must be specified with the number of elements. (The
+              elements precede the <c>ERL_DRV_TUPLE</c> term.)</p>
+          </item>
+          <item>
+            <p>A map must be specified with the number of key-value pairs
+              <c>N</c>. The key-value pairs must precede the <c>ERL_DRV_MAP</c>
+              in this order: <c>key1,value1,key2,value2,...,keyN,valueN</c>.
+              Duplicate keys are not allowed.</p>
+          </item>
+          <item>
+            <p>A list must be specified with the number of elements,
+              including the tail, which is the last term preceding
+              <c>ERL_DRV_LIST</c>.</p>
+          </item>
+        </list>
         <p>The special term <c>ERL_DRV_STRING_CONS</c> is used to
-          "splice" in a string in a list, a string given this way is
-          not a list per se, but the elements are elements of the
+          "splice" in a string in a list, a string specified this way is
+          not a list in itself, but the elements are elements of the
           surrounding list.</p>
         <pre>
-Term type            Argument(s)
-===========================================
+Term type            Arguments
+---------            ---------
 ERL_DRV_NIL
 ERL_DRV_ATOM         ErlDrvTermData atom (from driver_mk_atom(char *string))
 ERL_DRV_INT          ErlDrvSInt integer
@@ -2447,398 +2525,345 @@ ERL_DRV_BUF2BINARY   char *buf, ErlDrvUInt len
 ERL_DRV_STRING       char *str, int len
 ERL_DRV_TUPLE        int sz
 ERL_DRV_LIST         int sz
-ERL_DRV_PID          ErlDrvTermData pid (from driver_connected(ErlDrvPort port) or driver_caller(ErlDrvPort port))
+ERL_DRV_PID          ErlDrvTermData pid (from driver_connected(ErlDrvPort port)
+                     or driver_caller(ErlDrvPort port))
 ERL_DRV_STRING_CONS  char *str, int len
 ERL_DRV_FLOAT        double *dbl
 ERL_DRV_EXT2TERM     char *buf, ErlDrvUInt len
-ERL_DRV_MAP          int sz
-        </pre>
+ERL_DRV_MAP          int sz</pre>
 	<p>The unsigned integer data type <c>ErlDrvUInt</c> and the
 	  signed integer data type <c>ErlDrvSInt</c> are 64 bits wide
-	  on a 64 bit runtime system and 32 bits wide on a 32 bit
-	  runtime system. They were introduced in erts version 5.6,
-	  and replaced some of the <c>int</c> arguments in the list above.
-	</p>
+	  on a 64-bit runtime system and 32 bits wide on a 32-bit
+	  runtime system. They were introduced in <c>ERTS</c> 5.6
+	  and replaced some of the <c>int</c> arguments in the list above.</p>
 	<p>The unsigned integer data type <c>ErlDrvUInt64</c> and the
 	  signed integer data type <c>ErlDrvSInt64</c> are always 64 bits
-	  wide. They were introduced in erts version 5.7.4.
-	</p>
-
-        <p>To build the tuple <c>{tcp, Port, [100 | Binary]}</c>, the
-          following call could be made.</p>
-        <code type="none"><![CDATA[
-    ErlDrvBinary* bin = ...
-    ErlDrvPort port = ...
-    ErlDrvTermData spec[] = {
-        ERL_DRV_ATOM, driver_mk_atom("tcp"),
-        ERL_DRV_PORT, driver_mk_port(drvport),
-            ERL_DRV_INT, 100,
-            ERL_DRV_BINARY, bin, 50, 0,
-            ERL_DRV_LIST, 2,
-        ERL_DRV_TUPLE, 3,
-    };
-    erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));
-        ]]>
-      </code>
-        <p>Where <c>bin</c> is a driver binary of length at least 50
-          and <c>drvport</c> is a port handle. Note that the <c>ERL_DRV_LIST</c>
-          comes after the elements of the list, likewise the
+	  wide. They were introduced in <c>ERTS</c> 5.7.4.</p>
+	<p>To build the tuple <c>{tcp, Port, [100 | Binary]}</c>, the
+	  following call can be made.</p>
+	<code type="none"><![CDATA[
+ErlDrvBinary* bin = ...
+ErlDrvPort port = ...
+ErlDrvTermData spec[] = {
+    ERL_DRV_ATOM, driver_mk_atom("tcp"),
+    ERL_DRV_PORT, driver_mk_port(drvport),
+        ERL_DRV_INT, 100,
+        ERL_DRV_BINARY, bin, 50, 0,
+        ERL_DRV_LIST, 2,
+    ERL_DRV_TUPLE, 3,
+};
+erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));    ]]></code>
+        <p>Here <c>bin</c> is a driver binary of length at least 50 and
+          <c>drvport</c> is a port handle. Notice that <c>ERL_DRV_LIST</c>
+          comes after the elements of the list, likewise
           <c>ERL_DRV_TUPLE</c>.</p>
-        <p>The term <c>ERL_DRV_STRING_CONS</c> is a way to construct
+        <p>The <c>ERL_DRV_STRING_CONS</c> term is a way to construct
           strings. It works differently from how <c>ERL_DRV_STRING</c>
           works. <c>ERL_DRV_STRING_CONS</c> builds a string list in
-          reverse order, (as opposed to how <c>ERL_DRV_LIST</c>
+          reverse order (as opposed to how <c>ERL_DRV_LIST</c>
           works), concatenating the strings added to a list. The tail
-          must be given before <c>ERL_DRV_STRING_CONS</c>.</p>
-        <p>The <c>ERL_DRV_STRING</c> constructs a string, and ends
-          it. (So it's the same as <c>ERL_DRV_NIL</c> followed by
+          must be specifed before <c>ERL_DRV_STRING_CONS</c>.</p>
+        <p><c>ERL_DRV_STRING</c> constructs a string, and ends
+          it. (So it is the same as <c>ERL_DRV_NIL</c> followed by
           <c>ERL_DRV_STRING_CONS</c>.)</p>
         <code type="none"><![CDATA[
-    /* to send [x, "abc", y] to the port: */
-    ErlDrvTermData spec[] = {
-        ERL_DRV_ATOM, driver_mk_atom("x"),
-        ERL_DRV_STRING, (ErlDrvTermData)"abc", 3,
-        ERL_DRV_ATOM, driver_mk_atom("y"),
-        ERL_DRV_NIL,
-        ERL_DRV_LIST, 4
-    };
-    erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));
-        ]]></code>
-        <p></p>
+/* to send [x, "abc", y] to the port: */
+ErlDrvTermData spec[] = {
+    ERL_DRV_ATOM, driver_mk_atom("x"),
+    ERL_DRV_STRING, (ErlDrvTermData)"abc", 3,
+    ERL_DRV_ATOM, driver_mk_atom("y"),
+    ERL_DRV_NIL,
+    ERL_DRV_LIST, 4
+};
+erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));    ]]></code>
         <code type="none"><![CDATA[
-    /* to send "abc123" to the port: */
-    ErlDrvTermData spec[] = {
-        ERL_DRV_NIL,        /* with STRING_CONS, the tail comes first */
-        ERL_DRV_STRING_CONS, (ErlDrvTermData)"123", 3,
-        ERL_DRV_STRING_CONS, (ErlDrvTermData)"abc", 3,
-    };
-    erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));
-        ]]></code>
+/* to send "abc123" to the port: */
+ErlDrvTermData spec[] = {
+    ERL_DRV_NIL,        /* with STRING_CONS, the tail comes first */
+    ERL_DRV_STRING_CONS, (ErlDrvTermData)"123", 3,
+    ERL_DRV_STRING_CONS, (ErlDrvTermData)"abc", 3,
+};
+erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));    ]]></code>
 	<p>The <c>ERL_DRV_EXT2TERM</c> term type is used for passing a
-	term encoded with the
-	<seealso marker="erl_ext_dist">external format</seealso>,
-	i.e., a term that has been encoded by
-	<seealso marker="erlang#term_to_binary/2">erlang:term_to_binary</seealso>,
-	<seealso marker="erl_interface:ei">erl_interface</seealso>, etc.
-	For example, if <c>binp</c> is a pointer to an <c>ErlDrvBinary</c>
-	that contains the term <c>{17, 4711}</c> encoded with the
-	<seealso marker="erl_ext_dist">external format</seealso>
-	and you want to wrap it in a two tuple with the tag <c>my_tag</c>,
-	i.e., <c>{my_tag, {17, 4711}}</c>, you can do as follows:
-	</p>
-        <code type="none"><![CDATA[
-    ErlDrvTermData spec[] = {
-            ERL_DRV_ATOM, driver_mk_atom("my_tag"),
-            ERL_DRV_EXT2TERM, (ErlDrvTermData) binp->orig_bytes, binp->orig_size
-        ERL_DRV_TUPLE, 2,
-    };
-    erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));
-        ]]></code>
-
+	  term encoded with the
+	  <seealso marker="erl_ext_dist">external format</seealso>,
+	  that is, a term that has been encoded by
+	  <seealso marker="erlang#term_to_binary/2">
+	  <c>erlang:term_to_binary</c></seealso>,
+	  <seealso marker="erl_interface:ei"><c>erl_interface</c></seealso>,
+	  and so on.
+	  For example, if <c>binp</c> is a pointer to an <c>ErlDrvBinary</c>
+	  that contains term <c>{17, 4711}</c> encoded with the
+	  <seealso marker="erl_ext_dist">external format</seealso>,
+	  and you want to wrap it in a two-tuple with the tag <c>my_tag</c>,
+	  that is, <c>{my_tag, {17, 4711}}</c>, you can do as follows:</p>
+	<code type="none"><![CDATA[
+ErlDrvTermData spec[] = {
+        ERL_DRV_ATOM, driver_mk_atom("my_tag"),
+        ERL_DRV_EXT2TERM, (ErlDrvTermData) binp->orig_bytes, binp->orig_size
+    ERL_DRV_TUPLE, 2,
+};
+erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));    ]]></code>
         <p>To build the map <c>#{key1 => 100, key2 => {200, 300}}</c>, the
-          following call could be made.</p>
+          following call can be made.</p>
         <code type="none"><![CDATA[
-    ErlDrvPort port = ...
-    ErlDrvTermData spec[] = {
-          ERL_DRV_ATOM, driver_mk_atom("key1"),
-	  ERL_DRV_INT, 100,
-          ERL_DRV_ATOM, driver_mk_atom("key2"),
-	    ERL_DRV_INT, 200,
-	    ERL_DRV_INT, 300,
-	  ERL_DRV_TUPLE, 2,
-	ERL_DRV_MAP, 2
-    };
-    erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));
-        ]]>
-      </code>
-
-	<p>If you want to pass a binary and don't already have the content
-	of the binary in an <c>ErlDrvBinary</c>, you can benefit from using
-	<c>ERL_DRV_BUF2BINARY</c> instead of creating an <c>ErlDrvBinary</c>
-	via <c>driver_alloc_binary()</c> and then pass the binary via
-	<c>ERL_DRV_BINARY</c>. The runtime system will often allocate
-	binaries smarter if <c>ERL_DRV_BUF2BINARY</c> is used.
-	However, if the content of the binary to pass already resides in
-	an <c>ErlDrvBinary</c>, it is normally better to pass the binary
-	using <c>ERL_DRV_BINARY</c> and the <c>ErlDrvBinary</c> in question.
-	</p>
-	<p>The <c>ERL_DRV_UINT</c>, <c>ERL_DRV_BUF2BINARY</c>, and
-	<c>ERL_DRV_EXT2TERM</c> term types were introduced in the 5.6
-	version of erts.
-	</p>
+ErlDrvPort port = ...
+ErlDrvTermData spec[] = {
+    ERL_DRV_ATOM, driver_mk_atom("key1"),
+        ERL_DRV_INT, 100,
+    ERL_DRV_ATOM, driver_mk_atom("key2"),
+        ERL_DRV_INT, 200,
+        ERL_DRV_INT, 300,
+    ERL_DRV_TUPLE, 2,
+    ERL_DRV_MAP, 2
+};
+erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]));    ]]></code>
+        <p>If you want to pass a binary and do not already have the content
+          of the binary in an <c>ErlDrvBinary</c>, you can benefit from using
+          <c>ERL_DRV_BUF2BINARY</c> instead of creating an <c>ErlDrvBinary</c>
+          through <seealso marker="#driver_alloc_binary">
+          <c>driver_alloc_binary</c></seealso> and then pass the binary through
+          <c>ERL_DRV_BINARY</c>. The runtime system often allocates
+          binaries smarter if <c>ERL_DRV_BUF2BINARY</c> is used.
+          However, if the content of the binary to pass already resides in
+          an <c>ErlDrvBinary</c>, it is normally better to pass the binary using
+          <c>ERL_DRV_BINARY</c> and the <c>ErlDrvBinary</c> in question.</p>
+        <p>The <c>ERL_DRV_UINT</c>, <c>ERL_DRV_BUF2BINARY</c>, and
+          <c>ERL_DRV_EXT2TERM</c> term types were introduced in
+          <c>ERTS</c> 5.6.</p>
         <p>This function is only thread-safe when the emulator with SMP
           support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_putenv(const char *key, char *value)</nametext></name>
-      <fsummary>Set the value of an environment variable</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_putenv(const char *key, char
+        *value)</nametext></name>
+      <fsummary>Set the value of an environment variable.</fsummary>
       <desc>
         <marker id="erl_drv_putenv"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>key</c></tag>
-          <item>A null terminated string containing the
-	        name of the environment variable.</item>
-          <tag><c>value</c></tag>
-          <item>A null terminated string containing the
-	        new value of the environment variable.</item>
-        </taglist>
-        <p>This function sets the value of an environment variable.
-	   It returns <c>0</c> on success, and a value <c>!= 0</c> on
-	   failure.
-	</p>
-	<note><p>The result of passing the empty string ("") as a value
-	      is platform dependent. On some platforms the value of the
-	      variable is set to the empty string, on others, the
-	      environment variable is removed.</p>
-	</note>
-	<warning><p>Do <em>not</em> use libc's <c>putenv</c> or similar
-	         C library interfaces from a driver.
-	</p></warning>
+        <p>Sets the value of an environment variable.</p>
+        <p><c>key</c> is a <c>NULL</c>-terminated string containing the
+          name of the environment variable.</p>
+        <p><c>value</c> is a <c>NULL</c>-terminated string containing the
+          new value of the environment variable.</p>
+        <p>Returns <c>0</c> on success, otherwise a value <c>!= 0</c>.</p>
+        <note>
+          <p>The result of passing the empty string (<c>""</c>) as a value
+            is platform-dependent. On some platforms the variable value
+            is set to the empty string, on others the
+            environment variable is removed.</p>
+        </note>
+        <warning>
+          <p>Do <em>not</em> use libc's <c>putenv</c> or similar C library
+            interfaces from a driver.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvRWLock *</ret><nametext>erl_drv_rwlock_create(char *name)</nametext></name>
-      <fsummary>Create an rwlock</fsummary>
+      <name><ret>ErlDrvRWLock *</ret><nametext>erl_drv_rwlock_create(char
+        *name)</nametext></name>
+      <fsummary>Create an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_create"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>name</c></tag>
-          <item>A string identifying the created rwlock. It will be used to
-		identify the rwlock in planned future debug functionality.
-	  </item>
-        </taglist>
-        <p>This function creates an rwlock and returns a pointer to it. On
-	   failure <c>NULL</c> is returned. The driver creating the rwlock
-	   has the responsibility of destroying it before the driver is
-	   unloaded.
-	</p>
+        <p>Creates an rwlock and returns a pointer to it.</p>
+        <p><c>name</c> is a string identifying the created rwlock.
+          It is used to identify the rwlock in planned future
+          debug functionality.</p>
+        <p>Returns <c>NULL</c> on failure. The driver creating the rwlock
+          is responsible for destroying it before the driver is unloaded.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_rwlock_destroy(ErlDrvRWLock *rwlck)</nametext></name>
-      <fsummary>Destroy an rwlock</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_rwlock_destroy(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Destroy an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_destroy"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>rwlck</c></tag>
-          <item>A pointer to an rwlock to destroy.</item>
-        </taglist>
-        <p>This function destroys an rwlock previously created by
-	   <seealso marker="#erl_drv_rwlock_create">erl_drv_rwlock_create()</seealso>.
-	   The rwlock has to be in an unlocked state before being destroyed.
-	</p>
+        <p>Destroys an rwlock previously created by
+          <seealso marker="#erl_drv_rwlock_create">
+          <c>erl_drv_rwlock_create</c></seealso>.
+          The rwlock must be in an unlocked state before it is destroyed.</p>
+        <p><c>rwlck</c> is a pointer to an rwlock to destroy.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
-	<func>
-		<name><ret>char *</ret><nametext>erl_drv_rwlock_name(ErlDrvRWLock *rwlck)</nametext></name>
-		<fsummary>Get name of driver mutex.</fsummary>
-		<desc>
-			<marker id="erl_drv_rwlock_name"></marker>
-			<p>Arguments:</p>
-			<taglist>
-				<tag><c>rwlck</c></tag>
-				<item>A pointer to an initialized r/w-lock.</item>
-			</taglist>
-			<p>
-				Returns a pointer to the name of the r/w-lock.
-			</p>
-			<note>
-				<p>This function is intended for debugging purposes only.</p>
-			</note>
-		</desc>
-	</func>
+    <func>
+      <name><ret>char *</ret><nametext>erl_drv_rwlock_name(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Get name of driver mutex.</fsummary>
+      <desc>
+        <marker id="erl_drv_rwlock_name"></marker>
+        <p>Returns a pointer to the name of the rwlock.</p>
+        <p><c>rwlck</c> is a pointer to an initialized rwlock.</p>
+        <note>
+          <p>This function is intended for debugging purposes only.</p>
+        </note>
+      </desc>
+    </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_rwlock_rlock(ErlDrvRWLock *rwlck)</nametext></name>
-      <fsummary>Read lock an rwlock</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_rwlock_rlock(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Read lock an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_rlock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>rwlck</c></tag>
-          <item>A pointer to an rwlock to read lock.</item>
-        </taglist>
-        <p>This function read locks an rwlock. The calling thread will be
-	   blocked until the rwlock has been read locked. A thread
-	   which currently has read or read/write locked the rwlock may
-	   <em>not</em> lock the same rwlock again.
-	</p>
-	<warning><p>If you leave an rwlock locked in an emulator thread
-	            when you let the thread out of your control, you will
-		    <em>very likely</em> deadlock the whole emulator.
-	</p></warning>
+        <p>Read locks an rwlock. The calling thread is
+          blocked until the rwlock has been read locked. A thread
+          that currently has read or read/write locked the rwlock
+          <em>cannot</em> lock the same rwlock again.</p>
+        <p><c>rwlck</c> is a pointer to the rwlock to read lock.</p>
+        <warning>
+          <p>If you leave an rwlock locked in an emulator thread
+            when you let the thread out of your control, you will
+            <em>very likely</em> deadlock the whole emulator.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_rwlock_runlock(ErlDrvRWLock *rwlck)</nametext></name>
-      <fsummary>Read unlock an rwlock</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_rwlock_runlock(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Read unlock an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_runlock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>rwlck</c></tag>
-          <item>A pointer to an rwlock to read unlock.</item>
-        </taglist>
-        <p>This function read unlocks an rwlock. The rwlock currently
-	   has to be read locked by the calling thread.
-	</p>
+        <p>Read unlocks an rwlock. The rwlock currently must
+          be read locked by the calling thread.</p>
+        <p><c>rwlck</c> is a pointer to an rwlock to read unlock.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_rwlock_rwlock(ErlDrvRWLock *rwlck)</nametext></name>
-      <fsummary>Read/Write lock an rwlock</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_rwlock_rwlock(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Read/write lock an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_rwlock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>rwlck</c></tag>
-          <item>A pointer to an rwlock to read/write lock.</item>
-        </taglist>
-        <p>This function read/write locks an rwlock. The calling thread
-	   will be blocked until the rwlock has been read/write locked.
-	   A thread which currently has read or read/write locked the
-	   rwlock may <em>not</em> lock the same rwlock again.
-	</p>
-	<warning><p>If you leave an rwlock locked in an emulator thread
-	            when you let the thread out of your control, you will
-		    <em>very likely</em> deadlock the whole emulator.
-	</p></warning>
+        <p>Read/write locks an rwlock. The calling thread
+          is blocked until the rwlock has been read/write locked.
+          A thread that currently has read or read/write locked the
+          rwlock <em>cannot</em> lock the same rwlock again.</p>
+        <p><c>rwlck</c> is a pointer to an rwlock to read/write lock.</p>
+        <warning>
+          <p>If you leave an rwlock locked in an emulator thread
+            when you let the thread out of your control, you will
+            <em>very likely</em> deadlock the whole emulator.</p>
+          </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_rwlock_rwunlock(ErlDrvRWLock *rwlck)</nametext></name>
-      <fsummary>Read/Write unlock an rwlock</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_rwlock_rwunlock(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Read/write unlock an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_rwunlock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>rwlck</c></tag>
-          <item>A pointer to an rwlock to read/write unlock.</item>
-        </taglist>
-        <p>This function read/write unlocks an rwlock. The rwlock
-	   currently has to be read/write locked by the calling thread.
-	</p>
+        <p>Read/write unlocks an rwlock. The rwlock currently must be
+          read/write locked by the calling thread.</p>
+        <p><c>rwlck</c> is a pointer to an rwlock to read/write unlock.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_rwlock_tryrlock(ErlDrvRWLock *rwlck)</nametext></name>
-      <fsummary>Try to read lock an rwlock</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_rwlock_tryrlock(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Try to read lock an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_tryrlock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>rwlck</c></tag>
-          <item>A pointer to an rwlock to try to read lock.</item>
-        </taglist>
-        <p>This function tries to read lock an rwlock. If successful
-	   <c>0</c>, is returned; otherwise, <c>EBUSY</c> is returned.
-	   A thread which currently has read or read/write locked the
-	   rwlock may <em>not</em> try to lock the same rwlock again.
-	</p>
-	<warning><p>If you leave an rwlock locked in an emulator thread
-	            when you let the thread out of your control, you will
-		    <em>very likely</em> deadlock the whole emulator.
-	</p></warning>
+        <p>Tries to read lock an rwlock.</p>
+        <p><c>rwlck</c> is a pointer to an rwlock to try to read lock.</p>
+        <p>Returns <c>0</c> on success, otherwise <c>EBUSY</c>.
+          A thread that currently has read or read/write locked the
+          rwlock <em>cannot</em> try to lock the same rwlock again.</p>
+        <warning>
+          <p>If you leave an rwlock locked in an emulator thread
+            when you let the thread out of your control, you will
+            <em>very likely</em> deadlock the whole emulator.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_rwlock_tryrwlock(ErlDrvRWLock *rwlck)</nametext></name>
-      <fsummary>Try to read/write lock an rwlock</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_rwlock_tryrwlock(ErlDrvRWLock
+        *rwlck)</nametext></name>
+      <fsummary>Try to read/write lock an rwlock.</fsummary>
       <desc>
         <marker id="erl_drv_rwlock_tryrwlock"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>rwlck</c></tag>
-          <item>A pointer to an rwlock to try to read/write lock.</item>
-        </taglist>
-        <p>This function tries to read/write lock an rwlock. If successful
-	   <c>0</c>, is returned; otherwise, <c>EBUSY</c> is returned.
-	   A thread which currently has read or read/write locked the
-	   rwlock may <em>not</em> try to lock the same rwlock again.
-	</p>
-	<warning><p>If you leave an rwlock locked in an emulator thread
-	            when you let the thread out of your control, you will
-		    <em>very likely</em> deadlock the whole emulator.
-	</p></warning>
+        <p>Tries to read/write lock an rwlock.
+          A thread that currently has read or read/write locked the
+          rwlock <em>cannot</em> try to lock the same rwlock again.</p>
+        <p><c>rwlck</c>is pointer to an rwlock to try to read/write lock.</p>
+        <p>Returns <c>0</c> om success, otherwise <c>EBUSY</c>.</p>
+        <warning>
+          <p>If you leave an rwlock locked in an emulator thread
+            when you let the thread out of your control, you will
+            <em>very likely</em> deadlock the whole emulator.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_send_term(ErlDrvTermData port, ErlDrvTermData receiver, ErlDrvTermData* term, int n)</nametext></name>
-      <fsummary>Send term data to other process than port owner process</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_send_term(ErlDrvTermData port,
+        ErlDrvTermData receiver, ErlDrvTermData* term, int n)</nametext></name>
+      <fsummary>Send term data to other process than port owner process.
+      </fsummary>
       <desc>
         <marker id="erl_drv_send_term"></marker>
         <p>This function is the only way for a driver to send data to
-          <em>other</em> processes than the port owner process. The
-          <c>receiver</c> parameter specifies the process to receive
-          the data.</p>
-	<note><p>Note that the <c>port</c> parameter is <em>not</em>
-	  an ordinary port handle, but a port handle converted using
-	  <c>driver_mk_port()</c>.</p></note>
-        <p>The parameters <c>port</c>, <c>term</c> and <c>n</c> do the same thing
-          as in <seealso marker="#erl_drv_output_term">erl_drv_output_term()</seealso>.</p>
+          <em>other</em> processes than the port owner process. Parameter
+          <c>receiver</c> specifies the process to receive the data.</p>
+        <note>
+          <p>Parameter <c>port</c> is <em>not</em> an ordinary port handle, but
+            a port handle converted using
+            <seealso marker="#driver_mk_port">
+            <c>driver_mk_port</c></seealso>.</p>
+        </note>
+        <p>Parameters <c>port</c>, <c>term</c>, and <c>n</c> work as in
+          <seealso marker="#erl_drv_output_term">
+          <c>erl_drv_output_term</c></seealso>.</p>
         <p>This function is only thread-safe when the emulator with SMP
           support is used.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_set_os_pid(ErlDrvPort port, ErlDrvSInt pid)</nametext></name>
-      <fsummary>Set the os_pid for the port</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_set_os_pid(ErlDrvPort port,
+        ErlDrvSInt pid)</nametext></name>
+      <fsummary>Set the os_pid for the port.</fsummary>
       <desc>
         <marker id="erl_drv_set_os_pid"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>port</c></tag>
-          <item>The port handle of the port (driver instance) to set the pid on.
-	  </item>
-          <tag><c>pid</c></tag>
-          <item>The pid to set.</item>
-        </taglist>
-        <p>
-          Set the os_pid seen when doing erlang:port_info/2 on this port.
-        </p>
+        <p>Sets the <c>os_pid</c> seen when doing
+          <seealso marker="erlang:port_info/2">
+          <c>erlang:port_info/2</c></seealso> on this port.</p>
+        <p><c>port</c> is the port handle of the port (driver instance) to set
+          the pid on. <c>pid</c>is the pid to set.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_thread_create(char *name,
-				      ErlDrvTid *tid,
-				      void * (*func)(void *),
-				      void *arg,
-				      ErlDrvThreadOpts *opts)</nametext></name>
-      <fsummary>Create a thread</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_thread_create(char *name, ErlDrvTid
+        *tid, void * (*func)(void *), void *arg, ErlDrvThreadOpts
+        *opts)</nametext></name>
+      <fsummary>Create a thread.</fsummary>
       <desc>
         <marker id="erl_drv_thread_create"></marker>
-        <p>Arguments:</p>
+        <p>Creates a new thread.</p>
         <taglist>
           <tag><c>name</c></tag>
-          <item>A string identifying the created thread. It will be used
-	        to identify the thread in planned future debug
-		functionality.
-	  </item>
+          <item>A string identifying the created thread. It is used to
+            identify the thread in planned future debug functionality.
+          </item>
           <tag><c>tid</c></tag>
           <item>A pointer to a thread identifier variable.</item>
           <tag><c>func</c></tag>
@@ -2848,377 +2873,348 @@ ERL_DRV_MAP          int sz
           <tag><c>opts</c></tag>
           <item>A pointer to thread options to use or <c>NULL</c>.</item>
         </taglist>
-        <p>This function creates a new thread. On success <c>0</c> is returned;
-	   otherwise, an <c>errno</c> value is returned to indicate the error.
-	   The newly created thread will begin executing in the function pointed
-	   to by <c>func</c>, and <c>func</c> will be passed <c>arg</c> as
-	   argument. When <c>erl_drv_thread_create()</c> returns the thread
-	   identifier of the newly created thread will be available in
-	   <c>*tid</c>. <c>opts</c> can be either a <c>NULL</c> pointer, or a
-	   pointer to an
-	   <seealso marker="#ErlDrvThreadOpts">ErlDrvThreadOpts</seealso>
-	   structure. If <c>opts</c> is a <c>NULL</c> pointer, default options
-	   will be used; otherwise, the passed options will be used.
-	</p>
-	<warning><p>You are not allowed to allocate the
-	            <seealso marker="#ErlDrvThreadOpts">ErlDrvThreadOpts</seealso>
-	            structure by yourself. It has to be allocated and
-		    initialized by
-		    <seealso marker="#erl_drv_thread_opts_create">erl_drv_thread_opts_create()</seealso>.
-	</p></warning>
-	<p>The created thread will terminate either when <c>func</c> returns
-	   or if
-	   <seealso marker="#erl_drv_thread_exit">erl_drv_thread_exit()</seealso>
-	   is called by the thread. The exit value of the thread is either
-	   returned from <c>func</c> or passed as argument to
-	   <seealso marker="#erl_drv_thread_exit">erl_drv_thread_exit()</seealso>.
-	   The driver creating the thread has the responsibility of joining the
-	   thread, via
-	   <seealso marker="#erl_drv_thread_join">erl_drv_thread_join()</seealso>,
-	   before the driver is unloaded. It is not possible to create
-	   "detached" threads, i.e., threads that don't need to be joined.
-	</p>
-	<warning><p>All created threads need to be joined by the driver before
-	            it is unloaded.  If the driver fails to join all threads
-		    created before it is unloaded, the runtime system will
-		    most likely crash when the code of the driver is unloaded.
-	</p></warning>
+        <p>Returns <c>0</c> on success,
+          otherwise an <c>errno</c> value is returned to indicate the error.
+          The newly created thread begins executing in the function pointed
+          to by <c>func</c>, and <c>func</c> is passed <c>arg</c> as
+          argument. When <c>erl_drv_thread_create</c> returns, the thread
+          identifier of the newly created thread is available in
+          <c>*tid</c>. <c>opts</c> can be either a <c>NULL</c> pointer, or a
+          pointer to an
+          <seealso marker="#ErlDrvThreadOpts"><c>ErlDrvThreadOpts</c></seealso>
+          structure. If <c>opts</c> is a <c>NULL</c> pointer, default options
+          are used, otherwise the passed options are used.</p>
+        <warning>
+          <p>You are not allowed to allocate the
+            <seealso marker="#ErlDrvThreadOpts">
+            <c>ErlDrvThreadOpts</c></seealso> structure by yourself.
+            It must be allocated and initialized by
+            <seealso marker="#erl_drv_thread_opts_create">
+            <c>erl_drv_thread_opts_create</c></seealso>.</p>
+        </warning>
+        <p>The created thread terminates either when <c>func</c> returns or if
+          <seealso marker="#erl_drv_thread_exit">
+          <c>erl_drv_thread_exit</c></seealso>
+          is called by the thread. The exit value of the thread is either
+          returned from <c>func</c> or passed as argument to
+          <seealso marker="#erl_drv_thread_exit">
+          <c>erl_drv_thread_exit</c></seealso>.
+          The driver creating the thread is responsible for joining the
+          thread, through <seealso marker="#erl_drv_thread_join">
+          <c>erl_drv_thread_join</c></seealso>,
+          before the driver is unloaded. "Detached" threads cannot be created,
+          that is, threads that do not need to be joined.</p>
+        <warning>
+          <p>All created threads must be joined by the driver before
+            it is unloaded. If the driver fails to join all threads
+            created before it is unloaded, the runtime system
+            most likely crashes when the driver code is unloaded.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_thread_exit(void *exit_value)</nametext></name>
-      <fsummary>Terminate calling thread</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_thread_exit(void
+        *exit_value)</nametext></name>
+      <fsummary>Terminate calling thread.</fsummary>
       <desc>
         <marker id="erl_drv_thread_exit"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>exit_value</c></tag>
-          <item>A pointer to an exit value or <c>NULL</c>.</item>
-        </taglist>
-        <p>This function terminates the calling thread with the exit
-	   value passed as argument. You are only allowed to terminate
-	   threads created with
-	   <seealso marker="#erl_drv_thread_create">erl_drv_thread_create()</seealso>.
-	   The exit value can later be retrieved by another thread via
-	   <seealso marker="#erl_drv_thread_join">erl_drv_thread_join()</seealso>.
-	</p>
+        <p>Terminates the calling thread with the exit value passed as
+          argument. <c>exit_value</c> is a pointer to an exit value or
+          <c>NULL</c>.</p>
+        <p>You are only allowed to terminate threads created with
+          <seealso marker="#erl_drv_thread_create">
+          <c>erl_drv_thread_create</c></seealso>.</p>
+        <p>The exit value can later be retrieved by another thread through
+          <seealso marker="#erl_drv_thread_join">
+          <c>erl_drv_thread_join</c></seealso>.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_thread_join(ErlDrvTid tid, void **exit_value)</nametext></name>
-      <fsummary>Join with another thread</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_thread_join(ErlDrvTid tid, void
+        **exit_value)</nametext></name>
+      <fsummary>Join with another thread.</fsummary>
       <desc>
         <marker id="erl_drv_thread_join"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>tid</c></tag>
-          <item>The thread identifier of the thread to join.</item>
-          <tag><c>exit_value</c></tag>
-          <item>A pointer to a pointer to an exit value, or <c>NULL</c>.</item>
-        </taglist>
-        <p>This function joins the calling thread with another thread, i.e.,
-	   the calling thread is blocked until the thread identified by
-	   <c>tid</c> has terminated. On success <c>0</c> is returned;
-	   otherwise, an <c>errno</c> value is returned to indicate the error.
-	   A thread can only be joined once. The behavior of joining
-	   more than once is undefined, an emulator crash is likely. If
-	   <c>exit_value == NULL</c>, the exit value of the terminated thread
-	   will be ignored; otherwise, the exit value of the terminated thread
-	   will be stored at <c>*exit_value</c>.
-	</p>
+        <p>Joins the calling thread with another thread, that is,
+          the calling thread is blocked until the thread identified by
+          <c>tid</c> has terminated.</p>
+        <p><c>tid</c> is the thread identifier of the thread to join.
+          <c>exit_value</c> is a pointer to a pointer to an exit value,
+          or <c>NULL</c>.</p>
+        <p>Returns <c>0</c> on success, otherwise an <c>errno</c>
+          value is returned to indicate the error.</p>
+        <p>A thread can only be joined once. The behavior of joining
+          more than once is undefined, an emulator crash is likely. If
+          <c>exit_value == NULL</c>, the exit value of the terminated thread
+          is ignored, otherwise the exit value of the terminated thread
+          is stored at <c>*exit_value</c>.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
-	<func>
-		<name><ret>char *</ret><nametext>erl_drv_thread_name(ErlDrvTid tid)</nametext></name>
-		<fsummary>Get name of driver mutex.</fsummary>
-		<desc>
-			<marker id="erl_drv_rwlock_name"></marker>
-			<p>Arguments:</p>
-			<taglist>
-				<tag><c>tid</c></tag>
-				<item>A thread identifier.</item>
-			</taglist>
-			<p>
-				Returns a pointer to the name of the thread.
-			</p>
-			<note>
-				<p>This function is intended for debugging purposes only.</p>
-			</note>
-		</desc>
-	</func>
+    <func>
+      <name><ret>char *</ret><nametext>erl_drv_thread_name(ErlDrvTid
+        tid)</nametext></name>
+      <fsummary>Get name of driver mutex.</fsummary>
+      <desc>
+        <marker id="erl_drv_rwlock_name"></marker>
+        <p>Returns a pointer to the name of the thread.</p>
+        <p><c>tid</c> is a thread identifier.</p>
+        <note>
+          <p>This function is intended for debugging purposes only.</p>
+        </note>
+      </desc>
+    </func>
 
     <func>
-      <name><ret>ErlDrvThreadOpts *</ret><nametext>erl_drv_thread_opts_create(char *name)</nametext></name>
-      <fsummary>Create thread options</fsummary>
+      <name><ret>ErlDrvThreadOpts *</ret>
+        <nametext>erl_drv_thread_opts_create(char *name)</nametext></name>
+      <fsummary>Create thread options.</fsummary>
       <desc>
         <marker id="erl_drv_thread_opts_create"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>name</c></tag>
-          <item>A string identifying the created thread options. It will be used
-	        to identify the thread options in planned future debug
-		functionality.
-	  </item>
-        </taglist>
-        <p>This function allocates and initialize a thread option
-	   structure. On failure <c>NULL</c> is returned. A thread option
-	   structure is used for passing options to
-	   <seealso marker="#erl_drv_thread_create">erl_drv_thread_create()</seealso>.
-	   If the structure isn't modified before it is passed to
-	   <seealso marker="#erl_drv_thread_create">erl_drv_thread_create()</seealso>,
-	   the default values will be used.
-	</p>
-	<warning><p>You are not allowed to allocate the
-	            <seealso marker="#ErlDrvThreadOpts">ErlDrvThreadOpts</seealso>
-	            structure by yourself. It has to be allocated and
-		    initialized by <c>erl_drv_thread_opts_create()</c>.
-	</p></warning>
+        <p>Allocates and initializes a thread option structure.</p>
+        <p><c>name</c> is a string identifying the created thread options.
+          It is used to identify the thread options in planned future debug
+          functionality.</p>
+        <p>Returns <c>NULL</c> on failure. A thread option
+          structure is used for passing options to
+          <seealso marker="#erl_drv_thread_create">
+          <c>erl_drv_thread_create</c></seealso>.
+          If the structure is not modified before it is passed to
+          <seealso marker="#erl_drv_thread_create">
+          <c>erl_drv_thread_create</c></seealso>,
+          the default values are used.</p>
+        <warning>
+          <p>You are not allowed to allocate the
+            <seealso marker="#ErlDrvThreadOpts">
+            <c>ErlDrvThreadOpts</c></seealso>
+            structure by yourself. It must be allocated and initialized by
+            <c>erl_drv_thread_opts_create</c>.</p>
+          </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_thread_opts_destroy(ErlDrvThreadOpts *opts)</nametext></name>
-      <fsummary>Destroy thread options</fsummary>
+      <name><ret>void</ret>
+        <nametext>erl_drv_thread_opts_destroy(ErlDrvThreadOpts *opts)</nametext>
+      </name>
+      <fsummary>Destroy thread options.</fsummary>
       <desc>
         <marker id="erl_drv_thread_opts_destroy"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>opts</c></tag>
-          <item>A pointer to thread options to destroy.</item>
-        </taglist>
-        <p>This function destroys thread options previously created by
-	   <seealso marker="#erl_drv_thread_opts_create">erl_drv_thread_opts_create()</seealso>.
-	</p>
+        <p>Destroys thread options previously created by
+          <seealso marker="#erl_drv_thread_opts_create">
+          <c>erl_drv_thread_opts_create</c></seealso>.</p>
+        <p><c>opts</c> is a pointer to thread options to destroy.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlDrvTid</ret><nametext>erl_drv_thread_self(void)</nametext></name>
-      <fsummary>Get the thread identifier of the current thread</fsummary>
+      <name><ret>ErlDrvTid</ret>
+        <nametext>erl_drv_thread_self(void)</nametext></name>
+      <fsummary>Get the thread identifier of the current thread.</fsummary>
       <desc>
         <marker id="erl_drv_thread_self"></marker>
-        <p>This function returns the thread identifier of the
-	   calling thread.
-	</p>
+        <p>Returns the thread identifier of the calling thread.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
-	<func>
-	  <name><ret>ErlDrvTime</ret><nametext>erl_drv_time_offset(ErlDrvTimeUnit time_unit)</nametext></name>
-	  <fsummary>Get current Time Offset</fsummary>
-	  <desc>
-	    <marker id="erl_drv_time_offset"></marker>
-	    <p>Arguments:</p>
-	    <taglist>
-	      <tag><c>time_unit</c></tag>
-	      <item>Time unit of returned value.</item>
-	    </taglist>
-	    <p>Returns the current time offset between
-	    <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang monotonic time</seealso>
-	    and
-	    <seealso marker="time_correction#Erlang_System_Time">Erlang system time</seealso>
-	    converted into the <c>time_unit</c> passed as argument.</p>
-	    <p>Returns <c>ERL_DRV_TIME_ERROR</c> if called with an invalid
-	    time unit argument, or if called from a thread that is not a
-	    scheduler thread.</p>
-	    <p>See also:</p>
-	    <list>
-	      <item><seealso marker="#ErlDrvTime"><c>ErlDrvTime</c></seealso></item>
-	      <item><seealso marker="#ErlDrvTimeUnit"><c>ErlDrvTimeUnit</c></seealso></item>
-	    </list>
-	  </desc>
-	</func>
-
-    <func>
-      <name><ret>void *</ret><nametext>erl_drv_tsd_get(ErlDrvTSDKey key)</nametext></name>
-      <fsummary>Get thread specific data</fsummary>
+    <func>
+      <name><ret>ErlDrvTime</ret><nametext>erl_drv_time_offset(ErlDrvTimeUnit
+        time_unit)</nametext></name>
+      <fsummary>Get current time offset.</fsummary>
+      <desc>
+        <marker id="erl_drv_time_offset"></marker>
+        <p>Returns the current time offset between
+          <seealso marker="time_correction#Erlang_Monotonic_Time">
+          Erlang monotonic time</seealso> and
+          <seealso marker="time_correction#Erlang_System_Time">
+          Erlang system time</seealso>
+          converted into the <c>time_unit</c> passed as argument.</p>
+        <p><c>time_unit</c> is time unit of returned value.</p>
+        <p>Returns <c>ERL_DRV_TIME_ERROR</c> if called with an invalid
+          time unit argument, or if called from a thread that is not a
+          scheduler thread.</p>
+        <p>See also <seealso marker="#ErlDrvTime">
+          <c>ErlDrvTime</c></seealso> and
+          <seealso marker="#ErlDrvTimeUnit">
+          <c>ErlDrvTimeUnit</c></seealso>.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>void *</ret><nametext>erl_drv_tsd_get(ErlDrvTSDKey
+        key)</nametext></name>
+      <fsummary>Get thread-specific data.</fsummary>
       <desc>
         <marker id="erl_drv_tsd_get"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>key</c></tag>
-          <item>A thread specific data key.</item>
-        </taglist>
-        <p>This function returns the thread specific data
-	   associated with <c>key</c> for the calling thread.
-	   If no data has been associated with <c>key</c> for
-	   the calling thread, <c>NULL</c> is returned.
-	</p>
+        <p>Returns the thread-specific data
+          associated with <c>key</c> for the calling thread.</p>
+        <p><c>key</c> is a thread-specific data key.</p>
+        <p>Returns <c>NULL</c> if no data has been associated
+          with <c>key</c> for the calling thread.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>erl_drv_tsd_key_create(char *name, ErlDrvTSDKey *key)</nametext></name>
-      <fsummary>Create a thread specific data key</fsummary>
+      <name><ret>int</ret><nametext>erl_drv_tsd_key_create(char *name,
+        ErlDrvTSDKey *key)</nametext></name>
+      <fsummary>Create a thread-specific data key.</fsummary>
       <desc>
         <marker id="erl_drv_tsd_key_create"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>name</c></tag>
-          <item>A string identifying the created key. It will be used
-	        to identify the key in planned future debug
-		functionality.
-	  </item>
-          <tag><c>key</c></tag>
-          <item>A pointer to a thread specific data key variable.</item>
-        </taglist>
-        <p>This function creates a thread specific data key. On success
-	   <c>0</c> is returned; otherwise, an <c>errno</c> value is returned
-	   to indicate the error. The driver creating the key has the
-	   responsibility of destroying it before the driver is unloaded.
-	</p>
+        <p>Creates a thread-specific data key.</p>
+        <p><c>name</c> is a string identifying the created key. It is used
+          to identify the key in planned future debug functionality.</p>
+        <p><c>key</c> is a pointer to a thread-specific data key variable.</p>
+        <p>Returns <c>0</c> on success, otherwise an <c>errno</c> value is
+          returned to indicate the error. The driver creating the key is
+          responsible for destroying it before the driver is unloaded.</p>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_tsd_key_destroy(ErlDrvTSDKey key)</nametext></name>
-      <fsummary>Destroy a thread specific data key</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_tsd_key_destroy(ErlDrvTSDKey
+        key)</nametext></name>
+      <fsummary>Destroy a thread-specific data key.</fsummary>
       <desc>
         <marker id="erl_drv_tsd_key_destroy"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>key</c></tag>
-          <item>A thread specific data key to destroy.</item>
-        </taglist>
-        <p>This function destroys a thread specific data key
-	   previously created by
-	   <seealso marker="#erl_drv_tsd_key_create">erl_drv_tsd_key_create()</seealso>.
-	   All thread specific data using this key in all threads
-	   have to be cleared (see
-	   <seealso marker="#erl_drv_tsd_set">erl_drv_tsd_set()</seealso>)
-	   prior to the call to <c>erl_drv_tsd_key_destroy()</c>.
-	</p>
-	<warning><p>A destroyed key is very likely to be reused soon.
-		    Therefore, if you fail to clear the thread specific
-		    data using this key in a thread prior to destroying
-		    the key, you will <em>very likely</em> get unexpected
-		    errors in other parts of the system.
-	</p></warning>
+        <p>Destroys a thread-specific data key previously created by
+          <seealso marker="#erl_drv_tsd_key_create">
+          <c>erl_drv_tsd_key_create</c></seealso>.
+          All thread-specific data using this key in all threads
+          must be cleared (see <seealso marker="#erl_drv_tsd_set">
+          <c>erl_drv_tsd_set</c></seealso>)
+	  before the call to <c>erl_drv_tsd_key_destroy</c>.</p>
+        <p><c>key</c> is a thread-specific data key to destroy.</p>
+        <warning>
+          <p>A destroyed key is very likely to be reused soon.
+            Therefore, if you fail to clear the thread-specific
+            data using this key in a thread before destroying
+            the key, you will <em>very likely</em> get unexpected
+            errors in other parts of the system.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>erl_drv_tsd_set(ErlDrvTSDKey key, void *data)</nametext></name>
-      <fsummary>Set thread specific data</fsummary>
+      <name><ret>void</ret><nametext>erl_drv_tsd_set(ErlDrvTSDKey key, void
+        *data)</nametext></name>
+      <fsummary>Set thread-specific data.</fsummary>
       <desc>
         <marker id="erl_drv_tsd_set"></marker>
-        <p>Arguments:</p>
-        <taglist>
-          <tag><c>key</c></tag>
-          <item>A thread specific data key.</item>
-          <tag><c>data</c></tag>
-          <item>A pointer to data to associate with <c>key</c>
-	        in calling thread.
-	  </item>
-        </taglist>
-        <p>This function sets thread specific data associated with
-	   <c>key</c> for the calling thread. You are only allowed to set
-	   thread specific data for threads while they are fully under your
-	   control. For example, if you set thread specific data in a thread
-	   calling a driver call-back function, it has to be cleared, i.e.
-	   set to <c>NULL</c>, before returning from the driver call-back
-	   function.
-	</p>
-	<warning><p>If you fail to clear thread specific data in an
-	            emulator thread before letting it out of your control,
-		    you might not ever be able to clear this data with
-		    later unexpected errors in other parts of the system as
-		    a result.
-	</p></warning>
+        <p>Sets thread-specific data associated with
+          <c>key</c> for the calling thread. You are only allowed to set
+          thread-specific data for threads while they are fully under your
+          control. For example, if you set thread-specific data in a thread
+          calling a driver callback function, it must be cleared, that is,
+          set to <c>NULL</c>, before returning from the driver callback
+          function.</p>
+        <p><c>key</c> is a thread-specific data key.</p>
+        <p><c>data</c> is a pointer to data to associate with <c>key</c>
+          in the calling thread.</p>
+        <warning>
+          <p>If you fail to clear thread-specific data in an
+            emulator thread before letting it out of your control,
+            you might never be able to clear this data with
+            later unexpected errors in other parts of the system as
+            a result.</p>
+        </warning>
         <p>This function is thread-safe.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>char *</ret><nametext>erl_errno_id(int error)</nametext></name>
-      <fsummary>Get erlang error atom name from error number</fsummary>
+      <fsummary>Get Erlang error atom name from error number.</fsummary>
       <desc>
         <marker id="erl_errno_id"></marker>
-        <p>This function returns the atom name of the erlang error,
-          given the error number in <c>error</c>. Error atoms are:
-          <c>einval</c>, <c>enoent</c>, etc. It can be used to make
+        <p>Returns the atom name of the Erlang error,
+          given the error number in <c>error</c>. The error atoms are
+          <c>einval</c>, <c>enoent</c>, and so on. It can be used to make
           error terms from the driver.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>remove_driver_entry(ErlDrvEntry *de)</nametext></name>
-      <fsummary>Remove a driver entry</fsummary>
+      <name><ret>int</ret><nametext>remove_driver_entry(ErlDrvEntry
+        *de)</nametext></name>
+      <fsummary>Remove a driver entry.</fsummary>
       <desc>
         <marker id="remove_driver_entry"></marker>
-        <p>This function removes a driver entry <c>de</c> previously
-          added with <c>add_driver_entry</c>.</p>
-        <p>Driver entries added by the <c>erl_ddll</c> erlang interface can
-          not be removed by using this interface.</p>
+        <p>Removes a driver entry <c>de</c> previously added with
+          <seealso marker="#add_driver_entry">
+          <c>add_driver_entry</c></seealso>.</p>
+        <p>Driver entries added by the <c>erl_ddll</c> Erlang interface
+          cannot be removed by using this interface.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>set_busy_port(ErlDrvPort port, int on)</nametext></name>
-      <fsummary>Signal or unsignal port as busy</fsummary>
+      <name><ret>void</ret><nametext>set_busy_port(ErlDrvPort port, int
+        on)</nametext></name>
+      <fsummary>Signal or unsignal port as busy.</fsummary>
       <desc>
         <marker id="set_busy_port"></marker>
-        <p>This function set and unset the busy state of the port. If
-          <c>on</c> is non-zero, the port is set to busy, if it's zero the port
-          is set to not busy. You typically want to combine
-	  this feature with the <seealso marker="#erl_drv_busy_msgq_limits">busy
-	  port message queue</seealso> functionality.</p>
-	<p>Processes sending command data to the port will be suspended
-	if either the port is busy or if the port message queue
-	is busy. Suspended processes will be resumed when neither the
-	port is busy, nor the port message queue is busy. Command data
-	is in this context data passed to the port using either
-	<c>Port ! {Owner, {command, Data}}</c>, or
-	<c>port_command/[2,3]</c>.</p>
-	<p>If the
-	   <seealso marker="driver_entry#driver_flags"><![CDATA[ERL_DRV_FLAG_SOFT_BUSY]]></seealso>
-	   has been set in the
-	   <seealso marker="driver_entry">driver_entry</seealso>,
-	   data can be forced into the driver via
-	   <seealso marker="erlang#port_command/3">port_command(Port, Data, [force])</seealso>
-	   even though the driver has signaled that it is busy.
-	</p>
-	<p>For information about busy port message queue functionality
-	see the documentation of the
-	<seealso marker="#erl_drv_busy_msgq_limits">erl_drv_busy_msgq_limits()</seealso>
-	function.</p>
-      </desc>
-    </func>
-
-    <func>
-      <name><ret>void</ret><nametext>set_port_control_flags(ErlDrvPort port, int flags)</nametext></name>
-      <fsummary>Set flags on how to handle control entry function</fsummary>
+        <p>Sets and unsets the busy state of the port. If
+          <c>on</c> is non-zero, the port is set to busy. If it is zero,
+          the port is set to not busy. You typically want to combine
+          this feature with the <seealso marker="#erl_drv_busy_msgq_limits">
+          busy port message queue</seealso> functionality.</p>
+        <p>Processes sending command data to the port are suspended
+          if either the port or the port message queue
+          is busy. Suspended processes are resumed when neither the
+          port or the port message queue is busy. Command data
+          is in this context data passed to the port using either
+          <c>Port ! {Owner, {command, Data}}</c> or
+          <c>port_command/[2,3]</c>.</p>
+        <p>If the <seealso marker="driver_entry#driver_flags">
+          <![CDATA[ERL_DRV_FLAG_SOFT_BUSY]]></seealso> has been set in the
+          <seealso marker="driver_entry"><c>driver_entry</c></seealso>,
+          data can be forced into the driver through
+          <seealso marker="erlang#port_command/3">
+          <c>erlang:port_command(Port, Data, [force])</c></seealso>
+          even if the driver has signaled that it is busy.</p>
+        <p>For information about busy port message queue functionality, see
+          <seealso marker="#erl_drv_busy_msgq_limits">
+          <c>erl_drv_busy_msgq_limits</c></seealso>.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name><ret>void</ret><nametext>set_port_control_flags(ErlDrvPort port,
+        int flags)</nametext></name>
+      <fsummary>Set flags on how to handle control entry function.</fsummary>
       <desc>
         <marker id="set_port_control_flags"></marker>
-        <p>This function sets flags for how the <seealso marker="driver_entry#control">control</seealso> driver entry
-          function will return data to the port owner process. (The
-          <c>control</c> function is called from <c>port_control/3</c>
-          in erlang.)</p>
+        <p>Sets flags for how the <seealso marker="driver_entry#control">
+          <c>control</c></seealso> driver entry
+          function will return data to the port owner process.
+          (The <c>control</c> function is called from
+          <seealso marker="erlang:port_control/3">
+          <c>erlang:port_control/3</c></seealso>.)</p>
         <p>Currently there are only two meaningful values for
-          <c>flags</c>: 0 means that data is returned in a list, and
-          <c>PORT_CONTROL_FLAG_BINARY</c> means data is returned as
+          <c>flags</c>: <c>0</c> means that data is returned in a list,
+          and <c>PORT_CONTROL_FLAG_BINARY</c> means data is returned as
           a binary from <c>control</c>.</p>
       </desc>
     </func>
   </funcs>
+
   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="driver_entry">driver_entry(3)</seealso>,
-      <seealso marker="kernel:erl_ddll">erl_ddll(3)</seealso>,
-      <seealso marker="erlang">erlang(3)</seealso></p>
-    <p>An Alternative Distribution Driver (ERTS User's
-      Guide Ch. 3)</p>
+    <title>See Also</title>
+    <p><seealso marker="driver_entry"><c>driver_entry(3)</c></seealso>,
+      <seealso marker="erlang"><c>erlang(3)</c></seealso>,
+      <seealso marker="kernel:erl_ddll"><c>kernel:erl_ddll(3)</c></seealso>,
+      section <seealso marker="alt_dist">How to Implement an Alternative
+      Carrier for the Erlang Distribution></seealso> in the User's Guide</p>
   </section>
 </cref>
diff --git a/erts/doc/src/erl_ext_dist.xml b/erts/doc/src/erl_ext_dist.xml
index 2ac974f497..2ff0f39a3f 100644
--- a/erts/doc/src/erl_ext_dist.xml
+++ b/erts/doc/src/erl_ext_dist.xml
@@ -35,135 +35,130 @@
   <section>
     <title>Introduction</title>
     <p>
-      The external term format is mainly used in the distribution 
+      The external term format is mainly used in the distribution
       mechanism of Erlang.
     </p>
     <p>
-      Since Erlang has a fixed number of types, there is no need for a 
-      programmer to define a specification for the external format used 
+      As Erlang has a fixed number of types, there is no need for a
+      programmer to define a specification for the external format used
       within some application.
-      All Erlang terms has an external representation and the interpretation 
-      of the different terms are application specific.
+      All Erlang terms have an external representation and the interpretation
+      of the different terms is application-specific.
     </p>
     <p>
-      In Erlang the BIF <seealso marker="erts:erlang#term_to_binary/1">term_to_binary/1,2</seealso> is used to convert a 
-      term into the external format. 
-      To convert binary data encoding a term the BIF
+      In Erlang the BIF <seealso marker="erts:erlang#term_to_binary/1">
+      <c>erlang:term_to_binary/1,2</c></seealso> is used to convert a
+      term into the external format.
+      To convert binary data encoding to a term, the BIF
       <seealso marker="erts:erlang#binary_to_term/1">
-	binary_to_term/1
-      </seealso> 
-      is used.
+      <c>erlang:binary_to_term/1</c>c></seealso> is used.
     </p>
     <p>
-      The distribution does this implicitly when sending messages across 
+      The distribution does this implicitly when sending messages across
       node boundaries.
     </p>
     <marker id="overall_format"/>
     <p>
-      The overall format of the term format is:
+      The overall format of the term format is as follows:
     </p>
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">1</cell>
-	<cell align="center">N</cell>
+        <cell align="center">1</cell>
+        <cell align="center">1</cell>
+        <cell align="center">N</cell>
       </row>
-	  <row>
-	    <cell align="center"><c>131</c></cell>
-	    <cell align="center"><c>Tag</c></cell>
-	    <cell align="center"><c>Data</c></cell>
-	  </row>
-    <tcaption></tcaption></table>
+      <row>
+        <cell align="center"><c>131</c></cell>
+        <cell align="center"><c>Tag</c></cell>
+        <cell align="center"><c>Data</c></cell>
+      </row>
+    <tcaption>Term Format</tcaption></table>
     <note>
-    <p>
-      When messages are
-      <seealso marker="erl_dist_protocol#connected_nodes">passed between
-      connected nodes</seealso> and a
-      <seealso marker="#distribution_header">distribution
-      header</seealso> is used, the first byte containing the version
-      number (131) is omitted from the terms that follow the distribution
-      header. This since
-      the version number is implied by the version number in the
-      distribution header.
-    </p>
+      <p>
+        When messages are
+        <seealso marker="erl_dist_protocol#connected_nodes">passed between
+        connected nodes</seealso> and a
+        <seealso marker="#distribution_header">distribution
+        header</seealso> is used, the first byte containing the version
+        number (131) is omitted from the terms that follow the distribution
+        header. This is because the version number is implied by the version
+        number in the distribution header.
+      </p>
     </note>
     <p>
-      A compressed term looks like this:
+      The compressed term format is as follows:
     </p>
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">1</cell>
-	<cell align="center">4</cell>
-	<cell align="center">N</cell>
+        <cell align="center">1</cell>
+        <cell align="center">1</cell>
+        <cell align="center">4</cell>
+        <cell align="center">N</cell>
       </row>
       <row>
-	<cell align="center">131</cell>
-	<cell align="center">80</cell>
-	<cell align="center">UncompressedSize</cell>
-	<cell align="center">Zlib-compressedData</cell>
+        <cell align="center"><c>131</c></cell>
+        <cell align="center"><c>80</c></cell>
+        <cell align="center"><c>UncompressedSize</c></cell>
+        <cell align="center"><c>Zlib-compressedData</c></cell>
       </row>
-    <tcaption></tcaption></table>
+    <tcaption>Compressed Term Format</tcaption></table>
     <p>
-      Uncompressed Size (unsigned 32 bit integer in big-endian byte order)
+      Uncompressed size (unsigned 32-bit integer in big-endian byte order)
       is the size of the data before it was compressed.
-      The compressed data has the following format when it has been 
-      expanded:
+      The compressed data has the following format when it has been expanded:
     </p>
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">Uncompressed Size</cell>
+        <cell align="center">1</cell>
+        <cell align="center">Uncompressed Size</cell>
       </row>
       <row>
-	<cell align="center">Tag</cell>
-	<cell align="center">Data</cell>
+        <cell align="center"><c>Tag</c></cell>
+        <cell align="center"><c>Data</c></cell>
       </row>
-    <tcaption></tcaption></table>
+    <tcaption>Compressed Data Format when Expanded</tcaption></table>
     <marker id="utf8_atoms"/>
     <note>
-    <p>As of ERTS version 5.10 (OTP-R16) support
-    for UTF-8 encoded atoms has been introduced in the external format.
-    However, only characters that can be encoded using Latin1 (ISO-8859-1)
-    are currently supported in atoms. The support for UTF-8 encoded atoms
-    in the external format has been implemented in order to be able to support
-    all Unicode characters in atoms in <em>some future release</em>.
-    Until full Unicode support for
-    atoms has been introduced, it is an <em>error</em> to pass atoms containing
-    characters that cannot be encoded in Latin1, and <em>the behavior is
-    undefined</em>.</p>
-    <p>When the
-    <seealso marker="erl_dist_protocol#dflags"><c>DFLAG_UTF8_ATOMS</c></seealso>
-    distribution flag has been exchanged between both nodes in the
-    <seealso marker="erl_dist_protocol#distribution_handshake">distribution handshake</seealso>,
-    all atoms in the distribution header will be encoded in UTF-8; otherwise,
-    all atoms in the distribution header will be encoded in Latin1. The two
-    new tags <seealso marker="#ATOM_UTF8_EXT">ATOM_UTF8_EXT</seealso>, and
-    <seealso marker="#SMALL_ATOM_UTF8_EXT">SMALL_ATOM_UTF8_EXT</seealso>
-    will only be used if the <c>DFLAG_UTF8_ATOMS</c> distribution flag has
-    been exchanged between nodes, or if an atom containing characters
-    that cannot be encoded in Latin1 is encountered.
-    </p>
-    <p>The maximum number of allowed characters in an atom is 255. In the
-    UTF-8 case each character may need 4 bytes to be encoded.
-    </p>
+      <p>As from <c>ERTS</c> 5.10 (OTP R16) support
+        for UTF-8 encoded atoms has been introduced in the external format.
+        However, only characters that can be encoded using Latin-1 (ISO-8859-1)
+        are currently supported in atoms. The support for UTF-8 encoded atoms
+        in the external format has been implemented to be able to support
+        all Unicode characters in atoms in <em>some future release</em>.
+        Until full Unicode support for atoms has been introduced,
+        it is an <em>error</em> to pass atoms containing
+        characters that cannot be encoded in Latin-1, and <em>the behavior is
+        undefined</em>.</p>
+      <p>When distribution flag <seealso marker="erl_dist_protocol#dflags">
+        <c>DFLAG_UTF8_ATOMS</c></seealso> has been exchanged between both nodes
+        in th <seealso marker="erl_dist_protocol#distribution_handshake">
+        distribution handshake</seealso>, all atoms in the distribution header
+        are encoded in UTF-8, otherwise in Latin-1. The two
+        new tags <seealso marker="#ATOM_UTF8_EXT"><c>ATOM_UTF8_EXT</c></seealso>
+        and <seealso marker="#SMALL_ATOM_UTF8_EXT">
+        <c>SMALL_ATOM_UTF8_EXT</c></seealso>
+        are only used if the distribution flag <c>DFLAG_UTF8_ATOMS</c> has
+        been exchanged between nodes, or if an atom containing characters
+        that cannot be encoded in Latin-1 is encountered.</p>
+      <p>The maximum number of allowed characters in an atom is 255. In the
+        UTF-8 case, each character can need 4 bytes to be encoded.</p>
     </note>
   </section>
 
   <section>  
-    <title>Distribution header</title>
+    <title>Distribution Header</title>
     <p>
       <marker id="distribution_header"/>
-      As of erts version 5.7.2 the old atom cache protocol was
-      dropped and a new one was introduced. This atom cache protocol
-      introduced the distribution header. Nodes with erts versions
+      As from <c>ERTS</c> 5.7.2 the old atom cache protocol was
+      dropped and a new one was introduced. This protocol
+      introduced the distribution header. Nodes with an <c>ERTS</c> version
       earlier than 5.7.2 can still communicate with new nodes,
-      but no distribution header and no atom cache will be used.</p>
+      but no distribution header and no atom cache are used.</p>
     <p>
-      The distribution header currently only contains an atom cache
-      reference section, but could in the future contain more
+      The distribution header only contains an atom cache
+      reference section, but can in the future contain more
       information. The distribution header precedes one or more Erlang
-      terms on the external format. For more information see the
+      terms on the external format. For more information, see the
       documentation of the
       <seealso marker="erl_dist_protocol#connected_nodes">protocol between
       connected nodes</seealso> in the
@@ -173,37 +168,37 @@
     <p>
       <seealso marker="#ATOM_CACHE_REF">ATOM_CACHE_REF</seealso>
       entries with corresponding <c>AtomCacheReferenceIndex</c> in terms
-      encoded on the external format following a distribution header refers
+      encoded on the external format following a distribution header refer
       to the atom cache references made in the distribution header. The range
-      is 0 &lt;= <c>AtomCacheReferenceIndex</c> &lt; 255, i.e., at most 255
+      is 0 &lt;= <c>AtomCacheReferenceIndex</c> &lt; 255, that is, at most 255
       different atom cache references from the following terms can be made.
     </p>
     <p>
-      The distribution header format is:
+      The distribution header format is as follows:
     </p>
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">1</cell>
-	<cell align="center">1</cell>
-	<cell align="center">NumberOfAtomCacheRefs/2+1 | 0</cell>
-	<cell align="center">N | 0</cell>
+        <cell align="center">1</cell>
+        <cell align="center">1</cell>
+        <cell align="center">1</cell>
+        <cell align="center">NumberOfAtomCacheRefs/2+1 | 0</cell>
+        <cell align="center">N | 0</cell>
       </row>
       <row>
-	<cell align="center"><c>131</c></cell>
-	<cell align="center"><c>68</c></cell>
-	<cell align="center"><c>NumberOfAtomCacheRefs</c></cell>
-	<cell align="center"><c>Flags</c></cell>
-	<cell align="center"><c>AtomCacheRefs</c></cell>
+        <cell align="center"><c>131</c></cell>
+        <cell align="center"><c>68</c></cell>
+        <cell align="center"><c>NumberOfAtomCacheRefs</c></cell>
+        <cell align="center"><c>Flags</c></cell>
+        <cell align="center"><c>AtomCacheRefs</c></cell>
       </row>
-    <tcaption></tcaption></table>
+    <tcaption>Distribution Header Format</tcaption></table>
     <p>
-      <c>Flags</c> consists of <c>NumberOfAtomCacheRefs/2+1</c> bytes,
+      <c>Flags</c> consist of <c>NumberOfAtomCacheRefs/2+1</c> bytes,
       unless <c>NumberOfAtomCacheRefs</c> is <c>0</c>. If
       <c>NumberOfAtomCacheRefs</c> is <c>0</c>, <c>Flags</c> and
-      <c>AtomCacheRefs</c> are omitted. Each atom cache reference have
+      <c>AtomCacheRefs</c> are omitted. Each atom cache reference has
       a half byte flag field. Flags corresponding to a specific
-      <c>AtomCacheReferenceIndex</c>, are located in flag byte number
+      <c>AtomCacheReferenceIndex</c> are located in flag byte number
       <c>AtomCacheReferenceIndex/2</c>. Flag byte 0 is the first byte
       after the <c>NumberOfAtomCacheRefs</c> byte. Flags for an even
       <c>AtomCacheReferenceIndex</c> are located in the least significant
@@ -216,95 +211,97 @@
     </p>
     <table align="left">
       <row>
-	<cell align="center">1 bit</cell>
-	<cell align="center">3 bits</cell>
+        <cell align="center">1 bit</cell>
+        <cell align="center">3 bits</cell>
       </row>
       <row>
-	<cell align="center"><c>NewCacheEntryFlag</c></cell>
-	<cell align="center"><c>SegmentIndex</c></cell>
+        <cell align="center"><c>NewCacheEntryFlag</c></cell>
+        <cell align="center"><c>SegmentIndex</c></cell>
       </row>
     <tcaption></tcaption></table>
     <p>
       The most significant bit is the <c>NewCacheEntryFlag</c>. If set,
       the corresponding cache reference is new. The three least
       significant bits are the <c>SegmentIndex</c> of the corresponding
-      atom cache entry. An atom cache consists of 8 segments each of size
-      256, i.e., an atom cache can contain 2048 entries.
+      atom cache entry. An atom cache consists of 8 segments, each of size
+      256, that is, an atom cache can contain 2048 entries.
     </p>
     <p>
       After flag fields for atom cache references, another half byte flag
-      field is located which has the following format:
+      field is located with the following format:
     </p>
     <table align="left">
       <row>
-	<cell align="center">3 bits</cell>
-	<cell align="center">1 bit</cell>
+        <cell align="center">3 bits</cell>
+        <cell align="center">1 bit</cell>
       </row>
       <row>
-	<cell align="center"><c>CurrentlyUnused</c></cell>
-	<cell align="center"><c>LongAtoms</c></cell>
+        <cell align="center"><c>CurrentlyUnused</c></cell>
+        <cell align="center"><c>LongAtoms</c></cell>
       </row>
     <tcaption></tcaption></table>
     <p>
-      The least significant bit in that half byte is the <c>LongAtoms</c>
-      flag. If it is set, 2 bytes are used for atom lengths instead of
+      The least significant bit in that half byte is flag <c>LongAtoms</c>.
+      If it is set, 2 bytes are used for atom lengths instead of
       1 byte in the distribution header.
     </p>
     <p>
       After the <c>Flags</c> field follow the <c>AtomCacheRefs</c>. The
       first <c>AtomCacheRef</c> is the one corresponding to
-      <c>AtomCacheReferenceIndex</c> 0. Higher indices follows
+      <c>AtomCacheReferenceIndex</c> 0. Higher indices follow
       in sequence up to index <c>NumberOfAtomCacheRefs - 1</c>.
     </p>
     <p>
       If the <c>NewCacheEntryFlag</c> for the next <c>AtomCacheRef</c> has
-      been set, a <c>NewAtomCacheRef</c> on the following format will follow:
+      been set, a <c>NewAtomCacheRef</c> on the following format follows:
     </p>
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">1 | 2</cell>
-	<cell align="center">Length</cell>
+        <cell align="center">1</cell>
+        <cell align="center">1 | 2</cell>
+        <cell align="center">Length</cell>
       </row>
       <row>
-	<cell align="center"><c>InternalSegmentIndex</c></cell>
-	<cell align="center"><c>Length</c></cell>
-	<cell align="center"><c>AtomText</c></cell>
+        <cell align="center"><c>InternalSegmentIndex</c></cell>
+        <cell align="center"><c>Length</c></cell>
+        <cell align="center"><c>AtomText</c></cell>
       </row>
     <tcaption></tcaption></table>
     <p>
       <c>InternalSegmentIndex</c> together with the <c>SegmentIndex</c>
       completely identify the location of an atom cache entry in the
-      atom cache. <c>Length</c> is number of bytes that <c>AtomText</c>
-      consists of. Length is a two byte big endian integer
-      if the <c>LongAtoms</c> flag has been set, otherwise a one byte
-      integer. When the
-      <seealso marker="erl_dist_protocol#dflags"><c>DFLAG_UTF8_ATOMS</c></seealso>
-      distribution flag has been exchanged between both nodes in the
-      <seealso marker="erl_dist_protocol#distribution_handshake">distribution handshake</seealso>,
-      characters in <c>AtomText</c> is encoded in UTF-8; otherwise,
-      encoded in Latin1. Subsequent <c>CachedAtomRef</c>s with the same
+      atom cache. <c>Length</c> is the number of bytes that <c>AtomText</c>
+      consists of. Length is a 2 byte big-endian integer
+      if flag <c>LongAtoms</c> has been set, otherwise a 1 byte
+      integer. When distribution flag
+      <seealso marker="erl_dist_protocol#dflags">
+      <c>DFLAG_UTF8_ATOMS</c></seealso>
+      has been exchanged between both nodes in the
+      <seealso marker="erl_dist_protocol#distribution_handshake">
+      distribution handshake</seealso>,
+      characters in <c>AtomText</c> are encoded in UTF-8, otherwise
+      in Latin-1. The following <c>CachedAtomRef</c>s with the same
       <c>SegmentIndex</c> and <c>InternalSegmentIndex</c> as this
-      <c>NewAtomCacheRef</c> will refer to this atom until a new
+      <c>NewAtomCacheRef</c> refer to this atom until a new
       <c>NewAtomCacheRef</c> with the same <c>SegmentIndex</c>
       and <c>InternalSegmentIndex</c> appear.
     </p>
     <p>
-      For more information on encoding of atoms, see
+      For more information on encoding of atoms, see the
       <seealso marker="#utf8_atoms">note on UTF-8 encoded atoms</seealso>
-      in the beginning of this document.
+      in the beginning of this section.
     </p>
     <p>
       If the <c>NewCacheEntryFlag</c> for the next <c>AtomCacheRef</c>
       has not been set, a <c>CachedAtomRef</c> on the following format
-      will follow:
+      follows:
     </p>
     <table align="left">
       <row>
-	<cell align="center">1</cell>
+        <cell align="center">1</cell>
       </row>
       <row>
-	<cell align="center"><c>InternalSegmentIndex</c></cell>
+        <cell align="center"><c>InternalSegmentIndex</c></cell>
       </row>
     <tcaption></tcaption></table>
     <p>
@@ -319,157 +316,147 @@
   <section>
     <marker id="ATOM_CACHE_REF"/>
     <title>ATOM_CACHE_REF</title>
-
     <table align="left">
       <row>
         <cell align="center">1</cell>
-	<cell align="center">1</cell>
+        <cell align="center">1</cell>
       </row>
       <row>
-	<cell align="center"><c>82</c></cell>
-	<cell align="center"><c>AtomCacheReferenceIndex</c></cell>
+        <cell align="center"><c>82</c></cell>
+        <cell align="center"><c>AtomCacheReferenceIndex</c></cell>
       </row>
-      <tcaption></tcaption></table>
+      <tcaption>ATOM_CACHE_REF</tcaption></table>
       <p>
         Refers to the atom with <c>AtomCacheReferenceIndex</c> in the
-	<seealso marker="#distribution_header">distribution header</seealso>.
+        <seealso marker="#distribution_header">distribution header</seealso>.
      </p>
   </section>
 
   <section>
     <marker id="SMALL_INTEGER_EXT"/>
     <title>SMALL_INTEGER_EXT</title>
-
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">1</cell>
+        <cell align="center">1</cell>
+        <cell align="center">1</cell>
       </row>
       <row>
-	<cell align="center">97</cell>
-	<cell align="center">Int</cell>
+        <cell align="center"><c>97</c></cell>
+        <cell align="center"><c>Int</c></cell>
       </row>
-    <tcaption></tcaption></table>
+    <tcaption>SMALL_INTEGER_EXT</tcaption></table>
     <p>
-      Unsigned 8 bit integer.
+      Unsigned 8-bit integer.
     </p>
   </section>
 
   <section>
     <marker id="INTEGER_EXT"/>
     <title>INTEGER_EXT</title>
-
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">4</cell>
+        <cell align="center">1</cell>
+        <cell align="center">4</cell>
       </row>
       <row>
-	<cell align="center">98</cell>
-	<cell align="center">Int</cell>
+        <cell align="center"><c>98</c></cell>
+        <cell align="center"><c>Int</c></cell>
       </row>
-    <tcaption></tcaption></table>
+    <tcaption>INTEGER_EXT</tcaption></table>
     <p>
-      Signed 32 bit integer in big-endian format (i.e. MSB first)
+      Signed 32-bit integer in big-endian format (that is, MSB first).
     </p>
   </section>
 
   <section>
     <marker id="FLOAT_EXT"/>
     <title>FLOAT_EXT</title>
-
     <table align="left">
       <row>
-	<cell align="center">1</cell>
-	<cell align="center">31</cell>
+        <cell align="center">1</cell>
+        <cell align="center">31</cell>
       </row>
       <row>
-	<cell align="center">99</cell>
-	<cell align="center">Float String</cell>
+        <cell align="center"><c>99</c></cell>
+        <cell align="center"><c>Float string</c></cell>
       </row>
-    <tcaption></tcaption></table>
+    <tcaption>FLOAT_EXT</tcaption></table>
     <p>
-      A float is stored in string format. the format used in sprintf to
-      format the float is "%.20e"  
+      A float is stored in string format. The format used in sprintf to
+      format the float is "%.20e"
       (there are more bytes allocated than necessary).
-      To unpack the float use sscanf with format "%lf".
+      To unpack the float, use sscanf with format "%lf".
     </p>
     <p>
-      This term is used in minor version 0 of the external format; 
-      it has been superseded by 
-      <seealso marker="#NEW_FLOAT_EXT">
-	NEW_FLOAT_EXT
-	</seealso>.
+      This term is used in minor version 0 of the external format;
+      it has been superseded by
+      <seealso marker="#NEW_FLOAT_EXT"><c>NEW_FLOAT_EXT</c></seealso>.
     </p>
   </section>
 
     <section>
       <marker id="ATOM_EXT"/>
       <title>ATOM_EXT</title>
-
 	<table align="left">
 	  <row>
-	    <cell align="center">1</cell>
-	    <cell align="center">2</cell>
-	    <cell align="center">Len</cell>
+            <cell align="center">1</cell>
+            <cell align="center">2</cell>
+            <cell align="center">Len</cell>
 	  </row>
 	  <row>
-	    <cell align="center"><c>100</c></cell>
-	    <cell align="center"><c>Len</c></cell>
-	    <cell align="center"><c>AtomName</c></cell>
+            <cell align="center"><c>100</c></cell>
+            <cell align="center"><c>Len</c></cell>
+            <cell align="center"><c>AtomName</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>ATOM_EXT</tcaption></table>
       <p>
-	An atom is stored with a 2 byte unsigned length in big-endian order, 
-	followed by <c>Len</c> numbers of 8 bit Latin1 characters that forms
-	the <c>AtomName</c>.
-	<em>Note</em>: The maximum allowed value for <c>Len</c> is 255.
+        An atom is stored with a 2 byte unsigned length in big-endian order,
+        followed by <c>Len</c> numbers of 8-bit Latin-1 characters that forms
+        the <c>AtomName</c>. The maximum allowed value for <c>Len</c> is 255.
       </p>
     </section>
 
     <section>
       <marker id="REFERENCE_EXT"/>
       <title>REFERENCE_EXT</title>
-
-	<table align="left">
-	  <row>
-	    <cell align="center">1</cell>
-	    <cell align="center">N</cell>
-	    <cell align="center">4</cell>
-	    <cell align="center">1</cell>
-	  </row>
-	  <row>
-	    <cell align="center"><c>101</c></cell>
-	    <cell align="center"><c>Node</c></cell>
-	    <cell align="center"><c>ID</c></cell>
-	    <cell align="center"><c>Creation</c></cell>
-	  </row>
-	<tcaption></tcaption></table>
+      <table align="left">
+        <row>
+          <cell align="center">1</cell>
+          <cell align="center">N</cell>
+          <cell align="center">4</cell>
+          <cell align="center">1</cell>
+        </row>
+        <row>
+          <cell align="center"><c>101</c></cell>
+          <cell align="center"><c>Node</c></cell>
+          <cell align="center"><c>ID</c></cell>
+          <cell align="center"><c>Creation</c></cell>
+        </row>
+      <tcaption>REFERENCE_EXT</tcaption></table>
       <p>
-	Encode a reference object (an object generated with <c>make_ref/0</c>).
-	The <c>Node</c> term is an encoded atom, i.e. 
-	<seealso marker="#ATOM_EXT">ATOM_EXT</seealso>, 
-	<seealso marker="#SMALL_ATOM_EXT">SMALL_ATOM_EXT</seealso> or
-	<seealso marker="#ATOM_CACHE_REF">ATOM_CACHE_REF</seealso>. 
-	The <c>ID</c> field contains a big-endian 
-	unsigned integer,
-	but <em>should be regarded as uninterpreted data</em> 
-	since this field is node specific. 
-	<c>Creation</c> is a byte containing a node serial number that
-	makes it possible to separate old (crashed) nodes from a new one.
+        Encodes a reference object (an object generated with
+        <seealso marker="erlang:make_ref/0">erlang:make_ref/0</seealso>).
+        The <c>Node</c> term is an encoded atom, that is,
+        <seealso marker="#ATOM_EXT"><c>ATOM_EXT</c></seealso>, 
+        <seealso marker="#SMALL_ATOM_EXT"><c>SMALL_ATOM_EXT</c></seealso>, or
+        <seealso marker="#ATOM_CACHE_REF"><c>ATOM_CACHE_REF</c></seealso>. 
+        The <c>ID</c> field contains a big-endian unsigned integer,
+        but <em>is to be regarded as uninterpreted data</em>,
+        as this field is node-specific.
+        <c>Creation</c> is a byte containing a node serial number, which
+        makes it possible to separate old (crashed) nodes from a new one.
       </p>
       <p>
-	In <c>ID</c>, only 18 bits are significant; the rest should be 0.
-	In <c>Creation</c>, only 2 bits are significant; the rest should be 0.
-
-	See <seealso marker="#NEW_REFERENCE_EXT">NEW_REFERENCE_EXT</seealso>.
+        In <c>ID</c>, only 18 bits are significant; the rest are to be 0.
+        In <c>Creation</c>, only two bits are significant; the rest are to be 0.
+        See <seealso marker="#NEW_REFERENCE_EXT">
+        <c>NEW_REFERENCE_EXT</c></seealso>.
       </p>
     </section>
 
     <section>
       <marker id="PORT_EXT"/>
       <title>PORT_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -483,20 +470,21 @@
 	    <cell align="center"><c>ID</c></cell>
 	    <cell align="center"><c>Creation</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>PORT_EXT</tcaption></table>
 	<p>
-	  Encode a port object (obtained form <c>open_port/2</c>).
-	  The <c>ID</c> is a node specific identifier for a local port.
+	  Encodes a port object (obtained from
+          <seealso marker="erlang:open_port/2">
+          <c>erlang:open_port/2</c></seealso>).
+	  The <c>ID</c> is a node-specific identifier for a local port.
 	  Port operations are not allowed across node boundaries.
 	  The <c>Creation</c> works just like in
-	  <seealso marker="#REFERENCE_EXT">REFERENCE_EXT</seealso>.
+	  <seealso marker="#REFERENCE_EXT"><c>REFERENCE_EXT</c></seealso>.
 	</p>
     </section>
 
     <section>
       <marker id="PID_EXT"/>
       <title>PID_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -512,23 +500,20 @@
 	    <cell align="center"><c>Serial</c></cell>
 	    <cell align="center"><c>Creation</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>PID_EXT</tcaption></table>
 	<p>
-	  Encode a process identifier object (obtained from <c>spawn/3</c> or
-	  friends).
-	  The <c>ID</c> and <c>Creation</c> fields works just like in 
-	  <seealso marker="#REFERENCE_EXT">REFERENCE_EXT</seealso>, while
-	  the <c>Serial</c> field is used to improve safety.
-	  
-	  In <c>ID</c>, only 15 bits are significant; the rest should be 0.
+	  Encodes a process identifier object (obtained from
+          <seealso marker="erlang:spawn/3"><c>erlang:spawn/3</c></seealso> or
+	  friends). The <c>ID</c> and <c>Creation</c> fields works just like in
+	  <seealso marker="#REFERENCE_EXT"><c>REFERENCE_EXT</c></seealso>, while
+	  the <c>Serial</c> field is used to improve safety.	  
+	  In <c>ID</c>, only 15 bits are significant; the rest are to be 0.
 	</p>
-
     </section>
 
     <section>
       <marker id="SMALL_TUPLE_EXT"/>
       <title>SMALL_TUPLE_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -536,22 +521,21 @@
 	    <cell align="center">N</cell>
 	  </row>
 	  <row>
-	    <cell align="center">104</cell>
-	    <cell align="center">Arity</cell>
-	    <cell align="center">Elements</cell>
+	    <cell align="center"><c>104</c></cell>
+	    <cell align="center"><c>Arity</c></cell>
+	    <cell align="center"><c>Elements</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>SMALL_TUPLE_EXT</tcaption></table>
 	<p>
-	  <c>SMALL_TUPLE_EXT</c> encodes a tuple. The <c>Arity</c>
-	  field is an unsigned byte that determines how many element
-	  that follows in the <c>Elements</c> section.
+	  Encodes a tuple. The <c>Arity</c>
+	  field is an unsigned byte that determines how many elements
+	  that follows in section <c>Elements</c>.
 	</p>
     </section>
 
     <section>
       <marker id="LARGE_TUPLE_EXT"/>
       <title>LARGE_TUPLE_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -559,23 +543,22 @@
 	    <cell align="center">N</cell>
 	  </row>
 	  <row>
-	    <cell align="center">105</cell>
-	    <cell align="center">Arity</cell>
-	    <cell align="center">Elements</cell>
+	    <cell align="center"><c>105</c></cell>
+	    <cell align="center"><c>Arity</c></cell>
+	    <cell align="center"><c>Elements</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>LARGE_TUPLE_EXT</tcaption></table>
 	<p>
-	  Same as 
-	  <seealso marker="#SMALL_TUPLE_EXT">SMALL_TUPLE_EXT</seealso>
-	  with the exception that <c>Arity</c> is an 
-	  unsigned 4 byte integer in big endian format.
+	  Same as
+	  <seealso marker="#SMALL_TUPLE_EXT"><c>SMALL_TUPLE_EXT</c></seealso>
+	  except that <c>Arity</c> is an
+          unsigned 4 byte integer in big-endian format.
 	</p>
     </section>
 
     <section>
       <marker id="MAP_EXT"/>
       <title>MAP_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -583,43 +566,42 @@
 	    <cell align="center">N</cell>
 	  </row>
 	  <row>
-	    <cell align="center">116</cell>
-	    <cell align="center">Arity</cell>
-	    <cell align="center">Pairs</cell>
+	    <cell align="center"><c>116</c></cell>
+	    <cell align="center"><c>Arity</c></cell>
+	    <cell align="center"><c>Pairs</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>MAP_EXT</tcaption></table>
 	<p>
-	  <c>MAP_EXT</c> encodes a map. The <c>Arity</c> field is an unsigned
-	  4 byte integer in big endian format that determines the number of
+	  Encodes a map. The <c>Arity</c> field is an unsigned
+	  4 byte integer in big-endian format that determines the number of
 	  key-value pairs in the map. Key and value pairs (<c>Ki => Vi</c>)
-	  are encoded in the <c>Pairs</c> section in the following order:
+	  are encoded in section <c>Pairs</c> in the following order:
 	  <c>K1, V1, K2, V2,..., Kn, Vn</c>.
 	  Duplicate keys are <em>not allowed</em> within the same map.
 	</p>
-	<p><em>Since: </em>OTP 17.0</p>
+	<p><em>As from </em>Erlang/OTP 17.0</p>
     </section>
 
     <section>
       <marker id="NIL_EXT"/>
       <title>NIL_EXT</title>
-
       <table align="left">
 	<row>
 	  <cell align="center">1</cell>
 	</row>
 	<row>
-	  <cell align="center">106</cell>
+	  <cell align="center"><c>106</c></cell>
 	</row>
-      <tcaption></tcaption></table>
+      <tcaption>NIL_EXT</tcaption></table>
       <p>
-	The representation for an empty list, i.e. the Erlang syntax <c>[]</c>.
+	The representation for an empty list, that is, the Erlang syntax
+        <c>[]</c>.
       </p>
     </section>
 
     <section>
       <marker id="STRING_EXT"/>
       <title>STRING_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -627,27 +609,25 @@
 	    <cell align="center">Len</cell>
 	  </row>
 	  <row>
-	    <cell align="center">107</cell>
-	    <cell align="center">Length</cell>
-	    <cell align="center">Characters</cell>
+	    <cell align="center"><c>107</c></cell>
+	    <cell align="center"><c>Length</c></cell>
+	    <cell align="center"><c>Characters</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>STRING_EXT</tcaption></table>
 	<p>
-	  String does NOT have a corresponding Erlang representation,
+	  String does <em>not</em> have a corresponding Erlang representation,
 	  but is an optimization for sending lists of bytes (integer in
 	  the range 0-255) more efficiently over the distribution.
-	  Since the <c>Length</c> field is an unsigned 2 byte integer 
-	  (big endian), implementations must make sure that lists longer than 
-	  65535 elements are encoded as 
-	  <seealso marker="#LIST_EXT">LIST_EXT</seealso>.
+	  As field <c>Length</c> is an unsigned 2 byte integer
+	  (big-endian), implementations must ensure that lists longer than
+	  65535 elements are encoded as
+	  <seealso marker="#LIST_EXT"><c>LIST_EXT</c></seealso>.
 	</p>
-
     </section>
 
     <section>
       <marker id="LIST_EXT"/>
       <title>LIST_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -656,27 +636,24 @@
 	    <cell align="center">&nbsp;</cell>
 	  </row>
 	  <row>
-	    <cell align="center">108</cell>
-	    <cell align="center">Length</cell>
-	    <cell align="center">Elements</cell>
-	    <cell align="center">Tail</cell>
+	    <cell align="center"><c>108</c></cell>
+	    <cell align="center"><c>Length</c></cell>
+	    <cell align="center"><c>Elements</c></cell>
+	    <cell align="center"><c>Tail</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
-
+	<tcaption>LIST_EXT</tcaption></table>
 	<p>
-	  <c>Length</c> is the number of elements that follows in the
-	  <c>Elements</c> section. <c>Tail</c> is the final tail of
-	  the list; it is
-	  <seealso marker="#NIL_EXT">NIL_EXT</seealso>
-	  for a proper list, but may be anything type if the list is
-	  improper (for instance <c>[a|b]</c>).
+	  <c>Length</c> is the number of elements that follows in section
+	  <c>Elements</c>. <c>Tail</c> is the final tail of the list; it is
+	  <seealso marker="#NIL_EXT"><c>NIL_EXT</c></seealso>
+	  for a proper list, but can be any type if the list is
+	  improper (for example, <c>[a|b]</c>).
 	</p>
     </section>
 
     <section>
       <marker id="BINARY_EXT"/>
       <title>BINARY_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -684,25 +661,26 @@
 	    <cell align="center">Len</cell>
 	  </row>
 	  <row>
-	    <cell align="center">109</cell>
-	    <cell align="center">Len</cell>
-	    <cell align="center">Data</cell>
+	    <cell align="center"><c>109</c></cell>
+	    <cell align="center"><c>Len</c></cell>
+	    <cell align="center"><c>Data</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>BINARY_EXT</tcaption></table>
 	<p>
 	  Binaries are generated with bit syntax expression or with
-	  <seealso marker="erts:erlang#list_to_binary/1">list_to_binary/1</seealso>,
-	  <seealso marker="erts:erlang#term_to_binary/1">term_to_binary/1</seealso>,
+	  <seealso marker="erts:erlang#list_to_binary/1">
+	  <c>erlang:list_to_binary/1</c></seealso>,
+	  <seealso marker="erts:erlang#term_to_binary/1">
+	  <c>erlang:term_to_binary/1</c></seealso>,
 	  or as input from binary ports.
-	  The <c>Len</c> length field is an unsigned 4 byte integer 
-	  (big endian).
+	  The <c>Len</c> length field is an unsigned 4 byte integer
+	  (big-endian).
 	</p>
     </section>
 
     <section>
       <marker id="SMALL_BIG_EXT"/>
       <title>SMALL_BIG_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -711,27 +689,26 @@
 	    <cell align="center">n</cell>
 	  </row>
 	  <row>
-	    <cell align="center">110</cell>
-	    <cell align="center">n</cell>
-	    <cell align="center">Sign</cell>
-	    <cell align="center">d(0) ... d(n-1)</cell>
+	    <cell align="center"><c>110</c></cell>
+	    <cell align="center"><c>n</c></cell>
+	    <cell align="center"><c>Sign</c></cell>
+	    <cell align="center"><c>d(0)</c> ... <c>d(n-1)</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>SMALL_BIG_EXT</tcaption></table>
 	<p>
-	  Bignums are stored in unary form with a <c>Sign</c> byte
-	  that is 0 if the binum is positive and 1 if is negative. The
-	  digits are stored with the LSB byte stored first. To
-	  calculate the integer the following formula can be used:<br/>
-	  
-	  B = 256<br/>
-	  (d0*B^0 + d1*B^1 + d2*B^2 + ... d(N-1)*B^(n-1))
+	  Bignums are stored in unary form with a <c>Sign</c> byte,
+	  that is, 0 if the binum is positive and 1 if it is negative. The
+	  digits are stored with the least significant byte stored first. To
+	  calculate the integer, the following formula can be used:
+	</p>
+	<p><c>B</c> = 256<br/>
+	  <c>(d0*B^0 + d1*B^1 + d2*B^2 + ... d(N-1)*B^(n-1))</c>
 	</p>
     </section>
 
     <section>
       <marker id="LARGE_BIG_EXT"/>
       <title>LARGE_BIG_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -740,24 +717,22 @@
 	    <cell align="center">n</cell>
 	  </row>
 	  <row>
-	    <cell align="center">111</cell>
-	    <cell align="center">n</cell>
-	    <cell align="center">Sign</cell>
-	    <cell align="center">d(0) ... d(n-1)</cell>
+	    <cell align="center"><c>111</c></cell>
+	    <cell align="center"><c>n</c></cell>
+	    <cell align="center"><c>Sign</c></cell>
+	    <cell align="center"><c>d(0)</c> ... <c>d(n-1)</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>LARGE_BIG_EXT</tcaption></table>
 	<p>
-	  Same as <seealso marker="#SMALL_BIG_EXT">SMALL_BIG_EXT</seealso> 
-	  with the difference that the length field 
-	  is an unsigned 4 byte integer.
+	  Same as <seealso marker="#SMALL_BIG_EXT">
+	  <c>SMALL_BIG_EXT</c></seealso> 
+	  except that the length field is an unsigned 4 byte integer.
 	</p>
-
     </section>
 
     <section>
       <marker id="NEW_REFERENCE_EXT"/>
       <title>NEW_REFERENCE_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -767,44 +742,43 @@
 	    <cell align="center">N'</cell>
 	  </row>
 	  <row>
-	    <cell align="center">114</cell>
-	    <cell align="center">Len</cell>
-	    <cell align="center">Node</cell>
-	    <cell align="center">Creation</cell>
-	    <cell align="center">ID ...</cell>
+	    <cell align="center"><c>114</c></cell>
+	    <cell align="center"><c>Len</c></cell>
+	    <cell align="center"><c>Node</c></cell>
+	    <cell align="center"><c>Creation</c></cell>
+	    <cell align="center"><c>ID ...</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>NEW_REFERENCE_EXT</tcaption></table>
 	<p>
-	  Node and Creation are as in 
-	  <seealso marker="#REFERENCE_EXT">REFERENCE_EXT</seealso>.
+	  <c>Node</c> and <c>Creation</c> are as in
+	  <seealso marker="#REFERENCE_EXT"><c>REFERENCE_EXT</c></seealso>.
 	</p>
 	<p>
-	  <c>ID</c> contains a sequence of big-endian unsigned integers 
-	  (4 bytes each, so <c>N'</c> is a multiple of 4), 
-	  but should be regarded as uninterpreted data.
+	  <c>ID</c> contains a sequence of big-endian unsigned integers
+	  (4 bytes each, so <c>N'</c> is a multiple of 4),
+	  but is to be regarded as uninterpreted data.
 	</p>
 	<p>
 	  <c>N'</c> = 4 * <c>Len</c>.
 	</p>
 	<p>
-	  In the first word (four bytes) of <c>ID</c>, only 18 bits are 
-	  significant, the rest should be 0.
-	  In <c>Creation</c>, only 2 bits are significant, 
-	  the rest should be 0.
+	  In the first word (4 bytes) of <c>ID</c>, only 18 bits are
+	  significant, the rest are to be 0.
+	  In <c>Creation</c>, only two bits are significant,
+	  the rest are to be 0.
 	</p>
 	<p>
-	  NEW_REFERENCE_EXT was introduced with distribution version 4.
-	  In version 4, <c>N'</c> should be at most 12.
+	  <c>NEW_REFERENCE_EXT</c> was introduced with distribution version 4.
+	  In version 4, <c>N'</c> is to be at most 12.
 	</p>
 	<p>
-	  See <seealso marker="#REFERENCE_EXT">REFERENCE_EXT</seealso>).
+	  See <seealso marker="#REFERENCE_EXT"><c>REFERENCE_EXT</c></seealso>.
 	</p>
     </section>
 
     <section>
       <marker id="SMALL_ATOM_EXT"/>
       <title>SMALL_ATOM_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -816,24 +790,28 @@
 	    <cell align="center"><c>Len</c></cell>
 	    <cell align="center"><c>AtomName</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>SMALL_ATOM_EXT</tcaption></table>
       <p>
-	An atom is stored with a 1 byte unsigned length, 
-	followed by <c>Len</c> numbers of 8 bit Latin1 characters that
+	An atom is stored with a 1 byte unsigned length,
+	followed by <c>Len</c> numbers of 8-bit Latin-1 characters that
 	forms the <c>AtomName</c>. Longer atoms can be represented
-	by <seealso marker="#ATOM_EXT">ATOM_EXT</seealso>. <em>Note</em>
-	the <c>SMALL_ATOM_EXT</c> was introduced in erts version 5.7.2 and
-	require an exchange of the
-	<seealso marker="erl_dist_protocol#dflags"><c>DFLAG_SMALL_ATOM_TAGS</c></seealso>
-	distribution flag in the
-	<seealso marker="erl_dist_protocol#distribution_handshake">distribution handshake</seealso>.
+	by <seealso marker="#ATOM_EXT"><c>ATOM_EXT</c></seealso>.
       </p>
+      <note>
+	<p>
+	  <c>SMALL_ATOM_EXT</c> was introduced in <c>ERTS</c> 5.7.2 and
+	  require an exchange of distribution flag
+	  <seealso marker="erl_dist_protocol#dflags">
+	  <c>DFLAG_SMALL_ATOM_TAGS</c></seealso> in the
+	  <seealso marker="erl_dist_protocol#distribution_handshake">
+	  distribution handshake</seealso>.
+	</p>
+      </note>
     </section>
 
     <section>
       <marker id="FUN_EXT"/>
       <title>FUN_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -845,48 +823,56 @@
 	    <cell align="center">N5</cell>
 	  </row>
 	  <row>
-	    <cell align="center">117</cell>
-	    <cell align="center">NumFree</cell>
-	    <cell align="center">Pid</cell>
-	    <cell align="center">Module</cell>
-	    <cell align="center">Index</cell>
-	    <cell align="center">Uniq</cell>
-	    <cell align="center">Free vars ...</cell>
+	    <cell align="center"><c>117</c></cell>
+	    <cell align="center"><c>NumFree</c></cell>
+	    <cell align="center"><c>Pid</c></cell>
+	    <cell align="center"><c>Module</c></cell>
+	    <cell align="center"><c>Index</c></cell>
+	    <cell align="center"><c>Uniq</c></cell>
+	    <cell align="center"><c>Free vars ...</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>FUN_EXT</tcaption></table>
 	<taglist>
-	  <tag><c>Pid</c></tag> 
+	  <tag><c>Pid</c></tag>
 	  <item>
-	    is a process identifier as in 
-	    <seealso marker="#PID_EXT">PID_EXT</seealso>. 
-	    It represents the process in which the fun was created.
+	    <p>A process identifier as in
+	      <seealso marker="#PID_EXT"><c>PID_EXT</c></seealso>.
+	      Represents the process in which the fun was created.
+	    </p>
 	  </item>
 	<tag><c>Module</c></tag>
 	<item>
-	  is an encoded as an atom, using 
-	  <seealso marker="#ATOM_EXT">ATOM_EXT</seealso>, 
-	  <seealso marker="#SMALL_ATOM_EXT">SMALL_ATOM_EXT</seealso>
-	  or <seealso marker="#ATOM_CACHE_REF">ATOM_CACHE_REF</seealso>.
-	  This is the module that the fun is implemented in.
+	  <p>Encoded as an atom, using
+	    <seealso marker="#ATOM_EXT"><c>ATOM_EXT</c></seealso>,
+	    <seealso marker="#SMALL_ATOM_EXT"><c>SMALL_ATOM_EXT</c></seealso>,
+	    or <seealso marker="#ATOM_CACHE_REF">
+	    <c>ATOM_CACHE_REF</c></seealso>.
+	    This is the module that the fun is implemented in.
+	  </p>
 	</item>
 	<tag><c>Index</c></tag>
 	<item>
-	  is an integer encoded using 
-	  <seealso marker="#SMALL_INTEGER_EXT">SMALL_INTEGER_EXT</seealso> 
-	  or <seealso marker="#INTEGER_EXT">INTEGER_EXT</seealso>.
-	  It is typically a small index into the module's fun table.
+	  <p>An integer encoded using
+	    <seealso marker="#SMALL_INTEGER_EXT">
+	    <c>SMALL_INTEGER_EXT</c></seealso> 
+	    or <seealso marker="#INTEGER_EXT"><c>INTEGER_EXT</c></seealso>.
+	    It is typically a small index into the module's fun table.
+	  </p>
 	</item>
 	<tag><c>Uniq</c></tag>
 	<item>
-	  is an integer encoded using 
-	  <seealso marker="#SMALL_INTEGER_EXT">SMALL_INTEGER_EXT</seealso> or 
-	  <seealso marker="#INTEGER_EXT">INTEGER_EXT</seealso>.
-	  <c>Uniq</c> is the hash value of the parse for the fun.
+	  <p>An integer encoded using
+	    <seealso marker="#SMALL_INTEGER_EXT">
+	    <c>SMALL_INTEGER_EXT</c></seealso> or 
+	    <seealso marker="#INTEGER_EXT"><c>INTEGER_EXT</c></seealso>.
+	    <c>Uniq</c> is the hash value of the parse for the fun.
+	  </p>
 	</item>
 	<tag><c>Free vars</c></tag>
 	<item>
-	  is <c>NumFree</c> number of terms, each one encoded according 
-	  to its type.
+	  <p><c>NumFree</c> number of terms, each one encoded according
+	    to its type.
+	  </p>
 	</item>
 	</taglist>
     </section>
@@ -894,7 +880,6 @@
     <section>
       <marker id="NEW_FUN_EXT"/>
       <title>NEW_FUN_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -910,19 +895,19 @@
 	    <cell align="center">N5</cell>
 	  </row>
 	  <row>
-	    <cell align="center">112</cell>
-	    <cell align="center">Size</cell>
-	    <cell align="center">Arity</cell>
-	    <cell align="center">Uniq</cell>
-	    <cell align="center">Index</cell>
-	    <cell align="center">NumFree</cell>
-	    <cell align="center">Module</cell>
-	    <cell align="center">OldIndex</cell>
-	    <cell align="center">OldUniq</cell>
-	    <cell align="center">Pid</cell>
-	    <cell align="center">Free Vars</cell>
+	    <cell align="center"><c>112</c></cell>
+	    <cell align="center"><c>Size</c></cell>
+	    <cell align="center"><c>Arity</c></cell>
+	    <cell align="center"><c>Uniq</c></cell>
+	    <cell align="center"><c>Index</c></cell>
+	    <cell align="center"><c>NumFree</c></cell>
+	    <cell align="center"><c>Module</c></cell>
+	    <cell align="center"><c>OldIndex</c></cell>
+	    <cell align="center"><c>OldUniq</c></cell>
+	    <cell align="center"><c>Pid</c></cell>
+	    <cell align="center"><c>Free Vars</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>NEW_FUN_EXT</tcaption></table>
 	<p>
 	  This is the new encoding of internal funs: <c>fun F/A</c> and
 	  <c>fun(Arg1,..) -> ... end</c>.
@@ -930,68 +915,73 @@
 	<taglist>
 	  <tag><c>Size</c></tag> 
 	  <item>
-	    is the total number of bytes, including the <c>Size</c> field.
+	    <p>The total number of bytes, including field <c>Size</c>.</p>
 	  </item>
 	  <tag><c>Arity</c></tag> 
 	  <item>
-	    is the arity of the function implementing the fun.
+	    <p>The arity of the function implementing the fun.</p>
 	  </item>
 	  <tag><c>Uniq</c></tag>
 	  <item>
-	    is the 16 bytes MD5 of the significant parts of the Beam file.
+	    <p>The 16 bytes MD5 of the significant parts of the Beam file.</p>
 	  </item>
 	  <tag><c>Index</c></tag> 
 	  <item>
-	    is an index number. Each fun within a module has an unique
-	    index. <c>Index</c> is stored in big-endian byte order.
+	    <p>An index number. Each fun within a module has an unique
+	      index. <c>Index</c> is stored in big-endian byte order.
+	    </p>
 	  </item>
 	  <tag><c>NumFree</c></tag> 
 	  <item>
-	    is the number of free variables.
+	    <p>The number of free variables.</p>
 	  </item>
 	  <tag><c>Module</c></tag>
 	  <item>
-	    is an encoded as an atom, using 
-	    <seealso marker="#ATOM_EXT">ATOM_EXT</seealso>, 
-	    <seealso marker="#SMALL_ATOM_EXT">SMALL_ATOM_EXT</seealso> or
-	    <seealso marker="#ATOM_CACHE_REF">ATOM_CACHE_REF</seealso>. 
-	    This is the module that the fun is implemented in.
+	    <p>Encoded as an atom, using
+	      <seealso marker="#ATOM_EXT"><c>ATOM_EXT</c></seealso>, 
+	      <seealso marker="#SMALL_ATOM_EXT"><c>SMALL_ATOM_EXT</c></seealso>,
+	      or <seealso marker="#ATOM_CACHE_REF">
+	      <c>ATOM_CACHE_REF</c></seealso>. 
+	      Is the module that the fun is implemented in.
+	    </p>
 	  </item>
 	  <tag><c>OldIndex</c></tag>
 	  <item>
-	    is an integer encoded using 
-	    <seealso marker="#SMALL_INTEGER_EXT">SMALL_INTEGER_EXT</seealso> 
-	    or <seealso marker="#INTEGER_EXT">INTEGER_EXT</seealso>.
-	    It is typically a small index into the module's fun table.
+	    <p>An integer encoded using
+	      <seealso marker="#SMALL_INTEGER_EXT">
+	      <c>SMALL_INTEGER_EXT</c></seealso> or
+	      <seealso marker="#INTEGER_EXT"><c>INTEGER_EXT</c></seealso>.
+	      Is typically a small index into the module's fun table.
+	    </p>
 	  </item>
 	  <tag><c>OldUniq</c></tag>
 	  <item>
-	    is an integer encoded using 
-	    <seealso marker="#SMALL_INTEGER_EXT">SMALL_INTEGER_EXT</seealso> 
-	    or 
-	    <seealso marker="#INTEGER_EXT">INTEGER_EXT</seealso>.
-	    <c>Uniq</c> is the hash value of the parse tree for the fun.
+	    <p>An integer encoded using
+	      <seealso marker="#SMALL_INTEGER_EXT">
+	      <c>SMALL_INTEGER_EXT</c></seealso> or 
+	      <seealso marker="#INTEGER_EXT"><c>INTEGER_EXT</c></seealso>.
+	      <c>Uniq</c> is the hash value of the parse tree for the fun.
+	    </p>
 	  </item>
 	  <tag><c>Pid</c></tag>
 	  <item>
-	    is a process identifier as in 
-	    <seealso marker="#PID_EXT">PID_EXT</seealso>. 
-	    It represents the process in which
-	    the fun was created.
+	    <p>A process identifier as in
+	      <seealso marker="#PID_EXT"><c>PID_EXT</c></seealso>.
+	      Represents the process in which the fun was created.
+	    </p>
 	  </item>
-
 	  <tag><c>Free vars</c></tag>
 	  <item>
-	    is <c>NumFree</c> number of terms, each one encoded according 
-	    to its type.
+	    <p><c>NumFree</c> number of terms, each one encoded according
+	      to its type.
+	    </p>
 	  </item>
 	</taglist>
     </section>
 
     <section>
       <marker id="EXPORT_EXT"/>
-      <title>EXPORT_EXT</title>
-	
+      <title>EXPORT_EXT</title>	
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -1000,32 +990,31 @@
 	    <cell align="center">N3</cell>
 	  </row>
 	  <row>
-	    <cell align="center">113</cell>
-	    <cell align="center">Module</cell>
-	    <cell align="center">Function</cell>
-	    <cell align="center">Arity</cell>
+	    <cell align="center"><c>113</c></cell>
+	    <cell align="center"><c>Module</c></cell>
+	    <cell align="center"><c>Function</c></cell>
+	    <cell align="center"><c>Arity</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>EXPORT_EXT</tcaption></table>
 	<p>
 	  This term is the encoding for external funs: <c>fun M:F/A</c>.
 	</p>
 	<p>
-	  <c>Module</c> and <c>Function</c> are atoms 
-	  (encoded using <seealso marker="#ATOM_EXT">ATOM_EXT</seealso>, 
-	  <seealso marker="#SMALL_ATOM_EXT">SMALL_ATOM_EXT</seealso> or 
-	  <seealso marker="#ATOM_CACHE_REF">ATOM_CACHE_REF</seealso>).
+	  <c>Module</c> and <c>Function</c> are atoms
+	  (encoded using <seealso marker="#ATOM_EXT"><c>ATOM_EXT</c></seealso>, 
+	  <seealso marker="#SMALL_ATOM_EXT"><c>SMALL_ATOM_EXT</c></seealso>, or
+	  <seealso marker="#ATOM_CACHE_REF"><c>ATOM_CACHE_REF</c></seealso>).
 	</p>
 	<p>
-	  <c>Arity</c> is an integer encoded using 
-	  <seealso marker="#SMALL_INTEGER_EXT">SMALL_INTEGER_EXT</seealso>.
+	  <c>Arity</c> is an integer encoded using
+	  <seealso marker="#SMALL_INTEGER_EXT">
+	  <c>SMALL_INTEGER_EXT</c></seealso>.
 	</p>
-
     </section>
 
     <section>
       <marker id="BIT_BINARY_EXT"/>
       <title>BIT_BINARY_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -1034,39 +1023,35 @@
 	    <cell align="center">Len</cell>
 	  </row>
 	  <row>
-	    <cell align="center">77</cell>
-	    <cell align="center">Len</cell>
-	    <cell align="center">Bits</cell>
-	    <cell align="center">Data</cell>
+	    <cell align="center"><c>77</c></cell>
+	    <cell align="center"><c>Len</c></cell>
+	    <cell align="center"><c>Bits</c></cell>
+	    <cell align="center"><c>Data</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>BIT_BINARY_EXT</tcaption></table>
 	<p>
 	  This term represents a bitstring whose length in bits does
 	  not have to be a multiple of 8.
-	  The <c>Len</c> field is an unsigned 4 byte integer (big endian).
+	  The <c>Len</c> field is an unsigned 4 byte integer (big-endian).
 	  The <c>Bits</c> field is the number of bits (1-8) that are used
-	  in the last byte in the data field, 
-	  counting from the most significant bit towards the least
-	  significant.
+	  in the last byte in the data field,
+	  counting from the most significant bit to the least significant.
 	</p>
-
-
     </section>
 
     <section>
       <marker id="NEW_FLOAT_EXT"/>
       <title>NEW_FLOAT_EXT</title>
-	
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
 	    <cell align="center">8</cell>
 	  </row>
 	  <row>
-	    <cell align="center">70</cell>
-	    <cell align="center">IEEE float</cell>
+	    <cell align="center"><c>70</c></cell>
+	    <cell align="center"><c>IEEE float</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>NEW_FLOAT_EXT</tcaption></table>
 	<p>
 	  A float is stored as 8 bytes in big-endian IEEE format.
 	</p>
@@ -1074,10 +1059,10 @@
 	  This term is used in minor version 1 of the external format.
 	</p>
     </section>
+
     <section>
       <marker id="ATOM_UTF8_EXT"/>
       <title>ATOM_UTF8_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -1089,23 +1074,22 @@
 	    <cell align="center"><c>Len</c></cell>
 	    <cell align="center"><c>AtomName</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>ATOM_UTF8_EXT</tcaption></table>
       <p>
 	An atom is stored with a 2 byte unsigned length in big-endian order,
 	followed by <c>Len</c> bytes containing the <c>AtomName</c> encoded
 	in UTF-8.
       </p>
       <p>
-	For more information on encoding of atoms, see
+	For more information on encoding of atoms, see the
 	<seealso marker="#utf8_atoms">note on UTF-8 encoded atoms</seealso>
-	in the beginning of this document.
+	in the beginning of this section.
       </p>
     </section>
 
     <section>
       <marker id="SMALL_ATOM_UTF8_EXT"/>
       <title>SMALL_ATOM_UTF8_EXT</title>
-
 	<table align="left">
 	  <row>
 	    <cell align="center">1</cell>
@@ -1117,20 +1101,19 @@
 	    <cell align="center"><c>Len</c></cell>
 	    <cell align="center"><c>AtomName</c></cell>
 	  </row>
-	<tcaption></tcaption></table>
+	<tcaption>SMALL_ATOM_UTF8_EXT</tcaption></table>
       <p>
-	An atom is stored with a 1 byte unsigned length, 
+	An atom is stored with a 1 byte unsigned length,
 	followed by <c>Len</c> bytes containing the <c>AtomName</c> encoded
 	in UTF-8. Longer atoms encoded in UTF-8 can be represented using
-	<seealso marker="#ATOM_UTF8_EXT">ATOM_UTF8_EXT</seealso>.
+	<seealso marker="#ATOM_UTF8_EXT"><c>ATOM_UTF8_EXT</c></seealso>.
       </p>
       <p>
-	For more information on encoding of atoms, see
+	For more information on encoding of atoms, see the
 	<seealso marker="#utf8_atoms">note on UTF-8 encoded atoms</seealso>
-	in the beginning of this document.
+	in the beginning of this section.
       </p>
     </section>
-
   </chapter>
-  
+
 
diff --git a/erts/doc/src/erl_nif.xml b/erts/doc/src/erl_nif.xml
index 8ed042f6f9..d154a1bd21 100644
--- a/erts/doc/src/erl_nif.xml
+++ b/erts/doc/src/erl_nif.xml
@@ -33,43 +33,52 @@
     <file>erl_nif.xml</file>
   </header>
   <lib>erl_nif</lib>
-  <libsummary>API functions for an Erlang NIF library</libsummary>
+  <libsummary>API functions for an Erlang NIF library.</libsummary>
   <description>
     <p>A NIF library contains native implementation of some functions
-    of an Erlang module. The native implemented functions (NIFs) are
-    called like any other functions without any difference to the
-    caller. Each NIF must also have an implementation in Erlang that
-    will be invoked if the function is called before the NIF library
-    has been successfully loaded. A typical such stub implementation
-    is to throw an exception. But it can also be used as a fallback
-    implementation if the NIF library is not implemented for some
-    architecture.</p>     
-    <marker id="WARNING"/>
-      <warning><p><em>Use this functionality with extreme care!</em></p>
+      of an Erlang module. The native implemented functions (NIFs) are
+      called like any other functions without any difference to the
+      caller. Each NIF must have an implementation in Erlang that
+      is invoked if the function is called before the NIF library
+      is successfully loaded. A typical such stub implementation
+      is to throw an exception. But it can also be used as a fallback
+      implementation if the NIF library is not implemented for some
+      architecture.</p>
+
+    <warning>
+      <marker id="WARNING"/>
+      <p><em>Use this functionality with extreme care.</em></p>
       <p>A native function is executed as a direct extension of the
-      native code of the VM. Execution is not made in a safe environment.
-      The VM can <em>not</em> provide the same services as provided when
-      executing Erlang code, such as preemptive scheduling or memory
-      protection. If the native function doesn't behave well, the whole
-      VM will misbehave.</p>
-      <list>
-	<item><p>A native function that crash will crash the whole VM.</p></item>
-	<item><p>An erroneously implemented native function might cause
-	a VM internal state inconsistency which may cause a crash of the VM,
-	or miscellaneous misbehaviors of the VM at any point after the call
-	to the native function.</p></item>
-	<item><p>A native function that do <seealso marker="#lengthy_work">lengthy
-	work</seealso> before returning will degrade responsiveness of the VM,
-	and may cause miscellaneous strange behaviors. Such strange behaviors
-	include, but are not limited to, extreme memory usage, and bad load
-	balancing between schedulers. Strange behaviors that might occur due
-	to lengthy work may also vary between OTP releases.</p></item>
+        native code of the VM. Execution is not made in a safe environment.
+        The VM <em>cannot</em> provide the same services as provided when
+        executing Erlang code, such as pre-emptive scheduling or memory
+        protection. If the native function does not behave well, the whole
+        VM will misbehave.</p>
+      <list type="bulleted">
+        <item>
+          <p>A native function that crash will crash the whole VM.</p>
+        </item>
+        <item>
+          <p>An erroneously implemented native function can cause a VM
+            internal state inconsistency, which can cause a crash of the VM,
+            or miscellaneous misbehaviors of the VM at any point after the
+            call to the native function.</p>
+        </item>
+        <item>
+          <p>A native function doing <seealso marker="#lengthy_work">lengthy
+            work</seealso> before returning degrades responsiveness of the VM,
+            and can cause miscellaneous strange behaviors. Such strange
+            behaviors include, but are not limited to, extreme memory usage,
+            and bad load balancing between schedulers. Strange behaviors that
+            can occur because of lengthy work can also vary between Erlang/OTP
+            releases.</p>
+        </item>
       </list>
-      </warning>
+    </warning>
+
+    <p>A minimal example of a NIF library can look as follows:</p>
 
-    <p>A minimal example of a NIF library can look like this:</p>
-      <p/>
-      <code type="none">
+    <code type="none">
 /* niftest.c */
 #include "erl_nif.h"
 
@@ -83,13 +92,11 @@ static ErlNifFunc nif_funcs[] =
     {"hello", 0, hello}
 };
 
-ERL_NIF_INIT(niftest,nif_funcs,NULL,NULL,NULL,NULL)
-</code>
+ERL_NIF_INIT(niftest,nif_funcs,NULL,NULL,NULL,NULL)</code>
 
-    <p>and the Erlang module would have to look something like
-    this:</p>
-      <p/>
-      <code type="none">
+    <p>The Erlang module can look as follows:</p>
+
+    <code type="none">
 -module(niftest).
 
 -export([init/0, hello/0]).
@@ -98,11 +105,11 @@ init() ->
       erlang:load_nif("./niftest", 0).
 
 hello() ->
-      "NIF library not loaded".
-</code>
-    <p>and compile and test something like this (on Linux):</p>
-      <p/>
-      <code type="none">
+      "NIF library not loaded".</code>
+
+    <p>Compile and test can look as follows (on Linux):</p>
+
+    <code type="none">
 $> gcc -fPIC -shared -o niftest.so niftest.c -I $ERL_ROOT/usr/include/
 $> erl
 
@@ -113,290 +120,310 @@ $> erl
 3> niftest:init().
 ok
 4> niftest:hello().
-"Hello world!"
-</code>
-
-     <p>A better solution for a real module is to take advantage of
-     the new directive <seealso
-     marker="doc/reference_manual:code_loading#on_load">on_load</seealso> to automatically
-     load the NIF library when the module is loaded.</p>
-     <note><p>A NIF does not have to be exported, it can be local to the module.
-     Note however that unused local stub functions will be optimized
-     away by the compiler causing loading of the NIF library to fail.</p>
+"Hello world!"</code>
+
+    <p>A better solution for a real module is to take advantage of the new
+      directive <c>on load</c> (see section
+      <seealso marker="doc/reference_manual:code_loading#on_load">Running a
+      Function When a Module is Loaded</seealso> in the Erlang Reference
+      Manual) to load the NIF library automatically when the module is
+      loaded.</p>
+
+    <note>
+      <p>A NIF does not have to be exported, it can be local to the module.
+        However, unused local stub functions will be optimized
+        away by the compiler, causing loading of the NIF library to fail.</p>
     </note>
 
-     <p>A loaded NIF library is tied to the Erlang module code version
-     that loaded it. If the module is upgraded with a new version, the
-     new Erlang code will have to load its own NIF library (or maybe choose not
-     to). The new code version can however choose to load the exact
-     same NIF library as the old code if it wants to. Sharing the same
-     dynamic library will mean that static data defined by the library
-     will be shared as well. To avoid unintentionally shared static
-     data, each Erlang module code can keep its own private data. This
-     private data can be set when the NIF library is loaded and
-     then retrieved by calling <seealso marker="#enif_priv_data">enif_priv_data</seealso>.</p>
-    <p>There is no way to explicitly unload a NIF library. A library will be
-     automatically unloaded when the module code that it belongs to is purged
-     by the code server.</p>
-
+    <p>A loaded NIF library is tied to the Erlang module code version
+      that loaded it. If the module is upgraded with a new version, the
+      new Erlang code need to load its own NIF library (or maybe choose not
+      to). The new code version can, however, choose to load the
+      same NIF library as the old code if it wants to. Sharing the
+      dynamic library means that static data defined by the library
+      is shared as well. To avoid unintentionally shared static
+      data, each Erlang module code can keep its own private data. This
+      private data can be set when the NIF library is loaded and
+      then retrieved by calling <seealso marker="#enif_priv_data">
+      <c>enif_priv_data</c></seealso>.</p>
+
+    <p>A NIF library cannot be loaded explicitly. A library is
+      automatically unloaded when the module code that it belongs to is purged
+      by the code server.</p>
   </description>
+
   <section>
-  <title>FUNCTIONALITY</title>
-  <p>All functions that a NIF library needs to do with Erlang are
-      performed through the NIF API functions. There are functions
+  <title>Functionality</title>
+    <p>All functions that a NIF library needs to do with Erlang are
+      performed through the NIF API functions. Functions exist
       for the following functionality:</p>
+
     <taglist>
       <tag>Read and write Erlang terms</tag>
-      <item><p>Any Erlang terms can be passed to a NIF as function arguments and
-      be returned as function return values. The terms are of C-type
-      <seealso marker="#ERL_NIF_TERM">ERL_NIF_TERM</seealso>
-      and can only be read or written using API functions. Most functions to read
-      the content of a term are prefixed <c>enif_get_</c> and usually return
-      true (or false) if the term was of the expected type (or not).    
-      The functions to write terms are all prefixed <c>enif_make_</c> and usually
-      return the created <c>ERL_NIF_TERM</c>. There are also some functions
-      to query terms, like <c>enif_is_atom</c>, <c>enif_is_identical</c> and
-      <c>enif_compare</c>.</p>
-      <p>All terms of type <c>ERL_NIF_TERM</c> belong to an environment of type
-      <seealso marker="#ErlNifEnv">ErlNifEnv</seealso>. The lifetime of a term is
-      controlled by the lifetime of its environment object. All API functions that read
-      or write terms has the environment, that the term belongs to, as the first
-      function argument.</p></item>
+      <item>
+        <p>Any Erlang terms can be passed to a NIF as function arguments and
+          be returned as function return values. The terms are of C-type
+          <seealso marker="#ERL_NIF_TERM"><c>ERL_NIF_TERM</c></seealso> and can
+          only be read or written using API functions. Most functions to read
+          the content of a term are prefixed <c>enif_get_</c> and usually return
+          <c>true</c> (or <c>false</c>) if the term is of the expected type (or
+          not). The functions to write terms are all prefixed <c>enif_make_</c>
+          and usually
+          return the created <c>ERL_NIF_TERM</c>. There are also some functions
+          to query terms, like <c>enif_is_atom</c>, <c>enif_is_identical</c>,
+          and <c>enif_compare</c>.</p>
+        <p>All terms of type <c>ERL_NIF_TERM</c> belong to an environment of
+          type <seealso marker="#ErlNifEnv"><c>ErlNifEnv</c></seealso>. The
+          lifetime of a term is controlled by the lifetime of its environment
+          object. All API functions that read or write terms has the
+          environment that the term belongs to as the first function
+          argument.</p>
+      </item>
       <tag>Binaries</tag>
-      <item><p>Terms of type binary are accessed with the help of the struct type
-      <seealso marker="#ErlNifBinary">ErlNifBinary</seealso>    
-      that contains a pointer (<c>data</c>) to the raw binary data and the length
-      (<c>size</c>) of the data in bytes. Both <c>data</c> and <c>size</c> are
-      read-only and should only be written using calls to API functions.
-      Instances of <c>ErlNifBinary</c> are however always allocated by the user
-      (usually as local variables).</p>
-      <p>The raw data pointed to by <c>data</c> is only mutable after a call to
-      <seealso marker="#enif_alloc_binary">enif_alloc_binary</seealso> or
-      <seealso marker="#enif_realloc_binary">enif_realloc_binary</seealso>.
-      All other functions that operates on a binary will leave the data as read-only.
-      A mutable binary must in the end either be freed with
-      <seealso marker="#enif_release_binary">enif_release_binary</seealso>
-      or made read-only by transferring it to an Erlang term with
-      <seealso marker="#enif_make_binary">enif_make_binary</seealso>.
-      But it does not have to happen in the same NIF call. Read-only binaries
-      do not have to be released.</p>
-      <p><seealso marker="#enif_make_new_binary">enif_make_new_binary</seealso>
-      can be used as a shortcut to allocate and return a binary in the same NIF call.</p>
-      <p>Binaries are sequences of whole bytes. Bitstrings with an arbitrary
-      bit length have no support yet.</p>
-       </item>
+      <item>
+        <p>Terms of type binary are accessed with the help of struct type
+          <seealso marker="#ErlNifBinary"><c>ErlNifBinary</c></seealso>,
+          which contains a pointer (<c>data</c>) to the raw binary data and the
+          length (<c>size</c>) of the data in bytes. Both <c>data</c> and
+          <c>size</c> are read-only and are only to be written using calls to
+          API functions. Instances of <c>ErlNifBinary</c> are, however, always
+          allocated by the user (usually as local variables).</p>
+        <p>The raw data pointed to by <c>data</c> is only mutable after a call
+          to <seealso marker="#enif_alloc_binary">
+          <c>enif_alloc_binary</c></seealso> or
+          <seealso marker="#enif_realloc_binary">
+          <c>enif_realloc_binary</c></seealso>. All other functions that
+          operate on a binary leave the data as read-only.
+          A mutable binary must in the end either be freed with
+          <seealso marker="#enif_release_binary">
+          <c>enif_release_binary</c></seealso>
+          or made read-only by transferring it to an Erlang term with
+          <seealso marker="#enif_make_binary"><c>enif_make_binary</c></seealso>.
+          However, it does not have to occur in the same NIF call. Read-only
+          binaries do not have to be released.</p>
+        <p><seealso marker="#enif_make_new_binary">
+          <c>enif_make_new_binary</c></seealso> can be used as a shortcut to
+          allocate and return a binary in the same NIF call.</p>
+        <p>Binaries are sequences of whole bytes. Bitstrings with an arbitrary
+          bit length have no support yet.</p>
+      </item>
       <tag>Resource objects</tag>
-      <item><p>The use of resource objects is a safe way to return pointers to
-      native data structures from a NIF. A resource object is
-      just a block of memory allocated with
-      <seealso marker="#enif_alloc_resource">enif_alloc_resource</seealso>.
-      A handle ("safe pointer") to this memory block can then be returned to Erlang by the use of
-      <seealso marker="#enif_make_resource">enif_make_resource</seealso>.
-      The term returned by <c>enif_make_resource</c>
-      is totally opaque in nature. It can be stored and passed between processes
-      on the same node, but the only real end usage is to pass it back as an argument to a NIF.
-      The NIF can then call <seealso marker="#enif_get_resource">enif_get_resource</seealso>
-      and get back a pointer to the memory block that is guaranteed to still be
-      valid. A resource object will not be deallocated until the last handle term
-      has been garbage collected by the VM and the resource has been
-      released with <seealso marker="#enif_release_resource">enif_release_resource</seealso>
-      (not necessarily in that order).</p>      
-      <p>All resource objects are created as instances of some <em>resource type</em>.
-      This makes resources from different modules to be distinguishable. 
-      A resource type is created by calling
-      <seealso marker="#enif_open_resource_type">enif_open_resource_type</seealso>
-      when a library is loaded. Objects of that resource type can then later be allocated
-      and <c>enif_get_resource</c> verifies that the resource is of the expected type.
-      A resource type can have a user supplied destructor function that is
-      automatically called when resources of that type are released (by either
-      the garbage collector or <c>enif_release_resource</c>). Resource types
-      are uniquely identified by a supplied name string and the name of the
-      implementing module.</p>
-      <marker id="enif_resource_example"/><p>Here is a template example of how to create and return a resource object.</p>
-      <p/>
-      <code type="none">
-    ERL_NIF_TERM term;
-    MyStruct* obj = enif_alloc_resource(my_resource_type, sizeof(MyStruct));
-
-    /* initialize struct ... */
-
-    term = enif_make_resource(env, obj);
-
-    if (keep_a_reference_of_our_own) {
-        /* store 'obj' in static variable, private data or other resource object */
-    }
-    else {
-        enif_release_resource(obj);
-        /* resource now only owned by "Erlang" */
-    }
-    return term;
-    </code>
-      <p>Note that once <c>enif_make_resource</c> creates the term to
-      return to Erlang, the code can choose to either keep its own
-      native pointer to the allocated struct and release it later, or
-      release it immediately and rely solely on the garbage collector
-      to eventually deallocate the resource object when it collects
-      the term.</p> 
-      <p>Another usage of resource objects is to create binary terms with
-      user defined memory management.
-      <seealso marker="#enif_make_resource_binary">enif_make_resource_binary</seealso>
-      will create a binary term that is connected to a resource object. The
-      destructor of the resource will be called when the binary is garbage
-      collected, at which time the binary data can be released. An example of
-      this can be a binary term consisting of data from a <c>mmap</c>'ed file.
-      The destructor can then do <c>munmap</c> to release the memory
-      region.</p>
-      <p>Resource types support upgrade in runtime by allowing a loaded NIF
-      library to takeover an already existing resource type and thereby
-      "inherit" all existing objects of that type. The destructor of the new
-      library will thereafter be called for the inherited objects and the
-      library with the old destructor function can be safely unloaded. Existing
-      resource objects, of a module that is upgraded, must either be deleted
-      or taken over by the new NIF library. The unloading of a library will be
-      postponed as long as there exist resource objects with a destructor
-      function in the library.
-      </p>
+      <item>
+        <p>The use of resource objects is a safe way to return pointers to
+          native data structures from a NIF. A resource object is
+          only a block of memory allocated with
+          <seealso marker="#enif_alloc_resource">
+          <c>enif_alloc_resource</c></seealso>.
+          A handle ("safe pointer") to this memory block can then be returned
+          to Erlang by the use of
+          <seealso marker="#enif_make_resource">
+          <c>enif_make_resource</c></seealso>.
+          The term returned by <c>enif_make_resource</c> is opaque in nature.
+          It can be stored and passed between processes on the same node, but
+          the only real end usage is to pass it back as an argument to a NIF.
+          The NIF can then call <seealso marker="#enif_get_resource">
+          <c>enif_get_resource</c></seealso> and get back a pointer to the
+          memory block, which is guaranteed to still be valid. A resource
+          object is not deallocated until the last handle term
+          is garbage collected by the VM and the resource is released with
+          <seealso marker="#enif_release_resource">
+          <c>enif_release_resource</c></seealso>
+          (not necessarily in that order).</p>
+        <p>All resource objects are created as instances of some <em>resource
+          type</em>. This makes resources from different modules to be
+          distinguishable. A resource type is created by calling
+          <seealso marker="#enif_open_resource_type">
+          <c>enif_open_resource_type</c></seealso> when a library is loaded.
+          Objects of that resource type can then later be allocated and
+          <c>enif_get_resource</c> verifies that the resource is of the
+          expected type. A resource type can have a user-supplied destructor
+          function, which is automatically called when resources of that type
+          are released (by either the garbage collector or
+          <c>enif_release_resource</c>). Resource types are uniquely identified
+          by a supplied name string and the name of the implementing module.</p>
+        <marker id="enif_resource_example"/>
+        <p>The following is a template example of how to create and return a
+          resource object.</p>
+        <code type="none">
+ERL_NIF_TERM term;
+MyStruct* obj = enif_alloc_resource(my_resource_type, sizeof(MyStruct));
+
+/* initialize struct ... */
+
+term = enif_make_resource(env, obj);
+
+if (keep_a_reference_of_our_own) {
+    /* store 'obj' in static variable, private data or other resource object */
+}
+else {
+    enif_release_resource(obj);
+    /* resource now only owned by "Erlang" */
+}
+return term;</code>
+        <p>Notice that once <c>enif_make_resource</c> creates the term to
+          return to Erlang, the code can choose to either keep its own
+          native pointer to the allocated struct and release it later, or
+          release it immediately and rely only on the garbage collector
+          to deallocate the resource object eventually when it collects
+          the term.</p> 
+        <p>Another use of resource objects is to create binary terms with
+          user-defined memory management.
+          <seealso marker="#enif_make_resource_binary">
+          <c>enif_make_resource_binary</c></seealso>
+          creates a binary term that is connected to a resource object. The
+          destructor of the resource is called when the binary is garbage
+          collected, at which time the binary data can be released. An example
+          of this can be a binary term consisting of data from a <c>mmap</c>'ed
+          file. The destructor can then do <c>munmap</c> to release the memory
+          region.</p>
+        <p>Resource types support upgrade in runtime by allowing a loaded NIF
+          library to take over an already existing resource type and by that
+          "inherit" all existing objects of that type. The destructor of the
+          new library is thereafter called for the inherited objects and the
+          library with the old destructor function can be safely unloaded.
+          Existing resource objects, of a module that is upgraded, must either
+          be deleted or taken over by the new NIF library. The unloading of a
+          library is postponed as long as there exist resource objects with a
+          destructor function in the library.</p>
       </item>
       <tag>Threads and concurrency</tag>
-      <item><p>A NIF is thread-safe without any explicit synchronization as
-      long as it acts as a pure function and only reads the supplied
-      arguments. As soon as you write towards a shared state either through
-      static variables or <seealso marker="#enif_priv_data">enif_priv_data</seealso>
-      you need to supply your own explicit synchronization. This includes terms
-      in process independent environments that are shared between threads.
-      Resource objects will also require synchronization if you treat them as
-      mutable.</p>
-      <p>The library initialization callbacks <c>load</c>, <c>reload</c> and
-      <c>upgrade</c> are all thread-safe even for shared state data.</p>
+      <item>
+        <p>A NIF is thread-safe without any explicit synchronization as
+          long as it acts as a pure function and only reads the supplied
+          arguments. When you write to a shared state either through
+          static variables or <seealso marker="#enif_priv_data">
+          <c>enif_priv_data</c></seealso>, you need to supply your own explicit
+          synchronization. This includes terms in process-independent
+          environments that are shared between threads. Resource objects also
+          require synchronization if you treat them as mutable.</p>
+        <p>The library initialization callbacks <c>load</c>, <c>reload</c>, and
+          <c>upgrade</c> are all thread-safe even for shared state data.</p>
       </item>
-
       <tag><marker id="version_management"/>Version Management</tag>
-      <item><p>
-      When a NIF library is built, information about NIF API version
-      is compiled into the library. When a NIF library is loaded the
-      runtime system verifies that the library is of a compatible version.
-      <c>erl_nif.h</c> defines <c>ERL_NIF_MAJOR_VERSION</c>, and
-      <c>ERL_NIF_MINOR_VERSION</c>. <c>ERL_NIF_MAJOR_VERSION</c> will be
-      incremented when NIF library incompatible changes are made to the
-      Erlang runtime system. Normally it will suffice to recompile the NIF
-      library when the <c>ERL_NIF_MAJOR_VERSION</c> has changed, but it
-      could, under rare circumstances, mean that NIF libraries have to
-      be slightly modified. If so, this will of course be documented.
-      <c>ERL_NIF_MINOR_VERSION</c> will be incremented when
-      new features are added. The runtime system uses the minor version
-      to determine what features to use.
-      </p><p>
-      The runtime system will normally refuse to load a NIF library if
-      the major versions differ, or if the major versions are equal and
-      the minor version used by the NIF library is greater than the one
-      used by the runtime system. Old NIF libraries with lower major
-      versions will however be allowed after a bump of the major version
-      during a transition period of two major releases. Such old NIF
-      libraries might however fail if deprecated features are used.
-      </p></item>
-
+      <item>
+        <p>When a NIF library is built, information about the NIF API version
+          is compiled into the library. When a NIF library is loaded, the
+          runtime system verifies that the library is of a compatible version.
+          <c>erl_nif.h</c> defines the following:</p>
+        <taglist>
+          <tag><c>ERL_NIF_MAJOR_VERSION</c></tag>
+          <item>
+            <p>Incremented when NIF library incompatible changes are made to the
+              Erlang runtime system. Normally it suffices to recompile the NIF
+              library when the <c>ERL_NIF_MAJOR_VERSION</c> has changed, but it
+              can, under rare circumstances, mean that NIF libraries must be
+              slightly modified. If so, this will of course be documented.</p>
+          </item>
+          <tag><c>ERL_NIF_MINOR_VERSION</c></tag>
+          <item>
+            <p>Incremented when new features are added. The runtime system uses
+              the minor version to determine what features to use.</p>
+          </item>
+        </taglist>
+        <p>The runtime system normally refuses to load a NIF library if
+          the major versions differ, or if the major versions are equal and
+          the minor version used by the NIF library is greater than the one
+          used by the runtime system. Old NIF libraries with lower major
+          versions are, however, allowed after a bump of the major version
+          during a transition period of two major releases. Such old NIF
+          libraries can however fail if deprecated features are used.</p>
+      </item>
       <tag><marker id="time_measurement"/>Time Measurement</tag>
-      <item><p>Support for time measurement in NIF libraries:</p>
-      <list>
-	<item><seealso marker="#ErlNifTime"><c>ErlNifTime</c></seealso></item>
-	<item><seealso marker="#ErlNifTimeUnit"><c>ErlNifTimeUnit</c></seealso></item>
-	<item><seealso marker="#enif_monotonic_time"><c>enif_monotonic_time()</c></seealso></item>
-	<item><seealso marker="#enif_time_offset"><c>enif_time_offset()</c></seealso></item>
-	<item><seealso marker="#enif_convert_time_unit"><c>enif_convert_time_unit()</c></seealso></item>
+      <item>
+        <p>Support for time measurement in NIF libraries:</p>
+        <list type="bulleted">
+          <item><seealso marker="#ErlNifTime">
+            <c>ErlNifTime</c></seealso></item>
+          <item><seealso marker="#ErlNifTimeUnit">
+            <c>ErlNifTimeUnit</c></seealso></item>
+          <item><seealso marker="#enif_monotonic_time">
+            <c>enif_monotonic_time()</c></seealso></item>
+          <item><seealso marker="#enif_time_offset">
+            <c>enif_time_offset()</c></seealso></item>
+          <item><seealso marker="#enif_convert_time_unit">
+            <c>enif_convert_time_unit()</c></seealso></item>
       </list>
       </item>
-
       <tag><marker id="lengthy_work"/>Long-running NIFs</tag>
-
-      <item><p>
-	As mentioned in the <seealso marker="#WARNING">warning</seealso> text at
-	the beginning of this document it is of <em>vital importance</em> that a 
-	native function return relatively quickly. It is hard to give an exact
-	maximum amount of time that a native function is allowed to work, but as a
-	rule of thumb a well-behaving native function should return to its caller
-	before a millisecond has passed. This can be achieved using different
-	approaches. If you have full control over the code to execute in the
-	native function, the best approach is to divide the work into multiple
-	chunks of work and call the native function multiple times. In some
-	cases this might however not always be possible, e.g. when calling
-	third-party libraries.</p>
-	
-	<p>The
-	<seealso marker="#enif_consume_timeslice">enif_consume_timeslice()</seealso>
-	function can be used to inform the runtime system about the length of the
-	NIF call. It should typically always be used unless the NIF executes very
-	quickly.</p>
-
-	<p>If the NIF call is too lengthy one needs to handle this in one of the
-	following ways in order to avoid degraded responsiveness, scheduler load
-	balancing problems, and other strange behaviors:</p>
-
-	<taglist>
-	  <tag>Yielding NIF</tag>
-	  <item>
-	    <p>
-	      If the functionality of a long-running NIF can be split so that
-	      its work can be achieved through a series of shorter NIF calls,
-	      the application can either make that series of NIF calls from the
-	      Erlang level, or it can call a NIF that first performs a chunk of
-	      the work, then invokes the
-	      <seealso marker="#enif_schedule_nif">enif_schedule_nif</seealso>
-	      function to schedule another NIF call to perform the next chunk.
-	      The final call scheduled in this manner can then return the
-	      overall result. Breaking up a long-running function in
-	      this manner enables the VM to regain control between calls to the
-	      NIFs.
-	    </p>
-	    <p>
-	      This approach is always preferred over the other alternatives
-	      described below. This both from a performance perspective and
-	      a system characteristics perspective.
-	    </p>
-	  </item>
-
-	  <tag>Threaded NIF</tag>
-	  <item>
-	    <p>
-	      This is accomplished by dispatching the work to another thread
-	      managed by the NIF library, return from the NIF, and wait for the
-	      result. The thread can send the result back to the Erlang
-	      process using <seealso marker="#enif_send">enif_send</seealso>.
-	      Information about thread primitives can be found below.
-	    </p>
-	  </item>
-
-	  <tag><marker id="dirty_nifs"/>Dirty NIF</tag>
-	  <item>
-
-	    <note>
-	      <p>
-		<em>The dirty NIF functionality described here
-		is experimental</em>. Dirty NIF support is available only when
-		the emulator is configured with dirty schedulers enabled. This
-		feature is currently disabled by default. The Erlang runtime
-		without SMP support do not support dirty schedulers even when
-		the dirty scheduler support has been enabled. To check at
-		runtime for the presence of dirty scheduler threads, code can
-		use the
-		<seealso marker="#enif_system_info"><c>enif_system_info()</c></seealso>
-		API function.
-	      </p>
-	    </note>
-
-	    <p>
-	      A NIF that cannot be split and cannot execute in a millisecond or
-	      less is called a "dirty NIF" because it performs work that the
-	      ordinary schedulers of the Erlang runtime system cannot handle cleanly.
-	      Applications that make use of such functions must indicate to the
-	      runtime that the functions are dirty so they can be handled
-	      specially. This is handled by executing dirty jobs on a separate
+      <item>
+        <p>As mentioned in the <seealso marker="#WARNING">warning</seealso> text
+          at the beginning of this manual page, it is of <em>vital
+          importance</em> that a native function returns relatively fast. It is
+          difficult to give an exact maximum amount of time that a native
+          function is allowed to work, but usually a well-behaving native
+          function is to return to its caller within 1 millisecond. This can be
+          achieved using different approaches. If you have full control over the
+          code to execute in the native function, the best approach is to
+          divide the work into multiple chunks of work and call the native
+          function multiple times. This is, however, not always possible, for
+          example when calling third-party libraries.</p>
+        <p>The <seealso marker="#enif_consume_timeslice">
+          <c>enif_consume_timeslice()</c></seealso> function can be used to
+          inform the runtime system about the length of the NIF call.
+          It is typically always to be used unless the NIF executes very
+          fast.</p>
+        <p>If the NIF call is too lengthy, this must be handled in one of
+          the following ways to avoid degraded responsiveness, scheduler load
+          balancing problems, and other strange behaviors:</p>
+        <taglist>
+          <tag>Yielding NIF</tag>
+          <item>
+            <p>If the functionality of a long-running NIF can be split so that
+              its work can be achieved through a series of shorter NIF calls,
+              the application has two options:</p>
+            <list type="bulleted">
+              <item>
+                <p>Make that series of NIF calls from the Erlang level.</p>
+              </item>
+              <item>
+                <p>Call a NIF that first performs a chunk of the work, then
+                  invokes the <seealso marker="#enif_schedule_nif">
+                  <c>enif_schedule_nif</c></seealso> function to schedule
+                  another NIF call to perform the next chunk. The final call
+                  scheduled in this manner can then return the overall
+                  result.</p>
+              </item>
+            </list>
+            <p>Breaking up a long-running function in this manner enables the
+              VM to regain control between calls to the NIFs.</p>
+            <p>This approach is always preferred over the other alternatives
+              described below. This both from a performance perspective and
+              a system characteristics perspective.</p>
+          </item>
+          <tag>Threaded NIF</tag>
+          <item>
+            <p>This is accomplished by dispatching the work to another thread
+              managed by the NIF library, return from the NIF, and wait for
+              the result. The thread can send the result back to the Erlang
+              process using <seealso marker="#enif_send">
+              <c>enif_send</c></seealso>.
+              Information about thread primitives is provided below.</p>
+          </item>
+          <tag><marker id="dirty_nifs"/>Dirty NIF</tag>
+          <item>
+            <note>
+              <p><em>The dirty NIF functionality described here
+                is experimental</em>. Dirty NIF support is available only when
+                the emulator is configured with dirty schedulers enabled. This
+                feature is disabled by default. The Erlang runtime
+                without SMP support does not support dirty schedulers even when
+                the dirty scheduler support is enabled. To check at runtime for
+                the presence of dirty scheduler threads, code can use the
+                <seealso marker="#enif_system_info">
+                <c>enif_system_info()</c></seealso> API function.</p>
+            </note>
+            <p>A NIF that cannot be split and cannot execute in a millisecond
+              or less is called a "dirty NIF", as it performs work that the
+              ordinary schedulers of the Erlang runtime system cannot handle cleanly.
+              Applications that make use of such functions must indicate to the
+              runtime that the functions are dirty so they can be handled 
+              specially. This is handled by executing dirty jobs on a separate
 	      set of schedulers called dirty schedulers. A dirty NIF executing
 	      on a dirty scheduler does not have the same duration restriction
 	      as a normal NIF.
-	    </p>
-
-	    <p>
-	      It is important to classify the dirty job correct. An I/O bound
+            </p>
+            <p>
+              It is important to classify the dirty job correct. An I/O bound
 	      job should be classified as such, and a CPU bound job should be
 	      classified as such. If you should classify CPU bound jobs
 	      as I/O bound jobs, dirty I/O schedulers might starve ordinary
@@ -404,1240 +431,1636 @@ ok
 	      for I/O, and/or spend a limited amount of time moving data.
             </p>
 
-	    <p>
-	      To schedule a dirty NIF for execution, the appropriate
-	      <c>flags</c> value can be set for the NIF in its
-	      <seealso marker="#ErlNifFunc"><c>ErlNifFunc</c></seealso>
-	      entry, or the application can call
-	      <seealso marker="#enif_schedule_nif"><c>enif_schedule_nif</c></seealso>,
-	      passing to it a pointer to the dirty NIF to be executed and
-	      indicating with the <c>flags</c> argument whether it expects the
-	      operation to be CPU-bound or I/O-bound. A job that alternates
-	      between I/O bound and CPU bound can be reclassified and
-	      rescheduled using <c>enif_schedule_nif</c> so that it executes on
-	      the correct type of dirty scheduler at all times. For more
-	      information see the documentation of the <c>erl</c> command line
-	      arguments <seealso marker="erl#+SDcpu"><c>+SDcpu</c></seealso>,
-	      and <seealso marker="erl#+SDio"><c>+SDio</c></seealso>.
-	    </p>
-
-	    <p>
-	      While a process is executing a dirty NIF some operations that
-	      communicate with it may take a very long time to complete.
-	      Suspend, or garbage collection of a process executing a dirty
-	      NIF cannot be done until the dirty NIF has returned, so other
-	      processes waiting for such operations to complete might have to
-	      wait for a very long time. Blocking multi scheduling, i.e.,
-	      calling
-	      <seealso marker="erlang#system_flag_multi_scheduling"><c>erlang:system_flag(multi_scheduling,
-	      block)</c></seealso>, might also take a very long time to
-	      complete. This since all ongoing dirty operations on all
-	      dirty schedulers need to complete before the block
-	      operation can complete.
-	    </p>
-	    <p>
-	      A lot of operations communicating with a process executing a
-	      dirty NIF can, however, complete while it is executing the
-	      dirty NIF. For example, retrieving information about it via
-	      <c>process_info()</c>, setting its group leader,
-	      register/unregister its name, etc.
-	    </p>
-	    <p>
-	      Termination of a process executing a dirty NIF can only be
-	      completed up to a certain point while it is executing the
-	      dirty NIF. All Erlang resources such as its registered name,
-	      its ETS tables, etc will be released. All links and monitors
-	      will be triggered. The actual execution of the NIF will
-	      however <em>not</em> be stopped. The NIF can safely continue
-	      execution, allocate heap memory, etc, but it is of course better
-	      to stop executing as soon as possible. The NIF can check
-	      whether current process is alive or not using
-	      <seealso marker="#enif_is_current_process_alive"><c>enif_is_current_process_alive</c></seealso>.
-	      Communication using
-	      <seealso marker="#enif_send"><c>enif_send</c></seealso>,
-	      and <seealso marker="#enif_port_command"><c>enif_port_command</c></seealso>
-	      will also be dropped when the sending process is not alive.
-	      Deallocation of certain internal resources such as process
-	      heap, and process control block will be delayed until the
-	      dirty NIF has completed.
-	    </p>
-	    <p>Currently known issues that are planned to be fixed:</p>
-	    <list>
-	      <item>
-		<p>
-		  Since purging of a module currently might need to garbage
-		  collect a process in order to determine if it has
-		  references to the module, a process executing a dirty
-		  NIF might delay purging for a very long time. Delaying
-		  a purge operation implies delaying <em>all</em> code
-		  loading operations which might cause severe problems for
-		  the system as a whole.
-		</p>
-	      </item>
-	    </list>
-
-	  </item>
-	</taglist>
-
+            <p>
+              To schedule a dirty NIF for execution, the application has two options:</p>
+            <list type="bulleted">
+              <item>
+                <p>Set the appropriate flags value for the dirty NIF in its
+                  <seealso marker="#ErlNifFunc"> <c>ErlNifFunc</c></seealso>
+                  entry.</p>
+              </item>
+              <item>
+                <p>Call <seealso marker="#enif_schedule_nif">
+                  <c>enif_schedule_nif</c></seealso>, pass to it a pointer
+                  to the dirty NIF to be executed, and indicate with argument
+                  <c>flags</c> whether it expects the operation to be CPU-bound
+                  or I/O-bound.</p>
+              </item>
+            </list>
+            <p>A job that alternates between I/O bound and CPU bound can be
+              reclassified and rescheduled using <c>enif_schedule_nif</c> so
+              that it executes on the correct type of dirty scheduler at all
+              times. For more information see the documentation of the
+              <c>erl</c> command line arguments
+              <seealso marker="erl#+SDcpu"><c>+SDcpu</c></seealso>,
+              and <seealso marker="erl#+SDio"><c>+SDio</c></seealso>.</p>
+            <p>While a process executes a dirty NIF, some operations that
+              communicate with it can take a very long time to complete.
+              Suspend or garbage collection of a process executing a dirty
+              NIF cannot be done until the dirty NIF has returned. Thus, other
+              processes waiting for such operations to complete might
+              have to wait for a very long time. Blocking multi-scheduling, that
+              is, calling <seealso marker="erlang#system_flag_multi_scheduling">
+              <c>erlang:system_flag(multi_scheduling, block)</c></seealso>, can
+              also take a very long time to complete. This becaue all ongoing
+              dirty operations on all dirty schedulers must complete before
+              the block operation can complete.</p>
+            <p>Many operations communicating with a process executing a
+              dirty NIF can, however, complete while it executes the
+              dirty NIF. For example, retrieving information about it through
+              <seealso marker="erlang:process_info/1">
+              <c>erlang:process_info</c></seealso>, setting its group leader,
+              register/unregister its name, and so on.</p>
+            <p>Termination of a process executing a dirty NIF can only be
+              completed up to a certain point while it executes the dirty NIF.
+              All Erlang resources, such as its registered name and its <c>ets</c>
+              tables, are released. All links and monitors are triggered. The
+              execution of the NIF is, however, <em>not</em> stopped. The NIF
+              can safely continue execution, allocate heap memory, and so on,
+              but it is of course better to stop executing as soon as possible.
+              The NIF can check whether a current process is alive using
+              <seealso marker="#enif_is_current_process_alive">
+              <c>enif_is_current_process_alive</c></seealso>. Communication
+              using <seealso marker="#enif_send"><c>enif_send</c></seealso> and
+              <seealso marker="#enif_port_command">
+              <c>enif_port_command</c></seealso> is also dropped when the
+              sending process is not alive. Deallocation of certain internal
+              resources, such as process heap and process control block, is
+              delayed until the dirty NIF has completed.</p>
+            <p>Known issue that are planned to be fixed:</p>
+            <list type="bulleted">
+              <item>
+                <p>As purging of a module might need to garbage
+                  collect a process to determine if it has
+                  references to the module, a process executing a dirty
+                  NIF can delay purging for a very long time. Delaying
+                  a purge operation implies delaying <em>all</em> code
+                  loading operations, which can cause severe problems for
+                  the system as a whole.</p>
+              </item>
+            </list>
+          </item>
+        </taglist>
       </item>
     </taglist>
   </section>
+
   <section>
-    <title>INITIALIZATION</title>
+    <title>Initialization</title>
     <taglist>
-      <tag><marker id="ERL_NIF_INIT"/>ERL_NIF_INIT(MODULE, ErlNifFunc funcs[], load, reload, upgrade, unload)</tag>
-      <item><p>This is the magic macro to initialize a NIF library. It
-      should be evaluated in global file scope.</p>
-      <p><c>MODULE</c> is the name of the Erlang module as an
-      identifier without string quotations. It will be stringified by
-      the macro.</p>
-      <p><c>funcs</c> is a static array of function descriptors for
-      all the implemented NIFs in this library.</p>
-      <p><c>load</c>, <c>reload</c>, <c>upgrade</c> and <c>unload</c>
-      are pointers to functions. One of <c>load</c>, <c>reload</c> or
-      <c>upgrade</c> will be called to initialize the library.
-      <c>unload</c> is called to release the library. They are all
-      described individually below.</p>
-      <p>If compiling a nif for static inclusion via --enable-static-nifs you
-      have to define STATIC_ERLANG_NIF before the ERL_NIF_INIT declaration.</p>
+      <tag><marker id="ERL_NIF_INIT"/><c>ERL_NIF_INIT(MODULE,
+        ErlNifFunc funcs[], load, reload, upgrade, unload)</c></tag>
+      <item>
+        <p>This is the magic macro to initialize a NIF library. It
+          is to be evaluated in global file scope.</p>
+        <p><c>MODULE</c> is the name of the Erlang module as an
+          identifier without string quotations. It is stringified by
+          the macro.</p>
+        <p><c>funcs</c> is a static array of function descriptors for
+          all the implemented NIFs in this library.</p>
+        <p><c>load</c>, <c>reload</c>, <c>upgrade</c> and <c>unload</c>
+          are pointers to functions. One of <c>load</c>, <c>reload</c>, or
+          <c>upgrade</c> is called to initialize the library.
+          <c>unload</c> is called to release the library. All are
+          described individually below.</p>
+        <p>If compiling a NIF for static inclusion through
+          <c>--enable-static-nifs</c>, you must define <c>STATIC_ERLANG_NIF</c>
+           before the <c>ERL_NIF_INIT</c> declaration.</p>
       </item>
-
-      <tag><marker id="load"/>int (*load)(ErlNifEnv* env, void** priv_data, ERL_NIF_TERM load_info)</tag>
-       <item><p><c>load</c> is called when the NIF library is loaded
-        and there is no previously loaded library for this module.</p>
+      <tag><marker id="load"/><c>int (*load)(ErlNifEnv* env, void** priv_data,
+        ERL_NIF_TERM load_info)</c></tag>
+      <item>
+        <p><c>load</c> is called when the NIF library is loaded
+          and no previously loaded library exists for this module.</p>
         <p><c>*priv_data</c> can be set to point to some private data
-           that the library needs in order to keep a state between NIF
-           calls. <c>enif_priv_data</c> will return this pointer.
-           <c>*priv_data</c> will be initialized to NULL when <c>load</c> is
-           called.</p> 
+          that the library needs to keep a state between NIF
+          calls. <c>enif_priv_data</c> returns this pointer.
+          <c>*priv_data</c> is initialized to <c>NULL</c> when <c>load</c> is
+          called.</p> 
         <p><c>load_info</c> is the second argument to <seealso
-           marker="erlang#load_nif-2">erlang:load_nif/2</seealso>.</p>
-        <p>The library will fail to load if <c>load</c> returns
-           anything other than 0. <c>load</c> can be NULL in case no
-           initialization is needed.</p> 
-       </item>
-
-      <tag><marker id="upgrade"/>int (*upgrade)(ErlNifEnv* env, void** priv_data, void** old_priv_data, ERL_NIF_TERM load_info)</tag>
-       <item><p><c>upgrade</c> is called when the NIF library is loaded
-        and there is old code of this module with a loaded NIF library.</p>
-        <p>Works the same as <c>load</c>. The only difference is that
-        <c>*old_priv_data</c> already contains the value set by the
-         last call to <c>load</c> or <c>reload</c> for the old module
-         code. <c>*priv_data</c> will be initialized to NULL when <c>upgrade</c>
-         is called. It is allowed to write to both *priv_data and *old_priv_data.</p> 
-        <p>The library will fail to load if <c>upgrade</c> returns
-           anything other than 0 or if <c>upgrade</c> is NULL.</p>
+          marker="erlang#load_nif-2"><c>erlang:load_nif/2</c></seealso>.</p>
+        <p>The library fails to load if <c>load</c> returns
+          anything other than <c>0</c>. <c>load</c> can be <c>NULL</c> if
+          initialization is not needed.</p> 
       </item>
-
-      <tag><marker id="unload"/>void (*unload)(ErlNifEnv* env, void* priv_data)</tag>
-       <item><p><c>unload</c> is called when the module code that
-       the NIF library belongs to is purged as old. New code
-       of the same module may or may not exist. Note that <c>unload</c> is not
-       called for a replaced library as a consequence of <c>reload</c>.</p>
+      <tag><marker id="upgrade"/><c>int (*upgrade)(ErlNifEnv* env, void**
+        priv_data, void** old_priv_data, ERL_NIF_TERM load_info)</c></tag>
+      <item>
+        <p><c>upgrade</c> is called when the NIF library is loaded
+          and there is old code of this module with a loaded NIF library.</p>
+        <p>Works as <c>load</c>, except that <c>*old_priv_data</c> already
+          contains the value set by the last call to <c>load</c> or
+          <c>reload</c> for the old module code. <c>*priv_data</c> is
+          initialized to <c>NULL</c> when <c>upgrade</c> is called. It is
+          allowed to write to both <c>*priv_data</c> and
+          <c>*old_priv_data.</c></p> 
+        <p>The library fails to load if <c>upgrade</c> returns
+           anything other than <c>0</c> or if <c>upgrade</c> is <c>NULL</c>.</p>
       </item>
-
-      <tag><marker id="reload"/>int (*reload)(ErlNifEnv* env, void** priv_data, ERL_NIF_TERM load_info)</tag>
-     
-       <item>
-         <note><p>The reload mechanism is <em>deprecated</em>. It was only intended
-         as a development feature. Do not use it as an upgrade method for
-         live production systems. It might be removed in future releases. Be sure
-         to pass <c>reload</c> as <c>NULL</c> to <seealso marker="#ERL_NIF_INIT">ERL_NIF_INIT</seealso>
-         to disable it when not used.</p>
-         </note>
-        <p><c>reload</c> is called when the NIF library is loaded
-        and there is already a previously loaded library for this
-        module code.</p>
-        <p>Works the same as <c>load</c>. The only difference is that
-        <c>*priv_data</c> already contains the value set by the
-        previous call to <c>load</c> or <c>reload</c>.</p>
-        <p>The library will fail to load if <c>reload</c> returns
-           anything other than 0 or if <c>reload</c> is NULL.</p> 
+      <tag><marker id="unload"/><c>void (*unload)(ErlNifEnv* env, void*
+        priv_data)</c></tag>
+      <item>
+        <p><c>unload</c> is called when the module code that
+          the NIF library belongs to is purged as old. New code of the same
+          module may or may not exist. Notice that <c>unload</c> is not
+          called for a replaced library as a consequence of <c>reload</c>.</p>
+      </item>
+      <tag><marker id="reload"/><c>int (*reload)(ErlNifEnv* env, void**
+        priv_data, ERL_NIF_TERM load_info)</c></tag>
+      <item>
+        <note>
+          <p><em>The reload mechanism is deprecated.</em> It was only intended
+            as a development feature. Do not use it as an upgrade method for
+            live production systems. It can be removed in future releases.
+            Ensure to pass <c>reload</c> as <c>NULL</c> to
+            <seealso marker="#ERL_NIF_INIT"><c>ERL_NIF_INIT</c></seealso>
+            to disable it when not used.</p>
+        </note>
+        <p><c>reload</c> is called when the NIF library is loaded and a
+          previously loaded library already exists for this module code.</p>
+        <p>Works as <c>load</c>, except that
+          <c>*priv_data</c> already contains the value set by the
+          previous call to <c>load</c> or <c>reload</c>.</p>
+        <p>The library fails to load if <c>reload</c> returns
+          anything other than <c>0</c> or if <c>reload</c> is <c>NULL</c>.</p> 
       </item>
-
     </taglist>
   </section>
 
   <section>
-    <title>DATA TYPES</title>
-
+    <title>Data Types</title>
     <taglist>
-      <tag><marker id="ERL_NIF_TERM"/>ERL_NIF_TERM</tag>
-       <item>
+      <tag><marker id="ERL_NIF_TERM"/><c>ERL_NIF_TERM</c></tag>
+      <item>
         <p>Variables of type <c>ERL_NIF_TERM</c> can refer to any Erlang term.
-        This is an opaque type and values of it can only by used either as
-        arguments to API functions or as return values from NIFs. All
-        <c>ERL_NIF_TERM</c>'s belong to an environment
-        (<seealso marker="#ErlNifEnv">ErlNifEnv</seealso>). A term can not be
-        destructed individually, it is valid until its environment is destructed.</p>
+          This is an opaque type and values of it can only by used either as
+          arguments to API functions or as return values from NIFs. All
+          <c>ERL_NIF_TERM</c>s belong to an environment
+          (<seealso marker="#ErlNifEnv"><c>ErlNifEnv</c></seealso>).
+          A term cannot be destructed individually, it is valid until its
+          environment is destructed.</p>
       </item>
-     <tag><marker id="ErlNifEnv"/>ErlNifEnv</tag>
+      <tag><marker id="ErlNifEnv"/><c>ErlNifEnv</c></tag>
       <item>
-        <p><c>ErlNifEnv</c> represents an environment that can host Erlang terms.
-        All terms in an environment are valid as long as the environment is valid.
-        <c>ErlNifEnv</c> is an opaque type and pointers to it can only be passed
-        on to API functions. There are two types of environments; process
-        bound and process independent.</p>
-        <p>A <em>process bound environment</em> is passed as the first argument to all NIFs.
-        All function arguments passed to a NIF will belong to that environment.
-        The return value from a NIF must also be a term belonging to the same
-        environment.
-        In addition a process bound environment contains transient information
-        about the calling Erlang process. The environment is only valid in the 
-        thread where it was supplied as argument until the NIF returns. It is
-        thus useless and dangerous to store pointers to process bound
-        environments between NIF calls. </p>
-        <p>A <em>process independent environment</em> is created by calling
-        <seealso marker="#enif_alloc_env">enif_alloc_env</seealso>. It can be
-        used to store terms between NIF calls and to send terms with
-        <seealso marker="#enif_send">enif_send</seealso>. A process
-        independent environment with all its terms is valid until you explicitly
-        invalidates it with <seealso marker="#enif_free_env">enif_free_env</seealso>
-        or <c>enif_send</c>.</p>
+        <p><c>ErlNifEnv</c> represents an environment that can host Erlang
+          terms. All terms in an environment are valid as long as the
+          environment is valid. <c>ErlNifEnv</c> is an opaque type; pointers to
+          it can only be passed on to API functions. Two types of environments
+          exist:</p>
+        <taglist>
+          <tag>Process-bound environment</tag>
+          <item>
+            <p>Passed as the first argument to all NIFs. All function arguments
+              passed to a NIF belong to that environment. The return value from
+              a NIF must also be a term belonging to the same environment.</p>
+            <p>A process-bound environment contains transient information
+              about the calling Erlang process. The environment is only valid
+              in the thread where it was supplied as argument until the NIF
+              returns. It is thus useless and dangerous to store pointers to
+              process-bound environments between NIF calls.</p>
+          </item>
+          <tag>Process-independent environment</tag>
+          <item>
+            <p>Created by calling <seealso marker="#enif_alloc_env">
+              <c>enif_alloc_env</c></seealso>. This environment can be
+              used to store terms between NIF calls and to send terms with
+              <seealso marker="#enif_send"><c>enif_send</c></seealso>. A
+              process-independent environment with all its terms is valid until
+              you explicitly invalidate it with
+              <seealso marker="#enif_free_env"><c>enif_free_env</c></seealso>
+              or <c>enif_send</c>.</p>
+          </item>
+        </taglist>
         <p>All contained terms of a list/tuple/map must belong to the same
-	environment as the list/tuple/map itself. Terms can be copied between
-	environments with
-        <seealso marker="#enif_make_copy">enif_make_copy</seealso>.</p>
+          environment as the list/tuple/map itself. Terms can be copied between
+          environments with
+          <seealso marker="#enif_make_copy"><c>enif_make_copy</c></seealso>.</p>
       </item>
-    <tag><marker id="ErlNifFunc"/>ErlNifFunc</tag>
-     <item>
-      <p/>
-      <code type="none">
+      <tag><marker id="ErlNifFunc"/><c>ErlNifFunc</c></tag>
+      <item>
+        <code type="none">
 typedef struct {
     const char* name;
     unsigned arity;
     ERL_NIF_TERM (*fptr)(ErlNifEnv* env, int argc, const ERL_NIF_TERM argv[]);
     unsigned flags;
-} ErlNifFunc;
-</code>
-        <p>Describes a NIF by its name, arity and implementation.
-        <c>fptr</c> is a pointer to the function that implements the
-        NIF. The argument <c>argv</c> of a NIF will contain the
-        function arguments passed to the NIF and <c>argc</c> is the
-        length of the array, i.e. the function arity. <c>argv[N-1]</c>
-        will thus denote the Nth argument to the NIF. Note that the
-        <c>argc</c> argument allows for the same C function to
-        implement several Erlang functions with different arity (but
-        same name probably). For a regular NIF, <c>flags</c> is 0 (and
-        so its value can be omitted for statically initialized <c>ErlNifFunc</c>
-        instances), or it can be used to indicate that the NIF is a <seealso
-        marker="#dirty_nifs">dirty NIF</seealso> that should be executed
-        on a dirty scheduler thread (<em>note that the dirty NIF functionality
-        described here is experimental</em> and that you have to enable
-        support for dirty schedulers when building OTP in order to try the
-        functionality out). If the dirty NIF is expected to be
-        CPU-bound, its <c>flags</c> field should be set to
-        <c>ERL_NIF_DIRTY_JOB_CPU_BOUND</c>, or for I/O-bound jobs,
-        <c>ERL_NIF_DIRTY_JOB_IO_BOUND</c>.</p>
-	<note><p>If one of the
-	<c>ERL_NIF_DIRTY_JOB_*_BOUND</c> flags is set, and the runtime
-	system has no support for dirty schedulers, the runtime system
-	will refuse to load the NIF library.</p></note>
+} ErlNifFunc;</code>
+        <p>Describes a NIF by its name, arity, and implementation.</p>
+        <taglist>
+          <tag><c>fptr</c></tag>
+          <item>
+            <p>A pointer to the function that implements the NIF.</p>
+          </item>
+          <tag><c>argv</c></tag>
+          <item>
+            <p>Contains the function arguments passed to the NIF.</p>
+          </item>
+          <tag><c>argc</c></tag>
+          <item>
+            <p>The array length, that is, the function arity. <c>argv[N-1]</c>
+              thus denotes the Nth argument to the NIF. Notice that the argument
+              <c>argc</c> allows for the same C function to implement several
+              Erlang functions with different arity (but probably with the same
+              name).</p>
+          </item>
+          <tag><c>flags</c></tag>
+          <item>
+            <p>Is <c>0</c> for a regular NIF (and so its value can be omitted
+              for statically initialized <c>ErlNifFunc</c> instances).</p>
+            <p><c>flags</c> can be used to indicate that the NIF is a
+              <seealso marker="#dirty_nifs">dirty NIF</seealso> that is to be
+              executed on a dirty scheduler thread.</p>
+            <p><em>The dirty NIF functionality described here is
+              experimental.</em> You have to enable support for dirty
+              schedulers when building OTP to try out the functionality.</p>
+            <p>If the dirty NIF is expected to be CPU-bound, its <c>flags</c>
+              field is to be set to <c>ERL_NIF_DIRTY_JOB_CPU_BOUND</c> or
+              <c>ERL_NIF_DIRTY_JOB_IO_BOUND</c>.</p>
+            <note>
+              <p>If one of the <c>ERL_NIF_DIRTY_JOB_*_BOUND</c> flags is set,
+                and the runtime system has no support for dirty schedulers,
+                the runtime system refuses to load the NIF library.</p>
+            </note>
+          </item>
+        </taglist>
       </item>
-    <tag><marker id="ErlNifBinary"/>ErlNifBinary</tag>
-     <item>
-      <p/>
-      <code type="none">
+      <tag><marker id="ErlNifBinary"/><c>ErlNifBinary</c></tag>
+      <item>
+        <code type="none">
 typedef struct {
     unsigned size;
     unsigned char* data;
-} ErlNifBinary;
-</code>
+} ErlNifBinary;</code>
         <p><c>ErlNifBinary</c> contains transient information about an
           inspected binary term. <c>data</c> is a pointer to a buffer
           of <c>size</c> bytes with the raw content of the binary.</p>
-          <p>Note that <c>ErlNifBinary</c> is a semi-opaque type and you are
+          <p>Notice that <c>ErlNifBinary</c> is a semi-opaque type and you are
           only allowed to read fields <c>size</c> and <c>data</c>.</p>
       </item>
-
-      <tag><marker id="ErlNifBinaryToTerm"/>ErlNifBinaryToTerm</tag>
+      <tag><marker id="ErlNifBinaryToTerm"/><c>ErlNifBinaryToTerm</c></tag>
       <item>
-        <p>An enumeration of the options that can be given to
-        <seealso marker="#enif_binary_to_term">enif_binary_to_term</seealso>.
-	For default behavior, use the value <c>0</c>.</p>
-        <taglist>
-	  <tag><c>ERL_NIF_BIN2TERM_SAFE</c></tag>
-	  <item><p>Use this option when receiving data from untrusted sources.</p></item>
-	</taglist>
+        <p>An enumeration of the options that can be specified to
+          <seealso marker="#enif_binary_to_term">
+          <c>enif_binary_to_term</c></seealso>.
+          For default behavior, use value <c>0</c>.</p>
+        <p>When receiving data from untrusted sources, use option
+          <c>ERL_NIF_BIN2TERM_SAFE</c>.</p>
       </item>
-
-      <tag><marker id="ErlNifPid"/>ErlNifPid</tag>
-       <item>
-          <p><c>ErlNifPid</c> is a process identifier (pid). In contrast to
-          pid terms (instances of <c>ERL_NIF_TERM</c>), <c>ErlNifPid</c>'s are self
-          contained and not bound to any
-          <seealso marker="#ErlNifEnv">environment</seealso>. <c>ErlNifPid</c>
-          is an opaque type.</p>
-        </item>
-      <tag><marker id="ErlNifPort"/>ErlNifPort</tag>
-       <item>
-          <p><c>ErlNifPort</c> is a port identifier. In contrast to
-          port id terms (instances of <c>ERL_NIF_TERM</c>), <c>ErlNifPort</c>'s are self
-          contained and not bound to any
-          <seealso marker="#ErlNifEnv">environment</seealso>. <c>ErlNifPort</c>
-          is an opaque type.</p>
-        </item>
-
-      <tag><marker id="ErlNifResourceType"/>ErlNifResourceType</tag>
-       <item>
-          <p>Each instance of <c>ErlNifResourceType</c> represent a class of
-          memory managed resource objects that can be garbage collected.
+      <tag><marker id="ErlNifPid"/><c>ErlNifPid</c></tag>
+      <item>
+        <p>A process identifier (pid). In contrast to pid terms (instances of
+          <c>ERL_NIF_TERM</c>), <c>ErlNifPid</c>s are self-contained and not
+          bound to any <seealso marker="#ErlNifEnv">environment</seealso>.
+          <c>ErlNifPid</c> is an opaque type.</p>
+      </item>
+      <tag><marker id="ErlNifPort"/><c>ErlNifPort</c></tag>
+      <item>
+        <p>A port identifier. In contrast to port ID terms (instances of
+          <c>ERL_NIF_TERM</c>), <c>ErlNifPort</c>s are self-contained and not
+          bound to any <seealso marker="#ErlNifEnv">environment</seealso>.
+          <c>ErlNifPort</c> is an opaque type.</p>
+      </item>
+      <tag><marker id="ErlNifResourceType"/><c>ErlNifResourceType</c></tag>
+      <item>
+        <p>Each instance of <c>ErlNifResourceType</c> represents a class of
+          memory-managed resource objects that can be garbage collected.
           Each resource type has a unique name and a destructor function that
           is called when objects of its type are released.</p>
-        </item>
-        <tag><marker id="ErlNifResourceDtor"/>ErlNifResourceDtor</tag>
-         <item>
-           <p/>
-           <code type="none">
-typedef void ErlNifResourceDtor(ErlNifEnv* env, void* obj);
-</code>
-            <p>The function prototype of a resource destructor function.</p>
-          </item>
-          <tag><marker id="ErlNifCharEncoding"/>ErlNifCharEncoding</tag>
-           <item>
-             <p/>
-             <code type="none">
+      </item>
+      <tag><marker id="ErlNifResourceDtor"/><c>ErlNifResourceDtor</c></tag>
+      <item>
+        <code type="none">
+typedef void ErlNifResourceDtor(ErlNifEnv* env, void* obj);</code>
+        <p>The function prototype of a resource destructor function.</p>
+      </item>
+      <tag><marker id="ErlNifCharEncoding"/><c>ErlNifCharEncoding</c></tag>
+      <item>
+        <code type="none">
 typedef enum {
     ERL_NIF_LATIN1
-}ErlNifCharEncoding;
-</code>
-              <p>The character encoding used in strings and atoms. The only
-              supported encoding is currently <c>ERL_NIF_LATIN1</c> for
-              iso-latin-1 (8-bit ascii).</p>
-            </item>
-            <tag><marker id="ErlNifSysInfo"/>ErlNifSysInfo</tag>
-             <item>
-                <p>Used by <seealso marker="#enif_system_info">enif_system_info</seealso>
-                to return information about the runtime system. Contains currently
-                the exact same content as <seealso marker="erl_driver#ErlDrvSysInfo">ErlDrvSysInfo</seealso>.</p>
-              </item>
-              <tag><marker id="ErlNifSInt64"/>ErlNifSInt64</tag>
-               <item><p>A native signed 64-bit integer type.</p></item>
-              <tag><marker id="ErlNifUInt64"/>ErlNifUInt64</tag>
-               <item><p>A native unsigned 64-bit integer type.</p></item>
-	       
-      <tag><marker id="ErlNifTime"/>ErlNifTime</tag>
+}ErlNifCharEncoding;</code>
+        <p>The character encoding used in strings and atoms. The only
+          supported encoding is <c>ERL_NIF_LATIN1</c> for
+          ISO Latin-1 (8-bit ASCII).</p>
+      </item>
+      <tag><marker id="ErlNifSysInfo"/><c>ErlNifSysInfo</c></tag>
+      <item>
+        <p>Used by <seealso marker="#enif_system_info">
+          <c>enif_system_info</c></seealso> to return information about the
+          runtime system. Contains the same content as
+          <seealso marker="erl_driver#ErlDrvSysInfo">
+          <c>ErlDrvSysInfo</c></seealso>.</p>
+      </item>
+      <tag><marker id="ErlNifSInt64"/><c>ErlNifSInt64</c></tag>
+      <item>
+        <p>A native signed 64-bit integer type.</p>
+      </item>
+      <tag><marker id="ErlNifUInt64"/><c>ErlNifUInt64</c></tag>
+      <item>
+        <p>A native unsigned 64-bit integer type.</p>
+      </item>
+      <tag><marker id="ErlNifTime"/><c>ErlNifTime</c></tag>
       <item>
         <p>A signed 64-bit integer type for representation of time.</p>
       </item>
-      <tag><marker id="ErlNifTimeUnit"/>ErlNifTimeUnit</tag>
+      <tag><marker id="ErlNifTimeUnit"/><c>ErlNifTimeUnit</c></tag>
       <item>
         <p>An enumeration of time units supported by the NIF API:</p>
-	<taglist>
-	  <tag><c>ERL_NIF_SEC</c></tag>
-	  <item><p>Seconds</p></item>
-	  <tag><c>ERL_NIF_MSEC</c></tag>
-	  <item><p>Milliseconds</p></item>
-	  <tag><c>ERL_NIF_USEC</c></tag>
-	  <item><p>Microseconds</p></item>
-	  <tag><c>ERL_NIF_NSEC</c></tag>
-	  <item><p>Nanoseconds</p></item>
-	</taglist>
+        <taglist>
+          <tag><c>ERL_NIF_SEC</c></tag>
+          <item>Seconds</item>
+          <tag><c>ERL_NIF_MSEC</c></tag>
+          <item>Milliseconds</item>
+          <tag><c>ERL_NIF_USEC</c></tag>
+          <item>Microseconds</item>
+          <tag><c>ERL_NIF_NSEC</c></tag>
+          <item>Nanoseconds</item>
+        </taglist>
       </item>
-
-      <tag><marker id="ErlNifUniqueInteger"/>ErlNifUniqueInteger</tag>
+      <tag><marker id="ErlNifUniqueInteger"/><c>ErlNifUniqueInteger</c></tag>
       <item>
         <p>An enumeration of the properties that can be requested from
-        <seealso marker="#enif_make_unique_integer">enif_unique_integer</seealso>.
-	For default properties, use the value <c>0</c>.</p>
+          <seealso marker="#enif_make_unique_integer">
+          <c>enif_unique_integer</c></seealso>.
+          For default properties, use value <c>0</c>.</p>
         <taglist>
-	  <tag><c>ERL_NIF_UNIQUE_POSITIVE</c></tag>
-	  <item><p>Return only positive integers</p></item>
-	  <tag><c>ERL_NIF_UNIQUE_MONOTONIC</c></tag>
-	  <item><p>Return only
-	  <seealso marker="time_correction#Strictly_Monotonically_Increasing">strictly
-	  monotonically increasing</seealso> integer corresponding to creation time</p></item>
-	</taglist>
+          <tag><c>ERL_NIF_UNIQUE_POSITIVE</c></tag>
+          <item>
+            <p>Return only positive integers.</p>
+          </item>
+          <tag><c>ERL_NIF_UNIQUE_MONOTONIC</c></tag>
+          <item>
+            <p>Return only <seealso
+              marker="time_correction#Strictly_Monotonically_Increasing">
+              strictly monotonically increasing</seealso> integer corresponding
+              to creation time.</p>
+          </item>
+        </taglist>
       </item>
-
     </taglist>
   </section>
 
   <funcs>
     <func>
       <name><ret>void *</ret><nametext>enif_alloc(size_t size)</nametext></name>
-      <fsummary>Allocate dynamic memory</fsummary>
-      <desc><p>Allocate memory of <c>size</c> bytes. Return NULL if allocation failed.</p></desc>
+      <fsummary>Allocate dynamic memory.</fsummary>
+      <desc>
+        <p>Allocates memory of <c>size</c> bytes.</p>
+        <p>Returns <c>NULL</c> if the allocation fails.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_alloc_binary(size_t size, ErlNifBinary* bin)</nametext></name>
-      <fsummary>Create a new binary</fsummary>
-      <desc><p>Allocate a new binary of size <c>size</c>
-      bytes. Initialize the structure pointed to by <c>bin</c> to
-      refer to the allocated binary. The binary must either be released by 
-      <seealso marker="#enif_release_binary">enif_release_binary</seealso> 
-      or ownership transferred to an Erlang term with 
-      <seealso marker="#enif_make_binary">enif_make_binary</seealso>. 
-      An allocated (and owned) <c>ErlNifBinary</c> can be kept between NIF
-      calls.</p>
-        <p>Return true on success or false if allocation failed.</p>
+      <name><ret>int</ret>
+        <nametext>enif_alloc_binary(size_t size, ErlNifBinary* bin)</nametext>
+      </name>
+      <fsummary>Create a new binary.</fsummary>
+      <desc>
+        <p>Allocates a new binary of size <c>size</c> bytes.
+          Initializes the structure pointed to by <c>bin</c> to
+          refer to the allocated binary. The binary must either be released by
+          <seealso marker="#enif_release_binary">
+          <c>enif_release_binary</c></seealso> 
+          or ownership transferred to an Erlang term with
+          <seealso marker="#enif_make_binary"><c>enif_make_binary</c></seealso>.
+          An allocated (and owned) <c>ErlNifBinary</c> can be kept between NIF
+          calls.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if allocation
+          fails.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>ErlNifEnv *</ret><nametext>enif_alloc_env()</nametext></name>
-      <fsummary>Create a new environment</fsummary>
-      <desc><p>Allocate a new process independent environment. The environment can
-      be used to hold terms that is not bound to any process. Such terms can
-      later be copied to a process environment with
-      <seealso marker="#enif_make_copy">enif_make_copy</seealso>
-      or be sent to a process as a message with <seealso marker="#enif_send">enif_send</seealso>.</p>
-      <p>Return pointer to the new environment.</p>
-      </desc>
-    </func>
-
-    <func>
-      <name><ret>void *</ret><nametext>enif_alloc_resource(ErlNifResourceType* type, unsigned size)</nametext></name>
-      <fsummary>Allocate a memory managed resource object</fsummary>
-      <desc><p>Allocate a memory managed resource object of type <c>type</c> and size <c>size</c> bytes.</p></desc>
-    </func>
-
-    <func>
-      <name><ret>size_t</ret><nametext>enif_binary_to_term(ErlNifEnv *env, const unsigned char* data, size_t size, ERL_NIF_TERM *term, ErlNifBinaryToTerm opts)</nametext></name>
-    <fsummary>Create a term from the external format</fsummary>
-    <desc>
-      <p>Create a term that is the result of decoding the binary data
-      at <c>data</c>, which must be encoded according to the Erlang external term format.
-      No more than <c>size</c> bytes are read from <c>data</c>. Argument <c>opts</c>
-      correspond to the second argument to <seealso marker="erlang#binary_to_term-2">
-      <c>erlang:binary_to_term/2</c></seealso>, and must be either <c>0</c> or
-      <c>ERL_NIF_BIN2TERM_SAFE</c>.</p>
-      <p>On success, store the resulting term at <c>*term</c> and return
-      the actual number of bytes read. Return zero if decoding fails or if <c>opts</c>
-      is invalid.</p>
-      <p>See also:
-        <seealso marker="#ErlNifBinaryToTerm"><c>ErlNifBinaryToTerm</c></seealso>,
-        <seealso marker="erlang#binary_to_term-2"><c>erlang:binary_to_term/2</c></seealso> and
-        <seealso marker="#enif_term_to_binary"><c>enif_term_to_binary</c></seealso>.
-      </p>
-    </desc>
+      <fsummary>Create a new environment.</fsummary>
+      <desc>
+        <p>Allocates a new process-independent environment. The environment can
+          be used to hold terms that are not bound to any process. Such terms
+          can later be copied to a process environment with
+          <seealso marker="#enif_make_copy"><c>enif_make_copy</c></seealso> or
+          be sent to a process as a message with <seealso marker="#enif_send">
+          <c>enif_send</c></seealso>.</p>
+        <p>Returns pointer to the new environment.</p>
+      </desc>
     </func>
 
-
     <func>
-      <name><ret>void</ret><nametext>enif_clear_env(ErlNifEnv* env)</nametext></name>
-      <fsummary>Clear an environment for reuse</fsummary>
-      <desc><p>Free all terms in an environment and clear it for reuse. The environment must
-      have been allocated with <seealso marker="#enif_alloc_env">enif_alloc_env</seealso>.
-      </p></desc>
+      <name><ret>void *</ret><nametext>enif_alloc_resource(ErlNifResourceType*
+        type, unsigned size)</nametext></name>
+      <fsummary>Allocate a memory-managed resource object.</fsummary>
+      <desc>
+        <p>Allocates a memory-managed resource object of type <c>type</c> and
+          size <c>size</c> bytes.</p>
+      </desc>
     </func>
 
-
     <func>
-      <name><ret>int</ret><nametext>enif_compare(ERL_NIF_TERM lhs, ERL_NIF_TERM rhs)</nametext></name>
-      <fsummary>Compare two terms</fsummary>
-      <desc><p>Return an integer less than, equal to, or greater than
-      zero if <c>lhs</c> is found, respectively, to be less than,
-      equal, or greater than <c>rhs</c>. Corresponds to the Erlang
-      operators <c>==</c>, <c>/=</c>, <c>=&lt;</c>, <c>&lt;</c>,
-      <c>&gt;=</c> and <c>&gt;</c> (but <em>not</em> <c>=:=</c> or <c>=/=</c>).</p></desc>
+      <name><ret>size_t</ret><nametext>enif_binary_to_term(ErlNifEnv *env,
+        const unsigned char* data, size_t size, ERL_NIF_TERM *term,
+        ErlNifBinaryToTerm opts)</nametext></name>
+      <fsummary>Create a term from the external format.</fsummary>
+      <desc>
+        <p>Creates a term that is the result of decoding the binary data at
+          <c>data</c>, which must be encoded according to the Erlang external
+          term format. No more than <c>size</c> bytes are read from <c>data</c>.
+          Argument <c>opts</c> corresponds to the second argument to
+          <seealso marker="erlang#binary_to_term-2">
+          <c>erlang:binary_to_term/2</c></seealso> and must be either <c>0</c>
+          or <c>ERL_NIF_BIN2TERM_SAFE</c>.</p>
+        <p>On success, stores the resulting term at <c>*term</c> and returns
+          the number of bytes read. Returns <c>0</c> if decoding fails or if
+          <c>opts</c> is invalid.</p>
+        <p>See also <seealso marker="#ErlNifBinaryToTerm">
+          <c>ErlNifBinaryToTerm</c></seealso>,
+          <seealso marker="erlang#binary_to_term-2">
+          <c>erlang:binary_to_term/2</c></seealso>, and
+          <seealso marker="#enif_term_to_binary">
+          <c>enif_term_to_binary</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>enif_cond_broadcast(ErlNifCond *cnd)</nametext></name>
-    <fsummary></fsummary>
-    <desc><p>Same as <seealso marker="erl_driver#erl_drv_cond_broadcast">erl_drv_cond_broadcast</seealso>.
-          </p></desc>
+      <name><ret>void</ret><nametext>enif_clear_env(ErlNifEnv* env)</nametext>
+      </name>
+      <fsummary>Clear an environment for reuse.</fsummary>
+      <desc>
+        <p>Frees all terms in an environment and clears it for reuse.
+          The environment must have been allocated with
+          <seealso marker="#enif_alloc_env"><c>enif_alloc_env</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ErlNifCond *</ret><nametext>enif_cond_create(char *name)</nametext></name>
-    <fsummary></fsummary>
-    <desc><p>Same as <seealso marker="erl_driver#erl_drv_cond_create">erl_drv_cond_create</seealso>.
-          </p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_compare(ERL_NIF_TERM lhs, ERL_NIF_TERM rhs)</nametext>
+      </name>
+      <fsummary>Compare two terms.</fsummary>
+      <desc>
+        <p>Returns an integer &lt; <c>0</c> if <c>lhs</c> &lt; <c>rhs</c>,
+          <c>0</c> if <c>lhs</c> = <c>rhs</c>, and &gt; <c>0</c> if
+          <c>lhs</c> &gt; <c>rhs</c>. Corresponds to the Erlang
+          operators <c>==</c>, <c>/=</c>, <c>=&lt;</c>, <c>&lt;</c>,
+          <c>&gt;=</c>, and <c>&gt;</c> (but <em>not</em> <c>=:=</c> or
+          <c>=/=</c>).</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>enif_cond_destroy(ErlNifCond *cnd)</nametext></name>
-    <fsummary></fsummary>
-    <desc><p>Same as <seealso marker="erl_driver#erl_drv_cond_destroy">erl_drv_cond_destroy</seealso>.
-          </p></desc>
+      <name><ret>void</ret>
+        <nametext>enif_cond_broadcast(ErlNifCond *cnd)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_cond_broadcast">
+          <c>erl_drv_cond_broadcast</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>enif_cond_signal(ErlNifCond *cnd)</nametext></name>
-    <fsummary></fsummary>
-    <desc><p>Same as <seealso marker="erl_driver#erl_drv_cond_signal">erl_drv_cond_signal</seealso>.
-          </p></desc>
+      <name><ret>ErlNifCond *</ret>
+        <nametext>enif_cond_create(char *name)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_cond_create">
+          <c>erl_drv_cond_create</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>enif_cond_wait(ErlNifCond *cnd, ErlNifMutex *mtx)</nametext></name>
-    <fsummary></fsummary>
-    <desc><p>Same as <seealso marker="erl_driver#erl_drv_cond_wait">erl_drv_cond_wait</seealso>.
-          </p></desc>
+      <name><ret>void</ret>
+        <nametext>enif_cond_destroy(ErlNifCond *cnd)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_cond_destroy">
+          <c>erl_drv_cond_destroy</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_consume_timeslice(ErlNifEnv *env, int percent)</nametext></name>
-    <fsummary></fsummary>
-    <desc><p>Give the runtime system a hint about how much CPU time the current NIF call has consumed
-    since last hint, or since the start of the NIF if no previous hint has been given.
-    The time is given as a <c>percent</c> of the timeslice that a process is allowed to execute Erlang
-    code until it may be suspended to give time for other runnable processes.
-    The scheduling timeslice is not an exact entity, but can usually be
-    approximated to about 1 millisecond.</p>
-    <p>Note that it is up to the runtime system to determine if and how to use this information.
-    Implementations on some platforms may use other means in order to determine consumed
-    CPU time. Lengthy NIFs should regardless of this frequently call <c>enif_consume_timeslice</c>
-    in order to determine if it is allowed to continue execution or not.</p>
+      <name><ret>void</ret>
+        <nametext>enif_cond_signal(ErlNifCond *cnd)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_cond_signal">
+          <c>erl_drv_cond_signal</c></seealso>.</p>
+      </desc>
+    </func>
 
-    <p>Returns 1 if the timeslice is exhausted, or 0 otherwise. If 1 is returned the NIF should return
-    as soon as possible in order for the process to yield.</p>
-    <p>Argument <c>percent</c> must be an integer between 1 and 100. This function
-    must only be called from a NIF-calling thread and argument <c>env</c> must be
-    the environment of the calling process.</p>
-    <p>This function is provided to better support co-operative scheduling, improve system responsiveness,
-    and make it easier to prevent misbehaviors of the VM due to a NIF monopolizing a scheduler thread.
-    It can be used to divide <seealso marker="#lengthy_work">length work</seealso> into
-    a number of repeated NIF-calls without the need to create threads.
-    See also the <seealso marker="#WARNING">warning</seealso> text at the beginning of this document.</p>
-    </desc>
+    <func>
+      <name><ret>void</ret>
+        <nametext>enif_cond_wait(ErlNifCond *cnd, ErlNifMutex *mtx)</nametext>
+      </name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_cond_wait">
+          <c>erl_drv_cond_wait</c></seealso>.</p>
+      </desc>
     </func>
 
+    <func>
+      <name><ret>int</ret>
+        <nametext>enif_consume_timeslice(ErlNifEnv *env, int percent)</nametext>
+      </name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Gives the runtime system a hint about how much CPU time the current
+          NIF call has consumed since the last hint, or since the start of the
+          NIF if no previous hint has been specified. The time is specified as a
+          percent of the timeslice that a process is allowed to execute
+          Erlang code until it can be suspended to give time for other runnable
+          processes. The scheduling timeslice is not an exact entity, but can
+          usually be approximated to about 1 millisecond.</p>
+        <p>Notice that it is up to the runtime system to determine if and how
+          to use this information. Implementations on some platforms can use
+          other means to determine consumed CPU time. Lengthy NIFs should
+          regardless of this frequently call <c>enif_consume_timeslice</c> to
+          determine if it is allowed to continue execution.</p>
+        <p>Argument <c>percent</c> must be an integer between 1 and 100. This
+          function must only be called from a NIF-calling thread, and argument
+          <c>env</c> must be the environment of the calling process.</p>
+        <p>Returns <c>1</c> if the timeslice is exhausted, otherwise <c>0</c>.
+          If <c>1</c> is returned, the NIF is to return as soon as possible in
+          order for the process to yield.</p>
+        <p>This function is provided to better support co-operative scheduling,
+          improve system responsiveness, and make it easier to prevent
+          misbehaviors of the VM because of a NIF monopolizing a scheduler
+          thread. It can be used to divide <seealso marker="#lengthy_work">
+          length work</seealso> into a number of repeated NIF calls without the
+          need to create threads.</p>
+        <p>See also the <seealso marker="#WARNING">warning</seealso> text at
+          the beginning of this manual page.</p>
+      </desc>
+    </func>
 
     <func>
-      <name><ret>ErlNifTime</ret><nametext>enif_convert_time_unit(ErlNifTime val, ErlNifTimeUnit from, ErlNifTimeUnit to)</nametext></name>
-      <fsummary>Convert time unit of a time value</fsummary>
+      <name><ret>ErlNifTime</ret><nametext>enif_convert_time_unit(ErlNifTime
+        val, ErlNifTimeUnit from, ErlNifTimeUnit to)</nametext></name>
+      <fsummary>Convert time unit of a time value.</fsummary>
       <desc>
-	<marker id="enif_convert_time_unit"></marker>
-	<p>Arguments:</p>
-	<taglist>
-	  <tag><c>val</c></tag>
-	  <item>Value to convert time unit for.</item>
-	  <tag><c>from</c></tag>
-	  <item>Time unit of <c>val</c>.</item>
-	  <tag><c>to</c></tag>
-	  <item>Time unit of returned value.</item>
-	</taglist>
-	<p>Converts the <c>val</c> value of time unit <c>from</c> to
-	the corresponding value of time unit <c>to</c>. The result is
-	rounded using the floor function.</p>
-	<p>Returns <c>ERL_NIF_TIME_ERROR</c> if called with an invalid
-	time unit argument.</p>
-	<p>See also:
-	  <seealso marker="#ErlNifTime"><c>ErlNifTime</c></seealso> and
-	  <seealso marker="#ErlNifTimeUnit"><c>ErlNifTimeUnit</c></seealso>.
-	</p>
+        <marker id="enif_convert_time_unit"></marker>
+        <p>Converts the <c>val</c> value of time unit <c>from</c> to
+          the corresponding value of time unit <c>to</c>. The result is
+          rounded using the floor function.</p>
+        <taglist>
+          <tag><c>val</c></tag>
+          <item>Value to convert time unit for.</item>
+          <tag><c>from</c></tag>
+          <item>Time unit of <c>val</c>.</item>
+          <tag><c>to</c></tag>
+          <item>Time unit of returned value.</item>
+        </taglist>
+        <p>Returns <c>ERL_NIF_TIME_ERROR</c> if called with an invalid
+          time unit argument.</p>
+        <p>See also <seealso marker="#ErlNifTime"><c>ErlNifTime</c></seealso>
+          and
+          <seealso marker="#ErlNifTimeUnit"><c>ErlNifTimeUnit</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_cpu_time(ErlNifEnv *)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_cpu_time(ErlNifEnv *)</nametext></name>
       <fsummary></fsummary>
       <desc>
-        <p>Returns the CPU time in the same format as <seealso marker="erlang#timestamp-0">erlang:timestamp()</seealso>.
-        The CPU time is the time the current logical cpu has spent executing since
-        some arbitrary point in the past.
-        If the OS does not support fetching of this value <c>enif_cpu_time</c>
-        invokes <seealso marker="#enif_make_badarg">enif_make_badarg</seealso>.
-        </p>
+        <p>Returns the CPU time in the same format as
+          <seealso marker="erlang#timestamp-0">
+          <c>erlang:timestamp()</c></seealso>.
+          The CPU time is the time the current logical CPU has spent executing
+          since some arbitrary point in the past. If the OS does not support
+          fetching this value, <c>enif_cpu_time</c> invokes
+          <seealso marker="#enif_make_badarg">
+          <c>enif_make_badarg</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_equal_tids(ErlNifTid tid1, ErlNifTid tid2)</nametext></name>
-    <fsummary></fsummary>
-    <desc><p>Same as <seealso marker="erl_driver#erl_drv_equal_tids">erl_drv_equal_tids</seealso>.
-          </p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_equal_tids(ErlNifTid tid1, ErlNifTid tid2)</nametext>
+      </name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_equal_tids">
+          <c>erl_drv_equal_tids</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
       <name><ret>void</ret><nametext>enif_free(void* ptr)</nametext></name>
-      <fsummary>Free dynamic memory</fsummary>
-      <desc><p>Free memory allocated by <c>enif_alloc</c>.</p></desc>
+      <fsummary>Free dynamic memory.</fsummary>
+      <desc>
+        <p>Frees memory allocated by
+          <seealso marker="#enif_alloc"><c>enif_alloc</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>enif_free_env(ErlNifEnv* env)</nametext></name>
-      <fsummary>Free an environment allocated with enif_alloc_env</fsummary>
-      <desc><p>Free an environment allocated with <seealso marker="#enif_alloc_env">enif_alloc_env</seealso>.
-      All terms created in the environment will be freed as well.</p></desc>
+      <name><ret>void</ret>
+        <nametext>enif_free_env(ErlNifEnv* env)</nametext></name>
+      <fsummary>Free an environment allocated with enif_alloc_env.</fsummary>
+      <desc>
+        <p>Frees an environment allocated with
+          <seealso marker="#enif_alloc_env"><c>enif_alloc_env</c></seealso>.
+          All terms created in the environment are freed as well.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_atom(ErlNifEnv* env, ERL_NIF_TERM term, char* buf, unsigned size, ErlNifCharEncoding encode)</nametext></name>
-      <fsummary>Get the text representation of an atom term</fsummary>
-      <desc><p>Write a null-terminated string, in the buffer pointed to by
-              <c>buf</c> of size <c>size</c>, consisting of the string 
-              representation of the atom <c>term</c> with encoding
-              <seealso marker="#ErlNifCharEncoding">encode</seealso>. Return
-              the number of bytes written (including terminating null character) or 0 if
-              <c>term</c> is not an atom with maximum length of 
-              <c>size-1</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_atom(ErlNifEnv* env, ERL_NIF_TERM
+        term, char* buf, unsigned size, ErlNifCharEncoding encode)</nametext>
+      </name>
+      <fsummary>Get the text representation of an atom term.</fsummary>
+      <desc>
+        <p>Writes a <c>NULL</c>-terminated string in the buffer pointed to by
+          <c>buf</c> of size <c>size</c>, consisting of the string
+          representation of the atom <c>term</c> with encoding
+          <seealso marker="#ErlNifCharEncoding">encode</seealso>.</p>
+        <p>Returns the number of bytes written (including terminating
+          <c>NULL</c> character) or <c>0</c> if <c>term</c> is not an atom with
+           maximum length of <c>size-1</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_atom_length(ErlNifEnv* env, ERL_NIF_TERM term, unsigned* len, ErlNifCharEncoding encode)</nametext></name>
-      <fsummary>Get the length of atom <c>term</c></fsummary>
-      <desc><p>Set <c>*len</c> to the length (number of bytes excluding
-      terminating null character) of the atom <c>term</c> with encoding
-      <c>encode</c>. Return true on success or false if <c>term</c> is not an
-      atom.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_atom_length(ErlNifEnv* env,
+        ERL_NIF_TERM term, unsigned* len, ErlNifCharEncoding encode)</nametext>
+      </name>
+      <fsummary>Get the length of atom <c>term</c>.</fsummary>
+      <desc>
+        <p>Sets <c>*len</c> to the length (number of bytes excluding
+          terminating <c>NULL</c> character) of the atom <c>term</c> with
+          encoding <c>encode</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is not
+          an atom.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_double(ErlNifEnv* env, ERL_NIF_TERM term, double* dp)</nametext></name>
-      <fsummary>Read a floating-point number term</fsummary>
-      <desc><p>Set <c>*dp</c> to the floating point value of
-      <c>term</c>. Return true on success or false if <c>term</c> is not a float.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_double(ErlNifEnv* env,
+        ERL_NIF_TERM term, double* dp)</nametext></name>
+      <fsummary>Read a floating-point number term.</fsummary>
+      <desc>
+        <p>Sets <c>*dp</c> to the floating-point value of <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is not
+          a float.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_int(ErlNifEnv* env, ERL_NIF_TERM term, int* ip)</nametext></name>
-      <fsummary>Read an integer term</fsummary>
-      <desc><p>Set <c>*ip</c> to the integer value of
-      <c>term</c>. Return true on success or false if <c>term</c> is not an
-      integer or is outside the bounds of type <c>int</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_int(ErlNifEnv* env, ERL_NIF_TERM
+        term, int* ip)</nametext></name>
+      <fsummary>Read an integer term.</fsummary>
+      <desc>
+        <p>Sets <c>*ip</c> to the integer value of <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is not
+          an integer or is outside the bounds of type <c>int</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_int64(ErlNifEnv* env, ERL_NIF_TERM term, ErlNifSInt64* ip)</nametext></name>
-      <fsummary>Read a 64-bit integer term</fsummary>
-      <desc><p>Set <c>*ip</c> to the integer value of
-      <c>term</c>. Return true on success or false if <c>term</c> is not an
-      integer or is outside the bounds of a signed 64-bit integer.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_int64(ErlNifEnv* env, ERL_NIF_TERM
+        term, ErlNifSInt64* ip)</nametext></name>
+      <fsummary>Read a 64-bit integer term.</fsummary>
+      <desc>
+        <p>Sets <c>*ip</c> to the integer value of <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is not
+          an integer or is outside the bounds of a signed 64-bit integer.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_local_pid(ErlNifEnv* env, ERL_NIF_TERM term, ErlNifPid* pid)</nametext></name>
-    <fsummary>Read an local pid term</fsummary>
-    <desc><p>If <c>term</c> is the pid of a node local process, initialize the
-    pid variable <c>*pid</c> from it and return true. Otherwise return false.
-    No check if the process is alive is done.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_local_pid(ErlNifEnv* env,
+        ERL_NIF_TERM term, ErlNifPid* pid)</nametext></name>
+      <fsummary>Read a local pid term.</fsummary>
+      <desc>
+        <p>If <c>term</c> is the pid of a node local process, this function
+          initializes the pid variable <c>*pid</c> from it and returns
+          <c>true</c>. Otherwise returns <c>false</c>. No check is done if the
+          process is alive.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_local_port(ErlNifEnv* env, ERL_NIF_TERM term, ErlNifPort* port_id)</nametext></name>
-    <fsummary>Read an local port term</fsummary>
-    <desc><p>If <c>term</c> identifies a node local port, initialize the
-    port variable <c>*port_id</c> from it and return true. Otherwise return false.
-    No check if the port is alive is done.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_local_port(ErlNifEnv* env,
+        ERL_NIF_TERM term, ErlNifPort* port_id)</nametext></name>
+      <fsummary>Read a local port term.</fsummary>
+      <desc>
+        <p>If <c>term</c> identifies a node local port, this function
+          initializes the port variable <c>*port_id</c> from it and returns
+          <c>true</c>. Otherwise returns <c>false</c>. No check is done if the
+          port is alive.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_list_cell(ErlNifEnv* env, ERL_NIF_TERM list, ERL_NIF_TERM* head, ERL_NIF_TERM* tail)</nametext></name>
-      <fsummary>Get head and tail from a list</fsummary>
-      <desc><p>Set <c>*head</c> and <c>*tail</c> from
-      <c>list</c> and return true, or return false if <c>list</c> is not a
-      non-empty list.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_list_cell(ErlNifEnv* env,
+        ERL_NIF_TERM list, ERL_NIF_TERM* head, ERL_NIF_TERM* tail)</nametext>
+      </name>
+      <fsummary>Get head and tail from a list.</fsummary>
+      <desc>
+        <p>Sets <c>*head</c> and <c>*tail</c> from list <c>list</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if the list is
+          empty.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_list_length(ErlNifEnv* env, ERL_NIF_TERM term, unsigned* len)</nametext></name>
-      <fsummary>Get the length of list <c>term</c></fsummary>
-      <desc><p>Set <c>*len</c> to the length of list <c>term</c> and return true,
-      or return false if <c>term</c> is not a proper list.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_list_length(ErlNifEnv* env,
+        ERL_NIF_TERM term, unsigned* len)</nametext></name>
+      <fsummary>Get the length of list <c>term</c>.</fsummary>
+      <desc>
+        <p>Sets <c>*len</c> to the length of list <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not a proper list.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_long(ErlNifEnv* env, ERL_NIF_TERM term, long int* ip)</nametext></name>
-      <fsummary>Read an long integer term</fsummary>
-      <desc><p>Set <c>*ip</c> to the long integer value of <c>term</c> and
-      return true, or return false if <c>term</c> is not an integer or is
-      outside the bounds of type <c>long int</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_long(ErlNifEnv* env, ERL_NIF_TERM
+        term, long int* ip)</nametext></name>
+      <fsummary>Read a long integer term.</fsummary>
+      <desc>
+        <p>Sets <c>*ip</c> to the long integer value of <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not an integer or is outside the bounds of type <c>long int</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_map_size(ErlNifEnv* env, ERL_NIF_TERM term, size_t *size)</nametext></name>
-      <fsummary>Read the size of a map term</fsummary>
-      <desc><p>Set <c>*size</c> to the number of key-value pairs in the map <c>term</c> and
-      return true, or return false if <c>term</c> is not a map.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_map_size(ErlNifEnv* env,
+        ERL_NIF_TERM term, size_t *size)</nametext></name>
+      <fsummary>Read the size of a map term.</fsummary>
+      <desc>
+        <p>Sets <c>*size</c> to the number of key-value pairs in the map
+          <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not a map.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_map_value(ErlNifEnv* env, ERL_NIF_TERM map, ERL_NIF_TERM key, ERL_NIF_TERM* value)</nametext></name>
-     <fsummary>Get the value of a key in a map</fsummary>
-      <desc><p>Set <c>*value</c> to the value associated with <c>key</c> in the
-      map <c>map</c> and return true. Return false if <c>map</c> is not a map
-      or if <c>map</c> does not contain <c>key</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_map_value(ErlNifEnv* env,
+        ERL_NIF_TERM map, ERL_NIF_TERM key, ERL_NIF_TERM* value)</nametext>
+      </name>
+      <fsummary>Get the value of a key in a map.</fsummary>
+      <desc>
+        <p>Sets <c>*value</c> to the value associated with <c>key</c> in the
+          map <c>map</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>map</c> is not
+          a map or if <c>map</c> does not contain <c>key</c>.</p>
+      </desc>
     </func>
-   <func>
-      <name><ret>int</ret><nametext>enif_get_resource(ErlNifEnv* env, ERL_NIF_TERM term, ErlNifResourceType* type, void** objp)</nametext></name>
-      <fsummary>Get the pointer to a resource object</fsummary>
-      <desc><p>Set <c>*objp</c> to point to the resource object referred to by <c>term</c>.</p>
-      <p>Return true on success or false if <c>term</c> is not a handle to a resource object
-      of type <c>type</c>.</p></desc>
+
+    <func>
+      <name><ret>int</ret><nametext>enif_get_resource(ErlNifEnv* env,
+        ERL_NIF_TERM term, ErlNifResourceType* type, void** objp)</nametext>
+      </name>
+      <fsummary>Get the pointer to a resource object.</fsummary>
+      <desc>
+        <p>Sets <c>*objp</c> to point to the resource object referred to by
+          <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not a handle to a resource object of type <c>type</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_string(ErlNifEnv* env, 
-                                ERL_NIF_TERM list, char* buf, unsigned size,
-                                ErlNifCharEncoding encode)</nametext></name>
-      <fsummary>Get a C-string from a list</fsummary>
-      <desc><p>Write a null-terminated string, in the buffer pointed to by
-              <c>buf</c> with size <c>size</c>, consisting of the characters
-              in the string <c>list</c>. The characters are written using encoding
-              <seealso marker="#ErlNifCharEncoding">encode</seealso>.
-              Return the number of bytes written (including terminating null
-              character), or <c>-size</c> if the string was truncated due to
-              buffer space, or 0 if <c>list</c> is not a string that can be
-              encoded with <c>encode</c> or if <c>size</c> was less than 1.              
-              The written string is always null-terminated unless buffer
-              <c>size</c> is less than 1.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_string(ErlNifEnv* env,
+        ERL_NIF_TERM list, char* buf, unsigned size,
+        ErlNifCharEncoding encode)</nametext></name>
+      <fsummary>Get a C-string from a list.</fsummary>
+      <desc>
+        <p>Writes a <c>NULL</c>-terminated string in the buffer pointed to by
+          <c>buf</c> with size <c>size</c>, consisting of the characters
+          in the string <c>list</c>. The characters are written using encoding
+          <seealso marker="#ErlNifCharEncoding">encode</seealso>.</p>
+        <p>Returns one of the following:</p>
+        <list type="bulleted">
+          <item>The number of bytes written (including terminating <c>NULL</c>
+            character)</item>
+          <item><c>-size</c> if the string was truncated because of buffer
+            space</item>
+          <item><c>0</c> if <c>list</c> is not a string that can be encoded
+            with <c>encode</c> or if <c>size</c> was &lt; <c>1</c>.</item>
+        </list>
+        <p>The written string is always <c>NULL</c>-terminated, unless buffer
+          <c>size</c> is &lt; <c>1</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_tuple(ErlNifEnv* env, ERL_NIF_TERM term, int* arity, const ERL_NIF_TERM** array)</nametext></name>
-      <fsummary>Inspect the elements of a tuple</fsummary>
-      <desc><p>If <c>term</c> is a tuple, set <c>*array</c> to point
-      to an array containing the elements of the tuple and set
-      <c>*arity</c> to the number of elements. Note that the array
-      is read-only and <c>(*array)[N-1]</c> will be the Nth element of
-      the tuple. <c>*array</c> is undefined if the arity of the tuple
-      is zero.</p><p>Return true on success or false if <c>term</c> is not a
-      tuple.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_tuple(ErlNifEnv* env, ERL_NIF_TERM
+        term, int* arity, const ERL_NIF_TERM** array)</nametext></name>
+      <fsummary>Inspect the elements of a tuple.</fsummary>
+      <desc>
+        <p>If <c>term</c> is a tuple, this function sets <c>*array</c> to point
+          to an array containing the elements of the tuple, and sets
+          <c>*arity</c> to the number of elements. Notice that the array
+          is read-only and <c>(*array)[N-1]</c> is the Nth element of
+          the tuple. <c>*array</c> is undefined if the arity of the tuple
+          is zero.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not a tuple.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_uint(ErlNifEnv* env, ERL_NIF_TERM term, unsigned int* ip)</nametext></name>
-      <fsummary>Read an unsigned integer term</fsummary>
-      <desc><p>Set <c>*ip</c> to the unsigned integer value of <c>term</c> and
-      return true, or return false if <c>term</c> is not an unsigned integer or
-      is outside the bounds of type <c>unsigned int</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_uint(ErlNifEnv* env, ERL_NIF_TERM
+        term, unsigned int* ip)</nametext></name>
+      <fsummary>Read an unsigned integer term.</fsummary>
+      <desc>
+        <p>Sets <c>*ip</c> to the unsigned integer value of <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not an unsigned integer or is outside the bounds of type
+          <c>unsigned int</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_uint64(ErlNifEnv* env, ERL_NIF_TERM term, ErlNifUInt64* ip)</nametext></name>
-      <fsummary>Read an unsigned 64-bit integer term</fsummary>
-      <desc><p>Set <c>*ip</c> to the unsigned integer value of <c>term</c> and
-      return true, or return false if <c>term</c> is not an unsigned integer or
-      is outside the bounds of an unsigned 64-bit integer.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_uint64(ErlNifEnv* env,
+        ERL_NIF_TERM term, ErlNifUInt64* ip)</nametext></name>
+      <fsummary>Read an unsigned 64-bit integer term.</fsummary>
+      <desc>
+        <p>Sets <c>*ip</c> to the unsigned integer value of <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not an unsigned integer or is outside the bounds of an unsigned
+          64-bit integer.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_get_ulong(ErlNifEnv* env, ERL_NIF_TERM term, unsigned long* ip)</nametext></name>
-      <fsummary>Read an unsigned integer term</fsummary>
-      <desc><p>Set <c>*ip</c> to the unsigned long integer value of <c>term</c>
-      and return true, or return false if <c>term</c> is not an unsigned integer or is
-      outside the bounds of type <c>unsigned long</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_get_ulong(ErlNifEnv* env, ERL_NIF_TERM
+        term, unsigned long* ip)</nametext></name>
+      <fsummary>Read an unsigned integer term.</fsummary>
+      <desc>
+        <p>Sets <c>*ip</c> to the unsigned long integer value of
+          <c>term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>term</c> is
+          not an unsigned integer or is outside the bounds of type
+          <c>unsigned long</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_getenv(const char* key, char* value, size_t *value_size)</nametext></name>
-      <fsummary>Get the value of an environment variable</fsummary>
-      <desc><p>Same as <seealso marker="erl_driver#erl_drv_getenv">erl_drv_getenv</seealso>.</p></desc>
+      <name><ret>int</ret><nametext>enif_getenv(const char* key, char* value,
+        size_t *value_size)</nametext></name>
+      <fsummary>Get the value of an environment variable.</fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_getenv">
+          <c>erl_drv_getenv</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_has_pending_exception(ErlNifEnv* env, ERL_NIF_TERM* reason)</nametext></name>
-      <fsummary>Check if an exception has been raised</fsummary>
-      <desc><p>Return true if a pending exception is associated
-      with the environment <c>env</c>. If <c>reason</c> is a null pointer, ignore it.
-      Otherwise, if there's a pending exception associated with <c>env</c>, set the ERL_NIF_TERM
-      to which <c>reason</c> points to the value of the exception's term. For example, if
-      <seealso marker="#enif_make_badarg">enif_make_badarg</seealso> is called to set a
-      pending <c>badarg</c> exception, a subsequent call to <c>enif_has_pending_exception(env, &amp;reason)</c>
-      will set <c>reason</c> to the atom <c>badarg</c>, then return true.</p>
-      <p>See also: <seealso marker="#enif_make_badarg">enif_make_badarg</seealso>
-      and <seealso marker="#enif_raise_exception">enif_raise_exception</seealso>.</p>
+      <name><ret>int</ret><nametext>enif_has_pending_exception(ErlNifEnv* env,
+        ERL_NIF_TERM* reason)</nametext></name>
+      <fsummary>Check if an exception has been raised.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if a pending exception is associated with the
+          environment <c>env</c>. If <c>reason</c> is a <c>NULL</c> pointer,
+          ignore it. Otherwise, if a pending exception associated with
+          <c>env</c> exists, set <c>ERL_NIF_TERM</c> to which <c>reason</c>
+          points to the value of the exception's term. For example, if
+          <seealso marker="#enif_make_badarg">
+          <c>enif_make_badarg</c></seealso> is called to set a pending
+          <c>badarg</c> exception, a later call to
+          <c>enif_has_pending_exception(env, &amp;reason)</c> sets
+          <c>reason</c> to the atom <c>badarg</c>, then return <c>true</c>.</p>
+        <p>See also <seealso marker="#enif_make_badarg">
+          <c>enif_make_badarg</c></seealso> and
+          <seealso marker="#enif_raise_exception">
+          <c>enif_raise_exception</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_inspect_binary(ErlNifEnv* env, ERL_NIF_TERM bin_term, ErlNifBinary* bin)</nametext></name>
-      <fsummary>Inspect the content of a binary</fsummary>
-      <desc><p>Initialize the structure pointed to by <c>bin</c> with 
-              information about the binary term
-      <c>bin_term</c>. Return true on success or false if <c>bin_term</c> is not a binary.</p></desc> 
+      <name><ret>int</ret><nametext>enif_inspect_binary(ErlNifEnv* env,
+        ERL_NIF_TERM bin_term, ErlNifBinary* bin)</nametext></name>
+      <fsummary>Inspect the content of a binary.</fsummary>
+      <desc>
+        <p>Initializes the structure pointed to by <c>bin</c> with information
+          about binary term <c>bin_term</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>bin_term</c>
+          is not a binary.</p>
+      </desc> 
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_inspect_iolist_as_binary(ErlNifEnv* 
-                                env, ERL_NIF_TERM term, ErlNifBinary* bin)
-                              </nametext></name>
-      <fsummary>Inspect the content of an iolist</fsummary>
-      <desc><p>Initialize the structure pointed to by <c>bin</c> with one
-      continuous buffer with the same byte content as <c>iolist</c>. As with 
-      inspect_binary, the data pointed to by <c>bin</c> is transient and does 
-      not need to be released. Return true on success or false if <c>iolist</c> is not an
-      iolist.</p>
+      <name><ret>int</ret><nametext>enif_inspect_iolist_as_binary(ErlNifEnv*
+        env, ERL_NIF_TERM term, ErlNifBinary* bin)</nametext></name>
+      <fsummary>Inspect the content of an iolist.</fsummary>
+      <desc>
+        <p>Initializes the structure pointed to by <c>bin</c> with a
+          continuous buffer with the same byte content as <c>iolist</c>. As
+          with <c>inspect_binary</c>, the data pointed to by <c>bin</c> is
+          transient and does not need to be released.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>iolist</c> is
+          not an iolist.</p>
       </desc> 
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_atom(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is an atom</fsummary>
-      <desc><p>Return true if <c>term</c> is an atom.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_atom(ErlNifEnv* env, ERL_NIF_TERM term)</nametext>
+      </name>
+      <fsummary>Determine if a term is an atom.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is an atom.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_binary(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a binary</fsummary>
-      <desc><p>Return true if <c>term</c> is a binary</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_binary(ErlNifEnv* env, ERL_NIF_TERM term)</nametext>
+      </name>
+      <fsummary>Determine if a term is a binary.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a binary.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_current_process_alive(ErlNifEnv* env)</nametext></name>
-      <fsummary>Determine if currently executing process is alive or not.</fsummary>
-      <desc><p>Return true if currently executing process is currently alive; otherwise
-      false.</p>
-      <p>This function can only be used from a NIF-calling thread, and with an
-      environment corresponding to currently executing processes.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_current_process_alive(ErlNifEnv* env)</nametext>
+      </name>
+      <fsummary>Determine if currently executing process is alive.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if the currently executing process is currently
+          alive, otherwise <c>false</c>.</p>
+        <p>This function can only be used from a NIF-calling thread, and with
+          an environment corresponding to currently executing processes.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_empty_list(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is an empty list</fsummary>
-      <desc><p>Return true if <c>term</c> is an empty list.</p></desc>
+      <name><ret>int</ret><nametext>enif_is_empty_list(ErlNifEnv* env,
+        ERL_NIF_TERM term)</nametext></name>
+      <fsummary>Determine if a term is an empty list.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is an empty list.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_exception(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is an exception</fsummary>
+      <name><ret>int</ret><nametext>enif_is_exception(ErlNifEnv* env,
+        ERL_NIF_TERM term)</nametext></name>
+      <fsummary>Determine if a term is an exception.</fsummary>
       <desc><marker id="enif_is_exception"/>
-        <p>Return true if <c>term</c> is an exception.</p></desc>
+      <p>Return true if <c>term</c> is an exception.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_fun(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a fun</fsummary>
-      <desc><p>Return true if <c>term</c> is a fun.</p></desc>
+      <name><ret>int</ret><nametext>enif_is_fun(ErlNifEnv* env, ERL_NIF_TERM
+        term)</nametext></name>
+      <fsummary>Determine if a term is a fun.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a fun.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_identical(ERL_NIF_TERM lhs, ERL_NIF_TERM rhs)</nametext></name>
-      <fsummary>Erlang operator =:=</fsummary>
-      <desc><p>Return true if the two terms are identical. Corresponds to the
-      Erlang operators <c>=:=</c> and
-      <c>=/=</c>.</p></desc> 
+      <name><ret>int</ret><nametext>enif_is_identical(ERL_NIF_TERM lhs,
+        ERL_NIF_TERM rhs)</nametext></name>
+      <fsummary>Erlang operator =:=.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if the two terms are identical. Corresponds to
+          the Erlang operators <c>=:=</c> and <c>=/=</c>.</p>
+      </desc> 
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_list(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a list</fsummary>
-      <desc><p>Return true if <c>term</c> is a list.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_list(ErlNifEnv* env, ERL_NIF_TERM term)</nametext>
+      </name>
+      <fsummary>Determine if a term is a list.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a list.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_map(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a map</fsummary>
-      <desc><p>Return true if <c>term</c> is a map, false otherwise.</p></desc>
+      <name><ret>int</ret><nametext>enif_is_map(ErlNifEnv* env, ERL_NIF_TERM
+        term)</nametext></name>
+      <fsummary>Determine if a term is a map.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a map, otherwise
+          <c>false</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_number(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a number (integer or float)</fsummary>
-      <desc><p>Return true if <c>term</c> is a number.</p></desc>
+      <name><ret>int</ret><nametext>enif_is_number(ErlNifEnv* env, ERL_NIF_TERM
+        term)</nametext></name>
+      <fsummary>Determine if a term is a number (integer or float).</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a number.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_pid(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a pid</fsummary>
-      <desc><p>Return true if <c>term</c> is a pid.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_pid(ErlNifEnv* env, ERL_NIF_TERM term)</nametext>
+      </name>
+      <fsummary>Determine if a term is a pid.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a pid.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_port(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a port</fsummary>
-      <desc><p>Return true if <c>term</c> is a port.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_port(ErlNifEnv* env, ERL_NIF_TERM term)</nametext>
+      </name>
+      <fsummary>Determine if a term is a port.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a port.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_port_alive(ErlNifEnv* env, ErlNifPort *port_id)</nametext></name>
-      <fsummary>Determine if a local port is alive or not.</fsummary>
-      <desc><p>Return true if <c>port_id</c> is currently alive.</p>
-      <p>This function is only thread-safe when the emulator with SMP support is used.
-      It can only be used in a non-SMP emulator from a NIF-calling thread.</p></desc>
+      <name><ret>int</ret><nametext>enif_is_port_alive(ErlNifEnv* env,
+        ErlNifPort *port_id)</nametext></name>
+      <fsummary>Determine if a local port is alive.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>port_id</c> is alive.</p>
+        <p>This function is only thread-safe when the emulator with SMP support
+          is used. It can only be used in a non-SMP emulator from a NIF-calling
+          thread.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_process_alive(ErlNifEnv* env, ErlNifPid *pid)</nametext></name>
-      <fsummary>Determine if a local process is alive or not.</fsummary>
-      <desc><p>Return true if <c>pid</c> is currently alive.</p>
-      <p>This function is only thread-safe when the emulator with SMP support is used.
-      It can only be used in a non-SMP emulator from a NIF-calling thread.</p></desc>
+      <name><ret>int</ret><nametext>enif_is_process_alive(ErlNifEnv* env,
+        ErlNifPid *pid)</nametext></name>
+      <fsummary>Determine if a local process is alive.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>pid</c> is alive.</p>
+        <p>This function is only thread-safe when the emulator with SMP support
+          is used. It can only be used in a non-SMP emulator from a NIF-calling
+          thread.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_ref(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a reference</fsummary>
-      <desc><p>Return true if <c>term</c> is a reference.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_ref(ErlNifEnv* env, ERL_NIF_TERM term)</nametext>
+      </name>
+      <fsummary>Determine if a term is a reference.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a reference.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_is_tuple(ErlNifEnv* env, ERL_NIF_TERM term)</nametext></name>
-      <fsummary>Determine if a term is a tuple</fsummary>
-      <desc><p>Return true if <c>term</c> is a tuple.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_is_tuple(ErlNifEnv* env, ERL_NIF_TERM term)</nametext>
+      </name>
+      <fsummary>Determine if a term is a tuple.</fsummary>
+      <desc>
+        <p>Returns <c>true</c> if <c>term</c> is a tuple.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_keep_resource(void* obj)</nametext></name>
-      <fsummary>Add a reference to a resource object</fsummary>
-      <desc><p>Add a reference to resource object <c>obj</c> obtained from
-      <seealso marker="#enif_alloc_resource">enif_alloc_resource</seealso>.
-      Each call to <c>enif_keep_resource</c> for an object must be balanced by
-      a call to <seealso marker="#enif_release_resource">enif_release_resource</seealso>
-      before the object will be destructed.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_keep_resource(void* obj)</nametext>
+      </name>
+      <fsummary>Add a reference to a resource object.</fsummary>
+      <desc>
+        <p>Adds a reference to resource object <c>obj</c> obtained from
+          <seealso marker="#enif_alloc_resource">
+          <c>enif_alloc_resource</c></seealso>. Each call to
+          <c>enif_keep_resource</c> for an object must be balanced by a call to
+          <seealso marker="#enif_release_resource">
+          <c>enif_release_resource</c></seealso>
+          before the object is destructed.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_atom(ErlNifEnv* env, const char* name)</nametext></name>
-      <fsummary>Create an atom term</fsummary>
-      <desc><p>Create an atom term from the null-terminated C-string <c>name</c>
-      with iso-latin-1 encoding. If the length of <c>name</c> exceeds the maximum length
-      allowed for an atom (255 characters), <c>enif_make_atom</c> invokes
-      <seealso marker="#enif_make_badarg">enif_make_badarg</seealso>.
-      </p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_atom(ErlNifEnv* env, const char* name)</nametext>
+      </name>
+      <fsummary>Create an atom term.</fsummary>
+      <desc>
+        <p>Creates an atom term from the <c>NULL</c>-terminated C-string
+          <c>name</c> with ISO Latin-1 encoding. If the length of <c>name</c>
+          exceeds the maximum length allowed for an atom (255 characters),
+          <c>enif_make_atom</c> invokes <seealso marker="#enif_make_badarg">
+          <c>enif_make_badarg</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_atom_len(ErlNifEnv* env, const char* name, size_t len)</nametext></name>
-      <fsummary>Create an atom term</fsummary>
-      <desc><p>Create an atom term from the string <c>name</c> with length <c>len</c>.
-      Null-characters are treated as any other characters. If <c>len</c> is greater than the maximum length
-      allowed for an atom (255 characters), <c>enif_make_atom</c> invokes
-      <seealso marker="#enif_make_badarg">enif_make_badarg</seealso>.
-      </p></desc>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_atom_len(ErlNifEnv* env,
+        const char* name, size_t len)</nametext></name>
+      <fsummary>Create an atom term.</fsummary>
+      <desc>
+        <p>Create an atom term from the string <c>name</c> with length
+          <c>len</c>. <c>NULL</c> characters are treated as any other
+          characters. If <c>len</c> exceeds the maximum length
+          allowed for an atom (255 characters), <c>enif_make_atom</c> invokes
+          <seealso marker="#enif_make_badarg">
+          <c>enif_make_badarg</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_badarg(ErlNifEnv* env)</nametext></name>
-      <fsummary>Make a badarg exception</fsummary>
-      <desc><p>Make a badarg exception to be returned from a NIF, and associate
-      it with the environment <c>env</c>. Once a NIF or any function
-      it calls invokes <c>enif_make_badarg</c>, the runtime ensures that a
-      <c>badarg</c> exception is raised when the NIF returns, even if the NIF
-      attempts to return a non-exception term instead.
-      The return value from <c>enif_make_badarg</c> may be used only as the
-      return value from the NIF that invoked it (directly or indirectly)
-      or be passed to
-      <seealso marker="#enif_is_exception">enif_is_exception</seealso>, but
-      not to any other NIF API function.</p>
-      <p>See also: <seealso marker="#enif_has_pending_exception">enif_has_pending_exception</seealso>
-      and <seealso marker="#enif_raise_exception">enif_raise_exception</seealso>.
-      </p>
-      <note><p>In earlier versions (older than erts-7.0, OTP 18) the return value
-      from <c>enif_make_badarg</c> had to be returned from the NIF. This
-      requirement is now lifted as the return value from the NIF is ignored
-      if <c>enif_make_badarg</c> has been invoked.</p></note></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_badarg(ErlNifEnv* env)</nametext></name>
+      <fsummary>Make a badarg exception.</fsummary>
+      <desc>
+        <p>Makes a <c>badarg</c> exception to be returned from a NIF, and
+          associates it with environment <c>env</c>. Once a NIF or any function
+          it calls invokes <c>enif_make_badarg</c>, the runtime ensures that a
+          <c>badarg</c> exception is raised when the NIF returns, even if the
+          NIF attempts to return a non-exception term instead.</p>
+        <p>The return value from <c>enif_make_badarg</c> can be used only as
+          the return value from the NIF that invoked it (directly or indirectly)
+          or be passed to <seealso marker="#enif_is_exception">
+          <c>enif_is_exception</c></seealso>, but not to any other NIF API
+          function.</p>
+        <p>See also <seealso marker="#enif_has_pending_exception">
+          <c>enif_has_pending_exception</c></seealso> and
+          <seealso marker="#enif_raise_exception">
+          <c>enif_raise_exception</c></seealso>.</p>
+        <note>
+          <p>Before <c>ERTS</c> 7.0 (Erlang/OTP 18), the return value
+            from <c>enif_make_badarg</c> had to be returned from the NIF. This
+            requirement is now lifted as the return value from the NIF is
+            ignored if <c>enif_make_badarg</c> has been invoked.</p>
+        </note>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_binary(ErlNifEnv* env, ErlNifBinary* bin)</nametext></name>
-      <fsummary>Make a binary term</fsummary>
-      <desc><p>Make a binary term from <c>bin</c>. Any ownership of 
-              the binary data will be transferred to the created term and
-              <c>bin</c> should be considered read-only for the rest of the NIF
-              call and then as released.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_binary(ErlNifEnv* env, ErlNifBinary* bin)</nametext>
+      </name>
+      <fsummary>Make a binary term.</fsummary>
+      <desc>
+        <p>Makes a binary term from <c>bin</c>. Any ownership of
+          the binary data is transferred to the created term and
+          <c>bin</c> is to be considered read-only for the rest of the NIF
+          call and then as released.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_copy(ErlNifEnv* dst_env, ERL_NIF_TERM src_term)</nametext></name>
-      <fsummary>Make a copy of a term</fsummary>
-      <desc><p>Make a copy of term <c>src_term</c>. The copy will be created in
-      environment <c>dst_env</c>. The source term may be located in any
-      environment.</p></desc>        
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_copy(ErlNifEnv* dst_env,
+        ERL_NIF_TERM src_term)</nametext></name>
+      <fsummary>Make a copy of a term.</fsummary>
+      <desc>
+        <p>Makes a copy of term <c>src_term</c>. The copy is created in
+          environment <c>dst_env</c>. The source term can be located in any
+          environment.</p>
+      </desc>        
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_double(ErlNifEnv* env, double d)</nametext></name>
-      <fsummary>Create a floating-point term</fsummary>
-      <desc><p>Create a floating-point term from a <c>double</c>. If the <c>double</c> argument is
-      not finite or is NaN, <c>enif_make_double</c> invokes
-      <seealso marker="#enif_make_badarg">enif_make_badarg</seealso>.
-      </p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_double(ErlNifEnv* env, double d)</nametext></name>
+      <fsummary>Create a floating-point term.</fsummary>
+      <desc>
+        <p>Creates a floating-point term from a <c>double</c>. If argument
+          <c>double</c> is not finite or is NaN, <c>enif_make_double</c>
+          invokes <seealso marker="#enif_make_badarg">
+          <c>enif_make_badarg</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_make_existing_atom(ErlNifEnv* env, const char* name, ERL_NIF_TERM* atom, ErlNifCharEncoding encode)</nametext></name>
-      <fsummary>Create an existing atom term</fsummary>
-      <desc><p>Try to create the term of an already existing atom from
-      the null-terminated C-string <c>name</c> with encoding
-      <seealso marker="#ErlNifCharEncoding">encode</seealso>. If the atom
-      already exists store the term in <c>*atom</c> and return true, otherwise
-      return false. If the length of <c>name</c> exceeds the maximum length
-      allowed for an atom (255 characters), <c>enif_make_existing_atom</c>
-      returns false.</p></desc>
+      <name><ret>int</ret><nametext>enif_make_existing_atom(ErlNifEnv* env,
+        const char* name, ERL_NIF_TERM* atom, ErlNifCharEncoding
+        encode)</nametext></name>
+      <fsummary>Create an existing atom term.</fsummary>
+      <desc>
+        <p>Tries to create the term of an already existing atom from
+          the <c>NULL</c>-terminated C-string <c>name</c> with encoding
+          <seealso marker="#ErlNifCharEncoding">encode</seealso>.</p>
+        <p>If the atom already exists, this function stores the term in
+          <c>*atom</c> and returns <c>true</c>, otherwise <c>false</c>.
+          Also returns <c>false</c> if the length of <c>name</c> exceeds the
+          maximum length allowed for an atom (255 characters).</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_make_existing_atom_len(ErlNifEnv* env, const char* name, size_t len, ERL_NIF_TERM* atom, ErlNifCharEncoding encoding)</nametext></name>
-      <fsummary>Create an existing atom term</fsummary>
-      <desc><p>Try to create the term of an already existing atom from the
-      string <c>name</c> with length <c>len</c> and encoding
-      <seealso marker="#ErlNifCharEncoding">encode</seealso>. Null-characters
-      are treated as any other characters. If the atom already exists store the term
-      in <c>*atom</c> and return true, otherwise return false. If <c>len</c> is greater
-      than the maximum length allowed for an atom (255 characters),
-      <c>enif_make_existing_atom_len</c> returns false.</p></desc>
+      <name><ret>int</ret><nametext>enif_make_existing_atom_len(ErlNifEnv* env,
+        const char* name, size_t len, ERL_NIF_TERM* atom, ErlNifCharEncoding
+        encoding)</nametext></name>
+      <fsummary>Create an existing atom term.</fsummary>
+      <desc>
+        <p>Tries to create the term of an already existing atom from the
+          string <c>name</c> with length <c>len</c> and encoding
+          <seealso marker="#ErlNifCharEncoding">encode</seealso>. <c>NULL</c>
+          characters are treated as any other characters.</p>
+        <p>If the atom already exists, this function stores the term in
+          <c>*atom</c> and returns <c>true</c>, otherwise <c>false</c>.
+          Also returns <c>false</c> if <c>len</c> exceeds the maximum length
+          allowed for an atom (255 characters).</p>
+      </desc>
     </func>
 
-    <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_int(ErlNifEnv* env, int i)</nametext></name>
-      <fsummary>Create an integer term</fsummary>
-      <desc><p>Create an integer term.</p></desc>
+    <func><name><ret>ERL_NIF_TERM</ret>
+      <nametext>enif_make_int(ErlNifEnv* env, int i)</nametext></name>
+      <fsummary>Create an integer term.</fsummary>
+      <desc>
+        <p>Creates an integer term.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_int64(ErlNifEnv* env, ErlNifSInt64 i)</nametext></name>
-      <fsummary>Create an integer term</fsummary>
-      <desc><p>Create an integer term from a signed 64-bit integer.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_int64(ErlNifEnv* env, ErlNifSInt64 i)</nametext>
+      </name>
+      <fsummary>Create an integer term.</fsummary>
+      <desc>
+        <p>Creates an integer term from a signed 64-bit integer.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list(ErlNifEnv* env, unsigned cnt, ...)</nametext></name>
-      <fsummary>Create a list term</fsummary>
-      <desc><p>Create an ordinary list term of length <c>cnt</c>. Expects
-      <c>cnt</c> number of arguments (after <c>cnt</c>) of type ERL_NIF_TERM as the
-      elements of the list. An empty list is returned if <c>cnt</c> is 0.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_list(ErlNifEnv* env, unsigned cnt, ...)</nametext>
+      </name>
+      <fsummary>Create a list term.</fsummary>
+      <desc>
+        <p>Creates an ordinary list term of length <c>cnt</c>. Expects
+          <c>cnt</c> number of arguments (after <c>cnt</c>) of type
+          <c>ERL_NIF_TERM</c> as the elements of the list.</p>
+        <p>Returns an empty list if <c>cnt</c> is 0.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list1(ErlNifEnv* env, ERL_NIF_TERM e1)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list2(ErlNifEnv* env, ERL_NIF_TERM e1, ERL_NIF_TERM e2)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list3(ErlNifEnv* env, ERL_NIF_TERM e1, ERL_NIF_TERM e2, ERL_NIF_TERM e3)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list4(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e4)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list5(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e5)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list6(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e6)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list7(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e7)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list8(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e8)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list9(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e9)</nametext></name>
-      <fsummary>Create a list term</fsummary>
-      <desc><p>Create an ordinary list term with length indicated by the
-      function name. Prefer these functions (macros) over the variadic
-      <c>enif_make_list</c>  to get a compile time error if the number of
-      arguments does not match.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_list1(ErlNifEnv* env, ERL_NIF_TERM e1)</nametext>
+      </name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list2(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ERL_NIF_TERM e2)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list3(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ERL_NIF_TERM e2, ERL_NIF_TERM e3)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list4(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e4)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list5(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e5)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list6(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e6)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list7(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e7)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list8(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e8)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list9(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e9)</nametext></name>
+      <fsummary>Create a list term.</fsummary>
+      <desc>
+        <p>Creates an ordinary list term with length indicated by the
+          function name. Prefer these functions (macros) over the variadic
+          <c>enif_make_list</c> to get a compile-time error if the number of
+          arguments does not match.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list_cell(ErlNifEnv* env, ERL_NIF_TERM head, ERL_NIF_TERM tail)</nametext></name>
-      <fsummary>Create a list cell</fsummary>
-      <desc><p>Create a list cell <c>[head | tail]</c>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list_cell(ErlNifEnv*
+        env, ERL_NIF_TERM head, ERL_NIF_TERM tail)</nametext></name>
+      <fsummary>Create a list cell.</fsummary>
+      <desc>
+        <p>Creates a list cell <c>[head | tail]</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_list_from_array(ErlNifEnv* env, const ERL_NIF_TERM arr[], unsigned cnt)</nametext></name>
-      <fsummary>Create a list term from an array</fsummary>
-      <desc><p>Create an ordinary list containing the elements of array <c>arr</c>
-      of length <c>cnt</c>. An empty list is returned if <c>cnt</c> is 0.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_list_from_array(ErlNifEnv* env, const ERL_NIF_TERM
+          arr[], unsigned cnt)</nametext></name>
+      <fsummary>Create a list term from an array.</fsummary>
+      <desc>
+        <p>Creates an ordinary list containing the elements of array <c>arr</c>
+          of length <c>cnt</c>.</p>
+        <p>Returns an empty list if <c>cnt</c> is 0.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_long(ErlNifEnv* env, long int i)</nametext></name>
-      <fsummary>Create an integer term from a long int</fsummary>
-      <desc><p>Create an integer term from a <c>long int</c>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_long(ErlNifEnv* env, long int i)</nametext></name>
+      <fsummary>Create an integer term from a long int.</fsummary>
+      <desc>
+        <p>Creates an integer term from a <c>long int</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_make_map_put(ErlNifEnv* env, ERL_NIF_TERM map_in, ERL_NIF_TERM key, ERL_NIF_TERM value, ERL_NIF_TERM* map_out)</nametext></name>
-      <fsummary>Insert key-value pair in map</fsummary>
-      <desc><p>Make a copy of map <c>map_in</c> and insert <c>key</c> with
-      <c>value</c>. If <c>key</c> already exists in <c>map_in</c>, the old
-      associated value is replaced by <c>value</c>. If successful set
-      <c>*map_out</c> to the new map and return true. Return false if
-      <c>map_in</c> is not a map.</p>
-      <p>The <c>map_in</c> term must belong to the environment <c>env</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_make_map_put(ErlNifEnv* env,
+        ERL_NIF_TERM map_in, ERL_NIF_TERM key, ERL_NIF_TERM value,
+        ERL_NIF_TERM* map_out)</nametext></name>
+      <fsummary>Insert key-value pair in map.</fsummary>
+      <desc>
+        <p>Makes a copy of map <c>map_in</c> and inserts <c>key</c> with
+          <c>value</c>. If <c>key</c> already exists in <c>map_in</c>, the old
+          associated value is replaced by <c>value</c>.</p>
+        <p>If successful, this function sets <c>*map_out</c> to the new map and
+          returns <c>true</c>. Returns <c>false</c> if <c>map_in</c> is not a
+          map.</p>
+        <p>The <c>map_in</c> term must belong to environment <c>env</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_make_map_remove(ErlNifEnv* env, ERL_NIF_TERM map_in, ERL_NIF_TERM key, ERL_NIF_TERM* map_out)</nametext></name>
-      <fsummary>Remove key from map</fsummary>
-      <desc><p>If map <c>map_in</c> contains <c>key</c>, make a copy of
-      <c>map_in</c> in <c>*map_out</c> and remove <c>key</c> and associated
-      value. If map <c>map_in</c> does not contain <c>key</c>, set
-      <c>*map_out</c> to <c>map_in</c>. Return true for success or false if
-      <c>map_in</c> is not a map.</p>
-      <p>The <c>map_in</c> term must belong to the environment <c>env</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_make_map_remove(ErlNifEnv* env,
+        ERL_NIF_TERM map_in, ERL_NIF_TERM key, ERL_NIF_TERM* map_out)</nametext>
+      </name>
+      <fsummary>Remove key from map.</fsummary>
+      <desc>
+        <p>If map <c>map_in</c> contains <c>key</c>, this function makes a copy
+          of <c>map_in</c> in <c>*map_out</c>, and removes <c>key</c> and the
+          associated value. If map <c>map_in</c> does not contain <c>key</c>,
+          <c>*map_out</c> is set to <c>map_in</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if <c>map_in</c> is
+          not a map.</p>
+        <p>The <c>map_in</c> term must belong to environment <c>env</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_make_map_update(ErlNifEnv* env, ERL_NIF_TERM map_in, ERL_NIF_TERM key, ERL_NIF_TERM new_value, ERL_NIF_TERM* map_out)</nametext></name>
-      <fsummary>Replace value for key in map</fsummary>
-      <desc><p>Make a copy of map <c>map_in</c> and replace the old associated
-      value for <c>key</c> with <c>new_value</c>. If successful set
-      <c>*map_out</c> to the new map and return true. Return false if
-      <c>map_in</c> is not a map or if it does no contain <c>key</c>.</p>
-      <p>The <c>map_in</c> term must belong to the environment <c>env</c>.</p></desc>
+      <name><ret>int</ret><nametext>enif_make_map_update(ErlNifEnv* env,
+        ERL_NIF_TERM map_in, ERL_NIF_TERM key, ERL_NIF_TERM new_value,
+        ERL_NIF_TERM* map_out)</nametext></name>
+      <fsummary>Replace value for key in map.</fsummary>
+      <desc>
+        <p>Makes a copy of map <c>map_in</c> and replace the old associated
+          value for <c>key</c> with <c>new_value</c>.</p>
+        <p>If successful, this function sets <c>*map_out</c> to the new map and
+          returns <c>true</c>. Returns <c>false</c> if <c>map_in</c> is not a
+          map or if it does not contain <c>key</c>.</p>
+        <p>The <c>map_in</c> term must belong to environment <c>env</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>unsigned char *</ret><nametext>enif_make_new_binary(ErlNifEnv* env, size_t size, ERL_NIF_TERM* termp)</nametext></name>
-      <fsummary>Allocate and create a new binary term</fsummary>
-      <desc><p>Allocate a binary of size <c>size</c> bytes and create an owning
-      term. The binary data is mutable until the calling NIF returns. This is a
-      quick way to create a new binary without having to use
-      <seealso marker="#ErlNifBinary">ErlNifBinary</seealso>. The drawbacks are
-      that the binary can not be kept between NIF calls and it can not be
-      reallocated.</p><p>Return a pointer to the raw binary data and set
-      <c>*termp</c> to the binary term.</p></desc>
+      <name><ret>unsigned char *</ret><nametext>enif_make_new_binary(ErlNifEnv*
+        env, size_t size, ERL_NIF_TERM* termp)</nametext></name>
+      <fsummary>Allocate and create a new binary term.</fsummary>
+      <desc>
+        <p>Allocates a binary of size <c>size</c> bytes and creates an owning
+          term. The binary data is mutable until the calling NIF returns.
+          This is a quick way to create a new binary without having to use
+          <seealso marker="#ErlNifBinary"><c>ErlNifBinary</c></seealso>.
+          The drawbacks are that the binary cannot be kept between NIF calls
+          and it cannot be reallocated.</p>
+        <p>Returns a pointer to the raw binary data and sets
+          <c>*termp</c> to the binary term.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_new_map(ErlNifEnv* env)</nametext></name>
-      <fsummary>Make an empty map term</fsummary>
-      <desc><p>Make an empty map term.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_new_map(ErlNifEnv* env)</nametext></name>
+      <fsummary>Make an empty map term.</fsummary>
+      <desc>
+        <p>Makes an empty map term.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_pid(ErlNifEnv* env, const ErlNifPid* pid)</nametext></name>
-      <fsummary>Make a pid term</fsummary>
-      <desc><p>Make a pid term from <c>*pid</c>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_pid(ErlNifEnv* env, const ErlNifPid* pid)</nametext>
+      </name>
+      <fsummary>Make a pid term.</fsummary>
+      <desc>
+        <p>Makes a pid term from <c>*pid</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_ref(ErlNifEnv* env)</nametext></name>
-      <fsummary>Create a reference</fsummary>
-      <desc><p>Create a reference like <seealso marker="erlang#make_ref-0">erlang:make_ref/0</seealso>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_ref(ErlNifEnv* env)</nametext></name>
+      <fsummary>Create a reference.</fsummary>
+      <desc>
+        <p>Creates a reference like <seealso marker="erlang#make_ref-0">
+          <c>erlang:make_ref/0</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_resource(ErlNifEnv* env, void* obj)</nametext></name>
-      <fsummary>Create an opaque handle to a resource object</fsummary>
-      <desc><p>Create an opaque handle to a memory managed resource object
-      obtained by <seealso marker="#enif_alloc_resource">enif_alloc_resource</seealso>.
-      No ownership transfer is done, as the resource object still needs to be released by
-      <seealso marker="#enif_release_resource">enif_release_resource</seealso>,
-      but note that the call to <c>enif_release_resource</c> can occur
-      immediately after obtaining the term from <c>enif_make_resource</c>,
-      in which case the resource object will be deallocated when the
-      term is garbage collected. See the
-      <seealso marker="#enif_resource_example">example of creating and
-      returning a resource object</seealso> for more details.</p> 
-      <p>Note that the only defined behaviour of using a resource term in
-      an Erlang program is to store it and send it between processes on the
-      same node. Other operations such as matching or <c>term_to_binary</c>
-      will have unpredictable (but harmless) results.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_resource(ErlNifEnv* env, void* obj)</nametext>
+      </name>
+      <fsummary>Create an opaque handle to a resource object.</fsummary>
+      <desc>
+        <p>Creates an opaque handle to a memory-managed resource object
+          obtained by <seealso marker="#enif_alloc_resource">
+          <c>enif_alloc_resource</c></seealso>. No ownership transfer is done,
+          as the resource object still needs to be released by
+          <seealso marker="#enif_release_resource">
+          <c>enif_release_resource</c></seealso>. However, notice that the call
+          to <c>enif_release_resource</c> can occur immediately after obtaining
+          the term from <c>enif_make_resource</c>, in which case the resource
+          object is deallocated when the term is garbage collected. For more
+          details, see the <seealso marker="#enif_resource_example">example of
+          creating and returning a resource object</seealso> in the User's
+          Guide.</p>
+        <p>Notice that the only defined behavior of using a resource term in
+          an Erlang program is to store it and send it between processes on the
+          same node. Other operations, such as matching or
+          <c>term_to_binary</c>, have unpredictable (but harmless) results.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_resource_binary(ErlNifEnv* env, void* obj, const void* data, size_t size)</nametext></name>
-      <fsummary>Create a custom binary term</fsummary>
-      <desc><p>Create a binary term that is memory managed by a resource object
-      <c>obj</c> obtained by <seealso marker="#enif_alloc_resource">enif_alloc_resource</seealso>.
-      The returned binary term will consist of <c>size</c> bytes pointed to
-      by <c>data</c>. This raw binary data must be kept readable and unchanged
-      until the destructor of the resource is called. The binary data may be
-      stored external to the resource object in which case it is the responsibility
-      of the destructor to release the data.</p>
-      <p>Several binary terms may be managed by the same resource object. The
-      destructor will not be called until the last binary is garbage collected.
-      This can be useful as a way to return different parts of a larger binary
-      buffer.</p>
-      <p>As with <seealso marker="#enif_make_resource">enif_make_resource</seealso>,
-      no ownership transfer is done. The resource still needs to be released with
-      <seealso marker="#enif_release_resource">enif_release_resource</seealso>.</p>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_resource_binary(ErlNifEnv* env, void* obj, const
+        void* data, size_t size)</nametext></name>
+      <fsummary>Create a custom binary term.</fsummary>
+      <desc>
+        <p>Creates a binary term that is memory-managed by a resource object
+          <c>obj</c> obtained by <seealso marker="#enif_alloc_resource">
+          <c>enif_alloc_resource</c></seealso>. The returned binary term
+          consists of <c>size</c> bytes pointed to by <c>data</c>. This raw
+          binary data must be kept readable and unchanged until the destructor
+          of the resource is called. The binary data can be stored external to
+          the resource object, in which case the destructor is responsible
+          for releasing the data.</p>
+        <p>Several binary terms can be managed by the same resource object. The
+          destructor is not called until the last binary is garbage collected.
+          This can be useful to return different parts of a larger binary
+          buffer.</p>
+        <p>As with <seealso marker="#enif_make_resource">
+          <c>enif_make_resource</c></seealso>, no ownership transfer is done.
+          The resource still needs to be released with
+          <seealso marker="#enif_release_resource">
+          <c>enif_release_resource</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_make_reverse_list(ErlNifEnv* env, ERL_NIF_TERM list_in, ERL_NIF_TERM *list_out)</nametext></name>
-      <fsummary>Create the reverse of a list</fsummary>
-      <desc><p>Set <c>*list_out</c> to the reverse list of the list <c>list_in</c> and return true,
-      or return false if <c>list_in</c> is not a list. This function should only be used on
-      short lists as a copy will be created of the list which will not be released until after the
-      nif returns.</p>
-      <p>The <c>list_in</c> term must belong to the environment <c>env</c>.</p></desc>
+      <name><ret>int</ret>
+        <nametext>enif_make_reverse_list(ErlNifEnv* env, ERL_NIF_TERM list_in,
+        ERL_NIF_TERM *list_out)</nametext></name>
+      <fsummary>Create the reverse of a list.</fsummary>
+      <desc>
+        <p>Sets <c>*list_out</c> to the reverse list of the list <c>list_in</c>
+          and returns <c>true</c>, or returns <c>false</c> if <c>list_in</c> is
+          not a list.</p>
+        <p>This function is only to be used on short lists, as a copy is
+          created of the list, which is not released until after the NIF
+          returns.</p>
+        <p>The <c>list_in</c> term must belong to environment <c>env</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_string(ErlNifEnv* env, const char* string, ErlNifCharEncoding encoding)</nametext></name>
-      <fsummary>Create a string</fsummary>
-      <desc><p>Create a list containing the characters of the
-      null-terminated string <c>string</c> with encoding <seealso marker="#ErlNifCharEncoding">encoding</seealso>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_string(ErlNifEnv* env,
+        const char* string, ErlNifCharEncoding encoding)</nametext></name>
+      <fsummary>Create a string.</fsummary>
+      <desc>
+        <p>Creates a list containing the characters of the
+          <c>NULL</c>-terminated string <c>string</c> with encoding
+          <seealso marker="#ErlNifCharEncoding">encoding</seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_string_len(ErlNifEnv* env, const char* string, size_t len, ErlNifCharEncoding encoding)</nametext></name>
-      <fsummary>Create a string</fsummary>
-      <desc><p>Create a list containing the characters of the string <c>string</c> with
-      length <c>len</c> and encoding <seealso marker="#ErlNifCharEncoding">encoding</seealso>.
-      Null-characters are treated as any other characters.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_string_len(ErlNifEnv*
+        env, const char* string, size_t len, ErlNifCharEncoding
+        encoding)</nametext></name>
+      <fsummary>Create a string.</fsummary>
+      <desc>
+        <p>Creates a list containing the characters of the string <c>string</c>
+          with length <c>len</c> and encoding
+          <seealso marker="#ErlNifCharEncoding">encoding</seealso>.
+          <c>NULL</c> characters are treated as any other characters.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_sub_binary(ErlNifEnv* 
-      env, ERL_NIF_TERM bin_term, size_t pos, size_t size)</nametext></name>
-      <fsummary>Make a subbinary term</fsummary>
-      <desc><p>Make a subbinary of binary <c>bin_term</c>, starting at 
-              zero-based position <c>pos</c> with a length of <c>size</c> bytes. 
-              <c>bin_term</c> must be a binary or bitstring and
-              <c>pos+size</c> must be less or equal to the number of whole
-              bytes in <c>bin_term</c>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_sub_binary(ErlNifEnv*
+        env, ERL_NIF_TERM bin_term, size_t pos, size_t size)</nametext></name>
+      <fsummary>Make a subbinary term.</fsummary>
+      <desc>
+        <p>Makes a subbinary of binary <c>bin_term</c>, starting at
+          zero-based position <c>pos</c> with a length of <c>size</c> bytes.
+          <c>bin_term</c> must be a binary or bitstring. <c>pos+size</c> must
+          be less or equal to the number of whole bytes in <c>bin_term</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple(ErlNifEnv* env, unsigned cnt, ...)</nametext></name>
-      <fsummary>Create a tuple term</fsummary>
-      <desc><p>Create a tuple term of arity <c>cnt</c>. Expects
-      <c>cnt</c> number of arguments (after <c>cnt</c>) of type ERL_NIF_TERM as the
-      elements of the tuple.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple(ErlNifEnv* env,
+        unsigned cnt, ...)</nametext></name>
+      <fsummary>Creates a tuple term.</fsummary>
+      <desc>
+        <p>Creates a tuple term of arity <c>cnt</c>. Expects <c>cnt</c> number
+          of arguments (after <c>cnt</c>) of type <c>ERL_NIF_TERM</c> as the
+          elements of the tuple.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple1(ErlNifEnv* env, ERL_NIF_TERM e1)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple2(ErlNifEnv* env, ERL_NIF_TERM e1, ERL_NIF_TERM e2)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple3(ErlNifEnv* env, ERL_NIF_TERM e1, ERL_NIF_TERM e2, ERL_NIF_TERM e3)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple4(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e4)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple5(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e5)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple6(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e6)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple7(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e7)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple8(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e8)</nametext></name>
-    <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple9(ErlNifEnv* env, ERL_NIF_TERM e1, ..., ERL_NIF_TERM e9)</nametext></name>
-      <fsummary>Create a tuple term</fsummary>
-      <desc><p>Create a tuple term with length indicated by the
-      function name. Prefer these functions (macros) over the variadic
-      <c>enif_make_tuple</c>  to get a compile time error if the number of
-      arguments does not match.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple1(ErlNifEnv* env,
+        ERL_NIF_TERM e1)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple2(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ERL_NIF_TERM e2)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple3(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ERL_NIF_TERM e2, ERL_NIF_TERM e3)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple4(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e4)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple5(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e5)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple6(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e6)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple7(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e7)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple8(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e8)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple9(ErlNifEnv* env,
+        ERL_NIF_TERM e1, ..., ERL_NIF_TERM e9)</nametext></name>
+      <fsummary>Create a tuple term.</fsummary>
+      <desc>
+        <p>Creates a tuple term with length indicated by the
+          function name. Prefer these functions (macros) over the variadic
+          <c>enif_make_tuple</c> to get a compile-time error if the number of
+          arguments does not match.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_tuple_from_array(ErlNifEnv* env, const ERL_NIF_TERM arr[], unsigned cnt)</nametext></name>
-      <fsummary>Create a tuple term from an array</fsummary>
-      <desc><p>Create a tuple containing the elements of array <c>arr</c>
-      of length <c>cnt</c>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_tuple_from_array(ErlNifEnv* env, const ERL_NIF_TERM
+        arr[], unsigned cnt)</nametext></name>
+      <fsummary>Create a tuple term from an array.</fsummary>
+      <desc>
+        <p>Creates a tuple containing the elements of array <c>arr</c>
+          of length <c>cnt</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_uint(ErlNifEnv* env, unsigned int i)</nametext></name>
-      <fsummary>Create an unsigned integer term</fsummary>
-      <desc><p>Create an integer term from an <c>unsigned int</c>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_uint(ErlNifEnv* env, unsigned int i)</nametext>
+      </name>
+      <fsummary>Create an unsigned integer term.</fsummary>
+      <desc>
+        <p>Creates an integer term from an <c>unsigned int</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_uint64(ErlNifEnv* env, ErlNifUInt64 i)</nametext></name>
-      <fsummary>Create an unsigned integer term</fsummary>
-      <desc><p>Create an integer term from an unsigned 64-bit integer.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_uint64(ErlNifEnv* env, ErlNifUInt64 i)</nametext>
+      </name>
+      <fsummary>Create an unsigned integer term.</fsummary>
+      <desc>
+        <p>Creates an integer term from an unsigned 64-bit integer.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_ulong(ErlNifEnv* env, unsigned long i)</nametext></name>
-      <fsummary>Create an integer term from an unsigned long int</fsummary>
-      <desc><p>Create an integer term from an <c>unsigned long int</c>.</p></desc>
+      <name><ret>ERL_NIF_TERM</ret>
+        <nametext>enif_make_ulong(ErlNifEnv* env, unsigned long i)</nametext>
+      </name>
+      <fsummary>Create an integer term from an unsigned long int.</fsummary>
+      <desc>
+        <p>Creates an integer term from an <c>unsigned long int</c>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_unique_integer(ErlNifEnv *env, ErlNifUniqueInteger properties)</nametext></name>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_make_unique_integer(ErlNifEnv
+        *env, ErlNifUniqueInteger properties)</nametext></name>
       <fsummary></fsummary>
       <desc>
-        <p>Returns a unique integer with the same properties as given by <seealso marker="erlang#unique_integer-1">erlang:unique_integer/1</seealso>.</p>
+        <p>Returns a unique integer with the same properties as specified by
+          <seealso marker="erlang#unique_integer-1">
+          <c>erlang:unique_integer/1</c></seealso>.</p>
         <p><c>env</c> is the environment to create the integer in.</p>
-        <p>
-          <c>ERL_NIF_UNIQUE_POSITIVE</c> and <c>ERL_NIF_UNIQUE_MONOTONIC</c> can
-          be passed as the second argument to change the properties of the
-          integer returned. It is possible to combine them by or:ing the
-          two values together.
-        </p>
-        <p>See also:
-	<seealso marker="#ErlNifUniqueInteger"><c>ErlNifUniqueInteger</c></seealso>.
-	</p>
+        <p><c>ERL_NIF_UNIQUE_POSITIVE</c> and <c>ERL_NIF_UNIQUE_MONOTONIC</c>
+          can be passed as the second argument to change the properties of the
+          integer returned. They can be combined by OR:ing the two values
+          together.</p>
+        <p>See also <seealso marker="#ErlNifUniqueInteger">
+          <c>ErlNifUniqueInteger</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_map_iterator_create(ErlNifEnv *env, ERL_NIF_TERM map, ErlNifMapIterator *iter, ErlNifMapIteratorEntry entry)</nametext></name>
-      <fsummary>Create a map iterator</fsummary>
-      <desc><p>Create an iterator for the map <c>map</c> by initializing the
-      structure pointed to by <c>iter</c>. The <c>entry</c> argument determines
-      the start position of the iterator: <c>ERL_NIF_MAP_ITERATOR_FIRST</c> or
-      <c>ERL_NIF_MAP_ITERATOR_LAST</c>. Return true on success or false if
-      <c>map</c> is not a map.</p>
-      <p>A map iterator is only useful during the lifetime of the environment
-      <c>env</c> that the <c>map</c> belongs to. The iterator must be destroyed by
-      calling <seealso marker="#enif_map_iterator_destroy">
-      enif_map_iterator_destroy</seealso>.</p>
-      <code type="none">
+      <name><ret>int</ret><nametext>enif_map_iterator_create(ErlNifEnv *env,
+        ERL_NIF_TERM map, ErlNifMapIterator *iter, ErlNifMapIteratorEntry
+        entry)</nametext></name>
+      <fsummary>Create a map iterator.</fsummary>
+      <desc>
+        <p>Creates an iterator for the map <c>map</c> by initializing the
+          structure pointed to by <c>iter</c>. Argument <c>entry</c> determines
+          the start position of the iterator: <c>ERL_NIF_MAP_ITERATOR_FIRST</c>
+          or <c>ERL_NIF_MAP_ITERATOR_LAST</c>.</p>
+        <p>Returns <c>true</c> on success, or false if <c>map</c> is not a
+          map.</p>
+        <p>A map iterator is only useful during the lifetime of environment
+          <c>env</c> that the <c>map</c> belongs to. The iterator must be
+          destroyed by calling <seealso marker="#enif_map_iterator_destroy">
+          <c>enif_map_iterator_destroy</c></seealso>:</p>
+        <code type="none">
 ERL_NIF_TERM key, value;
 ErlNifMapIterator iter;
 enif_map_iterator_create(env, my_map, &amp;iter, ERL_NIF_MAP_ITERATOR_FIRST);
@@ -1646,643 +2069,712 @@ while (enif_map_iterator_get_pair(env, &amp;iter, &amp;key, &amp;value)) {
     do_something(key,value);
     enif_map_iterator_next(env, &amp;iter);
 }
-enif_map_iterator_destroy(env, &amp;iter);
-      </code>
-     <note><p>The key-value pairs of a map have no defined iteration
-     order. The only guarantee is that the iteration order of a single map
-     instance is preserved during the lifetime of the environment that the map
-     belongs to.</p>
-    </note>
+enif_map_iterator_destroy(env, &amp;iter);</code>
+        <note>
+          <p>The key-value pairs of a map have no defined iteration order.
+            The only guarantee is that the iteration order of a single map
+            instance is preserved during the lifetime of the environment that
+            the map belongs to.</p>
+        </note>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret><nametext>enif_map_iterator_destroy(ErlNifEnv *env, ErlNifMapIterator *iter)</nametext></name>
-      <fsummary>Destroy a map iterator</fsummary>
+      <name><ret>void</ret><nametext>enif_map_iterator_destroy(ErlNifEnv *env,
+        ErlNifMapIterator *iter)</nametext></name>
+      <fsummary>Destroy a map iterator.</fsummary>
       <desc>
-        <p>Destroy a map iterator created by
-      <seealso marker="#enif_map_iterator_create">enif_map_iterator_create</seealso>.
-      </p>
+        <p>Destroys a map iterator created by
+          <seealso marker="#enif_map_iterator_create">
+          <c>enif_map_iterator_create</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_map_iterator_get_pair(ErlNifEnv *env, ErlNifMapIterator *iter, ERL_NIF_TERM *key, ERL_NIF_TERM *value)</nametext></name>
-      <fsummary>Get key and value at current map iterator position</fsummary>
+      <name><ret>int</ret><nametext>enif_map_iterator_get_pair(ErlNifEnv *env,
+        ErlNifMapIterator *iter, ERL_NIF_TERM *key, ERL_NIF_TERM
+        *value)</nametext></name>
+      <fsummary>Get key and value at current map iterator position.</fsummary>
       <desc>
-        <p>Get key and value terms at current map iterator position.
-      On success set <c>*key</c> and <c>*value</c> and return true.
-      Return false if the iterator is positioned at head (before first entry)
-      or tail (beyond last entry).</p>
+        <p>Gets key and value terms at the current map iterator position.</p>
+        <p>On success, sets <c>*key</c> and <c>*value</c> and returns
+          <c>true</c>. Returns <c>false</c> if the iterator is positioned at
+          head (before first entry) or tail (beyond last entry).</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_map_iterator_is_head(ErlNifEnv *env, ErlNifMapIterator *iter)</nametext></name>
-      <fsummary>Check if map iterator is positioned before first</fsummary>
+      <name><ret>int</ret><nametext>enif_map_iterator_is_head(ErlNifEnv *env,
+        ErlNifMapIterator *iter)</nametext></name>
+      <fsummary>Check if map iterator is positioned before first.</fsummary>
       <desc>
-        <p>Return true if map iterator <c>iter</c> is positioned
-      before first entry.</p>
+        <p>Returns <c>true</c> if map iterator <c>iter</c> is positioned
+          before the first entry.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_map_iterator_is_tail(ErlNifEnv *env, ErlNifMapIterator *iter)</nametext></name>
-      <fsummary>Check if map iterator is positioned after last</fsummary>
+      <name><ret>int</ret><nametext>enif_map_iterator_is_tail(ErlNifEnv *env,
+        ErlNifMapIterator *iter)</nametext></name>
+      <fsummary>Check if map iterator is positioned after last.</fsummary>
       <desc>
-        <p>Return true if map iterator <c>iter</c> is positioned
-      after last entry.</p>
+        <p>Returns <c>true</c> if map iterator <c>iter</c> is positioned
+          after the last entry.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_map_iterator_next(ErlNifEnv *env, ErlNifMapIterator *iter)</nametext></name>
-      <fsummary>Increment map iterator to point to next entry</fsummary>
+      <name><ret>int</ret><nametext>enif_map_iterator_next(ErlNifEnv *env,
+        ErlNifMapIterator *iter)</nametext></name>
+      <fsummary>Increment map iterator to point to next entry.</fsummary>
       <desc>
-        <p>Increment map iterator to point to next key-value entry.
-      Return true if the iterator is now positioned at a valid key-value entry,
-      or false if the iterator is positioned at the tail (beyond the last
-      entry).</p>
+        <p>Increments map iterator to point to the next key-value entry.</p>
+        <p>Returns <c>true</c> if the iterator is now positioned at a valid
+          key-value entry, or <c>false</c> if the iterator is positioned at
+          the tail (beyond the last entry).</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret><nametext>enif_map_iterator_prev(ErlNifEnv *env, ErlNifMapIterator *iter)</nametext></name>
-      <fsummary>Decrement map iterator to point to previous entry</fsummary>
+      <name><ret>int</ret><nametext>enif_map_iterator_prev(ErlNifEnv *env,
+        ErlNifMapIterator *iter)</nametext></name>
+      <fsummary>Decrement map iterator to point to previous entry.</fsummary>
       <desc>
-        <p>Decrement map iterator to point to previous key-value entry.
-      Return true if the iterator is now positioned at a valid key-value entry,
-      or false if the iterator is positioned at the head (before the first
-      entry).</p>
+        <p>Decrements map iterator to point to the previous key-value entry.</p>
+        <p>Returns <c>true</c> if the iterator is now positioned at a valid
+          key-value entry, or <c>false</c> if the iterator is positioned at
+          the head (before the first entry).</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ErlNifTime</ret><nametext>enif_monotonic_time(ErlNifTimeUnit time_unit)</nametext></name>
-      <fsummary>Get Erlang Monotonic Time</fsummary>
+      <name><ret>ErlNifTime</ret>
+        <nametext>enif_monotonic_time(ErlNifTimeUnit time_unit)</nametext>
+      </name>
+      <fsummary>Get Erlang monotonic time.</fsummary>
       <desc>
-	<marker id="enif_monotonic_time"></marker>
-	<p>Arguments:</p>
-	<taglist>
-	  <tag><c>time_unit</c></tag>
-	  <item>Time unit of returned value.</item>
-	</taglist>
-	<p>
-	  Returns the current
-	  <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	  monotonic time</seealso>. Note that it is not uncommon with
-	  negative values.
-	</p>
-	<p>Returns <c>ERL_NIF_TIME_ERROR</c> if called with an invalid
-	time unit argument, or if called from a thread that is not a
-	scheduler thread.</p>
-	<p>See also:
-	  <seealso marker="#ErlNifTime"><c>ErlNifTime</c></seealso> and
-	  <seealso marker="#ErlNifTimeUnit"><c>ErlNifTimeUnit</c></seealso>.
-	</p>
+        <marker id="enif_monotonic_time"></marker>
+        <p>Returns the current
+          <seealso marker="time_correction#Erlang_Monotonic_Time">
+          Erlang monotonic time</seealso>. Notice that it is not uncommon with
+          negative values.</p>
+        <p><c>time_unit</c> is the time unit of the returned value.</p>
+        <p>Returns <c>ERL_NIF_TIME_ERROR</c> if called with an invalid time
+          unit argument, or if called from a thread that is not a scheduler
+          thread.</p>
+        <p>See also <seealso marker="#ErlNifTime"><c>ErlNifTime</c></seealso>
+          and <seealso marker="#ErlNifTimeUnit"><c>ErlNifTimeUnit</c></seealso>.
+        </p>
       </desc>
     </func>
 
     <func>
       <name><ret>ErlNifMutex *</ret>
-      <nametext>enif_mutex_create(char *name)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_create">erl_drv_mutex_create</seealso>.
-    </p>
+        <nametext>enif_mutex_create(char *name)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_create">
+          <c>erl_drv_mutex_create</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_mutex_destroy(ErlNifMutex *mtx)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_destroy">erl_drv_mutex_destroy</seealso>.
-          </p>
+        <nametext>enif_mutex_destroy(ErlNifMutex *mtx)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_destroy">
+          <c>erl_drv_mutex_destroy</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_mutex_lock(ErlNifMutex *mtx)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_lock">erl_drv_mutex_lock</seealso>.
-          </p>
+        <nametext>enif_mutex_lock(ErlNifMutex *mtx)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_lock">
+          <c>erl_drv_mutex_lock</c></seealso>.</p>
       </desc>
     </func>
 
-    <func>
-      <name><ret>int</ret>
+    <func><name><ret>int</ret>
       <nametext>enif_mutex_trylock(ErlNifMutex *mtx)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_trylock">erl_drv_mutex_trylock</seealso>.
-          </p>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_trylock">
+          <c>erl_drv_mutex_trylock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_mutex_unlock(ErlNifMutex *mtx)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_unlock">erl_drv_mutex_unlock</seealso>.
-          </p>
+        <nametext>enif_mutex_unlock(ErlNifMutex *mtx)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_mutex_unlock">
+          <c>erl_drv_mutex_unlock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>ERL_NIF_TERM</ret>
-      <nametext>enif_now_time(ErlNifEnv *env)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Retuns an <seealso marker="erlang#now-0">erlang:now()</seealso> timestamp.
-    The enif_now_time function is <em>deprecated</em>.</p>
+        <nametext>enif_now_time(ErlNifEnv *env)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Returns an <seealso marker="erlang#now-0">
+          <c>erlang:now()</c></seealso> time stamp.</p>
+        <p><em>This function is deprecated.</em></p>
       </desc>
     </func>
 
     <func>
       <name><ret>ErlNifResourceType *</ret>
-      <nametext>enif_open_resource_type(ErlNifEnv* env,
-                             const char* module_str, const char* name,
-                             ErlNifResourceDtor* dtor, ErlNifResourceFlags flags, ErlNifResourceFlags* tried)</nametext></name>
-      <fsummary>Create or takeover a resource type</fsummary>
-      <desc>
-        <p>Create or takeover a resource type identified by the string
-      <c>name</c> and give it the destructor function pointed to by <seealso marker="#ErlNifResourceDtor">dtor</seealso>.
-      Argument <c>flags</c> can have the following values:</p>
-      <taglist>
-        <tag><c>ERL_NIF_RT_CREATE</c></tag>
-              <item>Create a new resource type that does not already exist.</item>
-        <tag><c>ERL_NIF_RT_TAKEOVER</c></tag>
-              <item>Open an existing resource type and take over ownership of all its instances.
-               The supplied destructor <c>dtor</c> will be called both for existing instances
-               as well as new instances not yet created by the calling NIF library.</item>            
-      </taglist>
-      <p>The two flag values can be combined with bitwise-or. The name of the
-      resource type is local to the calling module. Argument <c>module_str</c>
-      is not (yet) used and must be NULL. The <c>dtor</c> may  be <c>NULL</c>
-      in case no destructor is needed.</p>
-      <p>On success, return a pointer to the resource type and <c>*tried</c>
-      will be set to either <c>ERL_NIF_RT_CREATE</c> or
-      <c>ERL_NIF_RT_TAKEOVER</c> to indicate what was actually done.
-       On failure, return <c>NULL</c> and set <c>*tried</c> to <c>flags</c>.
-       It is allowed to set <c>tried</c> to <c>NULL</c>.</p>
-       <p>Note that <c>enif_open_resource_type</c> is only allowed to be called in the three callbacks
-       <seealso marker="#load">load</seealso>, <seealso marker="#reload">reload</seealso>
-       and <seealso marker="#upgrade">upgrade</seealso>.</p>
+        <nametext>enif_open_resource_type(ErlNifEnv* env, const char*
+        module_str, const char* name, ErlNifResourceDtor* dtor,
+        ErlNifResourceFlags flags, ErlNifResourceFlags* tried)</nametext>
+      </name>
+      <fsummary>Create or takeover a resource type.</fsummary>
+      <desc>
+        <p>Creates or takes over a resource type identified by the string
+          <c>name</c> and gives it the destructor function pointed to by
+          <seealso marker="#ErlNifResourceDtor"><c>dtor</c></seealso>.
+          Argument <c>flags</c> can have the following values:</p>
+        <taglist>
+          <tag><c>ERL_NIF_RT_CREATE</c></tag>
+          <item>Creates a new resource type that does not already exist.</item>
+          <tag><c>ERL_NIF_RT_TAKEOVER</c></tag>
+          <item>Opens an existing resource type and takes over ownership of all
+            its instances. The supplied destructor <c>dtor</c> is called both
+            for existing instances and new instances not yet created by the
+            calling NIF library.</item>
+        </taglist>
+        <p>The two flag values can be combined with bitwise OR. The resource
+          type name is local to the calling module. Argument <c>module_str</c>
+          is not (yet) used and must be <c>NULL</c>. <c>dtor</c> can be
+          <c>NULL</c> if no destructor is needed.</p>
+        <p>On success, the function returns a pointer to the resource type and
+          <c>*tried</c> is set to either <c>ERL_NIF_RT_CREATE</c> or
+          <c>ERL_NIF_RT_TAKEOVER</c> to indicate what was done. On failure,
+          returns <c>NULL</c> and sets <c>*tried</c> to <c>flags</c>.
+          It is allowed to set <c>tried</c> to <c>NULL</c>.</p>
+        <p>Notice that <c>enif_open_resource_type</c> is only allowed to be
+          called in the three callbacks
+          <seealso marker="#load"><c>load</c></seealso>,
+          <seealso marker="#reload"><c>reload</c></seealso>, and
+          <seealso marker="#upgrade"><c>upgrade</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret>
-      <nametext>enif_port_command(ErlNifEnv* env, const ErlNifPort* to_port, ErlNifEnv *msg_env, ERL_NIF_TERM msg)</nametext></name>
-      <fsummary>Send a port_command to to_port</fsummary>
-      <desc>
-        <p>This function works the same as <seealso marker="erlang#port_command-2">erlang:port_command/2</seealso>
-        except that it is always completely asynchronous.</p>
-        <taglist>
-          <tag><c>env</c></tag>
-          <item>The environment of the calling process. May not be NULL.</item>
-          <tag><c>*to_port</c></tag>
-          <item>The port id of the receiving port. The port id should refer to a
-          port on the local node.</item>
-          <tag><c>msg_env</c></tag>
-          <item>The environment of the message term. Can be a process
-          independent environment allocated with
-          <seealso marker="#enif_alloc_env">enif_alloc_env</seealso> or NULL.</item>
-          <tag><c>msg</c></tag>
-          <item>The message term to send. The same limitations apply as on the
-          payload to <seealso marker="erlang#port_command-2">erlang:port_command/2</seealso>.</item>
-        </taglist>
-        <p>Using a <c>msg_env</c> of NULL is an optimization which groups together
-        calls to <c>enif_alloc_env</c>, <c>enif_make_copy</c>, <c>enif_port_command</c>
-        and <c>enif_free_env</c> into one call. This optimization is only usefull
-        when a majority of the terms are to be copied from <c>env</c> to the <c>msg_env</c>.</p>
-        <p>This function return true if the command was successfully sent; otherwise,
-	false. The call may return false if it detects that the command failed for some
-	reason. For example, <c>*to_port</c> does not refer to a local port, if currently
-	executing process, i.e. the sender, is not alive, or if <c>msg</c> is invalid.</p>
-        <p>See also: <seealso marker="#enif_get_local_port"><c>enif_get_local_port</c></seealso>.</p>
+     <name><ret>int</ret><nametext>enif_port_command(ErlNifEnv* env, const
+       ErlNifPort* to_port, ErlNifEnv *msg_env, ERL_NIF_TERM msg)</nametext>
+     </name>
+     <fsummary>Send a port_command to to_port.</fsummary>
+     <desc>
+       <p>Works as <seealso marker="erlang#port_command-2">
+         <c>erlang:port_command/2</c></seealso>,
+         except that it is always completely asynchronous.</p>
+       <taglist>
+         <tag><c>env</c></tag>
+         <item>The environment of the calling process. Must not be
+           <c>NULL</c>.</item>
+         <tag><c>*to_port</c></tag>
+         <item>The port ID of the receiving port. The port ID is to refer to a
+           port on the local node.</item>
+         <tag><c>msg_env</c></tag>
+         <item>The environment of the message term. Can be a process-independent
+           environment allocated with <seealso marker="#enif_alloc_env">
+           <c>enif_alloc_env</c></seealso> or <c>NULL</c>.</item>
+         <tag><c>msg</c></tag>
+         <item>The message term to send. The same limitations apply as on the
+           payload to <seealso marker="erlang#port_command-2">
+           <c>erlang:port_command/2</c></seealso>.</item>
+       </taglist>
+       <p>Using a <c>msg_env</c> of <c>NULL</c> is an optimization, which
+         groups together calls to <c>enif_alloc_env</c>, <c>enif_make_copy</c>,
+         <c>enif_port_command</c>, and <c>enif_free_env</c> into one call.
+         This optimization is only useful when a majority of the terms are to
+         be copied from <c>env</c> to <c>msg_env</c>.</p>
+       <p>Returns <c>true</c> if the command is successfully sent. Returns
+         <c>false</c> if the command fails, for example:</p>
+       <list type="bulleted">
+         <item><c>*to_port</c> does not refer to a local port.</item>
+         <item>The currently executing process (that is, the sender) is not
+           alive.</item>
+         <item><c>msg</c> is invalid.</item>
+       </list>
+       <p>See also <seealso marker="#enif_get_local_port">
+         <c>enif_get_local_port</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void *</ret>
-      <nametext>enif_priv_data(ErlNifEnv* env)</nametext></name>
-      <fsummary>Get the private data of a NIF library</fsummary>
+        <nametext>enif_priv_data(ErlNifEnv* env)</nametext></name>
+      <fsummary>Get the private data of a NIF library.</fsummary>
       <desc>
-        <p>Return the pointer to the private data that was set by <c>load</c>,
-      <c>reload</c> or <c>upgrade</c>.</p>
-      <p>Was previously named <c>enif_get_data</c>.</p>
+        <p>Returns the pointer to the private data that was set by
+          <seealso marker="#load"><c>load</c></seealso>,
+          <seealso marker="#reload"><c>reload</c></seealso>, or
+          <seealso marker="#upgrade"><c>upgrade</c></seealso>.</p>
+        <p>Was previously named <c>enif_get_data</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret>
-      <nametext>enif_raise_exception(ErlNifEnv* env, ERL_NIF_TERM reason)</nametext></name>
-      <fsummary>Raise a NIF error exception</fsummary>
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_raise_exception(ErlNifEnv*
+        env, ERL_NIF_TERM reason)</nametext></name>
+      <fsummary>Raise a NIF error exception.</fsummary>
       <desc>
-        <p>Create an error exception with the term <c>reason</c> to be returned from a NIF,
-      and associate it with the environment <c>env</c>. Once a NIF or any function it calls
-      invokes <c>enif_raise_exception</c>, the runtime ensures that the exception it creates
-      is raised when the NIF returns, even if the NIF attempts to return a non-exception
-      term instead. The return value from <c>enif_raise_exception</c> may be used only as
-      the return value from the NIF that invoked it (directly or indirectly) or be passed
-      to <seealso marker="#enif_is_exception">enif_is_exception</seealso>, but
-      not to any other NIF API function.</p>
-      <p>See also: <seealso marker="#enif_has_pending_exception">enif_has_pending_exception</seealso>
-      and <seealso marker="#enif_make_badarg">enif_make_badarg</seealso>.</p>
+        <p>Creates an error exception with the term <c>reason</c> to be
+          returned from a NIF, and associates it with environment <c>env</c>.
+          Once a NIF or any function it calls invokes
+          <c>enif_raise_exception</c>, the runtime ensures that the exception
+          it creates is raised when the NIF returns, even if the NIF attempts
+          to return a non-exception term instead.</p>
+        <p>The return value from <c>enif_raise_exception</c> can only be used
+          as the return value from the NIF that invoked it (directly or
+          indirectly) or be passed to <seealso marker="#enif_is_exception">
+          <c>enif_is_exception</c></seealso>, but not to any other NIF API
+          function.</p>
+        <p>See also <seealso marker="#enif_has_pending_exception">
+          <c>enif_has_pending_exception</c></seealso> and
+          <seealso marker="#enif_make_badarg">
+          <c>enif_make_badarg</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>int</ret>
-      <nametext>enif_realloc_binary(ErlNifBinary* bin, size_t size)</nametext></name>
-      <fsummary>Change the size of a binary</fsummary>
+        <nametext>enif_realloc_binary(ErlNifBinary* bin, size_t size)</nametext>
+      </name>
+      <fsummary>Change the size of a binary.</fsummary>
       <desc>
-        <p>Change the size of a binary <c>bin</c>. The source binary
-      may be read-only, in which case it will be left untouched and
-      a mutable copy is allocated and assigned to <c>*bin</c>. Return true on success,
-      false if memory allocation failed.</p>
+        <p>Changes the size of a binary <c>bin</c>. The source binary
+          can be read-only, in which case it is left untouched and
+          a mutable copy is allocated and assigned to <c>*bin</c>.</p>
+        <p>Returns <c>true</c> on success, or <c>false</c> if memory allocation
+          failed.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_release_binary(ErlNifBinary* bin)</nametext></name>
-      <fsummary>Release a binary</fsummary>
+        <nametext>enif_release_binary(ErlNifBinary* bin)</nametext></name>
+      <fsummary>Release a binary.</fsummary>
       <desc>
-        <p>Release a binary obtained from <c>enif_alloc_binary</c>.</p>
+        <p>Releases a binary obtained from
+          <seealso marker="#enif_alloc_binary">
+          <c>enif_alloc_binary</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_release_resource(void* obj)</nametext></name>
-      <fsummary>Release a resource object</fsummary>
+        <nametext>enif_release_resource(void* obj)</nametext></name>
+      <fsummary>Release a resource object.</fsummary>
       <desc>
-        <p>Remove a reference to resource object <c>obj</c>obtained from
-      <seealso marker="#enif_alloc_resource">enif_alloc_resource</seealso>.
-      The resource object will be destructed when the last reference is removed.
-      Each call to <c>enif_release_resource</c> must correspond to a previous
-      call to <c>enif_alloc_resource</c> or
-      <seealso marker="#enif_keep_resource">enif_keep_resource</seealso>.
-      References made by <seealso marker="#enif_make_resource">enif_make_resource</seealso>
-      can only be removed by the garbage collector.</p>
+        <p>Removes a reference to resource object <c>obj</c>obtained from
+          <seealso marker="#enif_alloc_resource">
+          <c>enif_alloc_resource</c></seealso>.
+          The resource object is destructed when the last reference is removed.
+          Each call to <c>enif_release_resource</c> must correspond to a
+          previous call to <c>enif_alloc_resource</c> or
+          <seealso marker="#enif_keep_resource">
+          <c>enif_keep_resource</c></seealso>.
+          References made by <seealso marker="#enif_make_resource">
+          <c>enif_make_resource</c></seealso>
+          can only be removed by the garbage collector.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>ErlNifRWLock *</ret>
-      <nametext>enif_rwlock_create(char *name)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_create">erl_drv_rwlock_create</seealso>.
-          </p>
+        <nametext>enif_rwlock_create(char *name)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_create">
+          <c>erl_drv_rwlock_create</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_rwlock_destroy(ErlNifRWLock *rwlck)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_destroy">erl_drv_rwlock_destroy</seealso>.
-          </p>
+        <nametext>enif_rwlock_destroy(ErlNifRWLock *rwlck)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_destroy">
+          <c>erl_drv_rwlock_destroy</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_rwlock_rlock(ErlNifRWLock *rwlck)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_rlock">erl_drv_rwlock_rlock</seealso>.
-          </p>
+        <nametext>enif_rwlock_rlock(ErlNifRWLock *rwlck)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_rlock">
+          <c>erl_drv_rwlock_rlock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_rwlock_runlock(ErlNifRWLock *rwlck)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_runlock">erl_drv_rwlock_runlock</seealso>.
-          </p>
+        <nametext>enif_rwlock_runlock(ErlNifRWLock *rwlck)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_runlock">
+          <c>erl_drv_rwlock_runlock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_rwlock_rwlock(ErlNifRWLock *rwlck)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_rwlock">erl_drv_rwlock_rwlock</seealso>.
-          </p>
+        <nametext>enif_rwlock_rwlock(ErlNifRWLock *rwlck)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_rwlock">
+          <c>erl_drv_rwlock_rwlock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_rwlock_rwunlock(ErlNifRWLock *rwlck)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_rwunlock">erl_drv_rwlock_rwunlock</seealso>.
-          </p>
+        <nametext>enif_rwlock_rwunlock(ErlNifRWLock *rwlck)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_rwunlock">
+          <c>erl_drv_rwlock_rwunlock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>int</ret>
-      <nametext>enif_rwlock_tryrlock(ErlNifRWLock *rwlck)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_tryrlock">erl_drv_rwlock_tryrlock</seealso>.
-          </p>
+        <nametext>enif_rwlock_tryrlock(ErlNifRWLock *rwlck)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_tryrlock">
+          <c>erl_drv_rwlock_tryrlock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>int</ret>
-      <nametext>enif_rwlock_tryrwlock(ErlNifRWLock *rwlck)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_tryrwlock">erl_drv_rwlock_tryrwlock</seealso>.
-          </p>
+        <nametext>enif_rwlock_tryrwlock(ErlNifRWLock *rwlck)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_rwlock_tryrwlock">
+          <c>erl_drv_rwlock_tryrwlock</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>ERL_NIF_TERM</ret>
-      <nametext>enif_schedule_nif(ErlNifEnv* env, const char* fun_name, int flags, ERL_NIF_TERM (*fp)(ErlNifEnv* env, int argc, const ERL_NIF_TERM argv[]), int argc, const ERL_NIF_TERM argv[])</nametext></name>
-      <fsummary>Schedule a NIF for execution</fsummary>
-      <desc>
-          <p>Schedule NIF <c>fp</c> to execute. This function allows an application to break up long-running
-          work into multiple regular NIF calls or to schedule a <seealso marker="#dirty_nifs">dirty NIF</seealso>
-          to execute on a dirty scheduler thread (<em>note that the dirty NIF functionality described here is
-          experimental</em> and that you have to enable support for dirty schedulers when building OTP in
-          order to try the functionality out).</p>
-          <p>The <c>fun_name</c> argument provides a name for the NIF being scheduled for execution. If it cannot
-          be converted to an atom, <c>enif_schedule_nif</c> returns a <c>badarg</c> exception.</p>
-          <p>The <c>flags</c> argument must be set to 0 for a regular NIF, or if the emulator was built the
-          experimental dirty scheduler support enabled, <c>flags</c> can be set to either <c>ERL_NIF_DIRTY_JOB_CPU_BOUND</c>
-          if the job is expected to be CPU-bound, or <c>ERL_NIF_DIRTY_JOB_IO_BOUND</c> for jobs that will
-          be I/O-bound. If dirty scheduler threads are not available in the emulator, a try to schedule such a job
-          will result in a <c>badarg</c> exception.</p>
-
-          <p>The <c>argc</c> and <c>argv</c> arguments can either be the originals passed into the calling NIF, or
-          they can be values created by the calling NIF.</p>
-          <p>The calling NIF must use the return value of <c>enif_schedule_nif</c> as its own return value.</p>
-          <p>Be aware that <c>enif_schedule_nif</c>, as its name implies, only schedules the
-          NIF for future execution. The calling NIF does not block waiting for the scheduled NIF to
-          execute and return, which means that the calling NIF can't expect to receive the scheduled NIF
+      <name><ret>ERL_NIF_TERM</ret><nametext>enif_schedule_nif(ErlNifEnv* env,
+        const char* fun_name, int flags, ERL_NIF_TERM (*fp)(ErlNifEnv* env, int
+        argc, const ERL_NIF_TERM argv[]), int argc, const ERL_NIF_TERM
+        argv[])</nametext></name>
+      <fsummary>Schedule a NIF for execution.</fsummary>
+      <desc>
+        <p>Schedules NIF <c>fp</c> to execute. This function allows an
+          application to break up long-running work into multiple regular NIF
+          calls or to schedule a <seealso marker="#dirty_nifs">
+          dirty NIF</seealso> to execute on a dirty scheduler thread.</p>
+        <p><em>The dirty NIF functionality described here is
+          experimental.</em> You have to enable support for dirty
+          schedulers when building OTP to try out the functionality.</p>
+        <taglist>
+          <tag><c>fun_name</c></tag>
+          <item>
+            <p>Provides a name for the NIF that is scheduled for execution.
+              If it cannot be converted to an atom, <c>enif_schedule_nif</c>
+              returns a <c>badarg</c> exception.</p>
+          </item>
+          <tag><c>flags</c></tag>
+          <item>
+            <p>Must be set to <c>0</c> for a regular NIF. If the emulator was
+              built with the experimental dirty scheduler support enabled,
+              <c>flags</c> can be set to either
+              <c>ERL_NIF_DIRTY_JOB_CPU_BOUND</c> if the job is expected to be
+              CPU-bound, or <c>ERL_NIF_DIRTY_JOB_IO_BOUND</c> for
+              jobs that will be I/O-bound. If dirty scheduler threads are not
+              available in the emulator, an attempt to schedule such a job
+              results in a <c>badarg</c> exception.</p>
+          </item>
+          <tag><c>argc</c> and <c>argv</c></tag>
+          <item>
+            <p>Can either be the originals passed into the calling NIF,
+              or can be values created by the calling NIF.</p>
+          </item>
+        </taglist>
+        <p>The calling NIF must use the return value of
+          <c>enif_schedule_nif</c> as its own return value.</p>
+        <p>Be aware that <c>enif_schedule_nif</c>, as its name implies, only
+          schedules the NIF for future execution. The calling NIF does not
+          block waiting for the scheduled NIF to execute and return. This means
+          that the calling NIF cannot expect to receive the scheduled NIF
           return value and use it for further operations.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>ErlNifPid *</ret>
-      <nametext>enif_self(ErlNifEnv* caller_env, ErlNifPid* pid)</nametext></name>
-      <fsummary>Get the pid of the calling process</fsummary>
+        <nametext>enif_self(ErlNifEnv* caller_env, ErlNifPid* pid)</nametext>
+      </name>
+      <fsummary>Get the pid of the calling process.</fsummary>
       <desc>
-        <p>Initialize the pid variable <c>*pid</c> to represent the
-      calling process. Return <c>pid</c>.</p>
+        <p>Initializes the pid variable <c>*pid</c> to represent the
+          calling process.</p>
+        <p>Returns <c>pid</c>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret>
-      <nametext>enif_send(ErlNifEnv* env, ErlNifPid* to_pid, ErlNifEnv* msg_env, ERL_NIF_TERM msg)</nametext></name>
-      <fsummary>Send a message to a process</fsummary>
-      <desc>
-        <p>Send a message to a process.</p>
-      <taglist>
-        <tag><c>env</c></tag>
-              <item>The environment of the calling process. Must be NULL if and
-              only if calling from a created thread.</item>
-        <tag><c>*to_pid</c></tag>
-              <item>The pid of the receiving process. The pid should refer to a process on the local node.</item>
-        <tag><c>msg_env</c></tag>
-              <item>The environment of the message term. Must be a process
-              independent environment allocated with
-               <seealso marker="#enif_alloc_env">enif_alloc_env</seealso> or NULL.</item>
-        <tag><c>msg</c></tag>
-              <item>The message term to send.</item>
-      </taglist>
-      <p>Return true if the message was successfully sent; otherwise, false. The send
-      operation will fail if <c>*to_pid</c> does not refer to an alive local process,
-      or if currently executing process, i.e. the sender, is not alive.</p>
-      <p>The message environment <c>msg_env</c> with all its terms (including
-      <c>msg</c>) will be invalidated by a successful call to <c>enif_send</c>. The environment
-      should either be freed with <seealso marker="#enif_free_env">enif_free_env</seealso>
-      of cleared for reuse with <seealso marker="#enif_clear_env">enif_clear_env</seealso>.</p>
-      <p>If <c>msg_env</c> is set to NULL the <c>msg</c> term is copied and
-      the original term and its environemt is still valid after the call.</p>
-      <p>This function is only thread-safe when the emulator with SMP support is used.
-      It can only be used in a non-SMP emulator from a NIF-calling thread.</p>
-      <note><p>Passing <c>msg_env</c> as <c>NULL</c> is only supported since
-      erts-8.0 (OTP 19).</p></note>
+      <name><ret>int</ret><nametext>enif_send(ErlNifEnv* env, ErlNifPid* to_pid,
+        ErlNifEnv* msg_env, ERL_NIF_TERM msg)</nametext></name>
+      <fsummary>Send a message to a process.</fsummary>
+      <desc>
+        <p>Sends a message to a process.</p>
+        <taglist>
+          <tag><c>env</c></tag>
+          <item>The environment of the calling process. Must be <c>NULL</c>
+            only if calling from a created thread.</item>
+          <tag><c>*to_pid</c></tag>
+          <item>The pid of the receiving process. The pid is to refer to a
+            process on the local node.</item>
+          <tag><c>msg_env</c></tag>
+          <item>The environment of the message term. Must be a
+            process-independent environment allocated with
+            <seealso marker="#enif_alloc_env"><c>enif_alloc_env</c></seealso>
+            or NULL.</item>
+          <tag><c>msg</c></tag>
+          <item>The message term to send.</item>
+        </taglist>
+        <p>Returns <c>true</c> if the message is successfully sent. Returns
+          <c>false</c> if the send operation fails, that is:</p>
+        <list type="bulleted">
+          <item><c>*to_pid</c> does not refer to an alive local process.</item>
+          <item>The currently executing process (that is, the sender) is not
+           alive.</item>
+        </list>
+        <p>The message environment <c>msg_env</c> with all its terms (including
+          <c>msg</c>) is invalidated by a successful call to <c>enif_send</c>.
+          The environment is to either be freed with
+          <seealso marker="#enif_free_env">
+          <c>enif_free_env</c></seealso> of cleared for reuse with
+          <seealso marker="#enif_clear_env"><c>enif_clear_env</c></seealso>.</p>
+        <p>If <c>msg_env</c> is set to <c>NULL</c>, the <c>msg</c> term is
+          copied and the original term and its environemt is still valid after
+          the call.</p>
+        <p>This function is only thread-safe when the emulator with SMP support
+          is used. It can only be used in a non-SMP emulator from a NIF-calling
+          thread.</p>
+        <note>
+          <p>Passing <c>msg_env</c> as <c>NULL</c> is only supported as from
+            <c>ERTS</c> 8.0 (Erlang/OTP 19).</p>
+        </note>
       </desc>
     </func>
 
     <func>
       <name><ret>unsigned</ret>
-      <nametext>enif_sizeof_resource(void* obj)</nametext></name>
-      <fsummary>Get the byte size of a resource object</fsummary>
+        <nametext>enif_sizeof_resource(void* obj)</nametext></name>
+      <fsummary>Get the byte size of a resource object.</fsummary>
       <desc>
-        <p>Get the byte size of a resource object <c>obj</c> obtained by
-      <seealso marker="#enif_alloc_resource">enif_alloc_resource</seealso>.</p>
+        <p>Gets the byte size of resource object <c>obj</c> obtained by
+          <seealso marker="#enif_alloc_resource">
+          <c>enif_alloc_resource</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret>
-      <nametext>enif_snprintf(char *str, size_t size, const char *format, ...)</nametext></name>
-      <fsummary>Format strings and Erlang terms</fsummary>
+      <name><ret>int</ret><nametext>enif_snprintf(char *str, size_t size, const
+        char *format, ...)</nametext></name>
+      <fsummary>Format strings and Erlang terms.</fsummary>
       <desc>
-          <p>Similar to <c>snprintf</c> but this format string also accepts <c>"%T"</c> which formats Erlang terms.
-          </p>
+        <p>Similar to <c>snprintf</c> but this format string also accepts
+          <c>"%T"</c>, which formats Erlang terms.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>void</ret>
-      <nametext>enif_system_info(ErlNifSysInfo *sys_info_ptr, size_t size)</nametext></name>
-      <fsummary>Get information about the Erlang runtime system</fsummary>
+      <name><ret>void</ret><nametext>enif_system_info(ErlNifSysInfo
+        *sys_info_ptr, size_t size)</nametext></name>
+      <fsummary>Get information about the Erlang runtime system.</fsummary>
       <desc>
-        <p>Same as <seealso marker="erl_driver#driver_system_info">driver_system_info</seealso>.
-            </p>
+        <p>Same as <seealso marker="erl_driver#driver_system_info">
+          <c>driver_system_info</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-      <name><ret>int</ret>
-      <nametext>enif_term_to_binary(ErlNifEnv *env, ERL_NIF_TERM term, ErlNifBinary *bin)</nametext></name>
-    <fsummary>Convert a term to the external format</fsummary>
-    <desc>
-      <p>Allocates a new binary with <seealso marker="#enif_alloc_binary">enif_alloc_binary</seealso>
-      and stores the result of encoding <c>term</c> according to the Erlang external term format.</p>
-      <p>Returns true on success or false if allocation failed.</p>
-      <p>See also:
-        <seealso marker="erlang#term_to_binary-1"><c>erlang:term_to_binary/1</c></seealso> and
-        <seealso marker="#enif_binary_to_term"><c>enif_binary_to_term</c></seealso>.
-      </p>
-    </desc>
+      <name><ret>int</ret><nametext>enif_term_to_binary(ErlNifEnv *env,
+        ERL_NIF_TERM term, ErlNifBinary *bin)</nametext></name>
+      <fsummary>Convert a term to the external format.</fsummary>
+      <desc>
+        <p>Allocates a new binary with <seealso marker="#enif_alloc_binary">
+          <c>enif_alloc_binary</c></seealso> and stores the result of encoding
+          <c>term</c> according to the Erlang external term format.</p>
+      <p>Returns <c>true</c> on success, or <c>false</c> if the allocation
+        fails.</p>
+      <p>See also <seealso marker="erlang#term_to_binary-1">
+        <c>erlang:term_to_binary/1</c></seealso> and
+        <seealso marker="#enif_binary_to_term">
+        <c>enif_binary_to_term</c></seealso>.</p>
+      </desc>
     </func>
 
     <func>
-      <name><ret>int</ret>
-      <nametext>enif_thread_create(char *name,ErlNifTid *tid,void * (*func)(void *),void *args,ErlNifThreadOpts *opts)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_thread_create">erl_drv_thread_create</seealso>.
-          </p>
+      <name><ret>int</ret><nametext>enif_thread_create(char *name,ErlNifTid
+        *tid,void * (*func)(void *),void *args,ErlNifThreadOpts
+        *opts)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_thread_create">
+          <c>erl_drv_thread_create</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_thread_exit(void *resp)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_thread_exit">erl_drv_thread_exit</seealso>.
-          </p>
+        <nametext>enif_thread_exit(void *resp)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_thread_exit">
+          <c>erl_drv_thread_exit</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>int</ret>
-      <nametext>enif_thread_join(ErlNifTid, void **respp)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_thread_join">erl_drv_thread_join </seealso>.
-          </p>
+        <nametext>enif_thread_join(ErlNifTid, void **respp)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_thread_join">
+          <c>erl_drv_thread_join</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>ErlNifThreadOpts *</ret>
-      <nametext>enif_thread_opts_create(char *name)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_thread_opts_create">erl_drv_thread_opts_create</seealso>.
-          </p>
+        <nametext>enif_thread_opts_create(char *name)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_thread_opts_create">
+          <c>erl_drv_thread_opts_create</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_thread_opts_destroy(ErlNifThreadOpts *opts)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_thread_opts_destroy">erl_drv_thread_opts_destroy</seealso>.
-          </p>
+        <nametext>enif_thread_opts_destroy(ErlNifThreadOpts *opts)</nametext>
+      </name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_thread_opts_destroy">
+          <c>erl_drv_thread_opts_destroy</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>ErlNifTid</ret>
-      <nametext>enif_thread_self(void)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_thread_self">erl_drv_thread_self</seealso>.
-          </p>
+        <nametext>enif_thread_self(void)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_thread_self">
+          <c>erl_drv_thread_self</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>int</ret>
       <nametext>enif_thread_type(void)</nametext></name>
-        <fsummary>Determine type of current thread</fsummary>
-        <desc>
-            <p>Determine the type of currently executing thread. A positive value
-                indicates a scheduler thread while a negative value or zero indicates
-                another type of thread. Currently the following specific types exist
-                (which may be extended in the future):</p>
-            <taglist>
-                <tag><c>ERL_NIF_THR_UNDEFINED</c></tag>
-                <item><p>Undefined thread that is not a scheduler thread.</p></item>
-                <tag><c>ERL_NIF_THR_NORMAL_SCHEDULER</c></tag>
-                <item><p>A normal scheduler thread.</p></item>
-                <tag><c>ERL_NIF_THR_DIRTY_CPU_SCHEDULER</c></tag>
-                <item><p>A dirty CPU scheduler thread.</p></item>
-                <tag><c>ERL_NIF_THR_DIRTY_IO_SCHEDULER</c></tag>
-                <item><p>A dirty I/O scheduler thread.</p></item>
-            </taglist>
-        </desc>
+      <fsummary>Determine type of current thread</fsummary>
+      <desc>
+        <p>Determine the type of currently executing thread. A positive value
+        indicates a scheduler thread while a negative value or zero indicates
+        another type of thread. Currently the following specific types exist
+        (which may be extended in the future):</p>
+        <taglist>
+          <tag><c>ERL_NIF_THR_UNDEFINED</c></tag>
+          <item><p>Undefined thread that is not a scheduler thread.</p></item>
+          <tag><c>ERL_NIF_THR_NORMAL_SCHEDULER</c></tag>
+          <item><p>A normal scheduler thread.</p></item>
+          <tag><c>ERL_NIF_THR_DIRTY_CPU_SCHEDULER</c></tag>
+          <item><p>A dirty CPU scheduler thread.</p></item>
+          <tag><c>ERL_NIF_THR_DIRTY_IO_SCHEDULER</c></tag>
+          <item><p>A dirty I/O scheduler thread.</p></item>
+        </taglist>
+      </desc>
     </func>
 
     <func>
       <name><ret>ErlNifTime</ret>
-      <nametext>enif_time_offset(ErlNifTimeUnit time_unit)</nametext></name>
-      <fsummary>Get current Time Offset</fsummary>
-      <desc>
-	<marker id="enif_time_offset"></marker>
-	<p>Arguments:</p>
-	<taglist>
-	  <tag><c>time_unit</c></tag>
-	  <item>Time unit of returned value.</item>
-	</taglist>
-	<p>Returns the current time offset between
-	<seealso marker="time_correction#Erlang_Monotonic_Time">Erlang monotonic time</seealso>
-	and
-	<seealso marker="time_correction#Erlang_System_Time">Erlang system time</seealso>
-	converted into the <c>time_unit</c> passed as argument.</p>
-	<p>Returns <c>ERL_NIF_TIME_ERROR</c> if called with an invalid
-	time unit argument, or if called from a thread that is not a
-	scheduler thread.</p>
-	<p>See also:
-	    <seealso marker="#ErlNifTime"><c>ErlNifTime</c></seealso> and
-	    <seealso marker="#ErlNifTimeUnit"><c>ErlNifTimeUnit</c></seealso>.
-	</p>
+        <nametext>enif_time_offset(ErlNifTimeUnit time_unit)</nametext></name>
+      <fsummary>Get current time offset.</fsummary>
+      <desc>
+        <marker id="enif_time_offset"></marker>
+        <p>Returns the current time offset between
+          <seealso marker="time_correction#Erlang_Monotonic_Time">
+          Erlang monotonic time</seealso> and
+          <seealso marker="time_correction#Erlang_System_Time">
+          Erlang system time</seealso>
+          converted into the <c>time_unit</c> passed as argument.</p>
+        <p><c>time_unit</c> is the time unit of the returned value.</p>
+        <p>Returns <c>ERL_NIF_TIME_ERROR</c> if called with an invalid
+          time unit argument or if called from a thread that is not a
+          scheduler thread.</p>
+        <p>See also <seealso marker="#ErlNifTime"><c>ErlNifTime</c></seealso>
+          and
+          <seealso marker="#ErlNifTimeUnit"><c>ErlNifTimeUnit</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void *</ret>
-      <nametext>enif_tsd_get(ErlNifTSDKey key)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_get">erl_drv_tsd_get</seealso>.
-          </p>
+        <nametext>enif_tsd_get(ErlNifTSDKey key)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_get">
+          <c>erl_drv_tsd_get</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>int</ret>
-      <nametext>enif_tsd_key_create(char *name, ErlNifTSDKey *key)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_key_create">erl_drv_tsd_key_create</seealso>.
-          </p>
-      </desc>
-    </func>
+        <nametext>enif_tsd_key_create(char *name, ErlNifTSDKey *key)</nametext>
+      </name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_key_create">
+          <c>erl_drv_tsd_key_create</c></seealso>.</p>
+    </desc>
+   </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_tsd_key_destroy(ErlNifTSDKey key)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_key_destroy">erl_drv_tsd_key_destroy</seealso>.
-          </p>
+        <nametext>enif_tsd_key_destroy(ErlNifTSDKey key)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_key_destroy">
+          <c>erl_drv_tsd_key_destroy</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name><ret>void</ret>
-      <nametext>enif_tsd_set(ErlNifTSDKey key, void *data)</nametext></name>
-    <fsummary></fsummary>
-    <desc>
-        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_set">erl_drv_tsd_set</seealso>.
-          </p>
+        <nametext>enif_tsd_set(ErlNifTSDKey key, void *data)</nametext></name>
+      <fsummary></fsummary>
+      <desc>
+        <p>Same as <seealso marker="erl_driver#erl_drv_tsd_set">
+          <c>erl_drv_tsd_set</c></seealso>.</p>
       </desc>
     </func>
   </funcs>
+
   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="erlang#load_nif-2">erlang:load_nif/2</seealso></p>
+    <title>See Also</title>
+    <p><seealso marker="erlang#load_nif-2">
+      <c>erlang:load_nif/2</c></seealso></p>
   </section>
 </cref>
diff --git a/erts/doc/src/erl_prim_loader.xml b/erts/doc/src/erl_prim_loader.xml
index d3ece37cc5..86a3b98eda 100644
--- a/erts/doc/src/erl_prim_loader.xml
+++ b/erts/doc/src/erl_prim_loader.xml
@@ -30,95 +30,98 @@
     <file>erl_prim_loader.xml</file>
   </header>
   <module>erl_prim_loader</module>
-  <modulesummary>Low Level Erlang Loader</modulesummary>
+  <modulesummary>Low-level Erlang loader.</modulesummary>
   <description>
-    <p><c>erl_prim_loader</c> is used to load all Erlang modules into
-      the system. The start script is also fetched with this low level
+    <p>This module is used to load all Erlang modules into
+      the system. The start script is also fetched with this low-level
       loader.</p>
+
     <p><c>erl_prim_loader</c> knows about the environment and how to
       fetch modules.</p>
-    <p>The <c>-loader Loader</c> command line flag can be used to
-      choose the method used by the <c>erl_prim_loader</c>. Two
+
+    <p>Command-line flag <c>-loader Loader</c> can be used to
+      choose the method used by <c>erl_prim_loader</c>. Two
       <c>Loader</c> methods are supported by the Erlang runtime system:
       <c>efile</c> and <c>inet</c>.</p>
-
-    <warning><p>The support for loading of code from archive files is
-     experimental. The sole purpose of releasing it before it is ready
-     is to obtain early feedback. The file format, semantics,
-     interfaces etc. may be changed in a future release. The functions
-     <c>list_dir/1</c> and <c>read_file_info/1</c> as well as the flag
-     <c>-loader_debug</c> are also experimental</p></warning>
-
   </description>
 
   <funcs>
     <func>
       <name name="get_file" arity="1"/>
-      <fsummary>Get a file</fsummary>
+      <fsummary>Get a file.</fsummary>
       <desc>
-        <p>This function fetches a file using the low level loader.
-          <c><anno>Filename</anno></c> is either an absolute file name or just the name
-          of the file, for example <c>"lists.beam"</c>. If an internal
+        <p>Fetches a file using the low-level loader.
+          <c><anno>Filename</anno></c> is either an absolute filename or only
+          the name of the file, for example, <c>"lists.beam"</c>. If an internal
           path is set to the loader, this path is used to find the file.
           <c><anno>FullName</anno></c> is the complete name of the fetched file.
           <c><anno>Bin</anno></c> is the contents of the file as a binary.</p>
-
-	  <p>The <c><anno>Filename</anno></c> can also be a file in an archive. For example
+        <p><c><anno>Filename</anno></c> can also be a file in an archive,
+          for example,
           <c>$OTPROOT/lib/</c><c>mnesia-4.4.7.ez/mnesia-4.4.7/ebin/</c><c>mnesia.beam</c>.
-          See <seealso marker="kernel:code">code(3)</seealso> about archive files.</p>
+          For information about archive files, see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="get_path" arity="0"/>
-      <fsummary>Get the path set in the loader</fsummary>
+      <fsummary>Get the path set in the loader.</fsummary>
       <desc>
-        <p>This function gets the path set in the loader. The path is
-          set by the <c>init</c> process according to information found
-          in the start script.</p>
+        <p>Gets the path set in the loader. The path is
+          set by the <seealso marker="init"><c>init(3)</c></seealso>
+          process according to information found in the start script.</p>
       </desc>
     </func>
+
     <func>
       <name name="list_dir" arity="1"/>
-      <fsummary>List files in a directory</fsummary>
+      <fsummary>List files in a directory.</fsummary>
       <desc>
         <p>Lists all the files in a directory. Returns
-          <c>{ok, <anno>Filenames</anno>}</c> if successful. Otherwise, it returns
+          <c>{ok, <anno>Filenames</anno>}</c> if successful, otherwise
           <c>error</c>. <c><anno>Filenames</anno></c> is a list of
           the names of all the files in the directory. The names are
           not sorted.</p>
-	  <p>The <c><anno>Dir</anno></c> can also be a directory in an archive. For example
+        <p><c><anno>Dir</anno></c> can also be a directory in an archive,
+          for example,
           <c>$OTPROOT/lib/</c><c>mnesia-4.4.7.ez/mnesia-4.4.7/ebin</c>.
-           See <seealso marker="kernel:code">code(3)</seealso> about archive files.</p>
+          For information about archive files, see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="read_file_info" arity="1"/>
-      <fsummary>Get information about a file</fsummary>
+      <fsummary>Get information about a file.</fsummary>
       <desc>
         <p>Retrieves information about a file. Returns
           <c>{ok, <anno>FileInfo</anno>}</c> if successful, otherwise
           <c>error</c>. <c><anno>FileInfo</anno></c> is a record
-          <c>file_info</c>, defined in the Kernel include file
+          <c>file_info</c>, defined in the <c>Kernel</c> include file
           <c>file.hrl</c>. Include the following directive in the module
           from which the function is called:</p>
         <code type="none">
 -include_lib("kernel/include/file.hrl").</code>
-        <p>See <seealso marker="kernel:file">file(3)</seealso> for more info about
-          the record <c>file_info</c>.</p>
-	<p>The <c><anno>Filename</anno></c> can also be a file in an archive. For example
+        <p>For more information about the record <c>file_info</c>, see
+          <seealso marker="kernel:file"><c>kernel:file(3)</c></seealso>.</p>
+        <p><c><anno>Filename</anno></c> can also be a file in an archive,
+          for example,
           <c>$OTPROOT/lib/</c><c>mnesia-4.4.7.ez/mnesia-4.4.7/ebin/</c><c>mnesia</c>.
-          See <seealso marker="kernel:code">code(3)</seealso> about archive files.</p>
+          For information about archive files, see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="read_link_info" arity="1"/>
-      <fsummary>Get information about a link or file</fsummary>
+      <fsummary>Get information about a link or file.</fsummary>
       <desc>
-        <p>This function works like
-          <seealso marker="#read_file_info/1">read_file_info/1</seealso>
+        <p>Works like
+          <seealso marker="#read_file_info/1"><c>read_file_info/1</c></seealso>
           except that if <c><anno>Filename</anno></c> is a symbolic link,
-          information about the link will be returned in the <c>file_info</c>
-          record and the <c>type</c> field of the record will be set to
+          information about the link is returned in the <c>file_info</c>
+          record and the <c>type</c> field of the record is set to
           <c>symlink</c>.</p>
         <p>If <c><anno>Filename</anno></c> is not a symbolic link, this function
           returns exactly the same result as <c>read_file_info/1</c>.
@@ -126,20 +129,23 @@
           is always equivalent to <c>read_file_info/1</c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="set_path" arity="1"/>
-      <fsummary>Set the path of the loader</fsummary>
+      <fsummary>Set the path of the loader.</fsummary>
       <desc>
-        <p>This function sets the path of the loader if <c>init</c>
+        <p>Sets the path of the loader if
+          <seealso marker="init"><c>init(3)</c></seealso>
           interprets a <c>path</c> command in the start script.</p>
       </desc>
     </func>
   </funcs>
 
   <section>
-    <title>Command Line Flags</title>
+    <title>Command-Line Flags</title>
     <p>The <c>erl_prim_loader</c> module interprets the following
-      command line flags:</p>
+      command-line flags:</p>
+
     <taglist>
       <tag><c>-loader Loader</c></tag>
       <item>
@@ -147,37 +153,38 @@
           <c>erl_prim_loader</c>. <c>Loader</c> can be <c>efile</c>
           (use the local file system) or <c>inet</c> (load using
           the <c>boot_server</c> on another Erlang node).</p>
-        <p>If the <c>-loader</c> flag is omitted, it defaults to
+        <p>If flag <c>-loader</c> is omitted, it defaults to
           <c>efile</c>.</p>
       </item>
       <tag><c>-loader_debug</c></tag>
       <item>
           <p>Makes the <c>efile</c> loader write some debug information,
-           such as the reason for failures, while it handles files.</p>
+            such as the reason for failures, while it handles files.</p>
       </item>
       <tag><c>-hosts Hosts</c></tag>
       <item>
         <p>Specifies which other Erlang nodes the <c>inet</c> loader
-          can use. This flag is mandatory if the <c>-loader inet</c>
-          flag is present. On each host, there must be on Erlang node
-          with the <seealso
-          marker="kernel:erl_boot_server">erl_boot_server(3)</seealso>
-	  which handles the load requests.
-	  <c>Hosts</c> is a list of IP addresses (hostnames
+          can use. This flag is mandatory if flag <c>-loader inet</c>
+          is present. On each host, there must be on Erlang node
+          with the <seealso marker="kernel:erl_boot_server">
+          <c>kernel:erl_boot_server(3)</c></seealso>,
+          which handles the load requests.
+          <c>Hosts</c> is a list of IP addresses (hostnames
           are not acceptable).</p>
       </item>
       <tag><c>-setcookie Cookie</c></tag>
       <item>
         <p>Specifies the cookie of the Erlang runtime system. This flag
-          is mandatory if the <c>-loader inet</c> flag is present.</p>
+          is mandatory if flag <c>-loader inet</c> is present.</p>
       </item>
     </taglist>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="init">init(3)</seealso>, 
-      <seealso marker="kernel:erl_boot_server">erl_boot_server(3)</seealso></p>
+    <title>See Also</title>
+    <p><seealso marker="init"><c>init(3)</c></seealso>,
+      <seealso marker="kernel:erl_boot_server">
+      <c>kernel:erl_boot_server(3)</c></seealso></p>
   </section>
 </erlref>
 
diff --git a/erts/doc/src/erl_tracer.xml b/erts/doc/src/erl_tracer.xml
index e2852ce49d..a2cfed684b 100644
--- a/erts/doc/src/erl_tracer.xml
+++ b/erts/doc/src/erl_tracer.xml
@@ -29,488 +29,618 @@
     <rev></rev>
   </header>
   <module>erl_tracer</module>
-  <modulesummary>Erlang Tracer Behaviour</modulesummary>
+  <modulesummary>Erlang tracer behavior.</modulesummary>
   <description>
-    <p>A behaviour module for implementing the back end of the erlang
-    tracing system. The functions in this module will be called whenever
-    a trace probe is triggered. Both the <c>enabled</c> and <c>trace</c>
-    functions are called in the context of the entity that triggered the
-    trace probe.
-    This means that the overhead by having the tracing enabled will be
-    greatly effected by how much time is spent in these functions. So do as
-    little work as possible in these functions.</p>
+    <p>This behavior module implements the back end of the Erlang
+      tracing system. The functions in this module are called whenever
+      a trace probe is triggered. Both the <c>enabled</c> and <c>trace</c>
+      functions are called in the context of the entity that triggered the
+      trace probe.
+      This means that the overhead by having the tracing enabled is
+      greatly effected by how much time is spent in these functions. So, do as
+      little work as possible in these functions.</p>
+
     <note>
-      <p>All functions in this behaviour have to be implemented as NIF's.
-      This is a limitation that may the lifted in the future.
-      There is an <seealso marker="#example">example tracer module nif</seealso>
-      implementation at the end of this page.</p>
+      <p>All functions in this behavior must be implemented as NIFs.
+        This limitation can be removed in a future releases.
+        An <seealso marker="#example">example tracer module NIF</seealso>
+        implementation is provided at the end of this page.</p>
     </note>
+
     <warning>
       <p>Do not send messages or issue port commands to the <c>Tracee</c>
-      in any of the callbacks. Doing so is not allowed and can cause all
-      sorts of strange behaviour, including but not limited to infinite
-      recursions.</p>
+        in any of the callbacks. This is not allowed and can cause all
+        sorts of strange behavior, including, but not limited to, infinite
+        recursions.</p>
     </warning>
   </description>
 
   <datatypes>
-      <datatype> <name name="trace_tag_send" /> </datatype>
-      <datatype> <name name="trace_tag_receive" /> </datatype>
-      <datatype> <name name="trace_tag_call" /> </datatype>
-      <datatype> <name name="trace_tag_procs" /> </datatype>
-      <datatype> <name name="trace_tag_ports" /> </datatype>
-      <datatype> <name name="trace_tag_running_procs" /> </datatype>
-      <datatype> <name name="trace_tag_running_ports" /> </datatype>
-      <datatype> <name name="trace_tag_gc" /> </datatype>
     <datatype>
-      <name name="trace_tag" />
+      <name name="trace_tag_call"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag_gc"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag_ports"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag_procs"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag_receive"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag_running_ports"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag_running_procs"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag_send"/>
+    </datatype>
+    <datatype>
+      <name name="trace_tag"/>
       <desc>
-	<p>The different trace tags that the tracer will be called with.
-        Each trace tag is described in greater detail in
-        <seealso marker="#Module:trace/5">Module:trace/5</seealso>
-        </p>
+        <p>The different trace tags that the tracer is called with.
+          Each trace tag is described in detail in
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>.</p>
       </desc>
     </datatype>
     <datatype>
-      <name name="tracee" />
+      <name name="tracee"/>
       <desc>
-	<p>The process or port that the trace belongs to.
-        </p>
+        <p>The process or port that the trace belongs to.</p>
       </desc>
     </datatype>
     <datatype>
-      <name name="trace_opts" />
+      <name name="trace_opts"/>
       <desc>
-	<p>The options for the tracee.</p>
+        <p>The options for the tracee:</p>
         <taglist>
           <tag><c>timestamp</c></tag>
-          <item>If set the tracer has been requested to include a timestamp.</item>
+          <item>If set the tracer has been requested to include a
+            time stamp.</item>
           <tag><c>extra</c></tag>
           <item>If set the tracepoint has included additonal data about
-          the trace event. What the additional data is depends on which
-          <c>TraceTag</c> has been triggered. The <c>extra</c> trace data
-          corresponds to the fifth elemnt in the trace tuples described in
-          <seealso marker="erlang#trace_3_trace_messages">erlang:trace/3</seealso>.</item>
+            the trace event. What the additional data is depends on which
+            <c>TraceTag</c> has been triggered. The <c>extra</c> trace data
+            corresponds to the fifth element in the trace tuples described in
+            <seealso marker="erlang#trace_3_trace_messages">
+              erlang:trace/3</seealso>.</item>
           <tag><c>match_spec_result</c></tag>
           <item>If set the tracer has been requested to include the output
-          of a match specification that was run.</item>
+            of a match specification that was run.</item>
           <tag><c>scheduler_id</c></tag>
-          <item>Set the scheduler id is to be included by the tracer.</item>
+          <item>If set the scheduler id is to be included by the tracer.</item>
         </taglist>
       </desc>
     </datatype>
     <datatype>
-      <name name="tracer_state" />
+      <name name="tracer_state"/>
       <desc>
-        <p>
-          The state which is given when calling
-          <seealso marker="erlang#trace-3"><c>erlang:trace(PidPortSpec,true,[{tracer,Module,TracerState}])</c></seealso>.
-          The tracer state is an immutable value that is passed to erl_tracer callbacks and should
-          contain all the data that is needed to generate the trace event.
-        </p>
+        <p>The state specified when calling
+          <seealso marker="erlang#trace-3">
+          <c>erlang:trace(PidPortSpec,true,[{tracer,Module,TracerState}])</c></seealso>.
+          The tracer state is an immutable value that is passed to
+          <c>erl_tracer</c> callbacks and is to
+          contain all the data that is needed to generate the trace event.</p>
       </desc>
     </datatype>
   </datatypes>
 
   <section>
-    <title>CALLBACK FUNCTIONS</title>
-    <p>The following functions
-      should be exported from a <c>erl_tracer</c> callback module.</p>
-   <taglist>
-       <tag><seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso></tag>
-       <item>Mandatory</item>
-       <tag><seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso></tag>
-       <item>Mandatory</item>
-       <tag><seealso marker="#Module:enabled_procs/3"><c>Module:enabled_procs/3</c></seealso></tag>
-       <item>Optional</item>
-       <tag><seealso marker="#Module:trace_procs/5"><c>Module:trace_procs/5</c></seealso></tag>
-       <item>Optional</item>
-       <tag><seealso marker="#Module:enabled_ports/3"><c>Module:enabled_ports/3</c></seealso></tag>
-       <item>Optional</item>
-       <tag><seealso marker="#Module:trace_ports/5"><c>Module:trace_ports/5</c></seealso></tag>
-       <item>Optional</item>
-       <tag><seealso marker="#Module:enabled_running_ports/3"><c>Module:enabled_running_ports/3</c></seealso></tag>
-       <item>Optional</item>
-       <tag><seealso marker="#Module:trace_running_ports/5"><c>Module:trace_running_ports/5</c></seealso></tag>
-       <item>Optional</item>
-       <tag><seealso marker="#Module:enabled_running_procs/3"><c>Module:enabled_running_procs/3</c></seealso></tag>
-       <item>Optional</item>
-       <tag><seealso marker="#Module:trace_running_procs/5"><c>Module:trace_running_procs/5</c></seealso></tag>
-       <item>Optional</item>
+    <title>Callback Functions</title>
+    <p>The following functions are to be exported from an <c>erl_tracer</c>
+      callback module:</p>
+
+    <taglist>
+      <tag><seealso marker="#Module:enabled/3">
+        <c>Module:enabled/3</c></seealso></tag>
+      <item>Mandatory</item>
+      <tag><seealso marker="#Module:trace/5">
+        <c>Module:trace/5</c></seealso></tag>
+      <item>Mandatory</item>
+      <tag><seealso marker="#Module:enabled_call/3">
+        <c>Module:enabled_call/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_call/5">
+        <c>Module:trace_call/5</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:enabled_garbage_collection/3">
+        <c>Module:enabled_garbage_collection/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_garbage_collection/5">
+        <c>Module:trace_garbage_collection/5</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:enabled_ports/3">
+        <c>Module:enabled_ports/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_ports/5">
+        <c>Module:trace_ports/5</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:enabled_procs/3">
+        <c>Module:enabled_procs/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_procs/5">
+        <c>Module:trace_procs/5</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:enabled_receive/3">
+        <c>Module:enabled_receive/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_receive/5">
+        <c>Module:trace_receive/5</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:enabled_running_ports/3">
+        <c>Module:enabled_running_ports/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_running_ports/5">
+        <c>Module:trace_running_ports/5</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:enabled_running_procs/3">
+        <c>Module:enabled_running_procs/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_running_procs/5">
+        <c>Module:trace_running_procs/5</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:enabled_send/3">
+        <c>Module:enabled_send/3</c></seealso></tag>
+      <item>Optional</item>
+      <tag><seealso marker="#Module:trace_send/5">
+        <c>Module:trace_send/5</c></seealso></tag>
+      <item>Optional</item>
    </taglist>
-
   </section>
 
   <funcs>
     <func>
       <name>Module:enabled(TraceTag, TracerState, Tracee) -> Result</name>
-      <fsummary>Check if a trace event should be generated.</fsummary>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
       <type>
-        <v>TraceTag = <seealso marker="#type-trace_tag">trace_tag()</seealso> | trace_status</v>
+        <v>TraceTag = <seealso marker="#type-trace_tag">
+          trace_tag()</seealso> | trace_status</v>
         <v>TracerState = term()</v>
         <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-        <v>Result =  trace | discard | remove</v>
+        <v>Result = trace | discard | remove</v>
       </type>
       <desc>
-        <p>This callback will be called whenever a tracepoint is triggered. It
-        allows the tracer to decide whether a trace should be generated or not.
-        This check is made as early as possible in order to limit the amount of
-        overhead associated with tracing. If <c>trace</c> is returned the
-        necessary trace data will be created and the trace call-back of the tracer
-        will be called. If <c>discard</c> is returned, this trace call
-        will be discarded and no call to trace will be done.
-        </p>
-        <p><c>trace_status</c> is a special type of <c>TraceTag</c> which is used
-        to check if the tracer should still be active. It is called in multiple
-        scenarios, but most significantly it is used when tracing is started
-        using this tracer. If <c>remove</c> is returned when the <c>trace_status</c>
-        is checked, the tracer will be removed from the tracee.</p>
-        <p>This function may be called multiple times per tracepoint, so it
-        is important that it is both fast and side effect free.</p>
+        <p>This callback is called whenever a tracepoint is triggered. It
+          allows the tracer to decide whether a trace is to be generated or not.
+          This check is made as early as possible to limit the amount of
+          overhead associated with tracing. If <c>trace</c> is returned, the
+          necessary trace data is created and the trace callback of the tracer
+          is called. If <c>discard</c> is returned, this trace call is
+          discarded and no call to trace is done.</p>
+        <p><c>trace_status</c> is a special type of <c>TraceTag</c>, which is
+          used to check if the tracer is still to be active. It is called in
+          multiple scenarios, but most significantly it is used when tracing
+          is started using this tracer. If <c>remove</c> is returned when the
+          <c>trace_status</c> is checked, the tracer is removed from the
+          tracee.</p>
+        <p>This function can be called multiple times per tracepoint, so it
+          is important that it is both fast and without side effects.</p>
       </desc>
     </func>
 
     <func>
-        <name>Module:enabled_call(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_call">trace_tag_call()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>call | return_to</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_call/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_call(TraceTag, TracerState, Tracee) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_call">
+          trace_tag_call()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3"><c>call | return_to</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_call/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:enabled_garbage_collection(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_gc">trace_tag_gc()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>garbage_collection</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_garbage_collection/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_garbage_collection(TraceTag, TracerState, Tracee) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_gc">
+          trace_tag_garbage_collection()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3"><c>garbage_collection</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_garbage_collection/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:enabled_ports(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_ports">trace_tag_ports()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>ports</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_ports/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_ports(TraceTag, TracerState, Tracee) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_ports">
+          trace_tag_ports()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3"><c>ports</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_ports/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:enabled_procs(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_procs">trace_tag_procs()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>procs</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_procs/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_procs(TraceTag, TracerState, Tracee) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_procs">
+          trace_tag_procs()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3"><c>procs</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_procs/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:enabled_receive(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_receive">trace_tag_receive()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>'receive'</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_receive/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_receive(TraceTag, TracerState, Tracee) -> Result
+      </name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_receive">
+          trace_tag_receive()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3"><c>'receive'</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_receive/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:enabled_running_ports(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_running_ports">trace_tag_running_ports()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>running_ports</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_running_ports/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_running_ports(TraceTag, TracerState, Tracee) ->
+        Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_running_ports">
+          trace_tag_running_ports()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3"><c>running_ports</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_running_ports/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:enabled_running_procs(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_running_procs">trace_tag_running_procs()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>running_procs | running</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_running_procs/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_running_procs(TraceTag, TracerState, Tracee) ->
+        Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_running_procs">
+          trace_tag_running_procs()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3">
+          <c>running_procs | running</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_running_procs/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:enabled_send(TraceTag, TracerState, Tracee) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_send">trace_tag_send()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>Result = trace | discard | remove</v>
-        </type>
-        <desc>
-            <p>This callback will be called whenever a tracepoint with trace flag
-                <seealso marker="erlang#trace-3"><c>send</c></seealso>
-                is triggered.</p>
-            <p>If <c>enabled_send/3</c> is not defined <c>enabled/3</c> will be called instead.</p>
-        </desc>
+      <name>Module:enabled_send(TraceTag, TracerState, Tracee) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_send">
+          trace_tag_send()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>Result = trace | discard | remove</v>
+      </type>
+      <desc>
+        <p>This callback is called whenever a tracepoint with trace flag
+          <seealso marker="erlang#trace-3"><c>send</c></seealso>
+          is triggered.</p>
+        <p>If <c>enabled_send/3</c> is undefined,
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-      <name>Module:trace(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-      <fsummary>Check if a trace event should be generated.</fsummary>
+      <name>Module:trace(TraceTag, TracerState, Tracee, TraceTerm,
+        Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
       <type>
-        <v>TraceTag = <seealso marker="#type-trace_tag">trace_tag()</seealso></v>
+        <v>TraceTag = <seealso marker="#type-trace_tag">
+          trace_tag()</seealso></v>
         <v>TracerState = term()</v>
         <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-        <v>FirstTraceTerm = term()</v>
+        <v>TraceTerm = term()</v>
         <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-        <v>Result =  ok</v>
+        <v>Result = ok</v>
       </type>
       <desc>
-        <p>This callback will be called when a tracepoint is triggered and
-        the <seealso marker="#Module:enabled/3">Module:enabled/3</seealso>
-        callback returned <c>trace</c>. In it any side effects needed by
-        the tracer should be done. The tracepoint payload is located in
-        the <c>TraceTerm</c>. The content of the TraceTerm depends on which
-        <c>TraceTag</c> has been triggered.
-        The <c>TraceTerm</c> corresponds to the
-        fourth element in the trace tuples described in
-        <seealso marker="erlang#trace_3_trace_messages">erlang:trace/3</seealso>.
-        If the trace tuple has five elements, the fifth element will be sent as
-        the <c>extra</c> value in the <c>Opts</c> maps.</p>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled/3"><c>Module:enabled/3</c></seealso>
+          callback returned <c>trace</c>. In it any side effects needed by
+          the tracer are to be done. The tracepoint payload is located in
+          the <c>TraceTerm</c>. The content of the <c>TraceTerm</c>
+          depends on which <c>TraceTag</c> is triggered.
+          <c>TraceTerm</c> corresponds to the
+          fourth element in the trace tuples described in
+          <seealso marker="erlang#trace_3_trace_messages">
+          <c>erlang:trace/3</c></seealso>.</p>
+        <p>If the trace tuple has five elements, the fifth element
+          will be sent as the <c>extra</c> value in the <c>Opts</c> maps.</p>
       </desc>
     </func>
+
     <func>
-      <name name="trace">Module:trace(seq_trace, TracerState, Label, SeqTraceInfo, Opts) -> Result</name>
-      <fsummary>Check if a sequence trace event should be generated.</fsummary>
+      <name name="trace">Module:trace(seq_trace, TracerState, Label,
+        SeqTraceInfo, Opts) -> Result</name>
+      <fsummary>Check if a sequence trace event is to be generated.</fsummary>
       <type>
         <v>TracerState = term()</v>
         <v>Label = term()</v>
         <v>SeqTraceInfo = term()</v>
         <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-        <v>Result =  ok</v>
+        <v>Result = ok</v>
       </type>
       <desc>
-        <p>The <c>TraceTag</c> <c>seq_trace</c> is handled a little bit
-        differently. There is not <c>Tracee</c> for seq_trace, instead the
-        <c>Label</c> associated with the seq_trace event is given.
-        For more info on what <c>Label</c> and <c>SeqTraceInfo</c> can be
-        see the <seealso marker="kernel:seq_trace">seq_trace</seealso> manual.</p>
+        <p>The <c>TraceTag</c> <c>seq_trace</c> is handled slightly
+          differently. There is no <c>Tracee</c> for <c>seq_trace</c>, instead
+          the <c>Label</c> associated with the <c>seq_trace</c> event is
+          specified.</p>
+        <p>For more information on what <c>Label</c> and <c>SeqTraceInfo</c>
+          can be, see <seealso marker="kernel:seq_trace">
+          <c>kernel:seq_trace</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
-        <name>Module:trace_call(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_call">trace_tag_call()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result = ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_call/3">Module:enabled_call/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_call/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_call(TraceTag, TracerState, Tracee, TraceTerm,
+          Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_call">
+          trace_tag_call()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_call/3">
+          <c>Module:enabled_call/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_call/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:trace_garbage_collection(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_gc">trace_tag_gc()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result =  ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_garbage_collection/3">Module:enabled_garbage_collection/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_garbage_collection/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_garbage_collection(TraceTag, TracerState, Tracee,
+        TraceTerm, Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_gc">
+          trace_tag_gc()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_garbage_collection/3">
+          <c>Module:enabled_garbage_collection/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_garbage_collection/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:trace_ports(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_ports">trace_tag()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result = ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_ports/3">Module:enabled_ports/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_ports/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_ports(TraceTag, TracerState, Tracee, TraceTerm,
+        Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_ports">
+          trace_tag()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_ports/3">
+          <c>Module:enabled_ports/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_ports/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:trace_procs(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_procs">trace_tag()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result = ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_procs/3">Module:enabled_procs/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_procs/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_procs(TraceTag, TracerState, Tracee, TraceTerm,
+        Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_procs">
+          trace_tag()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_procs/3">
+          <c>Module:enabled_procs/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_procs/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:trace_receive(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_receive">trace_tag_receive()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result =  ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_receive/3">Module:enabled_receive/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_receive/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_receive(TraceTag, TracerState, Tracee, TraceTerm,
+        Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_receive">
+          trace_tag_receive()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_receive/3">
+          <c>Module:enabled_receive/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_receive/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:trace_running_ports(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_running_ports">trace_tag_running_ports()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result = ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_running_ports/3">Module:enabled_running_ports/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_running_ports/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_running_ports(TraceTag, TracerState, Tracee,
+        TraceTerm, Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_running_ports">
+          trace_tag_running_ports()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_running_ports/3">
+          <c>Module:enabled_running_ports/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_running_ports/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:trace_running_procs(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_running_procs">trace_tag_running_procs()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result = ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_running_procs/3">Module:enabled_running_procs/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_running_procs/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_running_procs(TraceTag, TracerState, Tracee,
+        TraceTerm, Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_running_procs">
+          trace_tag_running_procs()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_running_procs/3">
+          <c>Module:enabled_running_procs/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_running_procs/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
 
     <func>
-        <name>Module:trace_send(TraceTag, TracerState, Tracee, TraceTerm, Opts) -> Result</name>
-        <fsummary>Check if a trace event should be generated.</fsummary>
-        <type>
-            <v>TraceTag = <seealso marker="#type-trace_tag_send">trace_tag_send()</seealso></v>
-            <v>TracerState = term()</v>
-            <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
-            <v>FirstTraceTerm = term()</v>
-            <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
-            <v>Result =  ok</v>
-        </type>
-        <desc>
-            <p>This callback will be called when a tracepoint is triggered and
-                the <seealso marker="#Module:enabled_send/3">Module:enabled_send/3</seealso>
-                callback returned <c>trace</c>.</p>
-            <p>If <c>trace_send/5</c> is not defined <c>trace/5</c> will be called instead.</p>
-        </desc>
+      <name>Module:trace_send(TraceTag, TracerState, Tracee, TraceTerm,
+        Opts) -> Result</name>
+      <fsummary>Check if a trace event is to be generated.</fsummary>
+      <type>
+        <v>TraceTag = <seealso marker="#type-trace_tag_send">
+          trace_tag_send()</seealso></v>
+        <v>TracerState = term()</v>
+        <v>Tracee = <seealso marker="#type-tracee">tracee()</seealso></v>
+        <v>TraceTerm = term()</v>
+        <v>Opts = <seealso marker="#type-trace_opts">trace_opts()</seealso></v>
+        <v>Result = ok</v>
+      </type>
+      <desc>
+        <p>This callback is called when a tracepoint is triggered and the
+          <seealso marker="#Module:enabled_send/3">
+          <c>Module:enabled_send/3</c></seealso>
+          callback returned <c>trace</c>.</p>
+        <p>If <c>trace_send/5</c> is undefined,
+          <seealso marker="#Module:trace/5"><c>Module:trace/5</c></seealso>
+          is called instead.</p>
+      </desc>
     </func>
-
   </funcs>
+
   <section>
     <marker id="example"></marker>
-    <title>Erl Tracer Module example</title>
-    <p>In the example below a tracer module with a nif backend sends a message
-    for each <c>send</c> trace tag containing only the sender and receiver.
-    Using this tracer module, a much more lightweight message tracer is
-    used that only records who sent messages to who.</p>
-    <p>Here is an example session using it on Linux.</p>
+    <title>Erl Tracer Module Example</title>
+    <p>In this example, a tracer module with a NIF back end sends a
+      message for each <c>send</c> trace tag containing only the sender and
+      receiver. Using this tracer module, a much more lightweight message
+      tracer is used, which only records who sent messages to who.</p>
+
+    <p>The following is an example session using it on Linux:</p>
+
     <pre>
 $ gcc -I erts-8.0/include/ -fPIC -shared -o erl_msg_tracer.so erl_msg_tracer.c
 $ erl
@@ -533,9 +663,10 @@ ok
 {trace,#Port&lt;0.490&gt;,&lt;0.4.0&gt;}
 {ok,&lt;0.40.0&gt;}
 {trace,&lt;0.41.0&gt;,&lt;0.27.0&gt;}
-5&gt;
-    </pre>
-    <p>erl_msg_tracer.erl</p>
+5&gt;</pre>
+
+    <p><c>erl_msg_tracer.erl</c>:</p>
+
     <pre>
 -module(erl_msg_tracer).
 
@@ -547,10 +678,11 @@ load() ->
 enabled(_, _, _) ->
     error.
 
-trace(_, _, _,_, _) ->
-    error.
-    </pre>
-    <p>erl_msg_tracer.c</p>
+trace(_, _, _, _, _) ->
+    error.</pre>
+
+    <p><c>erl_msg_tracer.c</c>:</p>
+
     <pre>
 #include "erl_nif.h"
 
@@ -641,7 +773,6 @@ static ERL_NIF_TERM trace(ErlNifEnv* env, int argc, const ERL_NIF_TERM argv[])
     }
 
     return enif_make_atom(env, "ok");
-}
-    </pre>
+}</pre>
   </section>
 </erlref>
diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml
index cab18ac8b8..3356447168 100644
--- a/erts/doc/src/erlang.xml
+++ b/erts/doc/src/erlang.xml
@@ -32,18 +32,21 @@
   <module>erlang</module>
   <modulesummary>The Erlang BIFs.</modulesummary>
   <description>
-    <p>By convention, most Built-In Functions (BIFs) are seen as being
+    <p>By convention, most Built-In Functions (BIFs) are included
       in this module. Some of the BIFs are viewed more
       or less as part of the Erlang programming language and are
       <em>auto-imported</em>. Thus, it is not necessary to specify the
       module name. For example, the calls <c>atom_to_list(Erlang)</c>
       and <c>erlang:atom_to_list(Erlang)</c> are identical.</p>
+
     <p>Auto-imported BIFs are listed without module prefix.
       BIFs listed with module prefix are not auto-imported.</p>
+
     <p>BIFs can fail for various reasons. All BIFs fail with
       reason <c>badarg</c> if they are called with arguments of an
       incorrect type. The other reasons are described in the
       description of each individual BIF.</p>
+
     <p>Some BIFs can be used in guard tests and are marked with
       "Allowed in guard tests".</p>
   </description>
@@ -53,107 +56,104 @@
       <name>ext_binary()</name>
       <desc>
         <p>A binary data object, structured according to
-           the Erlang external term format.</p>
+          the Erlang external term format.</p>
       </desc>
     </datatype>
-
     <datatype>
       <name name="message_queue_data"></name>
-      <desc><p>See <seealso marker="#process_flag_message_queue_data"><c>erlang:process_flag(message_queue_data, MQD)</c></seealso>.</p>
+      <desc>
+        <p>See <seealso marker="#process_flag_message_queue_data">
+          <c>process_flag(message_queue_data, MQD)</c></seealso>.</p>
       </desc>
     </datatype>
-
     <datatype>
       <name name="timestamp"></name>
-      <desc><p>See <seealso marker="#timestamp/0">erlang:timestamp/0</seealso>.</p>
+      <desc>
+        <p>See <seealso marker="#timestamp/0">
+          <c>erlang:timestamp/0</c></seealso>.</p>
       </desc>
     </datatype>
     <datatype>
       <name name="time_unit"></name>
-      <desc><p><marker id="type_time_unit"/>
-        Supported time unit representations:</p>
+      <desc>
+        <marker id="type_time_unit"/>
+        <p>Supported time unit representations:</p>
         <taglist>
-	  <tag><c>PartsPerSecond :: integer() >= 1</c></tag>
-	  <item>
+          <tag><c>PartsPerSecond :: integer() >= 1</c></tag>
+          <item>
             <p>Time unit expressed in parts per second. That is,
-	  the time unit equals <c>1/PartsPerSecond</c> second.</p></item>
-
-	  <tag><c>seconds</c></tag>
-	  <item>
+              the time unit equals <c>1/PartsPerSecond</c> second.</p>
+          </item>
+          <tag><c>seconds</c></tag>
+          <item>
             <p>Symbolic representation of the time unit
-	  represented by the integer <c>1</c>.</p></item>
-
-	  <tag><c>milli_seconds</c></tag>
-	  <item>
+              represented by the integer <c>1</c>.</p>
+          </item>
+          <tag><c>milli_seconds</c></tag>
+          <item>
             <p>Symbolic representation of the time unit
-	  represented by the integer <c>1000</c>.</p></item>
-
-	  <tag><c>micro_seconds</c></tag>
-	  <item>
+              represented by the integer <c>1000</c>.</p>
+          </item>
+          <tag><c>micro_seconds</c></tag>
+          <item>
             <p>Symbolic representation of the time unit
-	  represented by the integer <c>1000000</c>.</p></item>
-
-	  <tag><c>nano_seconds</c></tag>
-	  <item>
+              represented by the integer <c>1000000</c>.</p>
+          </item>
+          <tag><c>nano_seconds</c></tag>
+          <item>
             <p>Symbolic representation of the time unit
-	  represented by the integer <c>1000000000</c>.</p></item>
-
-	  <tag><c>native</c></tag>
-	  <item>
+              represented by the integer <c>1000000000</c>.</p>
+          </item>
+          <tag><c>native</c></tag>
+          <item>
             <p>Symbolic representation of the native time unit
-	  used by the Erlang runtime system.</p>
-
-	  <p>The <c>native</c> time unit is determined at
-	  runtime system start, and remains the same until
-	  the runtime system terminates. If a runtime system
-	  is stopped and then started again (even on the same
-	  machine), the <c>native</c> time unit of the new
-	  runtime system instance can differ from the
-	  <c>native</c> time unit of the old runtime system
-	  instance.</p>
-
-	  <p>One can get an approximation of the <c>native</c>
-	  time unit by calling <c>erlang:convert_time_unit(1,
-	  seconds, native)</c>. The result equals the number
-	  of whole <c>native</c> time units per second. In case
-	  the number of <c>native</c> time units per second does
-	  not add up to a whole number, the result is rounded downwards.</p>
-
-	  <note>
-	    <p>The value of the <c>native</c> time unit gives
-	    you more or less no information at all about the
-	    quality of time values. It sets a limit for
-	    the
-	    <seealso marker="time_correction#Time_Resolution">resolution</seealso>
-	    as well as for the
-	    <seealso marker="time_correction#Time_Precision">precision</seealso>
-	    of time values,
-	    but it gives absolutely no information at all about the
-	    <seealso marker="time_correction#Time_Accuracy">accuracy</seealso>
-	    of time values. The resolution of the <c>native</c> time
-	    unit and the resolution of time values can differ
-	    significantly.</p>
-	  </note>
-	  </item>
-
-	  <tag><c>perf_counter</c></tag>
-	  <item>
+              used by the Erlang runtime system.</p>
+            <p>The <c>native</c> time unit is determined at
+              runtime system start, and remains the same until
+              the runtime system terminates. If a runtime system
+              is stopped and then started again (even on the same
+              machine), the <c>native</c> time unit of the new
+              runtime system instance can differ from the
+              <c>native</c> time unit of the old runtime system
+              instance.</p>
+            <p>One can get an approximation of the <c>native</c>
+              time unit by calling
+              <seealso marker="erlang:convert_time_unit/3">
+              <c>erlang:convert_time_unit(1, seconds, native)</c></seealso>.
+              The result equals the number
+              of whole <c>native</c> time units per second. If
+              the number of <c>native</c> time units per second does not
+              add up to a whole number, the result is rounded downwards.</p>
+            <note>
+              <p>The value of the <c>native</c> time unit gives
+                you more or less no information about the
+                quality of time values. It sets a limit for the
+                <seealso marker="time_correction#Time_Resolution">
+                resolution</seealso> and for the
+                <seealso marker="time_correction#Time_Precision">
+                precision</seealso> of time values,
+                but it gives no information about the
+                <seealso marker="time_correction#Time_Accuracy">
+                accuracy</seealso> of time values. The resolution of
+                the <c>native</c> time unit and the resolution of time
+                values can differ significantly.</p>
+            </note>
+          </item>
+          <tag><c>perf_counter</c></tag>
+          <item>
             <p>Symbolic representation of the performance counter
-          time unit used by the Erlang runtime system.</p>
-
-          <p>The <c>perf_counter</c> time unit behaves much in the same way
-          as the <c>native</c> time unit. That is it might differ inbetween
-          run-time restarts. You get values of this type by calling
-          <seealso marker="kernel:os#perf_counter/0"><c>os:perf_counter()</c></seealso>
-          </p>
+              time unit used by the Erlang runtime system.</p>
+            <p>The <c>perf_counter</c> time unit behaves much in the same way
+              as the <c>native</c> time unit. That is, it can differ between
+              runtime restarts. To get values of this type, call
+              <seealso marker="kernel:os#perf_counter/0">
+              <c>os:perf_counter()</c></seealso>.</p>
           </item>
-
-	</taglist>
-
-	<p>The <c>time_unit/0</c> type may be extended. Use
-	<seealso marker="#convert_time_unit/3"><c>erlang:convert_time_unit/3</c></seealso>
-	in order to convert time values between time units.</p>
-
+        </taglist>
+        <p>The <c>time_unit/0</c> type can be extended.
+          To convert time values between time units, use
+          <seealso marker="#convert_time_unit/3">
+          <c>erlang:convert_time_unit/3</c></seealso>.</p>
       </desc>
     </datatype>
   </datatypes>
@@ -182,61 +182,60 @@
 
     <func>
       <name name="adler32" arity="1"/>
-      <fsummary>Computes adler32 checksum.</fsummary>
+      <fsummary>Compute adler32 checksum.</fsummary>
       <desc>
         <p>Computes and returns the adler32 checksum for
-        <c><anno>Data</anno></c>.</p>
+          <c><anno>Data</anno></c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="adler32" arity="2"/>
-      <fsummary>Computes adler32 checksum.</fsummary>
+      <fsummary>Compute adler32 checksum.</fsummary>
       <desc>
         <p>Continues computing the adler32 checksum by combining 
-        the previous checksum, <c><anno>OldAdler</anno></c>, with
-	the checksum of <c><anno>Data</anno></c>.</p>
+          the previous checksum, <c><anno>OldAdler</anno></c>, with
+          the checksum of <c><anno>Data</anno></c>.</p>
         <p>The following code:</p>
         <code>
-        X = erlang:adler32(Data1),
-        Y = erlang:adler32(X,Data2).</code>
-	<p>assigns the same value to <c>Y</c> as this:</p>
+X = erlang:adler32(Data1),
+Y = erlang:adler32(X,Data2).</code>
+        <p>assigns the same value to <c>Y</c> as this:</p>
         <code>
-        Y = erlang:adler32([Data1,Data2]).</code>
+Y = erlang:adler32([Data1,Data2]).</code>
       </desc>
     </func>
 
     <func>
       <name name="adler32_combine" arity="3"/>
-      <fsummary>Combines two adler32 checksums.</fsummary>
+      <fsummary>Combine two adler32 checksums.</fsummary>
       <desc>
         <p>Combines two previously computed adler32 checksums.
-        This computation requires the size of the data object for
-        the second checksum to be known.</p>
+          This computation requires the size of the data object for
+          the second checksum to be known.</p>
         <p>The following code:</p>
         <code>
-        Y = erlang:adler32(Data1),
-        Z = erlang:adler32(Y,Data2).</code>
+Y = erlang:adler32(Data1),
+Z = erlang:adler32(Y,Data2).</code>
         <p>assigns the same value to <c>Z</c> as this:</p>
         <code>
-        X = erlang:adler32(Data1),
-        Y = erlang:adler32(Data2),
-        Z = erlang:adler32_combine(X,Y,iolist_size(Data2)).</code>
+X = erlang:adler32(Data1),
+Y = erlang:adler32(Data2),
+Z = erlang:adler32_combine(X,Y,iolist_size(Data2)).</code>
       </desc>
     </func>
 
     <func>
       <name name="append_element" arity="2"/>
-      <fsummary>Appends an extra element to a tuple.</fsummary>
+      <fsummary>Append an extra element to a tuple.</fsummary>
       <desc>
         <p>Returns a new tuple that has one element more than
           <c><anno>Tuple1</anno></c>, and contains the elements in
-	  <c><anno>Tuple1</anno></c>
+          <c><anno>Tuple1</anno></c>
           followed by <c><anno>Term</anno></c> as the last element.
-	  Semantically equivalent to
+          Semantically equivalent to
           <c>list_to_tuple(tuple_to_list(<anno>Tuple1</anno>) ++
-	  [<anno>Term</anno>])</c>, but much faster.</p>
-        <p>Example:</p>
+          [<anno>Term</anno>])</c>, but much faster. Example:</p>
         <pre>
 > <input>erlang:append_element({one, two}, three).</input>
 {one,two,three}</pre>
@@ -245,32 +244,31 @@
 
     <func>
       <name name="apply" arity="2"/>
-      <fsummary>Applies a function to an argument list.</fsummary>
+      <fsummary>Apply a function to an argument list.</fsummary>
       <desc>
         <p>Calls a fun, passing the elements in <c><anno>Args</anno></c>
-	  as arguments.</p>
+          as arguments.</p>
         <p>If the number of elements in the arguments are known at
           compile time, the call is better written as
           <c><anno>Fun</anno>(Arg1, Arg2, ... ArgN)</c>.</p>
         <warning>
-          <p>Earlier, <c><anno>Fun</anno></c> could also be given as
+          <p>Earlier, <c><anno>Fun</anno></c> could also be speciifed as
             <c>{Module, Function}</c>, equivalent to
-            <c>apply(Module, Function, Args)</c>. This use is
-            deprecated and will stop working in a future release.</p>
+            <c>apply(Module, Function, Args)</c>. <em>This use is
+            deprecated and will stop working in a future release.</em></p>
         </warning>
       </desc>
     </func>
 
     <func>
       <name name="apply" arity="3"/>
-      <fsummary>Applies a function to an argument list.</fsummary>
+      <fsummary>Apply a function to an argument list.</fsummary>
       <desc>
         <p>Returns the result of applying <c>Function</c> in
           <c><anno>Module</anno></c> to <c><anno>Args</anno></c>.
-	  The applied function must
+          The applied function must
           be exported from <c>Module</c>. The arity of the function is
-          the length of <c>Args</c>.</p>
-        <p>Example:</p>
+          the length of <c>Args</c>. Example:</p>
         <pre>
 > <input>apply(lists, reverse, [[a, b, c]]).</input>
 [c,b,a]
@@ -278,39 +276,43 @@
 "Erlang"</pre>
         <p>If the number of arguments are known at compile time,
           the call is better written as
-          <c><anno>Module</anno>:<anno>Function</anno>(Arg1, Arg2, ..., ArgN)</c>.</p>
-        <p>Failure: <c>error_handler:undefined_function/3</c> is called
+          <c><anno>Module</anno>:<anno>Function</anno>(Arg1, Arg2, ...,
+          ArgN)</c>.</p>
+        <p>Failure: <seealso marker="kernel:error_handler#undefined_function/3">
+          <c>error_handler:undefined_function/3</c></seealso> is called
           if the applied function is not exported. The error handler
           can be redefined (see
-          <seealso marker="#process_flag/2">process_flag/2</seealso>).
+          <seealso marker="#process_flag/2"><c>process_flag/2</c></seealso>).
           If <c>error_handler</c> is undefined, or if the user has
           redefined the default <c>error_handler</c> so the replacement
-          module is undefined, an error with the reason <c>undef</c>
+          module is undefined, an error with reason <c>undef</c>
           is generated.</p>
       </desc>
     </func>
 
     <func>
       <name name="atom_to_binary" arity="2"/>
-      <fsummary>Returns the binary representation of an atom.</fsummary>
+      <fsummary>Return the binary representation of an atom.</fsummary>
       <desc>
         <p>Returns a binary corresponding to the text
           representation of <c><anno>Atom</anno></c>.
           If <c><anno>Encoding</anno></c>
-          is <c>latin1</c>, there is one byte for each character
+          is <c>latin1</c>, one byte exists for each character
           in the text representation. If <c><anno>Encoding</anno></c> is
           <c>utf8</c> or
           <c>unicode</c>, the characters are encoded using UTF-8
           (that is, characters from 128 through 255 are
           encoded in two bytes).</p>
-	<note><p><c>atom_to_binary(<anno>Atom</anno>, latin1)</c> never
-        fails because the text representation of an atom can only
-        contain characters from 0 through 255. In a future release,
-        the text representation
-        of atoms can be allowed to contain any Unicode character and
-        <c>atom_to_binary(<anno>Atom</anno>, latin1)</c> will then fail if the
-        text representation for <c><anno>Atom</anno></c> contains a Unicode
-        character greater than 255.</p></note>
+        <note>
+          <p><c>atom_to_binary(<anno>Atom</anno>, latin1)</c> never
+            fails, as the text representation of an atom can only
+            contain characters from 0 through 255. In a future release,
+            the text representation
+            of atoms can be allowed to contain any Unicode character and
+            <c>atom_to_binary(<anno>Atom</anno>, latin1)</c> then fails if the
+            text representation for <c><anno>Atom</anno></c> contains a Unicode
+            character &gt; 255.</p>
+        </note>
         <p>Example:</p>
         <pre>
 > <input>atom_to_binary('Erlang', latin1).</input>
@@ -332,12 +334,12 @@
 
     <func>
       <name name="binary_part" arity="2"/>
-      <fsummary>Extracts a part of a binary.</fsummary>
+      <fsummary>Extract a part of a binary.</fsummary>
       <desc>
       <p>Extracts the part of the binary described by
         <c><anno>PosLen</anno></c>.</p>
       <p>Negative length can be used to extract bytes at the end
-      of a binary, for example:</p>
+        of a binary, for example:</p>
 <code>
 1> Bin = &lt;&lt;1,2,3,4,5,6,7,8,9,10&gt;&gt;.
 2> binary_part(Bin,{byte_size(Bin), -5}).
@@ -349,43 +351,44 @@
 1> Bin = &lt;&lt;1,2,3&gt;&gt;
 2> binary_part(Bin,{0,2}).
 &lt;&lt;1,2&gt;&gt;</code>
-      <p>For details about the <c><anno>PosLen</anno></c> semantics, see the
-        <seealso marker="stdlib:binary">binary</seealso>
-        manual page in <c>STDLIB</c>.</p>
+      <p>For details about the <c><anno>PosLen</anno></c> semantics, see
+        <seealso marker="stdlib:binary"><c>stdlib:binary</c></seealso>.</p>
       <p>Allowed in guard tests.</p>
       </desc>
     </func>
 
     <func>
       <name name="binary_part" arity="3"/>
-      <fsummary>Extracts a part of a binary.</fsummary>
+      <fsummary>Extract a part of a binary.</fsummary>
       <desc>
       <p>The same as <c>binary_part(<anno>Subject</anno>,
-      {<anno>Start</anno>, <anno>Length</anno>})</c>.</p>
+        {<anno>Start</anno>, <anno>Length</anno>})</c>.</p>
       <p>Allowed in guard tests.</p>
       </desc>
     </func>
 
     <func>
       <name name="binary_to_atom" arity="2"/>
-      <fsummary>Converts from text representation to an atom.</fsummary>
+      <fsummary>Convert from text representation to an atom.</fsummary>
       <desc>
         <p>Returns the atom whose text representation is
-        <c><anno>Binary</anno></c>.
-        If <c><anno>Encoding</anno></c> is <c>latin1</c>, no
-        translation of bytes in the binary is done.
-        If <c><anno>Encoding</anno></c>
-        is <c>utf8</c> or <c>unicode</c>, the binary must contain
-        valid UTF-8 sequences. Only Unicode characters up
-        to 255 are allowed.</p>
-        <note><p><c>binary_to_atom(<anno>Binary</anno>, utf8)</c> fails if
-        the binary contains Unicode characters greater than 255.
-        In a future release, such Unicode characters can be allowed
-        and <c>binary_to_atom(<anno>Binary</anno>, utf8)</c> does then not fail.
-        For more information on Unicode support in atoms, see the
-        <seealso marker="erl_ext_dist#utf8_atoms">note on UTF-8
-        encoded atoms</seealso>
-        in Section "External Term Format" in the User's Guide.</p></note>
+          <c><anno>Binary</anno></c>.
+          If <c><anno>Encoding</anno></c> is <c>latin1</c>, no
+          translation of bytes in the binary is done.
+          If <c><anno>Encoding</anno></c>
+          is <c>utf8</c> or <c>unicode</c>, the binary must contain
+          valid UTF-8 sequences. Only Unicode characters up
+          to 255 are allowed.</p>
+        <note>
+          <p><c>binary_to_atom(<anno>Binary</anno>, utf8)</c> fails if
+            the binary contains Unicode characters &gt; 255.
+            In a future release, such Unicode characters can be allowed and
+            <c>binary_to_atom(<anno>Binary</anno>, utf8)</c> does then not fail.
+            For more information about Unicode support in atoms, see the
+            <seealso marker="erl_ext_dist#utf8_atoms">note on UTF-8
+            encoded atoms</seealso>
+            in section "External Term Format" in the User's Guide.</p>
+        </note>
         <p>Examples:</p>
         <pre>
 > <input>binary_to_atom(&lt;&lt;"Erlang"&gt;&gt;, latin1).</input>
@@ -399,10 +402,10 @@
 
     <func>
       <name name="binary_to_existing_atom" arity="2"/>
-      <fsummary>Converts from text representation to an atom.</fsummary>
+      <fsummary>Convert from text representation to an atom.</fsummary>
       <desc>
         <p>As
-          <seealso marker="#binary_to_atom/2">binary_to_atom/2</seealso>,
+          <seealso marker="#binary_to_atom/2"><c>binary_to_atom/2</c></seealso>,
           but the atom must exist.</p>
         <p>Failure: <c>badarg</c> if the atom does not exist.</p>
       </desc>
@@ -410,7 +413,7 @@
 
     <func>
       <name name="binary_to_float" arity="1"/>
-      <fsummary>Converts from text representation to a float.</fsummary>
+      <fsummary>Convert from text representation to a float.</fsummary>
       <desc>
         <p>Returns the float whose text representation is
           <c><anno>Binary</anno></c>, for example:</p>
@@ -424,7 +427,7 @@
 
     <func>
       <name name="binary_to_integer" arity="1"/>
-      <fsummary>Converts from text representation to an integer.</fsummary>
+      <fsummary>Convert from text representation to an integer.</fsummary>
       <desc>
         <p>Returns an integer whose text representation is
           <c><anno>Binary</anno></c>, for example:</p>
@@ -438,10 +441,11 @@
 
     <func>
       <name name="binary_to_integer" arity="2"/>
-      <fsummary>Converts from text representation to an integer.</fsummary>
+      <fsummary>Convert from text representation to an integer.</fsummary>
       <desc>
         <p>Returns an integer whose text representation in base
-          <c><anno>Base</anno></c> is <c><anno>Binary</anno></c>, for example:</p>
+          <c><anno>Base</anno></c> is <c><anno>Binary</anno></c>, for
+          example:</p>
         <pre>
 > <input>binary_to_integer(&lt;&lt;"3FF"&gt;&gt;, 16).</input>
 1023</pre>
@@ -452,7 +456,7 @@
 
     <func>
       <name name="binary_to_list" arity="1"/>
-      <fsummary>Converts a binary to a list.</fsummary>
+      <fsummary>Convert a binary to a list.</fsummary>
       <desc>
         <p>Returns a list of integers corresponding to the bytes of
           <c><anno>Binary</anno></c>.</p>
@@ -461,75 +465,83 @@
 
     <func>
       <name name="binary_to_list" arity="3"/>
-      <fsummary>Converts part of a binary to a list.</fsummary>
-      <type_desc variable="Start">1..byte_size(<c><anno>Binary</anno></c>)</type_desc>
+      <fsummary>Convert part of a binary to a list.</fsummary>
+      <type_desc variable="Start">1..byte_size(<c><anno>Binary</anno></c>)
+      </type_desc>
       <desc>
         <p>As <c>binary_to_list/1</c>, but returns a list of integers
           corresponding to the bytes from position <c><anno>Start</anno></c> to
           position <c><anno>Stop</anno></c> in <c><anno>Binary</anno></c>.
-	  The positions in the
+          The positions in the
           binary are numbered starting from 1.</p>
-          <note><p>The one-based indexing for binaries used by
-	  this function is deprecated. New code is to use
-          <seealso marker="stdlib:binary#bin_to_list/3">binary:bin_to_list/3</seealso>
-	  in <c>STDLIB</c> instead. All functions in module
-	  <c>binary</c> consistently use zero-based indexing.</p></note>
+        <note>
+          <p><em>The one-based indexing for binaries used by
+            this function is deprecated.</em> New code is to use
+            <seealso marker="stdlib:binary#bin_to_list/3">
+            <c>binary:bin_to_list/3</c></seealso>
+            in <c>STDLIB</c> instead. All functions in module
+            <c>binary</c> consistently use zero-based indexing.</p>
+        </note>
       </desc>
     </func>
 
     <func>
       <name name="binary_to_term" arity="1"/>
-      <fsummary>Decodes an Erlang external term format binary.</fsummary>
+      <fsummary>Decode an Erlang external term format binary.</fsummary>
       <desc>
         <p>Returns an Erlang term that is the result of decoding
           binary object <c><anno>Binary</anno></c>, which must be encoded
           according to the Erlang external term format.</p>
-        <warning><p>When decoding binaries from untrusted sources,
-        consider using <c>binary_to_term/2</c> to prevent Denial
-        of Service attacks.</p></warning>
+        <warning>
+          <p>When decoding binaries from untrusted sources,
+            consider using <c>binary_to_term/2</c> to prevent Denial
+            of Service attacks.</p>
+        </warning>
         <p>See also
-          <seealso marker="#term_to_binary/1">term_to_binary/1</seealso>
-          and
-          <seealso marker="#binary_to_term/2">binary_to_term/2</seealso>.</p>
+          <seealso marker="#term_to_binary/1"><c>term_to_binary/1</c></seealso>
+          and <seealso marker="#binary_to_term/2">
+          <c>binary_to_term/2</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="binary_to_term" arity="2"/>
-      <fsummary>Decodes an Erlang external term format binary.</fsummary>
+      <fsummary>Decode an Erlang external term format binary.</fsummary>
       <desc>
         <p>As <c>binary_to_term/1</c>, but takes options that affect decoding
-           of the binary.</p>
+          of the binary.</p>
+        <p>Option:</p>
         <taglist>
           <tag><c>safe</c></tag>
           <item>
             <p>Use this option when receiving binaries from an untrusted
-               source.</p>
+              source.</p>
             <p>When enabled, it prevents decoding data that can be used to
-               attack the Erlang system. In the event of receiving unsafe
-               data, decoding fails with a <c>badarg</c> error.</p>
+              attack the Erlang system. In the event of receiving unsafe
+              data, decoding fails with a <c>badarg</c> error.</p>
             <p>This prevents creation of new atoms directly,
-               creation of new atoms indirectly (as they are embedded in
-               certain structures, such as process identifiers,
-               refs, and funs), and
-               creation of new external function references.
-               None of those resources are garbage collected, so unchecked
-               creation of them can exhaust available memory.</p>
+              creation of new atoms indirectly (as they are embedded in
+              certain structures, such as process identifiers,
+              refs, and funs), and
+              creation of new external function references.
+              None of those resources are garbage collected, so unchecked
+              creation of them can exhaust available memory.</p>
           </item>
         </taglist>
         <p>Failure: <c>badarg</c> if <c>safe</c> is specified and unsafe
-           data is decoded.</p>
+          data is decoded.</p>
         <p>See also
-           <seealso marker="#term_to_binary/1">term_to_binary/1</seealso>,
-           <seealso marker="#binary_to_term/1">binary_to_term/1</seealso>,
-           and
-           <seealso marker="#list_to_existing_atom/1">list_to_existing_atom/1</seealso>.</p>
+          <seealso marker="#term_to_binary/1"><c>term_to_binary/1</c></seealso>,
+          <seealso marker="#binary_to_term/1">
+          <c>binary_to_term/1</c></seealso>, and
+          <seealso marker="#list_to_existing_atom/1">
+          <c>list_to_existing_atom/1</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="bit_size" arity="1"/>
-      <fsummary>Returns the size of a bitstring.</fsummary>
+      <fsummary>Return the size of a bitstring.</fsummary>
       <desc>
         <p>Returns an integer that is the size in bits of
           <c><anno>Bitstring</anno></c>, for example:</p>
@@ -544,7 +556,7 @@
 
     <func>
       <name name="bitstring_to_list" arity="1"/>
-      <fsummary>Converts a bitstring to a list.</fsummary>
+      <fsummary>Convert a bitstring to a list.</fsummary>
       <desc>
         <p>Returns a list of integers corresponding to the bytes of
           <c><anno>Bitstring</anno></c>. If the number of bits in the binary
@@ -555,14 +567,14 @@
 
     <func>
       <name name="bump_reductions" arity="1"/>
-      <fsummary>Increments the reduction counter.</fsummary>
+      <fsummary>Increment the reduction counter.</fsummary>
       <desc>
         <p>This implementation-dependent function increments
           the reduction counter for the calling process. In the Beam
           emulator, the reduction counter is normally incremented by
           one for each function and BIF call. A context switch is
           forced when the counter reaches the maximum number of
-          reductions for a process (2000 reductions in OTP R12B).</p>
+          reductions for a process (2000 reductions in Erlang/OTP R12B).</p>
         <warning>
           <p>This BIF can be removed in a future version of the Beam
             machine without prior warning. It is unlikely to be
@@ -573,13 +585,12 @@
 
     <func>
       <name name="byte_size" arity="1"/>
-      <fsummary>Returns the size of a bitstring (or binary).</fsummary>
+      <fsummary>Return the size of a bitstring (or binary).</fsummary>
       <desc>
         <p>Returns an integer that is the number of bytes needed to
           contain <c><anno>Bitstring</anno></c>. That is, if the number of bits
           in <c><anno>Bitstring</anno></c> is not divisible by 8, the resulting
-          number of bytes is rounded <em>up</em>.</p>
-        <p>Examples:</p>
+          number of bytes is rounded <em>up</em>. Examples:</p>
         <pre>
 > <input>byte_size(&lt;&lt;433:16,3:3&gt;&gt;).</input>
 3
@@ -591,134 +602,126 @@
 
     <func>
       <name name="cancel_timer" arity="1"/>
-      <fsummary>Cancels a timer.</fsummary>
+      <fsummary>Cancel a timer.</fsummary>
       <desc>
         <p>Cancels a timer. The same as calling
-	<seealso marker="#cancel_timer/2"><c>erlang:cancel_timer(TimerRef,
-	[])</c></seealso>.</p>
+          <seealso marker="#cancel_timer/2">
+          <c>erlang:cancel_timer(TimerRef, [])</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="cancel_timer" arity="2"/>
-      <fsummary>Cancels a timer.</fsummary>
-      <desc>
-        <p>
-	  Cancels a timer that has been created by
-	  <seealso marker="#start_timer/4"><c>erlang:start_timer()</c></seealso>,
-	  or <seealso marker="#send_after/4"><c>erlang:send_after()</c></seealso>.
-	  <c><anno>TimerRef</anno></c> identifies the timer, and
-	  was returned by the BIF that created the timer.
-	</p>
-	<p>Available <c><anno>Option</anno></c>s:</p>
+      <fsummary>Cancel a timer.</fsummary>
+      <desc>
+        <p>Cancels a timer that has been created by
+          <seealso marker="#start_timer/4">
+          <c>erlang:start_timer</c></seealso> or
+          <seealso marker="#send_after/4"><c>erlang:send_after</c></seealso>.
+          <c><anno>TimerRef</anno></c> identifies the timer, and
+          was returned by the BIF that created the timer.</p>
+        <p><c><anno>Option</anno></c>s:</p>
         <taglist>
           <tag><c>{async, Async}</c></tag>
           <item>
-	    <p>
-	      Asynchronous request for cancellation. <c>Async</c>
-	      defaults to <c>false</c> which will cause the
-	      cancellation to be performed synchronously. When
-	      <c>Async</c> is set to <c>true</c>, the cancel
-	      operation is performed asynchronously. That is,
-	      <c>erlang:cancel_timer()</c> will send an asynchronous
-	      request for cancellation to the timer service that
-	      manages the timer, and then return <c>ok</c>.
-	  </p>
-	  </item>
+            <p>Asynchronous request for cancellation. <c>Async</c>
+              defaults to <c>false</c>, which causes the
+              cancellation to be performed synchronously. When
+              <c>Async</c> is set to <c>true</c>, the cancel
+              operation is performed asynchronously. That is,
+              <c>cancel_timer()</c> sends an asynchronous
+              request for cancellation to the timer service that
+              manages the timer, and then returns <c>ok</c>.</p>
+          </item>
           <tag><c>{info, Info}</c></tag>
           <item>
-	    <p>
-	      Request information about the <c><anno>Result</anno></c>
-	      of the cancellation. <c>Info</c> defaults to <c>true</c>
-	      which means the <c><anno>Result</anno></c> is
-	      given. When <c>Info</c> is set to <c>false</c>, no
-	      information about the result of the cancellation
-	      is given. When the operation is performed</p>
-              <taglist>
-		<tag>synchronously</tag>
-		<item>
-		  <p>
-		    If <c>Info</c> is <c>true</c>, the <c>Result</c> is
-		    returned by <c>erlang:cancel_timer()</c>; otherwise,
-		    <c>ok</c> is returned.
-		  </p>
-		</item>
-		<tag>asynchronously</tag>
-		<item>
-		  <p>
-		    If <c>Info</c> is <c>true</c>, a message on the form
-		    <c>{cancel_timer, <anno>TimerRef</anno>,
-		    <anno>Result</anno>}</c> is sent to the
-		    caller of <c>erlang:cancel_timer()</c> when the
-		    cancellation operation has been performed; otherwise,
-		    no message is sent.
-		  </p>
-		</item>
-            </taglist>
-	  </item>
-        </taglist>
-	<p>
-	  More <c><anno>Option</anno></c>s may be added in the future.
-	</p>
-	<p>If <c><anno>Result</anno></c> is an integer, it represents
-	  the time in milli-seconds left until the canceled timer would
-	  have expired.</p>
-	<p>
-	  If <c><anno>Result</anno></c> is <c>false</c>, a
-	  timer corresponding to <c><anno>TimerRef</anno></c> could not
-	  be found. This can be either because the timer had expired,
-	  already had been canceled, or because <c><anno>TimerRef</anno></c>
-	  never corresponded to a timer. Even if the timer had expired,
-	  it does not tell you whether or not the timeout message has
-	  arrived at its destination yet.
-	</p>
-	<note>
-	  <p>
-	    The timer service that manages the timer may be co-located
-	    with another scheduler than the scheduler that the calling
-	    process is executing on. If this is the case, communication
-	    with the timer service takes much longer time than if it
-	    is located locally. If the calling process is in critical
-	    path, and can do other things while waiting for the result
-	    of this operation, or is not interested in the result of
-	    the operation, you want to use option <c>{async, true}</c>.
-	    If using option <c>{async, false}</c>, the calling
-	    process blocks until the operation has been performed.
-	  </p>
-	</note>
-        <p>See also 
+            <p>Requests information about the <c><anno>Result</anno></c>
+              of the cancellation. <c>Info</c> defaults to <c>true</c>,
+              which means the <c><anno>Result</anno></c> is
+              given. When <c>Info</c> is set to <c>false</c>, no
+              information about the result of the cancellation
+              is given.</p>
+            <list type="bulleted">
+              <item>
+                <p>When the operation is performed synchronously:
+                  if <c>Info</c> is <c>true</c>, the <c>Result</c> is
+                  returned by <c>erlang:cancel_timer()</c>. otherwise
+                  <c>ok</c> is returned.</p>
+              </item>
+              <item>
+                <p>When the operation is performed asynchronously:
+                  if <c>Info</c> is <c>true</c>, a message on the form
+                  <c>{cancel_timer, <anno>TimerRef</anno>,
+                  <anno>Result</anno>}</c> is sent to the
+                  caller of <c>erlang:cancel_timer()</c> when the
+                  cancellation operation has been performed, otherwise
+                  no message is sent.</p>
+              </item>
+            </list>
+           </item>
+         </taglist>
+        <p>More <c><anno>Option</anno></c>s may be added in the future.</p>
+        <p>If <c><anno>Result</anno></c> is an integer, it represents
+          the time in milliseconds left until the canceled timer would
+          have expired.</p>
+        <p>If <c><anno>Result</anno></c> is <c>false</c>, a
+          timer corresponding to <c><anno>TimerRef</anno></c> could not
+          be found. This can be either because the timer had expired,
+          already had been canceled, or because <c><anno>TimerRef</anno></c>
+          never corresponded to a timer. Even if the timer had expired,
+          it does not tell you if the time-out message has
+          arrived at its destination yet.</p>
+        <note>
+          <p>The timer service that manages the timer can be co-located
+            with another scheduler than the scheduler that the calling
+            process is executing on. If so, communication
+            with the timer service takes much longer time than if it
+            is located locally. If the calling process is in critical
+            path, and can do other things while waiting for the result
+            of this operation, or is not interested in the result of
+            the operation, you want to use option <c>{async, true}</c>.
+            If using option <c>{async, false}</c>, the calling
+            process blocks until the operation has been performed.</p>
+        </note>
+        <p>See also
           <seealso marker="#send_after/4"><c>erlang:send_after/4</c></seealso>,
-          <seealso marker="#start_timer/4"><c>erlang:start_timer/4</c></seealso>,
-          and
-          <seealso marker="#read_timer/2"><c>erlang:read_timer/2</c></seealso>.</p>
+          <seealso marker="#start_timer/4">
+          <c>erlang:start_timer/4</c></seealso>, and
+          <seealso marker="#read_timer/2">
+          <c>erlang:read_timer/2</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="check_old_code" arity="1"/>
-      <fsummary>Checks if a module has old code.</fsummary>
+      <fsummary>Check if a module has old code.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Module</anno></c> has old code,
-	  otherwise <c>false</c>.</p>
-        <p>See also <seealso marker="kernel:code">code(3)</seealso>.</p>
+          otherwise <c>false</c>.</p>
+        <p>See also <seealso marker="kernel:code">
+          <c>kernel:code(3)</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="check_process_code" arity="2"/>
-      <fsummary>Checks if a process executes old code for a module.</fsummary>
+      <fsummary>Check if a process executes old code for a module.</fsummary>
       <desc>
         <p>The same as
-        <seealso marker="#check_process_code/3"><c>erlang:check_process_code(<anno>Pid</anno>, <anno>Module</anno>, [])</c></seealso>.</p>
+          <seealso marker="#check_process_code/3">
+          <c>check_process_code(<anno>Pid</anno>, <anno>Module</anno>, [])</c>
+          </seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="check_process_code" arity="3"/>
-      <fsummary>Checks if a process executes old code for a module.</fsummary>
+      <fsummary>Check if a process executes old code for a module.</fsummary>
       <desc>
-        <p>Checks if the node local process identified by <c><anno>Pid</anno></c>
-        executes old code for <c><anno>Module</anno></c>.</p>
-        <p>The available <c><anno>Option</anno></c>s are as follows:</p>
+        <p>Checks if the node local process identified by
+          <c><anno>Pid</anno></c>
+          executes old code for <c><anno>Module</anno></c>.</p>
+        <p><c><anno>Option</anno></c>s:</p>
         <taglist>
           <tag><c>{allow_gc, boolean()}</c></tag>
           <item>
@@ -726,30 +729,30 @@
             the operation. If <c>{allow_gc, false}</c> is passed, and
             a garbage collection is needed to determine the
             result of the operation, the operation is aborted (see
-            information on <c><anno>CheckResult</anno></c> in the following).
+            information on <c><anno>CheckResult</anno></c> below).
             The default is to allow garbage collection, that is,
             <c>{allow_gc, true}</c>.</p>
-	  </item>
+          </item>
           <tag><c>{async, RequestId}</c></tag>
           <item>
             <p>The function <c>check_process_code/3</c> returns
             the value <c>async</c> immediately after the request
             has been sent. When the request has been processed, the
             process that called this function is passed a
-            message on the form
-            <c>{check_process_code, <anno>RequestId</anno>, <anno>CheckResult</anno>}</c>.</p>
-	  </item>
+            message on the form <c>{check_process_code, <anno>RequestId</anno>,
+            <anno>CheckResult</anno>}</c>.</p>
+          </item>
         </taglist>
         <p>If <c><anno>Pid</anno></c> equals <c>self()</c>, and
-        no <c>async</c> option has been passed, the operation
-        is performed at once. Otherwise a request for
-        the operation is sent to the process identified by
-        <c><anno>Pid</anno></c>, and is handled when
-        appropriate. If no <c>async</c> option has been passed,
-        the caller blocks until <c><anno>CheckResult</anno></c>
-        is available and can be returned.</p>
+          no <c>async</c> option has been passed, the operation
+          is performed at once. Otherwise a request for
+          the operation is sent to the process identified by
+          <c><anno>Pid</anno></c>, and is handled when
+          appropriate. If no <c>async</c> option has been passed,
+          the caller blocks until <c><anno>CheckResult</anno></c>
+          is available and can be returned.</p>
         <p><c><anno>CheckResult</anno></c> informs about the result of
-        the request as follows:</p>
+          the request as follows:</p>
         <taglist>
           <tag><c>true</c></tag>
           <item>
@@ -759,54 +762,59 @@
             code for this module, or the process has references
             to old code for this module, or the process contains
             funs that references old code for this module.</p>
-	  </item>
+          </item>
           <tag><c>false</c></tag>
           <item>
             <p>The process identified by <c><anno>Pid</anno></c> does
             not execute old code for <c><anno>Module</anno></c>.</p>
-	  </item>
+          </item>
           <tag><c>aborted</c></tag>
           <item>
             <p>The operation was aborted, as the process needed to
             be garbage collected to determine the operation result,
             and the operation was requested
-            by passing option <c>{allow_gc, false}</c>.</p></item>
+            by passing option <c>{allow_gc, false}</c>.</p>
+          </item>
         </taglist>
-        <p>See also <seealso marker="kernel:code">code(3)</seealso>.</p>
+        <p>See also <seealso marker="kernel:code">
+          <c>kernel:code(3)</c></seealso>.</p>
         <p>Failures:</p>
         <taglist>
           <tag><c>badarg</c></tag>
-          <item>If <c><anno>Pid</anno></c> is not a node local process identifier.
-	  </item>
+          <item>If <c><anno>Pid</anno></c> is not a node local process
+            identifier.
+          </item>
           <tag><c>badarg</c></tag>
           <item>If <c><anno>Module</anno></c> is not an atom.
-	  </item>
+          </item>
           <tag><c>badarg</c></tag>
           <item>If <c><anno>OptionList</anno></c> is an invalid list of options.
-	  </item>
+          </item>
         </taglist>
       </desc>
     </func>
 
     <func>
       <name name="convert_time_unit" arity="3"/>
-      <fsummary>Converts time unit of a time value.</fsummary>
+      <fsummary>Convert time unit of a time value.</fsummary>
       <desc>
-	<p>Converts the <c><anno>Time</anno></c> value of time unit
-	<c><anno>FromUnit</anno></c> to the corresponding
-	<c><anno>ConvertedTime</anno></c> value of time unit
-	<c><anno>ToUnit</anno></c>. The result is rounded
-	using the floor function.</p>
-
-	<warning><p>You may lose accuracy and precision when converting
-	between	time units. In order to minimize such loss, collect all
-	data at <c>native</c> time unit and do the conversion on the end
-	result.</p></warning>
+        <p>Converts the <c><anno>Time</anno></c> value of time unit
+          <c><anno>FromUnit</anno></c> to the corresponding
+          <c><anno>ConvertedTime</anno></c> value of time unit
+          <c><anno>ToUnit</anno></c>. The result is rounded
+          using the floor function.</p>
+        <warning>
+          <p>You can lose accuracy and precision when converting
+            between time units. To minimize such loss, collect all
+            data at <c>native</c> time unit and do the conversion on the end
+            result.</p>
+        </warning>
       </desc>
     </func>
+
     <func>
       <name name="crc32" arity="1"/>
-      <fsummary>Computes crc32 (IEEE 802.3) checksum.</fsummary>
+      <fsummary>Compute crc32 (IEEE 802.3) checksum.</fsummary>
       <desc>
         <p>Computes and returns the crc32 (IEEE 802.3 style) checksum
           for <c><anno>Data</anno></c>.</p>
@@ -815,37 +823,37 @@
 
     <func>
       <name name="crc32" arity="2"/>
-      <fsummary>Computes crc32 (IEEE 802.3) checksum.</fsummary>
+      <fsummary>Compute crc32 (IEEE 802.3) checksum.</fsummary>
       <desc>
         <p>Continues computing the crc32 checksum by combining
-        the previous checksum, <c><anno>OldCrc</anno></c>, with the checksum of
-        <c><anno>Data</anno></c>.</p>
+          the previous checksum, <c><anno>OldCrc</anno></c>, with the checksum
+          of <c><anno>Data</anno></c>.</p>
         <p>The following code:</p>
         <code>
-        X = erlang:crc32(Data1),
-        Y = erlang:crc32(X,Data2).</code>
+X = erlang:crc32(Data1),
+Y = erlang:crc32(X,Data2).</code>
         <p>assigns the same value to <c>Y</c> as this:</p>
         <code>
-        Y = erlang:crc32([Data1,Data2]).</code>
+Y = erlang:crc32([Data1,Data2]).</code>
       </desc>
     </func>
 
     <func>
       <name name="crc32_combine" arity="3"/>
-      <fsummary>Combines two crc32 (IEEE 802.3) checksums.</fsummary>
+      <fsummary>Combine two crc32 (IEEE 802.3) checksums.</fsummary>
       <desc>
         <p>Combines two previously computed crc32 checksums.
-        This computation requires the size of the data object for
-        the second checksum to be known.</p>
+          This computation requires the size of the data object for
+          the second checksum to be known.</p>
         <p>The following code:</p>
         <code>
-        Y = erlang:crc32(Data1),
-        Z = erlang:crc32(Y,Data2).</code>
+Y = erlang:crc32(Data1),
+Z = erlang:crc32(Y,Data2).</code>
         <p>assigns the same value to <c>Z</c> as this:</p>
 	<code>
-        X = erlang:crc32(Data1),
-        Y = erlang:crc32(Data2),
-        Z = erlang:crc32_combine(X,Y,iolist_size(Data2)).</code>
+X = erlang:crc32(Data1),
+Y = erlang:crc32(Data2),
+Z = erlang:crc32_combine(X,Y,iolist_size(Data2)).</code>
       </desc>
     </func>
 
@@ -855,8 +863,7 @@
       <desc>
         <p>Returns the current date as <c>{Year, Month, Day}</c>.</p>
         <p>The time zone and Daylight Saving Time correction depend on
-          the underlying OS.</p>
-        <p>Example:</p>
+          the underlying OS. Example:</p>
         <pre>
 > <input>date().</input>
 {1995,2,19}</pre>
@@ -865,28 +872,29 @@
 
     <func>
       <name name="decode_packet" arity="3"/>
-      <fsummary>Extracts a protocol packet from a binary.</fsummary>
+      <fsummary>Extract a protocol packet from a binary.</fsummary>
       <desc>
         <p>Decodes the binary <c><anno>Bin</anno></c> according to the packet
-        protocol specified by <c><anno>Type</anno></c>. Similar to the packet
-        handling done by sockets with option {packet,<anno>Type</anno>}.</p>
+          protocol specified by <c><anno>Type</anno></c>. Similar to the packet
+          handling done by sockets with option
+          <c>{packet,<anno>Type</anno>}.</c></p>
         <p>If an entire packet is contained in <c><anno>Bin</anno></c>, it is
-        returned together with the remainder of the binary as
-        <c>{ok,<anno>Packet</anno>,<anno>Rest</anno>}</c>.</p>
+          returned together with the remainder of the binary as
+          <c>{ok,<anno>Packet</anno>,<anno>Rest</anno>}</c>.</p>
         <p>If <c><anno>Bin</anno></c> does not contain the entire packet,
-        <c>{more,<anno>Length</anno>}</c> is returned.
-        <c><anno>Length</anno></c> is either the
-        expected <em>total size</em> of the packet, or <c>undefined</c>
-        if the expected packet size is unknown. <c>decode_packet</c>
-        can then be called again with more data added.</p>
+          <c>{more,<anno>Length</anno>}</c> is returned.
+          <c><anno>Length</anno></c> is either the
+          expected <em>total size</em> of the packet, or <c>undefined</c>
+          if the expected packet size is unknown. <c>decode_packet</c>
+          can then be called again with more data added.</p>
         <p>If the packet does not conform to the protocol format,
-        <c>{error,<anno>Reason</anno>}</c> is returned.</p>
-        <p>The following <c>Type</c>s are valid:</p>
+          <c>{error,<anno>Reason</anno>}</c> is returned.</p>
+        <p><c>Type</c>s:</p>
         <taglist>
           <tag><c>raw | 0</c></tag>
           <item>
             <p>No packet handling is done. The entire binary is
-            returned unless it is empty.</p>
+              returned unless it is empty.</p>
           </item>
           <tag><c>1 | 2 | 4</c></tag>
           <item>
@@ -898,10 +906,10 @@
           </item>
           <tag><c>line</c></tag>
           <item>
-            <p>A packet is a line terminated by a delimiter byte,
-            default is the latin1 newline character. The delimiter
-            byte is included in the returned packet unless the line
-            was truncated according to option <c>line_length</c>.</p>
+            <p>A packet is a line-terminated by a delimiter byte,
+              default is the latin-1 newline character. The delimiter
+              byte is included in the returned packet unless the line
+              was truncated according to option <c>line_length</c>.</p>
           </item>
           <tag><c>asn1 | cdr | sunrm | fcgi | tpkt</c></tag>
           <item>
@@ -918,53 +926,51 @@
           <tag><c>http | httph | http_bin | httph_bin</c></tag>
           <item>
             <p>The Hypertext Transfer Protocol. The packets
-               are returned with the format according to
-               <c><anno>HttpPacket</anno></c> described earlier.
-               A packet is either a
-               request, a response, a header, or an end of header
-               mark. Invalid lines are returned as
-               <c><anno>HttpError</anno></c>.</p>
+              are returned with the format according to
+              <c><anno>HttpPacket</anno></c> described earlier.
+              A packet is either a
+              request, a response, a header, or an end of header
+              mark. Invalid lines are returned as
+              <c><anno>HttpError</anno></c>.</p>
             <p>Recognized request methods and header fields are returned
-               as atoms. Others are returned as strings. Strings of
-               unrecognized header fields are formatted with only
-               capital letters first and after hyphen characters, for
-               example, <c>"Sec-Websocket-Key"</c>.</p>
+              as atoms. Others are returned as strings. Strings of
+              unrecognized header fields are formatted with only
+              capital letters first and after hyphen characters, for
+              example, <c>"Sec-Websocket-Key"</c>.</p>
             <p>The protocol type <c>http</c> is only to be used for
-               the first line when an <c><anno>HttpRequest</anno></c> or an
-               <c><anno>HttpResponse</anno></c> is expected.
-               The following calls are to use <c>httph</c> to get
-               <c><anno>HttpHeader</anno></c>s until
-               <c>http_eoh</c> is returned, which marks the end of the
-               headers and the beginning of any following message body.</p> 
+              the first line when an <c><anno>HttpRequest</anno></c> or an
+              <c><anno>HttpResponse</anno></c> is expected.
+              The following calls are to use <c>httph</c> to get
+              <c><anno>HttpHeader</anno></c>s until
+              <c>http_eoh</c> is returned, which marks the end of the
+              headers and the beginning of any following message body.</p> 
             <p>The variants <c>http_bin</c> and <c>httph_bin</c> return
-               strings (<c>HttpString</c>) as binaries instead of lists.</p>
+              strings (<c>HttpString</c>) as binaries instead of lists.</p>
           </item>
         </taglist>
-        <p>The following options are available:</p>
-            <taglist>
-              <tag><c>{packet_size, integer() >= 0}</c></tag>
-              <item>
-            <p>Sets the maximum allowed size of the packet body.
-                If the packet header indicates that the length of the
-                packet is longer than the maximum allowed length, the
-                packet is considered invalid. Default is 0, which means
-                no size limit.</p>
-              </item>
-              <tag><c>{line_length, integer() >= 0}</c></tag>
-              <item>
+        <p>Options:</p>
+        <taglist>
+          <tag><c>{packet_size, integer() >= 0}</c></tag>
+          <item><p>Sets the maximum allowed size of the packet body.
+            If the packet header indicates that the length of the
+            packet is longer than the maximum allowed length, the
+            packet is considered invalid. Defaults to 0, which means
+            no size limit.</p>
+          </item>
+          <tag><c>{line_length, integer() >= 0}</c></tag>
+          <item>
             <p>For packet type <c>line</c>, lines longer than
               the indicated length are truncated.</p>
-              <p>Option <c>line_length</c> also applies to <c>http*</c>
-                packet types as an alias for option <c>packet_size</c>
-                if <c>packet_size</c> itself is not set. This use is
-                only intended for backward compatibility.</p>
-              </item>
-              <tag><c>{line_delimiter, 0 =&lt; byte() =&lt; 255}</c></tag>
-              <item>
-            <p>For packet type <c>line</c>, sets the delimiting byte.
-                Default is the latin1 character <c>$\n</c>.</p>
-              </item>
-            </taglist>
+            <p>Option <c>line_length</c> also applies to <c>http*</c>
+              packet types as an alias for option <c>packet_size</c>
+              if <c>packet_size</c> itself is not set. This use is
+              only intended for backward compatibility.</p>
+          </item>
+          <tag><c>{line_delimiter, 0 =&lt; byte() =&lt; 255}</c></tag>
+          <item><p>For packet type <c>line</c>, sets the delimiting byte.
+            Default is the latin-1 character <c>$\n</c>.</p>
+          </item>
+        </taglist>
         <p>Examples:</p>
         <pre>
 > <input>erlang:decode_packet(1,&lt;&lt;3,"abcd"&gt;&gt;,[]).</input>
@@ -976,7 +982,7 @@
 
     <func>
       <name name="delete_element" arity="2"/>
-      <fsummary>Deletes element at index in a tuple.</fsummary>
+      <fsummary>Delete element at index in a tuple.</fsummary>
       <type_desc variable="Index">1..tuple_size(<anno>Tuple1</anno>)</type_desc>
       <desc>
         <p>Returns a new tuple with element at <c><anno>Index</anno></c>
@@ -989,16 +995,16 @@
 
     <func>
       <name name="delete_module" arity="1"/>
-      <fsummary>Makes the current code for a module old.</fsummary>
+      <fsummary>Make the current code for a module old.</fsummary>
       <desc>
-        <p>Makes the current code for <c><anno>Module</anno></c> become old code,
-          and deletes all references for this module from the export table.
+        <p>Makes the current code for <c><anno>Module</anno></c> become old
+          code and deletes all references for this module from the export table.
           Returns <c>undefined</c> if the module does not exist,
           otherwise <c>true</c>.</p>
         <warning>
           <p>This BIF is intended for the code server (see
-            <seealso marker="kernel:code">code(3)</seealso>) and is not
-            to be used elsewhere.</p>
+            <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>)
+            and is not to be used elsewhere.</p>
         </warning>
         <p>Failure: <c>badarg</c> if there already is an old version of
           <c>Module</c>.</p>
@@ -1007,54 +1013,56 @@
 
     <func>
       <name name="demonitor" arity="1"/>
-      <fsummary>Stops monitoring.</fsummary>
+      <fsummary>Stop monitoring.</fsummary>
       <desc>
         <p>If <c><anno>MonitorRef</anno></c> is a reference that the
           calling process obtained by calling
-          <seealso marker="#monitor/2">monitor/2</seealso>,
+          <seealso marker="#monitor/2"><c>monitor/2</c></seealso>,
           this monitoring is turned off. If the monitoring is already
           turned off, nothing happens.</p>
         <p>Once <c>demonitor(<anno>MonitorRef</anno>)</c> has returned, it is
           guaranteed that no <c>{'DOWN',
           <anno>MonitorRef</anno>, _, _, _}</c> message,
           because of the monitor, will be placed in the caller message queue
-          in the future. A <c>{'DOWN',
+          in the future. However, a <c>{'DOWN',
           <anno>MonitorRef</anno>, _, _, _}</c> message
           can have been placed in the caller message queue before
-          the call, though. It is therefore usually advisable
+          the call. It is therefore usually advisable
           to remove such a <c>'DOWN'</c> message from the message queue
           after monitoring has been stopped.
-          <seealso marker="#demonitor/2"><c>demonitor(<anno>MonitorRef</anno>, [flush])</c></seealso>
-          can be used instead of
-          <c>demonitor(<anno>MonitorRef</anno>)</c> if this cleanup is wanted.</p>
+          <seealso marker="#demonitor/2">
+          <c>demonitor(<anno>MonitorRef</anno>, [flush])</c></seealso>
+          can be used instead of <c>demonitor(<anno>MonitorRef</anno>)</c>
+          if this cleanup is wanted.</p>
         <note>
-          <p>Prior to OTP release R11B (ERTS version 5.5) <c>demonitor/1</c>
-            behaved completely asynchronously, i.e., the monitor was active
+          <p>Before Erlang/OTP R11B (ERTS 5.5) <c>demonitor/1</c>
+            behaved completely asynchronously, that is, the monitor was active
             until the "demonitor signal" reached the monitored entity. This
             had one undesirable effect. You could never know when
             you were guaranteed <em>not</em> to receive a <c>DOWN</c> message
-            due to the monitor.</p>
-          <p>Current behavior can be viewed as two combined operations:
+            because of the monitor.</p>
+          <p>The current behavior can be viewed as two combined operations:
             asynchronously send a "demonitor signal" to the monitored entity
-            and ignore any future results of the monitor. </p>
+            and ignore any future results of the monitor.</p>
         </note>
         <p>Failure: It is an error if <c><anno>MonitorRef</anno></c> refers to a
           monitoring started by another process. Not all such cases are
           cheap to check. If checking is cheap, the call fails with
-          <c>badarg</c> for example, if <c><anno>MonitorRef</anno></c> is a
+          <c>badarg</c>, for example if <c><anno>MonitorRef</anno></c> is a
           remote reference.</p>
       </desc>
     </func>
 
     <func>
       <name name="demonitor" arity="2"/>
-      <fsummary>Stops monitoring.</fsummary>
+      <fsummary>Stop monitoring.</fsummary>
       <desc>
         <p>The returned value is <c>true</c> unless <c>info</c> is part
           of <c><anno>OptionList</anno></c>.</p>
         <p><c>demonitor(<anno>MonitorRef</anno>, [])</c> is equivalent to
-          <seealso marker="#demonitor/1"><c>demonitor(<anno>MonitorRef</anno>)</c></seealso>.</p>
-        <p>The available <c><anno>Option</anno></c>s are as follows:</p>
+          <seealso marker="#demonitor/1">
+          <c>demonitor(<anno>MonitorRef</anno>)</c></seealso>.</p>
+        <p><c><anno>Option</anno></c>s:</p>
         <taglist>
           <tag><c>flush</c></tag>
           <item>
@@ -1065,28 +1073,28 @@
             <p>Calling <c>demonitor(<anno>MonitorRef</anno>, [flush])</c>
               is equivalent to the following, but more efficient:</p>
             <code type="none">
-    demonitor(MonitorRef),
-    receive
-        {_, MonitorRef, _, _, _} ->
-            true
-    after 0 ->
-            true
-    end</code>
+demonitor(MonitorRef),
+receive
+    {_, MonitorRef, _, _, _} ->
+        true
+after 0 ->
+        true
+end</code>
           </item>
           <tag><c>info</c></tag>
           <item>
             <p>The returned value is one of the following:</p>
             <taglist>
               <tag><c>true</c></tag>
-              <item>The monitor was found and removed. In this case,
+              <item><p>The monitor was found and removed. In this case,
                 no <c>'DOWN'</c> message corresponding to this
-                monitor has been delivered and will not be delivered.
+                monitor has been delivered and will not be delivered.</p>
               </item>
               <tag><c>false</c></tag>
-              <item>The monitor was not found and could not be removed.
+              <item><p>The monitor was not found and could not be removed.
                 This probably because someone already has placed a
                 <c>'DOWN'</c> message corresponding to this monitor
-                in the caller message queue.
+                in the caller message queue.</p>
               </item>
             </taglist>
             <p>If option <c>info</c> is combined with option <c>flush</c>,
@@ -1101,21 +1109,21 @@
         <taglist>
           <tag><c>badarg</c></tag>
           <item>If <c><anno>OptionList</anno></c> is not a list.
-	  </item>
+          </item>
           <tag><c>badarg</c></tag>
           <item>If <c><anno>Option</anno></c> is an invalid option.
-	  </item>
+          </item>
           <tag><c>badarg</c></tag>
           <item>The same failure as for
-            <seealso marker="#demonitor/1">demonitor/1</seealso>.
-	  </item>
+            <seealso marker="#demonitor/1"><c>demonitor/1</c></seealso>.
+          </item>
         </taglist>
       </desc>
     </func>
 
     <func>
       <name name="disconnect_node" arity="1"/>
-      <fsummary>Forces the disconnection of a node.</fsummary>
+      <fsummary>Force the disconnection of a node.</fsummary>
       <desc>
         <p>Forces the disconnection of a node. This appears to
           the node <c><anno>Node</anno></c> as if the local node has crashed.
@@ -1129,7 +1137,7 @@
 
     <func>
       <name name="display" arity="1"/>
-      <fsummary>Prints a term on standard output.</fsummary>
+      <fsummary>Print a term on standard output.</fsummary>
       <desc>
         <p>Prints a text representation of <c><anno>Term</anno></c> on the
           standard output.</p>
@@ -1141,7 +1149,7 @@
 
     <func>
       <name name="element" arity="2"/>
-      <fsummary>Returns the Nth element of a tuple.</fsummary>
+      <fsummary>Return the Nth element of a tuple.</fsummary>
       <type_desc variable="N">1..tuple_size(<anno>Tuple</anno>)</type_desc>
       <desc>
         <p>Returns the <c><anno>N</anno></c>th element (numbering from 1) of
@@ -1155,7 +1163,7 @@ b</pre>
 
     <func>
       <name name="erase" arity="0"/>
-      <fsummary>Returns and deletes the process dictionary.</fsummary>
+      <fsummary>Return and delete the process dictionary.</fsummary>
       <desc>
         <p>Returns the process dictionary and deletes it, for
           example:</p>
@@ -1169,13 +1177,13 @@ b</pre>
 
     <func>
       <name name="erase" arity="1"/>
-      <fsummary>Returns and deletes a value from the process dictionary.</fsummary>
+      <fsummary>Return and delete a value from the process dictionary.
+      </fsummary>
       <desc>
         <p>Returns the value <c><anno>Val</anno></c> associated with
           <c><anno>Key</anno></c> and deletes it from the process dictionary.
           Returns <c>undefined</c> if no value is associated with
-          <c><anno>Key</anno></c>.</p>
-        <p>Example:</p>
+          <c><anno>Key</anno></c>. Example:</p>
         <pre>
 > <input>put(key1, {merry, lambs, are, playing}),</input>
 <input>X = erase(key1),</input>
@@ -1186,16 +1194,15 @@ b</pre>
 
     <func>
       <name name="error" arity="1"/>
-      <fsummary>Stops execution with a given reason.</fsummary>
+      <fsummary>Stop execution with a specified reason.</fsummary>
       <desc>
         <p>Stops the execution of the calling process with the reason
           <c><anno>Reason</anno></c>, where <c><anno>Reason</anno></c>
           is any term. The exit reason is
           <c>{<anno>Reason</anno>, Where}</c>, where <c>Where</c>
           is a list of the functions most recently called (the current
-          function first). Since evaluating this function causes
-          the process to terminate, it has no return value.</p>
-        <p>Example:</p>
+          function first). As evaluating this function causes
+          the process to terminate, it has no return value. Example:</p>
         <pre>
 > <input>catch error(foobar).</input>
 {'EXIT',{foobar,[{erl_eval,do_apply,5},
@@ -1208,7 +1215,7 @@ b</pre>
 
     <func>
       <name name="error" arity="2"/>
-      <fsummary>Stops execution with a given reason.</fsummary>
+      <fsummary>Stop execution with a specified reason.</fsummary>
       <desc>
         <p>Stops the execution of the calling process with the reason
           <c><anno>Reason</anno></c>, where <c><anno>Reason</anno></c>
@@ -1218,21 +1225,20 @@ b</pre>
           function first). <c><anno>Args</anno></c> is expected to be the
           list of arguments for the current function; in Beam it is used
           to provide the arguments for the current function in
-          the term <c>Where</c>. Since evaluating this function causes
+          the term <c>Where</c>. As evaluating this function causes
           the process to terminate, it has no return value.</p>
       </desc>
     </func>
 
     <func>
       <name name="exit" arity="1"/>
-      <fsummary>Stops execution with a given reason.</fsummary>
+      <fsummary>Stop execution with a specified reason.</fsummary>
       <desc>
         <p>Stops the execution of the calling process with exit reason
           <c><anno>Reason</anno></c>, where <c><anno>Reason</anno></c>
-          is any term. Since
+          is any term. As
           evaluating this function causes the process to terminate, it
-          has no return value.</p>
-        <p>Example:</p>
+          has no return value. Example:</p>
         <pre>
 > <input>exit(foobar).</input>
 ** exception exit: foobar
@@ -1243,44 +1249,44 @@ b</pre>
 
     <func>
       <name name="exit" arity="2"/>
-      <fsummary>Sends an exit signal to a process or a port.</fsummary>
+      <fsummary>Send an exit signal to a process or a port.</fsummary>
       <desc>
         <p>Sends an exit signal with exit reason <c><anno>Reason</anno></c> to
           the process or port identified by <c><anno>Pid</anno></c>.</p>
         <p>The following behavior applies if <c><anno>Reason</anno></c>
           is any term, except <c>normal</c> or <c>kill</c>:</p>
-          <list type="bulleted">
-            <item>
-              If <c><anno>Pid</anno></c> is not trapping exits,
-              <c><anno>Pid</anno></c>
-              itself exits with exit reason <c><anno>Reason</anno></c>.
-            </item>
-            <item>If <c><anno>Pid</anno></c> is trapping exits, the exit
-              signal is transformed into a message
-              <c>{'EXIT', From, <anno>Reason</anno>}</c>
-              and delivered to the message queue of <c><anno>Pid</anno></c>.
-            </item>
-            <item><c>From</c> is the process identifier of the process
-              that sent the exit signal. See also
-              <seealso marker="#process_flag/2">process_flag/2</seealso>.
-            </item>
-          </list>
-          <p>If <c><anno>Reason</anno></c> is the atom <c>normal</c>,
+        <list type="bulleted">
+          <item><p>If <c><anno>Pid</anno></c> is not trapping exits,
             <c><anno>Pid</anno></c>
-            does not exit. If it is trapping exits, the exit signal is
-            transformed into a message <c>{'EXIT', From, normal}</c>
-            and delivered to its message queue.</p>
-          <p>If <c><anno>Reason</anno></c> is the atom <c>kill</c>,
-            that is, if <c>exit(<anno>Pid</anno>, kill)</c> is called,
-            an untrappable exit signal is sent to <c><anno>Pid</anno></c>,
-            which unconditionally exits with exit reason <c>killed</c>.
-          </p>
+            itself exits with exit reason <c><anno>Reason</anno></c>.</p>
+          </item>
+          <item><p>If <c><anno>Pid</anno></c> is trapping exits, the exit
+            signal is transformed into a message
+            <c>{'EXIT', From, <anno>Reason</anno>}</c>
+            and delivered to the message queue of <c><anno>Pid</anno></c>.</p>
+          </item>
+          <item><p><c>From</c> is the process identifier of the process
+            that sent the exit signal. See also
+            <seealso marker="#process_flag/2">
+            <c>process_flag/2</c></seealso>.</p>
+          </item>
+        </list>
+        <p>If <c><anno>Reason</anno></c> is the atom <c>normal</c>,
+          <c><anno>Pid</anno></c>
+          does not exit. If it is trapping exits, the exit signal is
+          transformed into a message <c>{'EXIT', From, normal}</c>
+          and delivered to its message queue.</p>
+        <p>If <c><anno>Reason</anno></c> is the atom <c>kill</c>,
+          that is, if <c>exit(<anno>Pid</anno>, kill)</c> is called,
+          an untrappable exit signal is sent to <c><anno>Pid</anno></c>,
+          which unconditionally exits with exit reason <c>killed</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="external_size" arity="1"/>
-      <fsummary>Calculates the maximum size for a term encoded in the Erlang external term format.</fsummary>
+      <fsummary>Calculate the maximum size for a term encoded in the Erlang
+        external term format.</fsummary>
       <desc>
         <p>Calculates, without doing the encoding, the maximum byte size for
           a term encoded in the Erlang external term format. The following
@@ -1291,13 +1297,15 @@ b</pre>
 > <input>true = Size1 =&lt; Size2.</input>
 true</pre>
         <p>This is equivalent to a call to:</p>
-<code>erlang:external_size(<anno>Term</anno>, [])</code>
+<code>
+erlang:external_size(<anno>Term</anno>, [])</code>
       </desc>
     </func>
 
     <func>
       <name name="external_size" arity="2"/>
-      <fsummary>Calculates the maximum size for a term encoded in the Erlang external term format.</fsummary>
+      <fsummary>Calculate the maximum size for a term encoded in the Erlang
+        external term format.</fsummary>
       <desc>
         <p>Calculates, without doing the encoding, the maximum byte size for
           a term encoded in the Erlang external term format. The following
@@ -1309,13 +1317,14 @@ true</pre>
 true</pre>
         <p>Option <c>{minor_version, <anno>Version</anno>}</c> specifies how
           floats are encoded. For a detailed description, see
-          <seealso marker="#term_to_binary/2">term_to_binary/2</seealso>.</p>
+          <seealso marker="#term_to_binary/2">
+          <c>term_to_binary/2</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="float" arity="1"/>
-      <fsummary>Converts a number to a float.</fsummary>
+      <fsummary>Convert a number to a float.</fsummary>
       <desc>
         <p>Returns a float by converting <c><anno>Number</anno></c> to a float,
           for example:</p>
@@ -1326,7 +1335,8 @@ true</pre>
         <note>
           <p>If used on the top level in a guard, it tests whether the
             argument is a floating point number; for clarity, use
-            <seealso marker="#is_float/1">is_float/1</seealso> instead.</p>
+            <seealso marker="#is_float/1"><c>is_float/1</c></seealso>
+            instead.</p>
           <p>When <c>float/1</c> is used in an expression in a guard,
             such as '<c>float(A) == 4.0</c>', it converts a number as
             described earlier.</p>
@@ -1345,13 +1355,14 @@ true</pre>
 
     <func>
       <name name="float_to_binary" arity="2"/>
-      <fsummary>Text representation of a float formatted using given options.</fsummary>
+      <fsummary>Text representation of a float formatted using specified
+        options.</fsummary>
       <desc>
         <p>Returns a binary corresponding to the text
           representation of <c><anno>Float</anno></c> using fixed decimal 
           point formatting. <c><anno>Options</anno></c> behaves in the same
-          way as <seealso marker="#float_to_list/2">float_to_list/2</seealso>.</p>
-        <p>Examples:</p>
+          way as <seealso marker="#float_to_list/2">
+          <c>float_to_list/2</c></seealso>. Examples:</p>
         <pre>
 > <input>float_to_binary(7.12, [{decimals, 4}]).</input>
 &lt;&lt;"7.1200">>
@@ -1371,27 +1382,29 @@ true</pre>
 
     <func>
       <name name="float_to_list" arity="2"/>
-      <fsummary>Text representation of a float formatted using given options.</fsummary>
+      <fsummary>Text representation of a float formatted using specified
+        options.</fsummary>
       <desc>
         <p>Returns a string corresponding to the text representation
-          of <c>Float</c> using fixed decimal point formatting. The
-          options are as follows:</p>
+          of <c>Float</c> using fixed decimal point formatting.</p>
+        <p>Available options:</p>
         <list type="bulleted">
-          <item>If option <c>decimals</c> is specified, the returned value
+          <item><p>If option <c>decimals</c> is specified, the returned value
             contains at most <c>Decimals</c> number of digits past the
-            decimal point.  If the number does not fit in the internal
-            static buffer of 256 bytes, the function throws <c>badarg</c>.
+            decimal point. If the number does not fit in the internal
+            static buffer of 256 bytes, the function throws <c>badarg</c>.</p>
           </item>
-          <item>If option <c>compact</c> is provided, the trailing zeros
+          <item><p>If option <c>compact</c> is specified, the trailing zeros
             at the end of the list are truncated. This option is only
-            meaningful together with option <c>decimals</c>.
+            meaningful together with option <c>decimals</c>.</p>
           </item>
-          <item>If option <c>scientific</c> is provided, the float is
+          <item><p>If option <c>scientific</c> is specified, the float is
             formatted using scientific notation with <c>Decimals</c>
-            digits of precision.
+            digits of precision.</p>
           </item>
-          <item>If <c>Options</c> is <c>[]</c>, the function behaves as
-            <seealso marker="#float_to_list/1">float_to_list/1</seealso>.
+          <item><p>If <c>Options</c> is <c>[]</c>, the function behaves as
+            <seealso marker="#float_to_list/1">
+            <c>float_to_list/1</c></seealso>.</p>
           </item>
         </list>
         <p>Examples:</p>
@@ -1418,16 +1431,16 @@ true</pre>
         </warning>
         <p>Two types of funs have slightly different semantics:</p>
         <list type="bulleted">
-          <item>A fun created by <c>fun M:F/A</c> is called an
+          <item><p>A fun created by <c>fun M:F/A</c> is called an
             <em>external</em> fun. Calling it will always call the
             function <c>F</c> with arity <c>A</c> in the latest code for
             module <c>M</c>. Notice that module <c>M</c> does not even
-            need to be loaded when the fun <c>fun M:F/A</c> is created.
+            need to be loaded when the fun <c>fun M:F/A</c> is created.</p>
           </item>
-          <item>All other funs are called <em>local</em>. When a local fun
+          <item><p>All other funs are called <em>local</em>. When a local fun
             is called, the same version of the code that created the fun
             is called (even if a newer version of the module has been
-            loaded).
+            loaded).</p>
           </item>
         </list>
         <p>The following elements are always present in the list
@@ -1491,14 +1504,14 @@ true</pre>
           <tag><c>{new_uniq, Uniq}</c></tag>
           <item>
             <p><c>Uniq</c> (a binary) is a unique value for this fun. It
-            is calculated from the compiled code for the entire module.</p>
+              is calculated from the compiled code for the entire module.</p>
           </item>
           <tag><c>{uniq, Uniq}</c></tag>
           <item>
             <p><c>Uniq</c> (an integer) is a unique value for this fun.
-            As from OTP R15, this integer is calculated from the
-            compiled code for the entire module. Before OTP R15, this
-            integer was based on only the body of the fun.</p>
+              As from Erlang/OTP R15, this integer is calculated from the
+              compiled code for the entire module. Before Erlang/OTP R15, this
+              integer was based on only the body of the fun.</p>
           </item>
         </taglist>
       </desc>
@@ -1520,7 +1533,7 @@ true</pre>
           <c>uniq</c>, and <c>pid</c>. For an external fun, the value
           of any of these items is always the atom <c>undefined</c>.</p>
         <p>See
-          <seealso marker="#fun_info/1">erlang:fun_info/1</seealso>.</p>
+          <seealso marker="#fun_info/1"><c>erlang:fun_info/1</c></seealso>.</p>
       </desc>
     </func>
 
@@ -1535,20 +1548,24 @@ true</pre>
 
     <func>
       <name name="function_exported" arity="3"/>
-      <fsummary>Checks if a function is exported and loaded.</fsummary>
+      <fsummary>Check if a function is exported and loaded.</fsummary>
       <desc>
-        <p>Returns <c>true</c> if the module <c><anno>Module</anno></c> is loaded
-          and contains an exported function <c><anno>Function</anno>/<anno>Arity</anno></c>,
-	  or if there is a BIF (a built-in function implemented in C)
-	  with the given name, otherwise returns <c>false</c>.</p>
-	  <note><p>This function used to return false for built-in
-	  functions before the 18.0 release.</p></note>
+        <p>Returns <c>true</c> if the module <c><anno>Module</anno></c> is
+          loaded and contains an exported function
+          <c><anno>Function</anno>/<anno>Arity</anno></c>,
+          or if there is a BIF (a built-in function implemented in C)
+          with the specified name, otherwise returns <c>false</c>.</p>
+        <note>
+          <p>This function used to return <c>false</c> for BIFs
+            before Erlang/OTP 18.0.</p>
+        </note>
       </desc>
     </func>
 
     <func>
       <name name="garbage_collect" arity="0"/>
-      <fsummary>Forces an immediate garbage collection of the calling process.</fsummary>
+      <fsummary>Force an immediate garbage collection of the calling process.
+      </fsummary>
       <desc>
         <p>Forces an immediate garbage collection of the
           executing process. The function is not to be used unless
@@ -1563,73 +1580,76 @@ true</pre>
 
     <func>
       <name name="garbage_collect" arity="1"/>
-      <fsummary>Garbage collects a process.</fsummary>
+      <fsummary>Garbage collect a process.</fsummary>
       <desc>
         <p>The same as
-	<seealso marker="#garbage_collect/2"><c>garbage_collect(<anno>Pid</anno>, [])</c></seealso>.</p>
+          <seealso marker="#garbage_collect/2">
+          <c>garbage_collect(<anno>Pid</anno>, [])</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="garbage_collect" arity="2"/>
-      <fsummary>Garbage collects a process.</fsummary>
+      <fsummary>Garbage collect a process.</fsummary>
       <desc>
         <p>Garbage collects the node local process identified by
-        <c><anno>Pid</anno></c>.</p>
-        <p>The available <c><anno>Option</anno></c>s are as follows:</p>
+          <c><anno>Pid</anno></c>.</p>
+        <p><c><anno>Option</anno></c>:</p>
         <taglist>
           <tag><c>{async, RequestId}</c></tag>
           <item>The function <c>garbage_collect/2</c> returns
-	    the value <c>async</c> immediately after the request
-	    has been sent. When the request has been processed, the
-	    process that called this function is passed a message on
+            the value <c>async</c> immediately after the request
+            has been sent. When the request has been processed, the
+            process that called this function is passed a message on
             the form <c>{garbage_collect,
             <anno>RequestId</anno>, <anno>GCResult</anno>}</c>.
           </item>
         </taglist>
-	<p>If <c><anno>Pid</anno></c> equals <c>self()</c>, and
-	no <c>async</c> option has been passed, the garbage
-	collection is performed at once, that is, the same as calling
-	<seealso marker="#garbage_collect/0">garbage_collect/0</seealso>.
-	Otherwise a request for garbage collection
-	is sent to the process identified by <c><anno>Pid</anno></c>,
-	and will be handled when appropriate. If no <c>async</c>
-	option has been passed, the caller blocks until
-	<c><anno>GCResult</anno></c> is available and can be returned.</p>
-	<p><c><anno>GCResult</anno></c> informs about the result of
-	the garbage collection request as follows:</p>
+        <p>If <c><anno>Pid</anno></c> equals <c>self()</c>, and
+          no <c>async</c> option has been passed, the garbage
+          collection is performed at once, that is, the same as calling
+          <seealso marker="#garbage_collect/0">
+          <c>garbage_collect/0</c></seealso>.
+          Otherwise a request for garbage collection
+          is sent to the process identified by <c><anno>Pid</anno></c>,
+          and will be handled when appropriate. If no <c>async</c>
+          option has been passed, the caller blocks until
+          <c><anno>GCResult</anno></c> is available and can be returned.</p>
+        <p><c><anno>GCResult</anno></c> informs about the result of
+          the garbage collection request as follows:</p>
         <taglist>
           <tag><c>true</c></tag>
           <item>
-	    The process identified by <c><anno>Pid</anno></c> has
-	    been garbage collected.
-	  </item>
+            The process identified by <c><anno>Pid</anno></c> has
+            been garbage collected.
+          </item>
           <tag><c>false</c></tag>
           <item>
-	    No garbage collection was performed, as
-	    the process identified by <c><anno>Pid</anno></c>
-	    terminated before the request could be satisfied.
-	  </item>
+            No garbage collection was performed, as
+            the process identified by <c><anno>Pid</anno></c>
+            terminated before the request could be satisfied.
+          </item>
         </taglist>
         <p>Notice that the same caveats apply as for
-	<seealso marker="#garbage_collect/0">garbage_collect/0</seealso>.</p>
+          <seealso marker="#garbage_collect/0">
+          <c>garbage_collect/0</c></seealso>.</p>
         <p>Failures:</p>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	    If <c><anno>Pid</anno></c> is not a node local process identifier.
-	  </item>
+            If <c><anno>Pid</anno></c> is not a node local process identifier.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	    If <c><anno>OptionList</anno></c> is an invalid list of options.
-	  </item>
+            If <c><anno>OptionList</anno></c> is an invalid list of options.
+          </item>
         </taglist>
       </desc>
     </func>
 
     <func>
       <name name="get" arity="0"/>
-      <fsummary>Returns the process dictionary.</fsummary>
+      <fsummary>Return the process dictionary.</fsummary>
       <desc>
         <p>Returns the process dictionary as a list of
           <c>{<anno>Key</anno>, <anno>Val</anno>}</c> tuples, for example:</p>
@@ -1644,12 +1664,11 @@ true</pre>
 
     <func>
       <name name="get" arity="1"/>
-      <fsummary>Returns a value from the process dictionary.</fsummary>
+      <fsummary>Return a value from the process dictionary.</fsummary>
       <desc>
-        <p>Returns the value <c><anno>Val</anno></c> associated with <c><anno>Key</anno></c> in
-          the process dictionary, or <c>undefined</c> if <c><anno>Key</anno></c>
-          does not exist.</p>
-        <p>Example:</p>
+        <p>Returns the value <c><anno>Val</anno></c> associated with
+          <c><anno>Key</anno></c> in the process dictionary, or <c>undefined</c>
+          if <c><anno>Key</anno></c> does not exist. Example:</p>
         <pre>
 > <input>put(key1, merry),</input>
 <input>put(key2, lambs),</input>
@@ -1661,7 +1680,7 @@ true</pre>
 
     <func>
       <name name="get_cookie" arity="0"/>
-      <fsummary>Gets the magic cookie of the local node.</fsummary>
+      <fsummary>Get the magic cookie of the local node.</fsummary>
       <desc>
         <p>Returns the magic cookie of the local node if the node is
           alive, otherwise the atom <c>nocookie</c>.</p>
@@ -1670,9 +1689,11 @@ true</pre>
 
     <func>
       <name name="get_keys" arity="0"/>
-      <fsummary>Return a list of all keys from the process dictionary</fsummary>
+      <fsummary>Return a list of all keys from the process dictionary.
+      </fsummary>
       <desc>
-        <p>Returns a list of keys all keys present in the process dictionary.</p>
+        <p>Returns a list of all keys present in the process dictionary,
+          for example:</p>
         <pre>
 > <input>put(dog, {animal,1}),</input>
 <input>put(cow, {animal,2}),</input>
@@ -1681,9 +1702,10 @@ true</pre>
 [dog,cow,lamb]</pre>
       </desc>
     </func>
+
     <func>
       <name name="get_keys" arity="1"/>
-      <fsummary>Returns a list of keys from the process dictionary.</fsummary>
+      <fsummary>Return a list of keys from the process dictionary.</fsummary>
       <desc>
         <p>Returns a list of keys that are associated with the value
           <c><anno>Val</anno></c> in the process dictionary, for example:</p>
@@ -1701,48 +1723,49 @@ true</pre>
 
     <func>
       <name name="get_stacktrace" arity="0"/>
-      <fsummary>Gets the call stack back-trace of the last exception.</fsummary>
+      <fsummary>Get the call stack back-trace of the last exception.</fsummary>
       <type name="stack_item"/>
       <desc>
         <p>Gets the call stack back-trace (<em>stacktrace</em>) of the
           last exception in the calling process as a list of
-          <c>{<anno>Module</anno>,<anno>Function</anno>,<anno>Arity</anno>,<anno>Location</anno>}</c> tuples.
-          Field <c><anno>Arity</anno></c> in the first tuple can be the
+          <c>{<anno>Module</anno>,<anno>Function</anno>,<anno>Arity</anno>,<anno>Location</anno>}</c>
+          tuples. Field <c><anno>Arity</anno></c> in the first tuple can be the
           argument list of that function call instead of an arity integer,
           depending on the exception.</p>
         <p>If there has not been any exceptions in a process, the
           stacktrace is <c>[]</c>. After a code change for the process,
           the stacktrace can also be reset to <c>[]</c>.</p>
-        <p>The stacktrace is the same data as the <c>catch</c> operator
+        <p>The stacktrace is the same data as operator <c>catch</c>
           returns, for example:</p>
-        <p><c>{'EXIT',{badarg,Stacktrace}} = catch abs(x)</c></p>
-	<p><c><anno>Location</anno></c> is a (possibly empty) list
+        <pre>
+{'EXIT',{badarg,Stacktrace}} = catch abs(x)</pre>
+        <p><c><anno>Location</anno></c> is a (possibly empty) list
           of two-tuples that
-	  can indicate the location in the source code of the function.
-	  The first element is an atom describing the type of
-	  information in the second element. The following
-	  items can occur:</p>
-	<taglist>
-	  <tag><c>file</c></tag>
-	  <item>The second element of the tuple is a string (list of
-	      characters) representing the file name of the source file
-	      of the function.
-	  </item>
-	  <tag><c>line</c></tag>
-	  <item>The second element of the tuple is the line number
-	      (an integer greater than zero) in the source file
-	      where the exception occurred or the function was called.
-	  </item>
-	</taglist>
+          can indicate the location in the source code of the function.
+          The first element is an atom describing the type of
+          information in the second element. The following
+          items can occur:</p>
+        <taglist>
+          <tag><c>file</c></tag>
+          <item>The second element of the tuple is a string (list of
+            characters) representing the filename of the source file
+            of the function.
+          </item>
+          <tag><c>line</c></tag>
+          <item>The second element of the tuple is the line number
+            (an integer &gt; 0) in the source file
+            where the exception occurred or the function was called.
+          </item>
+        </taglist>
         <p>See also
-          <seealso marker="#error/1">erlang:error/1</seealso> and
-          <seealso marker="#error/2">erlang:error/2</seealso>.</p>
+          <seealso marker="#error/1"><c>error/1</c></seealso> and
+          <seealso marker="#error/2"><c>error/2</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="group_leader" arity="0"/>
-      <fsummary>Gets the group leader for the calling process.</fsummary>
+      <fsummary>Get the group leader for the calling process.</fsummary>
       <desc>
         <p>Returns the process identifier of the group leader for the
           process evaluating the function.</p>
@@ -1750,14 +1773,14 @@ true</pre>
           groups have a <em>group leader</em>. All I/O from the group
           is channeled to the group leader. When a new process is
           spawned, it gets the same group leader as the spawning
-          process. Initially, at system start-up, <c>init</c> is both
+          process. Initially, at system startup, <c>init</c> is both
           its own group leader and the group leader of all processes.</p>
       </desc>
     </func>
 
     <func>
       <name name="group_leader" arity="2"/>
-      <fsummary>Sets the group leader for a process.</fsummary>
+      <fsummary>Set the group leader for a process.</fsummary>
       <desc>
         <p>Sets the group leader of <c><anno>Pid</anno></c>
           to <c><anno>GroupLeader</anno></c>.
@@ -1765,72 +1788,72 @@ true</pre>
           certain shell is to have another group leader than
           <c>init</c>.</p>
         <p>See also
-          <seealso marker="#group_leader/0">group_leader/0</seealso>.</p>
+          <seealso marker="#group_leader/0"><c>group_leader/0</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="halt" arity="0"/>
-      <fsummary>Halts the Erlang runtime system and indicates normal exit to the calling environment.</fsummary>
+      <fsummary>Halt the Erlang runtime system and indicate normal exit to
+        the calling environment.</fsummary>
       <desc>
-	<p>The same as
-	  <seealso marker="#halt/2"><c>halt(0, [])</c></seealso>.</p>
-        <p>Example:</p>
+        <p>The same as
+          <seealso marker="#halt/2"><c>halt(0, [])</c></seealso>. Example:</p>
         <pre>
 > <input>halt().</input>
-os_prompt% </pre>
+os_prompt%</pre>
       </desc>
     </func>
 
     <func>
       <name name="halt" arity="1"/>
-      <fsummary>Halts the Erlang runtime system.</fsummary>
+      <fsummary>Halt the Erlang runtime system.</fsummary>
       <desc>
-	<p>The same as
-	  <seealso marker="#halt/2"><c>halt(<anno>Status</anno>, [])</c></seealso>.</p>
-        <p>Example:</p>
+        <p>The same as <seealso marker="#halt/2">
+          <c>halt(<anno>Status</anno>, [])</c></seealso>. Example:</p>
         <pre>
 > <input>halt(17).</input>
 os_prompt% <input>echo $?</input>
 17
-os_prompt% </pre>
+os_prompt%</pre>
       </desc>
     </func>
 
     <func>
       <name name="halt" arity="2"/>
-      <fsummary>Halts the Erlang runtime system.</fsummary>
+      <fsummary>Halt the Erlang runtime system.</fsummary>
       <desc>
         <p><c><anno>Status</anno></c> must be a non-negative integer, a string,
-	  or the atom <c>abort</c>.
-	  Halts the Erlang runtime system. Has no return value.
-	  Depending on <c><anno>Status</anno></c>, the following occurs:</p>
-	<taglist>
-	  <tag>integer()</tag>
-	  <item>The runtime system exits with integer value
-          <c><anno>Status</anno></c>
-	  as status code to the calling environment (OS).
-	  </item>
-	  <tag>string()</tag>
-	  <item>An Erlang crash dump is produced with <c><anno>Status</anno></c>
-	  as slogan. Then the runtime system exits with status code <c>1</c>.
-	  Note that only code points in the range 0-255 may be used
-	  and the string will be truncated if longer than 200 characters.
-	  </item>
-	  <tag><c>abort</c></tag>
-	  <item>
-	    The runtime system aborts producing a core dump, if that is
-	    enabled in the OS.
-	  </item>
-	</taglist>
-        <note><p>On many platforms, the OS supports only status
-        codes 0-255. A too large status code will be truncated by clearing
-	the high bits.</p></note>
-	<p>For integer <c><anno>Status</anno></c>, the Erlang runtime system
+          or the atom <c>abort</c>.
+          Halts the Erlang runtime system. Has no return value.
+          Depending on <c><anno>Status</anno></c>, the following occurs:</p>
+        <taglist>
+          <tag>integer()</tag>
+          <item>The runtime system exits with integer value
+            <c><anno>Status</anno></c>
+            as status code to the calling environment (OS).
+          </item>
+          <tag>string()</tag>
+          <item>An Erlang crash dump is produced with <c><anno>Status</anno></c>
+            as slogan. Then the runtime system exits with status code <c>1</c>.
+            Note that only code points in the range 0-255 may be used
+	    and the string will be truncated if longer than 200 characters.
+          </item>
+          <tag><c>abort</c></tag>
+          <item>The runtime system aborts producing a core dump, if that is
+            enabled in the OS.
+          </item>
+        </taglist>
+        <note>
+          <p>On many platforms, the OS supports only status
+            codes 0-255. A too large status code is truncated by clearing
+            the high bits.</p>
+        </note>
+        <p>For integer <c><anno>Status</anno></c>, the Erlang runtime system
           closes all ports and allows async threads to finish their
           operations before exiting. To exit without such flushing, use
-	  <c><anno>Option</anno></c> as <c>{flush,false}</c>.</p>
-	<p>For statuses <c>string()</c> and <c>abort</c>, option
+          <c><anno>Option</anno></c> as <c>{flush,false}</c>.</p>
+        <p>For statuses <c>string()</c> and <c>abort</c>, option
           <c>flush</c> is ignored and flushing is <em>not</em> done.</p>
       </desc>
     </func>
@@ -1842,13 +1865,15 @@ os_prompt% </pre>
         <p>Returns a hash value for <c><anno>Term</anno></c> within the range
           <c>1..<anno>Range</anno></c>. The maximum range is 1..2^27-1.</p>
         <warning>
-          <p>This BIF is deprecated, as the hash value can differ on
-            different architectures. The hash values for integer
-            terms higher than 2^27 and large binaries are
+          <p><em>This BIF is deprecated, as the hash value can differ on
+            different architectures.</em> The hash values for integer
+            terms &gt; 2^27 and large binaries are
             poor. The BIF is retained for backward compatibility
             reasons (it can have been used to hash records into a file),
             but all new code is to use one of the BIFs
-            <c>erlang:phash/2</c> or <c>erlang:phash2/1,2</c> instead.</p>
+            <seealso marker="#phash/2"><c>erlang:phash/2</c></seealso> or
+            <seealso marker="#phash2/1"><c>erlang:phash2/1,2</c></seealso>
+            instead.</p>
         </warning>
       </desc>
     </func>
@@ -1870,7 +1895,7 @@ os_prompt% </pre>
 
     <func>
       <name name="hibernate" arity="3"/>
-      <fsummary>Hibernates a process until a message is sent to it.</fsummary>
+      <fsummary>Hibernate a process until a message is sent to it.</fsummary>
       <desc>
         <p>Puts the calling process into a wait state where its memory
           allocation has been reduced as much as possible. This is
@@ -1878,15 +1903,15 @@ os_prompt% </pre>
           soon.</p>
         <p>The process is awaken when a message is sent to it, and control
           resumes in <c><anno>Module</anno>:<anno>Function</anno></c> with
-          the arguments given by <c><anno>Args</anno></c> with the call
+          the arguments specified by <c><anno>Args</anno></c> with the call
           stack emptied, meaning that the process terminates when that
           function returns. Thus <c>erlang:hibernate/3</c> never
           returns to its caller.</p>
         <p>If the process has any message in its message queue,
           the process is awakened immediately in the same way as
           described earlier.</p>
-        <p>In more technical terms, what <c>erlang:hibernate/3</c> does
-          is the following. It discards the call stack for the process,
+        <p>In more technical terms, <c>erlang:hibernate/3</c>
+          discards the call stack for the process,
           and then garbage collects the process. After this,
           all live data is in one continuous heap. The heap
           is then shrunken to the exact same size as the live data
@@ -1898,11 +1923,12 @@ os_prompt% </pre>
           size is changed to a size not smaller than the minimum heap
           size.</p>
         <p>Notice that emptying the call stack means that any surrounding
-          <c>catch</c> is removed and must be reinserted after
+          <c>catch</c> is removed and must be re-inserted after
           hibernation. One effect of this is that processes started
           using <c>proc_lib</c> (also indirectly, such as
           <c>gen_server</c> processes), are to use
-          <seealso marker="stdlib:proc_lib#hibernate/3">proc_lib:hibernate/3</seealso>
+          <seealso marker="stdlib:proc_lib#hibernate/3">
+          <c>proc_lib:hibernate/3</c></seealso> in <c>STDLIB</c>
           instead, to ensure that the exception handler continues to work
           when the process wakes up.</p>
       </desc>
@@ -1910,15 +1936,16 @@ os_prompt% </pre>
 
     <func>
       <name name="insert_element" arity="3"/>
-      <fsummary>Inserts an element at index in a tuple.</fsummary>
-      <type_desc variable="Index">1..tuple_size(<anno>Tuple1</anno>) + 1</type_desc>
+      <fsummary>Insert an element at index in a tuple.</fsummary>
+      <type_desc variable="Index">1..tuple_size(<anno>Tuple1</anno>)
+        + 1</type_desc>
       <desc>
         <p>Returns a new tuple with element <c><anno>Term</anno></c>
-        inserted at position
-        <c><anno>Index</anno></c> in tuple <c><anno>Tuple1</anno></c>.
-        All elements from position <c><anno>Index</anno></c> and upwards are
-        pushed one step higher in the new tuple <c><anno>Tuple2</anno></c>.</p>
-        <p>Example:</p>
+          inserted at position
+          <c><anno>Index</anno></c> in tuple <c><anno>Tuple1</anno></c>.
+          All elements from position <c><anno>Index</anno></c> and upwards are
+          pushed one step higher in the new tuple <c><anno>Tuple2</anno></c>.
+          Example:</p>
         <pre>
 > <input>erlang:insert_element(2, {one, two, three}, new).</input>
 {one,new,two,three}</pre>
@@ -1942,8 +1969,8 @@ os_prompt% </pre>
       <fsummary>Text representation of an integer.</fsummary>
       <desc>
         <p>Returns a binary corresponding to the text
-        representation of <c><anno>Integer</anno></c> in base
-        <c><anno>Base</anno></c>, for example:</p>
+          representation of <c><anno>Integer</anno></c> in base
+          <c><anno>Base</anno></c>, for example:</p>
         <pre>
 > <input>integer_to_binary(1023, 16).</input>
 &lt;&lt;"3FF">></pre>
@@ -1979,7 +2006,7 @@ os_prompt% </pre>
       <name name="iolist_size" arity="1"/>
       <fsummary>Size of an iolist.</fsummary>
       <desc>
-        <p>Returns an integer that is the size in bytes
+        <p>Returns an integer, that is the size in bytes,
           of the binary that would be the result of
           <c>iolist_to_binary(<anno>Item</anno>)</c>, for example:</p>
         <pre>
@@ -1990,7 +2017,7 @@ os_prompt% </pre>
 
     <func>
       <name name="iolist_to_binary" arity="1"/>
-      <fsummary>Converts an iolist to a binary.</fsummary>
+      <fsummary>Convert an iolist to a binary.</fsummary>
       <desc>
         <p>Returns a binary that is made from the integers and
           binaries in <c><anno>IoListOrBinary</anno></c>, for example:</p>
@@ -2008,7 +2035,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_alive" arity="0"/>
-      <fsummary>Checks whether the local node is alive.</fsummary>
+      <fsummary>Check whether the local node is alive.</fsummary>
       <desc>
         <p>Returns <c>true</c> if the local node is alive (that is, if
           the node can be part of a distributed system), otherwise
@@ -2018,7 +2045,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_atom" arity="1"/>
-      <fsummary>Checks whether a term is an atom.</fsummary>
+      <fsummary>Check whether a term is an atom.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is an atom,
           otherwise <c>false</c>.</p>
@@ -2028,18 +2055,18 @@ os_prompt% </pre>
 
     <func>
       <name name="is_binary" arity="1"/>
-      <fsummary>Checks whether a term is a binary.</fsummary>
+      <fsummary>Check whether a term is a binary.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a binary,
           otherwise <c>false</c>.</p>
-	<p>A binary always contains a complete number of bytes.</p>
+        <p>A binary always contains a complete number of bytes.</p>
         <p>Allowed in guard tests.</p>
       </desc>
     </func>
 
     <func>
       <name name="is_bitstring" arity="1"/>
-      <fsummary>Checks whether a term is a bitstring.</fsummary>
+      <fsummary>Check whether a term is a bitstring.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a
           bitstring (including a binary), otherwise <c>false</c>.</p>
@@ -2049,7 +2076,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_boolean" arity="1"/>
-      <fsummary>Checks whether a term is a boolean.</fsummary>
+      <fsummary>Check whether a term is a boolean.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is the
           atom <c>true</c> or the atom <c>false</c> (that is, a boolean).
@@ -2060,18 +2087,18 @@ os_prompt% </pre>
 
     <func>
       <name name="is_builtin" arity="3"/>
-      <fsummary>Checks if a function is a BIF implemented in C.</fsummary>
+      <fsummary>Check if a function is a BIF implemented in C.</fsummary>
       <desc>
         <p>This BIF is useful for builders of cross-reference tools.</p>
         <p>Returns <c>true</c> if
           <c><anno>Module</anno>:<anno>Function</anno>/<anno>Arity</anno></c>
-          is a BIF implemented in C, otherwise  <c>false</c>.</p>
+          is a BIF implemented in C, otherwise <c>false</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="is_float" arity="1"/>
-      <fsummary>Checks whether a term is a float.</fsummary>
+      <fsummary>Check whether a term is a float.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a floating point
           number, otherwise <c>false</c>.</p>
@@ -2081,7 +2108,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_function" arity="1"/>
-      <fsummary>Checks whether a term is a fun.</fsummary>
+      <fsummary>Check whether a term is a fun.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a fun, otherwise
           <c>false</c>.</p>
@@ -2091,7 +2118,8 @@ os_prompt% </pre>
 
     <func>
       <name name="is_function" arity="2"/>
-      <fsummary>Checks whether a term is a fun with a given arity.</fsummary>
+      <fsummary>Check whether a term is a fun with a specified given arity.
+      </fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a fun that can be
           applied with <c><anno>Arity</anno></c> number of arguments, otherwise
@@ -2102,7 +2130,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_integer" arity="1"/>
-      <fsummary>Checks whether a term is an integer.</fsummary>
+      <fsummary>Check whether a term is an integer.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is an integer,
           otherwise <c>false</c>.</p>
@@ -2112,7 +2140,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_list" arity="1"/>
-      <fsummary>Checks whether a term is a list.</fsummary>
+      <fsummary>Check whether a term is a list.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a list with
           zero or more elements, otherwise <c>false</c>.</p>
@@ -2122,7 +2150,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_map" arity="1"/>
-      <fsummary>Checks whether a term is a map.</fsummary>
+      <fsummary>Check whether a term is a map.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a map,
           otherwise <c>false</c>.</p>
@@ -2132,7 +2160,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_number" arity="1"/>
-      <fsummary>Checks whether a term is a number.</fsummary>
+      <fsummary>Check whether a term is a number.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is an integer or a
           floating point number. Otherwise returns <c>false</c>.</p>
@@ -2142,7 +2170,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_pid" arity="1"/>
-      <fsummary>Checks whether a term is a process identifier.</fsummary>
+      <fsummary>Check whether a term is a process identifier.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a process
           identifier, otherwise <c>false</c>.</p>
@@ -2152,7 +2180,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_port" arity="1"/>
-      <fsummary>Checks whether a term is a port.</fsummary>
+      <fsummary>Check whether a term is a port.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a port identifier,
           otherwise <c>false</c>.</p>
@@ -2162,26 +2190,26 @@ os_prompt% </pre>
 
     <func>
       <name name="is_process_alive" arity="1"/>
-      <fsummary>Checks whether a process is alive.</fsummary>
+      <fsummary>Check whether a process is alive.</fsummary>
       <desc>
-        <p><c><anno>Pid</anno></c> must refer to a process at the local node.</p>
+        <p><c><anno>Pid</anno></c> must refer to a process at the local
+          node.</p>
         <p>Returns <c>true</c> if the process exists and is alive, that
           is, is not exiting and has not exited. Otherwise returns
-	  <c>false</c>.
-	</p>
+          <c>false</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="is_record" arity="2"/>
-      <fsummary>Checks whether a term appears to be a record.</fsummary>
+      <fsummary>Check whether a term appears to be a record.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a tuple and its
           first element is <c><anno>RecordTag</anno></c>.
           Otherwise returns <c>false</c>.</p>
         <note>
           <p>Normally the compiler treats calls to <c>is_record/2</c>
-            specially. It emits code to verify that <c><anno>Term</anno></c>
+            especially. It emits code to verify that <c><anno>Term</anno></c>
             is a tuple, that its first element is
             <c><anno>RecordTag</anno></c>, and that the
             size is correct. However, if <c><anno>RecordTag</anno></c> is
@@ -2195,7 +2223,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_record" arity="3"/>
-      <fsummary>Checks whether a term appears to be a record.</fsummary>
+      <fsummary>Check whether a term appears to be a record.</fsummary>
       <desc>
         <p><c><anno>RecordTag</anno></c> must be an atom.</p>
         <p>Returns <c>true</c> if
@@ -2214,7 +2242,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_reference" arity="1"/>
-      <fsummary>Checks whether a term is a reference.</fsummary>
+      <fsummary>Check whether a term is a reference.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a reference,
           otherwise <c>false</c>.</p>
@@ -2224,7 +2252,7 @@ os_prompt% </pre>
 
     <func>
       <name name="is_tuple" arity="1"/>
-      <fsummary>Checks whether a term is a tuple.</fsummary>
+      <fsummary>Check whether a term is a tuple.</fsummary>
       <desc>
         <p>Returns <c>true</c> if <c><anno>Term</anno></c> is a tuple,
           otherwise <c>false</c>.</p>
@@ -2246,7 +2274,7 @@ os_prompt% </pre>
 
     <func>
       <name name="link" arity="1"/>
-      <fsummary>Creates a link to another process (or port).</fsummary>
+      <fsummary>Create a link to another process (or port).</fsummary>
       <desc>
         <p>Creates a link between the calling process and another
           process (or port) <c><anno>PidOrPort</anno></c>, if there is
@@ -2256,34 +2284,34 @@ os_prompt% </pre>
         <p>If <c><anno>PidOrPort</anno></c> does not exist, the behavior
           of the BIF
           depends on if the calling process is trapping exits or not (see
-          <seealso marker="#process_flag/2">process_flag/2</seealso>):</p>
+          <seealso marker="#process_flag/2">
+          <c>process_flag/2</c></seealso>):</p>
         <list type="bulleted">
-          <item>If the calling process is not trapping exits, and
-           checking <c><anno>PidOrPort</anno></c> is cheap
-          (that is, if <c><anno>PidOrPort</anno></c>
-           is local), <c>link/1</c> fails with reason <c>noproc</c>.</item>
-          <item>Otherwise, if the calling process is trapping exits,
-           and/or <c><anno>PidOrPort</anno></c> is remote, <c>link/1</c>
-           returns <c>true</c>, but an exit signal with reason <c>noproc</c>
-           is sent to the calling process.</item>
+          <item><p>If the calling process is not trapping exits, and
+            checking <c><anno>PidOrPort</anno></c> is cheap
+            (that is, if <c><anno>PidOrPort</anno></c>
+            is local), <c>link/1</c> fails with reason <c>noproc</c>.</p></item>
+          <item><p>Otherwise, if the calling process is trapping exits,
+            and/or <c><anno>PidOrPort</anno></c> is remote, <c>link/1</c>
+            returns <c>true</c>, but an exit signal with reason <c>noproc</c>
+            is sent to the calling process.</p></item>
         </list>
       </desc>
     </func>
 
     <func>
       <name name="list_to_atom" arity="1"/>
-      <fsummary>Converts from text representation to an atom.</fsummary>
+      <fsummary>Convert from text representation to an atom.</fsummary>
       <desc>
         <p>Returns the atom whose text representation is
           <c><anno>String</anno></c>.</p>
-	<p><c><anno>String</anno></c> can only contain ISO-latin-1
-          characters (that is,
-          numbers less than 256) as the implementation does not
-          allow unicode characters equal to or above 256 in atoms.
-	  For more information on Unicode support in atoms, see
-	  <seealso marker="erl_ext_dist#utf8_atoms">note on UTF-8
+        <p><c><anno>String</anno></c> can only contain ISO-latin-1
+          characters (that is, numbers &lt; 256) as the implementation does not
+          allow Unicode characters equal to or above 256 in atoms.
+          For more information on Unicode support in atoms, see
+          <seealso marker="erl_ext_dist#utf8_atoms">note on UTF-8
           encoded atoms</seealso>
-	  in Section "External Term Format" in the User's Guide.</p>
+          in section "External Term Format" in the User's Guide.</p>
         <p>Example:</p>
         <pre>
 > <input>list_to_atom("Erlang").</input>
@@ -2293,7 +2321,7 @@ os_prompt% </pre>
 
     <func>
       <name name="list_to_binary" arity="1"/>
-      <fsummary>Converts a list to a binary.</fsummary>
+      <fsummary>Convert a list to a binary.</fsummary>
       <desc>
         <p>Returns a binary that is made from the integers and
           binaries in <c><anno>IoList</anno></c>, for example:</p>
@@ -2311,13 +2339,13 @@ os_prompt% </pre>
 
     <func>
       <name name="list_to_bitstring" arity="1"/>
-      <fsummary>Converts a list to a bitstring.</fsummary>
+      <fsummary>Convert a list to a bitstring.</fsummary>
       <type name="bitstring_list"/>
       <desc>
         <p>Returns a bitstring that is made from the integers and
           bitstrings in <c><anno>BitstringList</anno></c>. (The last tail in
-          <c><anno>BitstringList</anno></c> is allowed to be a bitstring.)</p>
-        <p>Example:</p>
+          <c><anno>BitstringList</anno></c> is allowed to be a bitstring.)
+          Example:</p>
         <pre>
 > <input>Bin1 = &lt;&lt;1,2,3&gt;&gt;.</input>
 &lt;&lt;1,2,3&gt;&gt;
@@ -2332,7 +2360,7 @@ os_prompt% </pre>
 
     <func>
       <name name="list_to_existing_atom" arity="1"/>
-      <fsummary>Converts from text representation to an atom.</fsummary>
+      <fsummary>Convert from text representation to an atom.</fsummary>
       <desc>
         <p>Returns the atom whose text representation is
           <c><anno>String</anno></c>,
@@ -2344,7 +2372,7 @@ os_prompt% </pre>
 
     <func>
       <name name="list_to_float" arity="1"/>
-      <fsummary>Converts from text representation to a float.</fsummary>
+      <fsummary>Convert from text representation to a float.</fsummary>
       <desc>
         <p>Returns the float whose text representation is
           <c><anno>String</anno></c>, for example:</p>
@@ -2358,7 +2386,7 @@ os_prompt% </pre>
 
     <func>
       <name name="list_to_integer" arity="1"/>
-      <fsummary>Converts from text representation to an integer.</fsummary>
+      <fsummary>Convert from text representation to an integer.</fsummary>
       <desc>
         <p>Returns an integer whose text representation is
           <c><anno>String</anno></c>, for example:</p>
@@ -2372,7 +2400,7 @@ os_prompt% </pre>
 
     <func>
       <name name="list_to_integer" arity="2"/>
-      <fsummary>Converts from text representation to an integer.</fsummary>
+      <fsummary>Convert from text representation to an integer.</fsummary>
       <desc>
         <p>Returns an integer whose text representation in base
           <c><anno>Base</anno></c> is <c><anno>String</anno></c>,
@@ -2387,7 +2415,7 @@ os_prompt% </pre>
 
     <func>
       <name name="list_to_pid" arity="1"/>
-      <fsummary>Converts from text representation to a pid.</fsummary>
+      <fsummary>Convert from text representation to a pid.</fsummary>
       <desc>
         <p>Returns a process identifier whose text representation is a 
           <c><anno>String</anno></c>, for example:</p>
@@ -2398,14 +2426,14 @@ os_prompt% </pre>
           representation of a process identifier.</p>
         <warning>
           <p>This BIF is intended for debugging and is not to be used
-	  in application programs.</p>
+            in application programs.</p>
         </warning>
       </desc>
     </func>
 
     <func>
       <name name="list_to_tuple" arity="1"/>
-      <fsummary>Converts a list to a tuple.</fsummary>
+      <fsummary>Convert a list to a tuple.</fsummary>
       <desc>
         <p>Returns a tuple corresponding to <c><anno>List</anno></c>,
           for example</p>
@@ -2418,7 +2446,7 @@ os_prompt% </pre>
 
     <func>
       <name name="load_module" arity="2"/>
-      <fsummary>Loads object code for a module.</fsummary>
+      <fsummary>Load object code for a module.</fsummary>
       <desc>
         <p>If <c><anno>Binary</anno></c> contains the object code for module
           <c><anno>Module</anno></c>, this BIF loads that object code. If
@@ -2429,23 +2457,21 @@ os_prompt% </pre>
           that code.</p>
         <p>Returns either <c>{module, <anno>Module</anno>}</c>, or
           <c>{error, <anno>Reason</anno>}</c> if loading fails.
-          <c><anno>Reason</anno></c> is any of the following:</p>
+          <c><anno>Reason</anno></c> is one of the following:</p>
         <taglist>
           <tag><c>badfile</c></tag>
-          <item>
-            <p>The object code in <c><anno>Binary</anno></c> has an
-              incorrect format <em>or</em> the object code contains code
-              for another module than <c><anno>Module</anno></c>.</p>
+          <item>The object code in <c><anno>Binary</anno></c> has an
+            incorrect format <em>or</em> the object code contains code
+            for another module than <c><anno>Module</anno></c>.
           </item>
           <tag><c>not_purged</c></tag>
-          <item>
-            <p><c><anno>Binary</anno></c> contains a module that cannot be
-              loaded because old code for this module already exists.</p>
+          <item><c><anno>Binary</anno></c> contains a module that cannot be
+            loaded because old code for this module already exists.
           </item>
         </taglist>
         <warning>
           <p>This BIF is intended for the code server (see
-            <seealso marker="kernel:code">code(3)</seealso>)
+            <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>)
             and is not to be used elsewhere.</p>
         </warning>
       </desc>
@@ -2453,33 +2479,33 @@ os_prompt% </pre>
 
     <func>
       <name name="load_nif" arity="2"/>
-      <fsummary>Loads NIF library.</fsummary>
+      <fsummary>Load NIF library.</fsummary>
       <desc>
         <note>
-          <p>Before OTP R14B, NIFs were an
-          experimental feature. Versions before OTP R14B can
-          have different and possibly incompatible NIF semantics and
-          interfaces. For example, in OTP R13B03 the return value on
-          failure was <c>{error,Reason,Text}</c>.</p>
+          <p>Before Erlang/OTP R14B, NIFs were an
+            experimental feature. Versions before Erlang/OTP R14B can
+            have different and possibly incompatible NIF semantics and
+            interfaces. For example, in Erlang/OTP R13B03 the return value on
+            failure was <c>{error,Reason,Text}</c>.</p>
         </note>
         <p>Loads and links a dynamic library containing native
-        implemented functions (NIFs) for a module. <c><anno>Path</anno></c>
-        is a file path to the shareable object/dynamic library file minus
-        the OS-dependent file extension (<c>.so</c> for Unix and
-        <c>.dll</c> for Windows. For information on how to
-        implement a NIF library, see
-        <seealso marker="erl_nif">erl_nif</seealso>.</p> 
+          implemented functions (NIFs) for a module. <c><anno>Path</anno></c>
+          is a file path to the shareable object/dynamic library file minus
+          the OS-dependent file extension (<c>.so</c> for Unix and
+          <c>.dll</c> for Windows). For information on how to
+          implement a NIF library, see
+          <seealso marker="erl_nif"><c>erl_nif</c></seealso>.</p> 
         <p><c><anno>LoadInfo</anno></c> can be any term. It is passed on to
-        the library as part of the initialization. A good practice is
-        to include a module version number to support future code
-        upgrade scenarios.</p>
+          the library as part of the initialization. A good practice is
+          to include a module version number to support future code
+          upgrade scenarios.</p>
         <p>The call to <c>load_nif/2</c> must be made
-        <em>directly</em> from the Erlang code of the module that the
-        NIF library belongs to. It returns either <c>ok</c>, or
-        <c>{error,{<anno>Reason</anno>,Text}}</c> if loading fails.
-        <c><anno>Reason</anno></c> is one of the following atoms
-        while <c><anno>Text</anno></c> is a human readable string that
-        can give more information about the failure:</p>
+          <em>directly</em> from the Erlang code of the module that the
+          NIF library belongs to. It returns either <c>ok</c>, or
+          <c>{error,{<anno>Reason</anno>,Text}}</c> if loading fails.
+          <c><anno>Reason</anno></c> is one of the following atoms
+          while <c><anno>Text</anno></c> is a human readable string that
+          can give more information about the failure:</p>
         <taglist>
           <tag><c>load_failed</c></tag>
           <item>The OS failed to load the NIF library.
@@ -2502,11 +2528,12 @@ os_prompt% </pre>
 
     <func>
       <name name="loaded" arity="0"/>
-      <fsummary>Lists all loaded modules.</fsummary>
+      <fsummary>List all loaded modules.</fsummary>
       <desc>
         <p>Returns a list of all loaded Erlang modules (current and
           old code), including preloaded modules.</p>
-        <p>See also <seealso marker="kernel:code">code(3)</seealso>.</p>
+        <p>See also <seealso marker="kernel:code">
+          <c>kernel:code(3)</c></seealso>.</p>
       </desc>
     </func>
 
@@ -2527,13 +2554,13 @@ os_prompt% </pre>
 
     <func>
       <name name="localtime_to_universaltime" arity="1"/>
-      <fsummary>Converts from local to Universal Time Coordinated (UTC) date and time.</fsummary>
+      <fsummary>Convert from local to Universal Time Coordinated (UTC) date
+        and time.</fsummary>
       <desc>
         <p>Converts local date and time to Universal Time Coordinated
           (UTC), if supported by the underlying OS. Otherwise
           no conversion is done and <c><anno>Localtime</anno></c>
-          is returned.</p>
-        <p>Example:</p>
+          is returned. Example:</p>
         <pre>
 > <input>erlang:localtime_to_universaltime({{1996,11,6},{14,45,17}}).</input>
 {{1996,11,6},{13,45,17}}</pre>
@@ -2544,15 +2571,16 @@ os_prompt% </pre>
 
     <func>
       <name name="localtime_to_universaltime" arity="2"/>
-      <fsummary>Converts from local to Universal Time Coordinated (UTC) date and time.</fsummary>
+      <fsummary>Convert from local to Universal Time Coordinated (UTC) date
+        and time.</fsummary>
       <desc>
         <p>Converts local date and time to Universal Time Coordinated
           (UTC) as <c>erlang:localtime_to_universaltime/1</c>,
           but the caller decides if Daylight Saving Time is active.</p>
-        <p>If <c><anno>IsDst</anno> == true</c>, <c><anno>Localtime</anno></c> is
-          during Daylight Saving Time, if <c><anno>IsDst</anno> == false</c> it is
-          not. If <c><anno>IsDst</anno> == undefined</c>, the underlying OS can
-          guess, which is the same as calling
+        <p>If <c><anno>IsDst</anno> == true</c>, <c><anno>Localtime</anno></c>
+          is during Daylight Saving Time, if <c><anno>IsDst</anno> == false</c>
+          it is not. If <c><anno>IsDst</anno> == undefined</c>, the underlying
+          OS can guess, which is the same as calling
           <c>erlang:localtime_to_universaltime(<anno>Localtime</anno>)</c>.</p>
         <p>Examples:</p>
         <pre>
@@ -2569,24 +2597,27 @@ os_prompt% </pre>
 
     <func>
       <name name="make_ref" arity="0"/>
-      <fsummary>Returns a unique reference.</fsummary>
+      <fsummary>Return a unique reference.</fsummary>
       <desc>
-	<p>Returns a <seealso marker="doc/efficiency_guide:advanced#unique_references">unique
-	reference</seealso>. The reference is unique among
-	connected nodes.</p>
-	<warning><p>Known issue: When a node is restarted multiple
-	times with the same node name, references created
-	on a newer node can be mistaken for a reference
-	created on an older node with the same node name.</p></warning>
+        <p>Returns a
+          <seealso marker="doc/efficiency_guide:advanced#unique_references">
+          unique reference</seealso>. The reference is unique among
+          connected nodes.</p>
+        <warning>
+          <p>Known issue: When a node is restarted multiple
+            times with the same node name, references created
+            on a newer node can be mistaken for a reference
+            created on an older node with the same node name.</p>
+        </warning>
       </desc>
     </func>
 
     <func>
       <name name="make_tuple" arity="2"/>
-      <fsummary>Creates a new tuple of a given arity.</fsummary>
+      <fsummary>Create a new tuple of a specified arity.</fsummary>
       <desc>
-        <p>Creates a new tuple of the given <c><anno>Arity</anno></c>, where all
-          elements are <c><anno>InitialValue</anno></c>, for example:</p>
+        <p>Creates a new tuple of the specified <c><anno>Arity</anno></c>, where
+          all elements are <c><anno>InitialValue</anno></c>, for example:</p>
         <pre>
 > <input>erlang:make_tuple(4, []).</input>
 {[],[],[],[]}</pre>
@@ -2595,17 +2626,16 @@ os_prompt% </pre>
 
     <func>
       <name name="make_tuple" arity="3"/>
-      <fsummary>Creates a new tuple with given arity and contents.</fsummary>
+      <fsummary>Create a new tuple with specifed arity and contents.</fsummary>
       <desc>
         <p>Creates a tuple of size <c><anno>Arity</anno></c>, where each element
           has value <c><anno>DefaultValue</anno></c>, and then fills in
-	  values from <c><anno>InitList</anno></c>.
+          values from <c><anno>InitList</anno></c>.
           Each list element in <c><anno>InitList</anno></c>
-	  must be a two-tuple, where the first element is a position in the
-	  newly created tuple and the second element is any term. If a
-	  position occurs more than once in the list, the term corresponding
-	  to the last occurrence is used.</p>
-        <p>Example:</p>
+          must be a two-tuple, where the first element is a position in the
+          newly created tuple and the second element is any term. If a
+          position occurs more than once in the list, the term corresponding
+          to the last occurrence is used. Example:</p>
         <pre>
 > <input>erlang:make_tuple(5, [], [{2,ignored},{5,zz},{2,aa}]).</input>
 {{[],aa,[],[],zz}</pre>
@@ -2614,7 +2644,7 @@ os_prompt% </pre>
 
     <func>
       <name name="map_size" arity="1"/>
-      <fsummary>Returns the size of a map.</fsummary>
+      <fsummary>Return the size of a map.</fsummary>
       <desc>
         <p>Returns an integer, which is the number of key-value pairs
           in <c><anno>Map</anno></c>, for example:</p>
@@ -2627,74 +2657,75 @@ os_prompt% </pre>
 
     <func>
       <name name="match_spec_test" arity="3"/>
-      <fsummary>Test that a match specification works</fsummary>
-      <desc>
-        <p>
-          This function is a utility to test a match_spec used in calls to
-          <seealso marker="stdlib:ets#select/2">ets:select/2</seealso> and
-          <seealso marker="#trace_pattern/3">erlang:trace_pattern/3</seealso>.
-          The function both tests MatchSpec for "syntactic" correctness and
-          runs the match_spec against the object. If the match_spec contains
-          errors, the tuple {error, Errors} is returned where Errors is a list
-          of natural language descriptions of what was wrong with the match_spec.
-        </p>
-        <p>
-          If the <c><anno>Type</anno></c> is <c>table</c> the object to match
-          against should be a tuple. The function then returns
-          {ok,Result,[],Warnings} where Result is what would have been the
-          result in a real ets:select/2 call or false if the match_spec does
-          not match the object tuple.
-        </p>
-
-        <p>
-          If <c><anno>Type</anno></c> is <c>trace</c> the object to match
-          against should be a list. The function returns
-          {ok, Result, Flags, Warnings} where Result is <c>true</c> if a trace
-          message should be emitted, <c>false</c> if a trace message should not
-          be emitted or the message term to be appended to the trace message.
-          Flags is a list containing all the trace flags that will be enabled,
-          at the moment this is only <c>return_trace</c>.
-        </p>
-
-        <p>
-          This is a useful debugging and test tool, especially when writing complicated
-          match specifications.
-        </p>
-        <p>
-          See also
-          <seealso marker="stdlib:ets#test_ms/2">ets:test_ms/2</seealso>.
-        </p>
+      <fsummary>Test that a match specification works.</fsummary>
+      <desc>
+        <p>Tests a match specification used in calls to
+          <seealso marker="stdlib:ets#select/2"><c>ets:select/2</c></seealso>
+          and <seealso marker="#trace_pattern/3">
+          <c>erlang:trace_pattern/3</c></seealso>.
+          The function tests both a match specification for "syntactic"
+          correctness and runs the match specification against the object. If
+          the match specification contains errors, the tuple <c>{error,
+          Errors}</c> is returned, where <c>Errors</c> is a list of natural
+          language descriptions of what was wrong with the match
+          specification.</p>
+        <p>If <c><anno>Type</anno></c> is <c>table</c>, the object to match
+          against is to be a tuple. The function then returns
+          <c>{ok,Result,[],Warnings}</c>, where <c>Result</c> is what would
+          have been the result in a real <c>ets:select/2</c> call, or
+          <c>false</c> if the match specification does not match the object
+          tuple.</p>
+        <p>If <c><anno>Type</anno></c> is <c>trace</c>, the object to match
+          against is to be a list. The function returns
+          <c>{ok, Result, Flags, Warnings}</c>, where <c>Result</c> is one of
+          the following:</p>
+        <list type="bulleted">
+          <item><c>true</c> if a trace message is to be emitted</item>
+          <item><c>false</c> if a trace message is not to be emitted</item>
+          <item>The message term to be appended to the trace message</item>
+        </list>
+        <p><c>Flags</c> is a list containing all the trace flags to be enabled,
+          currently this is only <c>return_trace</c>.</p>
+        <p>This is a useful debugging and test tool, especially when writing
+          complicated match specifications.</p>
+        <p>See also
+          <seealso marker="stdlib:ets#test_ms/2"><c>ets:test_ms/2</c></seealso>
+          in <c>STDLIB</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="max" arity="2"/>
-      <fsummary>Returns the largest of two terms.</fsummary>
+      <fsummary>Return the largest of two terms.</fsummary>
       <desc>
         <p>Returns the largest of <c><anno>Term1</anno></c> and
           <c><anno>Term2</anno></c>.
-	  If the terms are equal, <c><anno>Term1</anno></c> is returned.</p>
+          If the terms are equal, <c><anno>Term1</anno></c> is returned.</p>
       </desc>
     </func>
 
     <func>
       <name name="md5" arity="1"/>
-      <fsummary>Computes an MD5 message digest.</fsummary>
+      <fsummary>Compute an MD5 message digest.</fsummary>
       <desc>
         <p>Computes an MD5 message digest from <c><anno>Data</anno></c>, where
           the length of the digest is 128 bits (16 bytes).
           <c><anno>Data</anno></c>
           is a binary or a list of small integers and binaries.</p>
-        <p>For more information about MD5, see RFC 1321 - The
-          MD5 Message-Digest Algorithm.</p>
-	<warning><p>The MD5 Message-Digest Algorithm is <em>not</em> considered
-	safe for code-signing or software-integrity purposes.</p></warning>
+        <p>For more information about MD5, see
+          <url href="https://www.ietf.org/rfc/rfc1321.txt">
+          RFC 1321 - The MD5 Message-Digest Algorithm</url>.</p>
+        <warning>
+          <p>The MD5 Message-Digest Algorithm is <em>not</em> considered
+            safe for code-signing or software-integrity purposes.</p>
+        </warning>
       </desc>
     </func>
 
     <func>
       <name name="md5_final" arity="1"/>
-      <fsummary>Finishes the update of an MD5 context and returns the computed MD5 message digest.</fsummary>
+      <fsummary>Finish the update of an MD5 context and return the computed
+        MD5 message digest.</fsummary>
       <desc>
         <p>Finishes the update of an MD5 <c><anno>Context</anno></c> and returns
           the computed <c>MD5</c> message digest.</p>
@@ -2703,18 +2734,19 @@ os_prompt% </pre>
 
     <func>
       <name name="md5_init" arity="0"/>
-      <fsummary>Creates an MD5 context.</fsummary>
+      <fsummary>Create an MD5 context.</fsummary>
       <desc>
-        <p>Creates an MD5 context, to be used in subsequent calls to
+        <p>Creates an MD5 context, to be used in the following calls to
           <c>md5_update/2</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="md5_update" arity="2"/>
-      <fsummary>Updates an MD5 context with data and returns a new context.</fsummary>
+      <fsummary>Update an MD5 context with data and return a new context.
+      </fsummary>
       <desc>
-        <p>Updates an MD5 <c><anno>Context</anno></c> with
+        <p>Update an MD5 <c><anno>Context</anno></c> with
           <c><anno>Data</anno></c> and returns a
           <c><anno>NewContext</anno></c>.</p>
       </desc>
@@ -2730,7 +2762,7 @@ os_prompt% </pre>
           element is a tuple <c>{Type, Size}</c>. The first element
           <c><anno>Type</anno></c> is an atom describing memory type. The second
           element <c><anno>Size</anno></c> is the memory size in bytes.</p>
-        <p>The memory types are as follows:</p>
+        <p>Memory types:</p>
         <taglist>
           <tag><c>total</c></tag>
           <item>
@@ -2782,7 +2814,7 @@ os_prompt% </pre>
           </item>
           <tag><c>ets</c></tag>
           <item>
-            <p>The total amount of memory currently allocated for ets
+            <p>The total amount of memory currently allocated for <c>ets</c>
               tables. This memory is part of the memory presented as
               <c>system</c> memory.</p>
           </item>
@@ -2790,9 +2822,9 @@ os_prompt% </pre>
           <item>
             <p>Only on 64-bit halfword emulator.
               The total amount of memory allocated in low memory areas
-	      that are restricted to less than 4 GB, although
-	      the system can have more memory.</p>
-	    <p>Can be removed in a future release of the halfword
+              that are restricted to &lt; 4 GB, although
+              the system can have more memory.</p>
+            <p>Can be removed in a future release of the halfword
               emulator.</p>
           </item>
           <tag><c>maximum</c></tag>
@@ -2802,8 +2834,9 @@ os_prompt% </pre>
               when the emulator is run with instrumentation.</p>
             <p>For information on how to run the emulator with
               instrumentation, see
-              <seealso marker="tools:instrument">instrument(3)</seealso>
-              and/or <seealso marker="erts:erl">erl(1)</seealso>.</p>
+              <seealso marker="tools:instrument">
+              <c>tools:instrument(3)</c></seealso>
+              and/or <seealso marker="erl"><c>erl(1)</c></seealso>.</p>
           </item>
         </taglist>
         <note>
@@ -2820,20 +2853,20 @@ os_prompt% </pre>
           <p>As the <c>total</c> value is the sum of <c>processes</c>
             and <c>system</c>, the error in <c>system</c> propagates
             to the <c>total</c> value.</p>
-	  <p>The different amounts of memory that are summed are
-	    <em>not</em> gathered atomically, which introduces
-	    an error in the result.</p>
+          <p>The different amounts of memory that are summed are
+            <em>not</em> gathered atomically, which introduces
+            an error in the result.</p>
         </note>
         <p>The different values have the following relation to each
           other. Values beginning with an uppercase letter is not part
           of the result.</p>
         <code type="none">
-        total = processes + system
-        processes = processes_used + ProcessesNotUsed
-        system = atom + binary + code + ets + OtherSystem
-        atom = atom_used + AtomNotUsed
-        RealTotal = processes + RealSystem
-        RealSystem = system + MissedSystem</code>
+total      = processes + system
+processes  = processes_used + ProcessesNotUsed
+system     = atom + binary + code + ets + OtherSystem
+atom       = atom_used + AtomNotUsed
+RealTotal  = processes + RealSystem
+RealSystem = system + MissedSystem</code>
         <p>More tuples in the returned list can be added in a
           future release.</p>
         <note>
@@ -2843,20 +2876,20 @@ os_prompt% </pre>
             the emulator stacks are not supposed to be included. That
             is, the <c>total</c> value is <em>not</em> supposed to be
             equal to the total size of all pages mapped to the emulator.</p>
-          <p>Furthermore, because of fragmentation and prereservation of
+          <p>Also, because of fragmentation and prereservation of
             memory areas, the size of the memory segments containing
             the dynamically allocated memory blocks can be much
             larger than the total size of the dynamically allocated
             memory blocks.</p>
         </note>
-	<note>
-	  <p>As from <c>ERTS</c> 5.6.4, <c>erlang:memory/0</c> requires that
-	    all <seealso marker="erts:erts_alloc">erts_alloc(3)</seealso>
-	    allocators are enabled (default behavior).</p>
-	</note>
+        <note>
+          <p>As from <c>ERTS</c> 5.6.4, <c>erlang:memory/0</c> requires that
+            all <seealso marker="erts:erts_alloc"><c>erts_alloc(3)</c></seealso>
+            allocators are enabled (default behavior).</p>
+        </note>
         <p>Failure: <c>notsup</c> if an
-          <seealso marker="erts:erts_alloc">erts_alloc(3)</seealso>
-	  allocator has been disabled.</p>
+          <seealso marker="erts:erts_alloc"><c>erts_alloc(3)</c></seealso>
+          allocator has been disabled.</p>
       </desc>
     </func>
 
@@ -2866,61 +2899,61 @@ os_prompt% </pre>
       <fsummary>Information about dynamically allocated memory.</fsummary>
       <type name="memory_type"/>
       <desc>
-        <p>Returns the memory size in bytes allocated for memory of
-          type <c><anno>Type</anno></c>. The argument can also be given as a list
+        <p>Returns the memory size in bytes allocated for memory of type
+          <c><anno>Type</anno></c>. The argument can also be specifed as a list
           of <c>memory_type()</c> atoms, in which case a corresponding list of
           <c>{memory_type(), Size :: integer >= 0}</c> tuples is returned.</p>
-	<note>
-	  <p>As from <c>ERTS</c> version 5.6.4,
+        <note>
+          <p>As from <c>ERTS</c> 5.6.4,
             <c>erlang:memory/1</c> requires that
-	    all <seealso marker="erts:erts_alloc">erts_alloc(3)</seealso>
-	    allocators are enabled (default behavior).</p>
-	</note>
+            all <seealso marker="erts_alloc"><c>erts_alloc(3)</c></seealso>
+            allocators are enabled (default behavior).</p>
+        </note>
         <p>Failures:</p>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	    If <c><anno>Type</anno></c> is not one of the memory types
+            If <c><anno>Type</anno></c> is not one of the memory types
             listed in the description of
-	    <seealso marker="#memory/0">erlang:memory/0</seealso>.
-	  </item>
+            <seealso marker="#memory/0"><c>erlang:memory/0</c></seealso>.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	    If <c>maximum</c> is passed as <c><anno>Type</anno></c> and
+            If <c>maximum</c> is passed as <c><anno>Type</anno></c> and
             the emulator is not run in instrumented mode.
-	  </item>
+          </item>
           <tag><c>notsup</c></tag>
           <item>
-	    If an <seealso marker="erts:erts_alloc">erts_alloc(3)</seealso>
-	    allocator has been disabled.
-	  </item>
-	</taglist>
+            If an <seealso marker="erts_alloc"><c>erts_alloc(3)</c></seealso>
+            allocator has been disabled.
+          </item>
+        </taglist>
         <p>See also
-          <seealso marker="#memory/0">erlang:memory/0</seealso>.</p>
+          <seealso marker="#memory/0"><c>erlang:memory/0</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="min" arity="2"/>
-      <fsummary>Returns the smallest of two terms.</fsummary>
+      <fsummary>Return the smallest of two terms.</fsummary>
       <desc>
         <p>Returns the smallest of <c><anno>Term1</anno></c> and
           <c><anno>Term2</anno></c>.
-	  If the terms are equal, <c><anno>Term1</anno></c> is returned.</p>
+          If the terms are equal, <c><anno>Term1</anno></c> is returned.</p>
       </desc>
     </func>
 
     <func>
       <name name="module_loaded" arity="1"/>
-      <fsummary>Checks if a module is loaded.</fsummary>
+      <fsummary>Check if a module is loaded.</fsummary>
       <desc>
         <p>Returns <c>true</c> if the module <c><anno>Module</anno></c>
           is loaded, otherwise <c>false</c>. It does not attempt to load
           the module.</p>
         <warning>
           <p>This BIF is intended for the code server (see
-            <seealso marker="kernel:code">code(3)</seealso>) and is not to be
-            used elsewhere.</p>
+            <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>)
+            and is not to be used elsewhere.</p>
         </warning>
       </desc>
     </func>
@@ -2929,7 +2962,7 @@ os_prompt% </pre>
       <name name="monitor" arity="2" clause_i="1"/>
       <name name="monitor" arity="2" clause_i="2"/>
       <name name="monitor" arity="2" clause_i="3"/>
-      <fsummary>Starts monitoring.</fsummary>
+      <fsummary>Start monitoring.</fsummary>
       <type name="registered_name"/>
       <type name="registered_process_identifier"/>
       <type name="monitor_process_identifier"/>
@@ -2937,35 +2970,39 @@ os_prompt% </pre>
       <desc>
 	<p>Sends a monitor request of type <c><anno>Type</anno></c> to the
 	  entity identified by <c><anno>Item</anno></c>. If the monitored entity
-          does not exist or when it dies, the caller of <c>monitor/2</c> will
-          be notified by a message on the following format:</p>
-        <code type="none">{Tag, <anno>MonitorRef</anno>, <anno>Type</anno>, Object, Info}</code>
-	<note><p>The monitor request is an asynchronous signal. That is, it
-	takes time before the signal reaches its destination.</p></note>
+          does not exist or it changes monitored state, the caller of
+          <c>monitor/2</c> is notified by a message on the following format:</p>
+        <code type="none">
+{Tag, <anno>MonitorRef</anno>, <anno>Type</anno>, Object, Info}</code>
+	<note>
+          <p>The monitor request is an asynchronous signal. That is, it
+	    takes time before the signal reaches its destination.</p>
+        </note>
 
         <p><c><anno>Type</anno></c> can be one of the following atoms:
           <c>process</c>, <c>port</c> or <c>time_offset</c>.</p>
 
-        <p>A monitor is triggered only once, after that it is removed from
-          both monitoring process and the monitored entity.
-          Monitors are fired when the monitored process or port terminates,
-          does not exist at the moment of creation, or if the connection to
-          it is lost. In the case with connection, we lose knowledge about
-          the fact if it still exists or not. The monitoring is also turned off
-          when <seealso marker="#demonitor/1">demonitor/1</seealso>
-          is called.</p>
-
-        <p>When monitoring by name please note, that the <c>RegisteredName</c>
-          is resolved to <c>pid()</c> or <c>port()</c> only once
-          at the moment of monitor instantiation, later changes to the name
-          registration will not affect the existing monitor.</p>
-
-        <p>When a monitor is triggered, a <c>'DOWN'</c> message that has the
-          following pattern <c>{'DOWN', MonitorRef, Type, Object, Info}</c>
-          is sent to the monitoring process.</p>
-
-        <p>In monitor message <c>MonitorRef</c> and <c>Type</c> are the same as
-          described earlier, and:</p>
+        <p>A <c>process</c> or <c>port</c> monitor is triggered only once,
+          after that it is removed from both monitoring process and
+          the monitored entity. Monitors are fired when the monitored process
+          or port terminates, does not exist at the moment of creation,
+          or if the connection to it is lost. If the connection to it is lost,
+          we do not know if it still exixts. The monitoring is also turned off
+          when <seealso marker="#demonitor/1">demonitor/1</seealso> is
+          called.</p>
+
+        <p>A <c>process</c> or <c>port</c> monitor by name
+          resolves the <c>RegisteredName</c> to <c>pid()</c> or <c>port()</c>
+          only once at the moment of monitor instantiation, later changes to
+          the name registration will not affect the existing monitor.</p>
+
+        <p>When a <c>process</c> or <c>port</c> monitor is triggered,
+          a <c>'DOWN'</c> message is sent that has the following pattern:</p>
+          <code type="none">
+{'DOWN', MonitorRef, Type, Object, Info}</code>
+
+        <p>In the monitor message <c>MonitorRef</c> and <c>Type</c> are the
+          same as described earlier, and:</p>
         <taglist>
           <tag><c>Object</c></tag>
           <item>
@@ -2992,14 +3029,14 @@ os_prompt% </pre>
           implemented), the call fails with <c>badarg</c>.</p>
         <note>
           <p>The format of the <c>'DOWN'</c> message changed in ERTS
-            version 5.2 (OTP R9B) for monitoring
+            5.2 (Erlang/OTP R9B) for monitoring
             <em>by registered name</em>. Element <c>Object</c> of
             the <c>'DOWN'</c> message could in earlier versions
             sometimes be the process identifier of the monitored process and sometimes
             be the registered name. Now element <c>Object</c> is
             always a tuple consisting of the registered name and
-            the node name. Processes on new nodes (ERTS version 5.2
-            or higher) always get <c>'DOWN'</c> messages on
+            the node name. Processes on new nodes (ERTS 5.2
+            or higher versions) always get <c>'DOWN'</c> messages on
             the new format even if they are monitoring processes on old
             nodes. Processes on old nodes always get <c>'DOWN'</c>
             messages on the old format.</p>
@@ -3008,11 +3045,11 @@ os_prompt% </pre>
         <taglist>
         <tag>Monitoring a <marker id="monitor_process"/><c>process</c></tag>
         <item>
-        <p>Creates monitor between the current process and another
-          process identified by <c><anno>Item</anno></c>, which can be a
-          <c>pid()</c> (local or remote), an atom <c>RegisteredName</c> or
-          a tuple <c>{RegisteredName, Node}</c> for a registered process,
-          located elsewhere.</p>
+          <p>Creates monitor between the current process and another
+            process identified by <c><anno>Item</anno></c>, which can be a
+            <c>pid()</c> (local or remote), an atom <c>RegisteredName</c> or
+            a tuple <c>{RegisteredName, Node}</c> for a registered process,
+            located elsewhere.</p>
         </item>
 
         <tag>Monitoring a <marker id="monitor_port"/><c>port</c></tag>
@@ -3026,62 +3063,64 @@ os_prompt% </pre>
         </item>
 
         <tag>Monitoring a
-          <marker id="monitor_time_offset"/><c>time_offset</c></tag>
+          <marker id="monitor_time_offset"/>time_offset</tag>
 	  <item>
-	    <p>Monitor changes in
-	    <seealso marker="#time_offset/0">time offset</seealso>
-	    between
-	    <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	    monotonic time</seealso> and
-	    <seealso marker="time_correction#Erlang_System_Time">Erlang
-	    system time</seealso>. There is only one valid
-	    <c><anno>Item</anno></c> in combination with the
-	    <c>time_offset <anno>Type</anno></c>, namely the atom
-	    <c>clock_service</c>. Note that the atom <c>clock_service</c> is
-	    <em>not</em> the registered name of a process. In this specific
-	    case it serves as an identifier of the runtime system internal
-	    clock service at current runtime system instance.</p>
+	    <p>Monitors changes in
+	      <seealso marker="#time_offset/0"><c>time offset</c></seealso>
+	      between
+	      <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+	      monotonic time</seealso> and
+	      <seealso marker="time_correction#Erlang_System_Time">Erlang
+	      system time</seealso>. One valid <c><anno>Item</anno></c>
+              exists in combination with the
+	      <c>time_offset <anno>Type</anno></c>, namely the atom
+	      <c>clock_service</c>. Notice that the atom <c>clock_service</c> is
+	      <em>not</em> the registered name of a process. In this
+	      case it serves as an identifier of the runtime system internal
+	      clock service at current runtime system instance.</p>
 
 	    <p>The monitor is triggered when the time offset is changed.
-	    This either if the time offset value is changed, or if the
-	    offset is changed from preliminary to final during
-	    <seealso marker="#system_flag_time_offset">finalization
-	    of the time offset</seealso> when the
-	    <seealso marker="time_correction#Single_Time_Warp_Mode">single
-	    time warp mode</seealso> is used. When a change from preliminary
-	    to final time offset is made, the monitor will be triggered once
-	    regardless of whether the time offset value was actually changed
-	    or not.</p>
+	      This either if the time offset value is changed, or if the
+	      offset is changed from preliminary to final during
+	      <seealso marker="#system_flag_time_offset">finalization
+	      of the time offset</seealso> when the
+	      <seealso marker="time_correction#Single_Time_Warp_Mode">single
+	      time warp mode</seealso> is used. When a change from preliminary
+	      to final time offset is made, the monitor is triggered once
+	      regardless of whether the time offset value was changed
+	      or not.</p>
 
 	    <p>If the runtime system is in
-	    <seealso marker="time_correction#Multi_Time_Warp_Mode">multi
-	    time warp mode</seealso>, the time offset will be changed when
-	    the runtime system detects that the
-	    <seealso marker="time_correction#OS_System_Time">OS system
-	    time</seealso> has changed. The runtime system will, however,
-	    not detect this immediately when it happens. A task checking
-	    the time offset is scheduled to execute at least once a minute,
-	    so under normal operation this should be detected within a
-	    minute, but during heavy load it might take longer time.</p>
-
-	    <p>The monitor will <em>not</em> be automatically removed
-	    after it has been triggered. That is, repeated changes of
-	    the time offset will trigger the monitor repeatedly.</p>
-
-            <p>When the monitor is triggered a <c>'CHANGE'</c> message will
-	    be sent to the monitoring process. A <c>'CHANGE'</c> message has
-	    the following pattern:</p>
-            <code type="none">{'CHANGE', MonitorRef, Type, Item, NewTimeOffset}</code>
-            <p>where <c>MonitorRef</c>, <c><anno>Type</anno></c>, and 
-	    <c><anno>Item</anno></c> are the same as described above, and
-	    <c>NewTimeOffset</c> is the new time offset.</p>
+	      <seealso marker="time_correction#Multi_Time_Warp_Mode">multi
+	      time warp mode</seealso>, the time offset is changed when
+	      the runtime system detects that the
+	      <seealso marker="time_correction#OS_System_Time">OS system
+	      time</seealso> has changed. The runtime system does, however,
+	      not detect this immediately when it occurs. A task checking
+	      the time offset is scheduled to execute at least once a minute,
+	      so under normal operation this is to be detected within a
+	      minute, but during heavy load it can take longer time.</p>
+
+	    <p>The monitor is <em>not</em> automatically removed
+	      after it has been triggered. That is, repeated changes of
+	      the time offset trigger the monitor repeatedly.</p>
+
+            <p>When the monitor is triggered a <c>'CHANGE'</c> message is
+	      sent to the monitoring process. A <c>'CHANGE'</c> message has
+	      the following pattern:</p>
+              <code type="none">
+{'CHANGE', MonitorRef, Type, Item, NewTimeOffset}</code>
+              <p>where <c>MonitorRef</c>, <c><anno>Type</anno></c>, and
+	      <c><anno>Item</anno></c> are the same as described above, and
+	      <c>NewTimeOffset</c> is the new time offset.</p>
 
 	    <p>When the <c>'CHANGE'</c> message has been received you are
-	    guaranteed not to retrieve the old time offset when calling
-	    <seealso marker="#time_offset/0"><c>erlang:time_offset()</c></seealso>.
-	    Note that you can observe the change of the time offset
-	    when calling <c>erlang:time_offset()</c> before you
-	    get the <c>'CHANGE'</c> message.</p>
+	      guaranteed not to retrieve the old time offset when calling
+	      <seealso marker="#time_offset/0">
+              <c>erlang:time_offset()</c></seealso>.
+	      Notice that you can observe the change of the time offset
+	      when calling <c>erlang:time_offset()</c> before you
+	      get the <c>'CHANGE'</c> message.</p>
 	  </item>
 	</taglist>
 
@@ -3092,20 +3131,19 @@ os_prompt% </pre>
 	<p>The monitor functionality is expected to be extended. That is,
 	  other <c><anno>Type</anno></c>s and <c><anno>Item</anno></c>s
 	  are expected to be supported in a future release.</p>
-
         <note>
           <p>If or when <c>monitor/2</c> is extended, other
-            possible values for <c>Tag</c>, <c>Object</c> and
-	    <c>Info</c> in the monitor message will be introduced.</p>
+            possible values for <c>Tag</c>, <c>Object</c>, and
+            <c>Info</c> in the monitor message will be introduced.</p>
         </note>
       </desc>
     </func>
 
     <func>
       <name name="monitor_node" arity="2"/>
-      <fsummary>Monitors the status of a node.</fsummary>
+      <fsummary>Monitor the status of a node.</fsummary>
       <desc>
-        <p>Monitors the status of the node <c><anno>Node</anno></c>.
+        <p>Monitor the status of the node <c><anno>Node</anno></c>.
           If <c><anno>Flag</anno></c>
           is <c>true</c>, monitoring is turned on. If <c><anno>Flag</anno></c>
           is <c>false</c>, monitoring is turned off.</p>
@@ -3127,12 +3165,12 @@ os_prompt% </pre>
 
     <func>
       <name name="monitor_node" arity="3"/>
-      <fsummary>Monitors the status of a node.</fsummary>
+      <fsummary>Monitor the status of a node.</fsummary>
       <desc>
         <p>Behaves as
-          <seealso marker="#monitor_node/2">monitor_node/2</seealso>
+          <seealso marker="#monitor_node/2"><c>monitor_node/2</c></seealso>
           except that it allows an
-          extra option to be given, namely <c>allow_passive_connect</c>.
+          extra option to be specified, namely <c>allow_passive_connect</c>.
           This option allows the BIF to wait the normal network connection
           time-out for the <em>monitored node</em> to connect itself,
           even if it cannot be actively connected from this node
@@ -3155,70 +3193,77 @@ os_prompt% </pre>
       <name name="monotonic_time" arity="0"/>
       <fsummary>Current Erlang monotonic time.</fsummary>
       <desc>
-	<p>Returns the current
-	<seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	monotonic time</seealso> in <c>native</c>
-	<seealso marker="#type_time_unit">time unit</seealso>. This
-	is a monotonically increasing time since some unspecified point in
-	time.</p>
-
-	<note><p>This is a
-	<seealso marker="time_correction#Monotonically_Increasing">monotonically increasing</seealso> time, but <em>not</em> a
-	<seealso marker="time_correction#Strictly_Monotonically_Increasing">strictly monotonically increasing</seealso>
-	time. That is, consecutive calls to
-	<c>erlang:monotonic_time/0</c> can produce the same result.</p>
-
-	<p>Different runtime system instances will use different
-	unspecified points in time as base for their Erlang monotonic clocks.
-	That is, it is <em>pointless</em> comparing monotonic times from
-	different runtime system instances. Different runtime system instances
-	may also place this unspecified point in time different relative
-	runtime system start. It may be placed in the future (time at start
-	is a negative value), the past (time at start is a
-	positive value), or the runtime system start (time at start is
-	zero). The monotonic time at runtime system start can be
-	retrieved by calling
-	<seealso marker="#system_info_start_time"><c>erlang:system_info(start_time)</c></seealso>.</p></note>
+        <p>Returns the current
+          <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+          monotonic time</seealso> in <c>native</c>
+          <seealso marker="#type_time_unit">time unit</seealso>. This
+          is a monotonically increasing time since some unspecified point in
+          time.</p>
+        <note>
+          <p>This is a
+            <seealso marker="time_correction#Monotonically_Increasing">
+            monotonically increasing</seealso> time, but <em>not</em> a
+            <seealso marker="time_correction#Strictly_Monotonically_Increasing">
+            strictly monotonically increasing</seealso>
+            time. That is, consecutive calls to
+            <c>erlang:monotonic_time/0</c> can produce the same result.</p>
+          <p>Different runtime system instances will use different unspecified
+            points in time as base for their Erlang monotonic clocks.
+            That is, it is <em>pointless</em> comparing monotonic times from
+            different runtime system instances. Different runtime system
+            instances can also place this unspecified point in time different
+            relative runtime system start. It can be placed in the future (time
+            at start is a negative value), the past (time at start is a
+            positive value), or the runtime system start (time at start is
+            zero). The monotonic time at runtime system start can be
+            retrieved by calling
+            <seealso marker="#system_info_start_time">
+            <c>erlang:system_info(start_time)</c></seealso>.</p>
+        </note>
       </desc>
     </func>
+
     <func>
       <name name="monotonic_time" arity="1"/>
-      <fsummary>Current Erlang monotonic time</fsummary>
+      <fsummary>Current Erlang monotonic time.</fsummary>
       <desc>
-	<p>Returns the current
-	<seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	monotonic time</seealso> converted
-	into the <c><anno>Unit</anno></c> passed as argument.</p>
-
-	<p>Same as calling
-	<seealso marker="#convert_time_unit/3"><c>erlang:convert_time_unit</c></seealso><c>(</c><seealso marker="#monotonic_time/0"><c>erlang:monotonic_time()</c></seealso><c>,
-	native, <anno>Unit</anno>)</c>
-	however optimized for commonly used <c><anno>Unit</anno></c>s.</p>
+        <p>Returns the current
+          <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+          monotonic time</seealso> converted
+          into the <c><anno>Unit</anno></c> passed as argument.</p>
+        <p>Same as calling
+          <seealso marker="#convert_time_unit/3">
+          <c>erlang:convert_time_unit</c></seealso><c>(</c><seealso
+          marker="#monotonic_time/0">
+          <c>erlang:monotonic_time()</c></seealso><c>,
+          native, <anno>Unit</anno>)</c>,
+          however optimized for commonly used <c><anno>Unit</anno></c>s.</p>
       </desc>
     </func>
+
     <func>
       <name name="nif_error" arity="1"/>
-      <fsummary>Stops execution with a given reason.</fsummary>
+      <fsummary>Stop execution with a specifed reason.</fsummary>
       <desc>
         <p>Works exactly like
-	 <seealso marker="#error/1">erlang:error/1</seealso>, but
-	 <c>Dialyzer</c> thinks that this BIF will return an arbitrary
-	 term. When used in a stub function for a NIF to generate an
-	 exception when the NIF library is not loaded, <c>Dialyzer</c>
-	 does not generate false warnings.</p>
+         <seealso marker="#error/1"><c>error/1</c></seealso>, but
+         <c>Dialyzer</c> thinks that this BIF will return an arbitrary
+         term. When used in a stub function for a NIF to generate an
+         exception when the NIF library is not loaded, <c>Dialyzer</c>
+         does not generate false warnings.</p>
       </desc>
     </func>
 
     <func>
       <name name="nif_error" arity="2"/>
-      <fsummary>Stops execution with a given reason.</fsummary>
+      <fsummary>Stop execution with a specified reason.</fsummary>
       <desc>
         <p>Works exactly like
-	 <seealso marker="#error/2">erlang:error/2</seealso>, but
-	 <c>Dialyzer</c> thinks that this BIF will return an arbitrary
-	 term. When used in a stub function for a NIF to generate an
-	 exception when the NIF library is not loaded, <c>Dialyzer</c>
-	 does not generate false warnings.</p>
+          <seealso marker="#error/2"><c>error/2</c></seealso>, but
+          <c>Dialyzer</c> thinks that this BIF will return an arbitrary
+          term. When used in a stub function for a NIF to generate an
+          exception when the NIF library is not loaded, <c>Dialyzer</c>
+          does not generate false warnings.</p>
       </desc>
     </func>
 
@@ -3258,10 +3303,10 @@ os_prompt% </pre>
       <name name="nodes" arity="1"/>
       <fsummary>All nodes of a certain type in the system.</fsummary>
       <desc>
-        <p>Returns a list of nodes according to the argument given.
-          The returned result when the argument is a list, is the list
+        <p>Returns a list of nodes according to the argument specified.
+          The returned result, when the argument is a list, is the list
           of nodes satisfying the disjunction(s) of the list elements.</p>
-        <p><c><anno>NodeType</anno></c> can be any of the following:</p>
+        <p><c><anno>NodeType</anno></c>s:</p>
         <taglist>
           <tag><c>visible</c></tag>
           <item>
@@ -3282,13 +3327,15 @@ os_prompt% </pre>
           <tag><c>known</c></tag>
           <item>
             <p>Nodes that are known to this node. That is, connected
-	    nodes and nodes referred to by process identifiers, port
-	    identifiers and references located on this node.
-	    The set of known nodes is garbage collected. Notice that
-	    this garbage collection can be delayed. For more
-	    information, see
-	    <seealso marker="erlang#system_info_delayed_node_table_gc">delayed_node_table_gc</seealso>.
-	    </p>
+              nodes and nodes referred to by process identifiers, port
+              identifiers, and references located on this node.
+              The set of known nodes is garbage collected. Notice that
+              this garbage collection can be delayed. For more
+              information, see
+              <seealso marker="erlang#system_info_delayed_node_table_gc">
+              <c>delayed_node_table_gc</c></seealso> in
+              <seealso marker="system_info/1">
+              <c>erlang:system_info/1</c></seealso>.</p>
           </item>
         </taglist>
         <p>Some equalities: <c>[node()] = nodes(this)</c>,
@@ -3302,20 +3349,22 @@ os_prompt% </pre>
       <fsummary>Elapsed time since 00:00 GMT.</fsummary>
       <type name="timestamp"/>
       <desc>
-	<warning><p><em>This function is deprecated! Do not use it!</em>
-	See the users guide chapter
-	<seealso marker="time_correction">Time and Time Correction</seealso>
-	for more information. Specifically the 
-	<seealso marker="time_correction#Dos_and_Donts">Dos and Dont's</seealso>
-	section for information on what to use instead of <c>erlang:now/0</c>.
-	</p></warning>
-        <p>Returns the tuple <c>{MegaSecs, Secs, MicroSecs}</c> which is
+        <warning>
+          <p><em>This function is deprecated. Do not use it.</em></p>
+          <p>For more information, see section
+            <seealso marker="time_correction">Time and Time Correction</seealso>
+            in the User's Guide. Specifically, section
+            <seealso marker="time_correction#Dos_and_Donts">
+            Dos and Dont's</seealso> describes what to use instead of
+            <c>erlang:now/0</c>.</p>
+        </warning>
+        <p>Returns the tuple <c>{MegaSecs, Secs, MicroSecs}</c>, which is
           the elapsed time since 00:00 GMT, January 1, 1970 (zero hour),
-          on the assumption that the underlying OS supports this.
+          if provided by the underlying OS.
           Otherwise some other point in time is chosen. It is also
-          guaranteed that subsequent calls to this BIF return
+          guaranteed that the following calls to this BIF return
           continuously increasing values. Hence, the return value from
-          <c>now()</c> can be used to generate unique time-stamps.
+          <c>erlang:now/0</c> can be used to generate unique time stamps.
           If it is called in a tight loop on a fast machine,
           the time of the node can become skewed.</p>
         <p>Can only be used to check the local time of day if
@@ -3326,28 +3375,31 @@ os_prompt% </pre>
 
     <func>
       <name name="open_port" arity="2"/>
-      <fsummary>Opens a port.</fsummary>
+      <fsummary>Open a port.</fsummary>
       <desc>
         <p>Returns a port identifier as the result of opening a
           new Erlang port. A port can be seen as an external Erlang
           process.</p>
-	<p>The name of the executable as well as the arguments
-	given in <c>cd</c>, <c>env</c>, <c>args</c>, and <c>arg0</c> are
-        subject to Unicode file name translation if the system is running
-	in Unicode file name mode. To avoid
-	translation or to force, for example UTF-8, supply the executable
-	and/or arguments as a binary in the correct
-	encoding. For details, see the module
-        <seealso marker="kernel:file">file</seealso>, the function
-	<seealso marker="kernel:file#native_name_encoding/0">file:native_name_encoding/0</seealso>, and the
-	<seealso marker="stdlib:unicode_usage">STDLIB </seealso>
-        User's Guide.</p>
-	<note><p>The characters in the name (if given as a list) can
-	only be higher than 255 if the Erlang Virtual Machine is started
-	in Unicode file name translation mode. Otherwise the name
-	of the executable is limited to the ISO-latin-1
-	character set.</p></note>
-	<p><c><anno>PortName</anno></c> can be any of the following:</p>
+        <p>The name of the executable as well as the arguments
+          specifed in <c>cd</c>, <c>env</c>, <c>args</c>, and <c>arg0</c> are
+          subject to Unicode filename translation if the system is running
+          in Unicode filename mode. To avoid
+          translation or to force, for example UTF-8, supply the executable
+          and/or arguments as a binary in the correct
+          encoding. For details, see the module
+          <seealso marker="kernel:file"><c>kernel:file</c></seealso>, the
+          function <seealso marker="kernel:file#native_name_encoding/0">
+          <c>file:native_name_encoding/0</c></seealso> in <c>Kernel</c>, and
+          the <seealso marker="stdlib:unicode_usage"><c>STDLIB</c></seealso>
+          User's Guide.</p>
+        <note>
+          <p>The characters in the name (if specified as a list) can
+            only be &gt; 255 if the Erlang virtual machine is started
+            in Unicode filename translation mode. Otherwise the name
+            of the executable is limited to the ISO Latin-1
+            character set.</p>
+        </note>
+	<p><c><anno>PortName</anno></c>s:</p>
         <taglist>
           <tag><c>{spawn, <anno>Command</anno>}</c></tag>
           <item>
@@ -3366,55 +3418,57 @@ os_prompt% </pre>
               <c>vfork</c>, setting environment variable
               <c>ERL_NO_VFORK</c> to any value causes <c>fork</c>
               to be used instead.</p>
-	      <p>For external programs, <c>PATH</c> is searched
-	      (or an equivalent method is used to find programs,
-	      depending on OS). This is done by invoking
-	      the shell on certain platforms. The first space-separated
-	      token of the command is considered as the
-	      name of the executable (or driver). This (among other
-	      things) makes this option unsuitable for running
-	      programs having spaces in file names or directory names.
-              If spaces in executable file names are desired, use
-	      <c>{spawn_executable, <anno>Command</anno>}</c> instead.</p>
+            <p>For external programs, <c>PATH</c> is searched
+              (or an equivalent method is used to find programs,
+              depending on the OS). This is done by invoking
+              the shell on certain platforms. The first space-separated
+              token of the command is considered as the
+              name of the executable (or driver). This (among other
+              things) makes this option unsuitable for running
+              programs with spaces in filenames or directory names.
+              If spaces in executable filenames are desired, use
+              <c>{spawn_executable, <anno>Command</anno>}</c> instead.</p>
           </item>
           <tag><c>{spawn_driver, <anno>Command</anno>}</c></tag>
           <item>
-	      <p>Works like <c>{spawn, <anno>Command</anno>}</c>, but demands the
-	      first (space-separated) token of the command to be the name of a
-	      loaded driver. If no driver with that name is loaded, a
-	      <c>badarg</c> error is raised.</p>
+            <p>Works like <c>{spawn, <anno>Command</anno>}</c>, but demands
+              the first (space-separated) token of the command to be the name
+              of a loaded driver. If no driver with that name is loaded, a
+              <c>badarg</c> error is raised.</p>
           </item>
           <tag><c>{spawn_executable, <anno>FileName</anno>}</c></tag>
           <item>
-	      <p>Works like <c>{spawn, <anno>FileName</anno>}</c>, but only runs
-	      external executables. <c><anno>FileName</anno></c> in its whole
-	      is used as the name of the executable, including any spaces.
-	      If arguments are to be passed, the <c><anno>PortSettings</anno></c>
-	      <c>args</c> and <c>arg0</c> can be used.</p>
-	      <p>The shell is usually not invoked to start the
-	      program, it is executed directly. <c>PATH</c> (or
+            <p>Works like <c>{spawn, <anno>FileName</anno>}</c>, but only runs
+              external executables. <c><anno>FileName</anno></c> in its whole
+              is used as the name of the executable, including any spaces.
+              If arguments are to be passed, the
+              <c><anno>PortSettings</anno></c>
+              <c>args</c> and <c>arg0</c> can be used.</p>
+            <p>The shell is usually not invoked to start the
+              program, it is executed directly. <c>PATH</c> (or
               equivalent) is not searched. To find a program
-	      in <c>PATH</c> to execute, use
-              <seealso marker="kernel:os#find_executable/1">os:find_executable/1</seealso>.</p>
-	      <p>Only if a shell script or <c>.bat</c> file is
-	      executed, the appropriate command interpreter is
-	      invoked implicitly, but there is still no
-	      command argument expansion or implicit <c>PATH</c> search.</p>
-	      <p>If <c><anno>FileName</anno></c> cannot be run, an error
-	      exception is raised, with the POSIX error code as the reason.
-	      The error reason can differ between OSs.
-	      Typically the error <c>enoent</c> is raised when an
-	      attempt is made to run a program that is not found and
-	      <c>eacces</c> is raised when the given file is not
-	      executable.</p>
+              in <c>PATH</c> to execute, use
+              <seealso marker="kernel:os#find_executable/1">
+              <c>os:find_executable/1</c></seealso>.</p>
+            <p>Only if a shell script or <c>.bat</c> file is
+              executed, the appropriate command interpreter is
+              invoked implicitly, but there is still no
+              command-argument expansion or implicit <c>PATH</c> search.</p>
+            <p>If <c><anno>FileName</anno></c> cannot be run, an error
+              exception is raised, with the POSIX error code as the reason.
+              The error reason can differ between OSs.
+              Typically the error <c>enoent</c> is raised when an
+              attempt is made to run a program that is not found and
+              <c>eacces</c> is raised when the specified file is not
+              executable.</p>
           </item>
           <tag><c>{fd, <anno>In</anno>, <anno>Out</anno>}</c></tag>
           <item>
             <p>Allows an Erlang process to access any currently opened
               file descriptors used by Erlang. The file descriptor
-              <c><anno>In</anno></c> can be used for standard input, and the file
-              descriptor <c><anno>Out</anno></c> for standard output. It is only
-              used for various servers in the Erlang OS (<c>shell</c>
+              <c><anno>In</anno></c> can be used for standard input, and the
+              file descriptor <c><anno>Out</anno></c> for standard output.
+              It is only used for various servers in the Erlang OS (<c>shell</c>
               and <c>user</c>). Hence, its use is limited.</p>
           </item>
         </taglist>
@@ -3423,7 +3477,8 @@ os_prompt% </pre>
         <taglist>
           <tag><c>{packet, <anno>N</anno>}</c></tag>
           <item>
-            <p>Messages are preceded by their length, sent in <c><anno>N</anno></c>
+            <p>Messages are preceded by their length, sent in
+              <c><anno>N</anno></c>
               bytes, with the most significant byte first. The valid values
               for <c>N</c> are 1, 2, and 4.</p>
           </item>
@@ -3436,16 +3491,16 @@ os_prompt% </pre>
           <tag><c>{line, <anno>L</anno>}</c></tag>
           <item>
             <p>Messages are delivered on a per line basis. Each line
-              (delimited by the OS-dependent new line sequence) is
+              (delimited by the OS-dependent newline sequence) is
               delivered in a single message. The message data format
               is <c>{Flag, Line}</c>, where <c>Flag</c> is
               <c>eol</c> or <c>noeol</c>, and <c>Line</c> is the
-              data delivered (without the new line sequence).</p>
+              data delivered (without the newline sequence).</p>
             <p><c><anno>L</anno></c> specifies the maximum line length in bytes.
               Lines longer than this are delivered in more than one
               message, with <c>Flag</c> set to <c>noeol</c> for all
               but the last message. If end of file is encountered
-              anywhere else than immediately following a new line
+              anywhere else than immediately following a newline
               sequence, the last line is also delivered with
               <c>Flag</c> set to <c>noeol</c>. Otherwise
               lines are delivered with <c>Flag</c> set to <c>eol</c>.</p>
@@ -3455,14 +3510,14 @@ os_prompt% </pre>
           <tag><c>{cd, <anno>Dir</anno>}</c></tag>
           <item>
             <p>Only valid for <c>{spawn, <anno>Command</anno>}</c> and
-	      <c>{spawn_executable, <anno>FileName</anno>}</c>.
+              <c>{spawn_executable, <anno>FileName</anno>}</c>.
               The external program starts using <c><anno>Dir</anno></c> as its
               working directory. <c><anno>Dir</anno></c> must be a string.</p>
           </item>
           <tag><c>{env, <anno>Env</anno>}</c></tag>
           <item>
-            <p>Only valid for <c>{spawn, <anno>Command</anno>}</c> and
-	    <c>{spawn_executable, <anno>FileName</anno>}</c>.
+            <p>Only valid for <c>{spawn, <anno>Command</anno>}</c>, and
+              <c>{spawn_executable, <anno>FileName</anno>}</c>.
               The environment of the started process is extended using
               the environment specifications in <c><anno>Env</anno></c>.</p>
             <p><c><anno>Env</anno></c> is to be a list of tuples
@@ -3473,56 +3528,58 @@ os_prompt% </pre>
               port process. Both <c><anno>Name</anno></c> and
               <c><anno>Val</anno></c> must be strings. The one
               exception is <c><anno>Val</anno></c> being the atom
-              <c>false</c> (in analogy with <c>os:getenv/1</c>), which
-              removes the environment variable.</p>
-          </item>
-	  <tag><c>{args, [ string() | binary() ]}</c></tag>
-          <item>
-	    <p>Only valid for <c>{spawn_executable, <anno>FileName</anno>}</c>
-	    and specifies arguments to the executable. Each argument
-	    is given as a separate string and (on Unix) eventually
-	    ends up as one element each in the argument vector. On
-	    other platforms, a similar behavior is mimicked.</p>
-	    <p>The arguments are not expanded by the shell before
-	      being supplied to the executable. Most notably this
-	      means that file wild card expansion does not happen.
-              To expand wild cards for the arguments, use
-	      <seealso marker="stdlib:filelib#wildcard/1">filelib:wildcard/1</seealso>.
-	      Notice that even if
-	      the program is a Unix shell script, meaning that the
-	      shell ultimately is invoked, wild card expansion
-	      does not happen, and the script is provided with the
-	      untouched arguments. On Windows, wild card expansion
-	      is always up to the program itself, therefore this is
-	      not an issue issue.</p>
-	    <p>The executable name (also known as <c>argv[0]</c>)
-	      is not to be given in this list. The proper executable name
-	      is automatically used as argv[0], where applicable.</p>
-	    <p>If you explicitly want to set the
-	      program name in the argument vector, option <c>arg0</c>
-	      can be used.</p>
-          </item>
-	  <tag><c>{arg0, string() | binary()}</c></tag>
-          <item>
-	    <p>Only valid for <c>{spawn_executable, <anno>FileName</anno>}</c>
-	    and explicitly specifies the program name argument when
-	    running an executable. This can in some circumstances,
-	    on some OSs, be desirable. How the program
-	    responds to this is highly system-dependent and no specific
-	    effect is guaranteed.</p>
-	  </item> 
+              <c>false</c> (in analogy with
+              <seealso marker="kernel:os#getenv/1"><c>os:getenv/1</c></seealso>,
+              which removes the environment variable.</p>
+          </item>
+          <tag><c>{args, [ string() | binary() ]}</c></tag>
+          <item>
+            <p>Only valid for <c>{spawn_executable, <anno>FileName</anno>}</c>
+              and specifies arguments to the executable. Each argument
+              is specified as a separate string and (on Unix) eventually
+              ends up as one element each in the argument vector. On
+              other platforms, a similar behavior is mimicked.</p>
+            <p>The arguments are not expanded by the shell before
+              they are supplied to the executable. Most notably this
+              means that file wildcard expansion does not occur.
+              To expand wildcards for the arguments, use
+              <seealso marker="stdlib:filelib#wildcard/1">
+              <c>filelib:wildcard/1</c></seealso> in <c>STDLIB</c>.
+              Notice that even if
+              the program is a Unix shell script, meaning that the
+              shell ultimately is invoked, wildcard expansion
+              does not occur, and the script is provided with the
+              untouched arguments. On Windows, wildcard expansion
+              is always up to the program itself, therefore this is
+              not an issue.</p>
+            <p>The executable name (also known as <c>argv[0]</c>)
+              is not to be specified in this list. The proper executable name
+              is automatically used as <c>argv[0]</c>, where applicable.</p>
+            <p>If you explicitly want to set the
+              program name in the argument vector, option <c>arg0</c>
+              can be used.</p>
+          </item>
+          <tag><c>{arg0, string() | binary()}</c></tag>
+          <item>
+            <p>Only valid for <c>{spawn_executable, <anno>FileName</anno>}</c>
+              and explicitly specifies the program name argument when
+              running an executable. This can in some circumstances,
+              on some OSs, be desirable. How the program
+              responds to this is highly system-dependent and no specific
+              effect is guaranteed.</p>
+          </item> 
           <tag><c>exit_status</c></tag>
           <item>
             <p>Only valid for <c>{spawn, <anno>Command</anno>}</c>, where
               <c><anno>Command</anno></c> refers to an external program, and
-	      for <c>{spawn_executable, <anno>FileName</anno>}</c>.</p>
+              for <c>{spawn_executable, <anno>FileName</anno>}</c>.</p>
             <p>When the external process connected to the port exits, a
               message of the form <c>{Port,{exit_status,Status}}</c> is
               sent to the connected process, where <c>Status</c> is the
               exit status of the external process. If the program
               aborts on Unix, the same convention is used as the shells
               do (that is, 128+signal).</p>
-            <p>If option <c>eof</c> is also given, the messages <c>eof</c>
+            <p>If option <c>eof</c> is specified also, the messages <c>eof</c>
               and <c>exit_status</c> appear in an unspecified order.</p>
             <p>If the port program closes its <c>stdout</c> without exiting,
               option <c>exit_status</c> does not work.</p>
@@ -3530,7 +3587,7 @@ os_prompt% </pre>
           <tag><c>use_stdio</c></tag>
           <item>
             <p>Only valid for <c>{spawn, <anno>Command</anno>}</c> and
-	    <c>{spawn_executable, <anno>FileName</anno>}</c>. It
+              <c>{spawn_executable, <anno>FileName</anno>}</c>. It
               allows the standard input and output (file descriptors 0
               and 1) of the spawned (Unix) process for communication
               with Erlang.</p>
@@ -3550,14 +3607,14 @@ os_prompt% </pre>
           <tag><c>overlapped_io</c></tag>
           <item>
             <p>Affects ports to external programs on Windows only. The
-	    standard input and standard output handles of the port program
-	    are, if this option is supplied, opened with flag
-	    <c>FILE_FLAG_OVERLAPPED</c>, so that the port program can
-            (and must) do
-	    overlapped I/O on its standard handles. This is not normally
-	    the case for simple port programs, but an option of value for the
-	    experienced Windows programmer. <em>On all other platforms, this
-	    option is silently discarded.</em></p>
+              standard input and standard output handles of the port program
+              are, if this option is supplied, opened with flag
+              <c>FILE_FLAG_OVERLAPPED</c>, so that the port program can
+              (and must) do
+              overlapped I/O on its standard handles. This is not normally
+              the case for simple port programs, but an option of value for the
+              experienced Windows programmer. <em>On all other platforms, this
+              option is silently discarded.</em></p>
           </item>
           <tag><c>in</c></tag>
           <item>
@@ -3582,27 +3639,28 @@ os_prompt% </pre>
           <tag><c>hide</c></tag>
           <item>
             <p>When running on Windows, suppresses creation of a new
-	      console window when spawning the port program.
-	      (This option has no effect on other platforms.)</p>
+              console window when spawning the port program.
+              (This option has no effect on other platforms.)</p>
           </item>
           <tag><c>{parallelism, Boolean}</c></tag>
           <item>
-          <marker id="open_port_parallelism"></marker>
+            <marker id="open_port_parallelism"></marker>
             <p>Sets scheduler hint for port parallelism. If set to
-            <c>true</c>, the Virtual Machine schedules port tasks;
-            when doing so, it improves parallelism in the system. If set
-            to <c>false</c>, the Virtual Machine tries to
-	    perform port tasks immediately, improving latency at the
-            expense of parallelism. The default can be set at system startup
-            by passing command-line argument
-	    <seealso marker="erl#+spp">+spp</seealso> to <c>erl(1)</c>.</p>
+              <c>true</c>, the virtual machine schedules port tasks;
+              when doing so, it improves parallelism in the system. If set
+              to <c>false</c>, the virtual machine tries to
+              perform port tasks immediately, improving latency at the
+              expense of parallelism. The default can be set at system startup
+              by passing command-line argument
+              <seealso marker="erl#+spp"><c>+spp</c></seealso> to
+              <c>erl(1)</c>.</p>
           </item>
         </taglist>
         <p>Default is <c>stream</c> for all port types and
           <c>use_stdio</c> for spawned ports.</p>
-        <p>Failure: If the port cannot be opened, the exit reason is
-	  <c>badarg</c>, <c>system_limit</c>, or the POSIX error code that
-	  most closely describes the error, or <c>einval</c> if no POSIX
+        <p>Failure: if the port cannot be opened, the exit reason is
+          <c>badarg</c>, <c>system_limit</c>, or the POSIX error code that
+          most closely describes the error, or <c>einval</c> if no POSIX
           code is appropriate:</p>
         <taglist>
           <tag><c>badarg</c></tag>
@@ -3628,11 +3686,11 @@ os_prompt% </pre>
           <item>Full file table (for the entire OS).
           </item>
           <tag><c>eacces</c></tag>
-          <item><c>Command</c> given in <c>{spawn_executable, Command}</c>
+          <item><c>Command</c> specified in <c>{spawn_executable, Command}</c>
             does not point out an executable file.
           </item>
           <tag><c>enoent</c></tag>
-          <item><c><anno>FileName</anno></c> given in
+          <item><c><anno>FileName</anno></c> specified in
             <c>{spawn_executable, <anno>FileName</anno>}</c>
             does not point out an existing file.
           </item>
@@ -3642,13 +3700,12 @@ os_prompt% </pre>
           errors arising when sending messages to it are reported to
           the owning process using signals of the form
           <c>{'EXIT', Port, PosixCode}</c>. For the possible values of
-          <c>PosixCode</c>, see the
-          <seealso marker="kernel:file">file(3)</seealso>
-          manual page in <c>Kernel</c>.</p>
-	  <p>The maximum number of ports that can be open at the same
+          <c>PosixCode</c>, see
+          <seealso marker="kernel:file"><c>kernel:file(3)</c></seealso>.</p>
+        <p>The maximum number of ports that can be open at the same
           time can be configured by passing command-line flag
-	  <seealso marker="erl#max_ports"><c>+Q</c></seealso> to
-	  <c>erl(1)</c>.</p>
+          <seealso marker="erl#max_ports"><c>+Q</c></seealso> to
+          <c>erl(1)</c>.</p>
       </desc>
     </func>
 
@@ -3663,7 +3720,7 @@ os_prompt% </pre>
           The function returns a hash value for
           <c><anno>Term</anno></c> within the range
           <c>1..<anno>Range</anno></c>. The maximum value for
-	  <c><anno>Range</anno></c> is 2^32.</p>
+          <c><anno>Range</anno></c> is 2^32.</p>
         <p>This BIF can be used instead of the old deprecated BIF
           <c>erlang:hash/2</c>, as it calculates better hashes for
           all data types, but consider using <c>phash2/1,2</c> instead.</p>
@@ -3681,9 +3738,9 @@ os_prompt% </pre>
           the same Erlang term regardless of machine architecture and
           <c>ERTS</c> version (the BIF was introduced in <c>ERTS</c> 5.2).
           The function returns a hash value for
-	  <c><anno>Term</anno></c> within the range
-	  <c>0..<anno>Range</anno>-1</c>. The maximum value for
-	  <c><anno>Range</anno></c> is 2^32. When without argument
+          <c><anno>Term</anno></c> within the range
+          <c>0..<anno>Range</anno>-1</c>. The maximum value for
+          <c><anno>Range</anno></c> is 2^32. When without argument
           <c><anno>Range</anno></c>, a value in the range
           0..2^27-1 is returned.</p>
         <p>This BIF is always to be used for hashing terms. It
@@ -3703,14 +3760,14 @@ os_prompt% </pre>
           representation of <c><anno>Pid</anno></c>.</p>
         <warning>
           <p>This BIF is intended for debugging and is not to be used
-	  in application programs.</p>
+            in application programs.</p>
         </warning>
       </desc>
     </func>
 
     <func>
       <name name="port_call" arity="3"/>
-      <fsummary>Performs a synchronous call to a port with term data.</fsummary>
+      <fsummary>Perform a synchronous call to a port with term data.</fsummary>
       <desc>
         <p>Performs a synchronous call to a port. The meaning of
           <c><anno>Operation</anno></c> and <c><anno>Data</anno></c>
@@ -3728,87 +3785,84 @@ os_prompt% </pre>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Port</anno></c> is not an identifier of an open port,
-	     or the registered name of an open port. If the calling
-	     process was previously linked to the closed port,
-	     identified by <c><anno>Port</anno></c>, the exit signal
-	     from the port is guaranteed to be delivered before this
-	     <c>badarg</c> exception occurs.
-	  </item>
+            If <c><anno>Port</anno></c> is not an identifier of an open port,
+            or the registered name of an open port. If the calling
+            process was previously linked to the closed port,
+            identified by <c><anno>Port</anno></c>, the exit signal
+            from the port is guaranteed to be delivered before this
+            <c>badarg</c> exception occurs.
+            </item>
           <tag><c>badarg</c></tag>
-	  <item>
-	     If <c><anno>Operation</anno></c> does not fit in a 32-bit integer.
-	  </item>
+          <item>
+            If <c><anno>Operation</anno></c> does not fit in a 32-bit integer.
+          </item>
           <tag><c>badarg</c></tag>
-	  <item>
-	     If the port driver does not support synchronous control
-	     operations.
-	  </item>
+          <item>
+            If the port driver does not support synchronous control operations.
+          </item>
           <tag><c>badarg</c></tag>
-	  <item>
-	     If the port driver so decides for any reason (probably
-	     something wrong with <c><anno>Operation</anno></c>
-             or <c><anno>Data</anno></c>).
-	  </item>
-	</taglist>
+          <item>
+            If the port driver so decides for any reason (probably
+            something wrong with <c><anno>Operation</anno></c>
+            or <c><anno>Data</anno></c>).
+          </item>
+        </taglist>
       </desc>
     </func>
 
     <func>
       <name name="port_close" arity="1"/>
-      <fsummary>Closes an open port.</fsummary>
-      <desc>
-        <p>Closes an open port. Roughly the same as
-          <c><anno>Port</anno> ! {self(), close}</c> except for the error behavior
-          (see the following), being synchronous, and that the port does
-	  <em>not</em> reply with <c>{Port, closed}</c>. Any process can
-	  close a port with <c>port_close/1</c>, not only the port owner
-	  (the connected process). If the calling process is linked to
+      <fsummary>Close an open port.</fsummary>
+      <desc>
+        <p>Closes an open port. Roughly the same as <c><anno>Port</anno> !
+          {self(), close}</c> except for the error behavior
+          (see below), being synchronous, and that the port does
+          <em>not</em> reply with <c>{Port, closed}</c>. Any process can
+          close a port with <c>port_close/1</c>, not only the port owner
+          (the connected process). If the calling process is linked to
           the port identified by <c><anno>Port</anno></c>, the exit
-	  signal from the port is guaranteed to be delivered before
-	  <c>port_close/1</c> returns.</p> 
+          signal from the port is guaranteed to be delivered before
+          <c>port_close/1</c> returns.</p> 
         <p>For comparison: <c><anno>Port</anno> ! {self(), close}</c>
-	  only fails with <c>badarg</c> if <c><anno>Port</anno></c> does
-	  not refer to a port or a process. If <c><anno>Port</anno></c>
-	  is a closed port, nothing happens. If <c><anno>Port</anno></c>
+          only fails with <c>badarg</c> if <c><anno>Port</anno></c> does
+          not refer to a port or a process. If <c><anno>Port</anno></c>
+          is a closed port, nothing happens. If <c><anno>Port</anno></c>
           is an open port and the calling process is the port owner,
-	  the port replies with <c>{Port, closed}</c> when all buffers
-	  have been flushed and the port really closes. If the calling
-	  process is not the port owner, the <em>port owner</em> fails
-	  with <c>badsig</c>.</p> 
+          the port replies with <c>{Port, closed}</c> when all buffers
+          have been flushed and the port really closes. If the calling
+          process is not the port owner, the <em>port owner</em> fails
+          with <c>badsig</c>.</p> 
         <p>Notice that any process can close a port using
           <c><anno>Port</anno> ! {PortOwner, close}</c> as if it itself was
           the port owner, but the reply always goes to the port owner.</p>
-	<p>As from OTP R16, <c><anno>Port</anno> ! {PortOwner, close}</c> is truly
-	   asynchronous. Notice that this operation has always been
-	   documented as an asynchronous operation, while the underlying
-	   implementation has been synchronous. <c>port_close/1</c> is
-	   however still fully synchronous. This because of its error
-	   behavior.</p>
-        <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not an identifier
-           of an open port, or the registered name of an open port.
-	   If the calling process was previously linked to the closed
-	   port, identified by <c><anno>Port</anno></c>, the exit
-	   signal from the port is guaranteed to be delivered before
-	   this <c>badarg</c> exception occurs.</p>
+        <p>As from Erlang/OTP R16,
+          <c><anno>Port</anno> ! {PortOwner, close}</c> is truly
+          asynchronous. Notice that this operation has always been
+          documented as an asynchronous operation, while the underlying
+          implementation has been synchronous. <c>port_close/1</c> is
+          however still fully synchronous because of its error behavior.</p>
+        <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not an
+          identifier of an open port, or the registered name of an open port.
+          If the calling process was previously linked to the closed
+          port, identified by <c><anno>Port</anno></c>, the exit
+          signal from the port is guaranteed to be delivered before
+          this <c>badarg</c> exception occurs.</p>
       </desc>
     </func>
 
     <func>
       <name name="port_command" arity="2"/>
-      <fsummary>Sends data to a port.</fsummary>
+      <fsummary>Send data to a port.</fsummary>
       <desc>
         <p>Sends data to a port. Same as
-          <c><anno>Port</anno> ! {PortOwner, {command, Data}}</c> except
-          for the error
-          behavior and being synchronous (see the following). Any process
-	  can send data to a port with <c>port_command/2</c>, not only the
-	  port owner (the connected process).</p>
-        <p>For comparison: <c><anno>Port</anno> ! {PortOwner, {command, Data}}</c>
-          only fails with <c>badarg</c> if <c><anno>Port</anno></c>
-	  does not refer to a port or a process. If
-	  <c><anno>Port</anno></c> is a closed port, the data message
-	  disappears 
+          <c><anno>Port</anno> ! {PortOwner, {command, Data}}</c> except for
+          the error behavior and being synchronous (see below). Any process
+          can send data to a port with <c>port_command/2</c>, not only the
+          port owner (the connected process).</p>
+        <p>For comparison: <c><anno>Port</anno> ! {PortOwner, {command,
+          Data}}</c> only fails with <c>badarg</c> if <c><anno>Port</anno></c>
+          does not refer to a port or a process. If <c><anno>Port</anno></c> is
+          a closed port, the data message disappears 
           without a sound. If <c><anno>Port</anno></c> is open and the calling
           process is not the port owner, the <em>port owner</em> fails
           with <c>badsig</c>. The port owner fails with <c>badsig</c>
@@ -3816,57 +3870,58 @@ os_prompt% </pre>
         <p>Notice that any process can send to a port using
           <c><anno>Port</anno> ! {PortOwner, {command, <anno>Data</anno>}}</c>
           as if it itself was the port owner.</p>
-	<p>If the port is busy, the calling process is suspended
-	   until the port is not busy any more.</p>
-	<p>As from OTP-R16, <c><anno>Port</anno> ! {PortOwner, {command, Data}}</c>
-	   is truly asynchronous. Notice that this operation has always been
-	   documented as an asynchronous operation, while the underlying
-	   implementation has been synchronous. <c>port_command/2</c> is
-	   however still fully synchronous. This because of its error
-	   behavior.</p>
+        <p>If the port is busy, the calling process is suspended
+          until the port is not busy any more.</p>
+        <p>As from Erlang/OTP R16,
+          <c><anno>Port</anno> ! {PortOwner, {command, Data}}</c>
+          is truly asynchronous. Notice that this operation has always been
+          documented as an asynchronous operation, while the underlying
+          implementation has been synchronous. <c>port_command/2</c> is
+          however still fully synchronous because of its error behavior.</p>
         <p>Failures:</p>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Port</anno></c> is not an identifier of an open
-	     port, or the registered name of an open port. If the
-	     calling process was previously linked to the closed port,
-	     identified by <c><anno>Port</anno></c>, the exit signal
-	     from the port is guaranteed to be delivered before this
-	     <c>badarg</c> exception occurs.
-	  </item>
+            <p>If <c><anno>Port</anno></c> is not an identifier of an open
+              port, or the registered name of an open port. If the
+              calling process was previously linked to the closed port,
+              identified by <c><anno>Port</anno></c>, the exit signal
+              from the port is guaranteed to be delivered before this
+              <c>badarg</c> exception occurs.</p>
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Data</anno></c> is an invalid I/O list.
-	  </item>
-	</taglist>
+            <p>If <c><anno>Data</anno></c> is an invalid I/O list.</p>
+          </item>
+        </taglist>
       </desc>
     </func>
 
     <func>
       <name name="port_command" arity="3"/>
-      <fsummary>Sends data to a port.</fsummary>
+      <fsummary>Send data to a port.</fsummary>
       <desc>
         <p>Sends data to a port. <c>port_command(Port, Data, [])</c>
-	  equals <c>port_command(Port, Data)</c>.</p>
-	<p>If the port command is aborted, <c>false</c> is returned,
-	   otherwise <c>true</c>.</p>
-	<p>If the port is busy, the calling process is suspended
-	   until the port is not busy any more.</p>
-        <p>The following <c><anno>Option</anno></c>s are valid:</p>
+          equals <c>port_command(Port, Data)</c>.</p>
+        <p>If the port command is aborted, <c>false</c> is returned,
+          otherwise <c>true</c>.</p>
+        <p>If the port is busy, the calling process is suspended
+          until the port is not busy anymore.</p>
+        <p><c><anno>Option</anno></c>s:</p>
         <taglist>
           <tag><c>force</c></tag>
           <item>The calling process is not suspended if the port is
-	        busy, instead the port command is forced through. The
-		call fails with a <c>notsup</c> exception if the
-		driver of the port does not support this. For more
-		information, see driver flag
-		<seealso marker="driver_entry#driver_flags"><![CDATA[ERL_DRV_FLAG_SOFT_BUSY]]></seealso>.
+            busy, instead the port command is forced through. The
+            call fails with a <c>notsup</c> exception if the
+            driver of the port does not support this. For more
+            information, see driver flag
+            <seealso marker="driver_entry#driver_flags">
+            <c>![CDATA[ERL_DRV_FLAG_SOFT_BUSY]]</c></seealso>.
           </item>
           <tag><c>nosuspend</c></tag>
           <item>The calling process is not suspended if the port is
-	        busy, instead the port command is aborted and
-		<c>false</c> is returned. 
+            busy, instead the port command is aborted and
+            <c>false</c> is returned. 
           </item>
         </taglist>
         <note>
@@ -3876,34 +3931,34 @@ os_prompt% </pre>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Port</anno></c> is not an identifier of an open
-	     port, or the registered name of an open port. If the
-	     calling process was previously linked to the closed port,
-	     identified by <c><anno>Port</anno></c>, the exit signal
-	     from the port is guaranteed to be delivered before this
-	     <c>badarg</c> exception occurs.
-	  </item>
+            If <c><anno>Port</anno></c> is not an identifier of an open
+            port, or the registered name of an open port. If the
+            calling process was previously linked to the closed port,
+            identified by <c><anno>Port</anno></c>, the exit signal
+            from the port is guaranteed to be delivered before this
+            <c>badarg</c> exception occurs.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Data</anno></c> is an invalid I/O list.
-	  </item>
+            If <c><anno>Data</anno></c> is an invalid I/O list.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	    If <c><anno>OptionList</anno></c> is an invalid option list.
-	  </item>
+          If <c><anno>OptionList</anno></c> is an invalid option list.
+          </item>
           <tag><c>notsup</c></tag>
           <item>
-	    If option <c>force</c> has been passed, but the
-	    driver of the port does not allow forcing through
-	    a busy port.
-	  </item>
-	</taglist>
+            If option <c>force</c> has been passed, but the
+            driver of the port does not allow forcing through
+            a busy port.
+          </item>
+        </taglist>
       </desc>
     </func>
 
     <func>
       <name name="port_connect" arity="2"/>
-      <fsummary>Sets the owner of a port.</fsummary>
+      <fsummary>Set the owner of a port.</fsummary>
       <desc>
         <p>Sets the port owner (the connected port) to <c><anno>Pid</anno></c>.
           Roughly the same as
@@ -3911,14 +3966,14 @@ os_prompt% </pre>
           except for the following:</p>
         <list type="bulleted">
           <item>
-            <p>The error behavior differs, see the following.</p>
+            <p>The error behavior differs, see below.</p>
           </item>
           <item>
             <p>The port does <em>not</em> reply with
               <c>{Port,connected}</c>.</p>
           </item>
           <item>
-            <p><c>port_connect/1</c> is synchronous, see the following.</p>
+            <p><c>port_connect/1</c> is synchronous, see below.</p>
           </item>
           <item>
             <p>The new port owner gets linked to the port.</p>
@@ -3930,7 +3985,7 @@ os_prompt% </pre>
           <c>port_connect/2</c>.</p>
         <p>For comparison:
           <c><anno>Port</anno> ! {self(), {connect, <anno>Pid</anno>}}</c>
-	  only fails with <c>badarg</c> if <c><anno>Port</anno></c>
+          only fails with <c>badarg</c> if <c><anno>Port</anno></c>
           does not refer to a port or a process. If
           <c><anno>Port</anno></c> is a closed port, nothing happens.
           If <c><anno>Port</anno></c>
@@ -3940,40 +3995,39 @@ os_prompt% </pre>
           the port, while the new is not. If <c><anno>Port</anno></c> is an open
           port and the calling process is not the port owner,
           the <em>port owner</em> fails with <c>badsig</c>. The port
-          owner fails with <c>badsig</c> also if <c><anno>Pid</anno></c> is not an
-          existing local process identifier.</p>
+          owner fails with <c>badsig</c> also if <c><anno>Pid</anno></c> is not
+          an existing local process identifier.</p>
         <p>Notice that any process can set the port owner using
           <c><anno>Port</anno> ! {PortOwner, {connect, <anno>Pid</anno>}}</c>
           as if it itself was the port owner, but the reply always goes to
           the port owner.</p>
-	<p>As from OTP-R16,
-           <c><anno>Port</anno> ! {PortOwner, {connect, <anno>Pid</anno>}}</c> is
-	   truly asynchronous. Notice that this operation has always been
-	   documented as an asynchronous operation, while the underlying
-	   implementation has been synchronous. <c>port_connect/2</c> is
-	   however still fully synchronous. This because of its error
-	   behavior.</p>
+        <p>As from Erlang/OTP R16,
+          <c><anno>Port</anno> ! {PortOwner, {connect, <anno>Pid</anno>}}</c>
+          is truly asynchronous. Notice that this operation has always been
+          documented as an asynchronous operation, while the underlying
+          implementation has been synchronous. <c>port_connect/2</c> is
+          however still fully synchronous because of its error behavior.</p>
         <p>Failures:</p>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Port</anno></c> is not an identifier of an open port, or
-	     the registered name of an open port. If the calling
-	     process was previously linked to the closed port,
-	     identified by <c><anno>Port</anno></c>, the exit signal
-	     from the port is guaranteed to be delivered before this
-	     <c>badarg</c> exception occurs.
-	  </item>
+            If <c><anno>Port</anno></c> is not an identifier of an open port,
+            or the registered name of an open port. If the calling
+            process was previously linked to the closed port,
+            identified by <c><anno>Port</anno></c>, the exit signal
+            from the port is guaranteed to be delivered before this
+            <c>badarg</c> exception occurs.
+          </item>
           <tag><c>badarg</c></tag>
-	  <item>If process identified by <c>Pid</c> is not an existing
-	  local process.</item>
-	</taglist>
+          <item>If the process identified by <c>Pid</c> is not an existing
+            local process.</item>
+        </taglist>
       </desc>
     </func>
 
     <func>
       <name name="port_control" arity="3"/>
-      <fsummary>Performs a synchronous control operation on a port.</fsummary>
+      <fsummary>Perform a synchronous control operation on a port.</fsummary>
       <desc>
         <p>Performs a synchronous control operation on a port.
           The meaning of <c><anno>Operation</anno></c> and
@@ -3987,25 +4041,24 @@ os_prompt% </pre>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Port</anno></c> is not an open port or the registered
-             name of an open port.
-	  </item>
+            If <c><anno>Port</anno></c> is not an open port or the registered
+            name of an open port.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	     If <c><anno>Operation</anno></c> cannot fit in a 32-bit integer.
-	  </item>
+            If <c><anno>Operation</anno></c> cannot fit in a 32-bit integer.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	    If the port driver does not support synchronous control
-            operations.
-	  </item>
+            If the port driver does not support synchronous control operations.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	    If the port driver so decides for any reason (probably
+            If the port driver so decides for any reason (probably
             something wrong with <c><anno>Operation</anno></c> or
             <c><anno>Data</anno></c>).
-	  </item>
-	</taglist>
+          </item>
+        </taglist>
       </desc>
     </func>
 
@@ -4017,11 +4070,11 @@ os_prompt% </pre>
           <c><anno>Port</anno></c>, or <c>undefined</c> if the port is not open.
           The order of the tuples is undefined, and all the
           tuples are not mandatory.
-	  If the port is closed and the calling process
-	  was previously linked to the port, the exit signal from the
-	  port is guaranteed to be delivered before <c>port_info/1</c>
-	  returns <c>undefined</c>.</p>
-	<p>The result contains information about the following
+          If the port is closed and the calling process
+          was previously linked to the port, the exit signal from the
+          port is guaranteed to be delivered before <c>port_info/1</c>
+          returns <c>undefined</c>.</p>
+        <p>The result contains information about the following
           <c>Item</c>s:</p>
         <list type="bulleted">
           <item><c>registered_name</c> (if the port has a registered
@@ -4034,9 +4087,9 @@ os_prompt% </pre>
           <item><c>output</c></item>
         </list>
         <p>For more information about the different <c>Item</c>s, see
-	<seealso marker="#port_info/2">port_info/2</seealso>.</p>
+          <seealso marker="#port_info/2"><c>port_info/2</c></seealso>.</p>
         <p>Failure: <c>badarg</c> if <c>Port</c> is not a local port
-	identifier, or an atom.</p>
+          identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4044,15 +4097,15 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="1"/>
       <fsummary>Information about the connected process of a port.</fsummary>
       <desc>
-	<p><c><anno>Pid</anno></c> is the process identifier of the process
-	connected to the port.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Pid</anno></c> is the process identifier of the process
+          connected to the port.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4060,15 +4113,15 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="2"/>
       <fsummary>Information about the internal index of a port.</fsummary>
       <desc>
-	<p><c><anno>Index</anno></c> is the internal index of the port. This
-	index can be used to separate ports.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Index</anno></c> is the internal index of the port. This
+          index can be used to separate ports.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4076,15 +4129,15 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="3"/>
       <fsummary>Information about the input of a port.</fsummary>
       <desc>
-	<p><c><anno>Bytes</anno></c> is the total number of bytes
-	read from the port.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Bytes</anno></c> is the total number of bytes
+          read from the port.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4092,15 +4145,15 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="4"/>
       <fsummary>Information about the links of a port.</fsummary>
       <desc>
-	<p><c><anno>Pids</anno></c> is a list of the process identifiers
-	of the processes that the port is linked to.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Pids</anno></c> is a list of the process identifiers
+          of the processes that the port is linked to.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4108,7 +4161,7 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="5"/>
       <fsummary>Information about the locking of a port.</fsummary>
       <desc>
-	<p><c><anno>Locking</anno></c> is one of the following:</p>
+        <p><c><anno>Locking</anno></c> is one of the following:</p>
         <list type="bulleted">
           <item><c>false</c> (emulator without SMP support)</item>
           <item><c>port_level</c> (port-specific locking)</item>
@@ -4116,13 +4169,13 @@ os_prompt% </pre>
         </list>
         <p>Notice that these results are highly implementation-specific
           and can change in a future release.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4130,17 +4183,17 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="6"/>
       <fsummary>Information about the memory size of a port.</fsummary>
       <desc>
-	<p><c><anno>Bytes</anno></c> is the total number of
-	bytes allocated for this port by the runtime system. The
-	port itself can have allocated memory that is not
-	included in <c><anno>Bytes</anno></c>.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Bytes</anno></c> is the total number of
+          bytes allocated for this port by the runtime system. The
+          port itself can have allocated memory that is not
+          included in <c><anno>Bytes</anno></c>.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4148,15 +4201,15 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="7"/>
       <fsummary>Information about the monitors of a port.</fsummary>
       <desc>
-	<p><c><anno>Monitors</anno></c> represent processes that this port
-	monitors.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Monitors</anno></c> represent processes monitored by
+          this port.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4180,15 +4233,15 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="9"/>
       <fsummary>Information about the name of a port.</fsummary>
       <desc>
-	<p><c><anno>Name</anno></c> is the command name set by
-	<seealso marker="#open_port/2">open_port/2</seealso>.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Name</anno></c> is the command name set by
+          <seealso marker="#open_port/2"><c>open_port/2</c></seealso>.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4196,18 +4249,18 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="10"/>
       <fsummary>Information about the OS pid of a port.</fsummary>
       <desc>
-	<p><c><anno>OsPid</anno></c> is the process identifier (or equivalent)
-	of an OS process created with
-	<seealso marker="#open_port/2">open_port({spawn | spawn_executable,
-	Command}, Options)</seealso>. If the port is not the result of spawning
-	an OS process, the value is <c>undefined</c>.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>OsPid</anno></c> is the process identifier (or equivalent)
+          of an OS process created with
+          <seealso marker="#open_port/2"><c>open_port({spawn | spawn_executable,
+          Command}, Options)</c></seealso>. If the port is not the result of
+          spawning an OS process, the value is <c>undefined</c>.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4215,18 +4268,18 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="11"/>
       <fsummary>Information about the output of a port.</fsummary>
       <desc>
-	<p><c><anno>Bytes</anno></c> is the total number of bytes written
-	to the port from Erlang processes using
-	<seealso marker="#port_command/2">port_command/2</seealso>,
-	<seealso marker="#port_command/3">port_command/3</seealso>,
-	or <c><anno>Port</anno> ! {Owner, {command, Data}</c>.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Bytes</anno></c> is the total number of bytes written
+          to the port from Erlang processes using
+          <seealso marker="#port_command/2"><c>port_command/2</c></seealso>,
+          <seealso marker="#port_command/3"><c>port_command/3</c></seealso>,
+          or <c><anno>Port</anno> ! {Owner, {command, Data}</c>.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4234,10 +4287,10 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="12"/>
       <fsummary>Information about the parallelism hint of a port.</fsummary>
       <desc>
-	<p><c><anno>Boolean</anno></c> corresponds to the port parallelism
-	hint being used by this port. For more information, see option
-	<seealso marker="#open_port_parallelism">parallelism</seealso>
-	of <seealso marker="#open_port/2">open_port/2</seealso>.</p>
+        <p><c><anno>Boolean</anno></c> corresponds to the port parallelism
+          hint used by this port. For more information, see option
+          <seealso marker="#open_port_parallelism"><c>parallelism</c></seealso>
+          of <seealso marker="#open_port/2"><c>open_port/2</c></seealso>.</p>
       </desc>
     </func>
 
@@ -4245,16 +4298,16 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="13"/>
       <fsummary>Information about the queue size of a port.</fsummary>
       <desc>
-	<p><c><anno>Bytes</anno></c> is the total number
-	of bytes queued by the port using the <c>ERTS</c> driver queue
-	implementation.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>Bytes</anno></c> is the total number
+          of bytes queued by the port using the <c>ERTS</c> driver queue
+          implementation.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4262,15 +4315,16 @@ os_prompt% </pre>
       <name name="port_info" arity="2" clause_i="14"/>
       <fsummary>Information about the registered name of a port.</fsummary>
       <desc>
-	<p><c><anno>RegisteredName</anno></c> is the registered name of
-	the port. If the port has no registered name, <c>[]</c> is returned.</p>
-	<p>If the port identified by <c><anno>Port</anno></c> is not open,
-	<c>undefined</c> is returned. If the port is closed and the
-	calling process was previously linked to the port, the exit
-	signal from the port is guaranteed to be delivered before
-	<c>port_info/2</c> returns <c>undefined</c>.</p>
+        <p><c><anno>RegisteredName</anno></c> is the registered name of
+          the port. If the port has no registered name, <c>[]</c> is
+          returned.</p>
+        <p>If the port identified by <c><anno>Port</anno></c> is not open,
+          <c>undefined</c> is returned. If the port is closed and the
+          calling process was previously linked to the port, the exit
+          signal from the port is guaranteed to be delivered before
+          <c>port_info/2</c> returns <c>undefined</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Port</anno></c> is not a local
-	port identifier, or an atom.</p>
+          port identifier, or an atom.</p>
       </desc>
     </func>
 
@@ -4282,24 +4336,24 @@ os_prompt% </pre>
           representation of the port identifier <c><anno>Port</anno></c>.</p>
         <warning>
           <p>This BIF is intended for debugging. It is not to be used
-	  in application programs.</p>
+            in application programs.</p>
         </warning>
       </desc>
     </func>
 
     <func>
       <name name="ports" arity="0"/>
-      <fsummary>Lists all existing ports.</fsummary>
+      <fsummary>List all existing ports.</fsummary>
       <desc>
-	<p>Returns a list of port identifiers corresponding to all the
-	ports existing on the local node.</p>
-	<p>Notice that an exiting port exists, but is not open.</p>
+        <p>Returns a list of port identifiers corresponding to all the
+          ports existing on the local node.</p>
+        <p>Notice that an exiting port exists, but is not open.</p>
       </desc>
     </func>
 
     <func>
       <name name="pre_loaded" arity="0"/>
-      <fsummary>Lists all pre-loaded modules.</fsummary>
+      <fsummary>List all preloaded modules.</fsummary>
       <desc>
         <p>Returns a list of Erlang modules that are preloaded in
           the system. As all loading of code is done through the file
@@ -4310,12 +4364,13 @@ os_prompt% </pre>
 
     <func>
       <name name="process_display" arity="2"/>
-      <fsummary>Writes information about a local process on standard error.</fsummary>
+      <fsummary>Write information about a local process on standard error.
+      </fsummary>
       <desc>
         <p>Writes information about the local process <c><anno>Pid</anno></c> on
           standard error. The only allowed value for the atom
-          <c><anno>Type</anno></c> is <c>backtrace</c>, which shows the contents of
-          the call stack, including information about the call chain, with
+          <c><anno>Type</anno></c> is <c>backtrace</c>, which shows the contents
+          of the call stack, including information about the call chain, with
           the current function printed first. The format of the output
           is not further defined.</p>
       </desc>
@@ -4323,7 +4378,7 @@ os_prompt% </pre>
 
     <func>
       <name name="process_flag" arity="2" clause_i="1"/>
-      <fsummary>Sets process flag <c>trap_exit</c> for the calling process.</fsummary>
+      <fsummary>Set process flag trap_exit for the calling process.</fsummary>
       <desc>
         <p>When <c>trap_exit</c> is set to <c>true</c>, exit signals
           arriving to a process are converted to <c>{'EXIT', From, Reason}</c>
@@ -4334,13 +4389,14 @@ os_prompt% </pre>
           linked processes. Application processes are normally
           not to trap exits.</p>
         <p>Returns the old value of the flag.</p>
-        <p>See also <seealso marker="#exit/2">exit/2</seealso>.</p>
+        <p>See also <seealso marker="#exit/2"><c>exit/2</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="process_flag" arity="2" clause_i="2"/>
-      <fsummary>Sets process flag <c>error_handler</c> for the calling process.</fsummary>
+      <fsummary>Set process flag error_handler for the calling process.
+      </fsummary>
       <desc>
         <p>Used by a process to redefine the error handler
           for undefined function calls and undefined registered
@@ -4348,13 +4404,14 @@ os_prompt% </pre>
           as code auto-loading depends on the correct
           operation of the error handling module.</p>
         <p>Returns the old value of the flag.</p>
+        <marker id="process_flag_min_heap_size"/>
       </desc>
     </func>
 
-    <marker id="process_flag_min_heap_size"/>
     <func>
       <name name="process_flag" arity="2" clause_i="3"/>
-      <fsummary>Sets process flag <c>min_heap_size</c> for the calling process.</fsummary>
+      <fsummary>Set process flag min_heap_size for the calling process.
+      </fsummary>
       <desc>
         <p>Changes the minimum heap size for the calling process.</p>
         <p>Returns the old value of the flag.</p>
@@ -4363,90 +4420,79 @@ os_prompt% </pre>
 
     <func>
       <name name="process_flag" arity="2" clause_i="4"/>
-      <fsummary>Sets process flag <c>min_bin_vheap_size</c> for the calling process.</fsummary>
+      <fsummary>Set process flag min_bin_vheap_size for the calling process.
+      </fsummary>
       <desc>
         <p>Changes the minimum binary virtual heap size for the calling
           process.</p>
         <p>Returns the old value of the flag.</p>
       </desc>
     </func>
+
     <marker id="process_flag_max_heap_size"/>
     <func>
       <name name="process_flag" arity="2" clause_i="5"/>
-      <fsummary>Sets process flag <c>max_heap_size</c> for the calling process.</fsummary>
+      <fsummary>Set process flag max_heap_size for the calling process.
+      </fsummary>
       <type name="max_heap_size"/>
       <desc>
-        <p>
-          This flag sets the maximum heap size for the calling process.
+        <p>This flag sets the maximum heap size for the calling process.
           If <c><anno>MaxHeapSize</anno></c> is an integer, the system default
           values for <c>kill</c> and <c>error_logger</c> are used.
         </p>
         <taglist>
           <tag><c>size</c></tag>
           <item>
-            <p>
-              The maximum size in words of the process. If set to zero, the
-              heap size limit is disabled. Badarg will be thrown if the value is
-              smaller than
-              <seealso marker="#process_flag_min_heap_size"><c>min_heap_size</c></seealso>.
-              The size check is only done when a garbage collection is triggered.
-            </p>
-            <p>
-              <c>size</c> is the entire heap of the process when garbage collection
-              is triggered, this includes all generational heaps, the process stack, 
+            <p>The maximum size in words of the process. If set to zero, the
+              heap size limit is disabled. <c>badarg</c> is be thrown if the
+              value is smaller than <seealso marker="#process_flag_min_heap_size">
+              <c>min_heap_size</c></seealso>. The size check is only done when
+              a garbage collection is triggered.</p>
+            <p><c>size</c> is the entire heap of the process when garbage collection
+              is triggered. This includes all generational heaps, the process stack, 
               any <seealso marker="#process_flag_message_queue_data">
-              messages that are considered to be part of the heap</seealso> and any
-              extra memory that the garbage collector needs during collection.
-            </p>
-            <p>
-              <c>size</c> is the same as can be retrieved using
+              messages that are considered to be part of the heap</seealso>, and any
+              extra memory that the garbage collector needs during collection.</p>
+            <p><c>size</c> is the same as can be retrieved using
               <seealso marker="#process_info_total_heap_size">
                 <c>erlang:process_info(Pid, total_heap_size)</c></seealso>,
-                or by adding <c>heap_block_size</c>, <c>old_heap_block_size</c>
-                and <c>mbuf_size</c> from <seealso marker="#process_info_garbage_collection_info">
-                <c>erlang:process_info(Pid, garbage_collection_info)</c></seealso>.
-            </p>
+              or by adding <c>heap_block_size</c>, <c>old_heap_block_size</c>
+              and <c>mbuf_size</c> from <seealso marker="#process_info_garbage_collection_info">
+                <c>erlang:process_info(Pid, garbage_collection_info)</c></seealso>.</p>
           </item>
           <tag><c>kill</c></tag>
           <item>
-            <p>
-              When set to <c>true</c> the runtime system will send an
+            <p>When set to <c>true</c>, the runtime system sends an
               untrappable exit signal with reason <c>kill</c> to the process
               if the maximum heap size is reached. The garbage collection
-              that triggered the <c>kill</c> will not be completed, instead the
-              process will exit as soon as is possible. When set to <c>false</c>
-              no exit signal will be sent to the process, instead it will
-              continue executing.
-            </p>
-            <p>
-              If <c>kill</c> is not defined in the map
+              that triggered the <c>kill</c> is not completed, instead the
+              process exits as soon as possible. When set to <c>false</c>,
+              no exit signal is sent to the process, instead it continues
+              executing.</p>
+            <p>If <c>kill</c> is not defined in the map,
               the system default will be used. The default system default
-              is <c>true</c>. It can be changed by either the erl
-              <seealso marker="erl#+hmaxk">+hmaxk</seealso> option,
-              or <seealso marker="#system_flag_max_heap_size"><c>
-              erlang:system_flag(max_heap_size, MaxHeapSize)</c></seealso>.
-            </p>
+              is <c>true</c>. It can be changed by either option
+              <seealso marker="erl#+hmaxk">+hmaxk</seealso> in <c>erl(1)</c>,
+              or <seealso marker="#system_flag_max_heap_size">
+              <c>erlang:system_flag(max_heap_size, MaxHeapSize)</c></seealso>.</p>
           </item>
           <tag><c>error_logger</c></tag>
           <item>
-            <p>
-              When set to <c>true</c> the runtime system will send a
-              message to the current <seealso marker="kernel:error_logger"><c>error_logger</c></seealso>
+            <p>When set to <c>true</c>, the runtime system sends a
+              message to the current <seealso marker="kernel:error_logger">
+              <c>error_logger</c></seealso>
               containing details about the process when the maximum
-              heap size is reached. One <c>error_logger</c> report will
-              be sent each time the limit is reached.
-            </p>
-            <p>
-              If <c>error_logger</c> is not defined in the map the system
-              default will be used. The default system default is <c>true</c>.
-              It can be changed by either the erl <seealso marker="erl#+hmaxel">+hmaxel</seealso>
-              option, or <seealso marker="#system_flag_max_heap_size"><c>
-              erlang:system_flag(max_heap_size, MaxHeapSize)</c></seealso>.
-            </p>
+              heap size is reached. One <c>error_logger</c> report is sent
+              each time the limit is reached.</p>
+            <p>If <c>error_logger</c> is not defined in the map, the system
+              default is used. The default system default is <c>true</c>.
+              It can be changed by either the option
+              <seealso marker="erl#+hmaxel">+hmaxel</seealso> int <c>erl(1)</c>,
+              or <seealso marker="#system_flag_max_heap_size">
+              <c>erlang:system_flag(max_heap_size, MaxHeapSize)</c></seealso>.</p>
           </item>
         </taglist>
-        <p>
-          The heap size of a process is quite hard to predict, especially the
+        <p>The heap size of a process is quite hard to predict, especially the
           amount of memory that is used during the garbage collection. When
           contemplating using this option, it is recommended to first run
           it in production with <c>kill</c> set to <c>false</c> and inspect
@@ -4456,62 +4502,57 @@ os_prompt% </pre>
         </p>
       </desc>
     </func>
+
     <marker id="process_flag_message_queue_data"/>
     <func>
       <name name="process_flag" arity="2" clause_i="6"/>
-      <fsummary>Set process flag <c>message_queue_data</c> for the calling process</fsummary>
+      <fsummary>Set process flag message_queue_data for the calling process.
+      </fsummary>
       <type name="message_queue_data"/>
       <desc>
-	<p>This flag determines how messages in the message queue
-	are stored. When the flag is:</p>
+        <p>This flag determines how messages in the message queue
+          are stored, as follows:</p>
         <taglist>
           <tag><c>off_heap</c></tag>
-	  <item>
-            <p>
-	    <em>All</em> messages in the message queue will be stored
-	    outside of the process heap. This implies that <em>no</em>
-	    messages in the message queue will be part of a garbage
-	    collection of the process.
-	  </p></item>
+          <item>
+            <p><em>All</em> messages in the message queue will be stored
+              outside of the process heap. This implies that <em>no</em>
+              messages in the message queue will be part of a garbage
+              collection of the process.</p>
+          </item>
           <tag><c>on_heap</c></tag>
-	  <item>
-            <p>
-	    All messages in the message queue will eventually be
-	    placed on heap. They may however temporarily be stored
-	    off heap. This is how messages always have been stored
-	    up until ERTS version 8.0.
-	  </p></item>
+          <item>
+            <p>All messages in the message queue will eventually be
+              placed on heap. They can however temporarily be stored
+              off heap. This is how messages always have been stored
+              up until <c>ERTS</c> 8.0.</p>
+          </item>
         </taglist>
-	<p>
-	  The default <c>message_queue_data</c> process flag is determined
-	  by the <seealso marker="erl#+hmqd"><c>+hmqd</c></seealso>
-	  <c>erl</c> command line argument.
-	</p>
-	<p>
-	  If the process potentially may get a hugh amount of messages,
-	  you are recommended to set the flag to <c>off_heap</c>. This
-	  since a garbage collection with lots of messages placed on
-	  the heap may become extremly expensive and the process may
-	  consume large amounts of memory. Performance of the
-	  actual message passing is however generally better when not
-	  using the <c>off_heap</c> flag.
-	</p>
-	<p>
-	  When changing this flag messages will be moved. This work
-	  has been initiated but not completed when this function
-	  call returns.
-	</p>
+        <p>The default <c>message_queue_data</c> process flag is determined
+          by command-line argument <seealso marker="erl#+hmqd">
+          <c>+hmqd</c></seealso> in <c>erl(1)</c>.</p>
+        <p>If the process potentially can get many messages,
+          you are advised to set the flag to <c>off_heap</c>. This
+          because a garbage collection with many messages placed on
+          the heap can become extremly expensive and the process can
+          consume large amounts of memory. Performance of the
+          actual message passing is however generally better when not
+          using flag <c>off_heap</c>.</p>
+        <p>When changing this flag messages will be moved. This work
+          has been initiated but not completed when this function
+          call returns.</p>
         <p>Returns the old value of the flag.</p>
       </desc>
     </func>
+
     <func>
       <name name="process_flag" arity="2" clause_i="7"/>
-      <fsummary>Sets process flag <c>priority</c> for the calling process.</fsummary>
+      <fsummary>Set process flag priority for the calling process.</fsummary>
       <type name="priority_level"/>
       <desc>
         <p><marker id="process_flag_priority"></marker>
           Sets the process priority. <c><anno>Level</anno></c> is an atom.
-          There are four priority levels: <c>low</c>,
+          Four priority levels exist: <c>low</c>,
           <c>normal</c>, <c>high</c>, and <c>max</c>. Default
           is <c>normal</c>.</p>
         <note>
@@ -4525,23 +4566,23 @@ os_prompt% </pre>
           <c>low</c> are interleaved. Processes on priority
           <c>low</c> are selected for execution less
           frequently than processes on priority <c>normal</c>.</p>
-        <p>When there are runnable processes on priority <c>high</c>,
+        <p>When runnable processes on priority <c>high</c> exist,
           no processes on priority <c>low</c> or <c>normal</c> are
-          selected for execution. Notice however, that this does
+          selected for execution. Notice however that this does
           <em>not</em> mean that no processes on priority <c>low</c>
-          or <c>normal</c> can run when there are processes
-          running on priority <c>high</c>. On the runtime
+          or <c>normal</c> can run when processes
+          are running on priority <c>high</c>. On the runtime
           system with SMP support, more processes can be running
-          in parallel than processes on priority <c>high</c>, that is,
+          in parallel than processes on priority <c>high</c>. That is,
           a <c>low</c> and a <c>high</c> priority process can
           execute at the same time.</p>
-        <p>When there are runnable processes on priority <c>max</c>,
+        <p>When runnable processes on priority <c>max</c> exist,
           no processes on priority <c>low</c>, <c>normal</c>, or
           <c>high</c> are selected for execution. As with priority
           <c>high</c>, processes on lower priorities can
           execute in parallel with processes on priority <c>max</c>.</p>
-        <p>Scheduling is preemptive. Regardless of priority, a process
-          is preempted when it has consumed more than a certain number
+        <p>Scheduling is pre-emptive. Regardless of priority, a process
+          is pre-empted when it has consumed more than a certain number
           of reductions since the last time it was selected for
           execution.</p>
         <note>
@@ -4557,7 +4598,7 @@ os_prompt% </pre>
           take this into account and handle such scenarios by
           yourself.</p>
         <p>Making calls from a <c>high</c> priority process into code
-          that you have no control over can cause the <c>high</c>
+          that you has no control over can cause the <c>high</c>
           priority process to wait for a process with lower
           priority. That is, effectively decreasing the priority of the
           <c>high</c> priority process during the call. Even if this
@@ -4571,8 +4612,8 @@ os_prompt% </pre>
           <em>especially</em> priority <c>high</c>. A
           process on priority <c>high</c> is only
           to perform work for short periods. Busy looping for
-          long periods in a <c>high</c> priority process does
-          most likely cause problems, as important OTP servers
+          long periods in a <c>high</c> priority process causes
+          most likely problems, as important OTP servers
           run on priority <c>normal</c>.</p>
         <p>Returns the old value of the flag.</p>
       </desc>
@@ -4580,10 +4621,10 @@ os_prompt% </pre>
 
     <func>
       <name name="process_flag" arity="2" clause_i="8"/>
-      <fsummary>Sets process flag <c>save_calls</c> for the calling process.</fsummary>
+      <fsummary>Set process flag save_calls for the calling process.</fsummary>
       <desc>
         <p><c><anno>N</anno></c> must be an integer in the interval 0..10000.
-          If <c><anno>N</anno></c> is greater than 0, call saving is made
+          If <c><anno>N</anno></c> &gt; 0, call saving is made
           active for the
           process. This means that information about the <c><anno>N</anno></c>
           most recent global function calls, BIF calls, sends, and
@@ -4594,12 +4635,12 @@ os_prompt% </pre>
           explicitly mentioned. Only a fixed amount of information
           is saved, as follows:</p>
         <list type="bulleted">
-          <item>A tuple <c>{Module, Function, Arity}</c> for
-            function calls</item>
-          <item> The atoms <c>send</c>, <c>'receive'</c>, and
+          <item><p>A tuple <c>{Module, Function, Arity}</c> for
+            function calls</p></item>
+          <item><p>The atoms <c>send</c>, <c>'receive'</c>, and
             <c>timeout</c> for sends and receives (<c>'receive'</c>
             when a message is received and <c>timeout</c> when a
-            receive times out)</item>
+            receive times out)</p></item>
         </list>
         <p>If <c>N</c> = 0,
           call saving is disabled for the process, which is the
@@ -4611,7 +4652,7 @@ os_prompt% </pre>
 
     <func>
       <name name="process_flag" arity="2" clause_i="9"/>
-      <fsummary>Sets process flag <c>sensitive</c> for the calling process.</fsummary>
+      <fsummary>Set process flag sensitive for the calling process.</fsummary>
       <desc>
         <p>Sets or clears flag <c>sensitive</c> for the current process.
           When a process has been marked as sensitive by calling
@@ -4621,13 +4662,13 @@ os_prompt% </pre>
         <p>Features that are disabled include (but are not limited to)
           the following:</p>
         <list type="bulleted">
-          <item>Tracing: Trace flags can still be set for the process,
+          <item><p>Tracing. Trace flags can still be set for the process,
             but no trace messages of any kind are generated. (If flag
             <c>sensitive</c> is turned off, trace messages are again
-            generated if any trace flags are set.)</item>
-          <item>Sequential tracing: The sequential trace token is
+            generated if any trace flags are set.)</p></item>
+          <item><p>Sequential tracing. The sequential trace token is
             propagated as usual, but no sequential trace messages are
-            generated.</item>
+            generated.</p></item>
         </list>
         <p><c>process_info/1,2</c> cannot be used to read out the
           message queue or the process dictionary (both are returned
@@ -4637,19 +4678,19 @@ os_prompt% </pre>
           are omitted.</p>
         <p>If <c>{save_calls,N}</c> has been set for the process, no
           function calls are saved to the call saving list.
-          (The call saving list is not cleared. Furthermore, send, receive,
-          and timeout events are still added to the list.)</p>
+          (The call saving list is not cleared. Also, send, receive,
+          and time-out events are still added to the list.)</p>
         <p>Returns the old value of the flag.</p>
       </desc>
     </func>
 
     <func>
       <name name="process_flag" arity="3"/>
-      <fsummary>Sets process flags for a process.</fsummary>
+      <fsummary>Set process flags for a process.</fsummary>
       <desc>
         <p>Sets certain flags for the process <c><anno>Pid</anno></c>,
           in the same manner as
-          <seealso marker="#process_flag/2">process_flag/2</seealso>.
+          <seealso marker="#process_flag/2"><c>process_flag/2</c></seealso>.
           Returns the old value of the flag. The valid values for
           <c><anno>Flag</anno></c> are only a subset of those allowed in
           <c>process_flag/2</c>, namely <c>save_calls</c>.</p>
@@ -4664,46 +4705,46 @@ os_prompt% </pre>
       <type name="process_info_result_item"/>
       <type name="priority_level"/>
       <type name="stack_item"/>
-      <type name="max_heap_size" />
-      <type name="message_queue_data" />
+      <type name="max_heap_size"/>
+      <type name="message_queue_data"/>
       <desc>
         <p>Returns a list containing <c><anno>InfoTuple</anno></c>s with
-	  miscellaneous information about the process identified by
-	  <c>Pid</c>, or <c>undefined</c> if the process is not alive.</p>
-	<p>The order of the <c><anno>InfoTuple</anno></c>s is undefined and
-	  all <c><anno>InfoTuple</anno></c>s are not mandatory.
+          miscellaneous information about the process identified by
+          <c>Pid</c>, or <c>undefined</c> if the process is not alive.</p>
+        <p>The order of the <c><anno>InfoTuple</anno></c>s is undefined and
+          all <c><anno>InfoTuple</anno></c>s are not mandatory.
           The <c><anno>InfoTuple</anno></c>s
-	  part of the result can be changed without prior notice.</p>
-	<p>The <c><anno>InfoTuple</anno></c>s with the following items
-	  are part of the result:</p>
+          part of the result can be changed without prior notice.</p>
+        <p>The <c><anno>InfoTuple</anno></c>s with the following items
+          are part of the result:</p>
         <list type="bulleted">
           <item><c>current_function</c></item>
           <item><c>initial_call</c></item>
           <item><c>status</c></item>
-	  <item><c>message_queue_len</c></item>
+          <item><c>message_queue_len</c></item>
           <item><c>messages</c></item>
           <item><c>links</c></item>
-	  <item><c>dictionary</c></item>
+          <item><c>dictionary</c></item>
           <item><c>trap_exit</c></item>
           <item><c>error_handler</c></item>
-	  <item><c>priority</c></item>
+          <item><c>priority</c></item>
           <item><c>group_leader</c></item>
           <item><c>total_heap_size</c></item>
-	  <item><c>heap_size</c></item>
+          <item><c>heap_size</c></item>
           <item><c>stack_size</c></item>
           <item><c>reductions</c></item>
-	  <item><c>garbage_collection</c></item>
+          <item><c>garbage_collection</c></item>
         </list>
         <p>If the process identified by <c><anno>Pid</anno></c> has a
           registered name,
-	  also an <c><anno>InfoTuple</anno></c> with item <c>registered_name</c>
-	  appears.</p>
-	<p>For information about specific <c><anno>InfoTuple</anno></c>s, see
-          <seealso marker="#process_info/2">process_info/2</seealso>.</p>
+          also an <c><anno>InfoTuple</anno></c> with item <c>registered_name</c>
+          is included.</p>
+        <p>For information about specific <c><anno>InfoTuple</anno></c>s, see
+          <seealso marker="#process_info/2"><c>process_info/2</c></seealso>.</p>
         <warning>
           <p>This BIF is intended for <em>debugging only</em>. For
-            all other purposes, use
-	    <seealso marker="#process_info/2">process_info/2</seealso>.</p>
+            all other purposes, use <seealso marker="#process_info/2">
+            <c>process_info/2</c></seealso>.</p>
         </warning>
         <p>Failure: <c>badarg</c> if <c><anno>Pid</anno></c> is not a
           local process.</p>
@@ -4718,38 +4759,39 @@ os_prompt% </pre>
       <type name="process_info_result_item"/>
       <type name="stack_item"/>
       <type name="priority_level"/>
-      <type name="max_heap_size" />
-      <type name="message_queue_data" />
+      <type name="max_heap_size"/>
+      <type name="message_queue_data"/>
       <desc>
         <p>Returns information about the process identified by
-           <c><anno>Pid</anno></c>, as specified by
-           <c><anno>Item</anno></c> or <c><anno>ItemList</anno></c>.
-           Returns <c>undefined</c> if the process is not alive.</p>
-	<p>If the process is alive and a single <c><anno>Item</anno></c>
-           is given, the returned value is the corresponding
-	   <c><anno>InfoTuple</anno></c>, unless <c>Item =:= registered_name</c>
-	   and the process has no registered name. In this case,
-	   <c>[]</c> is returned. This strange behavior is because of
-	   historical reasons, and is kept for backward compatibility.</p>
-	<p>If <c><anno>ItemList</anno></c> is given, the result is
-	   <c><anno>InfoTupleList</anno></c>.
-           The <c><anno>InfoTuple</anno></c>s in
-	   <c><anno>InfoTupleList</anno></c> appear with the corresponding
-	   <c><anno>Item</anno></c>s in the same order as the
-           <c><anno>Item</anno></c>s appeared
-	   in <c><anno>ItemList</anno></c>. Valid <c><anno>Item</anno></c>s can
-           appear multiple times in <c><anno>ItemList</anno></c>.</p>
-	<note><p>If <c>registered_name</c> is part of <c><anno>ItemList</anno></c>
-	          and the process has no name registered a
-		  <c>{registered_name, []}</c>, <c><anno>InfoTuple</anno></c>
-                  <em>will</em> appear in the resulting
-                  <c><anno>InfoTupleList</anno></c>. This
-		  behavior is different when a single
-		  <c>Item =:= registered_name</c> is given, and when
-		  <c>process_info/1</c> is used.</p>
-	</note>
-	<p>The following <c><anno>InfoTuple</anno></c>s with corresponding
-	   <c><anno>Item</anno></c>s are valid:</p>
+          <c><anno>Pid</anno></c>, as specified by
+          <c><anno>Item</anno></c> or <c><anno>ItemList</anno></c>.
+          Returns <c>undefined</c> if the process is not alive.</p>
+        <p>If the process is alive and a single <c><anno>Item</anno></c>
+          is specified, the returned value is the corresponding
+          <c><anno>InfoTuple</anno></c>, unless <c>Item =:= registered_name</c>
+          and the process has no registered name. In this case,
+          <c>[]</c> is returned. This strange behavior is because of
+          historical reasons, and is kept for backward compatibility.</p>
+        <p>If <c><anno>ItemList</anno></c> is specified, the result is
+          <c><anno>InfoTupleList</anno></c>.
+          The <c><anno>InfoTuple</anno></c>s in
+          <c><anno>InfoTupleList</anno></c> are included with the corresponding
+          <c><anno>Item</anno></c>s in the same order as the
+          <c><anno>Item</anno></c>s were included
+          in <c><anno>ItemList</anno></c>. Valid <c><anno>Item</anno></c>s can
+          be included multiple times in <c><anno>ItemList</anno></c>.</p>
+        <note>
+          <p>If <c>registered_name</c> is part of <c><anno>ItemList</anno></c>
+            and the process has no name registered, a
+            <c>{registered_name, []}</c>, <c><anno>InfoTuple</anno></c>
+            <em>will</em> be included in the resulting
+            <c><anno>InfoTupleList</anno></c>. This
+            behavior is different when a single
+            <c>Item =:= registered_name</c> is specified, and when
+            <c>process_info/1</c> is used.</p>
+        </note>
+        <p>Valid <c><anno>InfoTuple</anno></c>s with corresponding
+          <c><anno>Item</anno></c>s:</p>
         <taglist>
           <tag><c>{backtrace, <anno>Bin</anno>}</c></tag>
           <item>
@@ -4762,15 +4804,15 @@ os_prompt% </pre>
           <tag><c>{binary, <anno>BinInfo</anno>}</c></tag>
           <item>
             <p><c><anno>BinInfo</anno></c> is a list containing miscellaneous
-              information about binaries currently being referred to by this
+              information about binaries currently referred to by this
               process. This <c><anno>InfoTuple</anno></c> can be changed or
               removed without prior notice.</p>
           </item>
           <tag><c>{catchlevel, <anno>CatchLevel</anno>}</c></tag>
           <item>
             <p><c><anno>CatchLevel</anno></c> is the number of currently active
-	    catches in this process. This <c><anno>InfoTuple</anno></c> can be
-	    changed or removed without prior notice.</p>
+              catches in this process. This <c><anno>InfoTuple</anno></c> can be
+              changed or removed without prior notice.</p>
           </item>
           <tag><c>{current_function, {<anno>Module</anno>,
             <anno>Function</anno>, Arity}}</c></tag>
@@ -4786,14 +4828,15 @@ os_prompt% </pre>
             <p><c><anno>Module</anno></c>, <c><anno>Function</anno></c>,
               <c><anno>Arity</anno></c> is
               the current function call of the process.
-	      <c><anno>Location</anno></c> is a list of two-tuples describing the
-	      location in the source code.</p>
+              <c><anno>Location</anno></c> is a list of two-tuples describing
+              the location in the source code.</p>
           </item>
           <tag><c>{current_stacktrace, <anno>Stack</anno>}</c></tag>
           <item>
             <p>Returns the current call stack back-trace (<em>stacktrace</em>)
               of the process. The stack has the same format as returned by
-	      <seealso marker="#get_stacktrace/0">erlang:get_stacktrace/0</seealso>.</p>
+              <seealso marker="#get_stacktrace/0">
+              <c>erlang:get_stacktrace/0</c></seealso>.</p>
           </item>
           <tag><c>{dictionary, <anno>Dictionary</anno>}</c></tag>
           <item>
@@ -4807,9 +4850,9 @@ os_prompt% </pre>
           <tag><c>{garbage_collection, <anno>GCInfo</anno>}</c></tag>
           <item>
             <p><c><anno>GCInfo</anno></c> is a list containing miscellaneous
-	       information about garbage collection for this process.
-	       The content of <c><anno>GCInfo</anno></c> can be changed without
-	       prior notice.</p>
+              information about garbage collection for this process.
+              The content of <c><anno>GCInfo</anno></c> can be changed without
+              prior notice.</p>
           </item>
           <tag>
             <marker id="process_info_garbage_collection_info"/>
@@ -4817,24 +4860,22 @@ os_prompt% </pre>
           </tag>
           <item>
             <p><c><anno>GCInfo</anno></c> is a list containing miscellaneous
-	       detailed information about garbage collection for this process.
-	       The content of <c><anno>GCInfo</anno></c> can be changed without
-	       prior notice.
-               See <seealso marker="#gc_minor_start">gc_minor_start</seealso> in
-               <seealso marker="#trace/3">erlang:trace/3</seealso> for details about
-               what each item means.
-            </p>
+              detailed information about garbage collection for this process.
+              The content of <c><anno>GCInfo</anno></c> can be changed without
+              prior notice. For details about the meaning of each item, see
+              <seealso marker="#gc_minor_start"><c>gc_minor_start</c></seealso>
+              in <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>.</p>
           </item>
           <tag><c>{group_leader, <anno>GroupLeader</anno>}</c></tag>
           <item>
-            <p><c><anno>GroupLeader</anno></c> is group leader for the I/O of
-              the process.</p>
+            <p><c><anno>GroupLeader</anno></c> is the group leader for the I/O
+              of the process.</p>
           </item>
           <tag><c>{heap_size, <anno>Size</anno>}</c></tag>
           <item>
-            <p><c><anno>Size</anno></c> is the size in words of the youngest heap
-              generation of the process. This generation includes
-	      the process stack. This information is highly
+            <p><c><anno>Size</anno></c> is the size in words of the youngest
+              heap generation of the process. This generation includes
+              the process stack. This information is highly
               implementation-dependent, and can change if the
               implementation changes.</p>
           </item>
@@ -4848,29 +4889,29 @@ os_prompt% </pre>
           </item>
           <tag><c>{links, <anno>PidsAndPorts</anno>}</c></tag>
           <item>
-            <p><c><anno>PidsAndPorts</anno></c> is a list of process identifiers 
-	    and port identifiers, with processes or ports to which the process
-	    has a link.</p>
+            <p><c><anno>PidsAndPorts</anno></c> is a list of process identifiers
+              and port identifiers, with processes or ports to which the process
+              has a link.</p>
           </item>
           <tag><c>{last_calls, false|Calls}</c></tag>
           <item>
             <p>The value is <c>false</c> if call saving is not active
-              for the process (see
-              <seealso marker="#process_flag/3">process_flag/3</seealso>).
+              for the process (see <seealso marker="#process_flag/3">
+              <c>process_flag/3</c></seealso>).
               If call saving is active, a list is returned, in which
               the last element is the most recent called.</p>
           </item>
           <tag><c>{memory, <anno>Size</anno>}</c></tag>
           <item>
-            <p><c><anno>Size</anno></c> is the size in bytes of the process. This
-              includes call stack, heap, and internal structures.</p>
+            <p><c><anno>Size</anno></c> is the size in bytes of the process.
+              This includes call stack, heap, and internal structures.</p>
           </item>
           <tag><c>{message_queue_len, <anno>MessageQueueLen</anno>}</c></tag>
           <item>
             <p><c><anno>MessageQueueLen</anno></c> is the number of messages
-              currently in the message queue of the process. This is
-              the length of the list <c><anno>MessageQueue</anno></c> returned as
-              the information item <c>messages</c> (see the following).</p>
+              currently in the message queue of the process. This is the
+              length of the list <c><anno>MessageQueue</anno></c> returned as
+              the information item <c>messages</c> (see below).</p>
           </item>
           <tag><c>{messages, <anno>MessageQueue</anno>}</c></tag>
           <item>
@@ -4913,36 +4954,37 @@ os_prompt% </pre>
           </item>
           <tag><c>{message_queue_data, <anno>MQD</anno>}</c></tag>
           <item>
-            <p>Returns the current state of the <c>message_queue_data</c>
-	    process flag. <c><anno>MQD</anno></c> is either <c>off_heap</c>,
-	    or <c>on_heap</c>. For more information, see the
-	    documentation of
-            <seealso marker="#process_flag_message_queue_data"><c>process_flag(message_queue_data,
-	    MQD)</c></seealso>.</p>
+            <p>Returns the current state of process flag
+              <c>message_queue_data</c>. <c><anno>MQD</anno></c> is either
+              <c>off_heap</c> or <c>on_heap</c>. For more
+              information, see the documentation of
+              <seealso marker="#process_flag_message_queue_data">
+              <c>process_flag(message_queue_data, MQD)</c></seealso>.</p>
           </item>
           <tag><c>{priority, <anno>Level</anno>}</c></tag>
           <item>
             <p><c><anno>Level</anno></c> is the current priority level for
-	      the process. For more information on priorities, see
-              <seealso marker="#process_flag_priority">process_flag(priority,
-              Level)</seealso>.</p>
+              the process. For more information on priorities, see
+              <seealso marker="#process_flag_priority">
+              <c>process_flag(priority, Level)</c></seealso>.</p>
           </item>
           <tag><c>{reductions, <anno>Number</anno>}</c></tag>
           <item>
-            <p><c><anno>Number</anno></c> is the number of reductions executed by
-              the process.</p>
+            <p><c><anno>Number</anno></c> is the number of reductions executed
+              by the process.</p>
           </item>
           <tag><c>{registered_name, <anno>Atom</anno>}</c></tag>
           <item>
-            <p><c><anno>Atom</anno></c> is the registered name of the process. If
-              the process has no registered name, this tuple is not
+            <p><c><anno>Atom</anno></c> is the registered process name.
+              If the process has no registered name, this tuple is not
               present in the list.</p>
           </item>
-          <tag><c>{sequential_trace_token, [] | <anno>SequentialTraceToken</anno>}</c></tag>
+          <tag><c>{sequential_trace_token, [] |
+            <anno>SequentialTraceToken</anno>}</c></tag>
           <item>
             <p><c><anno>SequentialTraceToken</anno></c> is the sequential trace
-            token for the process. This <c><anno>InfoTuple</anno></c> can be
-            changed or removed without prior notice.</p>
+              token for the process. This <c><anno>InfoTuple</anno></c> can be
+              changed or removed without prior notice.</p>
           </item>
           <tag><c>{stack_size, <anno>Size</anno>}</c></tag>
           <item>
@@ -4951,9 +4993,9 @@ os_prompt% </pre>
           </item>
           <tag><c>{status, <anno>Status</anno>}</c></tag>
           <item>
-            <p><c><anno>Status</anno></c> is the status of the process and is one
-              of the following:</p>
-	    <list type="bulleted">
+            <p><c><anno>Status</anno></c> is the status of the process and is
+              one of the following:</p>
+            <list type="bulleted">
               <item><c>exiting</c></item>
               <item><c>garbage_collecting</c></item>
               <item><c>waiting</c> (for a message)</item>
@@ -4961,46 +5003,44 @@ os_prompt% </pre>
               <item><c>runnable</c> (ready to run, but another process is
                 running)</item>
               <item><c>suspended</c> (suspended on a "busy" port
-                or by the BIF <c>erlang:suspend_process/[1,2]</c>)</item>
+                or by the BIF <c>erlang:suspend_process/1,2</c>)</item>
             </list>
           </item>
           <tag><c>{suspending, <anno>SuspendeeList</anno>}</c></tag>
           <item>
             <p><c><anno>SuspendeeList</anno></c> is a list of
-            <c>{<anno>Suspendee</anno>, <anno>ActiveSuspendCount</anno>,
-            <anno>OutstandingSuspendCount</anno>}</c> tuples.
-	    <c><anno>Suspendee</anno></c> is the process identifier of a
-            process that has been, or is to be,
-            suspended by the process identified by <c><anno>Pid</anno></c>
-            through one of the following BIFs:</p>
+              <c>{<anno>Suspendee</anno>, <anno>ActiveSuspendCount</anno>,
+              <anno>OutstandingSuspendCount</anno>}</c> tuples.
+              <c><anno>Suspendee</anno></c> is the process identifier of a
+              process that has been, or is to be,
+              suspended by the process identified by <c><anno>Pid</anno></c>
+              through the BIF <seealso marker="#suspend_process/2">
+              <c>erlang:suspend_process/2</c></seealso> or
+              <seealso marker="#suspend_process/1">
+              <c>erlang:suspend_process/1</c></seealso>.</p>
+            <p><c><anno>ActiveSuspendCount</anno></c> is the number of
+              times <c><anno>Suspendee</anno></c> has been suspended by
+              <c><anno>Pid</anno></c>.
+              <c><anno>OutstandingSuspendCount</anno></c> is the number of not
+              yet completed suspend requests sent by <c><anno>Pid</anno></c>,
+              that is:</p>
             <list type="bulleted">
               <item>
-	      <seealso marker="#suspend_process/2">erlang:suspend_process/2</seealso>
+                <p>If <c><anno>ActiveSuspendCount</anno> =/= 0</c>,
+                  <c><anno>Suspendee</anno></c> is
+                  currently in the suspended state.</p>
               </item>
-	      <item>
-	      <seealso marker="#suspend_process/1">erlang:suspend_process/1</seealso>
-              </item>
-            </list>
-	    <p><c><anno>ActiveSuspendCount</anno></c> is the number of
-            times <c><anno>Suspendee</anno></c> has been suspended by
-            <c><anno>Pid</anno></c>.
-	    <c><anno>OutstandingSuspendCount</anno></c> is the number of not yet
-	    completed suspend requests sent by <c><anno>Pid</anno></c>, that is:</p>
-            <list type="bulleted">
-              <item>If <c><anno>ActiveSuspendCount</anno> =/= 0</c>,
-                <c><anno>Suspendee</anno></c> is
-	        currently in the suspended state.
-              </item>
-              <item>If <c><anno>OutstandingSuspendCount</anno> =/= 0</c>, option
-                <c>asynchronous</c> of <c>erlang:suspend_process/2</c>
-                has been used and the suspendee has not yet been
-                suspended by <c><anno>Pid</anno></c>.
+              <item>
+                <p>If <c><anno>OutstandingSuspendCount</anno> =/= 0</c>,
+                  option <c>asynchronous</c> of <c>erlang:suspend_process/2</c>
+                  has been used and the suspendee has not yet been
+                  suspended by <c><anno>Pid</anno></c>.</p>
               </item>
             </list>
-	    <p>Notice that <c><anno>ActiveSuspendCount</anno></c> and
-	    <c><anno>OutstandingSuspendCount</anno></c> are not the
-            total suspend count on <c><anno>Suspendee</anno></c>,
-            only the parts contributed by <c><anno>Pid</anno></c>.</p>
+            <p>Notice that <c><anno>ActiveSuspendCount</anno></c> and
+              <c><anno>OutstandingSuspendCount</anno></c> are not the
+              total suspend count on <c><anno>Suspendee</anno></c>,
+              only the parts contributed by <c><anno>Pid</anno></c>.</p>
           </item>
           <tag>
             <marker id="process_info_total_heap_size"/>
@@ -5008,21 +5048,21 @@ os_prompt% </pre>
           </tag>
           <item>
             <p><c><anno>Size</anno></c> is the total size, in words, of all heap
-	    fragments of the process. This includes the process stack and
-            any unreceived messages that are considered to be part of the
-            heap. </p>
+              fragments of the process. This includes the process stack and
+              any unreceived messages that are considered to be part of the
+              heap.</p>
           </item>
           <tag><c>{trace, <anno>InternalTraceFlags</anno>}</c></tag>
           <item>
             <p><c><anno>InternalTraceFlags</anno></c> is an integer
-            representing the internal trace flag for this process.
-            This <c><anno>InfoTuple</anno></c>
-	    can be changed or removed without prior notice.</p>
+              representing the internal trace flag for this process.
+              This <c><anno>InfoTuple</anno></c>
+              can be changed or removed without prior notice.</p>
           </item>
           <tag><c>{trap_exit, <anno>Boolean</anno>}</c></tag>
           <item>
             <p><c><anno>Boolean</anno></c> is <c>true</c> if the process
-            is trapping exits, otherwise <c>false</c>.</p>
+              is trapping exits, otherwise <c>false</c>.</p>
           </item>
         </taglist>
         <p>Notice that not all implementations support all
@@ -5030,9 +5070,9 @@ os_prompt% </pre>
         <p>Failures:</p>
         <taglist>
           <tag><c>badarg</c></tag>
-            <item>If <c><anno>Pid</anno></c> is not a local process.</item>
+          <item>If <c><anno>Pid</anno></c> is not a local process.</item>
           <tag><c>badarg</c></tag>
-            <item>If <c><anno>Item</anno></c> is an invalid item.</item>
+          <item>If <c><anno>Item</anno></c> is an invalid item.</item>
         </taglist>
       </desc>
     </func>
@@ -5042,11 +5082,11 @@ os_prompt% </pre>
       <fsummary>All processes.</fsummary>
       <desc>
         <p>Returns a list of process identifiers corresponding to
-	   all the processes currently existing on the local node.</p>
-	<p>Notice that an exiting process exists, but is not alive.
-           That is, <c>is_process_alive/1</c> returns <c>false</c>
-           for an exiting process, but its process identifier is part
-	   of the result returned from <c>processes/0</c>.</p>
+          all the processes currently existing on the local node.</p>
+        <p>Notice that an exiting process exists, but is not alive.
+          That is, <c>is_process_alive/1</c> returns <c>false</c>
+          for an exiting process, but its process identifier is part
+          of the result returned from <c>processes/0</c>.</p>
         <p>Example:</p>
         <pre>
 > <input>processes().</input>
@@ -5056,22 +5096,23 @@ os_prompt% </pre>
 
     <func>
       <name name="purge_module" arity="1"/>
-      <fsummary>Removes old code for a module.</fsummary>
+      <fsummary>Remove old code for a module.</fsummary>
       <desc>
         <p>Removes old code for <c><anno>Module</anno></c>.
           Before this BIF is used,
-          <c>erlang:check_process_code/2</c> is to be called to check
+          <seealso marker="#check_process_code/2">
+          <c>check_process_code/2</c></seealso>is to be called to check
           that no processes execute old code in the module.</p>
         <warning>
           <p>This BIF is intended for the code server (see
-            <seealso marker="kernel:code">code(3)</seealso>)
+            <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>)
             and is not to be used elsewhere.</p>
         </warning>
         <note>
-	  <p>As from <c>ERTS</c> 8.0 (OTP 19), any lingering processes
-	   that still execute the old code will be killed by this function.
-	   In earlier versions, such incorrect use could cause much
-	   more fatal failures, like emulator crash.</p>
+          <p>As from <c>ERTS</c> 8.0 (Erlang/OTP 19), any lingering processes
+            that still execute the old code is killed by this function.
+            In earlier versions, such incorrect use could cause much
+            more fatal failures, like emulator crash.</p>
         </note>
         <p>Failure: <c>badarg</c> if there is no old code for
           <c><anno>Module</anno></c>.</p>
@@ -5080,14 +5121,13 @@ os_prompt% </pre>
 
     <func>
       <name name="put" arity="2"/>
-      <fsummary>Adds a new value to the process dictionary.</fsummary>
+      <fsummary>Add a new value to the process dictionary.</fsummary>
       <desc>
         <p>Adds a new <c><anno>Key</anno></c> to the process dictionary,
           associated with the value <c><anno>Val</anno></c>, and returns
           <c>undefined</c>. If <c><anno>Key</anno></c> exists, the old
           value is deleted and replaced by <c><anno>Val</anno></c>, and
-          the function returns the old value.</p>
-        <p>Example:</p>
+          the function returns the old value. Example:</p>
         <pre>
 > <input>X = put(name, walrus), Y = put(name, carpenter),</input>
 <input>Z = get(name),</input>
@@ -5103,17 +5143,18 @@ os_prompt% </pre>
 
     <func>
       <name name="raise" arity="3"/>
-      <fsummary>Stops execution with an exception of given class, reason, and call stack backtrace.</fsummary>
+      <fsummary>Stop execution with an exception of specified class, reason,
+        and call stack backtrace.</fsummary>
       <type name="raise_stacktrace"/>
       <desc>
         <p>Stops the execution of the calling process with an
-          exception of given class, reason, and call stack backtrace
+          exception of the specified class, reason, and call stack backtrace
           (<em>stacktrace</em>).</p>
         <p><c><anno>Class</anno></c> is <c>error</c>, <c>exit</c>, or
           <c>throw</c>. So, if it were not for the stacktrace,
           <c>erlang:raise(<anno>Class</anno>, <anno>Reason</anno>,
-          <anno>Stacktrace</anno>)</c> is
-          equivalent to <c>erlang:<anno>Class</anno>(<anno>Reason</anno>)</c>.</p>
+          <anno>Stacktrace</anno>)</c> is equivalent to
+          <c>erlang:<anno>Class</anno>(<anno>Reason</anno>)</c>.</p>
         <p><c><anno>Reason</anno></c> is any term.
           <c><anno>Stacktrace</anno></c> is a list as
           returned from <c>get_stacktrace()</c>, that is, a list of
@@ -5123,12 +5164,12 @@ os_prompt% </pre>
           argument list. The stacktrace can also contain <c>{Fun,
           Args, Location}</c> tuples, where <c>Fun</c> is a local
           fun and <c>Args</c> is an argument list.</p>
-	<p>Element <c>Location</c> at the end is optional.
-	  Omitting it is equivalent to specifying an empty list.</p>
+        <p>Element <c>Location</c> at the end is optional.
+          Omitting it is equivalent to specifying an empty list.</p>
         <p>The stacktrace is used as the exception stacktrace for the
           calling process; it is truncated to the current
           maximum stacktrace depth.</p>
-        <p>Since evaluating this function causes the process to
+        <p>As evaluating this function causes the process to
           terminate, it has no return value unless the arguments are
           invalid, in which case the function <em>returns the error
           reason</em> <c>badarg</c>. If you want to be
@@ -5141,77 +5182,67 @@ os_prompt% </pre>
 
     <func>
       <name name="read_timer" arity="1"/>
-      <fsummary>Reads the state of a timer.</fsummary>
+      <fsummary>Read the state of a timer.</fsummary>
       <desc>
-        <p>Read the state of a timer. The same as calling
-	<seealso marker="#read_timer/2"><c>erlang:read_timer(TimerRef,
-	[])</c></seealso>.</p>
+        <p>Reads the state of a timer. The same as calling
+          <seealso marker="#read_timer/2"><c>erlang:read_timer(TimerRef,
+          [])</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="read_timer" arity="2"/>
-      <fsummary>Reads the state of a timer.</fsummary>
-      <desc>
-        <p>
-	  Read the state of a timer that has been created by either
-	  <seealso marker="#start_timer/4"><c>erlang:start_timer()</c></seealso>,
-	  or <seealso marker="#send_after/4"><c>erlang:send_after()</c></seealso>.
-	  <c><anno>TimerRef</anno></c> identifies the timer, and
-	  was returned by the BIF that created the timer.
-	</p>
-	<p>Available <c><anno>Option</anno>s</c>:</p>
+      <fsummary>Read the state of a timer.</fsummary>
+      <desc>
+        <p>Reads the state of a timer that has been created by either
+          <seealso marker="#start_timer/4"><c>erlang:start_timer</c></seealso>
+          or <seealso marker="#send_after/4"><c>erlang:send_after</c></seealso>.
+          <c><anno>TimerRef</anno></c> identifies the timer, and
+          was returned by the BIF that created the timer.</p>
+        <p><c><anno>Option</anno>s</c>:</p>
         <taglist>
-          <tag><c>{async, Async}</c></tag>
-          <item>
-	    <p>
-	      Asynchronous request for state information. <c>Async</c>
-	      defaults to <c>false</c> which will cause the operation
-	      to be performed synchronously. In this case, the <c>Result</c>
-	      is returned by <c>erlang:read_timer()</c>. When
-	      <c>Async</c> is <c>true</c>, <c>erlang:read_timer()</c>
-	      sends an asynchronous request for the state information
-	      to the timer service that manages the timer, and then returns
-	      <c>ok</c>. A message on the format <c>{read_timer,
-	      <anno>TimerRef</anno>, <anno>Result</anno>}</c> is
-	      sent to the caller of <c>erlang:read_timer()</c> when the
-	      operation has been processed.
-	    </p>
-	  </item>
+        <tag><c>{async, Async}</c></tag>
+          <item>
+            <p>Asynchronous request for state information. <c>Async</c>
+              defaults to <c>false</c>, which causes the operation
+              to be performed synchronously. In this case, the <c>Result</c>
+              is returned by <c>erlang:read_timer</c>. When
+              <c>Async</c> is <c>true</c>, <c>erlang:read_timer</c>
+              sends an asynchronous request for the state information
+              to the timer service that manages the timer, and then returns
+              <c>ok</c>. A message on the format <c>{read_timer,
+              <anno>TimerRef</anno>, <anno>Result</anno>}</c> is
+              sent to the caller of <c>erlang:read_timer</c> when the
+              operation has been processed.</p>
+          </item>
         </taglist>
-	<p>
-	  More <c><anno>Option</anno></c>s may be added in the future.
-	</p>
-	<p>
-	  If <c><anno>Result</anno></c> is an integer, it represents the
-	  time in milli-seconds left until the timer expires.</p>
-	<p>
-	  If <c><anno>Result</anno></c> is <c>false</c>, a
-	  timer corresponding to <c><anno>TimerRef</anno></c> could not
-	  be found. This can be because the timer had expired,
-	  it had been canceled, or because <c><anno>TimerRef</anno></c>
-	  never has corresponded to a timer. Even if the timer has expired,
-	  it does not tell you whether or not the timeout message has
-	  arrived at its destination yet.
-	</p>
-	<note>
-	  <p>
-	    The timer service that manages the timer may be co-located
-	    with another scheduler than the scheduler that the calling
-	    process is executing on. If this is the case, communication
-	    with the timer service takes much longer time than if it
-	    is located locally. If the calling process is in critical
-	    path, and can do other things while waiting for the result
-	    of this operation, you want to use option <c>{async, true}</c>.
-	    If using option <c>{async, false}</c>, the calling
-	    process will be blocked until the operation has been
-	    performed.
-	  </p>
-	</note>
+        <p>More <c><anno>Option</anno></c>s can be added in the future.</p>
+        <p>If <c><anno>Result</anno></c> is an integer, it represents the
+          time in milliseconds left until the timer expires.</p>
+        <p>If <c><anno>Result</anno></c> is <c>false</c>, a
+          timer corresponding to <c><anno>TimerRef</anno></c> could not
+          be found. This because the timer had expired,
+          or been canceled, or because <c><anno>TimerRef</anno></c>
+          never has corresponded to a timer. Even if the timer has expired,
+          it does not tell you whether or not the time-out message has
+          arrived at its destination yet.</p>
+        <note>
+          <p>The timer service that manages the timer can be co-located
+            with another scheduler than the scheduler that the calling
+            process is executing on. If so, communication
+            with the timer service takes much longer time than if it
+            is located locally. If the calling process is in a critical
+            path, and can do other things while waiting for the result
+            of this operation, you want to use option <c>{async, true}</c>.
+            If using option <c>{async, false}</c>, the calling
+            process is blocked until the operation has been performed.</p>
+         </note>
         <p>See also 
           <seealso marker="#send_after/4"><c>erlang:send_after/4</c></seealso>,
-          <seealso marker="#start_timer/4"><c>erlang:start_timer/4</c></seealso>,
-          and
-          <seealso marker="#cancel_timer/2"><c>erlang:cancel_timer/2</c></seealso>.</p>
+          <seealso marker="#start_timer/4">
+          <c>erlang:start_timer/4</c></seealso>, and
+          <seealso marker="#cancel_timer/2">
+          <c>erlang:cancel_timer/2</c></seealso>.</p>
       </desc>
     </func>
 
@@ -5223,21 +5254,20 @@ os_prompt% </pre>
           representation of <c><anno>Ref</anno></c>.</p>
         <warning>
           <p>This BIF is intended for debugging and is not to be used
-	  in application programs.</p>
+            in application programs.</p>
         </warning>
       </desc>
     </func>
 
     <func>
       <name name="register" arity="2"/>
-      <fsummary>Registers a name for a pid (or port).</fsummary>
+      <fsummary>Register a name for a pid (or port).</fsummary>
       <desc>
         <p>Associates the name <c><anno>RegName</anno></c> with a process
           identifier (pid) or a port identifier.
           <c><anno>RegName</anno></c>, which must be an atom, can be used
           instead of the pid or port identifier in send operator
-          (<c><anno>RegName</anno> ! Message</c>).</p>
-        <p>Example:</p>
+          (<c><anno>RegName</anno> ! Message</c>). Example:</p>
         <pre>
 > <input>register(db, Pid).</input>
 true</pre>
@@ -5263,7 +5293,7 @@ true</pre>
       <fsummary>All registered names.</fsummary>
       <desc>
         <p>Returns a list of names that have been registered using
-          <seealso marker="#register/2">register/2</seealso>, for
+          <seealso marker="#register/2"><c>register/2</c></seealso>, for
           example:</p>
         <pre>
 > <input>registered().</input>
@@ -5273,20 +5303,21 @@ true</pre>
 
     <func>
       <name name="resume_process" arity="1"/>
-      <fsummary>Resumes a suspended process.</fsummary>
+      <fsummary>Resume a suspended process.</fsummary>
       <desc>
         <p>Decreases the suspend count on the process identified by
-	<c><anno>Suspendee</anno></c>. <c><anno>Suspendee</anno></c>
-        is previously to have been suspended through
-	<seealso marker="#suspend_process/2">erlang:suspend_process/2</seealso>
-	or
-	<seealso marker="#suspend_process/1">erlang:suspend_process/1</seealso>
-	by the process calling
-        <c>erlang:resume_process(<anno>Suspendee</anno>)</c>. When the
-        suspend count on <c><anno>Suspendee</anno></c> reaches zero,
-        <c><anno>Suspendee</anno></c> is resumed, that is, its state
-        is changed from suspended into the state it had before it was
-        suspended.</p>
+          <c><anno>Suspendee</anno></c>. <c><anno>Suspendee</anno></c>
+          is previously to have been suspended through
+          <seealso marker="#suspend_process/2">
+          <c>erlang:suspend_process/2</c></seealso> or
+          <seealso marker="#suspend_process/1">
+          <c>erlang:suspend_process/1</c></seealso>
+          by the process calling
+          <c>erlang:resume_process(<anno>Suspendee</anno>)</c>. When the
+          suspend count on <c><anno>Suspendee</anno></c> reaches zero,
+          <c><anno>Suspendee</anno></c> is resumed, that is, its state
+          is changed from suspended into the state it had before it was
+          suspended.</p>
         <warning>
           <p>This BIF is intended for debugging only.</p>
         </warning>
@@ -5294,29 +5325,29 @@ true</pre>
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	  If <c><anno>Suspendee</anno></c> is not a process identifier.
-	  </item>
+            If <c><anno>Suspendee</anno></c> is not a process identifier.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	  If the process calling <c>erlang:resume_process/1</c> had
-	  not previously increased the suspend count on the process
-	  identified by <c><anno>Suspendee</anno></c>.
-	  </item>
+            If the process calling <c>erlang:resume_process/1</c> had
+            not previously increased the suspend count on the process
+            identified by <c><anno>Suspendee</anno></c>.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	  If the process identified by <c><anno>Suspendee</anno></c>
-           is not alive.
-	  </item>
+            If the process identified by <c><anno>Suspendee</anno></c>
+            is not alive.
+          </item>
         </taglist>
       </desc>
     </func>
 
     <func>
       <name name="round" arity="1"/>
-      <fsummary>Returns an integer by rounding a number.</fsummary>
+      <fsummary>Return an integer by rounding a number.</fsummary>
       <desc>
         <p>Returns an integer by rounding <c><anno>Number</anno></c>,
-        for example:</p>
+          for example:</p>
         <pre>
 <input>round(5.5).</input>
 6</pre>
@@ -5326,7 +5357,7 @@ true</pre>
 
     <func>
       <name name="self" arity="0"/>
-      <fsummary>Returns pid of the calling process.</fsummary>
+      <fsummary>Return pid of the calling process.</fsummary>
       <desc>
         <p>Returns the process identifier of the calling process, for
           example:</p>
@@ -5339,7 +5370,7 @@ true</pre>
 
     <func>
       <name name="send" arity="2"/>
-      <fsummary>Sends a message.</fsummary>
+      <fsummary>Send a message.</fsummary>
       <type name="dst"/>
       <desc>
         <p>Sends a message and returns <c><anno>Msg</anno></c>. This
@@ -5353,27 +5384,27 @@ true</pre>
 
     <func>
       <name name="send" arity="3"/>
-      <fsummary>Sends a message conditionally.</fsummary>
+      <fsummary>Send a message conditionally.</fsummary>
       <type name="dst"/>
       <desc>
         <p>Either sends a message and returns <c>ok</c>, or does not send
-          the message but returns something else (see the following).
+          the message but returns something else (see below).
           Otherwise the same as
-          <seealso marker="#send/2">erlang:send/2</seealso>.
+          <seealso marker="#send/2"><c>erlang:send/2</c></seealso>.
           For more detailed explanation and warnings, see
-          <seealso marker="#send_nosuspend/2">erlang:send_nosuspend/2,3</seealso>.</p>
-        <p>The options are as follows:</p>
+          <seealso marker="#send_nosuspend/2">
+          <c>erlang:send_nosuspend/2,3</c></seealso>.</p>
+        <p>Options:</p>
         <taglist>
           <tag><c>nosuspend</c></tag>
-          <item>
-            <p>If the sender would have to be suspended to do the send,
-              <c>nosuspend</c> is returned instead.</p>
+          <item>If the sender would have to be suspended to do the send,
+            <c>nosuspend</c> is returned instead.
           </item>
           <tag><c>noconnect</c></tag>
           <item>
-            <p>If the destination node would have to be auto-connected
-              to do the send, <c>noconnect</c> is returned
-              instead.</p>
+            If the destination node would have to be auto-connected
+             to do the send, <c>noconnect</c> is returned
+             instead.
           </item>
         </taglist>
         <warning>
@@ -5385,35 +5416,36 @@ true</pre>
 
     <func>
       <name name="send_after" arity="3"/>
-      <fsummary>Starts a timer.</fsummary>
+      <fsummary>Start a timer.</fsummary>
       <desc>
         <p>Starts a timer. The same as calling
-	<seealso marker="#send_after/4"><c>erlang:send_after(<anno>Time</anno>,
-	<anno>Dest</anno>, <anno>Msg</anno>, [])</c></seealso>.</p>
+          <seealso marker="#send_after/4">
+          <c>erlang:send_after(<anno>Time</anno>, <anno>Dest</anno>,
+          <anno>Msg</anno>, [])</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="send_after" arity="4"/>
-      <fsummary>Start a timer</fsummary>
+      <fsummary>Start a timer.</fsummary>
       <desc>
-        <p>
-	  Starts a timer. When the timer expires, the message
+        <p>Starts a timer. When the timer expires, the message
           <c><anno>Msg</anno></c> is sent to the process
-	  identified by <c><anno>Dest</anno></c>. Apart from
-	  the format of the timeout message,
-	  <c>erlang:send_after/4</c> works exactly as
-	  <seealso marker="#start_timer/4"><c>erlang:start_timer/4</c></seealso>.</p>
+          identified by <c><anno>Dest</anno></c>. Apart from
+          the format of the time-out message, this function works exactly as
+          <seealso marker="#start_timer/4">
+          <c>erlang:start_timer/4</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="send_nosuspend" arity="2"/>
-      <fsummary>Tries to send a message without ever blocking.</fsummary>
+      <fsummary>Try to send a message without ever blocking.</fsummary>
       <type name="dst"/>
       <desc>
         <p>The same as
-          <seealso marker="#send/3">erlang:send(<anno>Dest</anno>,
-          <anno>Msg</anno>, [nosuspend])</seealso>,
+          <seealso marker="#send/3"><c>erlang:send(<anno>Dest</anno>,
+          <anno>Msg</anno>, [nosuspend])</c></seealso>,
           but returns <c>true</c> if
           the message was sent and <c>false</c> if the message was not
           sent because the sender would have had to be suspended.</p>
@@ -5439,12 +5471,12 @@ true</pre>
           contradictory to the Erlang programming model. The message is
           <em>not</em> sent if this function returns <c>false</c>.</p>
         <p>In many systems, transient states of
-          overloaded queues are normal. The fact that this function
+          overloaded queues are normal. Although this function
           returns <c>false</c> does not mean that the other
           node is guaranteed to be non-responsive, it could be a
           temporary overload. Also, a return value of <c>true</c> does
           only mean that the message can be sent on the (TCP) channel
-          without blocking, the message is not guaranteed to
+          without blocking; the message is not guaranteed to
           arrive at the remote node. For a disconnected
           non-responsive node, the return value is <c>true</c> (mimics
           the behavior of operator <c>!</c>). The expected
@@ -5458,15 +5490,16 @@ true</pre>
 
     <func>
       <name name="send_nosuspend" arity="3"/>
-      <fsummary>Tries to send a message without ever blocking.</fsummary>
+      <fsummary>Try to send a message without ever blocking.</fsummary>
       <type name="dst"/>
       <desc>
         <p>The same as
-          <seealso marker="#send/3">erlang:send(<anno>Dest</anno>,
-          <anno>Msg</anno>, [nosuspend | <anno>Options</anno>])</seealso>,
+          <seealso marker="#send/3"><c>erlang:send(<anno>Dest</anno>,
+          <anno>Msg</anno>, [nosuspend | <anno>Options</anno>])</c></seealso>,
           but with a Boolean return value.</p>
         <p>This function behaves like
-          <seealso marker="#send_nosuspend/2">erlang:send_nosuspend/2</seealso>,
+          <seealso marker="#send_nosuspend/2">
+          <c>erlang:send_nosuspend/2</c></seealso>,
           but takes a third parameter, a list of options.
           The only option is <c>noconnect</c>, which
           makes the function return <c>false</c> if
@@ -5490,14 +5523,15 @@ true</pre>
 
     <func>
       <name name="set_cookie" arity="2"/>
-      <fsummary>Sets the magic cookie of a node.</fsummary>
+      <fsummary>Set the magic cookie of a node.</fsummary>
       <desc>
         <p>Sets the magic cookie of <c><anno>Node</anno></c> to the atom
           <c><anno>Cookie</anno></c>. If <c><anno>Node</anno></c> is the
           local node, the function
           also sets the cookie of all other unknown nodes to
-          <c><anno>Cookie</anno></c> (see Section
-          <seealso marker="doc/reference_manual:distributed">Distributed Erlang</seealso>
+          <c><anno>Cookie</anno></c> (see section
+          <seealso marker="doc/reference_manual:distributed">
+          Distributed Erlang</seealso>
           in the Erlang Reference Manual in System Documentation).</p>
         <p>Failure: <c>function_clause</c> if the local node is not
           alive.</p>
@@ -5506,12 +5540,12 @@ true</pre>
 
     <func>
       <name name="setelement" arity="3"/>
-      <fsummary>Sets the Nth element of a tuple.</fsummary>
+      <fsummary>Set the Nth element of a tuple.</fsummary>
       <type_desc variable="Index">1..tuple_size(<anno>Tuple1</anno></type_desc>
       <desc>
         <p>Returns a tuple that is a copy of argument
           <c><anno>Tuple1</anno></c>
-          with the element given by integer argument
+          with the element specified by integer argument
           <c><anno>Index</anno></c>
           (the first element is the element with index 1) replaced by
           argument <c><anno>Value</anno></c>, for example:</p>
@@ -5526,52 +5560,52 @@ true</pre>
       <fsummary>Size of a tuple or binary.</fsummary>
       <desc>
         <p>Returns the number of elements in a tuple or the number of
-	bytes in a binary or bitstring, for example:</p>
+          bytes in a binary or bitstring, for example:</p>
         <pre>
 > <input>size({morni, mulle, bwange}).</input>
 3
 > <input>size(&lt;&lt;11, 22, 33&gt;&gt;).</input>
-3
-</pre>
-        <p>For bitstrings the number of whole bytes is returned. That is, if the number of bits
+3</pre>
+        <p>For bitstrings, the number of whole bytes is returned.
+          That is, if the number of bits
           in the bitstring is not divisible by 8, the resulting
           number of bytes is rounded <em>down</em>.</p>
         <p>Allowed in guard tests.</p>
         <p>See also
           <seealso marker="#tuple_size/1"><c>tuple_size/1</c></seealso>,
-          <seealso marker="#byte_size/1"><c>byte_size/1</c></seealso>
-	  and
+          <seealso marker="#byte_size/1"><c>byte_size/1</c></seealso>, and
           <seealso marker="#bit_size/1"><c>bit_size/1</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn" arity="1"/>
-      <fsummary>Creates a new process with a fun as entry point.</fsummary>
+      <fsummary>Create a new process with a fun as entry point.</fsummary>
       <desc>
         <p>Returns the process identifier of a new process started by the
           application of <c><anno>Fun</anno></c> to the empty list
           <c>[]</c>. Otherwise
-          works like <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          works like <seealso marker="#spawn/3"><c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn" arity="2"/>
-      <fsummary>Creates a new process with a fun as entry point on a given node.</fsummary>
+      <fsummary>Create a new process with a fun as entry point on a specified
+        node.</fsummary>
       <desc>
         <p>Returns the process identifier of a new process started
           by the application of <c><anno>Fun</anno></c> to the
           empty list <c>[]</c> on <c><anno>Node</anno></c>. If
           <c><anno>Node</anno></c> does not exist, a useless pid is
           returned. Otherwise works like
-          <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          <seealso marker="#spawn/3"><c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn" arity="3"/>
-      <fsummary>Creates a new process with a function as entry point.</fsummary>
+      <fsummary>Create a new process with a function as entry point.</fsummary>
       <desc>
         <p>Returns the process identifier of a new process started by
           the application of <c><anno>Module</anno>:<anno>Function</anno></c>
@@ -5583,7 +5617,7 @@ true</pre>
           does not exist (where <c>Arity</c> is the length of
           <c><anno>Args</anno></c>). The error handler
           can be redefined (see
-          <seealso marker="#process_flag/2">process_flag/2</seealso>).
+          <seealso marker="#process_flag/2"><c>process_flag/2</c></seealso>).
           If <c>error_handler</c> is undefined, or the user has
           redefined the default <c>error_handler</c> and its replacement is
           undefined, a failure with reason <c>undef</c> occurs.</p>
@@ -5596,7 +5630,8 @@ true</pre>
 
     <func>
       <name name="spawn" arity="4"/>
-      <fsummary>Creates a new process with a function as entry point on a given node.</fsummary>
+      <fsummary>Create a new process with a function as entry point on a
+        specified node.</fsummary>
       <desc>
         <p>Returns the process identifier (pid) of a new process started
           by the application
@@ -5604,26 +5639,28 @@ true</pre>
           to <c><anno>Args</anno></c> on <c><anno>Node</anno></c>. If
           <c><anno>Node</anno></c> does not exist, a useless pid is returned.
           Otherwise works like
-          <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          <seealso marker="#spawn/3"><c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_link" arity="1"/>
-      <fsummary>Creates and links to a new process with a fun as entry point.</fsummary>
+      <fsummary>Create and link to a new process with a fun as entry point.
+      </fsummary>
       <desc>
         <p>Returns the process identifier of a new process started by
           the application of <c><anno>Fun</anno></c> to the empty list
           <c>[]</c>. A link is created between
           the calling process and the new process, atomically.
           Otherwise works like
-          <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          <seealso marker="#spawn/3"><c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_link" arity="2"/>
-      <fsummary>Creates and links to a new process with a fun as entry point on a specified node.</fsummary>
+      <fsummary>Create and link to a new process with a fun as entry point on
+        a specified node.</fsummary>
       <desc>
         <p>Returns the process identifier (pid) of a new process started
           by the application of <c><anno>Fun</anno></c> to the empty
@@ -5632,26 +5669,29 @@ true</pre>
           atomically. If <c><anno>Node</anno></c> does not exist,
           a useless pid is returned and an exit signal with
           reason <c>noconnection</c> is sent to the calling
-	  process. Otherwise works like <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          process. Otherwise works like <seealso marker="#spawn/3">
+          <c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_link" arity="3"/>
-      <fsummary>Creates and links to a new process with a function as entry point.</fsummary>
+      <fsummary>Create and link to a new process with a function as entry point.
+      </fsummary>
       <desc>
         <p>Returns the process identifier of a new process started by
           the application of <c><anno>Module</anno>:<anno>Function</anno></c>
           to <c><anno>Args</anno></c>. A link is created
           between the calling process and the new process, atomically.
           Otherwise works like
-          <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          <seealso marker="#spawn/3"><c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_link" arity="4"/>
-      <fsummary>Creates and links to a new process with a function as entry point on a given node.</fsummary>
+      <fsummary>Create and link to a new process with a function as entry point
+        on a specified node.</fsummary>
       <desc>
         <p>Returns the process identifier (pid) of a new process
           started by the application
@@ -5661,109 +5701,113 @@ true</pre>
           process, atomically. If <c><anno>Node</anno></c> does
           not exist, a useless pid is returned and an exit signal with
           reason <c>noconnection</c> is sent to the calling
-	  process. Otherwise works like <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          process. Otherwise works like <seealso marker="#spawn/3">
+          <c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_monitor" arity="1"/>
-      <fsummary>Creates and monitors a new process with a fun as entry point.</fsummary>
+      <fsummary>Create and monitor a new process with a fun as entry point.
+      </fsummary>
       <desc>
         <p>Returns the process identifier of a new process, started by
           the application of <c><anno>Fun</anno></c> to the empty list
           <c>[]</c>,
           and a reference for a monitor created to the new process.
           Otherwise works like
-          <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          <seealso marker="#spawn/3"><c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_monitor" arity="3"/>
-      <fsummary>Creates and monitors a new process with a function as entry point.</fsummary>
+      <fsummary>Create and monitor a new process with a function as entry point.
+      </fsummary>
       <desc>
         <p>A new process is started by the application
           of <c><anno>Module</anno>:<anno>Function</anno></c>
           to <c><anno>Args</anno></c>. The process is
           monitored at the same time. Returns the process identifier
           and a reference for the monitor. Otherwise works like
-          <seealso marker="#spawn/3">spawn/3</seealso>.</p>
+          <seealso marker="#spawn/3"><c>spawn/3</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_opt" arity="2"/>
-      <fsummary>Creates a new process with a fun as entry point.</fsummary>
+      <fsummary>Create a new process with a fun as entry point.</fsummary>
       <type name="priority_level"/>
-      <type name="max_heap_size" />
-      <type name="message_queue_data" />
-      <type name="spawn_opt_option" />
+      <type name="max_heap_size"/>
+      <type name="message_queue_data"/>
+      <type name="spawn_opt_option"/>
       <desc>
         <p>Returns the process identifier (pid) of a new process
           started by the application of <c><anno>Fun</anno></c>
           to the empty list <c>[]</c>. Otherwise works like
-          <seealso marker="#spawn_opt/4">spawn_opt/4</seealso>.</p>
-        <p>If option <c>monitor</c> is given, the newly created
+          <seealso marker="#spawn_opt/4"><c>spawn_opt/4</c></seealso>.</p>
+        <p>If option <c>monitor</c> is specified, the newly created
           process is monitored, and both the pid and reference for
-          the monitor is returned.</p>
+          the monitor are returned.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_opt" arity="3"/>
-      <fsummary>Creates a new process with a fun as entry point on a given node.</fsummary>
+      <fsummary>Create a new process with a fun as entry point on a specified
+        node.</fsummary>
       <type name="priority_level"/>
-      <type name="max_heap_size" />
-      <type name="message_queue_data" />
-      <type name="spawn_opt_option" />
+      <type name="max_heap_size"/>
+      <type name="message_queue_data"/>
+      <type name="spawn_opt_option"/>
       <desc>
         <p>Returns the process identifier (pid) of a new process started
           by the application of <c><anno>Fun</anno></c> to the
           empty list <c>[]</c> on <c><anno>Node</anno></c>. If
           <c><anno>Node</anno></c> does not exist, a useless pid is
           returned. Otherwise works like
-          <seealso marker="#spawn_opt/4">spawn_opt/4</seealso>.</p>
+          <seealso marker="#spawn_opt/4"><c>spawn_opt/4</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="spawn_opt" arity="4"/>
-      <fsummary>Creates a new process with a function as entry point.</fsummary>
+      <fsummary>Create a new process with a function as entry point.</fsummary>
       <type name="priority_level"/>
-      <type name="max_heap_size" />
-      <type name="message_queue_data" />
-      <type name="spawn_opt_option" />
+      <type name="max_heap_size"/>
+      <type name="message_queue_data"/>
+      <type name="spawn_opt_option"/>
       <desc>
         <p>Works as
-          <seealso marker="#spawn/3">spawn/3</seealso>, except that an
-          extra option list is given when creating the process.</p>
-        <p>If option <c>monitor</c> is given, the newly created
+          <seealso marker="#spawn/3"><c>spawn/3</c></seealso>, except that an
+          extra option list is specified when creating the process.</p>
+        <p>If option <c>monitor</c> is specified, the newly created
           process is monitored, and both the pid and reference for
-          the monitor is returned.</p>
-        <p>The options are as follows:</p>
+          the monitor are returned.</p>
+        <p>Options:</p>
         <taglist>
           <tag><c>link</c></tag>
           <item>
             <p>Sets a link to the parent process (like
-              <c>spawn_link/3</c> does).</p>
+              <seealso marker="#spawn_link/3"><c>spawn_link/3</c></seealso>
+              does).</p>
           </item>
           <tag><c>monitor</c></tag>
           <item>
             <p>Monitors the new process (like
-              <seealso marker="#monitor/2">monitor/2</seealso> does).</p>
+              <seealso marker="#monitor/2"><c>monitor/2</c></seealso> does).</p>
           </item>
           <tag><c>{priority, <anno>Level</anno></c></tag>
           <item>
             <p>Sets the priority of the new process. Equivalent to
-              executing
-              <seealso marker="#process_flag_priority">process_flag(priority,
-              <anno>Level</anno>)</seealso>
+              executing <seealso marker="#process_flag_priority">
+              <c>process_flag(priority, <anno>Level</anno>)</c></seealso>
               in the start function of the new process,
               except that the priority is set before the process is
               selected for execution for the first time. For more
               information on priorities, see
-              <seealso marker="#process_flag_priority">process_flag(priority,
-              <anno>Level</anno>)</seealso>.</p>
+              <seealso marker="#process_flag_priority">
+              <c>process_flag(priority, <anno>Level</anno>)</c></seealso>.</p>
           </item>
           <tag><c>{fullsweep_after, <anno>Number</anno>}</c></tag>
           <item>
@@ -5786,21 +5830,22 @@ true</pre>
             <p>A few cases when it can be useful to change
               <c>fullsweep_after</c>:</p>
             <list type="bulleted">
-              <item>If binaries that are no longer used are to be
+              <item><p>If binaries that are no longer used are to be
                 thrown away as soon as possible. (Set
-                <c><anno>Number</anno></c> to zero.)
+                <c><anno>Number</anno></c> to zero.)</p>
               </item>
-              <item>A process that mostly have short-lived data is
+              <item><p>A process that mostly have short-lived data is
                 fullsweeped seldom or never, that is, the old heap
                 contains mostly garbage. To ensure a fullsweep
                 occasionally, set <c><anno>Number</anno></c> to a
-                suitable value, such as 10 or 20.
+                suitable value, such as 10 or 20.</p>
               </item>
               <item>In embedded systems with a limited amount of RAM
               and no virtual memory, you might want to preserve memory
               by setting <c><anno>Number</anno></c> to zero.
               (The value can be set globally, see
-              <seealso marker="#system_flag/2">erlang:system_flag/2</seealso>.)
+              <seealso marker="#system_flag/2">
+              <c>erlang:system_flag/2</c></seealso>.)
               </item>
             </list>
           </item>
@@ -5825,7 +5870,7 @@ true</pre>
               option unless you know that there is problem with
               execution times or memory consumption, and
               ensure that the option improves matters.</p>
-	      <p>Gives a minimum binary virtual heap size, in words.
+            <p>Gives a minimum binary virtual heap size, in words.
               Setting this value
               higher than the system default can speed up some
               processes because less garbage collection is done.
@@ -5837,24 +5882,25 @@ true</pre>
           <tag><c>{max_heap_size, <anno>Size</anno>}</c></tag>
           <item>
             <p>Sets the <c>max_heap_size</c> process flag. The default
-            <c>max_heap_size</c> is determined by the
-            <seealso marker="erl#+hmax"><c>+hmax</c></seealso> <c>erl</c>
-	    command line argument. For more information, see the
-	    documentation of
-            <seealso marker="#process_flag_max_heap_size"><c>process_flag(max_heap_size,
-	    <anno>Size</anno>)</c></seealso>.</p>
+              <c>max_heap_size</c> is determined by command-line argument
+              <seealso marker="erl#+hmax"><c>+hmax</c></seealso>
+              in <c>erl/1</c>. For more information, see the
+              documentation of <seealso marker="#process_flag_max_heap_size">
+              <c>process_flag(max_heap_size, <anno>Size</anno>)</c></seealso>.
+            </p>
           </item>
           <tag><c>{message_queue_data, <anno>MQD</anno>}</c></tag>
           <item>
             <p>Sets the state of the <c>message_queue_data</c> process
-	    flag. <c><anno>MQD</anno></c> should be either <c>off_heap</c>,
-	    or <c>on_heap</c>. The default
-	    <c>message_queue_data</c> process flag is determined by the
-	    <seealso marker="erl#+hmqd"><c>+hmqd</c></seealso> <c>erl</c>
-	    command line argument. For more information, see the
-	    documentation of
-            <seealso marker="#process_flag_message_queue_data"><c>process_flag(message_queue_data,
-	    <anno>MQD</anno>)</c></seealso>.</p>
+              flag. <c><anno>MQD</anno></c> is to be either <c>off_heap</c>
+              or <c>on_heap</c>. The default
+              <c>message_queue_data</c> process flag is determined by
+              command-line argument <seealso marker="erl#+hmqd">
+              <c>+hmqd</c></seealso> in <c>erl/1</c>.
+              For more information, see the documentation of
+              <seealso marker="#process_flag_message_queue_data">
+              <c>process_flag(message_queue_data,
+              <anno>MQD</anno>)</c></seealso>.</p>
           </item>
         </taglist>
       </desc>
@@ -5862,11 +5908,12 @@ true</pre>
 
     <func>
       <name name="spawn_opt" arity="5"/>
-      <fsummary>Creates a new process with a function as entry point on a given node.</fsummary>
+      <fsummary>Create a new process with a function as entry point on a
+        specified node.</fsummary>
       <type name="priority_level"/>
-      <type name="max_heap_size" />
-      <type name="message_queue_data" />
-      <type name="spawn_opt_option" />
+      <type name="max_heap_size"/>
+      <type name="message_queue_data"/>
+      <type name="spawn_opt_option"/>
       <desc>
         <p>Returns the process identifier (pid) of a new process started
           by the application
@@ -5874,23 +5921,24 @@ true</pre>
           <c><anno>Args</anno></c> on <c><anno>Node</anno></c>. If
           <c><anno>Node</anno></c> does not exist, a useless pid is returned.
           Otherwise works like
-          <seealso marker="#spawn_opt/4">spawn_opt/4</seealso>.</p>
-	  <note><p>Option <c>monitor</c> is not supported by
-	  <c>spawn_opt/5</c>.</p></note>
+          <seealso marker="#spawn_opt/4"><c>spawn_opt/4</c></seealso>.</p>
+        <note>
+          <p>Option <c>monitor</c> is not supported by
+            <c>spawn_opt/5</c>.</p>
+        </note>
       </desc>
     </func>
 
     <func>
       <name name="split_binary" arity="2"/>
-      <fsummary>Splits a binary into two.</fsummary>
+      <fsummary>Split a binary into two.</fsummary>
       <type_desc variable="Pos">0..byte_size(Bin)</type_desc>
       <desc>
         <p>Returns a tuple containing the binaries that are the result
           of splitting <c><anno>Bin</anno></c> into two parts at
           position <c><anno>Pos</anno></c>.
           This is not a destructive operation. After the operation,
-          there are three binaries altogether.</p>
-        <p>Example:</p>
+          there are three binaries altogether. Example:</p>
         <pre>
 > <input>B = list_to_binary("0123456789").</input>
 &lt;&lt;"0123456789">>
@@ -5907,79 +5955,68 @@ true</pre>
 
     <func>
       <name name="start_timer" arity="3"/>
-      <fsummary>Starts a timer.</fsummary>
+      <fsummary>Start a timer.</fsummary>
       <desc>
         <p>Starts a timer. The same as calling
-	<seealso marker="#start_timer/4"><c>erlang:start_timer(<anno>Time</anno>,
-	<anno>Dest</anno>, <anno>Msg</anno>, [])</c></seealso>.</p>
+          <seealso marker="#start_timer/4">
+          <c>erlang:start_timer(<anno>Time</anno>,
+          <anno>Dest</anno>, <anno>Msg</anno>, [])</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="start_timer" arity="4"/>
-      <fsummary>Starts a timer.</fsummary>
+      <fsummary>Start a timer.</fsummary>
       <desc>
-        <p>
-	  Starts a timer. When the timer expires, the message
+        <p>Starts a timer. When the timer expires, the message
           <c>{timeout, <anno>TimerRef</anno>, <anno>Msg</anno>}</c>
-	  is sent to the process identified by
-	  <c><anno>Dest</anno></c>.
-	</p>
-	<p>Available <c><anno>Option</anno></c>s:</p>
+          is sent to the process identified by <c><anno>Dest</anno></c>.</p>
+        <p><c><anno>Option</anno></c>s:</p>
         <taglist>
           <tag><c>{abs, false}</c></tag>
           <item>
-	    <p>
-	      This is the default. It means the
-	      <c><anno>Time</anno></c> value is interpreted
-	      as a time in milli-seconds <em>relative</em> current
-	      <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	      monotonic time</seealso>.
-	    </p>
-	  </item>
+            <p>This is the default. It means the
+              <c><anno>Time</anno></c> value is interpreted
+              as a time in milliseconds <em>relative</em> current
+              <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+              monotonic time</seealso>.</p>
+          </item>
           <tag><c>{abs, true}</c></tag>
           <item>
-	    <p>
-	      Absolute <c><anno>Time</anno></c> value. The
-	      <c><anno>Time</anno></c> value is interpreted as an
-	      absolute Erlang monotonic time in milli-seconds.
-	    </p>
-	  </item>
+            <p>Absolute <c><anno>Time</anno></c> value. The
+              <c><anno>Time</anno></c> value is interpreted as an
+              absolute Erlang monotonic time in milliseconds.</p>
+          </item>
         </taglist>
-	<p>
-	  More <c><anno>Option</anno></c>s may be added in the future.
-	</p>
-	<p>
-	  The absolute point in time, the timer is set to expire on,
-	  has to be in the interval
-	  <c>[</c><seealso marker="#system_info_start_time"><c>erlang:system_info(start_time)</c></seealso><c>,
-	  </c><seealso marker="#system_info_end_time"><c>erlang:system_info(end_time)</c></seealso><c>]</c>.
-	  Further, if a relative time is specified, the <c><anno>Time</anno></c> value
-	  is not allowed to be negative.
-	</p>
-	<p>
-	  If <c><anno>Dest</anno></c> is a <c>pid()</c>, it must
-	  be a <c>pid()</c> of a process created on the current
-	  runtime system instance. This process may or may not
-	  have terminated. If <c><anno>Dest</anno></c> is an
-	  <c>atom()</c>, it is interpreted as the name of a
-	  locally registered process. The process referred to by the
-	  name is looked up at the time of timer expiration. No error
-	  is given if the name does not refer to a process.
-	</p>
-        <p>
-	  If <c><anno>Dest</anno></c> is a <c>pid()</c>, the timer is
-	  automatically canceled if the process referred to by the
-	  <c>pid()</c> is not alive, or if the process exits. This
-	  feature was introduced in ERTS version 5.4.11. Notice that
-	  timers are not automatically canceled when
-	  <c><anno>Dest</anno></c> is an <c>atom()</c>.
-	</p>
+        <p>More <c><anno>Option</anno></c>s can be added in the future.</p>
+        <p>The absolute point in time, the timer is set to expire on,
+          must be in the interval
+          <c>[</c><seealso marker="#system_info_start_time">
+          <c>erlang:system_info(start_time)</c></seealso><c>,
+          </c><seealso marker="#system_info_end_time">
+          <c>erlang:system_info(end_time)</c></seealso><c>]</c>.
+          If a relative time is specified, the <c><anno>Time</anno></c>
+          value is not allowed to be negative.</p>
+        <p>If <c><anno>Dest</anno></c> is a <c>pid()</c>, it must
+          be a <c>pid()</c> of a process created on the current
+          runtime system instance. This process has either terminated
+          or not. If <c><anno>Dest</anno></c> is an
+          <c>atom()</c>, it is interpreted as the name of a
+          locally registered process. The process referred to by the
+          name is looked up at the time of timer expiration. No error
+          is returned if the name does not refer to a process.</p>
+        <p>If <c><anno>Dest</anno></c> is a <c>pid()</c>, the timer is
+          automatically canceled if the process referred to by the
+          <c>pid()</c> is not alive, or if the process exits. This
+          feature was introduced in <c>ERTS</c> 5.4.11. Notice that
+          timers are not automatically canceled when
+          <c><anno>Dest</anno></c> is an <c>atom()</c>.</p>
         <p>See also
           <seealso marker="#send_after/4"><c>erlang:send_after/4</c></seealso>,
-          <seealso marker="#cancel_timer/2"><c>erlang:cancel_timer/2</c></seealso>,
-          and
-          <seealso marker="#read_timer/2"><c>erlang:read_timer/2</c></seealso>.</p>
+          <seealso marker="#cancel_timer/2">
+          <c>erlang:cancel_timer/2</c></seealso>, and
+          <seealso marker="#read_timer/2">
+          <c>erlang:read_timer/2</c></seealso>.</p>
         <p>Failure: <c>badarg</c> if the arguments do not satisfy
           the requirements specified here.</p>
       </desc>
@@ -5988,22 +6025,25 @@ true</pre>
     <func>
       <name name="statistics" arity="1" clause_i="1"/>
       <fsummary>Information about active processes and ports.</fsummary>
-      <desc><marker id="statistics_active_tasks"></marker>
-	<p>
-	  Returns a list where each element represents the amount
-	  of active processes and ports on each run queue and its
-	  associated scheduler. That is, the number of processes and
-	  ports that are ready to run, or are currently running. The
-	  element location in the list corresponds to the scheduler
-	  and its run queue. The first element corresponds to scheduler
-	  number 1 and so on. The information is <em>not</em> gathered
-	  atomically. That is, the result is not necessarily a
-	  consistent snapshot of the state, but instead quite
-	  efficiently gathered. See also,
-	  <seealso marker="#statistics_total_active_tasks"><c>statistics(total_active_tasks)</c></seealso>,
-	  <seealso marker="#statistics_run_queue_lengths"><c>statistics(run_queue_lengths)</c></seealso>, and
-	  <seealso marker="#statistics_total_run_queue_lengths"><c>statistics(total_run_queue_lengths)</c></seealso>.
-	</p>
+      <desc>
+        <marker id="statistics_active_tasks"></marker>
+        <p>Returns a list where each element represents the amount
+          of active processes and ports on each run queue and its
+          associated scheduler. That is, the number of processes and
+          ports that are ready to run, or are currently running. The
+          element location in the list corresponds to the scheduler
+          and its run queue. The first element corresponds to scheduler
+          number 1 and so on. The information is <em>not</em> gathered
+          atomically. That is, the result is not necessarily a
+          consistent snapshot of the state, but instead quite
+          efficiently gathered.</p>
+        <p>See also
+          <seealso marker="#statistics_total_active_tasks">
+          <c>statistics(total_active_tasks)</c></seealso>,
+          <seealso marker="#statistics_run_queue_lengths">
+          <c>statistics(run_queue_lengths)</c></seealso>, and
+          <seealso marker="#statistics_total_run_queue_lengths">
+          <c>statistics(total_run_queue_lengths)</c></seealso>.</p>
       </desc>
     </func>
 
@@ -6022,11 +6062,13 @@ true</pre>
       <desc>
         <marker id="statistics_exact_reductions"></marker>
         <p>Returns the number of exact reductions.</p>
-      <note><p><c>statistics(exact_reductions)</c> is
-        a more expensive operation than
-        <seealso marker="#statistics_reductions">statistics(reductions)</seealso>,
-        especially on an Erlang machine with SMP support.</p>
-      </note>
+        <note>
+          <p><c>statistics(exact_reductions)</c> is
+            a more expensive operation than
+            <seealso marker="#statistics_reductions">
+            statistics(reductions)</seealso>,
+            especially on an Erlang machine with SMP support.</p>
+        </note>
       </desc>
     </func>
 
@@ -6035,7 +6077,7 @@ true</pre>
       <fsummary>Information about garbage collection.</fsummary>
       <desc>
         <p>Returns information about garbage collection, for example:</p>
-	  <pre>
+        <pre>
 > <input>statistics(garbage_collection).</input>
 {85,23961,0}</pre>
         <p>This information can be invalid for some implementations.</p>
@@ -6047,9 +6089,9 @@ true</pre>
       <fsummary>Information about I/O.</fsummary>
       <desc>
         <p>Returns <c><anno>Input</anno></c>,
-           which is the total number of bytes
-           received through ports, and <c><anno>Output</anno></c>,
-           which is the total number of bytes output to ports.</p>
+          which is the total number of bytes
+          received through ports, and <c><anno>Output</anno></c>,
+          which is the total number of bytes output to ports.</p>
       </desc>
     </func>
 
@@ -6058,23 +6100,21 @@ true</pre>
       <fsummary>Information about microstate accounting.</fsummary>
       <desc>
         <marker id="statistics_microstate_accounting"></marker>
-        <p>
-          Microstate accounting can be used to measure how much time the Erlang
+        <p>Microstate accounting can be used to measure how much time the Erlang
           runtime system spends doing various tasks. It is designed to be as
-          lightweight as possible, but there will be some overhead when this
+          lightweight as possible, but some overhead exists when this
           is enabled. Microstate accounting is meant to be a profiling tool
-          to help figure out performance bottlenecks.
-          To <c>start</c>/<c>stop</c>/<c>reset</c> microstate_accounting you use
-          the system_flag
-          <seealso marker="#system_flag_microstate_accounting">
-            <c>microstate_accounting</c></seealso>.
-        </p>
-        <p>
-          <c>erlang:statistics(microstate_accounting)</c> returns a list of maps
-          representing some of the OS threads within ERTS. Each map contains
-          <c>type</c> and <c>id</c> fields that can be used to identify what
+          to help finding performance bottlenecks.
+          To <c>start</c>/<c>stop</c>/<c>reset</c> microstate accounting, use
+          system flag <seealso marker="#system_flag_microstate_accounting">
+          <c>microstate_accounting</c></seealso>.</p>
+        <p><c>statistics(microstate_accounting)</c> returns a list of maps
+          representing some of the OS threads within <c>ERTS</c>. Each map
+          contains <c>type</c> and <c>id</c> fields that can be used to
+          identify what
           thread it is, and also a counters field that contains data about how
           much time has been spent in the various states.</p>
+        <p>Example:</p>
         <pre>
 > <input>erlang:statistics(microstate_accounting).</input>
 [#{counters => #{aux => 1899182914,
@@ -6085,12 +6125,11 @@ true</pre>
                  port => 221631,
                  sleep => 5150294100},
    id => 1,
-   type => scheduler}|...]
-        </pre>
+   type => scheduler}|...]</pre>
         <p>The time unit is the same as returned by
-        <seealso marker="kernel:os#perf_counter/0">
-          <c>os:perf_counter/0</c></seealso>.
-        So to convert it to milliseconds you could do something like this:</p>
+          <seealso marker="kernel:os#perf_counter/0">
+          <c>os:perf_counter/0</c></seealso> in <c>Kernel</c>.
+          So, to convert it to milliseconds, you can do something like this:</p>
         <pre>
 lists:map(
   fun(#{ counters := Cnt } = M) ->
@@ -6098,39 +6137,36 @@ lists:map(
                                    erlang:convert_time_unit(PerfCount, perf_counter, 1000)
                            end, Cnt),
          M#{ counters := MsCnt }
-  end, erlang:statistics(microstate_accounting)).
-        </pre>
-        <p>
-          It is important to note that these values are not guaranteed to be
+  end, erlang:statistics(microstate_accounting)).</pre>
+        <p>Notice that these values are not guaranteed to be
           the exact time spent in each state. This is because of various
-          optimisation done in order to keep the overhead as small as possible.
-        </p>
-
-        <p>Currently the following <c><anno>MSAcc_Thread_Type</anno></c> are available:</p>
+          optimisation done to keep the overhead as small as possible.</p>
+        <p><c><anno>MSAcc_Thread_Type</anno></c>s:</p>
         <taglist>
           <tag><c>scheduler</c></tag>
           <item>The main execution threads that do most of the work.</item>
-          <tag><c>async</c></tag><item>Async threads are used by various
-          linked-in drivers (mainly the file drivers) do offload non-cpu
-          intensive work.</item>
-          <tag><c>aux</c></tag><item>Takes care of any work that is not
-          specifically assigned to a scheduler.</item>
+          <tag><c>async</c></tag>
+          <item>Async threads are used by various linked-in drivers (mainly the
+            file drivers) do offload non-CPU intensive work.</item>
+          <tag><c>aux</c></tag>
+          <item>Takes care of any work that is not
+            specifically assigned to a scheduler.</item>
         </taglist>
-        <p>Currently the following <c><anno>MSAcc_Thread_State</anno></c>s are available.
-        All states are exclusive, meaning that a thread cannot be in two states
-        at once. So if you add the numbers of all counters in a thread
-        you will get the total run-time for that thread.</p>
+        <p>The following <c><anno>MSAcc_Thread_State</anno></c>s are available.
+          All states are exclusive, meaning that a thread cannot be in two
+          states at once. So, if you add the numbers of all counters in a
+          thread, you get the total runtime for that thread.</p>
         <taglist>
           <tag><c>aux</c></tag>
           <item>Time spent handling auxiliary jobs.</item>
           <tag><c>check_io</c></tag>
           <item>Time spent checking for new I/O events.</item>
           <tag><c>emulator</c></tag>
-          <item>Time spent executing erlang processes.</item>
+          <item>Time spent executing Erlang processes.</item>
           <tag><c>gc</c></tag>
           <item>Time spent doing garbage collection. When extra states are
-          enabled this is the time spent doing non-fullsweep garbage
-          collections.</item>
+            enabled this is the time spent doing non-fullsweep garbage
+            collections.</item>
           <tag><c>other</c></tag>
           <item>Time spent doing unaccounted things.</item>
           <tag><c>port</c></tag>
@@ -6138,61 +6174,60 @@ lists:map(
           <tag><c>sleep</c></tag>
           <item>Time spent sleeping.</item>
         </taglist>
-        <p>It is possible to add more fine grained <c><anno>MSAcc_Thread_State</anno></c>s
-        through configure.
-        (e.g. <c>./configure --with-microstate-accounting=extra</c>).
-        Enabling these states will cause a performance degradation when
-        microstate accounting is turned off and increase the overhead when
-        it is turned on.</p>
+        <p>More fine-grained <c><anno>MSAcc_Thread_State</anno></c>s can
+          be added through configure (such as
+          <c>./configure --with-microstate-accounting=extra</c>).
+          Enabling these states causes performance degradation when
+          microstate accounting is turned off and increases the overhead when
+          it is turned on.</p>
         <taglist>
           <tag><c>alloc</c></tag>
           <item>Time spent managing memory. Without extra states this time is
-          spread out over all other states.</item>
+            spread out over all other states.</item>
           <tag><c>bif</c></tag>
-          <item>Time spent in bifs. Without extra states this time is part of
-          the <c>emulator</c> state.</item>
+          <item>Time spent in BIFs. Without extra states this time is part of
+            the <c>emulator</c> state.</item>
           <tag><c>busy_wait</c></tag>
           <item>Time spent busy waiting. This is also the state where a
-          scheduler no longer reports that it is active when using
-          <seealso marker="#statistics_scheduler_wall_time">
-            <c>erlang:statistics(scheduler_wall_time)</c></seealso>.
-          So if you add all other states but this and sleep and then divide that
-          by all time in the thread you should get something very similar to the
-          scheduler_wall_time fraction. Without extra states this time is part
-          of the <c>other</c> state.</item>
+            scheduler no longer reports that it is active when using
+            <seealso marker="#statistics_scheduler_wall_time">
+            <c>statistics(scheduler_wall_time)</c></seealso>. So, if you add
+            all other states but this and sleep, and then divide that by all
+            time in the thread, you should get something very similar to the
+            <c>scheduler_wall_time</c> fraction. Without extra states this
+            time is part of the <c>other</c> state.</item>
           <tag><c>ets</c></tag>
-          <item>Time spent executing ETS bifs. Without extra states this time is
-          part of the <c>emulator</c> state.</item>
+          <item>Time spent executing <c>ets</c> BIFs. Without extra states
+            this time is part of the <c>emulator</c> state.</item>
           <tag><c>gc_full</c></tag>
           <item>Time spent doing fullsweep garbage collection. Without extra
-          states this time is part of the <c>gc</c> state.</item>
+            states this time is part of the <c>gc</c> state.</item>
           <tag><c>nif</c></tag>
-          <item>Time spent in nifs. Without extra states this time is part of
-          the <c>emulator</c> state.</item>
+          <item>Time spent in NIFs. Without extra states this time is part of
+            the <c>emulator</c> state.</item>
           <tag><c>send</c></tag>
           <item>Time spent sending messages (processes only). Without extra
-          states this time is part of the <c>emulator</c> state.</item>
+            states this time is part of the <c>emulator</c> state.</item>
           <tag><c>timers</c></tag>
           <item>Time spent managing timers. Without extra states this time is
-          part of the <c>other</c> state.</item>
+            part of the <c>other</c> state.</item>
         </taglist>
-        <p>There is a utility module called
-        <seealso marker="runtime_tools:msacc"><c>msacc</c></seealso> in
-        runtime_tools that can be used to more easily analyse these
-        statistics.</p>
-
-        <p>
-          Returns <c>undefined</c> if the system flag
+        <p>The utility module
+          <seealso marker="runtime_tools:msacc"><c>msacc</c></seealso> in the
+          <c>runtime_tools</c> spplication can be used to more easily analyse
+          these statistics.</p>
+        <p>Returns <c>undefined</c> if system flag
           <seealso marker="#system_flag_microstate_accounting">
-            <c>microstate_accounting</c></seealso>
-          is turned off.
-	</p>
-        <p>The list of thread information is unsorted and may appear in
-        different order between calls.</p>
-        <note><p>The threads and states are subject to change without any
-        prior notice.</p></note>
+          <c>microstate_accounting</c></seealso> is turned off.</p>
+        <p>The list of thread information is unsorted and can appear in
+          different order between calls.</p>
+        <note>
+          <p>The threads and states are subject to change without any
+            prior notice.</p>
+        </note>
       </desc>
     </func>
+
     <func>
       <name name="statistics" arity="1" clause_i="7"/>
       <fsummary>Information about reductions.</fsummary>
@@ -6202,11 +6237,12 @@ lists:map(
         <pre>
 > <input>statistics(reductions).</input>
 {2046,11}</pre>
-        <note><p>As from <c>ERTS</c> 5.5 (OTP R11B),
+        <note><p>As from <c>ERTS</c> 5.5 (Erlang/OTP R11B),
           this value does not include reductions performed in current
           time slices of currently scheduled processes. If an
           exact value is wanted, use
-          <seealso marker="#statistics_exact_reductions">statistics(exact_reductions)</seealso>.</p>
+          <seealso marker="#statistics_exact_reductions">
+          <c>statistics(exact_reductions)</c></seealso>.</p>
         </note>
       </desc>
     </func>
@@ -6215,15 +6251,14 @@ lists:map(
       <name name="statistics" arity="1" clause_i="8"/>
       <fsummary>Information about the run-queues.</fsummary>
       <desc><marker id="statistics_run_queue"></marker>
-        <p>
-	  Returns the total length of the run-queues. That is, the number
+        <p>Returns the total length of the run-queues. That is, the number
           of processes and ports that are ready to run on all available
-	  run-queues. The information is gathered atomically. That
-	  is, the result is a consistent snapshot of the state, but
-	  this operation is much more expensive compared to
-	  <seealso marker="#statistics_total_run_queue_lengths"><c>statistics(total_run_queue_lengths)</c></seealso>.
-	  This especially when a large amount of schedulers is used.
-	</p>
+          run-queues. The information is gathered atomically. That
+          is, the result is a consistent snapshot of the state, but
+          this operation is much more expensive compared to
+          <seealso marker="#statistics_total_run_queue_lengths">
+          <c>statistics(total_run_queue_lengths)</c></seealso>,
+          especially when a large amount of schedulers is used.</p>
       </desc>
     </func>
 
@@ -6231,19 +6266,21 @@ lists:map(
       <name name="statistics" arity="1" clause_i="9"/>
       <fsummary>Information about the run-queue lengths.</fsummary>
       <desc><marker id="statistics_run_queue_lengths"></marker>
-	<p>
-	  Returns a list where each element represents the amount
-	  of processes and ports ready to run for each run queue. The
-	  element location in the list corresponds to the run queue
-	  of a scheduler. The first element corresponds to the run
-	  queue of scheduler number 1 and so on. The information is
-	  <em>not</em> gathered atomically. That is, the result is
-	  not necessarily a consistent snapshot of the state, but
-	  instead quite efficiently gathered. See also,
-	  <seealso marker="#statistics_total_run_queue_lengths"><c>statistics(total_run_queue_lengths)</c></seealso>,
-	  <seealso marker="#statistics_active_tasks"><c>statistics(active_tasks)</c></seealso>, and
-	  <seealso marker="#statistics_total_active_tasks"><c>statistics(total_active_tasks)</c></seealso>.
-	</p>
+        <p>Returns a list where each element represents the amount
+          of processes and ports ready to run for each run queue. The
+          element location in the list corresponds to the run queue
+          of a scheduler. The first element corresponds to the run
+          queue of scheduler number 1 and so on. The information is
+          <em>not</em> gathered atomically. That is, the result is
+          not necessarily a consistent snapshot of the state, but
+          instead quite efficiently gathered.</p>
+        <p>See also
+          <seealso marker="#statistics_total_run_queue_lengths">
+          <c>statistics(total_run_queue_lengths)</c></seealso>,
+          <seealso marker="#statistics_active_tasks">
+          <c>statistics(active_tasks)</c></seealso>, and
+          <seealso marker="#statistics_total_active_tasks">
+          <c>statistics(total_active_tasks)</c></seealso>.</p>
       </desc>
     </func>
 
@@ -6253,8 +6290,8 @@ lists:map(
       <desc>
         <p>Returns information about runtime, in milliseconds.</p>
         <p>This is the sum of the runtime for all threads
-        in the Erlang runtime system and can therefore be greater
-        than the wall clock time.</p>
+          in the Erlang runtime system and can therefore be greater
+          than the wall clock time.</p>
         <p>Example:</p>
         <pre>
 > <input>statistics(runtime).</input>
@@ -6266,7 +6303,7 @@ lists:map(
       <name name="statistics" arity="1" clause_i="11"/>
       <fsummary>Information about each schedulers work time.</fsummary>
       <desc>
-      <marker id="statistics_scheduler_wall_time"></marker>
+        <marker id="statistics_scheduler_wall_time"></marker>
         <p>Returns a list of tuples with
           <c>{<anno>SchedulerId</anno>, <anno>ActiveTime</anno>,
           <anno>TotalTime</anno>}</c>, where
@@ -6274,7 +6311,8 @@ lists:map(
           <c><anno>ActiveTime</anno></c> is
           the duration the scheduler has been busy, and
           <c><anno>TotalTime</anno></c> is the total time duration since
-          <seealso marker="#system_flag_scheduler_wall_time">scheduler_wall_time</seealso>
+          <seealso marker="#system_flag_scheduler_wall_time">
+          <c>scheduler_wall_time</c></seealso>
           activation. The time unit is undefined and can be subject
           to change between releases, OSs, and system restarts.
           <c>scheduler_wall_time</c> is only to be used to
@@ -6286,28 +6324,28 @@ lists:map(
           that is:</p>
         <list type="bulleted">
           <item>Executing process code</item>
-          <item>Executing linked-in-driver or NIF code</item>
-          <item>Executing built-in-functions, or any other runtime
-            handling</item>
+          <item>Executing linked-in driver or NIF code</item>
+          <item>Executing BIFs, or any other runtime handling</item>
           <item>Garbage collecting</item>
           <item>Handling any other memory management</item>
         </list>
-          <p>Notice that a scheduler can also be busy even if the
-            OS has scheduled out the scheduler thread.</p>
+        <p>Notice that a scheduler can also be busy even if the
+          OS has scheduled out the scheduler thread.</p>
         <p>Returns <c>undefined</c> if system flag
-          <seealso marker="#system_flag_scheduler_wall_time">scheduler_wall_time</seealso>
-          is turned off.</p>
+          <seealso marker="#system_flag_scheduler_wall_time">
+          <c>scheduler_wall_time</c></seealso> is turned off.</p>
         <p>The list of scheduler information is unsorted and can
           appear in different order between calls.</p>
-        <p>Using <c>scheduler_wall_time</c> to calculate scheduler-utilization:</p>
-<pre>
+        <p>Using <c>scheduler_wall_time</c> to calculate
+          scheduler-utilization:</p>
+        <pre>
 > <input>erlang:system_flag(scheduler_wall_time, true).</input>
 false
 > <input>Ts0 = lists:sort(erlang:statistics(scheduler_wall_time)), ok.</input>
 ok</pre>
         <p>Some time later the user takes another snapshot and calculates
           scheduler-utilization per scheduler, for example:</p>
-<pre>
+        <pre>
 > <input>Ts1 = lists:sort(erlang:statistics(scheduler_wall_time)), ok.</input>
 ok
 > <input>lists:map(fun({{I, A0, T0}, {I, A1, T1}}) ->
@@ -6320,8 +6358,9 @@ ok
  {6,0.9739235846420741},
  {7,0.973237033077876},
  {8,0.9741297293248656}]</pre>
-		<p>Using the same snapshots to calculate a total scheduler-utilization:</p>
-<pre>
+        <p>Using the same snapshots to calculate a total
+          scheduler-utilization:</p>
+        <pre>
 > <input>{A, T} = lists:foldl(fun({{_, A0, T0}, {_, A1, T1}}, {Ai,Ti}) ->
 	{Ai + (A1 - A0), Ti + (T1 - T0)} end, {0, 0}, lists:zip(Ts0,Ts1)), A/T.</input>
 0.9769136803764825</pre>
@@ -6337,17 +6376,19 @@ ok
       <name name="statistics" arity="1" clause_i="12"/>
       <fsummary>Information about active processes and ports.</fsummary>
       <desc><marker id="statistics_total_active_tasks"></marker>
-	<p>
-	  Returns the total amount of active processes and ports in
-	  the system. That is, the number of processes and ports that
-	  are ready to run, or are currently running. The information
-	  is <em>not</em> gathered atomically. That is, the result
-	  is not necessarily a consistent snapshot of the state, but
-	  instead quite efficiently gathered. See also,
-	  <seealso marker="#statistics_active_tasks"><c>statistics(active_tasks)</c></seealso>,
-	  <seealso marker="#statistics_run_queue_lengths"><c>statistics(run_queue_lengths)</c></seealso>, and
-	  <seealso marker="#statistics_total_run_queue_lengths"><c>statistics(total_run_queue_lengths)</c></seealso>.
-	</p>
+        <p>Returns the total amount of active processes and ports in
+          the system. That is, the number of processes and ports that
+          are ready to run, or are currently running. The information
+          is <em>not</em> gathered atomically. That is, the result
+          is not necessarily a consistent snapshot of the state, but
+          instead quite efficiently gathered.</p>
+        <p>See also
+          <seealso marker="#statistics_active_tasks">
+          <c>statistics(active_tasks)</c></seealso>,
+          <seealso marker="#statistics_run_queue_lengths">
+          <c>statistics(run_queue_lengths)</c></seealso>, and
+          <seealso marker="#statistics_total_run_queue_lengths">
+          <c>statistics(total_run_queue_lengths)</c></seealso>.</p>
       </desc>
     </func>
 
@@ -6355,18 +6396,19 @@ ok
       <name name="statistics" arity="1" clause_i="13"/>
       <fsummary>Information about the run-queue lengths.</fsummary>
       <desc><marker id="statistics_total_run_queue_lengths"></marker>
-        <p>
-	  Returns the total length of the run-queues. That is, the number
+        <p>Returns the total length of the run queues. That is, the number
           of processes and ports that are ready to run on all available
-	  run-queues. The information is <em>not</em> gathered atomically.
-	  That is, the result is not necessarily a consistent snapshot of
-	  the state, but much more efficiently gathered compared to
-	  <seealso marker="#statistics_run_queue"><c>statistics(run_queue)</c></seealso>.
-	  See also,
-	  <seealso marker="#statistics_run_queue_lengths"><c>statistics(run_queue_lengths)</c></seealso>,
-	  <seealso marker="#statistics_total_active_tasks"><c>statistics(total_active_tasks)</c></seealso>, and
-	  <seealso marker="#statistics_active_tasks"><c>statistics(active_tasks)</c></seealso>.
-	</p>
+          run queues. The information is <em>not</em> gathered atomically.
+          That is, the result is not necessarily a consistent snapshot of
+          the state, but much more efficiently gathered compared to
+          <seealso marker="#statistics_run_queue">
+          <c>statistics(run_queue)</c></seealso>.</p>
+        <p>See also <seealso marker="#statistics_run_queue_lengths">
+          <c>statistics(run_queue_lengths)</c></seealso>,
+          <seealso marker="#statistics_total_active_tasks">
+          <c>statistics(total_active_tasks)</c></seealso>, and
+          <seealso marker="#statistics_active_tasks">
+          <c>statistics(active_tasks)</c></seealso>.</p>
       </desc>
     </func>
 
@@ -6383,12 +6425,13 @@ ok
 
     <func>
       <name name="suspend_process" arity="1"/>
-      <fsummary>Suspends a process.</fsummary>
+      <fsummary>Suspend a process.</fsummary>
       <desc>
         <p>Suspends the process identified by
-        <c><anno>Suspendee</anno></c>. The same as calling
-	<seealso marker="#suspend_process/2">erlang:suspend_process(<anno>Suspendee</anno>,
-        [])</seealso>.</p>
+          <c><anno>Suspendee</anno></c>. The same as calling
+          <seealso marker="#suspend_process/2">
+          <c>erlang:suspend_process(<anno>Suspendee</anno>,
+          [])</c></seealso>.</p>
         <warning>
           <p>This BIF is intended for debugging only.</p>
         </warning>
@@ -6397,63 +6440,64 @@ ok
 
     <func>
       <name name="suspend_process" arity="2"/>
-      <fsummary>Suspends a process.</fsummary>
+      <fsummary>Suspend a process.</fsummary>
       <desc>
         <p>Increases the suspend count on the process identified by
-	<c><anno>Suspendee</anno></c> and puts it in the suspended
-        state if it is not
-	already in that state. A suspended process will not be
-	scheduled for execution until the process has been resumed.</p>
-	<p>A process can be suspended by multiple processes and can
-	be suspended multiple times by a single process. A suspended
-	process does not leave the suspended state until its suspend 
-	count reaches zero. The suspend count of
-        <c><anno>Suspendee</anno></c> is decreased when
-	<seealso marker="#resume_process/1">erlang:resume_process(<anno>Suspendee</anno>)</seealso>
-	is called by the same process that called
-	<c>erlang:suspend_process(<anno>Suspendee</anno>)</c>.
-        All increased suspend
-	counts on other processes acquired by a process are automatically
-	decreased when the process terminates.</p>
-	<p>The options (<c><anno>Opt</anno></c>s) are as follows:</p>
+          <c><anno>Suspendee</anno></c> and puts it in the suspended
+          state if it is not
+          already in that state. A suspended process is not
+          scheduled for execution until the process has been resumed.</p>
+        <p>A process can be suspended by multiple processes and can
+          be suspended multiple times by a single process. A suspended
+          process does not leave the suspended state until its suspend 
+          count reaches zero. The suspend count of
+          <c><anno>Suspendee</anno></c> is decreased when
+          <seealso marker="#resume_process/1">
+          <c>erlang:resume_process(<anno>Suspendee</anno>)</c></seealso>
+          is called by the same process that called
+          <c>erlang:suspend_process(<anno>Suspendee</anno>)</c>.
+          All increased suspend
+          counts on other processes acquired by a process are automatically
+          decreased when the process terminates.</p>
+        <p>Options (<c><anno>Opt</anno></c>s):</p>
         <taglist>
           <tag><c>asynchronous</c></tag>
           <item>
-	  A suspend request is sent to the process identified by
-	  <c><anno>Suspendee</anno></c>. <c><anno>Suspendee</anno></c>
-          eventually suspends
-	  unless it is resumed before it could suspend. The caller
-	  of <c>erlang:suspend_process/2</c> returns immediately,
-	  regardless of whether <c><anno>Suspendee</anno></c> has
-          suspended yet or not. The point in time when
-          <c><anno>Suspendee</anno></c> suspends cannot be deduced
-          from other events in the system. It is only guaranteed that
-          <c><anno>Suspendee</anno></c> <em>eventually</em> suspends
-          (unless it
-	  is resumed). If option <c>asynchronous</c> has <em>not</em>
-	  been passed, the caller of <c>erlang:suspend_process/2</c> is
-	  blocked until <c><anno>Suspendee</anno></c> has suspended.
-	  </item>
+            <p>A suspend request is sent to the process identified by
+              <c><anno>Suspendee</anno></c>. <c><anno>Suspendee</anno></c>
+              eventually suspends
+              unless it is resumed before it could suspend. The caller
+              of <c>erlang:suspend_process/2</c> returns immediately,
+              regardless of whether <c><anno>Suspendee</anno></c> has
+              suspended yet or not. The point in time when
+              <c><anno>Suspendee</anno></c> suspends cannot be deduced
+              from other events in the system. It is only guaranteed that
+              <c><anno>Suspendee</anno></c> <em>eventually</em> suspends
+              (unless it
+              is resumed). If option <c>asynchronous</c> has <em>not</em>
+              been passed, the caller of <c>erlang:suspend_process/2</c> is
+              blocked until <c><anno>Suspendee</anno></c> has suspended.</p>
+          </item>
           <tag><c>unless_suspending</c></tag>
           <item>
-	  The process identified by <c><anno>Suspendee</anno></c> is
-          suspended unless the calling process already is suspending
-	  <c><anno>Suspendee</anno></c>.
-          If <c>unless_suspending</c> is combined
-	  with option <c>asynchronous</c>, a suspend request is
-	  sent unless the calling process already is suspending
-	  <c><anno>Suspendee</anno></c> or if a suspend request
-          already has been sent and is in transit. If the calling
-          process already is suspending <c><anno>Suspendee</anno></c>,
-          or if combined with option <c>asynchronous</c>
-	  and a send request already is in transit,
-	  <c>false</c> is returned and the suspend count on
-          <c><anno>Suspendee</anno></c> remains unchanged.
-	  </item>
+            <p>The process identified by <c><anno>Suspendee</anno></c> is
+              suspended unless the calling process already is suspending
+              <c><anno>Suspendee</anno></c>.
+              If <c>unless_suspending</c> is combined
+              with option <c>asynchronous</c>, a suspend request is
+              sent unless the calling process already is suspending
+              <c><anno>Suspendee</anno></c> or if a suspend request
+              already has been sent and is in transit. If the calling
+              process already is suspending <c><anno>Suspendee</anno></c>,
+              or if combined with option <c>asynchronous</c>
+              and a send request already is in transit,
+              <c>false</c> is returned and the suspend count on
+              <c><anno>Suspendee</anno></c> remains unchanged.</p>
+          </item>
         </taglist>
-	<p>If the suspend count on the process identified by
-	<c><anno>Suspendee</anno></c> is increased, <c>true</c>
-        is returned, otherwise <c>false</c>.</p>
+        <p>If the suspend count on the process identified by
+          <c><anno>Suspendee</anno></c> is increased, <c>true</c>
+          is returned, otherwise <c>false</c>.</p>
         <warning>
           <p>This BIF is intended for debugging only.</p>
         </warning>
@@ -6461,44 +6505,44 @@ ok
         <taglist>
           <tag><c>badarg</c></tag>
           <item>
-	  If <c><anno>Suspendee</anno></c> is not a process identifier.
-	  </item>
+            If <c><anno>Suspendee</anno></c> is not a process identifier.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	  If the process identified by <c><anno>Suspendee</anno></c>
-          is the same process
-	  as the process calling <c>erlang:suspend_process/2</c>.
-	  </item>
+            If the process identified by <c><anno>Suspendee</anno></c>
+            is the same process
+            as the process calling <c>erlang:suspend_process/2</c>.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	  If the process identified by <c><anno>Suspendee</anno></c>
-          is not alive.
-	  </item>
+            If the process identified by <c><anno>Suspendee</anno></c>
+            is not alive.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	  If the process identified by <c><anno>Suspendee</anno></c>
-          resides on another node.
-	  </item>
+            If the process identified by <c><anno>Suspendee</anno></c>
+            resides on another node.
+          </item>
           <tag><c>badarg</c></tag>
           <item>
-	  If <c><anno>OptList</anno></c> is not a proper list of valid
-          <c><anno>Opt</anno></c>s.
-	  </item>
+            If <c><anno>OptList</anno></c> is not a proper list of valid
+            <c><anno>Opt</anno></c>s.
+          </item>
           <tag><c>system_limit</c></tag>
           <item>
-	  If the process identified by <c><anno>Suspendee</anno></c>
-          has been suspended
-	  more times by the calling process than can be represented by the
-	  currently used internal data structures. The system limit is
-	  higher than 2,000,000,000 suspends and will never be lower.
-	  </item>
+            If the process identified by <c><anno>Suspendee</anno></c>
+            has been suspended
+            more times by the calling process than can be represented by the
+            currently used internal data structures. The system limit is
+            &gt; 2,000,000,000 suspends and will never be lower.
+          </item>
         </taglist>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="1"/>
-      <fsummary>Sets system flag <c>backtrace_depth</c>.</fsummary>
+      <fsummary>Set system flag <c>backtrace_depth</c>.</fsummary>
       <desc>
         <p>Sets the maximum depth of call stack back-traces in the
           exit reason element of <c>'EXIT'</c> tuples.</p>
@@ -6508,7 +6552,7 @@ ok
 
     <func>
       <name name="system_flag" arity="2" clause_i="2"/>
-      <fsummary>Sets system flag <c>cpu_topology</c>.</fsummary>
+      <fsummary>Set system flag <c>cpu_topology</c>.</fsummary>
       <type name="cpu_topology"/>
       <type name="level_entry"/>
       <type name="level_tag"/>
@@ -6517,52 +6561,52 @@ ok
       <desc>
         <warning>
           <p><marker id="system_flag_cpu_topology"></marker>
-          This argument is <em>deprecated</em> and scheduled for
-          removal in <c>ERTS</c> 5.10/OTP R16. Instead of using this
-          argument, use command-line argument
-          <seealso marker="erts:erl#+sct">+sct</seealso> in
-          <c>erl(1)</c>.</p>
+            <em>This argument is deprecated.</em>
+            Instead of using this argument, use command-line argument
+            <seealso marker="erts:erl#+sct"><c>+sct</c></seealso> in
+            <c>erl(1)</c>.</p>
           <p>When this argument is removed, a final CPU topology
-          to use is determined at emulator boot time.</p>
+            to use is determined at emulator boot time.</p>
         </warning>
         <p>Sets the user-defined <c><anno>CpuTopology</anno></c>.
-           The user-defined
-           CPU topology overrides any automatically detected
-           CPU topology. By passing <c>undefined</c> as
-           <c><anno>CpuTopology</anno></c>,
-           the system reverts to the CPU topology automatically
-           detected. The returned value equals the value returned
-           from <c>erlang:system_info(cpu_topology)</c> before the
-           change was made.</p>
+          The user-defined
+          CPU topology overrides any automatically detected
+          CPU topology. By passing <c>undefined</c> as
+          <c><anno>CpuTopology</anno></c>,
+          the system reverts to the CPU topology automatically
+          detected. The returned value equals the value returned
+          from <c>erlang:system_info(cpu_topology)</c> before the
+          change was made.</p>
         <p>Returns the old value of the flag.</p>
         <p>The CPU topology is used when binding schedulers to logical
-           processors. If schedulers are already bound when the CPU
-           topology is changed, the schedulers are sent a request
-           to rebind according to the new CPU topology.</p>
+          processors. If schedulers are already bound when the CPU
+          topology is changed, the schedulers are sent a request
+          to rebind according to the new CPU topology.</p>
         <p>The user-defined CPU topology can also be set by passing
-           command-line argument
-           <seealso marker="erts:erl#+sct">+sct</seealso> to
-           <c>erl(1)</c>.</p>
+          command-line argument
+          <seealso marker="erts:erl#+sct"><c>+sct</c></seealso> to
+          <c>erl(1)</c>.</p>
         <p>For information on type <c><anno>CpuTopology</anno></c>
-           and more, see
-           <seealso marker="#system_info_cpu_topology">erlang:system_info(cpu_topology)</seealso>
-           as well as the command-line flags
-           <seealso marker="erts:erl#+sct">+sct</seealso> and
-           <seealso marker="erts:erl#+sbt">+sbt</seealso> in
-           <c>erl(1)</c>.</p>
+          and more, see
+          <seealso marker="#system_info_cpu_topology">
+          <c>erlang:system_info(cpu_topology)</c></seealso>
+          as well as command-line flags
+          <seealso marker="erts:erl#+sct"><c>+sct</c></seealso> and
+          <seealso marker="erts:erl#+sbt"><c>+sbt</c></seealso> in
+          <c>erl(1)</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="3"/>
-      <fsummary>Sets <c>system_flag_dirty_cpu_schedulers_online</c>.</fsummary>
+      <fsummary>Set system_flag_dirty_cpu_schedulers_online.</fsummary>
       <desc>
         <p><marker id="system_flag_dirty_cpu_schedulers_online"></marker>
-        Sets the number of dirty CPU schedulers online. Range is
-        <![CDATA[1 <= DirtyCPUSchedulersOnline <= N]]>, where <c>N</c>
-        is the smallest of the return values of
-        <c>erlang:system_info(dirty_cpu_schedulers)</c> and
-        <c>erlang:system_info(schedulers_online)</c>.</p>
+          Sets the number of dirty CPU schedulers online. Range is
+          <c><![CDATA[1 <= DirtyCPUSchedulersOnline <= N]]></c>, where <c>N</c>
+          is the smallest of the return values of
+          <c>erlang:system_info(dirty_cpu_schedulers)</c> and
+          <c>erlang:system_info(schedulers_online)</c>.</p>
         <p>Returns the old value of the flag.</p>
         <p>The number of dirty CPU schedulers online can change if the
           number of schedulers online changes. For example, if 12
@@ -6573,20 +6617,22 @@ ok
           down to 3. Similarly, the number of dirty CPU schedulers
           online increases proportionally to increases in the number of
           schedulers online.</p>
-        <note><p>The dirty schedulers functionality is experimental.
-          Enable support for dirty schedulers when building OTP to
-          try out the functionality.</p>
+        <note>
+          <p>The dirty schedulers functionality is experimental.
+            Enable support for dirty schedulers when building OTP to
+            try out the functionality.</p>
         </note>
         <p>For more information, see
-        <seealso marker="#system_info_dirty_cpu_schedulers">erlang:system_info(dirty_cpu_schedulers)</seealso>
-        and
-        <seealso marker="#system_info_dirty_cpu_schedulers_online">erlang:system_info(dirty_cpu_schedulers_online)</seealso>.</p>
+          <seealso marker="#system_info_dirty_cpu_schedulers">
+          <c>erlang:system_info(dirty_cpu_schedulers)</c></seealso> and
+          <seealso marker="#system_info_dirty_cpu_schedulers_online">
+          <c>erlang:system_info(dirty_cpu_schedulers_online)</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="4"/>
-      <fsummary>Sets system flag <c>fullsweep_after</c>.</fsummary>
+      <fsummary>Set system flag fullsweep_after.</fsummary>
       <desc>
         <p>Sets system flag <c>fullsweep_after</c>.
           <c><anno>Number</anno></c> is a non-negative integer indicating
@@ -6605,43 +6651,45 @@ ok
 
     <func>
       <name name="system_flag" arity="2" clause_i="5"/>
-      <fsummary>Set system flag microstate_accounting</fsummary>
-      <desc><p><marker id="system_flag_microstate_accounting"></marker>
-      Turns on/off microstate accounting measurements. By passing reset it is possible to reset
-      all counters to 0.</p>
-      <p>For more information see,
-      <seealso marker="#statistics_microstate_accounting">erlang:statistics(microstate_accounting)</seealso>.
-      </p>
+      <fsummary>Set system flag microstate_accounting.</fsummary>
+      <desc>
+        <p><marker id="system_flag_microstate_accounting"></marker>
+          Turns on/off microstate accounting measurements. By passing reset,
+          all counters can be reset to 0.</p>
+        <p>For more information see
+          <seealso marker="#statistics_microstate_accounting">
+          <c>statistics(microstate_accounting)</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="system_flag" arity="2" clause_i="6"/>
-      <fsummary>Sets system flag <c>min_heap_size</c>.</fsummary>
+      <fsummary>Set system flag min_heap_size.</fsummary>
       <desc>
         <p>Sets the default minimum heap size for processes. The size
-          is given in words. The new <c>min_heap_size</c> effects
+          is specified in words. The new <c>min_heap_size</c> effects
           only processes spawned after the change of
           <c>min_heap_size</c> has been made. <c>min_heap_size</c>
           can be set for individual processes by using
-          <seealso marker="#spawn_opt/4">spawn_opt/N</seealso> or
-          <seealso marker="#process_flag/2">process_flag/2</seealso>.</p>
+          <seealso marker="#spawn_opt/4"><c>spawn_opt/4</c></seealso> or
+          <seealso marker="#process_flag/2"><c>process_flag/2</c></seealso>.</p>
         <p>Returns the old value of the flag.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="7"/>
-      <fsummary>Sets system flag <c>min_bin_vheap_size</c>.</fsummary>
+      <fsummary>Set system flag min_bin_vheap_size.</fsummary>
       <desc>
         <p>Sets the default minimum binary virtual heap size for
-          processes. The size is given in words.
+          processes. The size is specified in words.
           The new <c>min_bin_vhheap_size</c> effects only
           processes spawned after the change of
           <c>min_bin_vhheap_size</c> has been made.
           <c>min_bin_vheap_size</c> can be set for individual
           processes by using
-          <seealso marker="#spawn_opt/4">spawn_opt/N</seealso> or
-          <seealso marker="#process_flag/2">process_flag/2</seealso>.</p>
+          <seealso marker="#spawn_opt/4"><c>spawn_opt/4</c></seealso> or
+          <seealso marker="#process_flag/2"><c>process_flag/2</c></seealso>.</p>
         <p>Returns the old value of the flag.</p>
       </desc>
     </func>
@@ -6649,241 +6697,251 @@ ok
     <marker id="system_flag_max_heap_size"></marker>
     <func>
       <name name="system_flag" arity="2" clause_i="8"/>
-      <fsummary>Sets system flag <c>max_heap_size</c></fsummary>
+      <fsummary>Set system flag max_heap_size.</fsummary>
       <type name="max_heap_size"/>
       <desc>
         <p>
           Sets the default maximum heap size settings for processes.
-          The size is given in words. The new <c>max_heap_size</c>
+          The size is specified in words. The new <c>max_heap_size</c>
           effects only processes spawned efter the change has been made.
           <c>max_heap_size</c> can be set for individual processes using
-          <seealso marker="#spawn_opt/4">spawn_opt/N</seealso> or
-          <seealso marker="#process_flag_message_queue_data">process_flag/2</seealso>.</p>
+          <seealso marker="#spawn_opt/4"><c>spawn_opt/4</c></seealso> or
+          <seealso marker="#process_flag_message_queue_data">
+          <c>process_flag/2</c></seealso>.</p>
         <p>Returns the old value of the flag.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="9"/>
-      <fsummary>Sets system flag <c>multi_scheduling</c>.</fsummary>
+      <fsummary>Set system flag multi_scheduling.</fsummary>
       <desc>
         <p><marker id="system_flag_multi_scheduling"></marker>
           If multi-scheduling is enabled, more than one scheduler
           thread is used by the emulator. Multi-scheduling can be
           blocked in two different ways. Either all schedulers but
-	  one is blocked, or all <em>normal</em> schedulers but
-	  one is blocked. When only normal schedulers are blocked
-	  dirty schedulers are free to continue to schedule
-	  processes.</p>
+          one is blocked, or all <em>normal</em> schedulers but
+          one is blocked. When only normal schedulers are blocked,
+          dirty schedulers are free to continue to schedule
+          processes.</p>
         <p>If <c><anno>BlockState</anno> =:= block</c>, multi-scheduling is
           blocked. That is, one and only one scheduler thread will
-	  execute. If <c><anno>BlockState</anno> =:= unblock</c> and no one
+          execute. If <c><anno>BlockState</anno> =:= unblock</c> and no one
           else blocks multi-scheduling, and this process has
           blocked only once, multi-scheduling is unblocked.</p>
         <p>If <c><anno>BlockState</anno> =:= block_normal</c>, normal
-	  multi-scheduling is blocked. That is, only one normal scheduler
-	  thread will execute, but multiple dirty schedulers may execute.
-	  If <c><anno>BlockState</anno> =:= unblock_normal</c> and no one
+          multi-scheduling is blocked. That is, only one normal scheduler
+          thread will execute, but multiple dirty schedulers can execute.
+          If <c><anno>BlockState</anno> =:= unblock_normal</c> and no one
           else blocks normal multi-scheduling, and this process has
           blocked only once, normal multi-scheduling is unblocked.</p>
-        <p>One process can block multi-scheduling as well as normal
-	  multi-scheduling multiple times. If a process has blocked
-	  multiple times, it must unblock exactly as many times as it
-	  has blocked before it has released its multi-scheduling
-	  block. If a process that has blocked multi-scheduling or normal
-	  multi scheduling exits, it automatically releases its blocking
-	  of multi-scheduling and normal multi-scheduling.</p>
+        <p>One process can block multi-scheduling and normal
+          multi-scheduling multiple times. If a process has blocked
+          multiple times, it must unblock exactly as many times as it
+          has blocked before it has released its multi-scheduling
+          block. If a process that has blocked multi-scheduling or normal
+          multi-scheduling exits, it automatically releases its blocking
+          of multi-scheduling and normal multi-scheduling.</p>
         <p>The return values are <c>disabled</c>, <c>blocked</c>,
           <c>blocked_normal</c>, or <c>enabled</c>. The returned value
-	  describes the state just after the call to
+          describes the state just after the call to
           <c>erlang:system_flag(multi_scheduling, <anno>BlockState</anno>)</c>
           has been made. For information about the return values, see
-          <seealso marker="#system_info_multi_scheduling">erlang:system_info(multi_scheduling)</seealso>.</p>
+          <seealso marker="#system_info_multi_scheduling">
+          <c>erlang:system_info(multi_scheduling)</c></seealso>.</p>
         <note><p>Blocking of multi-scheduling and normal multi-scheduling
-	  is normally not needed. If you feel that you need to use these
-	  features, consider it a few more times again. Blocking
-	  multi-scheduling is only to be used as a last resort, as it is
-	  most likely a <em>very inefficient</em> way to solve the problem.</p>
+          is normally not needed. If you feel that you need to use these
+          features, consider it a few more times again. Blocking
+          multi-scheduling is only to be used as a last resort, as it is
+          most likely a <em>very inefficient</em> way to solve the problem.</p>
         </note>
         <p>See also
-          <seealso marker="#system_info_multi_scheduling">erlang:system_info(multi_scheduling)</seealso>,
-          <seealso marker="#system_info_normal_multi_scheduling_blockers">erlang:system_info(normal_multi_scheduling_blockers)</seealso>,
-          <seealso marker="#system_info_multi_scheduling_blockers">erlang:system_info(multi_scheduling_blockers)</seealso>, and
-          <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>.</p>
+          <seealso marker="#system_info_multi_scheduling">
+          <c>erlang:system_info(multi_scheduling)</c></seealso>,
+          <seealso marker="#system_info_normal_multi_scheduling_blockers">
+          <c>erlang:system_info(normal_multi_scheduling_blockers)</c></seealso>,
+          <seealso marker="#system_info_multi_scheduling_blockers">
+          <c>erlang:system_info(multi_scheduling_blockers)</c></seealso>, and
+          <seealso marker="#system_info_schedulers">
+          <c>erlang:system_info(schedulers)</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="10"/>
-      <fsummary>Sets system flag <c>scheduler_bind_type</c>.</fsummary>
+      <fsummary>Set system flag scheduler_bind_type.</fsummary>
       <type name="scheduler_bind_type"/>
       <desc>
         <warning>
           <p><marker id="system_flag_scheduler_bind_type"></marker>
-          This argument is <em>deprecated</em> and scheduled for
-          removal in <c>ERTS</c> 5.10/OTP R16. Instead of using this
-          argument, use command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt</seealso> in <c>erl(1)</c>.
-          When this argument is removed, a final scheduler bind
-          type to use is determined at emulator boot time.</p>
+            <em>This argument is deprecated.</em>
+            Instead of using this argument, use command-line argument
+            <seealso marker="erts:erl#+sbt"><c>+sbt</c></seealso> in
+            <c>erl(1)</c>. When this argument is removed, a final scheduler bind
+            type to use is determined at emulator boot time.</p>
         </warning>
         <p>Controls if and how schedulers are bound to logical
-           processors.</p>
+          processors.</p>
         <p>When <c>erlang:system_flag(scheduler_bind_type, <anno>How</anno>)</c>
-           is called, an asynchronous signal is sent to all schedulers
-           online, causing them to try to bind or unbind as requested.</p>
+          is called, an asynchronous signal is sent to all schedulers
+          online, causing them to try to bind or unbind as requested.</p>
         <note><p>If a scheduler fails to bind, this is often silently
-           ignored, as it is not always possible to verify valid
-           logical processor identifiers. If an error is reported,
-           it is reported to <c>error_logger</c>. To verify that the
-           schedulers have bound as requested, call
-           <seealso marker="#system_info_scheduler_bindings">erlang:system_info(scheduler_bindings)</seealso>.</p>
+          ignored, as it is not always possible to verify valid
+          logical processor identifiers. If an error is reported,
+          it is reported to <c>error_logger</c>. To verify that the
+          schedulers have bound as requested, call
+          <seealso marker="#system_info_scheduler_bindings">
+          <c>erlang:system_info(scheduler_bindings)</c></seealso>.</p>
         </note>
         <p>Schedulers can be bound on newer Linux,
-           Solaris, FreeBSD, and Windows systems, but more systems will be
-           supported in future releases.</p>
+          Solaris, FreeBSD, and Windows systems, but more systems will be
+          supported in future releases.</p>
         <p>In order for the runtime system to be able to bind schedulers,
-           the CPU topology must be known. If the runtime system fails
-           to detect the CPU topology automatically, it can be defined.
-           For more information on how to define the CPU topology, see
-           command-line flag <seealso marker="erts:erl#+sct">+sct</seealso>
-           in <c>erl(1)</c>.</p>
+          the CPU topology must be known. If the runtime system fails
+          to detect the CPU topology automatically, it can be defined.
+          For more information on how to define the CPU topology, see
+          command-line flag <seealso marker="erts:erl#+sct">
+          <c>+sct</c></seealso> in <c>erl(1)</c>.</p>
         <p>The runtime system does by default <em>not</em> bind schedulers
-           to logical processors.</p>
+          to logical processors.</p>
         <note><p>If the Erlang runtime system is the only OS
-           process binding threads to logical processors, this
-           improves the performance of the runtime system. However,
-           if other OS processes (for example, another Erlang
-           runtime system) also bind threads to logical processors,
-           there can be a performance penalty instead. Sometimes this
-           performance penalty can be severe. If so, it is recommended
-           to not bind the schedulers.</p>
+          process binding threads to logical processors, this
+          improves the performance of the runtime system. However,
+          if other OS processes (for example, another Erlang
+          runtime system) also bind threads to logical processors,
+          there can be a performance penalty instead. Sometimes this
+          performance penalty can be severe. If so, it is recommended
+          to not bind the schedulers.</p>
         </note>
         <p>Schedulers can be bound in different ways. Argument
-           <c><anno>How</anno></c> determines how schedulers are
-           bound and can be any of the following:</p>
+          <c><anno>How</anno></c> determines how schedulers are
+          bound and can be any of the following:</p>
         <taglist>
           <tag><c>unbound</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt u</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt u</c></seealso> in
+            <c>erl(1)</c>.
+          </item>
           <tag><c>no_spread</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt ns</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt ns</c></seealso>
+            in <c>erl(1)</c>.
+          </item>
           <tag><c>thread_spread</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt ts</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt ts</c></seealso>
+            in <c>erl(1)</c>.
+          </item>
           <tag><c>processor_spread</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt ps</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt ps</c></seealso>
+          in <c>erl(1)</c>.
+          </item>
           <tag><c>spread</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt s</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt s</c></seealso>
+            in <c>erl(1)</c>.
+          </item>
           <tag><c>no_node_thread_spread</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt nnts</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt nnts</c></seealso>
+            in <c>erl(1)</c>.
+          </item>
           <tag><c>no_node_processor_spread</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt nnps</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt nnps</c></seealso>
+            in <c>erl(1)</c>.
+          </item>
           <tag><c>thread_no_node_processor_spread</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt tnnps</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt tnnps</c></seealso>
+            in <c>erl(1)</c>.
+          </item>
           <tag><c>default_bind</c></tag>
-          <item>
-            <p>Same as command-line argument
-          <seealso marker="erts:erl#+sbt">+sbt db</seealso> in <c>erl(1)</c>.
-          </p></item>
+          <item>Same as command-line argument
+          <seealso marker="erts:erl#+sbt"><c>+sbt db</c></seealso>
+            in <c>erl(1)</c>.
+          </item>
         </taglist>
         <p>The returned value equals <c><anno>How</anno></c> before flag
            <c>scheduler_bind_type</c> was changed.</p>
         <p>Failures:</p>
         <taglist>
           <tag><c>notsup</c></tag>
-          <item>
-            <p>If binding of schedulers is not supported.</p>
+          <item>If binding of schedulers is not supported.
           </item>
           <tag><c>badarg</c></tag>
-          <item>
-            <p>If <c><anno>How</anno></c> is not one of the documented
-            alternatives.</p>
+          <item>If <c><anno>How</anno></c> is not one of the documented
+            alternatives.
           </item>
           <tag><c>badarg</c></tag>
-          <item>
-            <p>If CPU topology information is unavailable.</p>
+          <item>If CPU topology information is unavailable.
           </item>
         </taglist>
-        <p>The scheduler bind type can also be set by passing
-           command-line argument
-           <seealso marker="erts:erl#+sbt">+sbt</seealso> to <c>erl(1)</c>.</p>
+        <p>The scheduler bind type can also be set by passing command-line
+          argument <seealso marker="erts:erl#+sbt">
+          <c>+sbt</c></seealso> to <c>erl(1)</c>.</p>
         <p>For more information, see
-           <seealso marker="#system_info_scheduler_bind_type">erlang:system_info(scheduler_bind_type)</seealso>,
-           <seealso marker="#system_info_scheduler_bindings">erlang:system_info(scheduler_bindings)</seealso>,
-           as well as command-line flags
-           <seealso marker="erts:erl#+sbt">+sbt</seealso>
-           and <seealso marker="erts:erl#+sct">+sct</seealso>
-           in <c>erl(1)</c>.</p>
+          <seealso marker="#system_info_scheduler_bind_type">
+          <c>erlang:system_info(scheduler_bind_type)</c></seealso>,
+          <seealso marker="#system_info_scheduler_bindings">
+          <c>erlang:system_info(scheduler_bindings)</c></seealso>,
+          as well as command-line flags
+          <seealso marker="erts:erl#+sbt"><c>+sbt</c></seealso>
+          and <seealso marker="erts:erl#+sct"><c>+sct</c></seealso>
+          in <c>erl(1)</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="11"/>
-      <fsummary>Sets system flag <c>scheduler_wall_time</c>.</fsummary>
-      <desc><p><marker id="system_flag_scheduler_wall_time"></marker>
-      Turns on or off scheduler wall time measurements.</p>
-      <p>For more information, see
-      <seealso marker="#statistics_scheduler_wall_time">erlang:statistics(scheduler_wall_time)</seealso>.</p>
+      <fsummary>Set system flag scheduler_wall_time.</fsummary>
+      <desc>
+        <p><marker id="system_flag_scheduler_wall_time"></marker>
+          Turns on or off scheduler wall time measurements.</p>
+        <p>For more information, see
+          <seealso marker="#statistics_scheduler_wall_time">
+          <c>statistics(scheduler_wall_time)</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="12"/>
-      <fsummary>Sets system flag <c>schedulers_online</c>.</fsummary>
+      <fsummary>Set system flag schedulers_online.</fsummary>
       <desc>
         <p><marker id="system_flag_schedulers_online"></marker>
-        Sets the number of schedulers online. Range is
-        <![CDATA[1 <= SchedulersOnline <= erlang:system_info(schedulers)]]>.</p>
+          Sets the number of schedulers online. Range is
+          <c><![CDATA[1 <= SchedulersOnline <=
+          erlang:system_info(schedulers)]]></c>.</p>
         <p>Returns the old value of the flag.</p>
         <p>If the emulator was built with support for
-        <seealso marker="#system_flag_dirty_cpu_schedulers_online">dirty schedulers</seealso>,
-        changing the number of schedulers online can also change the
-        number of dirty CPU schedulers online. For example, if 12
-        schedulers and 6 dirty CPU schedulers are online, and
-        <c>system_flag/2</c> is used to set the number of schedulers
-        online to 6, then the number of dirty CPU schedulers online
-        is automatically decreased by half as well, down to 3.
-        Similarly, the number of dirty CPU schedulers online increases
-        proportionally to increases in the number of schedulers online.</p>
+          <seealso marker="#system_flag_dirty_cpu_schedulers_online">
+          dirty schedulers</seealso>,
+          changing the number of schedulers online can also change the
+          number of dirty CPU schedulers online. For example, if 12
+          schedulers and 6 dirty CPU schedulers are online, and
+          <c>system_flag/2</c> is used to set the number of schedulers
+          online to 6, then the number of dirty CPU schedulers online
+          is automatically decreased by half as well, down to 3.
+          Similarly, the number of dirty CPU schedulers online increases
+          proportionally to increases in the number of schedulers online.</p>
         <p>For more information, see
-        <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>
-        and
-        <seealso marker="#system_info_schedulers_online">erlang:system_info(schedulers_online)</seealso>.</p>
+          <seealso marker="#system_info_schedulers">
+          <c>erlang:system_info(schedulers)</c></seealso> and
+          <seealso marker="#system_info_schedulers_online">
+          <c>erlang:system_info(schedulers_online)</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_flag" arity="2" clause_i="13"/>
-      <fsummary>Sets system flag <c>trace_control_word</c>.</fsummary>
+      <fsummary>Set system flag trace_control_word.</fsummary>
       <desc>
         <p>Sets the value of the node trace control word to
           <c><anno>TCW</anno></c>, which is to be an unsigned integer.
-          For more information, see the function
-          <seealso marker="erts:match_spec#set_tcw">set_tcw</seealso>
-          in Section "Match Specifications in Erlang" in the
+          For more information, see function
+          <seealso marker="erts:match_spec#set_tcw"><c>set_tcw</c></seealso>
+          in section "Match Specifications in Erlang" in the
           User's Guide.</p>
         <p>Returns the old value of the flag.</p>
       </desc>
@@ -6891,32 +6949,30 @@ ok
 
     <func>
       <name name="system_flag" arity="2" clause_i="14"/>
-      <fsummary>Finalize the Time Offset</fsummary>
+      <fsummary>Finalize the time offset.</fsummary>
       <desc>
         <p><marker id="system_flag_time_offset"></marker>
-	Finalizes the <seealso marker="#time_offset/0">time offset</seealso>
-	when <seealso marker="time_correction#Single_Time_Warp_Mode">single
-	time warp mode</seealso> is used. If another time warp mode
-	is used, the time offset state is left unchanged.</p>
-        <p>Returns the old state identifier. That is:</p>
-	<list>
-	  <item>
-            <p>If <c>preliminary</c> is returned, finalization was
-	  performed and the time offset is now final.</p></item>
-
-	  <item>
-            <p>If <c>final</c> is returned, the time offset was
-	  already in the final state. This either because another
-	  <c>erlang:system_flag(time_offset, finalize)</c> call, or
-	  because <seealso marker="time_correction#No_Time_Warp_Mode">no
-	  time warp mode</seealso> is used.</p></item>
-
-	  <item>
-            <p>If <c>volatile</c> is returned, the time offset
-	  cannot be finalized because
-	  <seealso marker="time_correction#Multi_Time_Warp_Mode">multi
-	  time warp mode</seealso> is used.</p></item>
-	</list>
+          Finalizes the <seealso marker="#time_offset/0">time offset</seealso>
+          when <seealso marker="time_correction#Single_Time_Warp_Mode">single
+          time warp mode</seealso> is used. If another time warp mode
+          is used, the time offset state is left unchanged.</p>
+        <p>Returns the old state identifier, that is:</p>
+        <list>
+          <item><p>If <c>preliminary</c> is returned, finalization was
+            performed and the time offset is now final.</p>
+          </item>
+          <item><p>If <c>final</c> is returned, the time offset was
+            already in the final state. This either because another
+            <c>erlang:system_flag(time_offset, finalize)</c> call or
+            because <seealso marker="time_correction#No_Time_Warp_Mode">no
+            time warp mode</seealso> is used.</p>
+          </item>
+          <item><p>If <c>volatile</c> is returned, the time offset
+            cannot be finalized because
+            <seealso marker="time_correction#Multi_Time_Warp_Mode">multi-time
+            warp mode</seealso> is used.</p>
+          </item>
+        </list>
       </desc>
     </func>
 
@@ -6933,7 +6989,7 @@ ok
       <type variable="Settings" name_i="2"/>
       <type variable="Alloc" name_i="3"/>
       <desc>
-      <marker id="system_info_allocator_tags"></marker>
+        <marker id="system_info_allocator_tags"></marker>
         <p>Returns various information about the allocators of the
           current system (emulator) as specified by
           <c><anno>Item</anno></c>:</p>
@@ -6952,17 +7008,18 @@ ok
             <p><c>erlang:system_info(allocated_areas)</c> is intended
               for debugging, and the content is highly
               implementation-dependent. The content of the results
-             therefore changes when needed without prior notice.</p>
+              therefore changes when needed without prior notice.</p>
             <p>Notice that the sum of these values is <em>not</em>
               the total amount of memory allocated by the emulator.
               Some values are part of other values, and some memory
               areas are not part of the result. For information about
               the total amount of memory allocated by the emulator, see
-              <seealso marker="#memory/0">erlang:memory/0,1</seealso>.</p>
+              <seealso marker="#memory/0">
+              <c>erlang:memory/0,1</c></seealso>.</p>
           </item>
           <tag><c>allocator</c></tag>
           <item>
-          <marker id="system_info_allocator"></marker>
+            <marker id="system_info_allocator"></marker>
             <p>Returns <c>{<anno>Allocator</anno>, <anno>Version</anno>,
               <anno>Features</anno>, <anno>Settings</anno></c>, where:</p>
             <list type="bulleted">
@@ -6992,27 +7049,30 @@ ok
               </item>
             </list>
             <p>See also "System Flags Effecting erts_alloc" in
-              <seealso marker="erts:erts_alloc#flags">erts_alloc(3)</seealso>.</p>
+              <seealso marker="erts:erts_alloc#flags">
+              <c>erts_alloc(3)</c></seealso>.</p>
           </item>
           <tag><c>alloc_util_allocators</c></tag>
           <item>
-          <marker id="system_info_alloc_util_allocators"></marker>
-	     <p>Returns a list of the names of all allocators using
-	        the <c>ERTS</c> internal <c>alloc_util</c> framework
-		as atoms. For more information, see Section
-	        <seealso marker="erts:erts_alloc#alloc_util">"The
-		alloc_util framework" in erts_alloc(3)</seealso>.</p>
+            <marker id="system_info_alloc_util_allocators"></marker>
+            <p>Returns a list of the names of all allocators using
+              the <c>ERTS</c> internal <c>alloc_util</c> framework
+              as atoms. For more information, see section
+              <seealso marker="erts:erts_alloc#alloc_util">The
+              alloc_util framework</seealso>
+              in <c>erts_alloc(3)</c>.</p>
           </item>
           <tag><c>{allocator, <anno>Alloc</anno>}</c></tag>
           <item>
-          <marker id="system_info_allocator_tuple"></marker>
+            <marker id="system_info_allocator_tuple"></marker>
             <p>Returns information about the specified allocator.
-	       As from <c>ERTS</c> 5.6.1, the return value is a list
-	       of <c>{instance, InstanceNo, InstanceInfo}</c> tuples,
-	       where <c>InstanceInfo</c> contains information about
-	       a specific instance of the allocator. If <c><anno>Alloc</anno></c> is not a
-               recognized allocator, <c>undefined</c> is returned.
-               If <c><anno>Alloc</anno></c> is disabled,
+              As from <c>ERTS</c> 5.6.1, the return value is a list
+              of <c>{instance, InstanceNo, InstanceInfo}</c> tuples,
+              where <c>InstanceInfo</c> contains information about
+              a specific instance of the allocator.
+              If <c><anno>Alloc</anno></c> is not a
+              recognized allocator, <c>undefined</c> is returned.
+              If <c><anno>Alloc</anno></c> is disabled,
               <c>false</c> is returned.</p>
             <p>Notice that the information returned is highly
               implementation-dependent and can be changed or removed
@@ -7021,15 +7081,14 @@ ok
               as it can be of interest for others it has been
               briefly documented.</p>
             <p>The recognized allocators are listed in
-              <seealso marker="erts:erts_alloc">erts_alloc(3)</seealso>.
-	      Information about super carriers can be obtained from
-	      <c>ERTS</c> 8.0 with <c>{allocator, erts_mmap}</c> or from
-	      <c>ERTS</c> 5.10.4, the returned list when calling with
-	      <c>{allocator, mseg_alloc}</c> also includes an
-	      <c>{erts_mmap, _}</c> tuple as one element in the list.</p>
-
+              <seealso marker="erts:erts_alloc"><c>erts_alloc(3)</c></seealso>.
+              Information about super carriers can be obtained from
+              <c>ERTS</c> 8.0 with <c>{allocator, erts_mmap}</c> or from
+              <c>ERTS</c> 5.10.4; the returned list when calling with
+              <c>{allocator, mseg_alloc}</c> also includes an
+              <c>{erts_mmap, _}</c> tuple as one element in the list.</p>
             <p>After reading the <c>erts_alloc(3)</c> documentation,
-	      the returned information
+              the returned information
               more or less speaks for itself, but it can be worth
               explaining some things. Call counts are presented by two
               values, the first value is giga calls, and the second
@@ -7045,19 +7104,20 @@ ok
               <item>The third is the maximum value since the emulator
                 was started.</item>
             </list>
-              <p>If only one value is present, it is the current value.
+            <p>If only one value is present, it is the current value.
               <c>fix_alloc</c> memory block types are presented by two
               values. The first value is the memory pool size and
               the second value is the used memory size.</p>
           </item>
           <tag><c>{allocator_sizes, <anno>Alloc</anno>}</c></tag>
           <item>
-          <marker id="system_info_allocator_sizes"></marker>
-	    <p>Returns various size information for the specified
-	    allocator. The information returned is a subset of the
-	    information returned by
-	    <seealso marker="#system_info_allocator_tuple"><c>erlang:system_info({allocator, <anno>Alloc</anno>})</c></seealso>.
-	    </p>
+            <marker id="system_info_allocator_sizes"></marker>
+            <p>Returns various size information for the specified
+              allocator. The information returned is a subset of the
+              information returned by
+              <seealso marker="#system_info_allocator_tuple">
+              <c>erlang:system_info({allocator,
+              <anno>Alloc</anno>})</c></seealso>.</p>
           </item>
         </taglist>
       </desc>
@@ -7091,69 +7151,74 @@ ok
         The <c>info_list()</c> can be extended in a future release.
       </type_desc>
       <desc>
-      <marker id="system_info_cpu_topology_tags"></marker>
-      <marker id="system_info_cpu_topology"></marker>
+        <marker id="system_info_cpu_topology_tags"></marker>
+        <marker id="system_info_cpu_topology"></marker>
         <p>Returns various information about the CPU topology of
           the current system (emulator) as specified by
           <c><anno>Item</anno></c>:</p>
         <taglist>
           <tag><c>cpu_topology</c></tag>
           <item>
-	    <p>Returns the <c><anno>CpuTopology</anno></c> currently used by
-	       the emulator. The CPU topology is used when binding schedulers
-	       to logical processors. The CPU topology used is the
-	       <seealso marker="erlang#system_info_cpu_topology_defined">user-defined CPU topology</seealso>,
-               if such exists, otherwise the
-	       <seealso marker="erlang#system_info_cpu_topology_detected">automatically detected CPU topology</seealso>,
-               if such exists. If no CPU topology
-	       exists, <c>undefined</c> is returned.</p>
-	    <p><c>node</c> refers to Non-Uniform Memory Access (NUMA)
-	       nodes. <c>thread</c> refers to hardware threads
-	       (for example, Intel hyper-threads).</p>
+            <p>Returns the <c><anno>CpuTopology</anno></c> currently used by
+              the emulator. The CPU topology is used when binding schedulers
+              to logical processors. The CPU topology used is the
+              <seealso marker="erlang#system_info_cpu_topology_defined">
+              user-defined CPU topology</seealso>,
+              if such exists, otherwise the
+              <seealso marker="erlang#system_info_cpu_topology_detected">
+              automatically detected CPU topology</seealso>,
+              if such exists. If no CPU topology
+              exists, <c>undefined</c> is returned.</p>
+            <p><c>node</c> refers to Non-Uniform Memory Access (NUMA)
+              nodes. <c>thread</c> refers to hardware threads
+              (for example, Intel hyper-threads).</p>
             <p>A level in term <c><anno>CpuTopology</anno></c> can be
-               omitted if only one entry exists and
-               <c><anno>InfoList</anno></c> is empty.</p>
-	    <p><c>thread</c> can only be a sub level to <c>core</c>.
-	       <c>core</c> can be a sub level to <c>processor</c>
-	       or <c>node</c>. <c>processor</c> can be on the
-	       top level or a sub level to <c>node</c>. <c>node</c>
-	       can be on the top level or a sub level to
-	       <c>processor</c>. That is, NUMA nodes can be processor
-	       internal or processor external. A CPU topology can
-	       consist of a mix of processor internal and external
-	       NUMA nodes, as long as each logical CPU belongs to
-	       <em>one</em> NUMA node. Cache hierarchy is not part of
-	       the <c><anno>CpuTopology</anno></c> type, but will be in a
-               future release. Other things can also make it into the CPU
-	       topology in a future release. In other words, expect the
-	       <c><anno>CpuTopology</anno></c> type to change.</p>
+              omitted if only one entry exists and
+              <c><anno>InfoList</anno></c> is empty.</p>
+            <p><c>thread</c> can only be a sublevel to <c>core</c>.
+              <c>core</c> can be a sublevel to <c>processor</c>
+              or <c>node</c>. <c>processor</c> can be on the
+              top level or a sublevel to <c>node</c>. <c>node</c>
+              can be on the top level or a sublevel to
+              <c>processor</c>. That is, NUMA nodes can be processor
+              internal or processor external. A CPU topology can
+              consist of a mix of processor internal and external
+              NUMA nodes, as long as each logical CPU belongs to
+              <em>one</em> NUMA node. Cache hierarchy is not part of
+              the <c><anno>CpuTopology</anno></c> type, but will be in a
+              future release. Other things can also make it into the CPU
+              topology in a future release. So, expect the
+              <c><anno>CpuTopology</anno></c> type to change.</p>
           </item>
           <tag><c>{cpu_topology, defined}</c></tag>
           <item>
-          <marker id="system_info_cpu_topology_defined"></marker>
+            <marker id="system_info_cpu_topology_defined"></marker>
             <p>Returns the user-defined <c><anno>CpuTopology</anno></c>.
-               For more information, see command-line flag
-	       <seealso marker="erts:erl#+sct">+sct</seealso> in
-	       <c>erl(1)</c> and argument
-	       <seealso marker="#system_info_cpu_topology">cpu_topology</seealso>.</p>
+              For more information, see command-line flag
+              <seealso marker="erts:erl#+sct"><c>+sct</c></seealso> in
+              <c>erl(1)</c> and argument
+              <seealso marker="#system_info_cpu_topology">
+              <c>cpu_topology</c></seealso>.</p>
           </item>
           <tag><c>{cpu_topology, detected}</c></tag>
           <item>
-          <marker id="system_info_cpu_topology_detected"></marker>
+            <marker id="system_info_cpu_topology_detected"></marker>
             <p>Returns the automatically detected
-               <c><anno>CpuTopology</anno>y</c>. The
-	       emulator detects the CPU topology on some newer
-	       Linux, Solaris, FreeBSD, and Windows systems.
-               On Windows system with more than 32 logical processors,
-               the CPU topology is not detected.</p>
+              <c><anno>CpuTopology</anno>y</c>. The
+              emulator detects the CPU topology on some newer
+              Linux, Solaris, FreeBSD, and Windows systems.
+              On Windows system with more than 32 logical processors,
+              the CPU topology is not detected.</p>
             <p>For more information, see argument
-	       <seealso marker="#system_info_cpu_topology">cpu_topology</seealso>.</p>
+              <seealso marker="#system_info_cpu_topology">
+              <c>cpu_topology</c></seealso>.</p>
           </item>
           <tag><c>{cpu_topology, used}</c></tag>
           <item>
             <p>Returns <c><anno>CpuTopology</anno></c> used by the emulator.
               For more information, see argument
-	       <seealso marker="#system_info_cpu_topology">cpu_topology</seealso>.</p>
+              <seealso marker="#system_info_cpu_topology">
+              <c>cpu_topology</c></seealso>.</p>
           </item>
         </taglist>
       </desc>
@@ -7170,13 +7235,14 @@ ok
       <type name="message_queue_data"/>
       <type name="max_heap_size"/>
       <desc>
+        <p>Returns information about the default process heap settings:</p>
         <taglist>
           <tag><c>fullsweep_after</c></tag>
           <item>
             <p>Returns <c>{fullsweep_after, integer() >= 0}</c>, which is
               the <c>fullsweep_after</c> garbage collection setting used
               by default. For more information, see
-              <c>garbage_collection</c> described in the following.</p>
+              <c>garbage_collection</c> described below.</p>
           </item>
           <tag><c>garbage_collection</c></tag>
           <item>
@@ -7185,50 +7251,52 @@ ok
               <c>spawn</c> or <c>spawn_link</c> uses these
               garbage collection settings. The default settings can be
               changed by using
-              <seealso marker="#system_flag/2">system_flag/2</seealso>.
-              <seealso marker="#spawn_opt/4">spawn_opt/4</seealso>
+              <seealso marker="#system_flag/2">
+              <c>erlang:system_flag/2</c></seealso>.
+              <seealso marker="#spawn_opt/4"><c>spawn_opt/4</c></seealso>
               can spawn a process that does not use the default
               settings.</p>
           </item>
           <tag><c>max_heap_size</c></tag>
           <item>
-	      <p>Returns <c>{max_heap_size, <anno>MaxHeapSize</anno>}</c>,
+            <p>Returns <c>{max_heap_size, <anno>MaxHeapSize</anno>}</c>,
               where <c><anno>MaxHeapSize</anno></c> is the current
-              system-wide max heap size settings for spawned processes.
-              This setting can be set using the <c>erl</c> command line
-              flags <seealso marker="erl#+hmax"><c>+hmax</c></seealso>,
+              system-wide maximum heap size settings for spawned processes.
+              This setting can be set using the command-line flags
+              <seealso marker="erl#+hmax"><c>+hmax</c></seealso>,
               <seealso marker="erl#+hmaxk"><c>+hmaxk</c></seealso> and
-              <seealso marker="erl#+hmaxel"><c>+hmaxel</c></seealso>. It can
-              also be changed at run-time using
+              <seealso marker="erl#+hmaxel"><c>+hmaxel</c></seealso> in
+              <c>erl/1</c>. It can also be changed at runtime using
               <seealso marker="#system_flag_max_heap_size">
-                <c>erlang:system_flag(max_heap_size, MaxHeapSize)</c></seealso>.
-              For more details about the <c>max_heap_size</c> process flag
+              <c>erlang:system_flag(max_heap_size, MaxHeapSize)</c></seealso>.
+              For more details about the <c>max_heap_size</c> process flag,
               see <seealso marker="#process_flag_max_heap_size">
-                <c>process_flag(max_heap_size, MaxHeapSize)</c></seealso>.
-              </p>
+              <c>process_flag(max_heap_size, MaxHeapSize)</c></seealso>.</p>
           </item>
-	  <tag><c>min_heap_size</c></tag>
+          <tag><c>min_heap_size</c></tag>
           <item>
-	      <p>Returns <c>{min_heap_size, <anno>MinHeapSize</anno>}</c>,
+            <p>Returns <c>{min_heap_size, <anno>MinHeapSize</anno>}</c>,
               where <c><anno>MinHeapSize</anno></c> is the current
               system-wide minimum heap size for spawned processes.</p>
           </item>
-          <tag><marker id="system_info_message_queue_data"/><c>message_queue_data</c></tag>
+          <tag><marker id="system_info_message_queue_data"/>
+            <c>message_queue_data</c></tag>
           <item>
             <p>Returns the default value of the <c>message_queue_data</c>
-	    process flag which is either <c>off_heap</c>, or <c>on_heap</c>.
-	    This default is set by the <c>erl</c> command line argument
-	    <seealso marker="erl#+hmqd"><c>+hmqd</c></seealso>. For more information on the
-	    <c>message_queue_data</c> process flag, see documentation of
-            <seealso marker="#process_flag_message_queue_data"><c>process_flag(message_queue_data,
-	    MQD)</c></seealso>.</p>
+              process flag, which is either <c>off_heap</c> or <c>on_heap</c>.
+              This default is set by command-line argument
+              <seealso marker="erl#+hmqd"><c>+hmqd</c></seealso> in
+              <c>erl/1</c>. For more information on the
+              <c>message_queue_data</c> process flag, see documentation of
+              <seealso marker="#process_flag_message_queue_data">
+              <c>process_flag(message_queue_data, MQD)</c></seealso>.</p>
           </item>
-	  <tag><c>min_bin_vheap_size</c></tag>
+          <tag><c>min_bin_vheap_size</c></tag>
           <item>
-	      <p>Returns <c>{min_bin_vheap_size,
+            <p>Returns <c>{min_bin_vheap_size,
               <anno>MinBinVHeapSize</anno>}</c>, where
               <c><anno>MinBinVHeapSize</anno></c> is the current system-wide
-	      minimum binary virtual heap size for spawned processes.</p>
+              minimum binary virtual heap size for spawned processes.</p>
           </item>
         </taglist>
       </desc>
@@ -7299,24 +7367,25 @@ ok
           <tag><c>allocated_areas</c>, <c>allocator</c>,
             <c>alloc_util_allocators</c>, <c>allocator_sizes</c></tag>
           <item>
-            <p>See <seealso marker="#system_info_allocator_tags">above</seealso>.</p>
+            <p>See <seealso marker="#system_info_allocator_tags">
+              above</seealso>.</p>
           </item>
           <tag><c>build_type</c></tag>
           <item>
             <p>Returns an atom describing the build type of the runtime
-	       system. This is normally the atom <c>opt</c> for optimized.
-               Other possible return values are <c>debug</c>, <c>purify</c>,
-	       <c>quantify</c>, <c>purecov</c>, <c>gcov</c>, <c>valgrind</c>,
-	       <c>gprof</c>, and <c>lcnt</c>. Possible return values
-	       can be added or removed at any time without prior notice.</p>
+              system. This is normally the atom <c>opt</c> for optimized.
+              Other possible return values are <c>debug</c>, <c>purify</c>,
+              <c>quantify</c>, <c>purecov</c>, <c>gcov</c>, <c>valgrind</c>,
+              <c>gprof</c>, and <c>lcnt</c>. Possible return values
+              can be added or removed at any time without prior notice.</p>
           </item>
           <tag><c>c_compiler_used</c></tag>
           <item>
             <p>Returns a two-tuple describing the C compiler used when
-	       compiling the runtime system. The first element is an
-	       atom describing the name of the compiler, or <c>undefined</c>
-	       if unknown. The second element is a term describing the
-	       version of the compiler, or <c>undefined</c> if unknown.</p>
+              compiling the runtime system. The first element is an
+              atom describing the name of the compiler, or <c>undefined</c>
+              if unknown. The second element is a term describing the
+              version of the compiler, or <c>undefined</c> if unknown.</p>
           </item>
           <tag><c>check_io</c></tag>
           <item>
@@ -7333,12 +7402,13 @@ ok
               Erlang/OTP release that the current emulator has been
               set to be backward compatible with. The compatibility
               mode can be configured at startup by using command-line flag
-              <seealso marker="erts:erl#compat_rel">+R</seealso> in
+              <seealso marker="erts:erl#compat_rel"><c>+R</c></seealso> in
               <c>erl(1)</c>.</p>
           </item>
           <tag><c>cpu_topology</c></tag>
           <item>
-            <p>See <seealso marker="#system_info_cpu_topology_tags">above</seealso>.</p>
+            <p>See <seealso
+              marker="#system_info_cpu_topology_tags">above</seealso>.</p>
           </item>
           <tag><c>creation</c></tag>
           <item>
@@ -7354,22 +7424,22 @@ ok
           </item>
           <tag><c>debug_compiled</c></tag>
           <item>
-            <p>Returns <c>true</c> if the emulator has been debug
-	       compiled, otherwise <c>false</c>.</p>
+            <p>Returns <c>true</c> if the emulator has been
+              debug-compiled, otherwise <c>false</c>.</p>
           </item>
           <tag><c>delayed_node_table_gc</c></tag>
           <item>
             <marker id="system_info_delayed_node_table_gc"></marker>
             <p>Returns the amount of time in seconds garbage collection
-	    of an entry in a node table is delayed. This limit can be set
-	    on startup by passing the command line flag
-	    <seealso marker="erts:erl#+zdntgc">+zdntgc</seealso>
-	    to <c>erl</c>. For more information see the documentation of the
-	    command line flag.</p>
+              of an entry in a node table is delayed. This limit can be set
+              on startup by passing command-line flag
+              <seealso marker="erts:erl#+zdntgc"><c>+zdntgc</c></seealso>
+              to <c>erl/1</c>. For more information, see the documentation of
+              the command-line flag.</p>
           </item>
           <tag><c>dirty_cpu_schedulers</c></tag>
           <item>
-          <marker id="system_info_dirty_cpu_schedulers"></marker>
+            <marker id="system_info_dirty_cpu_schedulers"></marker>
             <p>Returns the number of dirty CPU scheduler threads used by
               the emulator. Dirty CPU schedulers execute CPU-bound
               native functions, such as NIFs, linked-in driver code,
@@ -7381,23 +7451,31 @@ ok
               can be changed at any time. The number of dirty CPU
               schedulers can be set at startup by passing
               command-line flag
-              <seealso marker="erts:erl#+SDcpu">+SDcpu</seealso> or
-              <seealso marker="erts:erl#+SDPcpu">+SDPcpu</seealso> in
+              <seealso marker="erts:erl#+SDcpu"><c>+SDcpu</c></seealso> or
+              <seealso marker="erts:erl#+SDPcpu"><c>+SDPcpu</c></seealso> in
               <c>erl(1)</c>.</p>
-	    <p>Notice that the dirty schedulers functionality is
+            <p>Notice that the dirty schedulers functionality is
               experimental. Enable support for dirty schedulers when
               building OTP to try out the functionality.</p>
             <p>See also
-              <seealso marker="#system_flag_dirty_cpu_schedulers_online">erlang:system_flag(dirty_cpu_schedulers_online, DirtyCPUSchedulersOnline)</seealso>,
-              <seealso marker="#system_info_dirty_cpu_schedulers_online">erlang:system_info(dirty_cpu_schedulers_online)</seealso>,
-              <seealso marker="#system_info_dirty_io_schedulers">erlang:system_info(dirty_io_schedulers)</seealso>,
-              <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>,
-	      <seealso marker="#system_info_schedulers_online">erlang:system_info(schedulers_online)</seealso>, and
-              <seealso marker="#system_flag_schedulers_online">erlang:system_flag(schedulers_online, SchedulersOnline)</seealso>.</p>
+              <seealso marker="#system_flag_dirty_cpu_schedulers_online">
+              <c>erlang:system_flag(dirty_cpu_schedulers_online,
+              DirtyCPUSchedulersOnline)</c></seealso>,
+              <seealso marker="#system_info_dirty_cpu_schedulers_online">
+              <c>erlang:system_info(dirty_cpu_schedulers_online)</c></seealso>,
+              <seealso marker="#system_info_dirty_io_schedulers">
+              <c>erlang:system_info(dirty_io_schedulers)</c></seealso>,
+              <seealso marker="#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso>,
+              <seealso marker="#system_info_schedulers_online">
+              <c>erlang:system_info(schedulers_online)</c></seealso>, and
+              <seealso marker="#system_flag_schedulers_online">
+              <c>erlang:system_flag(schedulers_online,
+              SchedulersOnline)</c></seealso>.</p>
           </item>
           <tag><c>dirty_cpu_schedulers_online</c></tag>
           <item>
-          <marker id="system_info_dirty_cpu_schedulers_online"></marker>
+            <marker id="system_info_dirty_cpu_schedulers_online"></marker>
             <p>Returns the number of dirty CPU schedulers online.
               The return value satisfies
               <c><![CDATA[1 <= DirtyCPUSchedulersOnline <= N]]></c>,
@@ -7406,51 +7484,60 @@ ok
               <c>erlang:system_info(schedulers_online)</c>.</p>
             <p>The number of dirty CPU schedulers online can be set at
               startup by passing command-line flag
-              <seealso marker="erts:erl#+SDcpu">+SDcpu</seealso> in
+              <seealso marker="erts:erl#+SDcpu"><c>+SDcpu</c></seealso> in
               <c>erl(1)</c>.</p>
 	    <p>Notice that the dirty schedulers functionality is
               experimental. Enable support for dirty schedulers when
               building OTP to try out the functionality.</p>
             <p>For more information, see
-              <seealso marker="#system_info_dirty_cpu_schedulers">erlang:system_info(dirty_cpu_schedulers)</seealso>,
-              <seealso marker="#system_info_dirty_io_schedulers">erlang:system_info(dirty_io_schedulers)</seealso>,
-              <seealso marker="#system_info_schedulers_online">erlang:system_info(schedulers_online)</seealso>, and
-              <seealso marker="#system_flag_dirty_cpu_schedulers_online">erlang:system_flag(dirty_cpu_schedulers_online, DirtyCPUSchedulersOnline)</seealso>.</p>
+              <seealso marker="#system_info_dirty_cpu_schedulers">
+              <c>erlang:system_info(dirty_cpu_schedulers)</c></seealso>,
+              <seealso marker="#system_info_dirty_io_schedulers">
+              <c>erlang:system_info(dirty_io_schedulers)</c></seealso>,
+              <seealso marker="#system_info_schedulers_online">
+              <c>erlang:system_info(schedulers_online)</c></seealso>, and
+              <seealso marker="#system_flag_dirty_cpu_schedulers_online">
+              <c>erlang:system_flag(dirty_cpu_schedulers_online,
+              DirtyCPUSchedulersOnline)</c></seealso>.</p>
           </item>
           <tag><c>dirty_io_schedulers</c></tag>
           <item>
-          <marker id="system_info_dirty_io_schedulers"></marker>
+            <marker id="system_info_dirty_io_schedulers"></marker>
             <p>Returns the number of dirty I/O schedulers as an integer.
               Dirty I/O schedulers execute I/O-bound native functions,
               such as NIFs and linked-in driver code, which cannot be
               managed cleanly by the normal emulator schedulers.</p>
             <p>This value can be set at startup by passing command-line
-              argument <seealso marker="erts:erl#+SDio">+SDio</seealso>
+              argument <seealso marker="erts:erl#+SDio"><c>+SDio</c></seealso>
               in <c>erl(1)</c>.</p>
-	    <p>Notice that the dirty schedulers functionality is
+            <p>Notice that the dirty schedulers functionality is
               experimental. Enable support for dirty schedulers when
               building OTP to try out the functionality.</p>
             <p>For more information, see
-              <seealso marker="#system_info_dirty_cpu_schedulers">erlang:system_info(dirty_cpu_schedulers)</seealso>,
-              <seealso marker="#system_info_dirty_cpu_schedulers_online">erlang:system_info(dirty_cpu_schedulers_online)</seealso>, and
-              <seealso marker="#system_flag_dirty_cpu_schedulers_online">erlang:system_flag(dirty_cpu_schedulers_online, DirtyCPUSchedulersOnline)</seealso>.</p>
+              <seealso marker="#system_info_dirty_cpu_schedulers">
+              <c>erlang:system_info(dirty_cpu_schedulers)</c></seealso>,
+              <seealso marker="#system_info_dirty_cpu_schedulers_online">
+              <c>erlang:system_info(dirty_cpu_schedulers_online)</c></seealso>,
+              and <seealso marker="#system_flag_dirty_cpu_schedulers_online">
+              <c>erlang:system_flag(dirty_cpu_schedulers_online,
+              DirtyCPUSchedulersOnline)</c></seealso>.</p>
           </item>
           <tag><c>dist</c></tag>
           <item>
             <p>Returns a binary containing a string of distribution
               information formatted as in Erlang crash dumps. For more
-              information, see Section
-              <seealso marker="erts:crash_dump">"How to interpret the Erlang crash dumps"</seealso>
+              information, see section <seealso marker="erts:crash_dump">
+              How to interpret the Erlang crash dumps</seealso>
               in the User's Guide.</p>
           </item>
           <tag><c>dist_buf_busy_limit</c></tag>
           <item>
-          <marker id="system_info_dist_buf_busy_limit"></marker>
+            <marker id="system_info_dist_buf_busy_limit"></marker>
             <p>Returns the value of the distribution buffer busy limit
-	    in bytes. This limit can be set at startup by passing
-            command-line flag
-	    <seealso marker="erts:erl#+zdbbl">+zdbbl</seealso>
-            to <c>erl</c>.</p>
+              in bytes. This limit can be set at startup by passing
+              command-line flag
+              <seealso marker="erts:erl#+zdbbl"><c>+zdbbl</c></seealso>
+              to <c>erl</c>.</p>
           </item>
           <tag><c>dist_ctrl</c></tag>
           <item>
@@ -7468,62 +7555,63 @@ ok
           <item>
             <p>Returns a string containing the Erlang driver version
               used by the runtime system. It has the form
-              <seealso marker="erts:erl_driver#version_management">"&lt;major ver&gt;.&lt;minor ver&gt;"</seealso>.</p>
+              <seealso marker="erts:erl_driver#version_management">
+              "&lt;major ver&gt;.&lt;minor ver&gt;"</seealso>.</p>
           </item>
           <tag><c>dynamic_trace</c></tag>
           <item>
             <p>Returns an atom describing the dynamic trace framework
-            compiled into the virtual machine. It can be
-            <c>dtrace</c>, <c>systemtap</c>, or <c>none</c>. For a
-            commercial or standard build, it is always <c>none</c>.
-            The other return values indicate a custom configuration
-            (for example, <c>./configure --with-dynamic-trace=dtrace</c>).
-            For more information about dynamic tracing, see the
-            <seealso marker="runtime_tools:dyntrace">dyntrace</seealso>
-            manual page and the
-            <c>README.dtrace</c>/<c>README.systemtap</c> files in the
-            Erlang source code top directory.</p>
+              compiled into the virtual machine. It can be
+              <c>dtrace</c>, <c>systemtap</c>, or <c>none</c>. For a
+              commercial or standard build, it is always <c>none</c>.
+              The other return values indicate a custom configuration
+              (for example, <c>./configure --with-dynamic-trace=dtrace</c>).
+              For more information about dynamic tracing, see
+              <seealso marker="runtime_tools:dyntrace">
+              <c>runtime_tools:dyntrace</c></seealso> manual page and the
+              <c>README.dtrace</c>/<c>README.systemtap</c> files in the
+              Erlang source code top directory.</p>
           </item>
           <tag><c>dynamic_trace_probes</c></tag>
           <item>
             <p>Returns a <c>boolean()</c> indicating if dynamic trace
-            probes (<c>dtrace</c> or <c>systemtap</c>) are built into
-            the emulator. This can only be <c>true</c> if the Virtual
-            Machine was built for dynamic tracing (that is,
-            <c>system_info(dynamic_trace)</c> returns
-            <c>dtrace</c> or <c>systemtap</c>).</p>
+              probes (<c>dtrace</c> or <c>systemtap</c>) are built into
+              the emulator. This can only be <c>true</c> if the virtual
+              machine was built for dynamic tracing (that is,
+              <c>system_info(dynamic_trace)</c> returns
+              <c>dtrace</c> or <c>systemtap</c>).</p>
           </item>
-	  <tag><marker id="system_info_end_time"/><c>end_time</c></tag>
-	  <item>
+          <tag><marker id="system_info_end_time"/><c>end_time</c></tag>
+          <item>
             <p>The last <seealso marker="#monotonic_time/0">Erlang monotonic
-	  time</seealso> in <c>native</c>
-	  <seealso marker="#type_time_unit">time unit</seealso> that
-	  can be represented internally in the current Erlang runtime system
-	  instance. The time between the
-	  <seealso marker="#system_info_start_time">start time</seealso> and
-	  the end time is at least a quarter of a millennium.</p></item>
+              time</seealso> in <c>native</c>
+              <seealso marker="#type_time_unit">time unit</seealso> that
+              can be represented internally in the current Erlang runtime system
+              instance. The time between the
+              <seealso marker="#system_info_start_time">start time</seealso> and
+              the end time is at least a quarter of a millennium.</p>
+          </item>
           <tag><c>elib_malloc</c></tag>
           <item>
             <p>This option will be removed in a future release.
-	      The return value will always be <c>false</c>, as the
-	      <c>elib_malloc</c> allocator has been removed.</p>
+              The return value will always be <c>false</c>, as the
+              <c>elib_malloc</c> allocator has been removed.</p>
           </item>
-          <tag><marker id="system_info_eager_check_io"/><c>eager_check_io</c></tag>
+          <tag><marker id="system_info_eager_check_io"/>
+            <c>eager_check_io</c></tag>
           <item>
-            <p>
-	      Returns the value of the <c>erl</c> command line flag
-	      <seealso marker="erl#+secio">+secio</seealso>
-	      which is either <c>true</c> or <c>false</c>. See the
-	      documentation of the command line flag for information about
-	      the different values.
-	    </p>
+            <p>Returns the value of command-line flag
+              <seealso marker="erl#+secio"><c>+secio</c></seealso> in
+              <c>erl/1</c>, which is either <c>true</c> or <c>false</c>.
+              For information about the different values, see the
+              documentation of the command-line flag.</p>
           </item>
           <tag><c>ets_limit</c></tag>
           <item>
-            <p>Returns the maximum number of ETS tables allowed. This
+            <p>Returns the maximum number of <c>ets</c> tables allowed. This
               limit can be increased at startup by passing
               command-line flag
-              <seealso marker="erts:erl#+e">+e</seealso> to
+              <seealso marker="erts:erl#+e"><c>+e</c></seealso> to
               <c>erl(1)</c> or by setting environment variable
               <c>ERL_MAX_ETS_TABLES</c> before starting the Erlang
               runtime system.</p>
@@ -7541,10 +7629,10 @@ ok
             <taglist>
               <tag><c>private</c></tag>
               <item>
-                <p>Each process has a heap reserved for its use and no
-                  references between heaps of different processes are
-                  allowed. Messages passed between processes are copied
-                  between heaps.</p>
+                Each process has a heap reserved for its use and no
+                references between heaps of different processes are
+                allowed. Messages passed between processes are copied
+                between heaps.
               </item>
             </taglist>
           </item>
@@ -7552,8 +7640,9 @@ ok
           <item>
             <p>Returns a binary containing a string of miscellaneous
               system information formatted as in Erlang crash dumps.
-              For more information, see Section
-              <seealso marker="erts:crash_dump">"How to interpret the Erlang crash dumps"</seealso>
+              For more information, see section
+              <seealso marker="erts:crash_dump">
+              How to interpret the Erlang crash dumps</seealso>
               in the User's Guide.</p>
           </item>
           <tag><c>kernel_poll</c></tag>
@@ -7565,38 +7654,39 @@ ok
           <item>
             <p>Returns a binary containing a string of loaded module
               information formatted as in Erlang crash dumps. For more
-              information, see Section
-              <seealso marker="erts:crash_dump">"How to interpret the Erlang crash dumps"</seealso>
-              in the User's Guide.</p>
+              information, see section
+              <seealso marker="erts:crash_dump">How to interpret the Erlang
+              crash dumps</seealso> in the User's Guide.</p>
           </item>
-	  <tag><c>logical_processors</c></tag>
+          <tag><c>logical_processors</c></tag>
           <item>
-          <marker id="logical_processors"></marker>
+            <marker id="logical_processors"></marker>
             <p>Returns the detected number of logical processors configured
-	       in the system. The return value is either an integer, or
-	       the atom <c>unknown</c> if the emulator cannot
-	       detect the configured logical processors.</p>
+              in the system. The return value is either an integer, or
+              the atom <c>unknown</c> if the emulator cannot
+              detect the configured logical processors.</p>
           </item>
-	  <tag><c>logical_processors_available</c></tag>
+          <tag><c>logical_processors_available</c></tag>
           <item>
-          <marker id="logical_processors_available"></marker>
+            <marker id="logical_processors_available"></marker>
             <p>Returns the detected number of logical processors available
-	       to the Erlang runtime system. The return value is either an
-	       integer, or the atom <c>unknown</c> if the emulator
-	       cannot detect the available logical processors. The number
-	       of available logical processors is less than or equal to
-	       the number of
-               <seealso marker="#logical_processors_online">logical processors online</seealso>.</p>
+              to the Erlang runtime system. The return value is either an
+              integer, or the atom <c>unknown</c> if the emulator
+              cannot detect the available logical processors. The number
+              of available logical processors is less than or equal to
+              the number of <seealso marker="#logical_processors_online">
+              logical processors online</seealso>.</p>
           </item>
-	  <tag><c>logical_processors_online</c></tag>
+          <tag><c>logical_processors_online</c></tag>
           <item>
-          <marker id="logical_processors_online"></marker>
+            <marker id="logical_processors_online"></marker>
             <p>Returns the detected number of logical processors online on
-	       the system. The return value is either an integer,
-	       or the atom <c>unknown</c> if the emulator cannot
-	       detect logical processors online. The number of logical
-	       processors online is less than or equal to the number of
-	       <seealso marker="#logical_processors">logical processors configured</seealso>.</p>
+              the system. The return value is either an integer,
+              or the atom <c>unknown</c> if the emulator cannot
+              detect logical processors online. The number of logical
+              processors online is less than or equal to the number of
+              <seealso marker="#logical_processors">logical processors
+              configured</seealso>.</p>
           </item>
           <tag><c>machine</c></tag>
           <item>
@@ -7605,17 +7695,16 @@ ok
           <tag><c>modified_timing_level</c></tag>
           <item>
             <p>Returns the modified timing-level (an integer) if
-              modified timing is enabled, otherwise, <c>undefined</c>.
+              modified timing is enabled, otherwise <c>undefined</c>.
               For more information about modified timing, see
               command-line flag
-              <seealso marker="erts:erl#+T">+T</seealso>
+              <seealso marker="erts:erl#+T"><c>+T</c></seealso>
               in <c>erl(1)</c></p>
           </item>
           <tag><c>multi_scheduling</c></tag>
           <item>
-          <marker id="system_info_multi_scheduling"></marker>
-            <p>Returns <c>disabled</c>, <c>blocked</c>, <c>blocked_normal</c>,
-	    or <c>enabled</c>:</p>
+            <marker id="system_info_multi_scheduling"></marker>
+            <p>Returns one of the following:</p>
             <taglist>
               <tag><c>disabled</c></tag>
               <item>
@@ -7634,9 +7723,9 @@ ok
               <item>
                 <p>The emulator has more than one scheduler thread,
                   but all normal scheduler threads except one are
-		  blocked. Note that dirty schedulers are not
-		  blocked, and may schedule Erlang processes and
-		  execute native code.</p>
+                  blocked. Notice that dirty schedulers are not
+                  blocked, and can schedule Erlang processes and
+                  execute native code.</p>
               </item>
               <tag><c>enabled</c></tag>
               <item>
@@ -7647,201 +7736,204 @@ ok
               </item>
             </taglist>
             <p>See also
-              <seealso marker="#system_flag_multi_scheduling">erlang:system_flag(multi_scheduling, BlockState)</seealso>,
-              <seealso marker="#system_info_multi_scheduling_blockers">erlang:system_info(multi_scheduling_blockers)</seealso>,
-              <seealso marker="#system_info_normal_multi_scheduling_blockers">erlang:system_info(normal_multi_scheduling_blockers)</seealso>,
-              and
-              <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>.</p>
+              <seealso marker="#system_flag_multi_scheduling">
+              <c>erlang:system_flag(multi_scheduling, BlockState)</c></seealso>,
+              <seealso marker="#system_info_multi_scheduling_blockers">
+              <c>erlang:system_info(multi_scheduling_blockers)</c></seealso>,
+              <seealso marker="#system_info_normal_multi_scheduling_blockers">
+              <c>erlang:system_info(normal_multi_scheduling_blockers)</c></seealso>,
+              and <seealso marker="#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso>.</p>
           </item>
           <tag><c>multi_scheduling_blockers</c></tag>
           <item>
-          <marker id="system_info_multi_scheduling_blockers"></marker>
+            <marker id="system_info_multi_scheduling_blockers"></marker>
             <p>Returns a list of <c><anno>Pid</anno></c>s when
               multi-scheduling is blocked, otherwise the empty list is
               returned. The <c><anno>Pid</anno></c>s in the list
-	      represent all the processes currently
+              represent all the processes currently
               blocking multi-scheduling. A <c><anno>Pid</anno></c> occurs
               only once in the list, even if the corresponding
               process has blocked multiple times.</p>
             <p>See also
-              <seealso marker="#system_flag_multi_scheduling">erlang:system_flag(multi_scheduling, BlockState)</seealso>,
-              <seealso marker="#system_info_multi_scheduling">erlang:system_info(multi_scheduling)</seealso>,
-	      <seealso marker="#system_info_normal_multi_scheduling_blockers">erlang:system_info(normal_multi_scheduling_blockers)</seealso>,
-
-              and
-              <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>.</p>
+              <seealso marker="#system_flag_multi_scheduling">
+              <c>erlang:system_flag(multi_scheduling, BlockState)</c></seealso>,
+              <seealso marker="#system_info_multi_scheduling">
+              <c>erlang:system_info(multi_scheduling)</c></seealso>,
+              <seealso marker="#system_info_normal_multi_scheduling_blockers">
+              <c>erlang:system_info(normal_multi_scheduling_blockers)</c></seealso>,
+              and <seealso marker="#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso>.</p>
           </item>
           <tag><c>nif_version</c></tag>
           <item>
-            <p>Returns a string containing the version of the Erlang NIF interface
-              used by the runtime system. It is on the form
-	      "&lt;major ver&gt;.&lt;minor ver&gt;".</p>
+            <p>Returns a string containing the version of the Erlang NIF
+              interface used by the runtime system. It is on the form
+              "&lt;major ver&gt;.&lt;minor ver&gt;".</p>
           </item>
           <tag><c>normal_multi_scheduling_blockers</c></tag>
           <item>
-          <marker id="system_info_normal_multi_scheduling_blockers"></marker>
+            <marker id="system_info_normal_multi_scheduling_blockers"></marker>
             <p>Returns a list of <c><anno>Pid</anno></c>s when
-              normal multi-scheduling is blocked (i.e. all normal schedulers
-	      but one is blocked), otherwise the empty list is returned.
-	      The <c><anno>Pid</anno></c>s in the list represent all the
-	      processes currently blocking normal multi-scheduling.
-	      A <c><anno>Pid</anno></c> occurs only once in the list, even if
-	      the corresponding process has blocked multiple times.</p>
+              normal multi-scheduling is blocked (that is, all normal schedulers
+              but one is blocked), otherwise the empty list is returned.
+              The <c><anno>Pid</anno></c>s in the list represent all the
+              processes currently blocking normal multi-scheduling.
+              A <c><anno>Pid</anno></c> occurs only once in the list, even if
+              the corresponding process has blocked multiple times.</p>
             <p>See also
-              <seealso marker="#system_flag_multi_scheduling">erlang:system_flag(multi_scheduling, BlockState)</seealso>,
-              <seealso marker="#system_info_multi_scheduling">erlang:system_info(multi_scheduling)</seealso>,
-	      <seealso marker="#system_info_multi_scheduling_blockers">erlang:system_info(multi_scheduling_blockers)</seealso>,
-
-              and
-              <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>.</p>
-          </item>
-          <tag><marker id="system_info_otp_release"/><c>otp_release</c></tag>
-          <item>
-          <marker id="system_info_otp_release"></marker>
+              <seealso marker="#system_flag_multi_scheduling">
+              <c>erlang:system_flag(multi_scheduling, BlockState)</c></seealso>,
+              <seealso marker="#system_info_multi_scheduling">
+              <c>erlang:system_info(multi_scheduling)</c></seealso>,
+              <seealso marker="#system_info_multi_scheduling_blockers">
+              <c>erlang:system_info(multi_scheduling_blockers)</c></seealso>,
+              and <seealso marker="#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso>.</p>
+          </item>
+          <tag><marker id="system_info_otp_release"/>
+            <c>otp_release</c></tag>
+          <item>
+            <marker id="system_info_otp_release"></marker>
             <p>Returns a string containing the OTP release number of the
-	    OTP release that the currently executing <c>ERTS</c> application is
-            part of.</p>
-            <p>As from OTP 17, the OTP release number corresponds to
-            the major OTP version number. No
-	    <c>erlang:system_info()</c> argument gives the exact OTP
-	    version. This is because the exact OTP version in the general case
-	    is difficult to determine. For more information, see the description
-	    of versions in <seealso marker="doc/system_principles:versions">
-	    System principles</seealso> in System Documentation.</p>
-          </item>
-          <tag><marker id="system_info_os_monotonic_time_source"/><c>os_monotonic_time_source</c></tag>
+              OTP release that the currently executing <c>ERTS</c> application
+              is part of.</p>
+            <p>As from Erlang/OTP 17, the OTP release number corresponds to
+              the major OTP version number. No
+              <c>erlang:system_info()</c> argument gives the exact OTP
+              version. This is because the exact OTP version in the general case
+              is difficult to determine. For more information, see the
+              description of versions in
+              <seealso marker="doc/system_principles:versions">
+              System principles</seealso> in System Documentation.</p>
+          </item>
+          <tag><marker id="system_info_os_monotonic_time_source"/>
+            <c>os_monotonic_time_source</c></tag>
           <item>
             <p>Returns a list containing information about the source of
-	    <seealso marker="erts:time_correction#OS_Monotonic_Time">OS
-	    monotonic time</seealso> that is used by the runtime system.</p>
-	    <p>If <c>[]</c> is returned, no OS monotonic time is
-	    available. The list contains two-tuples with <c>Key</c>s
-	    as first element, and <c>Value</c>s as second element. The
-	    order of these tuples is undefined. The following
-	    tuples can be part of the list, but more tuples can be
-	    introduced in the future:</p>
-	    <taglist>
-	      <tag><c>{function, Function}</c></tag>
-	      <item>
-            <p><c>Function</c> is the name of the function
-	      used. This tuple always exist if OS monotonic time is
-	      available to the runtime system.</p></item>
-
-	      <tag><c>{clock_id, ClockId}</c></tag>
-	      <item>
-            <p>This tuple only exist if <c>Function</c>
-	      can be used with different clocks. <c>ClockId</c>
-	      corresponds to the clock identifier used when calling
-	      <c>Function</c>.</p></item>
-
-	      <tag><c>{resolution, OsMonotonicTimeResolution}</c></tag>
-	      <item>
-            <p>Highest possible
-	      <seealso marker="time_correction#Time_Resolution">resolution</seealso>
-	      of current OS monotonic time source as parts per
-	      second. If no resolution information can be retrieved
-	      from the OS, <c>OsMonotonicTimeResolution</c> is
-	      set to the resolution of the time unit of
-	      <c>Function</c>s return value. That is, the actual
-	      resolution can be lower than
-	      <c>OsMonotonicTimeResolution</c>. Also note that
-	      the resolution does not say anything about the
-	      <seealso marker="time_correction#Time_Accuracy">accuracy</seealso>,
-	      and whether the
-	      <seealso marker="time_correction#Time_Precision">precision</seealso>
-	      do align with the resolution. You do,
-	      however, know that the precision is not better than
-	      <c>OsMonotonicTimeResolution</c>.</p></item>
-
-	      <tag><c>{extended, Extended}</c></tag>
-	      <item>
-            <p><c>Extended</c> equals <c>yes</c> if
-	      the range of time values has been extended;
-	      otherwise, <c>Extended</c> equals <c>no</c>. The
-	      range needs to be extended if <c>Function</c>
-	      returns values that wrap fast. This typically
-	      is the case when the return value is a 32-bit
-	      value.</p></item>
-
-	      <tag><c>{parallel, Parallel}</c></tag>
-	      <item>
-            <p><c>Parallel</c> equals <c>yes</c> if
-	      <c>Function</c> is called in parallel from multiple
-	      threads. If it is not called in parallel, because
-	      calls needs to be serialized, <c>Parallel</c> equals
-	      <c>no</c>.</p></item>
-
-	      <tag><c>{time, OsMonotonicTime}</c></tag>
-	      <item>
-            <p><c>OsMonotonicTime</c> equals current OS
-	      monotonic time in <c>native</c>
-	      <seealso marker="#type_time_unit">time unit</seealso>.</p></item>
-	    </taglist>
-          </item>
-          <tag><marker id="system_info_os_system_time_source"/><c>os_system_time_source</c></tag>
+              <seealso marker="erts:time_correction#OS_Monotonic_Time">OS
+              monotonic time</seealso> that is used by the runtime system.</p>
+            <p>If <c>[]</c> is returned, no OS monotonic time is
+              available. The list contains two-tuples with <c>Key</c>s
+              as first element, and <c>Value</c>s as second element. The
+              order of these tuples is undefined. The following
+              tuples can be part of the list, but more tuples can be
+              introduced in the future:</p>
+            <taglist>
+              <tag><c>{function, Function}</c></tag>
+              <item><p><c>Function</c> is the name of the function
+                used. This tuple always exists if OS monotonic time is
+                available to the runtime system.</p>
+              </item>
+              <tag><c>{clock_id, ClockId}</c></tag>
+              <item><p>This tuple only exists if <c>Function</c>
+                can be used with different clocks. <c>ClockId</c>
+                corresponds to the clock identifier used when calling
+                <c>Function</c>.</p>
+              </item>
+              <tag><c>{resolution, OsMonotonicTimeResolution}</c></tag>
+              <item><p>Highest possible
+                <seealso marker="time_correction#Time_Resolution">
+                resolution</seealso>
+                of current OS monotonic time source as parts per
+                second. If no resolution information can be retrieved
+                from the OS, <c>OsMonotonicTimeResolution</c> is
+                set to the resolution of the time unit of
+                <c>Function</c>s return value. That is, the actual
+                resolution can be lower than
+                <c>OsMonotonicTimeResolution</c>. Notice that
+                the resolution does not say anything about the
+                <seealso marker="time_correction#Time_Accuracy">
+                accuracy</seealso> or whether the
+                <seealso marker="time_correction#Time_Precision">
+                precision</seealso> aligns with the resolution. You do,
+                however, know that the precision is not better than
+                <c>OsMonotonicTimeResolution</c>.</p>
+              </item>
+              <tag><c>{extended, Extended}</c></tag>
+              <item><p><c>Extended</c> equals <c>yes</c> if
+                the range of time values has been extended;
+                otherwise <c>Extended</c> equals <c>no</c>. The
+                range must be extended if <c>Function</c>
+                returns values that wrap fast. This typically
+                is the case when the return value is a 32-bit value.</p>
+              </item>
+              <tag><c>{parallel, Parallel}</c></tag>
+              <item><p><c>Parallel</c> equals <c>yes</c> if
+                <c>Function</c> is called in parallel from multiple
+                threads. If it is not called in parallel, because
+                calls must be serialized, <c>Parallel</c> equals
+                <c>no</c>.</p>
+              </item>
+              <tag><c>{time, OsMonotonicTime}</c></tag>
+              <item><p><c>OsMonotonicTime</c> equals current OS
+                monotonic time in <c>native</c>
+                <seealso marker="#type_time_unit">time unit</seealso>.</p>
+              </item>
+            </taglist>
+          </item>
+          <tag><marker id="system_info_os_system_time_source"/>
+          <c>os_system_time_source</c></tag>
           <item>
             <p>Returns a list containing information about the source of
-	    <seealso marker="erts:time_correction#OS_System_Time">OS
-	    system time</seealso> that is used by the runtime system.</p>
-	    <p>The list contains two-tuples with <c>Key</c>s
-	    as first element, and <c>Value</c>s as second element. The
-	    order if these tuples is undefined. The following
-	    tuples can be part of the list, but more tuples can be
-	    introduced in the future:</p>
-	    <taglist>
-	      <tag><c>{function, Function}</c></tag>
-	      <item>
-            <p><c>Function</c> is the name of the funcion
-	      used.</p>
+              <seealso marker="erts:time_correction#OS_System_Time">OS
+              system time</seealso> that is used by the runtime system.</p>
+            <p>The list contains two-tuples with <c>Key</c>s
+              as first element, and <c>Value</c>s as second element. The
+              order if these tuples is undefined. The following
+              tuples can be part of the list, but more tuples can be
+              introduced in the future:</p>
+            <taglist>
+              <tag><c>{function, Function}</c></tag>
+              <item><p><c>Function</c> is the name of the funcion used.</p>
               </item>
-	      <tag><c>{clock_id, ClockId}</c></tag>
-	      <item>
-            <p>This tuple only exist if <c>Function</c>
-	      can be used with different clocks. <c>ClockId</c>
-	      corresponds to the clock identifier used when calling
-	      <c>Function</c>.</p>
+              <tag><c>{clock_id, ClockId}</c></tag>
+              <item><p>Exists only if <c>Function</c>
+                can be used with different clocks. <c>ClockId</c>
+                corresponds to the clock identifier used when calling
+                <c>Function</c>.</p>
               </item>
-	      <tag><c>{resolution, OsSystemTimeResolution}</c></tag>
-	      <item>
-            <p>Highest possible
-	      <seealso marker="time_correction#Time_Resolution">resolution</seealso>
-	      of current OS system time source as parts per
-	      second. If no resolution information can be retrieved
-	      from the OS, <c>OsSystemTimeResolution</c> is
-	      set to the resolution of the time unit of
-	      <c>Function</c>s return value. That is, the actual
-	      resolution may be lower than
-	      <c>OsSystemTimeResolution</c>. Also note that
-	      the resolution does not say anything about the
-	      <seealso marker="time_correction#Time_Accuracy">accuracy</seealso>,
-	      and whether the
-	      <seealso marker="time_correction#Time_Precision">precision</seealso>
-	      do align with the resolution. You do,
-	      however, know that the precision is not better than
-	      <c>OsSystemTimeResolution</c>.</p>
+              <tag><c>{resolution, OsSystemTimeResolution}</c></tag>
+              <item><p>Highest possible
+                <seealso marker="time_correction#Time_Resolution">
+                resolution</seealso>
+                of current OS system time source as parts per
+                second. If no resolution information can be retrieved
+                from the OS, <c>OsSystemTimeResolution</c> is
+                set to the resolution of the time unit of
+                <c>Function</c>s return value. That is, the actual
+                resolution can be lower than
+                <c>OsSystemTimeResolution</c>. Notice that
+                the resolution does not say anything about the
+                <seealso marker="time_correction#Time_Accuracy">
+                accuracy</seealso> or whether the
+                <seealso marker="time_correction#Time_Precision">
+                precision</seealso> do align with the resolution. You do,
+                however, know that the precision is not better than
+                <c>OsSystemTimeResolution</c>.</p>
               </item>
-	      <tag><c>{parallel, Parallel}</c></tag>
-	      <item>
-            <p><c>Parallel</c> equals <c>yes</c> if
-	      <c>Function</c> is called in parallel from multiple
-	      threads. If it is not called in parallel, because
-	      calls needs to be serialized, <c>Parallel</c> equals
-	      <c>no</c>.</p>
+              <tag><c>{parallel, Parallel}</c></tag>
+              <item><p><c>Parallel</c> equals <c>yes</c> if
+                <c>Function</c> is called in parallel from multiple
+                threads. If it is not called in parallel, because
+                calls needs to be serialized, <c>Parallel</c> equals
+                <c>no</c>.</p>
               </item>
-	      <tag><c>{time, OsSystemTime}</c></tag>
-	      <item>
-            <p><c>OsSystemTime</c> equals current OS
-	      system time in <c>native</c>
-	      <seealso marker="#type_time_unit">time unit</seealso>.</p>
+              <tag><c>{time, OsSystemTime}</c></tag>
+              <item><p><c>OsSystemTime</c> equals current OS
+                system time in <c>native</c>
+                <seealso marker="#type_time_unit">time unit</seealso>.</p>
               </item>
-	    </taglist>
+            </taglist>
+          </item>
+          <tag><c>port_parallelism</c></tag>
+          <item>
+            <marker id="system_info_port_parallelism"></marker>
+            <p>Returns the default port parallelism scheduling hint used.
+              For more information, see command-line argument
+              <seealso marker="erl#+spp"><c>+spp</c></seealso>
+              in <c>erl(1)</c>.</p>
           </item>
-	  <tag><c>port_parallelism</c></tag>
-	  <item>
-	  <marker id="system_info_port_parallelism"></marker>
-	  <p>Returns the default port parallelism scheduling hint used.
-	  For more information, see command-line argument
-	  <seealso marker="erl#+spp">+spp</seealso> in <c>erl(1)</c>.</p></item>
           <tag><marker id="system_info_port_count"/><c>port_count</c></tag>
           <item>
             <p>Returns the number of ports currently existing at the
@@ -7855,9 +7947,10 @@ ok
             <p>Returns the maximum number of simultaneously existing
               ports at the local node as an integer. This limit can be
               configured at startup by using command-line flag
-              <seealso marker="erl#+Q">+Q</seealso> in <c>erl(1)</c>.</p>
+              <seealso marker="erl#+Q"><c>+Q</c></seealso> in <c>erl(1)</c>.</p>
           </item>
-          <tag><marker id="system_info_process_count"/><c>process_count</c></tag>
+          <tag><marker id="system_info_process_count"/>
+            <c>process_count</c></tag>
           <item>
             <p>Returns the number of processes currently existing at the
               local node. The value is given as an integer. This is
@@ -7866,74 +7959,78 @@ ok
           </item>
           <tag><c>process_limit</c></tag>
           <item>
-          <marker id="system_info_process_limit"></marker>
+            <marker id="system_info_process_limit"></marker>
             <p>Returns the maximum number of simultaneously existing
               processes at the local node. The value is given as an
               integer. This limit can be configured at startup by using
-              command-line flag <seealso marker="erl#+P">+P</seealso>
-	      in <c>erl(1)</c>.</p>
+              command-line flag <seealso marker="erl#+P"><c>+P</c></seealso>
+              in <c>erl(1)</c>.</p>
           </item>
           <tag><c>procs</c></tag>
           <item>
             <p>Returns a binary containing a string of process and port
               information formatted as in Erlang crash dumps. For more
-              information, see Section
-              <seealso marker="erts:crash_dump">"How to interpret the Erlang crash dumps"</seealso>
+              information, see section <seealso marker="erts:crash_dump">
+              How to interpret the Erlang crash dumps</seealso>
               in the User's Guide.</p>
           </item>
           <tag><c>scheduler_bind_type</c></tag>
           <item>
-          <marker id="system_info_scheduler_bind_type"></marker>
-	    <p>Returns information about how the user has requested
-	       schedulers to be bound or not bound.</p>
-	    <p>Notice that even though a user has requested
-	       schedulers to be bound, they can silently have failed
-	       to bind. To inspect the scheduler bindings, call
-	       <seealso marker="#system_info_scheduler_bindings">erlang:system_info(scheduler_bindings)</seealso>.</p>
-	    <p>For more information, see command-line argument
-	       <seealso marker="erts:erl#+sbt">+sbt</seealso>
-	       in <c>erl(1)</c> and
-	       <seealso marker="#system_info_scheduler_bindings">erlang:system_info(scheduler_bindings)</seealso>.</p>
+            <marker id="system_info_scheduler_bind_type"></marker>
+            <p>Returns information about how the user has requested
+              schedulers to be bound or not bound.</p>
+            <p>Notice that although a user has requested
+              schedulers to be bound, they can silently have failed
+              to bind. To inspect the scheduler bindings, call
+              <seealso marker="#system_info_scheduler_bindings">
+              <c>erlang:system_info(scheduler_bindings)</c></seealso>.</p>
+            <p>For more information, see command-line argument
+              <seealso marker="erts:erl#+sbt"><c>+sbt</c></seealso>
+              in <c>erl(1)</c> and
+              <seealso marker="#system_info_scheduler_bindings">
+              <c>erlang:system_info(scheduler_bindings)</c></seealso>.</p>
           </item>
           <tag><c>scheduler_bindings</c></tag>
           <item>
-          <marker id="system_info_scheduler_bindings"></marker>
-	    <p>Returns information about the currently used scheduler
-	       bindings.</p>
-	    <p>A tuple of a size equal to
-	       <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>
-               is returned. The tuple elements are integers
-	       or the atom <c>unbound</c>. Logical processor identifiers
-	       are represented as integers. The <c>N</c>th
-	       element of the tuple equals the current binding for
-	       the scheduler with the scheduler identifier equal to
-	       <c>N</c>. For example, if the schedulers are bound,
-	       <c>element(erlang:system_info(scheduler_id),
-	       erlang:system_info(scheduler_bindings))</c> returns
-	       the identifier of the logical processor that the calling
-	       process is executing on.</p>
-	    <p>Notice that only schedulers online can be bound to logical
-	       processors.</p>
-	    <p>For more information, see command-line argument
-	       <seealso marker="erts:erl#+sbt">+sbt</seealso>
-	       in <c>erl(1)</c> and
-	       <seealso marker="#system_info_schedulers_online">erlang:system_info(schedulers_online)</seealso>.
-	    </p>
+            <marker id="system_info_scheduler_bindings"></marker>
+            <p>Returns information about the currently used scheduler
+              bindings.</p>
+            <p>A tuple of a size equal to
+              <seealso marker="#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso>
+              is returned. The tuple elements are integers
+              or the atom <c>unbound</c>. Logical processor identifiers
+              are represented as integers. The <c>N</c>th
+              element of the tuple equals the current binding for
+              the scheduler with the scheduler identifier equal to
+              <c>N</c>. For example, if the schedulers are bound,
+              <c>element(erlang:system_info(scheduler_id),
+              erlang:system_info(scheduler_bindings))</c> returns
+              the identifier of the logical processor that the calling
+              process is executing on.</p>
+            <p>Notice that only schedulers online can be bound to logical
+              processors.</p>
+            <p>For more information, see command-line argument
+              <seealso marker="erts:erl#+sbt"><c>+sbt</c></seealso>
+              in <c>erl(1)</c> and
+              <seealso marker="#system_info_schedulers_online">
+              <c>erlang:system_info(schedulers_online)</c></seealso>.</p>
           </item>
           <tag><c>scheduler_id</c></tag>
           <item>
-          <marker id="system_info_scheduler_id"></marker>
+            <marker id="system_info_scheduler_id"></marker>
             <p>Returns the scheduler ID (<c>SchedulerId</c>) of the
               scheduler thread that the calling process is executing
               on. <c><anno>SchedulerId</anno></c> is a positive integer,
-              where
-              <c><![CDATA[1 <= SchedulerId <= erlang:system_info(schedulers)]]></c>.
-              See also
-              <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>.</p>
+              where <c><![CDATA[1 <= SchedulerId <=
+              erlang:system_info(schedulers)]]></c>.</p>
+            <p>See also
+              <seealso marker="#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso>.</p>
           </item>
           <tag><c>schedulers</c></tag>
           <item>
-          <marker id="system_info_schedulers"></marker>
+            <marker id="system_info_schedulers"></marker>
             <p>Returns the number of scheduler threads used by
               the emulator. Scheduler threads online schedules Erlang
               processes and Erlang ports, and execute Erlang code
@@ -7941,45 +8038,57 @@ ok
             <p>The number of scheduler threads is determined at
               emulator boot time and cannot be changed later.
               However, the number of schedulers online can
-	      be changed at any time.</p>
+              be changed at any time.</p>
             <p>See also
-              <seealso marker="#system_flag_schedulers_online">erlang:system_flag(schedulers_online, SchedulersOnline)</seealso>,
-	      <seealso marker="#system_info_schedulers_online">erlang:system_info(schedulers_online)</seealso>,
-	      <seealso marker="#system_info_scheduler_id">erlang:system_info(scheduler_id)</seealso>,
-              <seealso marker="#system_flag_multi_scheduling">erlang:system_flag(multi_scheduling, BlockState)</seealso>,
-              <seealso marker="#system_info_multi_scheduling">erlang:system_info(multi_scheduling)</seealso>,
-	      <seealso marker="#system_info_normal_multi_scheduling_blockers">erlang:system_info(normal_multi_scheduling_blockers)</seealso>
-              and
-              <seealso marker="#system_info_multi_scheduling_blockers">erlang:system_info(multi_scheduling_blockers)</seealso>.</p>
+              <seealso marker="#system_flag_schedulers_online">
+              <c>erlang:system_flag(schedulers_online,
+              SchedulersOnline)</c></seealso>,
+              <seealso marker="#system_info_schedulers_online">
+              <c>erlang:system_info(schedulers_online)</c></seealso>,
+              <seealso marker="#system_info_scheduler_id">
+              <c>erlang:system_info(scheduler_id)</c></seealso>,
+              <seealso marker="#system_flag_multi_scheduling">
+              <c>erlang:system_flag(multi_scheduling, BlockState)</c></seealso>,
+              <seealso marker="#system_info_multi_scheduling">
+              <c>erlang:system_info(multi_scheduling)</c></seealso>,
+              <seealso marker="#system_info_normal_multi_scheduling_blockers">
+              <c>erlang:system_info(normal_multi_scheduling_blockers)</c></seealso>
+              and <seealso marker="#system_info_multi_scheduling_blockers">
+              <c>erlang:system_info(multi_scheduling_blockers)</c></seealso>.
+            </p>
           </item>
           <tag><c>schedulers_online</c></tag>
           <item>
-          <marker id="system_info_schedulers_online"></marker>
+            <marker id="system_info_schedulers_online"></marker>
             <p>Returns the number of schedulers online. The scheduler
-	    identifiers of schedulers online satisfy the relationship
-	    <c><![CDATA[1 <= SchedulerId <= erlang:system_info(schedulers_online)]]></c>.</p>
-	    <p>For more information, see
-	    <seealso marker="#system_info_schedulers">erlang:system_info(schedulers)</seealso>
-	    and
-	    <seealso marker="#system_flag_schedulers_online">erlang:system_flag(schedulers_online, SchedulersOnline)</seealso>.</p>
+              identifiers of schedulers online satisfy the relationship
+              <c><![CDATA[1 <= SchedulerId <=
+              erlang:system_info(schedulers_online)]]></c>.</p>
+            <p>For more information, see
+              <seealso marker="#system_info_schedulers">
+              <c>erlang:system_info(schedulers)</c></seealso> and
+              <seealso marker="#system_flag_schedulers_online">
+              <c>erlang:system_flag(schedulers_online,
+              SchedulersOnline)</c></seealso>.</p>
           </item>
           <tag><c>smp_support</c></tag>
           <item>
             <p>Returns <c>true</c> if the emulator has been compiled
               with SMP support, otherwise <c>false</c> is returned.</p>
           </item>
-	  <tag><marker id="system_info_start_time"/><c>start_time</c></tag>
-	  <item>
+          <tag><marker id="system_info_start_time"/><c>start_time</c></tag>
+          <item>
             <p>The <seealso marker="#monotonic_time/0">Erlang monotonic
-	  time</seealso> in <c>native</c>
-	  <seealso marker="#type_time_unit">time unit</seealso> at the
-	  time when current Erlang runtime system instance started. See also
-	  <seealso marker="#system_info_end_time"><c>erlang:system_info(end_time)</c></seealso>.
-	  </p></item>
+              time</seealso> in <c>native</c>
+              <seealso marker="#type_time_unit">time unit</seealso> at the
+              time when current Erlang runtime system instance started.</p>
+            <p>See also <seealso marker="#system_info_end_time">
+              <c>erlang:system_info(end_time)</c></seealso>.</p>
+          </item>
           <tag><c>system_version</c></tag>
           <item>
             <p>Returns a string containing version number and
-	    some important properties, such as the number of schedulers.</p>
+              some important properties, such as the number of schedulers.</p>
           </item>
           <tag><c>system_architecture</c></tag>
           <item>
@@ -7993,112 +8102,114 @@ ok
           </item>
           <tag><c>thread_pool_size</c></tag>
           <item>
-          <marker id="system_info_thread_pool_size"></marker>
+            <marker id="system_info_thread_pool_size"></marker>
             <p>Returns the number of async threads in the async thread
               pool used for asynchronous driver calls
-              (<seealso marker="erts:erl_driver#driver_async">driver_async()</seealso>).
+              (<seealso marker="erts:erl_driver#driver_async">
+              <c>driver_async()</c></seealso>).
               The value is given as an integer.</p>
           </item>
-
-	  <tag><c>time_correction</c></tag>
-	  <item>
-	    <marker id="system_info_time_correction"></marker>
-	    <p>Returns a boolean value indicating whether
-	  <seealso marker="time_correction#Time_Correction">time correction</seealso>
-	  is enabled or not.
-	  </p></item>
-	  <tag><c>time_offset</c></tag>
-	  <item>
-	    <marker id="system_info_time_offset"></marker>
-	    <p>Returns the state of the time offset:</p>
-	  <taglist>
-	    <tag><c>preliminary</c></tag>
-	    <item>
-            <p>The time offset is preliminary, and will be changed
-	    at a later time when being finalized. The preliminary time offset
-	    is used during the preliminary phase of the
-	    <seealso marker="time_correction#Single_Time_Warp_Mode">single
-	    time warp mode</seealso>.</p></item>
-
-	    <tag><c>final</c></tag>
-	    <item>
-            <p>The time offset is final. This either because
-	    <seealso marker="time_correction#No_Time_Warp_Mode">no
-	    time warp mode</seealso> is used, or because the time
-	    offset have been finalized when
-	    <seealso marker="time_correction#Single_Time_Warp_Mode">single
-	    time warp mode</seealso> is used.</p></item>
-
-	    <tag><c>volatile</c></tag>
-	    <item>
-            <p>The time offset is volatile. That is, it can
-	    change at any time. This is because
-	    <seealso marker="time_correction#Multi_Time_Warp_Mode">multi
-	    time warp mode</seealso> is used.</p></item>
-	  </taglist>
-	  </item>
-	  <tag><marker id="system_info_time_warp_mode"/><c>time_warp_mode</c></tag>
-	  <item>
+          <tag><c>time_correction</c></tag>
+          <item>
+            <marker id="system_info_time_correction"></marker>
+            <p>Returns a boolean value indicating whether
+              <seealso marker="time_correction#Time_Correction">
+              time correction</seealso> is enabled or not.</p>
+          </item>
+          <tag><c>time_offset</c></tag>
+          <item>
+            <marker id="system_info_time_offset"></marker>
+            <p>Returns the state of the time offset:</p>
+            <taglist>
+              <tag><c>preliminary</c></tag>
+              <item>
+                <p>The time offset is preliminary, and will be changed
+                  and finalized later. The preliminary time offset
+                  is used during the preliminary phase of the
+                  <seealso marker="time_correction#Single_Time_Warp_Mode">
+                  single time warp mode</seealso>.</p>
+              </item>
+              <tag><c>final</c></tag>
+              <item>
+                <p>The time offset is final. This either because
+                  <seealso marker="time_correction#No_Time_Warp_Mode">
+                  no time warp mode</seealso> is used, or because the time
+                  offset have been finalized when
+                  <seealso marker="time_correction#Single_Time_Warp_Mode">
+                  single time warp mode</seealso> is used.</p>
+              </item>
+              <tag><c>volatile</c></tag>
+              <item>
+                <p>The time offset is volatile. That is, it can
+                  change at any time. This is because
+                  <seealso marker="time_correction#Multi_Time_Warp_Mode">
+                  multi-time warp mode</seealso> is used.</p>
+              </item>
+            </taglist>
+          </item>
+          <tag><marker id="system_info_time_warp_mode"/>
+            <c>time_warp_mode</c></tag>
+          <item>
             <p>Returns a value identifying the
-	  <seealso marker="time_correction#Time_Warp_Modes">time warp
-	  mode</seealso> being used:</p>
-	  <taglist>
-	    <tag><c>no_time_warp</c></tag>
-	    <item>
-            <p>The <seealso marker="time_correction#No_Time_Warp_Mode">no
-	    time warp mode</seealso> is used.</p></item>
-
-	    <tag><c>single_time_warp</c></tag>
-	    <item>
-            <p>The <seealso marker="time_correction#Single_Time_Warp_Mode">single
-	    time warp mode</seealso> is used.</p></item>
-
-	    <tag><c>multi_time_warp</c></tag>
-	    <item>
-            <p>The <seealso marker="time_correction#Multi_Time_Warp_Mode">multi
-	    time warp mode</seealso> is used.</p></item>
-	  </taglist>
-	  </item>
+              <seealso marker="time_correction#Time_Warp_Modes">
+              time warp mode</seealso> that is used:</p>
+            <taglist>
+              <tag><c>no_time_warp</c></tag>
+              <item>The <seealso marker="time_correction#No_Time_Warp_Mode">
+                no time warp mode</seealso> is used.
+              </item>
+              <tag><c>single_time_warp</c></tag>
+              <item>The <seealso marker="time_correction#Single_Time_Warp_Mode">
+                single time warp mode</seealso> is used.
+              </item>
+              <tag><c>multi_time_warp</c></tag>
+              <item>The <seealso marker="time_correction#Multi_Time_Warp_Mode">
+                multi-time warp mode</seealso> is used.
+              </item>
+            </taglist>
+          </item>
           <tag><c>tolerant_timeofday</c></tag>
           <item>
-          <marker id="system_info_tolerant_timeofday"></marker>
-            <p>Returns whether a pre erts-7.0 backwards compatible compensation
-	    for sudden changes of system time is <c>enabled</c> or <c>disabled</c>.
-	    Such compensation is <c>enabled</c> when the
-	    <seealso marker="#system_info_time_offset">time offset</seealso> is
-	    <c>final</c>, and
-	    <seealso marker="#system_info_time_correction">time correction</seealso>
-	    is enabled.</p>
+            <marker id="system_info_tolerant_timeofday"></marker>
+            <p>Returns whether a pre <c>ERTS</c> 7.0 backwards compatible
+              compensation for sudden changes of system time is <c>enabled</c>
+              or <c>disabled</c>. Such compensation is <c>enabled</c> when the
+              <seealso marker="#system_info_time_offset">time offset</seealso>
+              is <c>final</c>, and
+              <seealso marker="#system_info_time_correction">
+              time correction</seealso> is enabled.</p>
           </item>
           <tag><c>trace_control_word</c></tag>
           <item>
             <p>Returns the value of the node trace control word. For
-              more information, see function <c>get_tcw</c> in Section
-              <seealso marker="erts:match_spec#get_tcw">Match Specifications in Erlang</seealso> in the User's Guide.</p>
+              more information, see function <c>get_tcw</c> in section
+              <seealso marker="erts:match_spec#get_tcw">
+              Match Specifications in Erlang</seealso> in the User's Guide.</p>
           </item>
           <tag><c>update_cpu_info</c></tag>
           <item>
-          <marker id="update_cpu_info"></marker>
+            <marker id="update_cpu_info"></marker>
             <p>The runtime system rereads the CPU information available
-	       and updates its internally stored information about the
-	       <seealso marker="#system_info_cpu_topology_detected">detected
-               CPU topology</seealso> and the number of logical processors
-	       <seealso marker="#logical_processors">configured</seealso>,
-	       <seealso marker="#logical_processors_online">online</seealso>, and
-	       <seealso marker="#logical_processors_available">available</seealso>.</p>
-               <p>If the CPU information has changed since the last time
-               it was read, the atom <c>changed</c> is returned, otherwise
-               the atom <c>unchanged</c>. If the CPU information has changed,
-	       you probably want to
-	       <seealso marker="#system_flag_schedulers_online">adjust the
-               number of schedulers online</seealso>. You typically want
-               to have as many schedulers online as
-	       <seealso marker="#logical_processors_available">logical
-               processors available</seealso>.</p>
+              and updates its internally stored information about the
+              <seealso marker="#system_info_cpu_topology_detected">detected
+              CPU topology</seealso> and the number of logical processors
+              <seealso marker="#logical_processors">configured</seealso>,
+              <seealso marker="#logical_processors_online">online</seealso>,
+              and <seealso marker="#logical_processors_available">
+              available</seealso>.</p>
+            <p>If the CPU information has changed since the last time
+              it was read, the atom <c>changed</c> is returned, otherwise
+              the atom <c>unchanged</c>. If the CPU information has changed,
+              you probably want to
+              <seealso marker="#system_flag_schedulers_online">adjust the
+              number of schedulers online</seealso>. You typically want
+              to have as many schedulers online as
+              <seealso marker="#logical_processors_available">logical
+              processors available</seealso>.</p>
           </item>
           <tag><c>version</c></tag>
           <item>
-          <marker id="system_info_version"></marker>
+            <marker id="system_info_version"></marker>
             <p>Returns a string containing the version number of the
               emulator.</p>
           </item>
@@ -8117,11 +8228,11 @@ ok
           </item>
           <tag><c>{wordsize, external}</c></tag>
           <item>
-	    <p>Returns the true word size of the emulator, that is,
-               the size of a pointer. The value is given in bytes
-               as an integer. On a pure 32-bit architecture, 4 is
-               returned. On both a half word and on a pure
-	       64-bit architecture, 8 is returned.</p>
+            <p>Returns the true word size of the emulator, that is,
+              the size of a pointer. The value is given in bytes
+              as an integer. On a pure 32-bit architecture, 4 is
+              returned. On both a half word and on a pure
+              64-bit architecture, 8 is returned.</p>
           </item>
         </taglist>
         <note>
@@ -8140,32 +8251,35 @@ ok
       <type name="system_monitor_option"/>
       <desc>
         <p>Returns the current system monitoring settings set by
-          <seealso marker="#system_monitor/2">erlang:system_monitor/2</seealso>
+          <seealso marker="#system_monitor/2">
+          <c>erlang:system_monitor/2</c></seealso>
           as <c>{<anno>MonitorPid</anno>, <anno>Options</anno>}</c>,
-          or <c>undefined</c> if there
-          are no settings. The order of the options can be different
-          from the one that was set.</p>
+          or <c>undefined</c> if no settings exist. The order of the
+          options can be different from the one that was set.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_monitor" arity="1"/>
-      <fsummary>Sets or clears system performance monitoring options.</fsummary>
+      <fsummary>Set or clear system performance monitoring options.</fsummary>
       <type name="system_monitor_option"/>
       <desc>
         <p>When called with argument <c>undefined</c>, all
           system performance monitoring settings are cleared.</p>
         <p>Calling the function with <c>{<anno>MonitorPid</anno>,
           <anno>Options</anno>}</c> as argument is the same as calling
-          <seealso marker="#system_monitor/2"><c>erlang:system_monitor(<anno>MonitorPid</anno>, <anno>Options</anno>)</c></seealso>.</p>
+          <seealso marker="#system_monitor/2">
+          <c>erlang:system_monitor(<anno>MonitorPid</anno>,
+          <anno>Options</anno>)</c></seealso>.</p>
         <p>Returns the previous system monitor settings just like
-          <seealso marker="#system_monitor/0">erlang:system_monitor/0</seealso>.</p>
+          <seealso marker="#system_monitor/0">
+          <c>erlang:system_monitor/0</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="system_monitor" arity="2"/>
-      <fsummary>Sets system performance monitoring options.</fsummary>
+      <fsummary>Set system performance monitoring options.</fsummary>
       <type name="system_monitor_option"/>
       <desc>
         <p>Sets the system performance monitoring options.
@@ -8184,12 +8298,12 @@ ok
             <p>One of the tuples is <c>{timeout, GcTime}</c>, where
               <c>GcTime</c> is the time for the garbage
               collection in milliseconds. The other tuples are
-              tagged with <c>heap_size</c>, <c>heap_block_size</c>
+              tagged with <c>heap_size</c>, <c>heap_block_size</c>,
               <c>stack_size</c>, <c>mbuf_size</c>, <c>old_heap_size</c>,
               and <c>old_heap_block_size</c>. These tuples are
               explained in the description of trace message
-              <seealso marker="#gc_minor_start">gc_minor_start</seealso> (see
-              <seealso marker="#trace/3">erlang:trace/3</seealso>).
+              <seealso marker="#gc_minor_start"><c>gc_minor_start</c></seealso>
+              (see <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>).
               New tuples can be added, and the order of the tuples in
               the <c>Info</c> list can be changed at any time without
               prior notice.</p>
@@ -8220,7 +8334,7 @@ ok
               <c>timeout</c>, <c>ready_input</c>, <c>ready_output</c>,
               <c>event</c>, and <c>outputv</c> (when the port
               is used by distribution). Value <c>Millis</c> in
-              the <c>timeout</c> tuple informs about the
+              tuple <c>timeout</c> informs about the
               uninterrupted execution time of the process or port, which
               always is equal to or higher than the <c>Time</c> value
               supplied when starting the trace. New tuples can be
@@ -8231,7 +8345,7 @@ ok
               drivers that take too long to execute. 1 ms is
               considered a good maximum time for a driver callback
               or a NIF. However, a time-sharing system is usually to
-              consider everything below 100 ms as "possible" and
+              consider everything &lt; 100 ms as "possible" and
               fairly "normal". However, longer schedule times can
               indicate swapping or a misbehaving NIF/driver.
               Misbehaving NIFs and drivers can cause bad resource
@@ -8249,10 +8363,11 @@ ok
             <p>The monitor message is sent if the sum of the sizes of
               all memory blocks allocated for all heap generations after
               a garbage collection is equal to or higher than <c>Size</c>.</p>
-            <p>When a process is killed by <seealso marker="#process_flag_max_heap_size">
+            <p>When a process is killed by
+              <seealso marker="#process_flag_max_heap_size">
               <c>max_heap_size</c></seealso>, it is killed before the
               garbage collection is complete and thus no large heap message
-              will be sent.</p>
+              is sent.</p>
           </item>
           <tag><c>busy_port</c></tag>
           <item>
@@ -8274,7 +8389,8 @@ ok
           </item>
         </taglist>
         <p>Returns the previous system monitor settings just like
-          <seealso marker="#system_monitor/0">erlang:system_monitor/0</seealso>.</p>
+          <seealso marker="#system_monitor/0">
+          <c>erlang:system_monitor/0</c></seealso>.</p>
         <note>
           <p>If a monitoring process gets so large that it itself
             starts to cause system monitor messages when garbage
@@ -8299,7 +8415,8 @@ ok
       <type name="system_profile_option"/>
       <desc>
         <p>Returns the current system profiling settings set by
-          <seealso marker="#system_profile/2">erlang:system_profile/2</seealso>
+          <seealso marker="#system_profile/2">
+          <c>erlang:system_profile/2</c></seealso>
           as <c>{<anno>ProfilerPid</anno>, <anno>Options</anno>}</c>,
           or <c>undefined</c> if there
           are no settings. The order of the options can be different
@@ -8319,106 +8436,116 @@ ok
         <taglist>
           <tag><c>exclusive</c></tag>
           <item>
-          <p>If a synchronous call to a port from a process is done, the
-	     calling process is considered not runnable during the call
-             runtime to the port. The calling process is notified as
-             <c>inactive</c>, and later <c>active</c> when the port
-	     callback returns.</p>
+            <p>If a synchronous call to a port from a process is done, the
+              calling process is considered not runnable during the call
+              runtime to the port. The calling process is notified as
+              <c>inactive</c>, and later <c>active</c> when the port
+              callback returns.</p>
           </item>
           <tag><c>monotonic_timestamp</c></tag>
           <item>
-            <p>Timestamps in profile messages will use
-	    <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	    monotonic time</seealso>. The time-stamp (Ts) has the same
-	    format and value as produced by
-	    <c>erlang:monotonic_time(nano_seconds)</c>.</p>
+            <p>Time stamps in profile messages use
+              <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+              monotonic time</seealso>. The time stamp (Ts) has the same
+              format and value as produced by
+              <c>erlang:monotonic_time(nano_seconds)</c>.</p>
           </item>
           <tag><c>runnable_procs</c></tag>
           <item>
-          <p>If a process is put into or removed from the run queue, a
-             message, <c>{profile, Pid, State, Mfa, Ts}</c>, is sent to
-	     <c><anno>ProfilerPid</anno></c>. Running processes that
-             are reinserted into the run queue after having been
-	     preempted do not trigger this message.</p>
+            <p>If a process is put into or removed from the run queue, a
+              message, <c>{profile, Pid, State, Mfa, Ts}</c>, is sent to
+              <c><anno>ProfilerPid</anno></c>. Running processes that
+              are reinserted into the run queue after having been
+              pre-empted do not trigger this message.</p>
           </item>
           <tag><c>runnable_ports</c></tag>
           <item>
-          <p>If a port is put into or removed from the run queue, a 
-             message, <c>{profile, Port, State, 0, Ts}</c>, is sent to
-	     <c><anno>ProfilerPid</anno></c>.</p>
+            <p>If a port is put into or removed from the run queue, a 
+              message, <c>{profile, Port, State, 0, Ts}</c>, is sent to
+              <c><anno>ProfilerPid</anno></c>.</p>
           </item>
           <tag><c>scheduler</c></tag>
           <item>
-          <p>If a scheduler is put to sleep or awoken, a message,
-             <c>{profile, scheduler, Id, State, NoScheds, Ts}</c>, is
-             sent to <c><anno>ProfilerPid</anno></c>.</p>
+            <p>If a scheduler is put to sleep or awoken, a message,
+              <c>{profile, scheduler, Id, State, NoScheds, Ts}</c>, is
+              sent to <c><anno>ProfilerPid</anno></c>.</p>
           </item>
           <tag><c>strict_monotonic_timestamp</c></tag>
           <item>
-            <p>Timestamps in profile messages will consisting of
-	    <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	    monotonic time</seealso> and a monotonically increasing
-	    integer. The time-stamp (Ts) has the same format and value
-	    as produced by <c>{erlang:monotonic_time(nano_seconds),
-	    erlang:unique_integer([monotonic])}</c>.</p>
+            <p>Time stamps in profile messages consist of
+              <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+              monotonic time</seealso> and a monotonically increasing
+              integer. The time stamp (Ts) has the same format and value
+              as produced by <c>{erlang:monotonic_time(nano_seconds),
+              erlang:unique_integer([monotonic])}</c>.</p>
           </item>
           <tag><c>timestamp</c></tag>
           <item>
-            <p>Timestamps in profile messages will include a
-            time-stamp (Ts) that has the same form as returned by
-            <c>erlang:now()</c>. This is also the default if no
-	    timestamp flag is given. If <c>cpu_timestamp</c> has
-	    been enabled via <c>erlang:trace/3</c>, this will also
-	    effect the timestamp produced in profiling messages
-	    when <c>timestamp</c> flag is enabled.</p>
+            <p>Time stamps in profile messages include a
+              time stamp (Ts) that has the same form as returned by
+              <c>erlang:now()</c>. This is also the default if no
+              time stamp flag is specified. If <c>cpu_timestamp</c> has
+              been enabled through
+              <seealso marker="erlang:trace/3"><c>erlang:trace/3</c></seealso>,
+              this also effects the time stamp produced in profiling messages
+              when flag <c>timestamp</c> is enabled.</p>
           </item>
         </taglist>
-        <note><p><c>erlang:system_profile</c> is considered experimental
-          and its behavior can change in a future release.</p>
+        <note>
+          <p><c>erlang:system_profile</c> is considered experimental
+            and its behavior can change in a future release.</p>
         </note>
       </desc>
     </func>
+
     <func>
       <name name="system_time" arity="0"/>
-      <fsummary>Current Erlang system time</fsummary>
-      <desc>
-	<p>Returns current
-	<seealso marker="time_correction#Erlang_System_Time">Erlang system time</seealso>
-	in <c>native</c>
-	<seealso marker="#type_time_unit">time unit</seealso>.</p>
-
-	<p>Calling <c>erlang:system_time()</c> is equivalent to: 
-	<seealso marker="#monotonic_time/0"><c>erlang:monotonic_time()</c></seealso><c>
-	+
-        </c><seealso marker="#time_offset/0"><c>erlang:time_offset()</c></seealso>.</p>
-
-	<note><p>This time is <em>not</em> a monotonically increasing time
-	in the general case. For more information, see the documentation of
-	<seealso marker="time_correction#Time_Warp_Modes">time warp modes</seealso> in the
-	ERTS User's Guide.</p></note>
+      <fsummary>Current Erlang system time.</fsummary>
+      <desc>
+        <p>Returns current
+          <seealso marker="time_correction#Erlang_System_Time">
+          Erlang system time</seealso> in <c>native</c>
+          <seealso marker="#type_time_unit">time unit</seealso>.</p>
+        <p>Calling <c>erlang:system_time()</c> is equivalent to
+          <seealso marker="#monotonic_time/0">
+          <c>erlang:monotonic_time()</c></seealso><c> +
+          </c><seealso marker="#time_offset/0">
+          <c>erlang:time_offset()</c></seealso>.</p>
+        <note>
+          <p>This time is <em>not</em> a monotonically increasing time
+            in the general case. For more information, see the documentation of
+            <seealso marker="time_correction#Time_Warp_Modes">
+            time warp modes</seealso> in the User's Guide.</p>
+        </note>
       </desc>
     </func>
+
     <func>
       <name name="system_time" arity="1"/>
-      <fsummary>Current Erlang system time</fsummary>
-      <desc>
-	<p>Returns current
-	<seealso marker="time_correction#Erlang_System_Time">Erlang system time</seealso>
-	converted into the <c><anno>Unit</anno></c> passed as argument.</p>
-
-	<p>Calling <c>erlang:system_time(<anno>Unit</anno>)</c> is equivalent to: 
-	<seealso marker="#convert_time_unit/3"><c>erlang:convert_time_unit</c></seealso><c>(</c><seealso marker="#system_time/0"><c>erlang:system_time()</c></seealso><c>,
-	native, <anno>Unit</anno>)</c>.</p>
-
-	<note><p>This time is <em>not</em> a monotonically increasing time
-	in the general case. For more information, see the documentation of
-	<seealso marker="time_correction#Time_Warp_Modes">time warp modes</seealso> in the
-	ERTS User's Guide.</p></note>
+      <fsummary>Current Erlang system time.</fsummary>
+      <desc>
+        <p>Returns current
+          <seealso marker="time_correction#Erlang_System_Time">
+          Erlang system time</seealso>
+          converted into the <c><anno>Unit</anno></c> passed as argument.</p>
+        <p>Calling <c>erlang:system_time(<anno>Unit</anno>)</c> is equivalent
+          to <seealso marker="#convert_time_unit/3">
+          <c>erlang:convert_time_unit</c></seealso><c>(</c><seealso
+          marker="#system_time/0"><c>erlang:system_time()</c></seealso><c>,
+          native, <anno>Unit</anno>)</c>.</p>
+        <note>
+          <p>This time is <em>not</em> a monotonically increasing time
+            in the general case. For more information, see the documentation of
+            <seealso marker="time_correction#Time_Warp_Modes">
+            time warp modes</seealso> in the User's Guide.</p>
+        </note>
       </desc>
     </func>
+
     <func>
       <name name="term_to_binary" arity="1"/>
-      <fsummary>Encodes a term to an Erlang external term format binary.</fsummary>
+      <fsummary>Encode a term to an Erlang external term format binary.
+      </fsummary>
       <desc>
         <p>Returns a binary data object that is the result of encoding
           <c><anno>Term</anno></c> according to the Erlang external
@@ -8427,64 +8554,65 @@ ok
           writing a term to a file in an efficient way, or sending an
           Erlang term to some type of communications channel not
           supported by distributed Erlang.</p>
-        <p>See also
-          <seealso marker="#binary_to_term/1">binary_to_term/1</seealso>.</p>
+        <p>See also <seealso marker="#binary_to_term/1">
+          <c>binary_to_term/1</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="term_to_binary" arity="2"/>
-      <fsummary>Encodes a term to en Erlang external term format binary.</fsummary>
+      <fsummary>Encode a term to en Erlang external term format binary.
+      </fsummary>
       <desc>
         <p>Returns a binary data object that is the result of encoding
           <c><anno>Term</anno></c> according to the Erlang external
           term format.</p>
         <p>If option <c>compressed</c> is provided, the external term
           format is compressed. The compressed format is automatically
-          recognized by <c>binary_to_term/1</c> as from Erlang R7B.</p>
+          recognized by <c>binary_to_term/1</c> as from Erlang/OTP R7B.</p>
         <p>A compression level can be specified by giving option
           <c>{compressed, <anno>Level</anno>}</c>.
           <c><anno>Level</anno></c> is an integer
           with range 0..9, where:</p>
         <list type="bulleted">
-          <item><c>0</c> - No compression is done (it is the same as
-            giving no <c>compressed</c> option).</item>
-          <item><c>1</c> - Takes least time but may not compress
-            as well as the higher levels.</item>
-          <item><c>6</c> - Default level when option <c>compressed</c>
-	    is provided.</item>
-          <item><c>9</c> - Takes most time and tries to produce a smaller
+          <item><p><c>0</c> - No compression is done (it is the same as
+            giving no <c>compressed</c> option).</p></item>
+          <item><p><c>1</c> - Takes least time but may not compress
+            as well as the higher levels.</p></item>
+          <item><p><c>6</c> - Default level when option <c>compressed</c>
+            is provided.</p></item>
+          <item><p><c>9</c> - Takes most time and tries to produce a smaller
             result. Notice "tries" in the preceding sentence; depending
             on the input term, level 9 compression either does or does
-            not produce a smaller result than level 1 compression.</item>
+            not produce a smaller result than level 1 compression.</p></item>
         </list>
         <p>Option <c>{minor_version, <anno>Version</anno>}</c>
-          can be used to control
-          some encoding details. This option was introduced in OTP R11B-4.
+          can be used to control some
+          encoding details. This option was introduced in Erlang/OTP R11B-4.
           The valid values for <c><anno>Version</anno></c> are
           <c>0</c> and <c>1</c>.</p>
-        <p>As from OTP 17.0, <c>{minor_version, 1}</c> is the default. It
+        <p>As from Erlang/OTP 17.0, <c>{minor_version, 1}</c> is the default. It
           forces any floats in the term to be encoded in a more
           space-efficient and exact way (namely in the 64-bit IEEE format,
           rather than converted to a textual representation).</p>
-        <p>As from OTP R11B-4, <c>binary_to_term/1</c> can decode this
+        <p>As from Erlang/OTP R11B-4, <c>binary_to_term/1</c> can decode this
           representation.</p>
         <p><c>{minor_version, 0}</c> means that floats are encoded
           using a textual representation. This option is useful to
-          ensure that releases before OTP R11B-4 can decode resulting
+          ensure that releases before Erlang/OTP R11B-4 can decode resulting
           binary.</p>
-        <p>See also
-          <seealso marker="#binary_to_term/1">binary_to_term/1</seealso>.</p>
+        <p>See also <seealso marker="#binary_to_term/1">
+          <c>binary_to_term/1</c></seealso>.</p>
       </desc>
     </func>
 
     <func>
       <name name="throw" arity="1"/>
-      <fsummary>Throws an exception.</fsummary>
+      <fsummary>Throw an exception.</fsummary>
       <desc>
         <p>A non-local return from a function. If evaluated within a
-          <c>catch</c>, <c>catch</c> returns value <c><anno>Any</anno></c>.</p>
-        <p>Example:</p>
+          <c>catch</c>, <c>catch</c> returns value <c><anno>Any</anno></c>.
+          Example:</p>
         <pre>
 > <input>catch throw({hello, there}).</input>
 {hello,there}</pre>
@@ -8498,8 +8626,7 @@ ok
       <desc>
         <p>Returns the current time as <c>{Hour, Minute, Second}</c>.</p>
         <p>The time zone and Daylight Saving Time correction depend on
-          the underlying OS.</p>
-        <p>Example:</p>
+          the underlying OS. Example:</p>
         <pre>
 > <input>time().</input>
 {9,42,44}</pre>
@@ -8508,86 +8635,94 @@ ok
 
     <func>
       <name name="time_offset" arity="0"/>
-      <fsummary>Current time offset</fsummary>
-      <desc>
-	<p>Returns the current time offset between
-	<seealso marker="time_correction#Erlang_Monotonic_Time">Erlang monotonic time</seealso>
-	and
-	<seealso marker="time_correction#Erlang_System_Time">Erlang system time</seealso> in
-	<c>native</c> <seealso marker="#type_time_unit">time unit</seealso>.
-	Current time offset added to an Erlang monotonic time gives
-	corresponding Erlang system time.</p>
-
-	<p>The time offset may or may not change during operation depending
-	on the <seealso marker="time_correction#Time_Warp_Modes">time
-	warp mode</seealso> used.</p>
-
-	<note>
-	  <p>A change in time offset may be observed at slightly
-	  different points in time by different processes.</p>
-
-	  <p>If the runtime system is in
-	  <seealso marker="time_correction#Multi_Time_Warp_Mode">multi
-	  time warp mode</seealso>, the time offset will be changed when
-	  the runtime system detects that the
-	  <seealso marker="time_correction#OS_System_Time">OS system
-	  time</seealso> has changed. The runtime system will, however,
-	  not detect this immediately when it happens. A task checking
-	  the time offset is scheduled to execute at least once a minute,
-	  so under normal operation this should be detected within a
-	  minute, but during heavy load it might take longer time.</p>
-	</note>
+      <fsummary>Current time offset.</fsummary>
+      <desc>
+        <p>Returns the current time offset between
+          <seealso marker="time_correction#Erlang_Monotonic_Time">
+          Erlang monotonic time</seealso> and
+          <seealso marker="time_correction#Erlang_System_Time">
+          Erlang system time</seealso> in
+          <c>native</c> <seealso marker="#type_time_unit">time unit</seealso>.
+          Current time offset added to an Erlang monotonic time gives
+          corresponding Erlang system time.</p>
+        <p>The time offset may or may not change during operation depending
+          on the <seealso marker="time_correction#Time_Warp_Modes">time
+          warp mode</seealso> used.</p>
+        <note>
+          <p>A change in time offset can be observed at slightly
+            different points in time by different processes.</p>
+          <p>If the runtime system is in
+            <seealso marker="time_correction#Multi_Time_Warp_Mode">multi-time
+            warp mode</seealso>, the time offset is changed when
+            the runtime system detects that the
+            <seealso marker="time_correction#OS_System_Time">OS system
+            time</seealso> has changed. The runtime system will, however,
+            not detect this immediately when it occurs. A task checking
+            the time offset is scheduled to execute at least once a minute;
+            so, under normal operation this is to be detected within a
+            minute, but during heavy load it can take longer time.</p>
+        </note>
       </desc>
     </func>
+
     <func>
       <name name="time_offset" arity="1"/>
-      <fsummary>Current time offset</fsummary>
+      <fsummary>Current time offset.</fsummary>
       <desc>
-	<p>Returns the current time offset between
-	<seealso marker="time_correction#Erlang_Monotonic_Time">Erlang monotonic time</seealso>
-	and
-	<seealso marker="time_correction#Erlang_System_Time">Erlang system time</seealso>
-	converted into the <c><anno>Unit</anno></c> passed as argument.</p>
-
-	<p>Same as calling	
-	<seealso marker="#convert_time_unit/3"><c>erlang:convert_time_unit</c></seealso><c>(</c><seealso marker="#time_offset/0"><c>erlang:time_offset()</c></seealso><c>, native, <anno>Unit</anno>)</c>
-	however optimized for commonly used <c><anno>Unit</anno></c>s.</p>
+        <p>Returns the current time offset between
+          <seealso marker="time_correction#Erlang_Monotonic_Time">
+          Erlang monotonic time</seealso> and
+          <seealso marker="time_correction#Erlang_System_Time">
+          Erlang system time</seealso>
+          converted into the <c><anno>Unit</anno></c> passed as argument.</p>
+        <p>Same as calling
+          <seealso marker="#convert_time_unit/3">
+          <c>erlang:convert_time_unit</c></seealso><c>(</c><seealso marker="#time_offset/0">
+          <c>erlang:time_offset()</c></seealso><c>, native,
+          <anno>Unit</anno>)</c>
+          however optimized for commonly used <c><anno>Unit</anno></c>s.</p>
       </desc>
     </func>
+
     <func>
       <name name="timestamp" arity="0"/>
-      <fsummary>Current Erlang System time</fsummary>
+      <fsummary>Current Erlang System time.</fsummary>
       <type name="timestamp"/>
       <desc>
-	<p>Returns current
-	<seealso marker="time_correction#Erlang_System_Time">Erlang system time</seealso>
-	on the format <c>{MegaSecs, Secs, MicroSecs}</c>. This format is 
-	the same as <seealso marker="kernel:os#timestamp/0"><c>os:timestamp/0</c></seealso>
-	and the deprecated <seealso marker="#now/0"><c>erlang:now/0</c></seealso>
-	uses. The reason for the existence of <c>erlang:timestamp()</c> is
-	purely to simplify usage for existing code that assumes this timestamp
-	format. Current Erlang system time can more efficiently be retrieved in
-	the time unit of your choice using
-	<seealso marker="#system_time/1"><c>erlang:system_time/1</c></seealso>.</p>
-
-	<p>The <c>erlang:timestamp()</c> BIF is equivalent to:</p><code type="none">
+        <p>Returns current
+          <seealso marker="time_correction#Erlang_System_Time">
+          Erlang system time</seealso>
+          on the format <c>{MegaSecs, Secs, MicroSecs}</c>. This format is 
+          the same as <seealso marker="kernel:os#timestamp/0">
+          <c>os:timestamp/0</c></seealso>
+          and the deprecated <seealso marker="#now/0">
+          <c>erlang:now/0</c></seealso>
+          use. The reason for the existence of <c>erlang:timestamp()</c> is
+          purely to simplify use for existing code that assumes this time stamp
+          format. Current Erlang system time can more efficiently be retrieved
+          in the time unit of your choice using
+          <seealso marker="#system_time/1">
+          <c>erlang:system_time/1</c></seealso>.</p>
+        <p>The <c>erlang:timestamp()</c> BIF is equivalent to:</p>
+<code type="none">
 timestamp() ->
     ErlangSystemTime = erlang:system_time(micro_seconds),
     MegaSecs = ErlangSystemTime div 1000000000000,
     Secs = ErlangSystemTime div 1000000 - MegaSecs*1000000,
     MicroSecs = ErlangSystemTime rem 1000000,
     {MegaSecs, Secs, MicroSecs}.</code>
-    <p>It, however, uses a native implementation which does
-    not build garbage on the heap and with slightly better
-    performance.</p>
-
-	<note><p>This time is <em>not</em> a monotonically increasing time
-	in the general case. For more information, see the documentation of
-	<seealso marker="time_correction#Time_Warp_Modes">time warp modes</seealso> in the
-	ERTS User's Guide.</p></note>
+        <p>It, however, uses a native implementation that does
+          not build garbage on the heap and with slightly better
+          performance.</p>
+        <note>
+          <p>This time is <em>not</em> a monotonically increasing time
+            in the general case. For more information, see the documentation of
+            <seealso marker="time_correction#Time_Warp_Modes">
+            time warp modes</seealso> in the User's Guide.</p>
+	</note>
       </desc>
-
     </func>
+
     <func>
       <name name="tl" arity="1"/>
       <fsummary>Tail of a list.</fsummary>
@@ -8605,7 +8740,7 @@ timestamp() ->
 
     <func>
       <name name="trace" arity="3"/>
-      <fsummary>Sets trace flags for a process or processes.</fsummary>
+      <fsummary>Set trace flags for a process or processes.</fsummary>
       <type name="trace_flag"/>
       <desc>
         <p>Turns on (if <c><anno>How</anno> == true</c>) or off (if
@@ -8615,49 +8750,43 @@ timestamp() ->
           <c><anno>PidPortSpec</anno></c>.</p>
         <p><c><anno>PidPortSpec</anno></c> is either a process identifier
           (pid) for a local process, a port identifier,
-        or one of the following atoms:</p>
+          or one of the following atoms:</p>
         <taglist>
           <tag><c>all</c></tag>
-          <item>
-            <p>All currently existing processes and ports and all that
-              will be created in the future.</p>
+          <item>All currently existing processes and ports and all that
+            will be created in the future.
           </item>
           <tag><c>processes</c></tag>
-          <item>
-            <p>All currently existing processes and all that will be created in the future.</p>
+          <item>All currently existing processes and all that will be created
+            in the future.
           </item>
           <tag><c>ports</c></tag>
-          <item>
-            <p>All currently existing ports and all that will be created in the future.</p>
+          <item>All currently existing ports and all that will be created in
+            the future.
           </item>
           <tag><c>existing</c></tag>
-          <item>
-            <p>All currently existing processes and ports.</p>
+          <item>All currently existing processes and ports.
           </item>
           <tag><c>existing_processes</c></tag>
-          <item>
-            <p>All currently existing processes.</p>
+          <item>All currently existing processes.
           </item>
           <tag><c>existing_ports</c></tag>
-          <item>
-            <p>All currently existing ports.</p>
+          <item>All currently existing ports.
           </item>
           <tag><c>new</c></tag>
-          <item>
-            <p>All processes and ports that will be created in the future.</p>
+          <item>All processes and ports that will be created in the future.
           </item>
           <tag><c>new_processes</c></tag>
-          <item>
-            <p>All processes that will be created in the future.</p>
+          <item>All processes that will be created in the future.
           </item>
           <tag><c>new_ports</c></tag>
-          <item>
-            <p>All ports that will be created in the future.</p>
+          <item>All ports that will be created in the future.
           </item>
         </taglist>
         <p><c><anno>FlagList</anno></c> can contain any number of the
           following flags (the "message tags" refers to the list of
-	  <seealso marker="#trace_3_trace_messages">trace messages</seealso>):</p>
+          <seealso marker="#trace_3_trace_messages">
+          <c>trace messages</c></seealso>):</p>
         <taglist>
           <tag><c>all</c></tag>
           <item>
@@ -8668,21 +8797,29 @@ timestamp() ->
           <tag><c>send</c></tag>
           <item>
             <p>Traces sending of messages.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_send"><c>send</c></seealso> and
-            <seealso marker="#trace_3_trace_messages_send_to_non_existing_process"><c>send_to_non_existing_process</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_send">
+              <c>send</c></seealso> and
+              <seealso marker="#trace_3_trace_messages_send_to_non_existing_process">
+              <c>send_to_non_existing_process</c></seealso>.</p>
           </item>
           <tag><c>'receive'</c></tag>
           <item>
             <p>Traces receiving of messages.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_receive"><c>'receive'</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_receive">
+                <c>'receive'</c></seealso>.</p>
           </item>
-<tag><c>call</c></tag>
+          <tag><c>call</c></tag>
           <item>
             <p>Traces certain function calls. Specify which function
-              calls to trace by calling
-              <seealso marker="#trace_pattern/3">erlang:trace_pattern/3</seealso>.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_call"><c>call</c></seealso> and
-            <seealso marker="#trace_3_trace_messages_return_from"><c>return_from</c></seealso>.</p>
+              calls to trace by calling <seealso marker="#trace_pattern/3">
+              <c>erlang:trace_pattern/3</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_call">
+              <c>call</c></seealso> and
+              <seealso marker="#trace_3_trace_messages_return_from">
+              <c>return_from</c></seealso>.</p>
           </item>
           <tag><c>silent</c></tag>
           <item>
@@ -8700,17 +8837,21 @@ timestamp() ->
               specification function <c>{silent,Bool}</c>, giving
               a high degree of control of which functions with which 
               arguments that trigger the trace.</p>
-              <p>Message tags: <seealso marker="#trace_3_trace_messages_call"><c>call</c></seealso>,
-              <seealso marker="#trace_3_trace_messages_return_from"><c>return_from</c></seealso>, and
-              <seealso marker="#trace_3_trace_messages_return_to"><c>return_to</c></seealso>. Or rather, the absence of.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_call">
+              <c>call</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_return_from">
+              <c>return_from</c></seealso>, and
+              <seealso marker="#trace_3_trace_messages_return_to">
+              <c>return_to</c></seealso>. Or rather, the absence of.</p>
           </item>
           <tag><c>return_to</c></tag>
           <item>
             <p>Used with the <c>call</c> trace flag.
               Traces the return from a traced function back to
               its caller. Only works for functions traced with
-              option <c>local</c> to
-              <seealso marker="#trace_pattern/3">erlang:trace_pattern/3</seealso>.</p>
+              option <c>local</c> to <seealso marker="#trace_pattern/3">
+              <c>erlang:trace_pattern/3</c></seealso>.</p>
             <p>The semantics is that a trace message is sent when a
               call traced function returns, that is, when a
               chain of tail recursive calls ends. Only one trace
@@ -8723,105 +8864,144 @@ timestamp() ->
             <p>To get trace messages containing return values from
               functions, use the <c>{return_trace}</c> match
               specification action instead.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_return_to"><c>return_to</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_return_to">
+              <c>return_to</c></seealso>.</p>
           </item>
           <tag><c>procs</c></tag>
           <item>
             <p>Traces process-related events.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_spawn"><c>spawn</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_spawned"><c>spawned</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_exit"><c>exit</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_register"><c>register</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_unregister"><c>unregister</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_link"><c>link</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_unlink"><c>unlink</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_getting_linked"><c>getting_linked</c></seealso>, and
-            <seealso marker="#trace_3_trace_messages_getting_unlinked"><c>getting_unlinked</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_spawn">
+              <c>spawn</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_spawned">
+              <c>spawned</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_exit">
+              <c>exit</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_register">
+              <c>register</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_unregister">
+              <c>unregister</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_link">
+              <c>link</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_unlink">
+              <c>unlink</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_getting_linked">
+              <c>getting_linked</c></seealso>, and
+              <seealso marker="#trace_3_trace_messages_getting_unlinked">
+              <c>getting_unlinked</c></seealso>.</p>
           </item>
           <tag><c>ports</c></tag>
           <item>
             <p>Traces port-related events.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_open"><c>open</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_closed"><c>closed</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_register"><c>register</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_unregister"><c>unregister</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_getting_linked"><c>getting_linked</c></seealso>, and
-            <seealso marker="#trace_3_trace_messages_getting_unlinked"><c>getting_unlinked</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_open">
+              <c>open</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_closed">
+              <c>closed</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_register">
+              <c>register</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_unregister">
+              <c>unregister</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_getting_linked">
+              <c>getting_linked</c></seealso>, and
+              <seealso marker="#trace_3_trace_messages_getting_unlinked">
+              <c>getting_unlinked</c></seealso>.</p>
           </item>
           <tag><c>running</c></tag>
           <item>
             <p>Traces scheduling of processes.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_in_proc"><c>in</c></seealso> and
-            <seealso marker="#trace_3_trace_messages_out_proc"><c>out</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_in_proc">
+              <c>in</c></seealso> and
+              <seealso marker="#trace_3_trace_messages_out_proc">
+              <c>out</c></seealso>.</p>
           </item>
           <tag><c>exiting</c></tag>
           <item>
             <p>Traces scheduling of exiting processes.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_in_exiting_proc"><c>in_exiting</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_out_exiting_proc"><c>out_exiting</c></seealso>, and
-	    <seealso marker="#trace_3_trace_messages_out_exited_proc"><c>out_exited</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_in_exiting_proc">
+              <c>in_exiting</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_out_exiting_proc">
+              <c>out_exiting</c></seealso>, and
+              <seealso marker="#trace_3_trace_messages_out_exited_proc">
+              <c>out_exited</c></seealso>.</p>
           </item>
           <tag><c>running_procs</c></tag>
           <item>
             <p>Traces scheduling of processes just like <c>running</c>.
-            However this option also includes schedule events when the
-            process executes within the context of a port without
-            being scheduled out itself.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_in_proc"><c>in</c></seealso> and
-            <seealso marker="#trace_3_trace_messages_out_proc"><c>out</c></seealso>.</p>
+              However, this option also includes schedule events when the
+              process executes within the context of a port without
+              being scheduled out itself.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_in_proc">
+              <c>in</c></seealso> and
+              <seealso marker="#trace_3_trace_messages_out_proc">
+              <c>out</c></seealso>.</p>
           </item>
           <tag><c>running_ports</c></tag>
           <item>
             <p>Traces scheduling of ports.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_in_port"><c>in</c></seealso> and
-            <seealso marker="#trace_3_trace_messages_out_port"><c>out</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_in_port">
+              <c>in</c></seealso> and
+              <seealso marker="#trace_3_trace_messages_out_port">
+              <c>out</c></seealso>.</p>
           </item>
           <tag><c>garbage_collection</c></tag>
           <item>
             <p>Traces garbage collections of processes.</p>
-            <p>Message tags: <seealso marker="#trace_3_trace_messages_gc_minor_start"><c>gc_minor_start</c></seealso>,
-            <seealso marker="#trace_3_trace_messages_gc_max_heap_size"><c>gc_max_heap_size</c></seealso> and
-	    <seealso marker="#trace_3_trace_messages_gc_minor_end"><c>gc_minor_end</c></seealso>.</p>
+            <p>Message tags:
+              <seealso marker="#trace_3_trace_messages_gc_minor_start">
+              <c>gc_minor_start</c></seealso>,
+              <seealso marker="#trace_3_trace_messages_gc_max_heap_size">
+              <c>gc_max_heap_size</c></seealso>, and
+              <seealso marker="#trace_3_trace_messages_gc_minor_end">
+              <c>gc_minor_end</c></seealso>.</p>
           </item>
           <tag><c>timestamp</c></tag>
           <item>
-            <p>Includes a time-stamp in all trace messages. The
-              time-stamp (Ts) has the same form as returned by
+            <p>Includes a time stamp in all trace messages. The
+              time stamp (Ts) has the same form as returned by
               <c>erlang:now()</c>.</p>
           </item>
           <tag><c>cpu_timestamp</c></tag>
           <item>
             <p>A global trace flag for the Erlang node that makes all
-              trace time-stamps using the <c>timestamp</c> flag to be
-	      in CPU time, not wall clock time. That is, <c>cpu_timestamp</c>
-	      will not be used if <c>monotonic_timestamp</c>, or
-	      <c>strict_monotonic_timestamp</c> is enabled.
+              trace time stamps using flag <c>timestamp</c> to be
+              in CPU time, not wall clock time. That is, <c>cpu_timestamp</c>
+              is not be used if <c>monotonic_timestamp</c> or
+              <c>strict_monotonic_timestamp</c> is enabled.
               Only allowed with <c><anno>PidPortSpec</anno>==all</c>. If the
               host machine OS does not support high-resolution
               CPU time measurements, <c>trace/3</c> exits with
               <c>badarg</c>. Notice that most OS do
               not synchronize this value across cores, so be prepared
-              that time might seem to go backwards when using this option.</p>
+              that time can seem to go backwards when using this option.</p>
           </item>
           <tag><c>monotonic_timestamp</c></tag>
           <item>
             <p>Includes an
-	    <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	    monotonic time</seealso> time-stamp in all trace messages. The
-            time-stamp (Ts) has the same format and value as produced by
-            <seealso marker="#monotonic_time-1"><c>erlang:monotonic_time(nano_seconds)</c></seealso>.
-            This flag overrides the <c>cpu_timestamp</c> flag.</p>
+              <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+              monotonic time</seealso> time stamp in all trace messages. The
+              time stamp (Ts) has the same format and value as produced by
+              <seealso marker="#monotonic_time-1">
+              <c>erlang:monotonic_time(nano_seconds)</c></seealso>.
+              This flag overrides flag <c>cpu_timestamp</c>.</p>
           </item>
           <tag><c>strict_monotonic_timestamp</c></tag>
           <item>
-            <p>Includes an timestamp consisting of
-	    <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
-	    monotonic time</seealso> and a monotonically increasing
-	    integer in all trace messages. The time-stamp (Ts) has the
-	    same format and value as produced by
-            <c>{</c><seealso marker="#monotonic_time-1"><c>erlang:monotonic_time(nano_seconds)</c></seealso><c>,</c>
-	    <seealso marker="#unique_integer-1"><c>erlang:unique_integer([monotonic])</c></seealso><c>}</c>.
-            This flag overrides the <c>cpu_timestamp</c> flag.</p>
+            <p>Includes an time stamp consisting of
+              <seealso marker="time_correction#Erlang_Monotonic_Time">Erlang
+              monotonic time</seealso> and a monotonically increasing
+              integer in all trace messages. The time stamp (Ts) has the
+              same format and value as produced by <c>{</c>
+              <seealso marker="#monotonic_time-1">
+              <c>erlang:monotonic_time(nano_seconds)</c></seealso><c>,</c>
+              <seealso marker="#unique_integer-1">
+              <c>erlang:unique_integer([monotonic])</c></seealso><c>}</c>.
+              This flag overrides flag <c>cpu_timestamp</c>.</p>
           </item>
           <tag><c>arity</c></tag>
           <item>
@@ -8859,34 +9039,34 @@ timestamp() ->
           </item>
           <tag><c>{tracer, TracerModule, TracerState}</c></tag>
           <item>
-            <p>Specifies that a tracer module should be called
-            instead of sending a trace message. The tracer module
-            can then ignore or change the trace message. For more details
-            on how to write a tracer module see
-            <seealso marker="erts:erl_tracer"><c>erl_tracer</c></seealso>
-          </p>
+            <p>Specifies that a tracer module is to be called
+              instead of sending a trace message. The tracer module
+              can then ignore or change the trace message. For more details
+              on how to write a tracer module, see
+              <seealso marker="erts:erl_tracer"><c>erl_tracer</c></seealso>.</p>
           </item>
         </taglist>
-        <p>If no <c>tracer</c> is given, the calling process
-        will be receiving all of the trace messages</p>
+        <p>If no <c>tracer</c> is specified, the calling process
+          receives all the trace messages.</p>
         <p>The effect of combining <c>set_on_first_link</c> with
-          <c>set_on_link</c> is the same as having
+          <c>set_on_link</c> is the same as
           <c>set_on_first_link</c> alone. Likewise for
           <c>set_on_spawn</c> and <c>set_on_first_spawn</c>.</p>
         <p>The tracing process receives the <em>trace messages</em> described
-	in the following list. <c>Pid</c> is the process identifier of the
-	traced process in which the traced event has occurred. The
-	third tuple element is the message tag.</p>
+          in the following list. <c>Pid</c> is the process identifier of the
+          traced process in which the traced event has occurred. The
+          third tuple element is the message tag.</p>
         <p>If flag <c>timestamp</c>, <c>strict_monotonic_timestamp</c>, or
-	<c>monotonic_timestamp</c> is given, the first tuple
-        element is <c>trace_ts</c> instead, and the time-stamp
-        is added as an extra element last in the message tuple. If
-	multiple timestamp flags are passed, <c>timestamp</c> has
-	precedence over <c>strict_monotonic_timestamp</c> which
-	in turn has precedence over <c>monotonic_timestamp</c>. All
-	timestamp flags are remembered, so if two are passed
-	and the one with highest precedence later is disabled
-	the other one will become active.</p>
+          <c>monotonic_timestamp</c> is specified, the first tuple
+          element is <c>trace_ts</c> instead, and the time stamp
+          is added as an extra element last in the message tuple. If
+          multiple time stamp flags are passed, <c>timestamp</c> has
+          precedence over <c>strict_monotonic_timestamp</c>, which
+          in turn has precedence over <c>monotonic_timestamp</c>. All
+          time stamp flags are remembered, so if two are passed
+          and the one with highest precedence later is disabled,
+          the other one becomes active.</p>
+        <p>Trace messages:</p>
         <marker id="trace_3_trace_messages"></marker>
         <taglist>
           <tag>
@@ -8898,7 +9078,7 @@ timestamp() ->
               process <c>To</c>.</p>
           </item>
           <tag>
-            <marker id="trace_3_trace_messages_send_to_non_existing_process"></marker>
+            <marker id="trace_3_trace_messages_send_to_non_existing_process"/>
             <c>{trace, PidPort, send_to_non_existing_process, Msg, To}</c>
           </tag>
           <item>
@@ -8911,9 +9091,9 @@ timestamp() ->
           </tag>
           <item>
             <p>When <c>PidPort</c> receives message <c>Msg</c>.
-            If <c>Msg</c> is set to timeout, then a receive
-            statement may have timedout, or the process received
-            a message with the payload <c>timeout</c>.</p>
+              If <c>Msg</c> is set to time-out, a receive
+              statement can have timed out, or the process received
+              a message with the payload <c>timeout</c>.</p>
           </item>
           <tag>
             <marker id="trace_3_trace_messages_call"></marker>
@@ -9047,7 +9227,7 @@ timestamp() ->
           </tag>
           <item>
             <p>When <c>Pid</c> opens a new port <c>Port</c> with
-              the running the <c>Driver</c>.</p>
+              the running <c>Driver</c>.</p>
             <p><c>Driver</c> is the name of the driver as an atom.</p>
           </item>
           <tag>
@@ -9055,7 +9235,7 @@ timestamp() ->
             <c>{trace, Port, closed, Reason}</c>
           </tag>
           <item>
-            <p>When <c>Port</c> closed with <c>Reason</c>.</p>
+            <p>When <c>Port</c> closes with <c>Reason</c>.</p>
           </item>
           <tag>
             <marker id="trace_3_trace_messages_in_proc"></marker>
@@ -9072,7 +9252,8 @@ timestamp() ->
             <marker id="trace_3_trace_messages_out_proc"></marker>
             <marker id="trace_3_trace_messages_out_exiting_proc"></marker>
             <marker id="trace_3_trace_messages_out_exited_proc"></marker>
-            <c>{trace, Pid, out | out_exiting | out_exited, {M, F, Arity} | 0}</c>
+            <c>{trace, Pid, out | out_exiting | out_exited, {M, F, Arity}
+            | 0}</c>
           </tag>
           <item>
             <p>When <c>Pid</c> is scheduled out. The process was
@@ -9086,11 +9267,13 @@ timestamp() ->
           </tag>
           <item>
             <p>When <c>Port</c> is scheduled to run. <c>Command</c> is the
-            first thing the port will execute, it may however run several
-            commands before being scheduled out. On some rare
-            occasions, the current function cannot be determined,
-            then the last element is <c>0</c>.</p>
-            <p>The possible commands are: <c>call | close | command | connect | control | flush | info | link | open | unlink</c></p>
+              first thing the port will execute, it can however run several
+              commands before being scheduled out. On some rare
+              occasions, the current function cannot be determined,
+              then the last element is <c>0</c>.</p>
+            <p>The possible commands are <c>call</c>, <c>close</c>,
+              <c>command</c>, <c>connect</c>, <c>control</c>, <c>flush</c>,
+              <c>info</c>, <c>link</c>, <c>open</c>, and <c>unlink</c>.</p>
           </item>
           <tag>
             <marker id="trace_3_trace_messages_out_port"></marker>
@@ -9101,8 +9284,7 @@ timestamp() ->
               was <c>Command</c>. On some rare occasions,
               the current function cannot be determined, then the last
               element is <c>0</c>. <c>Command</c> can contain the same
-              commands as <c>in</c>
-            </p>
+              commands as <c>in</c></p>
           </item>
           <tag>
             <marker id="trace_3_trace_messages_gc_minor_start"></marker>
@@ -9118,13 +9300,13 @@ timestamp() ->
             <taglist>
               <tag><c>heap_size</c></tag>
               <item>The size of the used part of the heap.</item>
-	      <tag><c>heap_block_size</c></tag>
-	      <item>The size of the memory block used for storing
-	        the heap and the stack.</item>
+              <tag><c>heap_block_size</c></tag>
+              <item>The size of the memory block used for storing
+                the heap and the stack.</item>
               <tag><c>old_heap_size</c></tag>
               <item>The size of the used part of the old heap.</item>
-	      <tag><c>old_heap_block_size</c></tag>
-	      <item>The size of the memory block used for storing
+              <tag><c>old_heap_block_size</c></tag>
+              <item>The size of the memory block used for storing
                 the old heap.</item>
               <tag><c>stack_size</c></tag>
               <item>The size of the stack.</item>
@@ -9138,14 +9320,15 @@ timestamp() ->
               <item>The total size of unique off-heap binaries referenced
                 from the process heap.</item>
               <tag><c>bin_vheap_block_size</c></tag>
-	      <item>The total size of binaries allowed in the virtual
-	        heap in the process before doing a garbage collection.</item>
+              <item>The total size of binaries allowed in the virtual
+                heap in the process before doing a garbage collection.</item>
               <tag><c>bin_old_vheap_size</c></tag>
               <item>The total size of unique off-heap binaries referenced
                 from the process old heap.</item>
               <tag><c>bin_old_vheap_block_size</c></tag>
-	      <item>The total size of binaries allowed in the virtual
-	        old heap in the process before doing a garbage collection.</item>
+              <item>The total size of binaries allowed in the virtual
+                old heap in the process before doing a garbage
+                collection.</item>
             </taglist>
             <p>All sizes are in words.</p>
           </item>
@@ -9154,13 +9337,12 @@ timestamp() ->
             <c>{trace, Pid, gc_max_heap_size, Info}</c>
           </tag>
           <item>
-            <p>
-              Sent when the <seealso marker="#process_flag_max_heap_size"><c>max_heap_size</c></seealso>
+            <p>Sent when the <seealso marker="#process_flag_max_heap_size">
+              <c>max_heap_size</c></seealso>
               is reached during garbage collection. <c>Info</c> contains the
               same kind of list as in message <c>gc_start</c>,
-              but the sizes reflect the sizes that triggered max_heap_size to
-              be reached.
-            </p>
+              but the sizes reflect the sizes that triggered
+              <c>max_heap_size</c> to be reached.</p>
           </item>
           <tag>
             <marker id="trace_3_trace_messages_gc_minor_end"></marker>
@@ -9168,7 +9350,8 @@ timestamp() ->
           </tag>
           <item>
             <p>Sent when young garbage collection is finished. <c>Info</c>
-              contains the same kind of list as in message <c>gc_minor_start</c>,
+              contains the same kind of list as in message
+              <c>gc_minor_start</c>,
               but the sizes reflect the new sizes after
               garbage collection.</p>
           </item>
@@ -9177,8 +9360,9 @@ timestamp() ->
             <c>{trace, Pid, gc_major_start, Info}</c>
           </tag>
           <item>
-            <p>Sent when fullsweep garbage collection is about to be started. <c>Info</c>
-                contains the same kind of list as in message <c>gc_minor_start</c>.</p>
+            <p>Sent when fullsweep garbage collection is about to be started.
+              <c>Info</c> contains the same kind of list as in message
+              <c>gc_minor_start</c>.</p>
           </item>
           <tag>
             <marker id="trace_3_trace_messages_gc_major_end"></marker>
@@ -9186,15 +9370,16 @@ timestamp() ->
           </tag>
           <item>
             <p>Sent when fullsweep garbage collection is finished. <c>Info</c>
-                contains the same kind of list as in message <c>gc_minor_start</c>
-              but the sizes reflect the new sizes after a fullsweep garbage collection.</p>
+              contains the same kind of list as in message
+              <c>gc_minor_start</c>, but the sizes reflect the new sizes after
+              a fullsweep garbage collection.</p>
           </item>
         </taglist>
         <p>If the tracing process/port dies or the tracer module returns
-        <c>remove</c>, the flags are silently removed.</p>
+          <c>remove</c>, the flags are silently removed.</p>
         <p>Each process can only be traced by one tracer. Therefore,
           attempts to trace an already traced process fail.</p>
-        <p>Returns: A number indicating the number of processes that
+        <p>Returns a number indicating the number of processes that
           matched <c><anno>PidPortSpec</anno></c>.
           If <c><anno>PidPortSpec</anno></c> is a process
           identifier, the return value is <c>1</c>.
@@ -9214,22 +9399,24 @@ timestamp() ->
       <fsummary>Notification when trace has been delivered.</fsummary>
       <desc>
         <p>The delivery of trace messages (generated by
-         <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>,
-         <seealso marker="kernel:seq_trace"><c>seq_trace</c></seealso> or
-         <seealso marker="#system_profile/2"><c>erlang:system_profile/2</c></seealso>)
+          <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>,
+          <seealso marker="kernel:seq_trace"><c>kernel:seq_trace</c></seealso>,
+          or <seealso marker="#system_profile/2">
+          <c>erlang:system_profile/2</c></seealso>)
           is dislocated on the time-line
           compared to other events in the system. If you know that
           <c><anno>Tracee</anno></c> has passed some specific point
           in its execution,
           and you want to know when at least all trace messages
           corresponding to events up to this point have reached the
-          tracer, use <c>erlang:trace_delivered(<anno>Tracee</anno>)</c>. A
-          <c>{trace_delivered, <anno>Tracee</anno>, <anno>Ref</anno>}</c> message is sent to
-          the caller of <c>erlang:trace_delivered(<anno>Tracee</anno>)</c> when it
-          is guaranteed that all trace messages are delivered to
+          tracer, use <c>erlang:trace_delivered(<anno>Tracee</anno>)</c>.</p>
+        <p>When it is guaranteed that all trace messages are delivered to
           the tracer up to the point that <c><anno>Tracee</anno></c> reached
           at the time of the call to
-          <c>erlang:trace_delivered(<anno>Tracee</anno>)</c>.</p>
+          <c>erlang:trace_delivered(<anno>Tracee</anno>)</c>, then a
+          <c>{trace_delivered, <anno>Tracee</anno>, <anno>Ref</anno>}</c>
+          message is sent to the caller of
+          <c>erlang:trace_delivered(<anno>Tracee</anno>)</c> .</p>
         <p>Notice that message <c>trace_delivered</c> does <em>not</em>
           imply that trace messages have been delivered.
           Instead it implies that all trace messages that
@@ -9239,22 +9426,22 @@ timestamp() ->
           <em>no</em> trace messages have been delivered when the
           <c>trace_delivered</c> message arrives.</p>
         <p>Notice that <c><anno>Tracee</anno></c> must refer
-          to a process currently,
+          to a process currently
           or previously existing on the same node as the caller of
           <c>erlang:trace_delivered(<anno>Tracee</anno>)</c> resides on.
           The special <c><anno>Tracee</anno></c> atom <c>all</c>
           denotes all processes that currently are traced in the node.</p>
-        <p>When used together with an <seealso marker="erts:erl_tracer">
-          Tracer Module</seealso> any message sent in the trace callback
-          is guaranteed to have reached it's recipient before the
+        <p>When used together with a <seealso marker="erts:erl_tracer">
+          Tracer Module</seealso>, any message sent in the trace callback
+          is guaranteed to have reached its recipient before the
           <c>trace_delivered</c> message is sent.</p>
         <p>Example: Process <c>A</c> is <c><anno>Tracee</anno></c>,
-	  port <c>B</c> is tracer, and process <c>C</c> is the port
-	  owner of <c>B</c>. <c>C</c> wants to close <c>B</c> when
-	  <c>A</c> exits. To ensure that the trace is not truncated,
-	  <c>C</c> can call <c>erlang:trace_delivered(A)</c>, when
-	  <c>A</c> exits, and wait for message <c>{trace_delivered, A,
-	  <anno>Ref</anno>}</c> before closing <c>B</c>.</p>
+          port <c>B</c> is tracer, and process <c>C</c> is the port
+          owner of <c>B</c>. <c>C</c> wants to close <c>B</c> when
+          <c>A</c> exits. To ensure that the trace is not truncated,
+          <c>C</c> can call <c>erlang:trace_delivered(A)</c> when
+          <c>A</c> exits, and wait for message <c>{trace_delivered, A,
+          <anno>Ref</anno>}</c> before closing <c>B</c>.</p>
         <p>Failure: <c>badarg</c> if <c><anno>Tracee</anno></c>
           does not refer to a
           process (dead or alive) on the same node as the caller of
@@ -9264,22 +9451,23 @@ timestamp() ->
 
     <func>
       <name name="trace_info" arity="2"/>
-     <fsummary>Trace information about a process or function.</fsummary>
+      <fsummary>Trace information about a process or function.</fsummary>
       <type name="trace_info_return"/>
       <type name="trace_info_item_result"/>
       <type name="trace_info_flag"/>
       <type name="trace_match_spec"/>
       <desc>
-        <p>Returns trace information about a port, process, function or event.</p>
+        <p>Returns trace information about a port, process, function, or
+          event.</p>
         <p><em>To get information about a port or process</em>,
-         <c><anno>PidPortFuncEvent</anno></c> is to
-          be a process identifier (pid), port identifier or one of
-          the atoms <c>new</c>, <c>new_processes</c>, <c>new_ports</c>.
-          The atom <c>new</c> or <c>new_processes</c> means that the default trace
-          state for processes to be created is returned. The atom <c>new_ports</c>
-          means that the default trace state for ports to be created is returned.
-        </p>
-        <p>The following <c>Item</c>s are valid for ports and processes:</p>
+          <c><anno>PidPortFuncEvent</anno></c> is to
+          be a process identifier (pid), port identifier, or one of
+          the atoms <c>new</c>, <c>new_processes</c>, or <c>new_ports</c>. The
+          atom <c>new</c> or <c>new_processes</c> means that the default trace
+          state for processes to be created is returned. The atom
+          <c>new_ports</c> means that the default trace state for ports to be
+          created is returned.</p>
+        <p>Valid <c>Item</c>s for ports and processes:</p>
         <taglist>
           <tag><c>flags</c></tag>
           <item>
@@ -9288,30 +9476,32 @@ timestamp() ->
               traces are enabled, and one or more of the followings
               atoms if traces are enabled: <c>send</c>,
               <c>'receive'</c>, <c>set_on_spawn</c>, <c>call</c>,
-              <c>return_to</c>, <c>procs</c>, <c>ports</c>, <c>set_on_first_spawn</c>,
+              <c>return_to</c>, <c>procs</c>, <c>ports</c>,
+              <c>set_on_first_spawn</c>,
               <c>set_on_link</c>, <c>running</c>, <c>running_procs</c>,
-              <c>running_ports</c>, <c>silent</c>, <c>exiting</c>
+              <c>running_ports</c>, <c>silent</c>, <c>exiting</c>,
               <c>monotonic_timestamp</c>, <c>strict_monotonic_timestamp</c>,
               <c>garbage_collection</c>, <c>timestamp</c>, and
               <c>arity</c>. The order is arbitrary.</p>
           </item>
           <tag><c>tracer</c></tag>
           <item>
-            <p>Returns the identifier for process, port or a tuple containing
+            <p>Returns the identifier for process, port, or a tuple containing
               the tracer module and tracer state tracing this
-              process. If this process is not being traced, the return
+              process. If this process is not traced, the return
               value is <c>[]</c>.</p>
           </item>
         </taglist>
-        <p><em>To get information about a function</em>, <c><anno>PidPortFuncEvent</anno></c> is to
+        <p><em>To get information about a function</em>,
+          <c><anno>PidPortFuncEvent</anno></c> is to
           be the three-element tuple <c>{Module, Function, Arity}</c> or
-          the atom <c>on_load</c>. No wild cards are allowed. Returns
+          the atom <c>on_load</c>. No wildcards are allowed. Returns
           <c>undefined</c> if the function does not exist, or
-          <c>false</c> if the function is not traced. If <c><anno>PidPortFuncEvent</anno></c>
-	  is <c>on_load</c>, the information returned refers to
-	  the default value for code that will be loaded.</p>
-
-         <p>The following <c>Item</c>s are valid for functions:</p>
+          <c>false</c> if the function is not traced.
+          If <c><anno>PidPortFuncEvent</anno></c>
+          is <c>on_load</c>, the information returned refers to
+          the default value for code that will be loaded.</p>
+        <p>Valid <c>Item</c>s for functions:</p>
         <taglist>
           <tag><c>traced</c></tag>
           <item>
@@ -9330,11 +9520,12 @@ timestamp() ->
           </item>
           <tag><c>meta</c></tag>
           <item>
-            <p>Returns the meta-trace tracer process, port or trace module
+            <p>Returns the meta-trace tracer process, port, or trace module
               for this function, if it has one. If the function is not
               meta-traced, the returned value is <c>false</c>. If
               the function is meta-traced but has once detected that
-              the tracer process is invalid, the returned value is [].</p>
+              the tracer process is invalid, the returned value is
+              <c>[]</c>.</p>
           </item>
           <tag><c>meta_match_spec</c></tag>
           <item>
@@ -9347,21 +9538,22 @@ timestamp() ->
           <item>
             <p>Returns the call count value for this function or
               <c>true</c> for the pseudo function <c>on_load</c> if call
-              count tracing is active. Otherwise <c>false</c> is returned.
-              See also
-              <seealso marker="#trace_pattern/3">erlang:trace_pattern/3</seealso>.</p>
+              count tracing is active. Otherwise <c>false</c> is returned.</p>
+            <p>See also <seealso marker="#trace_pattern/3">
+              <c>erlang:trace_pattern/3</c></seealso>.</p>
           </item>
           <tag><c>call_time</c></tag>
           <item>
-	      <p>Returns the call time values for this function or
+            <p>Returns the call time values for this function or
               <c>true</c> for the pseudo function <c>on_load</c> if call
-	      time tracing is active. Otherwise <c>false</c> is returned.
-	      The call time values returned, <c>[{Pid, Count, S, Us}]</c>,
-	      is a list of each process that executed the function
-              and its specific counters. See also
-              <seealso marker="#trace_pattern/3">erlang:trace_pattern/3</seealso>.</p>
+              time tracing is active. Otherwise <c>false</c> is returned.
+              The call time values returned, <c>[{Pid, Count, S, Us}]</c>,
+              is a list of each process that executed the function
+              and its specific counters.</p>
+            <p>See also
+              <seealso marker="#trace_pattern/3">
+              <c>erlang:trace_pattern/3</c></seealso>.</p>
           </item>
-
           <tag><c>all</c></tag>
           <item>
             <p>Returns a list containing the
@@ -9370,80 +9562,84 @@ timestamp() ->
               is active for this function.</p>
           </item>
         </taglist>
-        <p><em>To get information about an event</em>, <c><anno>PidPortFuncEvent</anno></c> is to
+        <p><em>To get information about an event</em>,
+          <c><anno>PidPortFuncEvent</anno></c> is to
           be one of the atoms <c>send</c> or <c>'receive'</c>.</p>
-         <p>The only valid <c>Item</c> for events is:</p>
+        <p>One valid <c>Item</c> for events exists:</p>
         <taglist>
           <tag><c>match_spec</c></tag>
           <item>
             <p>Returns the match specification for this event, if it
               has one, or <c>true</c> if no match specification has been
-	      set.</p>
+              set.</p>
           </item>
         </taglist>
         <p>The return value is <c>{<anno>Item</anno>, Value}</c>, where
           <c>Value</c> is the requested information as described earlier.
-          If a pid for a dead process was given, or the name of a
+          If a pid for a dead process was specified, or the name of a
           non-existing function, <c>Value</c> is <c>undefined</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="trace_pattern" arity="2" clause_i="1"/>
-      <fsummary>Sets trace patterns for call, send or 'receive' tracing.</fsummary>
+      <fsummary>Set trace patterns for call, send, or 'receive' tracing.
+      </fsummary>
       <type name="trace_pattern_mfa"/>
       <type name="trace_match_spec"/>
       <desc>
         <p>The same as
-          <seealso marker="#trace_pattern/3">erlang:trace_pattern(Event, MatchSpec, [])</seealso>,
+          <seealso marker="#trace_pattern/3">
+          <c>erlang:trace_pattern(Event, MatchSpec, [])</c></seealso>,
           retained for backward compatibility.</p>
       </desc>
     </func>
 
     <func>
       <name name="trace_pattern" arity="3" clause_i="1"/>
-      <fsummary>Sets trace pattern for message sending.</fsummary>
+      <fsummary>Set trace pattern for message sending.</fsummary>
       <type name="trace_match_spec"/>
       <desc>
         <p>Sets trace pattern for <em>message sending</em>.
-	  Must be combined with
-          <seealso marker="#trace/3">erlang:trace/3</seealso>
+          Must be combined with
+          <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>
           to set the <c>send</c> trace flag for one or more processes.
-	  By default all messages, sent from <c>send</c> traced processes,
-	  are traced. Use <c>erlang:trace_pattern/3</c> to limit
-	  traced send events based on the message content, the sender
-	  and/or the receiver.</p>
+          By default all messages sent from <c>send</c> traced processes
+          are traced. To limit
+          traced send events based on the message content, the sender
+          and/or the receiver, use <c>erlang:trace_pattern/3</c>.</p>
         <p>Argument <c><anno>MatchSpec</anno></c> can take the
           following forms:</p>
         <taglist>
           <tag><c><anno>MatchSpecList</anno></c></tag>
           <item>
             <p>A list of match specifications. The matching is done
-	      on the list <c>[Receiver, Msg]</c>. <c>Receiver</c>
-	      is the process or port identity of the receiver and
-	      <c>Msg</c> is the message term. The pid of the sending
-	      process can be accessed with the guard function
-	      <c>self/0</c>. An empty list is the same as <c>true</c>.
-	      See the users guide section
-	      <seealso marker="erts:match_spec">Match Specifications in Erlang</seealso>
-	      for more information.</p>
+              on the list <c>[Receiver, Msg]</c>. <c>Receiver</c>
+              is the process or port identity of the receiver and
+              <c>Msg</c> is the message term. The pid of the sending
+              process can be accessed with the guard function
+              <c>self/0</c>. An empty list is the same as <c>true</c>.
+              For more information, see section
+              <seealso marker="erts:match_spec">
+              Match Specifications in Erlang</seealso> in the User's Guide.</p>
           </item>
           <tag><c>true</c></tag>
           <item>
             <p>Enables tracing for all sent messages (from <c>send</c>
-	    traced processes). Any match specification is
-	    removed. <em>This is the default</em>.</p>
+              traced processes). Any match specification is
+              removed. <em>This is the default</em>.</p>
           </item>
           <tag><c>false</c></tag>
           <item>
             <p>Disables tracing for all sent messages.
-	       Any match specification is removed.</p>
+              Any match specification is removed.</p>
           </item>
         </taglist>
-	<p>Argument <c><anno>FlagList</anno></c> must be <c>[]</c>
-	for send tracing.</p>
-	<p>The return value is always <c>1</c>.</p>
-        <p>Example; only trace messages to a specific process <c>Pid</c>:</p>
+        <p>Argument <c><anno>FlagList</anno></c> must be <c>[]</c>
+          for send tracing.</p>
+        <p>The return value is always <c>1</c>.</p>
+        <p>Examples:</p>
+        <p>Only trace messages to a specific process <c>Pid</c>:</p>
         <pre>
 > <input>erlang:trace_pattern(send, [{[Pid, '_'],[],[]}], []).</input>
 1</pre>
@@ -9459,58 +9655,60 @@ timestamp() ->
         <pre>
 > <input>erlang:trace_pattern(send, [{['$1', '_'],[{'=/=',{node,'$1'},{node}}],[]}], []).</input>
 1</pre>
-        <note><p>A match specification for <c>send</c> trace can use
-	all guard and body functions except <c>caller</c>.</p></note>
+        <note>
+          <p>A match specification for <c>send</c> trace can use
+            all guard and body functions except <c>caller</c>.</p>
+        </note>
       </desc>
     </func>
 
     <func>
       <name name="trace_pattern" arity="3" clause_i="2"/>
-      <fsummary>Sets trace pattern for tracing of message receiving.</fsummary>
+      <fsummary>Set trace pattern for tracing of message receiving.</fsummary>
       <type name="trace_match_spec"/>
       <desc>
-        <p></p>
         <p>Sets trace pattern for <em>message receiving</em>.
-	  Must be combined with
-          <seealso marker="#trace/3">erlang:trace/3</seealso>
+          Must be combined with
+          <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>
           to set the <c>'receive'</c> trace flag for one or more processes.
-	  By default all messages, received by <c>'receive'</c> traced processes,
-	  are traced. Use <c>erlang:trace_pattern/3</c> to limit
-	  traced receive events based on the message content, the sender
-	  and/or the receiver.</p>
+          By default all messages received by <c>'receive'</c> traced
+          processes are traced. To limit
+          traced receive events based on the message content, the sender
+          and/or the receiver, use <c>erlang:trace_pattern/3</c>.</p>
         <p>Argument <c><anno>MatchSpec</anno></c> can take the
           following forms:</p>
         <taglist>
           <tag><c><anno>MatchSpecList</anno></c></tag>
           <item>
             <p>A list of match specifications. The matching is done
-	      on the list <c>[Node, Sender, Msg]</c>. <c>Node</c>
-	      is the node name of the sender. <c>Sender</c> is the
-	      process or port identity of the sender, or the atom
-	      <c>undefined</c> if the sender is not known (which may
-	      be the case for remote senders). <c>Msg</c> is the
-	      message term. The pid of the receiving process can be
-	      accessed with the guard function <c>self/0</c>. An empty
-	      list is the same as <c>true</c>. See the users guide section
-	      <seealso marker="erts:match_spec">Match Specifications in Erlang</seealso>
-	      for more information.</p>
+              on the list <c>[Node, Sender, Msg]</c>. <c>Node</c>
+              is the node name of the sender. <c>Sender</c> is the
+              process or port identity of the sender, or the atom
+              <c>undefined</c> if the sender is not known (which can
+              be the case for remote senders). <c>Msg</c> is the
+              message term. The pid of the receiving process can be
+              accessed with the guard function <c>self/0</c>. An empty
+              list is the same as <c>true</c>. For more information, see
+              section <seealso marker="erts:match_spec">
+              Match Specifications in Erlang</seealso> in the User's Guide.</p>
           </item>
           <tag><c>true</c></tag>
           <item>
             <p>Enables tracing for all received messages (to <c>'receive'</c>
-	    traced processes). Any match specification is
-	    removed. <em>This is the default</em>.</p>
+              traced processes). Any match specification is
+              removed. <em>This is the default</em>.</p>
           </item>
           <tag><c>false</c></tag>
           <item>
             <p>Disables tracing for all received messages.
-	       Any match specification is removed.</p>
+              Any match specification is removed.</p>
           </item>
         </taglist>
-	<p>Argument <c><anno>FlagList</anno></c> must be <c>[]</c>
-	for receive tracing.</p>
-	<p>The return value is always <c>1</c>.</p>
-        <p>Example; only trace messages from a specific process <c>Pid</c>:</p>
+        <p>Argument <c><anno>FlagList</anno></c> must be <c>[]</c>
+          for receive tracing.</p>
+        <p>The return value is always <c>1</c>.</p>
+        <p>Examples:</p>
+        <p>Only trace messages from a specific process <c>Pid</c>:</p>
         <pre>
 > <input>erlang:trace_pattern('receive', [{['_',Pid, '_'],[],[]}], []).</input>
 1</pre>
@@ -9522,33 +9720,36 @@ timestamp() ->
         <pre>
 > <input>erlang:trace_pattern('receive', [{['$1', '_', '_'],[{'=/=','$1',{node}}],[]}], []).</input>
 1</pre>
-        <note><p>A match specification for <c>'receive'</c> trace can
-	use all guard and body functions except <c>caller,
-	is_seq_trace, get_seq_token, set_seq_token, enable_trace,
-	disable_trace, trace, silent</c> and <c>process_dump</c>.</p></note>
+        <note>
+          <p>A match specification for <c>'receive'</c> trace can
+            use all guard and body functions except <c>caller</c>,
+            <c>is_seq_trace</c>, <c>get_seq_token</c>, <c>set_seq_token</c>,
+            <c>enable_trace</c>, <c>disable_trace</c>, <c>trace</c>,
+            <c>silent</c>, and <c>process_dump</c>.</p>
+        </note>
       </desc>
     </func>
 
     <func>
       <name name="trace_pattern" arity="3" clause_i="3"/>
-      <fsummary>Sets trace patterns for tracing of function calls.</fsummary>
+      <fsummary>Set trace patterns for tracing of function calls.</fsummary>
       <type name="trace_pattern_mfa"/>
       <type name="trace_match_spec"/>
       <type name="trace_pattern_flag"/>
       <desc>
         <p>Enables or disables <em>call tracing</em> for one or more functions.
-	  Must be combined with
-          <seealso marker="#trace/3">erlang:trace/3</seealso>
+          Must be combined with
+          <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>
           to set the <c>call</c> trace flag
-	  for one or more processes.</p>
+          for one or more processes.</p>
         <p>Conceptually, call tracing works as follows. Inside
-          the Erlang Virtual Machine, a set of processes and
+          the Erlang virtual machine, a set of processes and
           a set of functions are to be traced. If a traced process
           calls a traced function, the trace action is taken.
           Otherwise, nothing happens.</p>
         <p>To add or remove one or more processes to the set of traced
           processes, use
-          <seealso marker="#trace/3">erlang:trace/3</seealso>.</p>
+          <seealso marker="#trace/3"><c>erlang:trace/3</c></seealso>.</p>
         <p>To add or remove functions to the set of traced
           functions, use <c>erlang:trace_pattern/3</c>.</p>
         <p>The BIF <c>erlang:trace_pattern/3</c> can also add match
@@ -9560,10 +9761,10 @@ timestamp() ->
           fails, the action is not executed.</p>
         <p>Argument <c><anno>MFA</anno></c> is to be a tuple, such as
           <c>{Module, Function, Arity}</c>, or the atom <c>on_load</c>
-          (described in the following). It can be the module, function,
+          (described below). It can be the module, function,
           and arity for a function (or a BIF in any module).
-          The atom <c>'_'</c> can be used as a wild card in any of the
-	  following ways:</p>
+          The atom <c>'_'</c> can be used as a wildcard in any of the
+          following ways:</p>
         <taglist>
           <tag><c>{Module,Function,'_'}</c></tag>
           <item>
@@ -9580,7 +9781,7 @@ timestamp() ->
           </item>
         </taglist>
         <p>Other combinations, such as <c>{Module,'_',Arity}</c>, are
-          not allowed. Local functions match wild cards only if
+          not allowed. Local functions match wildcards only if
           option <c>local</c> is in <c><anno>FlagList</anno></c>.</p>
         <p>If argument <c><anno>MFA</anno></c> is the atom <c>on_load</c>,
           the match specification and flag list are used on all
@@ -9596,13 +9797,14 @@ timestamp() ->
           <tag><c>true</c></tag>
           <item>
             <p>Enables tracing for the matching functions.
-	       Any match specification is removed.</p>
+              Any match specification is removed.</p>
           </item>
           <tag><c><anno>MatchSpecList</anno></c></tag>
           <item>
             <p>A list of match specifications. An empty list is
               equivalent to <c>true</c>. For a description of match
-              specifications, see the User's Guide.</p>
+              specifications, see section <seealso marker="erts:match_spec">
+              Match Specifications in Erlang</seealso> in the User's Guide.</p>
           </item>
           <tag><c>restart</c></tag>
           <item>
@@ -9613,7 +9815,7 @@ timestamp() ->
           </item>
           <tag><c>pause</c></tag>
           <item>
-	      <p>For the <c><anno>FlagList</anno></c> options
+            <p>For the <c><anno>FlagList</anno></c> options
               <c>call_count</c> and <c>call_time</c>: pauses
               the existing counters. The behavior is undefined for
               other <c><anno>FlagList</anno></c> options.</p>
@@ -9638,7 +9840,8 @@ timestamp() ->
               the process, a <c>return_to</c> message is also sent
               when this function returns to its caller.</p>
           </item>
-          <tag><c>meta | {meta, <anno>Pid</anno>} | {meta, <anno>TracerModule</anno>, <anno>TracerState</anno>}</c>
+          <tag><c>meta | {meta, <anno>Pid</anno>} |
+            {meta, <anno>TracerModule</anno>, <anno>TracerState</anno>}</c>
           </tag>
           <item>
             <p>Turns on or off meta-tracing for all types of function
@@ -9646,7 +9849,7 @@ timestamp() ->
               the specified functions are called. If no tracer is specified,
               <c>self()</c> is used as a default tracer process.</p>
             <p>Meta-tracing traces all processes and does not care
-              about the process trace flags set by <c>trace/3</c>,
+              about the process trace flags set by <c>erlang:trace/3</c>,
               the trace flags are instead fixed to
               <c>[call, timestamp]</c>.</p>
             <p>The match specification function <c>{return_trace}</c>
@@ -9667,7 +9870,8 @@ timestamp() ->
               Paused and running counters can be restarted from zero with
               <c><anno>MatchSpec</anno> == restart</c>.</p>
             <p>To read the counter value, use
-              <seealso marker="#trace_info/2">erlang:trace_info/2</seealso>.</p>
+              <seealso marker="#trace_info/2">
+              <c>erlang:trace_info/2</c></seealso>.</p>
           </item>
           <tag><c>call_time</c></tag>
           <item>
@@ -9675,17 +9879,18 @@ timestamp() ->
               (<c><anno>MatchSpec</anno> == false</c>) call time
               tracing for all
               types of function calls. For every function, a counter is
-	      incremented when the function is called.
+              incremented when the function is called.
               Time spent in the function is accumulated in
               two other counters, seconds and microseconds.
-	      The counters are stored for each call traced process.</p>
+              The counters are stored for each call traced process.</p>
             <p>If call time tracing is started while already running,
-              the count and time is restarted from zero. To pause
+              the count and time restart from zero. To pause
               running counters, use <c><anno>MatchSpec</anno> == pause</c>.
               Paused and running counters can be restarted from zero with
               <c><anno>MatchSpec</anno> == restart</c>.</p>
             <p>To read the counter value, use
-              <seealso marker="#trace_info/2">erlang:trace_info/2</seealso>.</p>
+              <seealso marker="#trace_info/2">
+              <c>erlang:trace_info/2</c></seealso>.</p>
           </item>
         </taglist>
         <p>The options <c>global</c> and <c>local</c> are mutually
@@ -9700,12 +9905,12 @@ timestamp() ->
         <p>When disabling trace, the option must match the type of trace
           set on the function. That is, local tracing must be
           disabled with option <c>local</c> and global tracing with
-          option <c>global</c> (or no option), and so forth.</p>
+          option <c>global</c> (or no option), and so on.</p>
         <p>Part of a match specification list cannot be changed directly.
           If a function has a match specification, it can be replaced
           with a new one. To change an existing match specification,
           use the BIF
-          <seealso marker="#trace_info/2">erlang:trace_info/2</seealso>
+          <seealso marker="#trace_info/2"><c>erlang:trace_info/2</c></seealso>
           to retrieve the existing match specification.</p>
         <p>Returns the number of functions matching
           argument <c><anno>MFA</anno></c>. This is zero if none matched.</p>
@@ -9714,7 +9919,7 @@ timestamp() ->
 
     <func>
       <name name="trunc" arity="1"/>
-      <fsummary>Returns an integer by truncating a number</fsummary>
+      <fsummary>Return an integer by truncating a number.</fsummary>
       <desc>
         <p>Returns an integer by truncating <c><anno>Number</anno></c>,
           for example:</p>
@@ -9727,7 +9932,7 @@ timestamp() ->
 
     <func>
       <name name="tuple_size" arity="1"/>
-      <fsummary>Returns the size of a tuple.</fsummary>
+      <fsummary>Return the size of a tuple.</fsummary>
       <desc>
         <p>Returns an integer that is the number of elements in
           <c><anno>Tuple</anno></c>, for example:</p>
@@ -9740,11 +9945,11 @@ timestamp() ->
 
     <func>
       <name name="tuple_to_list" arity="1"/>
-      <fsummary>Converts a tuple to a list.</fsummary>
+      <fsummary>Convert a tuple to a list.</fsummary>
       <desc>
         <p>Returns a list corresponding to <c><anno>Tuple</anno></c>.
-          <c><anno>Tuple</anno></c> can contain any Erlang terms.</p>
-        <p>Example:</p>
+          <c><anno>Tuple</anno></c> can contain any Erlang terms.
+          Example:</p>
         <pre>
 > <input>tuple_to_list({share, {'Ericsson_B', 163}}).</input>
 [share,{'Ericsson_B',163}]</pre>
@@ -9753,112 +9958,110 @@ timestamp() ->
 
     <func>
       <name name="unique_integer" arity="0"/>
-      <fsummary>Get a unique integer value</fsummary>
+      <fsummary>Get a unique integer value.</fsummary>
       <desc>
-	<p>Generates and returns an
-	<seealso marker="doc/efficiency_guide:advanced#unique_integers">integer
-	unique on current runtime system instance</seealso>. The same as calling
-	<seealso marker="#unique_integer/1"><c>erlang:unique_integer([])</c></seealso>.</p>
+        <p>Generates and returns an
+          <seealso marker="doc/efficiency_guide:advanced#unique_integers">
+          integer unique on current runtime system instance</seealso>.
+          The same as calling
+          <seealso marker="#unique_integer/1">
+          <c>erlang:unique_integer([])</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="unique_integer" arity="1"/>
-      <fsummary>Get a unique integer value</fsummary>
-      <desc>
-	<p>Generates and returns an
-	<seealso marker="doc/efficiency_guide:advanced#unique_integers">integer
-	unique on current runtime system
-	instance</seealso>. The integer is unique in the
-	sense that this BIF, using the same set of
-	modifiers, will not return the same integer more
-	than once on the current runtime system instance.
-	Each integer value can of course be constructed
-	by other means.</p>
-
-	<p>By default, when <c>[]</c> is passed as
-	<c><anno>ModifierList</anno></c>, both negative and
-	positive integers can be returned. This in order
-	to utilize the range of integers that do
-	not need heap memory allocation as much as possible.
-	By default the returned integers are also only
-	guaranteed to be unique, that is, any returned integer
-	can be smaller or larger than previously
-	returned integers.</p>
-
-	<p>Valid <c><anno>Modifier</anno></c>s:</p>
-	<taglist>
-
-	  <tag>positive</tag>
-	  <item>
-            <p>Return only positive integers.</p>
-	  <p>Note that by passing the <c>positive</c> modifier
-	  you will get heap allocated integers (bignums)
-	  quicker.</p>
-	  </item>
-
-	  <tag>monotonic</tag>
-	  <item>
-            <p>Return
-	  <seealso marker="time_correction#Strictly_Monotonically_Increasing">strictly
-	  monotonically increasing</seealso> integers
-	  corresponding to creation time. That is, the integer
-	  returned will always be larger than previously
-	  returned integers on the current runtime system
-	  instance.</p>
-	  <p>These values can be used to determine order between events
-	  on the runtime system instance. That is, if both
-	  <c>X = erlang:unique_integer([monotonic])</c> and
-	  <c>Y = erlang:unique_integer([monotonic])</c> are
-	  executed by different processes (or the same
-	  process) on the same runtime system instance and
-	  <c>X &lt; Y</c> we know that <c>X</c> was created
-	  before <c>Y</c>.</p>
-	  <warning><p>Strictly monotonically increasing values
-	  are inherently quite expensive to generate and scales
-	  poorly. This is because the values need to be
-	  synchronized between cpu cores. That is, do not pass the <c>monotonic</c>
-	  modifier unless you really need strictly monotonically
-	  increasing values.</p></warning>
-	  </item>
-
-	</taglist>
-
-	<p>All valid <c><anno>Modifier</anno></c>s
-	can be combined. Repeated (valid)
-	<c><anno>Modifier</anno></c>s in the <c>ModifierList</c>
-	are ignored.</p>
-
-	<note><p>Note that the set of integers returned by
-	<c>unique_integer/1</c> using different sets of
-	<c><anno>Modifier</anno></c>s <em>will overlap</em>.
-	For example, by calling	<c>unique_integer([monotonic])</c>,
-	and <c>unique_integer([positive, monotonic])</c>
-	repeatedly, you will eventually see some integers being
-	returned by both calls.</p></note>
-
+      <fsummary>Get a unique integer value.</fsummary>
+      <desc>
+        <p>Generates and returns an
+          <seealso marker="doc/efficiency_guide:advanced#unique_integers">
+          integer unique on current runtime system
+          instance</seealso>. The integer is unique in the
+          sense that this BIF, using the same set of
+          modifiers, does not return the same integer more
+          than once on the current runtime system instance.
+          Each integer value can of course be constructed
+          by other means.</p>
+        <p>By default, when <c>[]</c> is passed as
+          <c><anno>ModifierList</anno></c>, both negative and
+          positive integers can be returned. This
+          to use the range of integers that do
+          not need heap memory allocation as much as possible.
+          By default the returned integers are also only
+          guaranteed to be unique, that is, any returned integer
+          can be smaller or larger than previously
+          returned integers.</p>
+        <p><c><anno>Modifier</anno></c>s:</p>
+        <taglist>
+          <tag>positive</tag>
+          <item>
+            <p>Returns only positive integers.</p>
+            <p>Notice that by passing the <c>positive</c> modifier
+              you will get heap allocated integers (bignums) quicker.</p>
+          </item>
+          <tag>monotonic</tag>
+          <item>
+            <p>Returns <seealso
+              marker="time_correction#Strictly_Monotonically_Increasing">
+              strictly monotonically increasing</seealso> integers
+              corresponding to creation time. That is, the integer
+              returned is always larger than previously
+              returned integers on the current runtime system
+              instance.</p>
+            <p>These values can be used to determine order between events
+              on the runtime system instance. That is, if both
+              <c>X = erlang:unique_integer([monotonic])</c> and
+              <c>Y = erlang:unique_integer([monotonic])</c> are
+              executed by different processes (or the same
+              process) on the same runtime system instance and
+              <c>X &lt; Y</c>, we know that <c>X</c> was created
+              before <c>Y</c>.</p>
+            <warning>
+              <p>Strictly monotonically increasing values
+                are inherently quite expensive to generate and scales
+                poorly. This is because the values need to be synchronized
+                between CPU cores. That is, do not pass the <c>monotonic</c>
+                modifier unless you really need strictly monotonically
+                increasing values.</p>
+            </warning>
+        </item>
+        </taglist>
+        <p>All valid <c><anno>Modifier</anno></c>s
+          can be combined. Repeated (valid)
+          <c><anno>Modifier</anno></c>s in the <c>ModifierList</c>
+          are ignored.</p>
+        <note>
+          <p>The set of integers returned by
+            <c>erlang:unique_integer/1</c> using different sets of
+            <c><anno>Modifier</anno></c>s <em>will overlap</em>.
+            For example, by calling <c>unique_integer([monotonic])</c>,
+            and <c>unique_integer([positive, monotonic])</c>
+            repeatedly, you will eventually see some integers that are
+            returned by both calls.</p>
+        </note>
         <p>Failures:</p>
-	<taglist>
-	  <tag><c>badarg</c></tag>
-	  <item>if <c><anno>ModifierList</anno></c> is not a
-	  proper list.</item>
-	  <tag><c>badarg</c></tag>
-	  <item>if <c><anno>Modifier</anno></c> is not a
-	  valid modifier.</item>
-	</taglist>
+        <taglist>
+          <tag><c>badarg</c></tag>
+          <item>if <c><anno>ModifierList</anno></c> is not a
+            proper list.</item>
+          <tag><c>badarg</c></tag>
+          <item>if <c><anno>Modifier</anno></c> is not a
+            valid modifier.</item>
+        </taglist>
       </desc>
     </func>
 
     <func>
       <name name="universaltime" arity="0"/>
-      <fsummary>Current date and time according to Universal Time Coordinated (UTC).</fsummary>
+      <fsummary>Current date and time according to Universal Time Coordinated
+        (UTC).</fsummary>
       <desc>
         <p>Returns the current date and time according to Universal
           Time Coordinated (UTC) in the form
           <c>{{Year, Month, Day}, {Hour, Minute, Second}}</c> if
           supported by the underlying OS.
           Otherwise <c>erlang:universaltime()</c> is equivalent to
-          <c>erlang:localtime()</c>.</p>
-        <p>Example:</p>
+          <c>erlang:localtime()</c>. Example:</p>
         <pre>
 > <input>erlang:universaltime().</input>
 {{1996,11,6},{14,18,43}}</pre>
@@ -9867,15 +10070,15 @@ timestamp() ->
 
     <func>
       <name name="universaltime_to_localtime" arity="1"/>
-      <fsummary>Converts from Universal Time Coordinated (UTC) to local date and time.</fsummary>
+      <fsummary>Convert from Universal Time Coordinated (UTC) to local date
+        and time.</fsummary>
       <desc>
         <p>Converts Universal Time Coordinated (UTC) date and time to
           local date and time in the form
           <c>{{Year, Month, Day}, {Hour, Minute, Second}}</c> if
           supported by the underlying OS.
           Otherwise no conversion is done, and
-          <c><anno>Universaltime</anno></c> is returned.</p>
-        <p>Example:</p>
+          <c><anno>Universaltime</anno></c> is returned. Example:</p>
         <pre>
 > <input>erlang:universaltime_to_localtime({{1996,11,6},{14,18,43}}).</input>
 {{1996,11,7},{15,18,43}}</pre>
@@ -9886,7 +10089,7 @@ timestamp() ->
 
     <func>
       <name name="unlink" arity="1"/>
-      <fsummary>Removes a link to another process or port.</fsummary>
+      <fsummary>Remove a link to another process or port.</fsummary>
       <desc>
         <p>Removes the link, if there is one, between the calling
           process and the process or port referred to by
@@ -9901,8 +10104,8 @@ timestamp() ->
           in the future (unless
           the link is setup again). If the caller is trapping exits, an
           <c>{'EXIT', <anno>Id</anno>, _}</c> message from the link
-	  can have been placed in the caller's message queue before
-	  the call.</p>
+          can have been placed in the caller's message queue before
+          the call.</p>
         <p>Notice that the <c>{'EXIT', <anno>Id</anno>, _}</c>
           message can be the
           result of the link, but can also be the result of <c>Id</c>
@@ -9910,16 +10113,16 @@ timestamp() ->
           appropriate to clean up the message queue when trapping exits
           after the call to <c>unlink(<anno>Id</anno>)</c>, as follows:</p>
         <code type="none">
-    unlink(Id),
-    receive
-        {'EXIT', Id, _} ->
-            true
-    after 0 ->
-            true
-    end</code>
+unlink(Id),
+receive
+    {'EXIT', Id, _} ->
+        true
+after 0 ->
+        true
+end</code>
         <note>
-          <p>Prior to OTP release R11B (ERTS version 5.5) <c>unlink/1</c>
-            behaved completely asynchronously, i.e., the link was active
+          <p>Before Erlang/OTP R11B (ERTS 5.5) <c>unlink/1</c>
+            behaved completely asynchronously, that is, the link was active
             until the "unlink signal" reached the linked entity. This
             had an undesirable effect, as you could never know when
             you were guaranteed <em>not</em> to be effected by the link.</p>
@@ -9932,7 +10135,7 @@ timestamp() ->
 
     <func>
       <name name="unregister" arity="1"/>
-      <fsummary>Removes the registered name for a process (or port).</fsummary>
+      <fsummary>Remove the registered name for a process (or port).</fsummary>
       <desc>
         <p>Removes the registered name <c><anno>RegName</anno></c>
           associated with a
@@ -9948,12 +10151,12 @@ true</pre>
 
     <func>
       <name name="whereis" arity="1"/>
-      <fsummary>Gets the pid (or port) with a given registered name.</fsummary>
+      <fsummary>Get the pid (or port) with a specified registered name.
+      </fsummary>
       <desc>
         <p>Returns the process identifier or port identifier with
           the registered name <c>RegName</c>. Returns <c>undefined</c>
-          if the name is not registered.</p>
-        <p>Example:</p>
+          if the name is not registered. Example:</p>
         <pre>
 > <input>whereis(db).</input>
 &lt;0.43.0></pre>
@@ -9962,17 +10165,19 @@ true</pre>
 
     <func>
       <name name="yield" arity="0"/>
-      <fsummary>Lets other processes get a chance to execute.</fsummary>
+      <fsummary>Let other processes get a chance to execute.</fsummary>
       <desc>
         <p>Voluntarily lets other processes (if any) get a chance to
-          execute. Using <c>erlang:yield()</c> is similar to
+          execute. Using this function is similar to
           <c>receive after 1 -> ok end</c>, except that <c>yield()</c>
           is faster.</p>
-	<warning><p>There is seldom or never any need to use this BIF,
-        especially in the SMP emulator, as other processes have a
-        chance to run in another scheduler thread anyway.
-        Using this BIF without a thorough grasp of how the scheduler
-        works can cause performance degradation.</p></warning>
+        <warning>
+          <p>There is seldom or never any need to use this BIF,
+            especially in the SMP emulator, as other processes have a
+            chance to run in another scheduler thread anyway.
+            Using this BIF without a thorough grasp of how the scheduler
+            works can cause performance degradation.</p>
+        </warning>
       </desc>
     </func>
   </funcs>
diff --git a/erts/doc/src/erlc.xml b/erts/doc/src/erlc.xml
index a64927fec2..ca3412b72c 100644
--- a/erts/doc/src/erlc.xml
+++ b/erts/doc/src/erlc.xml
@@ -28,7 +28,7 @@
     <docno>1</docno>
     <approved>Bjarne D&auml;cker</approved>
     <checked></checked>
-    <date>97-03-24</date>
+    <date>1997-03-24</date>
     <rev>A</rev>
     <file>erlc.xml</file>
   </header>
@@ -38,167 +38,162 @@
     <p>The <c><![CDATA[erlc]]></c> program provides a common way to run
       all compilers in the Erlang system.
       Depending on the extension of each input file, <c><![CDATA[erlc]]></c>
-      will invoke the appropriate compiler.
-      Regardless of which compiler is used, the same flags are used to provide parameters such as include paths and output directory.</p>
-    <p>The current working directory, <c>"."</c>, will not be included
-    in the code path when running the compiler (to avoid loading
-    Beam files from the current working directory that could potentially
-    be in conflict with the compiler or Erlang/OTP system used by the
-    compiler).</p>
+      invokes the appropriate compiler.
+      Regardless of which compiler is used, the same flags are used to provide
+      parameters, such as include paths and output directory.</p>
+    <p>The current working directory, <c>"."</c>, is not included
+      in the code path when running the compiler. This to avoid loading
+      Beam files from the current working directory that could potentially
+      be in conflict with the compiler or the Erlang/OTP system used by the
+      compiler.</p>
   </description>
+
   <funcs>
     <func>
       <name>erlc flags file1.ext file2.ext...</name>
-      <fsummary>Compile files</fsummary>
+      <fsummary>Compile files.</fsummary>
       <desc>
-        <p><c><![CDATA[Erlc]]></c> compiles one or more files.
-          The files must include the extension, for example <c><![CDATA[.erl]]></c>
-          for Erlang source code, or <c><![CDATA[.yrl]]></c> for Yecc source code.
-          <c><![CDATA[Erlc]]></c> uses the extension to invoke the correct compiler.</p>
+        <p>Compiles one or more files. The files must include the extension,
+          for example, <c><![CDATA[.erl]]></c> for Erlang source code, or
+          <c><![CDATA[.yrl]]></c> for Yecc source code.
+          <c><![CDATA[Erlc]]></c> uses the extension to invoke the correct
+          compiler.</p>
       </desc>
     </func>
   </funcs>
 
   <section>
     <title>Generally Useful Flags</title>
-    <p>The following flags are supported:
-      </p>
+    <p>The following flags are supported:</p>
     <taglist>
-      <tag>-I <em>directory</em></tag>
+      <tag><c>-I &lt;Directory&gt;</c></tag>
       <item>
         <p>Instructs the compiler to search for include files in
-          the specified directory. When encountering an
-          <c><![CDATA[-include]]></c> or <c><![CDATA[-include_lib]]></c> directive, the
-          compiler searches for header files in the following
+          the <c>Directory</c>. When encountering an
+          <c><![CDATA[-include]]></c> or <c><![CDATA[-include_lib]]></c>
+          directive, the compiler searches for header files in the following
           directories:</p>
-        <list type="ordered">
+        <list type="bulleted">
           <item>
             <p><c><![CDATA["."]]></c>, the current working directory of the
-              file server;</p>
+              file server</p>
           </item>
           <item>
-            <p>the base name of the compiled file;</p>
+            <p>The base name of the compiled file</p>
           </item>
           <item>
-            <p>the directories specified using the <c><![CDATA[-I]]></c> option.
-              The directory specified last is searched first.</p>
+            <p>The directories specified using option <c><![CDATA[-I]]></c>;
+              the directory specified last is searched first</p>
           </item>
         </list>
       </item>
-      <tag>-o <em>directory</em></tag>
+      <tag><c>-o &lt;Directory&gt;</c></tag>
       <item>
-        <p>The directory where the compiler should place the output files.
-          If not specified, output files will be placed in the current working
-          directory.</p>
+        <p>The directory where the compiler is to place the output files.
+          Defaults to the current working directory.</p>
       </item>
-      <tag>-D<em>name</em></tag>
+      <tag><c>-D&lt;Name&gt;</c></tag>
       <item>
         <p>Defines a macro.</p>
       </item>
-      <tag>-D<em>name</em>=<em>value</em></tag>
+      <tag><c>-D&lt;Name&gt;=&lt;Value&gt;</c></tag>
       <item>
-        <p>Defines a macro with the given value.
+        <p>Defines a macro with the specified value.
           The value can be any Erlang term.
           Depending on the platform, the value may need to be
           quoted if the shell itself interprets certain characters.
-          On Unix, terms which contain tuples and list
-          must be quoted. Terms which contain spaces
+          On Unix, terms containing tuples and lists
+          must be quoted. Terms containing spaces
           must be quoted on all platforms.</p>
       </item>
-      <tag>-W<em>error</em></tag>
+      <tag><c>-W&lt;Error&gt;</c></tag>
       <item>
         <p>Makes all warnings into errors.</p>
       </item>
-      <tag>-W<em>number</em></tag>
+      <tag><c>-W&lt;Number&gt;</c></tag>
       <item>
-        <p>Sets warning level to <em>number</em>. Default is <c><![CDATA[1]]></c>.
-          Use <c><![CDATA[-W0]]></c> to turn off warnings.</p>
+        <p>Sets warning level to <c>Number</c>. Defaults to
+          <c><![CDATA[1]]></c>. To turn off warnings,
+          use <c><![CDATA[-W0]]></c>.</p>
       </item>
-      <tag>-W</tag>
+      <tag><c>-W</c></tag>
       <item>
         <p>Same as <c><![CDATA[-W1]]></c>. Default.</p>
       </item>
-      <tag>-v</tag>
+      <tag><c>-v</c></tag>
       <item>
         <p>Enables verbose output.</p>
       </item>
-      <tag>-b <em>output-type</em></tag>
+      <tag><c>-b &lt;Output_type&gt;</c></tag>
       <item>
         <p>Specifies the type of output file.
-          Generally, <em>output-type</em> is the same as the file extension
-          of the output file but without the period.
-          This option will be ignored by compilers that have a
+          <c>Output_type</c> is the same as the file extension
+          of the output file, but without the period.
+          This option is ignored by compilers that have
           a single output format.</p>
       </item>
-      <tag>-smp</tag>
+      <tag><c>-smp</c></tag>
       <item>
-        <p>Compile using the SMP emulator. This is mainly useful
-          for compiling native code, which needs to be compiled with the same
-          run-time system that it should be run on.</p>
+        <p>Compiles using the SMP emulator. This is mainly useful
+          for compiling native code, which must be compiled with the same
+          runtime system that it is to be run on.</p>
       </item>
-      <tag>-M</tag>
+      <tag><c>-M</c></tag>
       <item>
-        <p>Produces a Makefile rule to track headers dependencies. The
-          rule is sent to stdout. No object file is produced.
-        </p>
+        <p>Produces a Makefile rule to track header dependencies. The
+          rule is sent to <c>stdout</c>. No object file is produced.</p>
       </item>
-      <tag>-MF <em>Makefile</em></tag>
+      <tag><c>-MF &lt;Makefile&gt;</c></tag>
       <item>
-        <p>Like the <c><![CDATA[-M]]></c> option above, except that the
-          Makefile is written to <em>Makefile</em>. No object
-          file is produced.
-        </p>
+        <p>As option <c><![CDATA[-M]]></c>, except that the
+          Makefile is written to <c>Makefile</c>. No object
+          file is produced.</p>
       </item>
-      <tag>-MD</tag>
+      <tag><c>-MD</c></tag>
       <item>
-        <p>Same as <c><![CDATA[-M -MF <File>.Pbeam]]></c>.
-        </p>
+        <p>Same as <c><![CDATA[-M -MF <File>.Pbeam]]></c>.</p>
       </item>
-      <tag>-MT <em>Target</em></tag>
+      <tag><c>-MT &lt;Target&gt;</c></tag>
       <item>
-        <p>In conjunction with <c><![CDATA[-M]]></c> or
-          <c><![CDATA[-MF]]></c>, change the name of the rule emitted
-          to <em>Target</em>.
-        </p>
+        <p>In conjunction with option <c><![CDATA[-M]]></c> or
+          <c><![CDATA[-MF]]></c>, changes the name of the rule emitted
+          to <c>Target</c>.</p>
       </item>
-      <tag>-MQ <em>Target</em></tag>
+      <tag><c>-MQ &lt;Target&gt;</c></tag>
       <item>
-        <p>Like the <c><![CDATA[-MT]]></c> option above, except that
-          characters special to make(1) are quoted.
-        </p>
+        <p>As option <c><![CDATA[-MT]]></c>, except that characters special to
+          <c>make/1</c> are quoted.</p>
       </item>
-      <tag>-MP</tag>
+      <tag><c>-MP</c></tag>
       <item>
-        <p>In conjunction with <c><![CDATA[-M]]></c> or
-          <c><![CDATA[-MF]]></c>, add a phony target for each dependency.
-        </p>
+        <p>In conjunction with option <c><![CDATA[-M]]></c> or
+          <c><![CDATA[-MF]]></c>, adds a phony target for each dependency.</p>
       </item>
-      <tag>-MG</tag>
+      <tag><c>-MG</c></tag>
       <item>
-        <p>In conjunction with <c><![CDATA[-M]]></c> or
-          <c><![CDATA[-MF]]></c>, consider missing headers as generated
-          files and add them to the dependencies.
-        </p>
+        <p>In conjunction with option <c><![CDATA[-M]]></c> or
+          <c><![CDATA[-MF]]></c>, considers missing headers as generated
+          files and adds them to the dependencies.</p>
       </item>
-      <tag>--</tag>
+      <tag><c>--</c></tag>
       <item>
         <p>Signals that no more options will follow.
-          The rest of the arguments will be treated as file names,
+          The rest of the arguments is treated as filenames,
           even if they start with hyphens.</p>
       </item>
-      <tag>+<em>term</em></tag>
+      <tag><c>+&lt;Term&gt;</c></tag>
       <item>
-        <p>A flag starting with a plus ('<em>+</em>') rather than a hyphen
-          will be converted to an Erlang term and passed unchanged to
+        <p>A flag starting with a plus (<c>+</c>) rather than a hyphen
+          is converted to an Erlang term and passed unchanged to
           the compiler.
-          For instance, the <c><![CDATA[export_all]]></c> option for the Erlang
+          For example, option <c><![CDATA[export_all]]></c> for the Erlang
           compiler can be specified as follows:</p>
         <pre>
 erlc +export_all file.erl</pre>
         <p>Depending on the platform, the value may need to be
           quoted if the shell itself interprets certain characters.
-          On Unix, terms which contain tuples and list
-          must be quoted. Terms which contain spaces
+          On Unix, terms containing tuples and lists
+          must be quoted. Terms containing spaces
           must be quoted on all platforms.</p>
       </item>
     </taglist>
@@ -206,19 +201,19 @@ erlc +export_all file.erl</pre>
 
   <section>
     <title>Special Flags</title>
-    <p>The flags in this section are useful in special situations
-      such as re-building the OTP system.</p>
+    <p>The following flags are useful in special situations,
+      such as rebuilding the OTP system:</p>
     <taglist>
-      <tag>-pa <em>directory</em></tag>
+      <tag><c>-pa &lt;Directory&gt;</c></tag>
       <item>
-        <p>Appends <em>directory</em> to the front of the code path in
+        <p>Appends <c>Directory</c> to the front of the code path in
           the invoked Erlang emulator.
           This can be used to invoke another
           compiler than the default one.</p>
       </item>
-      <tag>-pz <em>directory</em></tag>
+      <tag><c>-pz &lt;Directory&gt;</c></tag>
       <item>
-        <p>Appends <em>directory</em> to the code path in
+        <p>Appends <c>Directory</c> to the code path in
           the invoked Erlang emulator.</p>
       </item>
     </taglist>
@@ -226,63 +221,70 @@ erlc +export_all file.erl</pre>
 
   <section>
     <title>Supported Compilers</title>
+    <p>The following compilers are supported:</p>
     <taglist>
-      <tag>.erl</tag>
+      <tag><c>.erl</c></tag>
       <item>
         <p>Erlang source code. It generates a <c><![CDATA[.beam]]></c> file.</p>
-        <p>The options -P, -E, and -S are equivalent to +'P',
-          +'E', and +'S', except that it is not necessary to include the single quotes to protect them
-          from the shell.</p>
-        <p>Supported options: -I, -o, -D, -v, -W, -b.</p>
+        <p>Options <c>-P</c>, <c>-E</c>, and <c>-S</c> are equivalent to
+          <c>+'P'</c>, <c>+'E'</c>, and <c>+'S'</c>, except that it is not
+          necessary to include the single quotes to protect them from the
+          shell.</p>
+        <p>Supported options: <c>-I</c>, <c>-o</c>, <c>-D</c>, <c>-v</c>,
+          <c>-W</c>, <c>-b</c>.</p>
       </item>
-      <tag>.S</tag>
+      <tag><c>.S</c></tag>
       <item>
-        <p>Erlang assembler source code. It generates a <c><![CDATA[.beam]]></c> file.</p>
-        <p>Supported options: same as for .erl.</p>
+        <p>Erlang assembler source code. It generates a <c><![CDATA[.beam]]></c>
+          file.</p>
+        <p>Supported options: same as for <c>.erl</c>.</p>
       </item>
-      <tag>.core</tag>
+      <tag><c>.core</c></tag>
       <item>
-        <p>Erlang core source code. It generates a <c><![CDATA[.beam]]></c> file.</p>
-        <p>Supported options: same as for .erl.</p>
+        <p>Erlang core source code. It generates a <c><![CDATA[.beam]]></c>
+          file.</p>
+        <p>Supported options: same as for <c>.erl</c>.</p>
       </item>
-      <tag>.yrl</tag>
+      <tag><c>.yrl</c></tag>
       <item>
         <p>Yecc source code. It generates an <c><![CDATA[.erl]]></c> file.</p>
-        <p>Use the -I option with the name of a file to use that file
-          as a customized prologue file (the <c><![CDATA[includefile]]></c> option).</p>
-        <p>Supported options: -o, -v, -I, -W (see above).</p>
+        <p>Use option <c>-I</c> with the name of a file to use that file
+          as a customized prologue file (option
+          <c><![CDATA[includefile]]></c>).</p>
+        <p>Supported options: <c>-o</c>, <c>-v</c>, <c>-I</c>, <c>-W</c>.</p>
       </item>
-      <tag>.mib</tag>
+      <tag><c>.mib</c></tag>
       <item>
         <p>MIB for SNMP. It generates a <c><![CDATA[.bin]]></c> file.</p>
-        <p>Supported options: -I, -o, -W.</p>
+        <p>Supported options: <c>-I</c>, <c>-o</c>, <c>-W</c>.</p>
       </item>
-      <tag>.bin</tag>
+      <tag><c>.bin</c></tag>
       <item>
-        <p>A compiled MIB for SNMP. It generates a <c><![CDATA[.hrl]]></c> file.</p>
-        <p>Supported options: -o, -v.</p>
+        <p>A compiled MIB for SNMP. It generates a <c><![CDATA[.hrl]]></c>
+          file.</p>
+        <p>Supported options: <c>-o</c>, <c>-v</c>.</p>
       </item>
-      <tag>.rel</tag>
+      <tag><c>.rel</c></tag>
       <item>
         <p>Script file. It generates a boot file.</p>
-        <p>Use the -I to name directories to be searched for application
-          files (equivalent to the <c><![CDATA[path]]></c> in the option list for
-          <c><![CDATA[systools:make_script/2]]></c>).</p>
-        <p>Supported options: -o.</p>
+        <p>Use option <c>-I</c> to name directories to be searched for
+          application files (equivalent to the <c><![CDATA[path]]></c> in the
+          option list for <c><![CDATA[systools:make_script/2]]></c>).</p>
+        <p>Supported option: <c>-o</c>.</p>
       </item>
-      <tag>.asn1</tag>
+      <tag><c>.asn1</c></tag>
       <item>
-        <p>ASN1 file.</p>
-        <p>Creates an <c><![CDATA[.erl]]></c>, <c><![CDATA[.hrl]]></c>, and <c><![CDATA[.asn1db]]></c> file from
-          an <c><![CDATA[.asn1]]></c> file. Also compiles the <c><![CDATA[.erl]]></c> using the Erlang
-          compiler unless the <c><![CDATA[+noobj]]></c> options is given.</p>
-        <p>Supported options: -I, -o, -b, -W.</p>
+        <p>ASN1 file. It creates an <c><![CDATA[.erl]]></c>,
+          <c><![CDATA[.hrl]]></c>, and <c><![CDATA[.asn1db]]></c> file from
+          an <c><![CDATA[.asn1]]></c> file. Also compiles the
+          <c><![CDATA[.erl]]></c> using the Erlang compiler unless option
+          <c><![CDATA[+noobj]]></c> is specified.</p>
+        <p>Supported options: <c>-I</c>, <c>-o</c>, <c>-b</c>, <c>-W</c>.</p>
       </item>
-      <tag>.idl</tag>
+      <tag><c>.idl</c></tag>
       <item>
-        <p>IC file.</p>
-        <p>Runs the IDL compiler.</p>
-        <p>Supported options: -I, -o.</p>
+        <p>IC file. It runs the IDL compiler.</p>
+        <p>Supported options: <c>-I</c>, <c>-o</c>.</p>
       </item>
     </taglist>
   </section>
@@ -290,20 +292,20 @@ erlc +export_all file.erl</pre>
   <section>
     <title>Environment Variables</title>
     <taglist>
-      <tag>ERLC_EMULATOR</tag>
-      <item>The command for starting the emulator.
-       Default is <em>erl</em> in the same directory as the <em>erlc</em> program
-       itself, or if it doesn't exist, <em>erl</em> in any of the directories
-       given in the <em>PATH</em> environment variable.</item>
+      <tag><c>ERLC_EMULATOR</c></tag>
+      <item>The command for starting the emulator. Defaults to <c>erl</c>
+        in the same directory as the <c>erlc</c> program itself,
+        or, if it does not exist, <c>erl</c> in any of the directories
+        specified in environment variable <c>PATH</c>.</item>
     </taglist>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="erl">erl(1)</seealso>,
-      <seealso marker="compiler:compile">compile(3)</seealso>,
-      <seealso marker="parsetools:yecc">yecc(3)</seealso>,
-      <seealso marker="snmp:snmp">snmp(3)</seealso></p>
+    <title>See Also</title>
+    <p><seealso marker="erl"><c>erl(1)</c></seealso>,
+      <seealso marker="compiler:compile"><c>compiler:compile(3)</c></seealso>,
+      <seealso marker="parsetools:yecc"><c>parsetools:yecc(3)</c></seealso>,
+      <seealso marker="snmp:snmp"><c>snmp:snmp(3)</c></seealso></p>
   </section>
 </comref>
 
diff --git a/erts/doc/src/erlsrv.xml b/erts/doc/src/erlsrv.xml
index fb00444aa4..53583b625d 100644
--- a/erts/doc/src/erlsrv.xml
+++ b/erts/doc/src/erlsrv.xml
@@ -28,343 +28,447 @@
     <docno></docno>
     <approved></approved>
     <checked></checked>
-    <date>98-04-29</date>
+    <date>1998-04-29</date>
     <rev></rev>
     <file>erlsrv.xml</file>
   </header>
   <com>erlsrv</com>
-  <comsummary>Run the Erlang emulator as a service on Windows NT&reg;</comsummary>
+  <comsummary>Run the Erlang emulator as a service on Windows</comsummary>
   <description>
-    <p>This utility is specific to Windows NT/2000/XP&reg; (and subsequent versions of Windows) It allows Erlang
+    <p>This utility is specific to Windows NT/2000/XP (and later
+      versions of Windows). It allows Erlang
       emulators to run as services on the Windows system, allowing embedded
-      systems to start without any user needing to log in. The
+      systems to start without any user needing to log on. The
       emulator started in this way can be manipulated through the
-      Windows&reg; services applet in a manner similar to other
-      services.</p>
-    <p>Note that erlsrv is not a general service utility for Windows, but designed for embedded Erlang systems.</p> 
-    <p>As well as being the actual service, erlsrv also provides a
-      command line interface for registering, changing, starting and
-      stopping services.</p>
-    <p>To manipulate services, the logged in user should have
-      Administrator privileges on the machine. The Erlang machine
+      Windows services applet in a manner similar to other services.</p>
+
+    <p>Notice that <c>erlsrv</c> is not a general service utility for Windows,
+      but designed for embedded Erlang systems.</p> 
+
+    <p><c>erlsrv</c> also provides a command-line interface for registering,
+      changing, starting, and stopping services.</p>
+
+    <p>To manipulate services, the logged on user is to have
+      administrator privileges on the machine. The Erlang machine
       itself is (default) run as the local administrator. This can be
-      changed with the Services applet in Windows &reg;.</p>
+      changed with the Services applet in Windows.</p>
+
     <p>The processes created by the service can, as opposed to normal
-      services, be "killed" with the task manager. Killing a emulator
-      that is started by a service will trigger the "OnFail" action
-      specified for that service, which may be a reboot.</p>
-    <p>The following parameters may be specified for each Erlang
-      service:</p>
-    <list type="bulleted">
+      services, be "killed" with the task manager. Killing an emulator
+      that is started by a service triggers the "OnFail" action
+      specified for that service, which can be a reboot.</p>
+
+    <p>The following parameters can be specified for each Erlang service:</p>
+
+    <taglist>
+      <tag><c><![CDATA[StopAction]]></c></tag>
       <item>
-        <p><c><![CDATA[StopAction]]></c>: This tells <c><![CDATA[erlsrv]]></c> how to stop
+        <p>Tells <c><![CDATA[erlsrv]]></c> how to stop
           the Erlang emulator. Default is to kill it (Win32
           TerminateProcess), but this action can specify any Erlang
           shell command that will be executed in the emulator to make
           it stop. The emulator is expected to stop within 30 seconds
           after the command is issued in the shell. If the emulator is
-          not stopped, it will report a running state to the service
+          not stopped, it reports a running state to the service
           manager.</p>
       </item>
+      <tag><c><![CDATA[OnFail]]></c></tag>
       <item>
-        <p><c><![CDATA[OnFail]]></c>: This can be either of <c><![CDATA[reboot]]></c>,
-          <c><![CDATA[restart]]></c>, <c><![CDATA[restart_always]]></c> or <c><![CDATA[ignore]]></c> (the
-          default). In case of <c><![CDATA[reboot]]></c>, the NT system is
-          rebooted whenever the emulator stops (a more simple form of
-          watchdog), this could be useful for less critical systems,
-          otherwise use the heart functionality to accomplish
-          this. The restart value makes the Erlang emulator be
-          restarted (with whatever parameters are registered for the
-          service at the occasion) when it stops. If the emulator
-          stops again within 10 seconds, it is not restarted to avoid
-          an infinite loop which could completely hang the NT
-          system. <c><![CDATA[restart_always]]></c> is similar to restart, but
-          does not try to detect cyclic restarts, it is expected that
-          some other mechanism is present to avoid the problem.  The
-          default (ignore) just reports the service as stopped to the
-          service manager whenever it fails, it has to be manually
-          restarted.</p>
-        <p>On a system where release handling is
-          used, this should always be set to <c><![CDATA[ignore]]></c>. Use
-          <c><![CDATA[heart]]></c> to restart the service on failure instead.</p>
+        <p>Can be one of the following:</p>
+        <taglist>
+          <tag><c><![CDATA[reboot]]></c></tag>
+          <item>
+            <p>The Windows system is rebooted whenever the emulator stops
+              (a more simple form of watchdog). This can be useful for
+              less critical systems, otherwise use the heart functionality
+              to accomplish this.</p>
+          </item>
+          <tag><c><![CDATA[restart]]></c></tag>
+          <item>
+            <p>Makes the Erlang emulator be
+              restarted (with whatever parameters are registered for the
+              service at the occasion) when it stops. If the emulator
+              stops again within 10 seconds, it is not restarted to avoid
+              an infinite loop, which could hang the Windows system.</p>
+          </item>
+          <tag><c><![CDATA[restart_always]]></c></tag>
+          <item>
+            <p>Similar to <c><![CDATA[restart]]></c>, but does
+              not try to detect cyclic restarts; it is expected that
+              some other mechanism is present to avoid the problem.</p>
+          </item>
+          <tag><c><![CDATA[ignore]]></c> (the default)</tag>
+          <item>
+            <p>Reports the service as stopped to the service manager
+              whenever it fails; it must be manually restarted.</p>
+          </item>
+        </taglist>
+        <p>On a system where release handling is used,
+          this is always to be set to <c><![CDATA[ignore]]></c>. Use
+          <c><![CDATA[heart]]></c> to restart the service on failure
+          instead.</p>
       </item>
+      <tag><c><![CDATA[Machine]]></c></tag>
       <item>
-        <p><c><![CDATA[Machine]]></c>: The location of the Erlang
-          emulator. The default is the <c><![CDATA[erl.exe]]></c> located in the
-          same directory as erlsrv.exe. Do not specify <c><![CDATA[werl.exe]]></c>
-          as this emulator, it will not work.</p>
-        <p>If the system
-          uses release handling, this should be set to a program
-          similar to <c><![CDATA[start_erl.exe]]></c>.</p>
+        <p>The location of the Erlang emulator.
+          The default is the <c><![CDATA[erl.exe]]></c> located in the same
+          directory as <c>erlsrv.exe</c>. Do not specify
+          <c><![CDATA[werl.exe]]></c> as this emulator, it will not work.</p>
+        <p>If the system uses release handling, this is to be set to a
+          program similar to <c><![CDATA[start_erl.exe]]></c>.</p>
       </item>
+      <tag><c><![CDATA[Env]]></c></tag>
       <item>
-        <p><c><![CDATA[Env]]></c>: Specifies an <em>additional</em> environment
+        <p>Specifies an <em>extra</em> environment
           for the emulator. The environment variables specified
-          here are added to the system wide environment block that is
+          here are added to the system-wide environment block that is
           normally present when a service starts up. Variables present
-          in both the system wide environment and in the service
+          in both the system-wide environment and in the service
           environment specification will be set to the value specified
           in the service.</p>
       </item>
+      <tag><c><![CDATA[WorkDir]]></c></tag>
       <item>
-        <p><c><![CDATA[WorkDir]]></c>: The working directory for the Erlang
-          emulator, has to be on a local drive (there are no network
-          drives mounted when a service starts). Default working
-          directory for services is <c><![CDATA[%SystemDrive%%SystemPath%]]></c>.
+        <p>The working directory for the Erlang emulator.
+          Must be on a local drive (no network drives are mounted when a
+          service starts). Default working directory for services is
+          <c><![CDATA[%SystemDrive%%SystemPath%]]></c>.
           Debug log files will be placed in this directory.</p>
       </item>
+      <tag><c><![CDATA[Priority]]></c></tag>
       <item>
-        <p><c><![CDATA[Priority]]></c>: The process priority of the emulator,
-          this can be one of <c><![CDATA[realtime]]></c>, <c><![CDATA[high]]></c>, <c><![CDATA[low]]></c>
-          or <c><![CDATA[default]]></c> (the default). Real-time priority is not
-          recommended, the machine will possibly be inaccessible to
-          interactive users. High priority could be used if two Erlang
-          nodes should reside on one dedicated system and one should
-          have precedence over the other. Low process priority may be
-          used if interactive performance should not be affected by
-          the emulator process.</p>
+        <p>The process priority of the emulator. Can be one of the
+          following:</p>
+        <taglist>
+          <tag><c><![CDATA[realtime]]></c></tag>
+          <item>
+            <p>Not recommended, as the machine will possibly be
+              inaccessible to interactive users.</p>
+          </item>
+          <tag><c><![CDATA[high]]></c></tag>
+          <item>
+            <p>Can be used if two Erlang nodes are to reside on one dedicated
+              system and one is to have precedence over the other.</p>
+          </item>
+          <tag><c><![CDATA[low]]></c></tag>
+          <item>
+            <p>Can be used if interactive performance is not to be affected
+              by the emulator process.</p>
+          </item>
+          <tag><c><![CDATA[default]]></c> (the default></tag>
+          <item>
+          </item>
+        </taglist>
       </item>
+      <tag><c><![CDATA[SName or Name]]></c></tag>
       <item>
-        <p><c><![CDATA[SName or Name]]></c>: Specifies the short or long
-          node-name of the Erlang emulator. The Erlang services are
-          always distributed, default is to use the service name as
-          (short) node-name.</p>
+        <p>Specifies the short or long
+          node name of the Erlang emulator. The Erlang services are
+          always distributed. Default is to use the service name as
+          (short) nodename.</p>
       </item>
+      <tag><c><![CDATA[DebugType]]></c></tag>
       <item>
-        <p><c><![CDATA[DebugType]]></c>: Can be one of <c><![CDATA[none]]></c> (default),
-          <c><![CDATA[new]]></c>, <c><![CDATA[reuse]]></c> or <c><![CDATA[console]]></c>.
-          Specifies that output from the Erlang shell should be
+        <p>Specifies that output from the Erlang shell is to be
           sent to a "debug log". The log file is named
           &lt;servicename&gt;<c><![CDATA[.debug]]></c> or
-          &lt;servicename&gt;<c><![CDATA[.debug.]]></c>&lt;N&gt;, where &lt;N&gt; is
-          an integer between 1 and 99. The log-file is placed in the
-          working directory of the service (as specified in WorkDir). The
-          <c><![CDATA[reuse]]></c> option always reuses the same log file
-          (&lt;servicename&gt;<c><![CDATA[.debug]]></c>) and the <c><![CDATA[new]]></c> option
-          uses a separate log file for every invocation of the service
-          (&lt;servicename&gt;<c><![CDATA[.debug.]]></c>&lt;N&gt;). The <c><![CDATA[console]]></c>
-          option opens an interactive Windows&reg; console window for
-          the Erlang shell of the service. The <c><![CDATA[console]]></c> option 
-          automatically
-          disables the <c><![CDATA[StopAction]]></c> and a service started with an
-          interactive console window will not survive logouts, 
-          <c><![CDATA[OnFail]]></c> actions do not work with debug-consoles either.
-          If no <c><![CDATA[DebugType]]></c> is specified (<c><![CDATA[none]]></c>), the
-          output of the Erlang shell is discarded.</p>
-        <p>The <c><![CDATA[console]]></c><c><![CDATA[DebugType]]></c> is <em>not in any way</em>
-          intended for production. It is <em>only</em> a convenient way to
-          debug Erlang services during development. The <c><![CDATA[new]]></c> and
-          <c><![CDATA[reuse]]></c> options might seem convenient to have in a
-          production system, but one has to take into account that the
-          logs will grow indefinitely during the systems lifetime and
-          there is no way, short of restarting the service, to
-          truncate those logs. In short, the <c><![CDATA[DebugType]]></c> is
-          intended for debugging only. Logs during production are
-          better produced with the standard Erlang logging
-          facilities.</p>
+          &lt;servicename&gt;<c><![CDATA[.debug.]]></c>&lt;N&gt;,
+          where &lt;N&gt; is an integer from 1 through 99.
+          The log file is placed in the working directory of the
+          service (as specified in <c>WorkDir</c>).</p>
+        <p>Can be one of the following:</p>
+        <taglist>
+          <tag><c><![CDATA[new]]></c></tag>
+          <item>
+            <p>Uses a separate log file for every invocation of the service
+              (&lt;servicename&gt;<c><![CDATA[.debug.]]></c>&lt;N&gt;).</p>
+          </item>
+          <tag><c><![CDATA[reuse]]></c></tag>
+          <item>
+            <p>Reuses the same log file
+              (&lt;servicename&gt;<c><![CDATA[.debug]]></c>).</p>
+          </item>
+          <tag><c><![CDATA[console]]></c></tag>
+          <item>
+            <p>Opens an interactive Windows console window for the Erlang
+              shell of the service. Automatically disables the
+              <c><![CDATA[StopAction]]></c>. A service started with an
+              interactive console window does not survive logouts.
+              <c><![CDATA[OnFail]]></c> actions do not work with
+              debug consoles either.</p>
+          </item>
+          <tag><c><![CDATA[none]]></c> (the default)</tag>
+          <item>
+            <p>The output of the Erlang shell is discarded.</p>
+          </item>
+        </taglist>
+        <note>
+          <p>The <c><![CDATA[console]]></c> option is <em>not</em> intended
+            for production. It is <em>only</em> a convenient way to debug
+            Erlang services during development.</p>
+          <p>The <c><![CDATA[new]]></c> and <c><![CDATA[reuse]]></c> options
+            might seem convenient in a production system, but consider that
+            the logs grow indefinitely during the system lifetime and cannot
+            be truncated, except if the service is restarted.</p>
+          <p>In short, the <c><![CDATA[DebugType]]></c> is
+            intended for debugging only. Logs during production are
+            better produced with the standard Erlang logging facilities.</p>
+        </note>
       </item>
+      <tag><c><![CDATA[Args]]></c></tag>
       <item>
-        <p><c><![CDATA[Args]]></c>: Additional arguments passed to the
-          emulator startup program <c><![CDATA[erl.exe]]></c> (or
-          <c><![CDATA[start_erl.exe]]></c>).  Arguments that cannot be specified
-          here are <c><![CDATA[-noinput]]></c> (StopActions would not work),
-          <c><![CDATA[-name]]></c> and <c><![CDATA[-sname]]></c> (they are specified in any
-          way. The most common use is for specifying cookies and flags
-          to be passed to init:boot() (<c><![CDATA[-s]]></c>).</p>
+        <p>Passes extra arguments to the emulator startup program
+          <c><![CDATA[erl.exe]]></c> (or <c><![CDATA[start_erl.exe]]></c>).
+          Arguments that cannot be specified here are
+          <c><![CDATA[-noinput]]></c> (<c>StopActions</c> would not work),
+          <c><![CDATA[-name]]></c>, and <c><![CDATA[-sname]]></c> (they are
+          specified in any way). The most common use is for specifying cookies
+          and flags to be passed to <c>init:boot()</c>
+          (<c><![CDATA[-s]]></c>).</p>
       </item>
+      <tag><c><![CDATA[InternalServiceName]]></c></tag>
       <item>
-        <p><c><![CDATA[InternalServiceName]]></c>: Specifies the Windows&reg; internal service name (not the display name, which is the one <c>erlsrv</c> uses to identify the service).</p>
-	<p>This internal name can not be changed, it is fixed even if the service is renamed. <c>Erlsrv</c> generates a unique internal name when a service is created, it is recommended to keep to the defaut if release-handling is to be used for the application.</p>
-	<p>The internal service name can be seen in the Windows&reg; service manager if viewing <c>Properties</c> for an erlang service.</p>
+        <p>Specifies the Windows-internal service name (not the display name,
+          which is the one <c>erlsrv</c> uses to identify the service).</p>
+        <p>This internal name cannot be changed, it is fixed even if the
+          service is renamed. <c>erlsrv</c> generates a unique internal name
+          when a service is created. It is recommended to keep to the default
+          if release handling is to be used for the application.</p>
+        <p>The internal service name can be seen in the Windows service
+          manager if viewing <c>Properties</c> for an Erlang service.</p>
       </item>
+      <tag><c><![CDATA[Comment]]></c></tag>
       <item>
-        <p><c><![CDATA[Comment]]></c>: A textual comment describing the service. Not mandatory, but shows up as the service description in the Windows&reg; service manager.</p>
+        <p>A textual comment describing the service. Not mandatory, but shows
+          up as the service description in the Windows service manager.</p>
       </item>
-    </list>
-    <p>      <marker id="001"></marker>
- The naming of the service in a system that
-      uses release handling has to follow the convention
+    </taglist>
+
+    <p><marker id="001"></marker>
+      The naming of the service in a system that
+      uses release handling must follow the convention
       <em>NodeName</em>_<em>Release</em>, where <em>NodeName</em> is
-      the first part of the Erlang nodename (up to, but not including
+      the first part of the Erlang node name (up to, but not including
       the "@") and <em>Release</em> is the current release of the
       application.</p>
   </description>
+
   <funcs>
     <func>
       <name>erlsrv {set | add} &lt;service-name> [&lt;service options>]</name>
-      <fsummary>Add or modify an Erlang service</fsummary>
+      <fsummary>Add or modify an Erlang service.</fsummary>
       <desc>
-        <p>The set and add commands adds or modifies a Erlang service
-          respectively.  The simplest form of an add command would be
-          completely without options in which case all default values
+        <p>The <c>set</c> and <c>add</c> commands modifies or adds an Erlang
+          service, respectively. The simplest form of an <c>add</c> command is
+          without any options in which case all default values
           (described above) apply. The service name is mandatory.</p>
-        <p>Every option can be given without parameters, in which case
-          the default value is applied. Values to the options are
-          supplied <em>only</em> when the default should not be used
-          (i.e. <c><![CDATA[erlsrv set myservice -prio -arg]]></c> sets the
-          default priority and removes all arguments).</p>
-        <p>The following service options are currently available:</p>
+        <p>Every option can be specified without parameters, the
+          default value is then applied. Values to the options are
+          supplied <em>only</em> when the default is not to be used.
+          For example, <c><![CDATA[erlsrv set myservice -prio -arg]]></c>
+          sets the default priority and removes all arguments.</p>
+        <p>Service options:</p>
         <taglist>
-          <tag>-st[opaction] [&lt;erlang shell command&gt;]</tag>
-          <item>Defines the StopAction, the command given to the Erlang
-           shell when the service is stopped. Default is none.</item>
-          <tag>-on[fail] [{reboot | restart | restart_always}]</tag>
-          <item>Specifies the action to take when the Erlang emulator
-           stops unexpectedly. Default is to ignore.</item>
-          <tag>-m[achine] [&lt;erl-command&gt;]</tag>
-          <item>The complete path to the Erlang emulator, never use the
-           werl program for this. Default is the <c><![CDATA[erl.exe]]></c> in the
-           same directory as <c><![CDATA[erlsrv.exe]]></c>. When release handling
-           is used, this should be set to a program similar to
-          <c><![CDATA[start_erl.exe]]></c>.</item>
-          <tag>-e[nv] [&lt;variable&gt;[=&lt;value&gt;]] ...</tag>
-          <item>Edits the environment block for the service. Every
-           environment variable specified will add to the system
-           environment block. If a variable specified here has the same
-           name as a system wide environment variable, the specified
-           value overrides the system wide.  Environment variables are
-           added to this list by specifying
-           &lt;variable&gt;=&lt;value&gt; and deleted from the list by
-           specifying &lt;variable&gt; alone. The environment block is
-           automatically sorted. Any number of <c><![CDATA[-env]]></c> options can
-           be specified in one command. Default is to use the system
-           environment block unmodified (except for two additions, see
-          <seealso marker="#002">below</seealso>).</item>
-          <tag>-w[orkdir] [&lt;directory&gt;]</tag>
-          <item>The initial working directory of the Erlang
-           emulator. Default is the system directory.</item>
-          <tag>-p[riority] [{low|high|realtime}]</tag>
-          <item>The priority of the Erlang emulator. The default is the
-           Windows&reg; default priority.</item>
-          <tag>{-sn[ame] | -n[ame]} [&lt;node-name&gt;]</tag>
-          <item>The node-name of the Erlang machine, distribution is
-           mandatory. Default is <c><![CDATA[-sname <service name>]]></c>.
+          <tag><c>-st[opaction] [&lt;erlang shell command&gt;]</c></tag>
+          <item>
+            <p>Defines the <c><![CDATA[StopAction]]></c>, the command given
+              to the Erlang shell when the service is stopped.
+              Default is none.</p>
+          </item>
+          <tag><c>-on[fail] [{reboot | restart | restart_always}]</c></tag>
+          <item>
+            <p>The action to take when the Erlang emulator
+              stops unexpectedly. Default is to ignore.</p>
+          </item>
+          <tag><c>-m[achine] [&lt;erl-command&gt;]</c></tag>
+          <item>
+            <p>The complete path to the Erlang emulator. Never use the
+              <c>werl</c> program for this. Defaults to the
+              <c><![CDATA[erl.exe]]></c> in the same directory as
+              <c><![CDATA[erlsrv.exe]]></c>. When release handling
+              is used, this is to be set to a program similar to
+              <c><![CDATA[start_erl.exe]]></c>.</p>
+          </item>
+          <tag><c>-e[nv] [&lt;variable&gt;[=&lt;value&gt;]] ...</c></tag>
+          <item>
+            <p>Edits the environment block for the service. Every
+              environment variable specified is added to the system
+              environment block. If a variable specified here has the same
+              name as a system-wide environment variable, the specified
+              value overrides the system-wide. Environment variables are
+              added to this list by specifying
+              &lt;variable&gt;=&lt;value&gt; and deleted from the list by
+              specifying &lt;variable&gt; alone. The environment block is
+              automatically sorted. Any number of <c><![CDATA[-env]]></c>
+              options can be specified in one command. Default is to use the
+              system environment block unmodified (except for two additions,
+              see section <seealso marker="#002">Environment</seealso>
+              below).</p>
+          </item>
+          <tag><c>-w[orkdir] [&lt;directory&gt;]</c></tag>
+          <item>
+            <p>The initial working directory of the Erlang
+              emulator. Defaults to the system directory.</p>
+          </item>
+          <tag><c>-p[riority] [{low|high|realtime}]</c></tag>
+          <item>
+            <p>The priority of the Erlang emulator. Default to the
+              Windows default priority.</p>
+          </item>
+          <tag><c>{-sn[ame] | -n[ame]} [&lt;node-name&gt;]</c></tag>
+          <item>
+            <p>The node name of the Erlang machine. Distribution is mandatory.
+              Defaults to <c><![CDATA[-sname <service name>]]></c>.</p>
+          </item>
+          <tag><c>-d[ebugtype] [{new|reuse|console}]</c></tag>
+          <item>
+            <p>Specifies where shell output is to be sent.
+              Default is that shell output is discarded.
+              To be used only for debugging.</p>
+          </item>
+          <tag><c>-ar[gs] [&lt;limited erl arguments&gt;]</c></tag>
+          <item>
+            <p>Extra arguments to the Erlang emulator. Avoid
+              <c><![CDATA[-noinput]]></c>, <c><![CDATA[-noshell]]></c>, and
+              <c><![CDATA[-sname]]></c>/<c><![CDATA[-name]]></c>. Default is
+              no extra arguments. Remember that the services cookie file is not
+              necessarily the same as the interactive users. The service
+              runs as the local administrator. Specify all arguments
+              together in one string, use double quotes (") to specify an
+              argument string containing spaces, and use quoted quotes (\")
+              to specify a quote within the argument string if necessary.</p>
+          </item>
+          <tag><c>-i[nternalservicename] [&lt;internal name&gt;]</c></tag>
+          <item>
+            <p><em>Only</em> allowed for <c>add</c>. Specifies a
+              Windows-internal service name for the service, which by
+              default is set to something unique (prefixed with the
+              original service name) by <c>erlsrv</c> when adding a new
+              service. Specifying this is a purely cosmethic action and is
+              <em>not</em> recommended if release handling is to be
+              performed. The internal service name cannot be changed once
+              the service is created. The internal name is <em>not</em> to
+              be confused with the ordinary service name, which is the name
+              used to identify a service to <c>erlsrv</c>.</p>
+          </item>
+          <tag><c>-c[omment] [&lt;short description&gt;]</c></tag>
+          <item>
+            <p>Specifies a textual comment describing the
+              service. This comment shows up as the service description
+              in the Windows service manager.</p>
           </item>
-          <tag>-d[ebugtype] [{new|reuse|console}]</tag>
-          <item>Specifies where shell output should be sent,
-           default is that shell output is discarded. 
-           To be used only for debugging.</item>
-          <tag>-ar[gs] [&lt;limited erl arguments&gt;]</tag>
-          <item>Additional arguments to the Erlang emulator, avoid
-          <c><![CDATA[-noinput]]></c>, <c><![CDATA[-noshell]]></c> and
-          <c><![CDATA[-sname]]></c>/<c><![CDATA[-name]]></c>. Default is no additional
-           arguments. Remember that the services cookie file is not
-           necessarily the same as the interactive users. The service
-           runs as the local administrator. All arguments should be given
-           together in one string, use double quotes (") to give an
-           argument string containing spaces and use quoted quotes (\")
-           to give an quote within the argument string if
-           necessary.</item>
-	   <tag>-i[nternalservicename] [&lt;internal name&gt;]</tag>
-           <item><em>Only</em> allowed for <c>add</c>. Specifies a
-           Windows&reg; internal service name for the service, which by
-           default is set to something unique (prefixed with the
-           original service name) by erlsrv when adding a new
-           service. Specifying this is a purely cosmethic action and is
-           <em>not</em> recommended if release handling is to be
-           performed. The internal service name cannot be changed once
-           the service is created. The internal name is <em>not</em> to 
-	   be confused with the ordinary service name, which is the name 
-	   used to identify a service to erlsrv.</item>
-	   <tag>-c[omment] [&lt;short description&gt;]</tag>
-           <item>Specifies a textual comment describing the
-           service. This comment will show upp as the service description
-           in the Windows&reg; service manager.</item>
         </taglist>
       </desc>
     </func>
+
     <func>
-      <name>erlsrv {start | start_disabled | stop | disable | enable} &lt;service-name></name>
+      <name>erlsrv {start | start_disabled | stop | disable |
+        enable} &lt;service-name></name>
       <fsummary>Manipulate the current service status.</fsummary>
       <desc>
         <p>These commands are only added for convenience, the normal
           way to manipulate the state of a service is through the
-          control panels services applet. The <c><![CDATA[start]]></c> and
+          control panels services applet.</p>
+        <p>The <c><![CDATA[start]]></c> and
           <c><![CDATA[stop]]></c> commands communicates
-          with the service manager for stopping and starting a
-          service. The commands wait until the service is actually
-          stopped or started. When disabling a service, it is not
-          stopped, the disabled state will not take effect until the
-          service actually is stopped. Enabling a service sets it in
-          automatic mode, that is started at boot. This command cannot
-          set the service to manual.  </p>
-
-	<p>The <c>start_disabled</c> command operates on a service
-	regardless of if it's enabled/disabled or started/stopped.  It
-	does this by first enabling it (regardless of if it's enabled
-	or not), then starting it (if it's not already started) and
-	then disabling it. The result will be a disabled but started
-	service, regardless of its earlier state. This is useful for
-	starting services temporarily during a release upgrade. The
-	difference between using <c>start_disabled</c> and the
-	sequence <c>enable</c>, <c>start</c> and <c>disable</c> is
-	that all other <c>erlsrv</c> commands are locked out during
-	the sequence of operations in <c>start_disable</c>, making the
-	operation atomic from an <c>erlsrv</c> user's point of
-	view.</p>
-
+          with the service manager for starting and stopping a
+          service. The commands wait until the service is
+          started or stopped. When disabling a service, it is not
+          stopped, the disabled state does not take effect until the
+          service is stopped. Enabling a service sets it in
+          automatic mode, which is started at boot. This command cannot
+          set the service to manual.</p>
+        <p>The <c>start_disabled</c> command operates on a service
+          regardless of if it is enabled/disabled or started/stopped. It
+          does this by first enabling it (regardless of if it is enabled
+          or not), then starting it (if not already started), and
+          then disabling it. The result is a disabled but started
+          service, regardless of its earlier state. This is useful for
+          starting services temporarily during a release upgrade. The
+          difference between using <c>start_disabled</c> and the
+          sequence <c>enable</c>, <c>start</c>, and <c>disable</c> is
+          that all other <c>erlsrv</c> commands are locked out during
+          the sequence of operations in <c>start_disable</c>, making the
+          operation atomic from an <c>erlsrv</c> user's point of view.</p>
       </desc>
     </func>
+
     <func>
       <name>erlsrv remove &lt;service-name&gt;</name>
       <fsummary>Remove the service.</fsummary>
       <desc>
-        <p>This command removes the service completely with all its registered
-          options. It will be stopped before it is removed.</p>
+        <p>Removes the service completely with all its registered
+          options. It is stopped before it is removed.</p>
       </desc>
     </func>
+
     <func>
       <name>erlsrv list [&lt;service-name&gt;]</name>
-      <fsummary>List all Erlang services or all options for one service.</fsummary>
+      <fsummary>List all Erlang services or all options for one service.
+      </fsummary>
       <desc>
-        <p>If no service name is supplied, a brief listing of all Erlang services
-          is presented. If a service-name is supplied, all options for that
-          service are presented.</p>
+        <p>If no service name is specified, a brief listing of all Erlang
+          services is presented. If a service name is supplied, all options
+          for that service are presented.</p>
       </desc>
     </func>
+
     <func>
       <name>erlsrv help</name>
-      <fsummary>Display a brief help text</fsummary>
+      <fsummary>Display a brief help text.</fsummary>
+      <desc>
+        <p>Displays a brief help text.</p>
+      </desc>
     </func>
   </funcs>
 
   <section>
-    <title>ENVIRONMENT</title>
-    <p>      <marker id="002"></marker>
-The environment of an Erlang machine started
-      as a service will contain two special variables,
-      <c><![CDATA[ERLSRV_SERVICE_NAME]]></c>, which is the name of the service that
-      started the machine and <c><![CDATA[ERLSRV_EXECUTABLE]]></c> which is the
-      full path to the <c><![CDATA[erlsrv.exe]]></c> that can be used to manipulate
-      the service. This will come in handy when defining a heart command for
-      your service. A command file for restarting a service will
-      simply look like this:</p>
+    <title>Environment</title>
+    <p><marker id="002"></marker>
+      The environment of an Erlang machine started
+      as a service contains two special variables:</p>
+
+    <taglist>
+      <tag><c><![CDATA[ERLSRV_SERVICE_NAME]]></c></tag>
+      <item>The name of the service that started the machine.</item>
+      <tag><c><![CDATA[ERLSRV_EXECUTABLE]]></c></tag>
+      <item>The full path to the <c><![CDATA[erlsrv.exe]]></c>, which can be
+        used to manipulate the service. This comes in handy when defining a
+        heart command for your service.</item>
+    </taglist>
+
+    <p>A command file for restarting a service looks as follows:</p>
+
     <code type="none"><![CDATA[
 @echo off
 %ERLSRV_EXECUTABLE% stop %ERLSRV_SERVICE_NAME%
 %ERLSRV_EXECUTABLE% start %ERLSRV_SERVICE_NAME%    ]]></code>
+
     <p>This command file is then set as heart command.</p>
+
     <p>The environment variables can also be used to detect that we
       are running as a service and make port programs react correctly
-      to the control events generated on logout (see below).</p>
+      to the control events generated on logout (see the next section).</p>
   </section>
 
   <section>
-    <title>PORT PROGRAMS</title>
+    <title>Port Programs</title>
     <p>When a program runs in
-      the service context, it has to handle the control events that is
+      the service context, it must handle the control events that are
       sent to every program in the system when the interactive user
       logs off. This is done in different ways for programs running in
       the console subsystem and programs running as window
-      applications. An application which runs in the console subsystem
+      applications. An application running in the console subsystem
       (normal for port programs) uses the win32 function
       <c><![CDATA[SetConsoleCtrlHandler]]></c> to register a control handler
-      that returns TRUE in answer to the <c><![CDATA[CTRL_LOGOFF_EVENT]]></c>
+      that returns <c>true</c> in answer to the
+      <c><![CDATA[CTRL_LOGOFF_EVENT]]></c>
       and <c><![CDATA[CTRL_SHUTDOWN_EVENT]]></c> events. Other applications
-      just forward <c><![CDATA[WM_ENDSESSION]]></c> and
-      <c><![CDATA[WM_QUERYENDSESSION]]></c> to the default window procedure.
-      Here is a brief example in C of how to set the console control
-      handler:</p>
+      only forward <c><![CDATA[WM_ENDSESSION]]></c> and
+      <c><![CDATA[WM_QUERYENDSESSION]]></c> to the default window procedure.</p>
+
+    <p>A brief example in C of how to set the console control handler:</p>
+
     <code type="none"><![CDATA[
 #include <windows.h>
 /* 
@@ -383,7 +487,7 @@ void initialize_handler(void){
     char buffer[2];
     /* 
      * We assume we are running as a service if this  
-     * environment variable is defined
+     * environment variable is defined.
      */
     if(GetEnvironmentVariable("ERLSRV_SERVICE_NAME",buffer,
                               (DWORD) 2)){
@@ -396,29 +500,34 @@ void initialize_handler(void){
   </section>
 
   <section>
-    <title>NOTES</title>
-    <p>Even though the options are described in a Unix-like format, the case of
-      the options or commands is not relevant, and the "/" character for options
-      can be used as well as the "-" character. </p>
-    <p>Note that the program resides in the emulators
-      <c><![CDATA[bin]]></c>-directory, not in the <c><![CDATA[bin]]></c>-directory directly under
+    <title>Notes</title>
+    <p>Although the options are described in a Unix-like format, the case of
+      the options or commands is not relevant, and both character "/" and "-"
+      can be used for options.</p>
+
+    <p>Notice that the program resides in the emulator's <c><![CDATA[bin]]></c>
+      directory, not in the <c><![CDATA[bin]]></c> directory directly under
       the Erlang root. The reasons for this are the subtle problem of
       upgrading the emulator on a running system, where a new version of
       the runtime system should not need to overwrite existing (and probably
       used) executables.</p>
-    <p>To easily manipulate the Erlang services, put
+
+    <p>To manipulate the Erlang services easily, put
       the <c><![CDATA[<erlang_root>\erts-<version>\bin]]></c> directory in
-      the path instead of <c><![CDATA[<erlang_root>\bin]]></c>. The erlsrv program
-      can be found from inside Erlang by using the
+      the path instead of <c><![CDATA[<erlang_root>\bin]]></c>. The
+      <c>erlsrv</c> program can be found from inside Erlang by using the
       <c><![CDATA[os:find_executable/1]]></c> Erlang function.</p>
-    <p>For release handling to work, use <c><![CDATA[start_erl]]></c> as the Erlang
-      machine. It is also worth mentioning again that the name of the 
-      service is significant (see <seealso marker="#001">above</seealso>).</p>
+
+    <p>For release handling to work, use <c><![CDATA[start_erl]]></c> as the
+      Erlang machine. As stated <seealso marker="#001">above</seealso>,
+      the service name is significant.</p>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p>start_erl(1), release_handler(3)</p>
+    <title>See Also</title>
+    <p><seealso marker="start_erl"><c>start_erl(1)</c></seealso>,
+      <seealso marker="sasl:release_handler">
+      <c>sasl:release_handler(3)</c></seealso></p>
   </section>
 </comref>
 
diff --git a/erts/doc/src/erts_alloc.xml b/erts/doc/src/erts_alloc.xml
index 9aef1c0b1f..c1706806fe 100644
--- a/erts/doc/src/erts_alloc.xml
+++ b/erts/doc/src/erts_alloc.xml
@@ -25,63 +25,68 @@
     <title>erts_alloc</title>
     <prepared>Rickard Green</prepared>
     <docno>1</docno>
-    <date>03-06-11</date>
+    <date>2003-06-11</date>
     <rev>1</rev>
     <file>erts_alloc.xml</file>
   </header>
   <lib>erts_alloc</lib>
-  <libsummary>An Erlang Run-Time System internal memory allocator library.</libsummary>
+  <libsummary>An Erlang runtime system internal memory allocator library.
+  </libsummary>
   <description>
-    <p><c>erts_alloc</c> is an Erlang Run-Time System internal memory
+    <p><c>erts_alloc</c> is an Erlang runtime system internal memory
       allocator library. <c>erts_alloc</c> provides the Erlang
-      Run-Time System with a number of memory allocators.</p>
+      runtiime system with a number of memory allocators.</p>
   </description>
 
   <section>
     <title>Allocators</title>
     <marker id="allocators"></marker>
-    <p>Currently the following allocators are present:</p>
+    <p>The following allocators are present:</p>
+
     <taglist>
       <tag><c>temp_alloc</c></tag>
       <item>Allocator used for temporary allocations.</item>
       <tag><c>eheap_alloc</c></tag>
-      <item>Allocator used for Erlang heap data, such as Erlang process heaps.</item>
+      <item>Allocator used for Erlang heap data, such as Erlang process heaps.
+      </item>
       <tag><c>binary_alloc</c></tag>
       <item>Allocator used for Erlang binary data.</item>
       <tag><c>ets_alloc</c></tag>
-      <item>Allocator used for ETS data.</item>
+      <item>Allocator used for <c>ets</c> data.</item>
       <tag><c>driver_alloc</c></tag>
       <item>Allocator used for driver data.</item>
       <tag><c>literal_alloc</c></tag>
       <item>Allocator used for constant terms in Erlang code.</item>
       <tag><c>sl_alloc</c></tag>
       <item>Allocator used for memory blocks that are expected to be
-       short-lived.</item>
+        short-lived.</item>
       <tag><c>ll_alloc</c></tag>
       <item>Allocator used for memory blocks that are expected to be
-       long-lived, for example Erlang code.</item>
+        long-lived, for example, Erlang code.</item>
       <tag><c>fix_alloc</c></tag>
       <item>A fast allocator used for some frequently used
        fixed size data types.</item>
       <tag><c>exec_alloc</c></tag>
-      <item>Allocator used by hipe for native executable code
-      on specific architectures (x86_64).</item>
+      <item>Allocator used by the <seealso marker="hipe"><c>HiPE</c></seealso>
+        application for native executable code on specific architectures
+        (x86_64).</item>
       <tag><c>std_alloc</c></tag>
-      <item>Allocator used for most memory blocks not allocated via any of
-       the other allocators described above.</item>
+      <item>Allocator used for most memory blocks not allocated through any of
+        the other allocators described above.</item>
       <tag><c>sys_alloc</c></tag>
       <item>This is normally the default <c>malloc</c> implementation
-       used on the specific OS.</item>
+        used on the specific OS.</item>
       <tag><c>mseg_alloc</c></tag>
-      <item>A memory segment allocator. <c>mseg_alloc</c> is used by other
-       allocators for allocating memory segments and is currently only
-       available on systems that have the <c>mmap</c> system
-       call. Memory segments that are deallocated are kept for a
-       while in a segment cache before they are destroyed. When
-       segments are allocated, cached segments are used if possible
-       instead of creating new segments.  This in order to reduce
-       the number of system calls made.</item>
+      <item>A memory segment allocator. It is used by other
+        allocators for allocating memory segments and is only
+        available on systems that have the <c>mmap</c> system
+        call. Memory segments that are deallocated are kept for a
+        while in a segment cache before they are destroyed. When
+        segments are allocated, cached segments are used if possible
+        instead of creating new segments. This to reduce
+        the number of system calls made.</item>
     </taglist>
+
     <p><c>sys_alloc</c> and <c>literal_alloc</c> are always enabled and
       cannot be disabled. <c>exec_alloc</c> is only available if it is needed
       and cannot be disabled. <c>mseg_alloc</c> is always enabled if it is
@@ -90,9 +95,10 @@
       By default all allocators are enabled.
       When an allocator is disabled, <c>sys_alloc</c> is used instead of
       the disabled allocator.</p>
+
     <p>The main idea with the <c>erts_alloc</c> library is to separate
       memory blocks that are used differently into different memory
-      areas, and by this achieving less memory fragmentation. By
+      areas, to achieve less memory fragmentation. By
       putting less effort in finding a good fit for memory blocks that
       are frequently allocated than for those less frequently
       allocated, a performance gain can be achieved.</p>
@@ -100,61 +106,85 @@
 
   <section>
     <marker id="alloc_util"></marker>
-    <title>The alloc_util framework</title>
+    <title>The alloc_util Framework</title>
     <p>Internally a framework called <c>alloc_util</c> is used for
-      implementing allocators. <c>sys_alloc</c>, and
-      <c>mseg_alloc</c> do not use this framework; hence, the
+      implementing allocators. <c>sys_alloc</c> and
+      <c>mseg_alloc</c> do not use this framework, so the
       following does <em>not</em> apply to them.</p>
+
     <p>An allocator manages multiple areas, called carriers, in which
       memory blocks are placed. A carrier is either placed in a
-      separate memory segment (allocated via <c>mseg_alloc</c>), or in
-      the heap segment (allocated via <c>sys_alloc</c>). Multiblock
-      carriers are used for storage of several blocks. Singleblock
-      carriers are used for storage of one block. Blocks that are
-      larger than the value of the singleblock carrier threshold
-      (<seealso marker="#M_sbct">sbct</seealso>) parameter are placed
-      in singleblock carriers. Blocks that are smaller than the value
-      of the <c>sbct</c> parameter are placed in multiblock
-      carriers. Normally an allocator creates a "main multiblock
+      separate memory segment (allocated through <c>mseg_alloc</c>), or in
+      the heap segment (allocated through <c>sys_alloc</c>).</p>
+
+    <list type="bulleted">
+      <item>
+        <p>Multiblock carriers are used for storage of several blocks.</p>
+      </item>
+      <item>
+        <p>Singleblock carriers are used for storage of one block.</p>
+      </item>
+      <item>
+        <p>Blocks that are larger than the value of the singleblock carrier
+          threshold (<seealso marker="#M_sbct"><c>sbct</c></seealso>) parameter
+          are placed in singleblock carriers.</p>
+      </item>
+      <item>
+        <p>Blocks that are smaller than the value of parameter <c>sbct</c>
+          are placed in multiblock carriers.</p></item>
+    </list>
+
+    <p>Normally an allocator creates a "main multiblock
       carrier". Main multiblock carriers are never deallocated. The
-      size of the main multiblock carrier is determined by the value
-      of the <seealso marker="#M_mmbcs">mmbcs</seealso> parameter.</p>
+      size of the main multiblock carrier is determined by the value of
+      parameter <seealso marker="#M_mmbcs"><c>mmbcs</c></seealso>.</p>
+
     <p><marker id="mseg_mbc_sizes"></marker>Sizes of multiblock carriers
-      allocated via <c>mseg_alloc</c> are
-      decided based on the values of the largest multiblock carrier
-      size (<seealso marker="#M_lmbcs">lmbcs</seealso>), the smallest
-      multiblock carrier size (<seealso marker="#M_smbcs">smbcs</seealso>),
-      and the multiblock carrier growth stages
-      (<seealso marker="#M_mbcgs">mbcgs</seealso>) parameters. If
-      <c>nc</c> is the current number of multiblock carriers (the main
+      allocated through <c>mseg_alloc</c> are decided based on the
+      following parameters:</p>
+
+    <list type="bulleted">
+      <item>The values of the largest multiblock carrier size
+        (<seealso marker="#M_lmbcs"><c>lmbcs</c></seealso>)</item>
+      <item>The smallest multiblock carrier size
+        (<seealso marker="#M_smbcs"><c>smbcs</c></seealso>)</item>
+      <item>The multiblock carrier growth stages
+        (<seealso marker="#M_mbcgs"><c>mbcgs</c></seealso>)</item>
+    </list>
+
+    <p>If <c>nc</c> is the current number of multiblock carriers (the main
       multiblock carrier excluded) managed by an allocator, the size
       of the next <c>mseg_alloc</c> multiblock carrier allocated by
-      this allocator will roughly be
+      this allocator is roughly
       <c><![CDATA[smbcs+nc*(lmbcs-smbcs)/mbcgs]]></c> when
       <c><![CDATA[nc <= mbcgs]]></c>,
-      and <c>lmbcs</c> when <c><![CDATA[nc > mbcgs]]></c>. If the value of the
-      <c>sbct</c> parameter should be larger than the value of the
-      <c>lmbcs</c> parameter, the allocator may have to create
-      multiblock carriers that are larger than the value of the
-      <c>lmbcs</c> parameter, though.
-      Singleblock carriers allocated via <c>mseg_alloc</c> are sized
+      and <c>lmbcs</c> when <c><![CDATA[nc > mbcgs]]></c>. If the value of
+      parameter <c>sbct</c> is larger than the value of parameter
+      <c>lmbcs</c>, the allocator may have to create
+      multiblock carriers that are larger than the value of
+      parameter <c>lmbcs</c>, though.
+      Singleblock carriers allocated through <c>mseg_alloc</c> are sized
       to whole pages.</p>
-    <p>Sizes of carriers allocated via <c>sys_alloc</c> are
+
+    <p>Sizes of carriers allocated through <c>sys_alloc</c> are
       decided based on the value of the <c>sys_alloc</c> carrier size
-      (<seealso marker="#Muycs">ycs</seealso>) parameter. The size of
-      a carrier is the least number of multiples of the value of the
-      <c>ycs</c> parameter that satisfies the request.</p>
+      (<seealso marker="#Muycs"><c>ycs</c></seealso>) parameter. The size of
+      a carrier is the least number of multiples of the value of
+      parameter <c>ycs</c> satisfying the request.</p>
+
     <p>Coalescing of free blocks are always performed immediately.
-      Boundary tags (headers and footers) in free blocks are used
+      Boundary tags (headers and footers) in free blocks are used,
       which makes the time complexity for coalescing constant.</p>
+
     <p><marker id="strategy"></marker>The memory allocation strategy
-      used for multiblock carriers by an
-      allocator is configurable via the <seealso marker="#M_as">as</seealso>
-      parameter. Currently the following strategies are available:</p>
+      used for multiblock carriers by an allocator can be
+      configured using parameter <seealso marker="#M_as"><c>as</c></seealso>.
+      The following strategies are available:</p>
+
     <taglist>
       <tag>Best fit</tag>
       <item>
-        <p>Strategy: Find the smallest block that satisfies the
+        <p>Strategy: Find the smallest block satisfying the
           requested block size.</p>
         <p>Implementation: A balanced binary search tree is
           used. The time complexity is proportional to log N, where
@@ -162,7 +192,7 @@
       </item>
       <tag>Address order best fit</tag>
       <item>
-        <p>Strategy: Find the smallest block that satisfies the
+        <p>Strategy: Find the smallest block satisfying the
           requested block size. If multiple blocks are found, choose
           the one with the lowest address.</p>
         <p>Implementation: A balanced binary search tree is
@@ -171,7 +201,7 @@
       </item>
       <tag>Address order first fit</tag>
       <item>
-        <p>Strategy: Find the block with the lowest address that satisfies the
+        <p>Strategy: Find the block with the lowest address satisfying the
           requested block size.</p>
         <p>Implementation: A balanced binary search tree is
           used. The time complexity is proportional to log N, where
@@ -180,8 +210,8 @@
       <tag>Address order first fit carrier best fit</tag>
       <item>
         <p>Strategy: Find the <em>carrier</em> with the lowest address that
-	can satisfy the requested block size, then find a block within
-	that carrier using the "best fit" strategy.</p>
+          can satisfy the requested block size, then find a block within
+          that carrier using the "best fit" strategy.</p>
         <p>Implementation: Balanced binary search trees are
           used. The time complexity is proportional to log N, where
           N is the number of free blocks.</p>
@@ -189,8 +219,8 @@
       <tag>Address order first fit carrier address order best fit</tag>
       <item>
         <p>Strategy: Find the <em>carrier</em> with the lowest address that
-	can satisfy the requested block size, then find a block within
-	that carrier using the "adress order best fit" strategy.</p>
+          can satisfy the requested block size, then find a block within
+          that carrier using the "address order best fit" strategy.</p>
         <p>Implementation: Balanced binary search trees are
           used. The time complexity is proportional to log N, where
           N is the number of free blocks.</p>
@@ -200,12 +230,12 @@
         <p>Strategy: Try to find the best fit, but settle for the best fit
           found during a limited search.</p>
         <p>Implementation: The implementation uses segregated free
-          lists with a maximum block search depth (in each list) in
-          order to find a good fit fast. When the maximum block
-          search depth is small (by default 3) this implementation
+          lists with a maximum block search depth (in each list)
+          to find a good fit fast. When the maximum block
+          search depth is small (by default 3), this implementation
           has a time complexity that is constant. The maximum block
-          search depth is configurable via the
-          <seealso marker="#M_mbsd">mbsd</seealso> parameter.</p>
+          search depth can be configured using parameter
+          <seealso marker="#M_mbsd"><c>mbsd</c></seealso>.</p>
       </item>
       <tag>A fit</tag>
       <item>
@@ -213,43 +243,47 @@
           block to see if it satisfies the request. This strategy is
           only intended to be used for temporary allocations.</p>
         <p>Implementation: Inspect the first block in a free-list.
-          If it satisfies the request, it is used; otherwise, a new
+          If it satisfies the request, it is used, otherwise a new
           carrier is created. The implementation has a time
           complexity that is constant.</p>
-	<p>As of erts version 5.6.1 the emulator will refuse to
-	  use this strategy on other allocators than <c>temp_alloc</c>.
-	  This since it will only cause problems for other allocators.</p>
+        <p>As from <c>ERTS</c> 5.6.1 the emulator refuses to
+          use this strategy on other allocators than <c>temp_alloc</c>.
+          This because it only causes problems for other allocators.</p>
       </item>
     </taglist>
-    <p>Apart from the ordinary allocators described above a number of
-       pre-allocators are used for some specific data types. These
-       pre-allocators pre-allocate a fixed amount of memory for certain data
-       types when the run-time system starts. As long as pre-allocated memory
-       is available, it will be used. When no pre-allocated memory is
-       available, memory will be allocated in ordinary allocators. These
-       pre-allocators are typically much faster than the ordinary allocators,
-       but can only satisfy a limited amount of requests.</p>
+
+    <p>Apart from the ordinary allocators described above, some
+      pre-allocators are used for some specific data types. These
+      pre-allocators pre-allocate a fixed amount of memory for certain data
+      types when the runtime system starts. As long as pre-allocated memory
+      is available, it is used. When no pre-allocated memory is
+      available, memory is allocated in ordinary allocators. These
+      pre-allocators are typically much faster than the ordinary allocators,
+      but can only satisfy a limited number of requests.</p>
   </section>
 
   <section>
     <marker id="flags"></marker>
     <title>System Flags Effecting erts_alloc</title>
     <warning>
-      <p>Only use these flags if you are absolutely sure what you are
-        doing. Unsuitable settings may cause serious performance
+      <p>Only use these flags if you are sure what you are
+        doing. Unsuitable settings can cause serious performance
         degradation and even a system crash at any time during
         operation.</p>
     </warning>
+
     <p>Memory allocator system flags have the following syntax:
-      <c><![CDATA[+M<S><P> <V>]]></c>
+      <c><![CDATA[+M<S><P> <V>]]></c>,
       where <c><![CDATA[<S>]]></c> is a letter identifying a subsystem,
       <c><![CDATA[<P>]]></c> is a parameter, and <c><![CDATA[<V>]]></c> is the
       value to use. The flags can be passed to the Erlang emulator
-      (<seealso marker="erl">erl</seealso>) as command line
+      (<seealso marker="erl"><c>erl(1)</c></seealso>) as command-line
       arguments.</p>
-    <p>System flags effecting specific allocators have an upper-case
+
+    <p>System flags effecting specific allocators have an uppercase
       letter as <c><![CDATA[<S>]]></c>. The following letters are used for
-      the currently present allocators:</p>
+      the allocators:</p>
+
     <list type="bulleted">
       <item><c>B: binary_alloc</c></item>
       <item><c>D: std_alloc</c></item>
@@ -265,421 +299,516 @@
       <item><c>X: exec_alloc</c></item>
       <item><c>Y: sys_alloc</c></item>
     </list>
-    <p>The following flags are available for configuration of
-      <c>mseg_alloc</c>:</p>
-    <taglist>
-      <tag><marker id="MMamcbf"/><c><![CDATA[+MMamcbf <size>]]></c></tag>
-      <item>
-       Absolute max cache bad fit (in kilobytes). A segment in the
-       memory segment cache is not reused if its size exceeds the
-       requested size with more than the value of this
-       parameter. Default value is 4096. </item>
-      <tag><marker id="MMrmcbf"/><c><![CDATA[+MMrmcbf <ratio>]]></c></tag>
-      <item>
-       Relative max cache bad fit (in percent). A segment in the
-       memory segment cache is not reused if its size exceeds the
-       requested size with more than relative max cache bad fit
-       percent of the requested size. Default value is 20.</item>
-      <tag><marker id="MMsco"/><c><![CDATA[+MMsco true|false]]></c></tag>
-      <item>
-	Set <seealso marker="#MMscs">super carrier</seealso> only flag. This
-	flag defaults to <c>true</c>. When a super carrier is used and this
-	flag is <c>true</c>, <c>mseg_alloc</c> will only create carriers
-	in the super carrier. Note that the <c>alloc_util</c> framework may
-	create <c>sys_alloc</c> carriers, so if you want all carriers to
-	be created in the super carrier, you therefore want to disable use
-	of <c>sys_alloc</c> carriers by also passing
-	<seealso marker="#Musac"><c>+Musac false</c></seealso>. When the flag
-	is <c>false</c>, <c>mseg_alloc</c> will try to create carriers outside
-	of the super carrier when the super carrier is full.
-	<br/><br/>
-	<em>NOTE</em>: Setting this flag to <c>false</c> may not be supported
-	on all systems. This flag will in that case be ignored.
-	<br/><br/>
-	<em>NOTE</em>: The super carrier cannot be enabled nor
-	disabled on halfword heap systems. This flag will be
-	ignored on halfword heap systems.
-      </item>
-      <tag><marker id="MMscrfsd"/><c><![CDATA[+MMscrfsd <amount>]]></c></tag>
-      <item>
-	Set <seealso marker="#MMscs">super carrier</seealso> reserved
-	free segment descriptors. This parameter defaults to <c>65536</c>.
-	This parameter determines the amount of memory to reserve for
-	free segment descriptors used by the super carrier. If the system
-	runs out of reserved memory for free segment descriptors, other
-	memory will be used. This may however cause fragmentation issues,
-	so you want to ensure that this	never happens. The maximum amount
-	of free segment descriptors used can be retrieved from the
-	<c>erts_mmap</c> tuple part of the result from calling
-	<seealso marker="erts:erlang#system_info_allocator_tuple">erlang:system_info({allocator, mseg_alloc})</seealso>.
-      </item>
-      <tag><marker id="MMscrpm"/><c><![CDATA[+MMscrpm true|false]]></c></tag>
-      <item>
-	Set <seealso marker="#MMscs">super carrier</seealso> reserve physical
-	memory flag. This flag defaults	to <c>true</c>. When this flag is
-	<c>true</c>, physical memory will be reserved for the whole super
-	carrier at once when it is created. The reservation will after that
-	be left unchanged. When this flag is set to <c>false</c> only virtual
-	address space will be reserved for the super carrier upon creation.
-	The system will attempt to reserve physical memory upon carrier
-	creations in the super carrier, and attempt to unreserve physical
-	memory upon carrier destructions in the super carrier.
-	<br/><br/>
-	<em>NOTE</em>: What reservation of physical memory actually means
-	highly depends on the operating system, and how it is configured. For
-	example, different memory overcommit settings on Linux drastically
-	change the behaviour. Also note, setting this flag to <c>false</c>
-	may not be supported on all systems. This flag will in that case
-	be ignored.
-	<br/><br/>
-	<em>NOTE</em>: The super carrier cannot be enabled nor
-	disabled on halfword heap systems. This flag will be
-	ignored on halfword heap systems.
-      </item>
-      <tag><marker id="MMscs"/><c><![CDATA[+MMscs <size in MB>]]></c></tag>
-      <item>
-	Set super carrier size (in MB). The super carrier size defaults to
-	zero; i.e, the super carrier is by default disabled. The super
-	carrier is a large continuous area in the virtual address space.
-	<c>mseg_alloc</c> will always try to create new carriers in the super
-	carrier if it exists. Note that the <c>alloc_util</c> framework may
-	create <c>sys_alloc</c> carriers. For more information on this, see the
-	documentation of the <seealso marker="#MMsco"><c>+MMsco</c></seealso>
-	flag.
-	<br/><br/>
-	<em>NOTE</em>: The super carrier cannot be enabled nor
-	disabled on halfword heap systems. This flag will be
-	ignored on halfword heap systems.
-      </item>
-      <tag><marker id="MMmcs"/><c><![CDATA[+MMmcs <amount>]]></c></tag>
-      <item>
-       Max cached segments. The maximum number of memory segments
-       stored in the memory segment cache. Valid range is
-       0-30. Default value is 10.</item>
-    </taglist>
-    <p>The following flags are available for configuration of
-      <c>sys_alloc</c>:</p>
-    <taglist>
-      <tag><marker id="MYe"/><c>+MYe true</c></tag>
-      <item>
-       Enable <c>sys_alloc</c>. Note: <c>sys_alloc</c> cannot be disabled.</item>
-      <tag><marker id="MYm"/><c>+MYm libc</c></tag>
-      <item>
-      <c>malloc</c> library to use. Currently only
-      <c>libc</c> is available. <c>libc</c> enables the standard
-      <c>libc</c> malloc implementation. By default <c>libc</c> is used.</item>
-      <tag><marker id="MYtt"/><c><![CDATA[+MYtt <size>]]></c></tag>
-      <item>
-       Trim threshold size (in kilobytes). This is the maximum amount
-       of free memory at the top of the heap (allocated by
-      <c>sbrk</c>) that will be kept by <c>malloc</c> (not
-       released to the operating system). When the amount of free
-       memory at the top of the heap exceeds the trim threshold,
-      <c>malloc</c> will release it (by calling
-      <c>sbrk</c>). Trim threshold is given in kilobytes. Default
-       trim threshold is 128. <em>Note:</em> This flag will
-       only have any effect when the emulator has been linked with
-       the GNU C library, and uses its <c>malloc</c> implementation.</item>
-      <tag><marker id="MYtp"/><c><![CDATA[+MYtp <size>]]></c></tag>
-      <item>
-       Top pad size (in kilobytes). This is the amount of extra
-       memory that will be allocated by <c>malloc</c> when
-      <c>sbrk</c> is called to get more memory from the operating
-       system. Default top pad size is 0. <em>Note:</em> This flag
-       will only have any effect when the emulator has been linked
-       with the GNU C library, and uses its <c>malloc</c>
-       implementation.</item>
-    </taglist>
-    <p>The following flags are available for configuration of allocators
-       based on <c>alloc_util</c>. If <c>u</c> is used as subsystem
-       identifier (i.e., <c><![CDATA[<S> = u]]></c>) all allocators based on
-       <c>alloc_util</c> will be effected. If <c>B</c>, <c>D</c>, <c>E</c>,
-        <c>F</c>, <c>H</c>, <c>L</c>, <c>R</c>, <c>S</c>, or <c>T</c> is used as
-       subsystem identifier, only the specific allocator identified will be
-       effected:</p>
-    <taglist>
-      <tag><marker id="M_acul"/><c><![CDATA[+M<S>acul <utilization>|de]]></c></tag>
-      <item>
-	Abandon carrier utilization limit. A valid
-	<c><![CDATA[<utilization>]]></c> is an integer in the range
-	<c>[0, 100]</c> representing utilization in percent. When a
-	utilization value larger than zero is used, allocator instances
-	are allowed to abandon multiblock carriers. If <c>de</c> (default
-	enabled) is passed instead of a <c><![CDATA[<utilization>]]></c>,
-	a recomended non zero utilization value will be used. The actual
-	value chosen depend on allocator type and may be changed between
-	ERTS versions. Currently the default equals <c>de</c>, but this
-	may be changed in the future. Carriers will be abandoned when
-	memory utilization in the allocator instance falls below the
-	utilization value used. Once a carrier has been abandoned, no new
-	allocations will be made in it. When an allocator instance gets an
-	increased multiblock carrier need, it will first try to fetch an
-	abandoned carrier from an allocator instances of the same
-	allocator type. If no abandoned carrier could be fetched, it will
-	create a new empty carrier. When an abandoned carrier has been
-	fetched it will function as an ordinary carrier. This feature has
-	special requirements on the
-	<seealso marker="#M_as">allocation strategy</seealso> used. Currently
-	only the strategies <c>aoff</c>, <c>aoffcbf</c> and <c>aoffcaobf</c> support
-	abandoned carriers. This feature also requires
-	<seealso marker="#M_t">multiple thread specific instances</seealso>
-	to be enabled. When enabling this feature, multiple thread specific
-	instances will be enabled if not already enabled, and the
-	<c>aoffcbf</c> strategy will be enabled if current strategy does not
-	support abandoned carriers. This feature can be enabled on all
-	allocators based on the <c>alloc_util</c> framework with the
-	exception of <c>temp_alloc</c> (which would be pointless).
-      </item>
-      <tag><marker id="M_as"/><c><![CDATA[+M<S>as bf|aobf|aoff|aoffcbf|aoffcaobf|gf|af]]></c></tag>
-      <item>
-       Allocation strategy. Valid strategies are <c>bf</c> (best fit),
-      <c>aobf</c> (address order best fit), <c>aoff</c> (address order first fit),
-      <c>aoffcbf</c> (address order first fit carrier best fit),
-      <c>aoffcaobf</c> (address order first fit carrier address order best fit),
-      <c>gf</c> (good fit), and <c>af</c> (a fit). See 
-      <seealso marker="#strategy">the description of allocation strategies</seealso> in "the <c>alloc_util</c> framework" section.</item>
-      <tag><marker id="M_asbcst"/><c><![CDATA[+M<S>asbcst <size>]]></c></tag>
-      <item>
-       Absolute singleblock carrier shrink threshold (in
-       kilobytes). When a block located in an
-      <c>mseg_alloc</c> singleblock carrier is shrunk, the carrier
-       will be left unchanged if the amount of unused memory is less
-       than this threshold; otherwise, the carrier will be shrunk.
-       See also <seealso marker="#M_rsbcst">rsbcst</seealso>.</item>
-      <tag><marker id="M_e"/><c><![CDATA[+M<S>e true|false]]></c></tag>
-      <item>
-       Enable allocator <c><![CDATA[<S>]]></c>.</item>
-      <tag><marker id="M_lmbcs"/><c><![CDATA[+M<S>lmbcs <size>]]></c></tag>
-      <item>
-       Largest (<c>mseg_alloc</c>) multiblock carrier size (in
-       kilobytes).  See <seealso marker="#mseg_mbc_sizes">the description
-       on how sizes for mseg_alloc multiblock carriers are decided</seealso>
-       in "the <c>alloc_util</c> framework" section. On 32-bit Unix style OS
-       this limit can not be set higher than 128 megabyte.</item>
-      <tag><marker id="M_mbcgs"/><c><![CDATA[+M<S>mbcgs <ratio>]]></c></tag>
-      <item>
-       (<c>mseg_alloc</c>) multiblock carrier growth stages. See
-      <seealso marker="#mseg_mbc_sizes">the description on how sizes for
-       mseg_alloc multiblock carriers are decided</seealso>
-       in "the <c>alloc_util</c> framework" section.</item>
-      <tag><marker id="M_mbsd"/><c><![CDATA[+M<S>mbsd <depth>]]></c></tag>
-      <item>
-       Max block search depth. This flag has effect only if the
-       good fit strategy has been selected for allocator
-      <c><![CDATA[<S>]]></c>. When the good fit strategy is used, free
-       blocks are placed in segregated free-lists. Each free list
-       contains blocks of sizes in a specific range. The max block
-       search depth sets a limit on the maximum number of blocks to
-       inspect in a free list during a search for suitable block
-       satisfying the request.</item>
-      <tag><marker id="M_mmbcs"/><c><![CDATA[+M<S>mmbcs <size>]]></c></tag>
-      <item>
-       Main multiblock carrier size. Sets the size of the main
-       multiblock carrier for allocator <c><![CDATA[<S>]]></c>. The main
-       multiblock carrier is allocated via <c><![CDATA[sys_alloc]]></c> and is
-       never deallocated.</item>
-      <tag><marker id="M_mmmbc"/><c><![CDATA[+M<S>mmmbc <amount>]]></c></tag>
-      <item>
-       Max <c>mseg_alloc</c> multiblock carriers. Maximum number of
-       multiblock carriers allocated via <c>mseg_alloc</c> by
-       allocator <c><![CDATA[<S>]]></c>. When this limit has been reached,
-       new multiblock carriers will be allocated via
-      <c>sys_alloc</c>.</item>
-      <tag><marker id="M_mmsbc"/><c><![CDATA[+M<S>mmsbc <amount>]]></c></tag>
-      <item>
-       Max <c>mseg_alloc</c> singleblock carriers. Maximum number of
-       singleblock carriers allocated via <c>mseg_alloc</c> by
-       allocator <c><![CDATA[<S>]]></c>. When this limit has been reached,
-       new singleblock carriers will be allocated via
-      <c>sys_alloc</c>.</item>
-      <tag><marker id="M_ramv"/><c><![CDATA[+M<S>ramv <bool>]]></c></tag>
-      <item>
-       Realloc always moves. When enabled, reallocate operations will
-       more or less be translated into an allocate, copy, free sequence.
-       This often reduce memory fragmentation, but costs performance.
-      </item>
-      <tag><marker id="M_rmbcmt"/><c><![CDATA[+M<S>rmbcmt <ratio>]]></c></tag>
-      <item>
-       Relative multiblock carrier move threshold (in percent). When
-       a block located in a multiblock carrier is shrunk,
-       the block will be moved if the ratio of the size of the returned
-       memory compared to the previous size is more than this threshold;
-       otherwise, the block will be shrunk at current location.</item>
-      <tag><marker id="M_rsbcmt"/><c><![CDATA[+M<S>rsbcmt <ratio>]]></c></tag>
-      <item>
-       Relative singleblock carrier move threshold (in percent). When
-       a block located in a singleblock carrier is shrunk to
-       a size smaller than the value of the
-      <seealso marker="#M_sbct">sbct</seealso> parameter,
-       the block will be left unchanged in the singleblock carrier if
-       the ratio of unused memory is less than this threshold;
-       otherwise, it will be moved into a multiblock carrier. </item>
-      <tag><marker id="M_rsbcst"/><c><![CDATA[+M<S>rsbcst <ratio>]]></c></tag>
-      <item>
-       Relative singleblock carrier shrink threshold (in
-       percent). When a block located in an <c>mseg_alloc</c>
-       singleblock carrier is shrunk, the carrier will be left
-       unchanged if the ratio of unused memory is less than this
-       threshold; otherwise, the carrier will be shrunk.
-       See also <seealso marker="#M_asbcst">asbcst</seealso>.</item>
-      <tag><marker id="M_sbct"/><c><![CDATA[+M<S>sbct <size>]]></c></tag>
-      <item>
-       Singleblock carrier threshold. Blocks larger than this
-       threshold will be placed in singleblock carriers. Blocks
-       smaller than this threshold will be placed in multiblock
-       carriers. On 32-bit Unix style OS this threshold can not be set higher
-       than 8 megabytes.</item>
-      <tag><marker id="M_smbcs"/><c><![CDATA[+M<S>smbcs <size>]]></c></tag>
-      <item>
-       Smallest (<c>mseg_alloc</c>) multiblock carrier size (in
-       kilobytes). See <seealso marker="#mseg_mbc_sizes">the description
-       on how sizes for mseg_alloc multiblock carriers are decided</seealso>
-       in "the <c>alloc_util</c> framework" section.</item>
-      <tag><marker id="M_t"/><c><![CDATA[+M<S>t true|false]]></c></tag>
-      <item>
-       <p>Multiple, thread specific instances of the allocator.
-       This option will only have any effect on the runtime system
-       with SMP support. Default behaviour on the runtime system with
-       SMP support is <c>NoSchedulers+1</c> instances. Each scheduler will use
-       a lock-free instance of its own and other threads will use
-       a common instance.</p>
-       <p>It was previously (before ERTS version 5.9) possible to configure
-       a smaller amount of thread specific instances than schedulers.
-       This is, however, not possible any more.</p>
-      </item>
-    </taglist>
-    <p>Currently the following flags are available for configuration of
-      <c>alloc_util</c>, i.e. all allocators based on <c>alloc_util</c>
-      will be effected:</p>
-    <taglist>
-      <tag><marker id="Muycs"/><c><![CDATA[+Muycs <size>]]></c></tag>
-      <item>
-      <c>sys_alloc</c> carrier size. Carriers allocated via
-      <c>sys_alloc</c> will be allocated in sizes which are
-       multiples of the <c>sys_alloc</c> carrier size. This is not
-       true for main multiblock carriers and carriers allocated
-       during a memory shortage, though.</item>
-      <tag><marker id="Mummc"/><c><![CDATA[+Mummc <amount>]]></c></tag>
-      <item>
-       Max <c>mseg_alloc</c> carriers. Maximum number of carriers
-       placed in separate memory segments. When this limit has been
-       reached, new carriers will be placed in memory retrieved from
-      <c>sys_alloc</c>.</item>
-      <tag><marker id="Musac"/><c><![CDATA[+Musac <bool>]]></c></tag>
-      <item>
-	Allow <c>sys_alloc</c> carriers. By default <c>true</c>. If
-	set to <c>false</c>, <c>sys_alloc</c> carriers will never be
-	created by allocators using the <c>alloc_util</c> framework.</item>
-    </taglist>
-    <p>The following flag is special for <c>literal_alloc</c>:</p>
-    <taglist>
-      <tag><marker id="MIscs"/><c><![CDATA[+MIscs <size in MB>]]></c></tag>
-      <item>
-      <c>literal_alloc</c> super carrier size (in MB). The amount of
-      <em>virtual</em> address space reserved for literal terms in
-      Erlang code on 64-bit architectures. The default is 1024 (1GB)
-      and is usually sufficient. The flag is ignored on 32-bit
-      architectures.</item>
-    </taglist>
-    <p>The following flag is special for <c>exec_alloc</c>:</p>
-    <taglist>
-      <tag><marker id="MXscs"/><c><![CDATA[+MXscs <size in MB>]]></c></tag>
-      <item>
-      <c>exec_alloc</c> super carrier size (in MB). The amount of
-      <em>virtual</em> address space reserved for native executable code
-      used by hipe on specific architectures (x86_64). The default is 512 MB.
-      </item>
-    </taglist>
-    <p>Instrumentation flags:</p>
-    <taglist>
-      <tag><marker id="Mim"/><c>+Mim true|false</c></tag>
-      <item>
-       A map over current allocations is kept by the emulator. The
-       allocation map can be retrieved via the <c>instrument</c>
-       module. <c>+Mim true</c> implies <c>+Mis true</c>.
-      <c>+Mim true</c> is the same as
-      <seealso marker="erl#instr">-instr</seealso>.</item>
-      <tag><marker id="Mis"/><c>+Mis true|false</c></tag>
-      <item>
-       Status over allocated memory is kept by the emulator. The
-       allocation status can be retrieved via the <c>instrument</c>
-       module.</item>
-      <tag><marker id="Mit"/><c>+Mit X</c></tag>
-      <item>
-       Reserved for future use. Do <em>not</em> use this flag.</item>
-    </taglist>
-    <note>
-      <p>When instrumentation of the emulator is enabled, the emulator
-        uses more memory and runs slower.</p>
-    </note>
-    <p>Other flags:</p>
-    <taglist>
-      <tag><marker id="Mea"/><c>+Mea min|max|r9c|r10b|r11b|config</c></tag>
-      <item>
+
+    <section>
+      <title>Flags for Configuration of mseg_alloc</title>
+      <taglist>
+        <tag><marker id="MMamcbf"/><c><![CDATA[+MMamcbf <size>]]></c></tag>
+        <item>
+          <p>Absolute maximum cache bad fit (in kilobytes). A segment in the
+            memory segment cache is not reused if its size exceeds the
+            requested size with more than the value of this
+            parameter. Defaults to <c>4096</c>.</p>
+        </item>
+        <tag><marker id="MMrmcbf"/><c><![CDATA[+MMrmcbf <ratio>]]></c></tag>
+        <item>
+          <p>Relative maximum cache bad fit (in percent). A segment in the
+            memory segment cache is not reused if its size exceeds the
+            requested size with more than relative maximum cache bad fit
+            percent of the requested size. Defaults to <c>20</c>.</p>
+        </item>
+        <tag><marker id="MMsco"/><c><![CDATA[+MMsco true|false]]></c></tag>
+        <item>
+          <p>Sets <seealso marker="#MMscs">super carrier</seealso> only flag.
+            Defaults to <c>true</c>. When a super carrier is used and this
+            flag is <c>true</c>, <c>mseg_alloc</c> only creates carriers in
+            the super carrier. Notice that the <c>alloc_util</c> framework can
+            create <c>sys_alloc</c> carriers, so if you want all carriers to
+            be created in the super carrier, you therefore want to disable use
+            of <c>sys_alloc</c> carriers by also passing
+            <seealso marker="#Musac"><c>+Musac false</c></seealso>. When
+            the flag is <c>false</c>, <c>mseg_alloc</c> tries to create carriers
+            outside of the super carrier when the super carrier is full.</p>
+	  <note>
+            <p>Setting this flag to <c>false</c> is possibly not supported
+              on all systems. The flag is then ignored.</p>
+          </note>
+          <note>
+            <p>The super carrier cannot be enabled or
+              disabled on halfword heap systems. This flag is
+              ignored on halfword heap systems.</p>
+          </note>
+        </item>
+        <tag><marker id="MMscrfsd"/><c><![CDATA[+MMscrfsd <amount>]]></c></tag>
+        <item>
+          <p>Sets <seealso marker="#MMscs">super carrier</seealso> reserved
+            free segment descriptors. Defaults to <c>65536</c>.
+            This parameter determines the amount of memory to reserve for
+            free segment descriptors used by the super carrier. If the system
+            runs out of reserved memory for free segment descriptors, other
+            memory is used. This can however cause fragmentation issues,
+            so you want to ensure that this never happens. The maximum amount
+            of free segment descriptors used can be retrieved from the
+            <c>erts_mmap</c> tuple part of the result from calling
+            <seealso marker="erts:erlang#system_info_allocator_tuple">
+            <c>erlang:system_info({allocator, mseg_alloc})</c></seealso>.</p>
+        </item>
+        <tag><marker id="MMscrpm"/><c><![CDATA[+MMscrpm true|false]]></c></tag>
+        <item>
+          <p>Sets <seealso marker="#MMscs">super carrier</seealso> reserve
+            physical memory flag. Defaults to <c>true</c>. When this flag is
+            <c>true</c>, physical memory is reserved for the whole super
+            carrier at once when it is created. The reservation is after that
+            left unchanged. When this flag is set to <c>false</c>, only virtual
+            address space is reserved for the super carrier upon creation.
+            The system attempts to reserve physical memory upon carrier
+            creations in the super carrier, and attempt to unreserve physical
+            memory upon carrier destructions in the super carrier.</p>
+          <note>
+            <p>What reservation of physical memory means, highly
+              depends on the operating system, and how it is configured. For
+              example, different memory overcommit settings on Linux drastically
+              change the behavior.</p>
+            <p>Setting this flag to <c>false</c> is possibly not supported on
+              all systems. The flag is then ignored.</p>
+          </note>
+          <note>
+            <p>The super carrier cannot be enabled or
+              disabled on halfword heap systems. This flag is
+              ignored on halfword heap systems.</p>
+          </note>
+        </item>
+        <tag><marker id="MMscs"/><c><![CDATA[+MMscs <size in MB>]]></c></tag>
+        <item>
+          <p>Sets super carrier size (in MB). Defaults to <c>0</c>, that is,
+            the super carrier is by default disabled. The super
+            carrier is a large continuous area in the virtual address space.
+            <c>mseg_alloc</c> always tries to create new carriers in the super
+            carrier if it exists. Notice that the <c>alloc_util</c> framework
+            can create <c>sys_alloc</c> carriers. For more information, see
+            <seealso marker="#MMsco"><c>+MMsco</c></seealso>.</p>
+          <note>
+            <p>The super carrier cannot be enabled or
+              disabled on halfword heap systems. This flag is
+              ignored on halfword heap systems.</p>
+          </note>
+        </item>
+        <tag><marker id="MMmcs"/><c><![CDATA[+MMmcs <amount>]]></c></tag>
+        <item>
+          <p>Maximum cached segments. The maximum number of memory segments
+            stored in the memory segment cache. Valid range is <c>[0, 30]</c>.
+            Defaults to <c>10</c>.</p>
+        </item>
+      </taglist>
+    </section>
+
+    <section>
+      <title>Flags for Configuration of sys_alloc</title>
+      <taglist>
+        <tag><marker id="MYe"/><c>+MYe true</c></tag>
+        <item>
+          <p>Enables <c>sys_alloc</c>.</p>
+          <note>
+            <p><c>sys_alloc</c> cannot be disabled.</p>
+          </note>
+        </item>
+        <tag><marker id="MYm"/><c>+MYm libc</c></tag>
+        <item>
+          <p><c>malloc</c> library to use. Only
+            <c>libc</c> is available. <c>libc</c> enables the standard
+            <c>libc</c> <c>malloc</c> implementation. By default <c>libc</c>
+            is used.</p>
+        </item>
+        <tag><marker id="MYtt"/><c><![CDATA[+MYtt <size>]]></c></tag>
+        <item>
+          <p>Trim threshold size (in kilobytes). This is the maximum amount
+            of free memory at the top of the heap (allocated by
+            <c>sbrk</c>) that is kept by <c>malloc</c> (not
+            released to the operating system). When the amount of free
+            memory at the top of the heap exceeds the trim threshold,
+            <c>malloc</c> releases it (by calling <c>sbrk</c>).
+            Trim threshold is specified in kilobytes.
+            Defaults to <c>128</c>.</p>
+          <note>
+            <p>This flag has effect only when the emulator is linked with
+              the GNU C library, and uses its <c>malloc</c> implementation.</p>
+          </note>
+        </item>
+        <tag><marker id="MYtp"/><c><![CDATA[+MYtp <size>]]></c></tag>
+        <item>
+          <p>Top pad size (in kilobytes). This is the amount of extra
+            memory that is allocated by <c>malloc</c> when
+            <c>sbrk</c> is called to get more memory from the operating
+            system. Defaults to <c>0</c>.</p>
+          <note>
+            <p>This flag has effect only when the emulator is linked with
+              the GNU C library, and uses its <c>malloc</c> implementation.</p>
+          </note>
+        </item>
+      </taglist>
+    </section>
+
+    <section>
+      <title>Flags for Configuration of Allocators Based on alloc_util</title>
+      <p>If <c>u</c> is used as subsystem identifier (that is,
+        <c><![CDATA[<S> = u]]></c>), all allocators based on
+        <c>alloc_util</c> are effected. If <c>B</c>, <c>D</c>, <c>E</c>,
+        <c>F</c>, <c>H</c>, <c>L</c>, <c>R</c>, <c>S</c>, or <c>T</c> is used
+        as subsystem identifier, only the specific allocator identifier is
+        effected.</p>
+
+      <taglist>
+        <tag><marker id="M_acul"/><c><![CDATA[+M<S>acul <utilization>|de]]></c>
+        </tag>
+        <item>
+          <p>Abandon carrier utilization limit. A valid
+            <c><![CDATA[<utilization>]]></c> is an integer in the range
+            <c>[0, 100]</c> representing utilization in percent. When a
+            utilization value &gt; 0 is used, allocator instances
+            are allowed to abandon multiblock carriers. If <c>de</c> (default
+            enabled) is passed instead of a <c><![CDATA[<utilization>]]></c>,
+            a recomended non-zero utilization value is used. The value
+            chosen depends on the allocator type and can be changed between
+            <c>ERTS</c> versions. Defaults to <c>de</c>, but this
+            can be changed in the future.</p>
+          <p>Carriers are abandoned when
+            memory utilization in the allocator instance falls below the
+            utilization value used. Once a carrier is abandoned, no new
+            allocations are made in it. When an allocator instance gets an
+            increased multiblock carrier need, it first tries to fetch an
+            abandoned carrier from an allocator instances of the same
+            allocator type. If no abandoned carrier can be fetched, it
+            creates a new empty carrier. When an abandoned carrier has been
+            fetched, it will function as an ordinary carrier. This feature has
+            special requirements on the
+            <seealso marker="#M_as">allocation strategy</seealso> used. Only
+            the strategies <c>aoff</c>, <c>aoffcbf</c>, and <c>aoffcaobf</c>
+            support abandoned carriers.</p>
+          <p>This feature also requires
+            <seealso marker="#M_t">multiple thread specific instances</seealso>
+            to be enabled. When enabling this feature, multiple thread-specific
+            instances are enabled if not already enabled, and the
+            <c>aoffcbf</c> strategy is enabled if the current strategy does not
+            support abandoned carriers. This feature can be enabled on all
+            allocators based on the <c>alloc_util</c> framework, except
+            <c>temp_alloc</c> (which would be pointless).</p>
+        </item>
+        <tag><marker id="M_as"/>
+          <c><![CDATA[+M<S>as bf|aobf|aoff|aoffcbf|aoffcaobf|gf|af]]></c></tag>
+        <item>
+          <p>Allocation strategy. The following strategies are valid:</p>
+          <list type="bulleted">
+            <item><c>bf</c> (best fit)</item>
+            <item><c>aobf</c> (address order best fit)</item>
+            <item><c>aoff</c> (address order first fit)</item>
+            <item><c>aoffcbf</c> (address order first fit carrier best fit)
+            </item>
+            <item><c>aoffcaobf</c> (address order first fit carrier address
+              order best fit)</item>
+            <item><c>gf</c> (good fit)</item>
+            <item><c>af</c> (a fit)</item>
+          </list>
+          <p>See the description of allocation strategies in section
+             <seealso marker="#strategy">The alloc_util Framework</seealso>.</p>
+        </item>
+        <tag><marker id="M_asbcst"/><c><![CDATA[+M<S>asbcst <size>]]></c></tag>
+        <item>
+          <p>Absolute singleblock carrier shrink threshold (in
+            kilobytes). When a block located in an
+            <c>mseg_alloc</c> singleblock carrier is shrunk, the carrier
+            is left unchanged if the amount of unused memory is less
+            than this threshold, otherwise the carrier is shrunk.
+            See also <seealso marker="#M_rsbcst"><c>rsbcst</c></seealso>.</p>
+        </item>
+        <tag><marker id="M_e"/><c><![CDATA[+M<S>e true|false]]></c></tag>
+        <item>
+          <p>Enables allocator <c><![CDATA[<S>]]></c>.</p>
+        </item>
+        <tag><marker id="M_lmbcs"/><c><![CDATA[+M<S>lmbcs <size>]]></c></tag>
+        <item>
+          <p>Largest (<c>mseg_alloc</c>) multiblock carrier size (in kilobytes).
+            See the description on how sizes for <c>mseg_alloc</c> multiblock
+            carriers are decided in section
+            <seealso marker="#mseg_mbc_sizes">
+            The alloc_util Framework</seealso>. On
+            32-bit Unix style OS this limit cannot be set &gt; 128 MB.</p>
+        </item>
+        <tag><marker id="M_mbcgs"/><c><![CDATA[+M<S>mbcgs <ratio>]]></c></tag>
+        <item>
+          <p>(<c>mseg_alloc</c>) multiblock carrier growth stages.
+            See the description on how sizes for <c>mseg_alloc</c> multiblock
+            carriers are decided in section
+            <seealso marker="#mseg_mbc_sizes">
+            The alloc_util Framework</seealso>.</p>
+        </item>
+        <tag><marker id="M_mbsd"/><c><![CDATA[+M<S>mbsd <depth>]]></c></tag>
+        <item>
+          <p>Maximum block search depth. This flag has effect only if the
+            good fit strategy is selected for allocator
+            <c><![CDATA[<S>]]></c>. When the good fit strategy is used, free
+            blocks are placed in segregated free-lists. Each free-list
+            contains blocks of sizes in a specific range. The maxiumum block
+            search depth sets a limit on the maximum number of blocks to
+            inspect in a free-list during a search for suitable block
+            satisfying the request.</p>
+        </item>
+        <tag><marker id="M_mmbcs"/><c><![CDATA[+M<S>mmbcs <size>]]></c></tag>
+        <item>
+          <p>Main multiblock carrier size. Sets the size of the main
+            multiblock carrier for allocator <c><![CDATA[<S>]]></c>. The main
+            multiblock carrier is allocated through <c><![CDATA[sys_alloc]]></c>
+            and is never deallocated.</p>
+        </item>
+        <tag><marker id="M_mmmbc"/><c><![CDATA[+M<S>mmmbc <amount>]]></c></tag>
+        <item>
+          <p>Maximum <c>mseg_alloc</c> multiblock carriers. Maximum number of
+            multiblock carriers allocated through <c>mseg_alloc</c> by
+            allocator <c><![CDATA[<S>]]></c>. When this limit is reached,
+            new multiblock carriers are allocated through
+            <c>sys_alloc</c>.</p>
+        </item>
+        <tag><marker id="M_mmsbc"/><c><![CDATA[+M<S>mmsbc <amount>]]></c></tag>
+        <item>
+          <p>Maximum <c>mseg_alloc</c> singleblock carriers. Maximum number of
+            singleblock carriers allocated through <c>mseg_alloc</c> by
+            allocator <c><![CDATA[<S>]]></c>. When this limit is reached,
+            new singleblock carriers are allocated through
+            <c>sys_alloc</c>.</p>
+        </item>
+        <tag><marker id="M_ramv"/><c><![CDATA[+M<S>ramv <bool>]]></c></tag>
+        <item>
+          <p>Realloc always moves. When enabled, reallocate operations are
+            more or less translated into an allocate, copy, free sequence.
+            This often reduces memory fragmentation, but costs performance.</p>
+        </item>
+        <tag><marker id="M_rmbcmt"/><c><![CDATA[+M<S>rmbcmt <ratio>]]></c></tag>
+        <item>
+          <p>Relative multiblock carrier move threshold (in percent). When
+            a block located in a multiblock carrier is shrunk,
+            the block is moved if the ratio of the size of the returned
+            memory compared to the previous size is more than this threshold,
+            otherwise the block is shrunk at the current location.</p>
+        </item>
+        <tag><marker id="M_rsbcmt"/><c><![CDATA[+M<S>rsbcmt <ratio>]]></c></tag>
+        <item>
+          <p>Relative singleblock carrier move threshold (in percent). When
+            a block located in a singleblock carrier is shrunk to
+            a size smaller than the value of parameter
+            <seealso marker="#M_sbct"><c>sbct</c></seealso>,
+            the block is left unchanged in the singleblock carrier if
+            the ratio of unused memory is less than this threshold,
+            otherwise it is moved into a multiblock carrier.</p>
+        </item>
+        <tag><marker id="M_rsbcst"/><c><![CDATA[+M<S>rsbcst <ratio>]]></c></tag>
+        <item>
+          <p>Relative singleblock carrier shrink threshold (in
+            percent). When a block located in an <c>mseg_alloc</c>
+            singleblock carrier is shrunk, the carrier is left
+            unchanged if the ratio of unused memory is less than this
+            threshold, otherwise the carrier is shrunk.
+            See also <seealso marker="#M_asbcst"><c>asbcst</c></seealso>.</p>
+        </item>
+        <tag><marker id="M_sbct"/><c><![CDATA[+M<S>sbct <size>]]></c></tag>
+        <item>
+          <p>Singleblock carrier threshold. Blocks larger than this
+            threshold are placed in singleblock carriers. Blocks
+            smaller than this threshold are placed in multiblock
+            carriers. On 32-bit Unix style OS this threshold cannot be set
+            &gt; 8 MB.</p>
+        </item>
+        <tag><marker id="M_smbcs"/><c><![CDATA[+M<S>smbcs <size>]]></c></tag>
+        <item>
+          <p>Smallest (<c>mseg_alloc</c>) multiblock carrier size (in
+            kilobytes). See the description on how sizes for <c>mseg_alloc</c>
+            multiblock carriers are decided in section
+            <seealso marker="#mseg_mbc_sizes">
+            The alloc_util Framework</seealso>.</p>
+        </item>
+        <tag><marker id="M_t"/><c><![CDATA[+M<S>t true|false]]></c></tag>
+        <item>
+          <p>Multiple, thread-specific instances of the allocator.
+            This option has only effect on the runtime system
+            with SMP support. Default behavior on the runtime system with
+            SMP support is <c>NoSchedulers+1</c> instances. Each scheduler
+            uses a lock-free instance of its own and other threads use
+            a common instance.</p>
+          <p>Before <c>ERTS</c> 5.9 it was possible to configure
+            a smaller number of thread-specific instances than schedulers.
+            This is, however, not possible anymore.</p>
+        </item>
+      </taglist>
+    </section>
+
+    <section>
+      <title>Flags for Configuration of alloc_util</title>
+      <p>All allocators based on <c>alloc_util</c> are effected.</p>
+
+      <taglist>
+        <tag><marker id="Muycs"/><c><![CDATA[+Muycs <size>]]></c></tag>
+        <item>
+          <p><c>sys_alloc</c> carrier size. Carriers allocated through
+            <c>sys_alloc</c> are allocated in sizes that are
+            multiples of the <c>sys_alloc</c> carrier size. This is not
+            true for main multiblock carriers and carriers allocated
+            during a memory shortage, though.</p>
+        </item>
+        <tag><marker id="Mummc"/><c><![CDATA[+Mummc <amount>]]></c></tag>
+        <item>
+          <p>Maximum <c>mseg_alloc</c> carriers. Maximum number of carriers
+            placed in separate memory segments. When this limit is
+            reached, new carriers are placed in memory retrieved from
+            <c>sys_alloc</c>.</p>
+        </item>
+        <tag><marker id="Musac"/><c><![CDATA[+Musac <bool>]]></c></tag>
+        <item>
+          <p>Allow <c>sys_alloc</c> carriers. Defaults to <c>true</c>.
+            If set to <c>false</c>, <c>sys_alloc</c> carriers are never
+            created by allocators using the <c>alloc_util</c> framework.</p>
+        </item>
+      </taglist>
+    </section>
+
+    <section>
+      <title>Special Flag for literal_alloc</title>
       <taglist>
-        <tag><c>min</c></tag>
+        <tag><marker id="MIscs"/><c><![CDATA[+MIscs <size in MB>]]></c></tag>
         <item>
-	  Disables all allocators that can be disabled.
-	</item>
+          <p><c>literal_alloc</c> super carrier size (in MB). The amount of
+            <em>virtual</em> address space reserved for literal terms in
+            Erlang code on 64-bit architectures. Defaults to <c>1024</c>
+            (that is, 1 GB), which is usually sufficient.
+            The flag is ignored on 32-bit architectures.</p>
+        </item>
+      </taglist>
+    </section>
 
-        <tag><c>max</c></tag>
+    <section>
+      <title>Special Flag for exec_alloc</title>
+      <taglist>
+        <tag><marker id="MXscs"/><c><![CDATA[+MXscs <size in MB>]]></c></tag>
         <item>
-	  Enables all allocators (currently default).
-	</item>
+          <p><c>exec_alloc</c> super carrier size (in MB). The amount of
+            <em>virtual</em> address space reserved for native executable code
+            used by the <seealso marker="hipe"><c>HiPE</c></seealso> application
+            on specific architectures (x86_64). Defaults to <c>512</c>.</p>
+        </item>
+      </taglist>
+    </section>
 
-        <tag><c>r9c|r10b|r11b</c></tag>
+    <section>
+      <title>Instrumentation Flags</title>
+      <taglist>
+        <tag><marker id="Mim"/><c>+Mim true|false</c></tag>
         <item>
-	  Configures all allocators as they were configured in respective
-	  OTP release. These will eventually be removed.
-	</item>
+          <p>A map over current allocations is kept by the emulator.
+            The allocation map can be retrieved through module
+            <seealso marker="tools:instrument">
+            <c>tools:instrument(3)</c></seealso>. <c>+Mim true</c>
+            implies <c>+Mis true</c>. <c>+Mim true</c> is the same as flag
+            <seealso marker="erl#instr"><c>-instr</c></seealso> in 
+            <c>erl(1)</c>.</p>
+        </item>
+        <tag><marker id="Mis"/><c>+Mis true|false</c></tag>
+        <item>
+          <p>Status over allocated memory is kept by the emulator.
+            The allocation status can be retrieved through module
+            <seealso marker="tools:instrument">
+            <c>tools:instrument(3)</c></seealso>.</p>
+        </item>
+        <tag><marker id="Mit"/><c>+Mit X</c></tag>
+        <item>
+          <p>Reserved for future use. Do <em>not</em> use this flag.</p>
+        </item>
+      </taglist>
 
-        <tag><c>config</c></tag>
+      <note>
+        <p>When instrumentation of the emulator is enabled, the emulator
+          uses more memory and runs slower.</p>
+      </note>
+    </section>
+
+    <section>
+      <title>Other Flags</title>
+      <taglist>
+        <tag><marker id="Mea"/><c>+Mea min|max|r9c|r10b|r11b|config</c></tag>
+        <item>
+          <p>Options:</p>
+          <taglist>
+            <tag><c>min</c></tag>
+            <item>
+              <p>Disables all allocators that can be disabled.</p>
+            </item>
+            <tag><c>max</c></tag>
+            <item>
+              <p>Enables all allocators (default).</p>
+            </item>
+            <tag><c>r9c|r10b|r11b</c></tag>
+            <item>
+              <p>Configures all allocators as they were configured in respective
+                Erlang/OTP release. These will eventually be removed.</p>
+            </item>
+            <tag><c>config</c></tag>
+            <item>
+              <p>Disables features that cannot be enabled while creating an
+                allocator configuration with
+                <seealso marker="runtime_tools:erts_alloc_config">
+                <c>runtime_tools:erts_alloc_config(3)</c></seealso>.</p>
+              <note>
+                <p>This option is to be used only while running
+                  <c>runtime_tools:erts_alloc_config(3)</c>, <em>not</em> when
+                  using the created configuration.</p>
+              </note>
+            </item>
+          </taglist>
+        </item>
+        <tag><marker id="Mlpm"/><c>+Mlpm all|no</c></tag>
         <item>
-	  Disables features that cannot be enabled while creating an
-	  allocator configuration with
-	  <seealso marker="runtime_tools:erts_alloc_config">erts_alloc_config(3)</seealso>.
-	  Note, this option should only be used while running
-	  <c>erts_alloc_config</c>, <em>not</em> when using the created
-	  configuration.
+          <p>Lock physical memory. Defaults to <c>no</c>, that is,
+            no physical memory is locked. If set to <c>all</c>, all
+            memory mappings made by the runtime system are locked into
+            physical memory. If set to <c>all</c>, the runtime system fails to
+            start if this feature is not supported, the user has not got enough
+            privileges, or the user is not allowed to lock enough physical
+            memory. The runtime system also fails with an out of memory
+            condition if the user limit on the amount of locked memory is
+            reached.</p>
         </item>
       </taglist>
-      </item>
-      <tag><marker id="Mlpm"/><c>+Mlpm all|no</c></tag>
-      <item>Lock physical memory. The default value is <c>no</c>, i.e.,
-      no physical memory will be locked. If set to <c>all</c>, all
-      memory mappings made by the runtime system, will be locked into
-      physical memory. If set to <c>all</c>, the runtime system will fail
-      to start if this feature is not supported, the user has not got enough
-      privileges, or the user is not allowed to lock enough physical memory.
-      The runtime system will also fail with an out of memory condition
-      if the user limit on the amount of locked memory is reached.
-      </item>
-    </taglist>
-    <p>Only some default values have been presented
-      here.
-      <seealso marker="erts:erlang#system_info_allocator">erlang:system_info(allocator)</seealso>,
-      and
-      <seealso marker="erts:erlang#system_info_allocator_tuple">erlang:system_info({allocator, Alloc})</seealso>
-      can be used in order to obtain currently used settings and current
-      status of the allocators.</p>
+    </section>
+  </section>
+
+  <section>
+    <title>Notes</title>
+    <p>Only some default values have been presented here. For information
+      about the currently used settings and the current status of the
+      allocators, see
+      <seealso marker="erts:erlang#system_info_allocator">
+      <c>erlang:system_info(allocator)</c></seealso> and
+      <seealso marker="erts:erlang#system_info_allocator_tuple">
+      <c>erlang:system_info({allocator, Alloc})</c></seealso>.</p>
+
     <note>
-      <p>Most of these flags are highly implementation dependent, and they
-        may be changed or removed without prior notice.</p>
+      <p>Most of these flags are highly implementation-dependent and
+        can be changed or removed without prior notice.</p>
       <p><c>erts_alloc</c> is not obliged to strictly use the settings that
-        have been passed to it (it may even ignore them).</p>
+        have been passed to it (it can even ignore them).</p>
     </note>
-    <p><seealso marker="runtime_tools:erts_alloc_config">erts_alloc_config(3)</seealso>
-      is a tool that can be used to aid creation of an
+
+    <p>The <seealso marker="runtime_tools:erts_alloc_config">
+      <c>runtime_tools:erts_alloc_config(3)</c></seealso>
+      tool can be used to aid creation of an
       <c>erts_alloc</c> configuration that is suitable for a limited
       number of runtime scenarios.</p>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="runtime_tools:erts_alloc_config">erts_alloc_config(3)</seealso>,
-      <seealso marker="erl">erl(1)</seealso>,
-      <seealso marker="tools:instrument">instrument(3)</seealso>,
-      <seealso marker="erts:erlang">erlang(3)</seealso></p>
+    <title>See Also</title>
+    <p><seealso marker="erl"><c>erl(1)</c></seealso>,
+      <seealso marker="erlang"><c>erlang(3)</c></seealso>,
+      <seealso marker="runtime_tools:erts_alloc_config">
+      <c>runtime_tools:erts_alloc_config(3)</c></seealso>,
+      <seealso marker="tools:instrument">
+      <c>tools:instrument(3)</c></seealso></p>
   </section>
 </cref>
 
diff --git a/erts/doc/src/escript.xml b/erts/doc/src/escript.xml
index f12f76890c..602b88f6ed 100644
--- a/erts/doc/src/escript.xml
+++ b/erts/doc/src/escript.xml
@@ -33,17 +33,18 @@
   <comsummary>Erlang scripting support</comsummary>
   <description>
     <p><c>escript</c> provides support for running short Erlang programs
-      without having to compile them first and an easy way to retrieve the
-      command line arguments.</p>
+      without having to compile them first, and an easy way to retrieve the
+      command-line arguments.</p>
   </description>
+
   <funcs>
     <func>
       <name>script-name script-arg1 script-arg2...</name>
       <name>escript escript-flags script-name script-arg1 script-arg2...</name>
-      <fsummary>Run a script written in Erlang</fsummary>
+      <fsummary>Run a script written in Erlang.</fsummary>
       <desc>
         <p><c>escript</c> runs a script written in Erlang.</p>
-        <p>Here follows an example.</p>
+        <p>Example:</p>
         <pre>
 $ <input>chmod u+x factorial</input>
 $ <input>cat factorial</input>
@@ -73,195 +74,183 @@ factorial 5 = 120
 $ <input>./factorial</input>
 usage: factorial integer
 $ <input>./factorial five</input>
-usage: factorial integer
-        </pre>
+usage: factorial integer</pre>
         <p>The header of the Erlang script in the example differs from
-        a normal Erlang module.  The first line is intended to be the
-        interpreter line, which invokes <c>escript</c>. However if you
-        invoke the <c>escript</c> like this</p>
+          a normal Erlang module. The first line is intended to be the
+          interpreter line, which invokes <c>escript</c>.</p>
+        <p>However, if you invoke the <c>escript</c> as follows,
+          the contents of the first line does not matter, but it
+          cannot contain Erlang code as it will be ignored:</p>
         <pre>
-$ <input>escript factorial 5</input>        </pre>
-        <p>the contents of the first line does not matter, but it
-        cannot contain Erlang code as it will be ignored.</p>
-        <p>The second line in the example, contains an optional
-          directive to the <c>Emacs</c> editor which causes it to
+$ <input>escript factorial 5</input></pre>
+        <p>The second line in the example contains an optional
+          directive to the <c>Emacs</c> editor, which causes it to
           enter the major mode for editing Erlang source files. If the
-          directive is present it must be located on the second
+          directive is present, it must be located on the second
           line.</p>
-
-        <p>If there is a comment selecting the <seealso
-          marker="stdlib:epp#encoding">encoding</seealso> it can be
+        <p>If a comment selecting the <seealso
+          marker="stdlib:epp#encoding">encoding</seealso> exists, it can be
           located on the second line.</p>
-
-        <note><p>
-          The encoding specified by the above mentioned comment
-          applies to the script itself. The encoding of the
-          I/O-server, however, has to be set explicitly like this:</p>
-<code>io:setopts([{encoding, unicode}])</code>
+        <note>
+          <p>The encoding specified by the above mentioned comment
+            applies to the script itself. The encoding of the
+            I/O-server, however, must be set explicitly as follows:</p>
+          <code>
+io:setopts([{encoding, unicode}])</code>
           <p>The default encoding of the I/O-server for <c>standard_io</c>
-          is <c>latin1</c>
-          since the script runs in a non-interactive terminal
-          (see <seealso marker="stdlib:unicode_usage#unicode_options_summary">
-          Using Unicode in Erlang</seealso>).
-        </p></note>
-
-	<p>On the third line (or second line depending on the presence
-          of the Emacs directive), it is possible to give arguments to
-          the emulator, such as </p>
+            is <c>latin1</c>, as the script runs in a non-interactive terminal
+            (see section
+            <seealso marker="stdlib:unicode_usage#unicode_options_summary">
+            Summary of Options</seealso>) in the <c>STDLIB</c> User's Guide.</p>
+        </note>
+        <p>On the third line (or second line depending on the presence
+          of the Emacs directive), arguments can be specified to
+          the emulator, for example:</p>
         <pre>
 %%! -smp enable -sname factorial -mnesia debug verbose</pre>
         <p>Such an argument line must start with <c>%%!</c> and the
-          rest of the line will interpreted as arguments to the emulator.</p>
+          remaining line is interpreted as arguments to the emulator.</p>
         <p>If you know the location of the <c>escript</c> executable, the first
-          line can directly give the path to <c>escript</c>. For instance:</p>
+          line can directly give the path to <c>escript</c>, for example:</p>
         <pre>
-#!/usr/local/bin/escript        </pre>
-        <p>As any other kind of scripts, Erlang scripts will not work on
+#!/usr/local/bin/escript</pre>
+        <p>As any other type of scripts, Erlang scripts do not work on
           Unix platforms if the execution bit for the script file is not set.
-          (Use <c>chmod +x script-name</c> to turn on the execution bit.)
-          </p>
-
-        <p>The rest of the Erlang script file may either contain
-        Erlang <c>source code</c>, an <c>inlined beam file</c> or an
-        <c>inlined archive file</c>.</p>
-
-        <p>An Erlang script file must always contain the function
-        <em>main/1</em>.  When the script is run, the
-        <c>main/1</c> function will be called with a list
-        of strings representing the arguments given to the script (not
-        changed or interpreted in any way).</p>
-
+          (To turn on the execution bit, use <c>chmod +x script-name</c>.)</p>
+        <p>The remaining Erlang script file can either contain
+          Erlang <em>source code</em>, an <em>inlined beam file</em>, or an
+          <em>inlined archive file</em>.</p>
+        <p>An Erlang script file must always contain the <c>main/1</c>
+          function. When the script is run, the
+          <c>main/1</c> function is called with a list
+          of strings representing the arguments specified to the script (not
+          changed or interpreted in any way).</p>
         <p>If the <c>main/1</c> function in the script returns successfully,
-          the exit status for the script will be 0. If an exception is generated
-          during execution, a short message will be printed and the script terminated
-          with exit status 127.</p>
-
-        <p>To return your own non-zero exit code, call <c>halt(ExitCode)</c>;
-          for instance:</p>
+          the exit status for the script is <c>0</c>. If an exception is
+          generated during execution, a short message is printed and the script
+          terminates with exit status <c>127</c>.</p>
+        <p>To return your own non-zero exit code, call <c>halt(ExitCode)</c>,
+          for example:</p>
         <pre>
 halt(1).</pre>
-
-        <p>Call <seealso marker="#script_name_0">escript:script_name()</seealso>
-	from your to script to retrieve the pathname of the script
-	(the pathname is usually, but not always, absolute).</p>
-
+        <p>To retrieve the pathname of the script, call
+          <seealso marker="#script_name_0">
+          <c>escript:script_name()</c></seealso> from your script
+	  (the pathname is usually, but not always, absolute).</p>
         <p>If the file contains source code (as in the example above),
-          it will be processed by the preprocessor <c>epp</c>. This
-          means that you for example may use pre-defined macros (such as
-          <c>?MODULE</c>) as well as include directives like
-          the <c>-include_lib</c> directive. For instance, use</p>
+          it is processed by the
+          <seealso marker="stdlib:epp"><c>epp</c></seealso> preprocessor.
+          This means that you, for example, can use predefined macros
+          (such as <c>?MODULE</c>) and include directives like
+          the <c>-include_lib</c> directive. For example, use</p>
         <pre>
 -include_lib("kernel/include/file.hrl").</pre>
-        <p>to include the record definitions for the records used by the
-          <c>file:read_link_info/1</c> function. You can also select
-          encoding by including a encoding comment here, but if there
-          is a valid encoding comment on the second line it takes
+        <p>to include the record definitions for the records used by function
+          <seealso marker="kernel:file#read_link_info/1">
+          <c>file:read_link_info/1</c></seealso>. You can also select
+          encoding by including an encoding comment here, but if
+          a valid encoding comment exists on the second line, it takes
           precedence.</p>
-
-        <p>The script will be checked for syntactic and semantic
-          correctness before being run. If there are warnings (such as
-          unused variables), they will be printed and the script will
-          still be run. If there are errors, they will be printed and
-          the script will not be run and its exit status will be
-          127.</p>
-
+        <p>The script is checked for syntactic and semantic
+          correctness before it is run. If there are warnings (such as
+          unused variables), they are printed and the script will
+          still be run. If there are errors, they are printed and
+          the script will not be run and its exit status is
+          <c>127</c>.</p>
         <p>Both the module declaration and the export declaration of
           the <c>main/1</c> function are optional.</p>
-
         <p>By default, the script will be interpreted. You can force
           it to be compiled by including the following line somewhere
-          in the script file:</p><pre>
+          in the script file:</p>
+        <pre>
 -mode(compile).</pre>
-
         <p>Execution of interpreted code is slower than compiled code.
-          If much of the execution takes place in interpreted code it
-          may be worthwhile to compile it, even though the compilation
-          itself will take a little while. It is also possible to supply
-	  <c>native</c> instead of <c>compile</c>, this will compile the script
-	  using the native flag, again depending on the characteristics 
-	  of the escript this could or could not be worth while.</p>
-
-        <p>As mentioned earlier, it is possible to have a script which
+          If much of the execution takes place in interpreted code, it
+          can be worthwhile to compile it, although the compilation
+          itself takes a little while. Also, <c>native</c> can be supplied
+          instead of <c>compile</c>. This compiles the script
+          using the native flag and may or may not be worthwhile
+          depending on the escript characteristics.</p>
+        <p>As mentioned earlier, a script can
           contains precompiled <c>beam</c> code. In a precompiled
-          script, the interpretation of the script header is exactly
-          the same as in a script containing source code. That means
+          script, the interpretation of the script header is
+          the same as in a script containing source code. This means
           that you can make a <c>beam</c> file executable by
           prepending the file with the lines starting with <c>#!</c>
           and <c>%%!</c> mentioned above. In a precompiled script, the
-          function
-          <c>main/1</c> must be exported.</p>
-
-        <p>As yet another option it is possible to have an entire
-          Erlang archive in the script. In a archive script, the
-          interpretation of the script header is exactly the same as
-          in a script containing source code. That means that you can
+          <c>main/1</c> function must be exported.</p>
+        <p>Another option is to have an entire
+          Erlang archive in the script. In an archive script, the
+          interpretation of the script header is the same as
+          in a script containing source code. This means that you can
           make an archive file executable by prepending the file with
           the lines starting with <c>#!</c> and <c>%%!</c> mentioned
-          above. In an archive script, the function <c>main/1</c> must
+          above. In an archive script, the <c>main/1</c> function must
           be exported. By default the <c>main/1</c> function in the
           module with the same name as the basename of the
-          <c>escript</c> file will be invoked. This behavior can be
-          overridden by setting the flag <c>-escript main Module</c>
-          as one of the emulator flags. The <c>Module</c> must be the
-          name of a module which has an exported <c>main/1</c>
-          function. See <seealso marker="kernel:code">code(3)</seealso>
-          for more information about archives and code loading.</p>
-
-	  <p>In many cases it is very convenient to have a header in
-	  the escript, especially on Unix platforms. But the header is
-	  in fact optional. This means that you directly can "execute"
-	  an Erlang module, beam file or archive file without adding
-	  any header to them. But then you have to invoke the script
-	  like this:</p>
-	  <pre>
+          <c>escript</c> file is invoked. This behavior can be
+          overridden by setting flag <c>-escript main Module</c>
+          as one of the emulator flags. <c>Module</c> must be the
+          name of a module that has an exported <c>main/1</c>
+          function. For more information about archives and code loading, see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
+        <p>It is often very convenient to have a header in
+          the escript, especially on Unix platforms. However, the header
+          is optional, so you directly can "execute"
+          an Erlang module, Beam file, or archive file without adding
+          any header to them. But then you have to invoke the script
+          as follows:</p>
+        <pre>
 $ <input>escript factorial.erl 5</input>
 factorial 5 = 120
 $ <input>escript factorial.beam 5</input>
 factorial 5 = 120
 $ <input>escript factorial.zip 5</input>
-factorial 5 = 120
-</pre>
+factorial 5 = 120</pre>
       </desc>
     </func>
+
     <func>
-      <name>escript:create(FileOrBin, Sections) -> ok | {ok, binary()} | {error, term()}</name>
-      <fsummary>Create an escript</fsummary>
+      <name>escript:create(FileOrBin, Sections) -> ok | {ok, binary()} |
+        {error, term()}</name>
+      <fsummary>Create an escript.</fsummary>
       <type>
         <v>FileOrBin = filename() | 'binary'</v>
         <v>Sections = [Header] Body | Body</v>
         <v>Header = shebang | {shebang, Shebang}
-                    | comment | {comment, Comment}
-                    | {emu_args, EmuArgs}</v>
+        &nbsp;&nbsp;&nbsp;| comment | {comment, Comment}
+        &nbsp;&nbsp;&nbsp;| {emu_args, EmuArgs}</v>
         <v>Shebang = string() | 'default' | 'undefined'</v>
         <v>Comment = string() | 'default' | 'undefined'</v>
         <v>EmuArgs = string() | 'undefined'</v>
-        <v>Body = {source, SourceCode}
-                | {beam, BeamCode}
-                | {archive, ZipArchive}
-                | {archive, ZipFiles, ZipOptions}</v>
+        <v>Body = {source, SourceCode} | {beam, BeamCode}
+        &nbsp;&nbsp;&nbsp;| {archive, ZipArchive}
+        &nbsp;&nbsp;&nbsp;| {archive, ZipFiles, ZipOptions}</v>
         <v>SourceCode = BeamCode = file:filename() | binary()</v>
-        <v>ZipArchive = <seealso marker="stdlib:zip#type-filename">zip:filename()</seealso> | binary()</v>
+        <v>ZipArchive = <seealso marker="stdlib:zip#type-filename">
+          zip:filename()</seealso> | binary()</v>
         <v>ZipFiles = [ZipFile]</v>
-        <v>ZipFile = file:filename() | {file:filename(), binary()} | {file:filename(), binary(), file:file_info()}</v>
-        <v>ZipOptions = [<seealso marker="stdlib:zip#type-create_option">zip:create_option()</seealso>]</v>
+        <v>ZipFile = file:filename()
+        &nbsp;&nbsp;&nbsp;| {file:filename(), binary()}
+        &nbsp;&nbsp;&nbsp;| {file:filename(), binary(), file:file_info()}</v>
+        <v>ZipOptions = [<seealso marker="stdlib:zip#type-create_option">
+          zip:create_option()</seealso>]</v>
       </type>
       <desc>
-        <p>The <marker id="create_2"></marker> <c>create/2</c>
-        function creates an escript from a list of sections. The
-        sections can be given in any order. An escript begins with an
-        optional <c>Header</c> followed by a mandatory <c>Body</c>. If
-        the header is present, it does always begin with a
-        <c>shebang</c>, possibly followed by a <c>comment</c> and
-        <c>emu_args</c>. The <c>shebang</c> defaults to
-        <c>"/usr/bin/env escript"</c>. The comment defaults to
-        <c>"This is an -*- erlang -*- file"</c>. The created escript
-        can either be returned as a binary or written to file.</p>
-
-	<p>As an example of how the function can be used, we create an
-	interpreted escript which uses <c>emu_args</c> to set some emulator
-	flag. In this case it happens to disable the smp_support. We
-	do also extract the different sections from the newly created
-	script:</p>
+        <p><marker id="create_2"></marker>
+          Creates an escript from a list of sections. The
+          sections can be specified in any order. An escript begins with an
+          optional <c>Header</c> followed by a mandatory <c>Body</c>. If
+          the header is present, it does always begin with a
+          <c>shebang</c>, possibly followed by a <c>comment</c> and
+          <c>emu_args</c>. The <c>shebang</c> defaults to
+          <c>"/usr/bin/env escript"</c>. The <c>comment</c> defaults to
+          <c>"This is an -*- erlang -*- file"</c>. The created escript
+          can either be returned as a binary or written to file.</p>
+        <p>As an example of how the function can be used, we create an
+          interpreted escript that uses <c>emu_args</c> to set some emulator
+          flag. In this case, it happens to disable the <c>smp_support</c>. We
+          also extract the different sections from the newly created script:</p>
         <pre>
 &gt; <input>Source = "%% Demo\nmain(_Args) ->\n    io:format(erlang:system_info(smp_support)).\n".</input>
 "%% Demo\nmain(_Args) ->\n    io:format(erlang:system_info(smp_support)).\n"
@@ -280,11 +269,9 @@ ok
 "false"
 &gt; <input>escript:extract("demo.escript", []).</input>
 {ok,[{shebang,default}, {comment,default}, {emu_args,"-smp disable"},
-     {source,&lt;&lt;"%% Demo\nmain(_Args) ->\n    io:format(erlang:system_info(smp_su"...&gt;&gt;}]}
-	</pre>
-
-	<p>An escript without header can be created like this:</p>
-<pre>
+     {source,&lt;&lt;"%% Demo\nmain(_Args) ->\n    io:format(erlang:system_info(smp_su"...&gt;&gt;}]}</pre>
+        <p>An escript without header can be created as follows:</p>
+        <pre>
 &gt; <input>file:write_file("demo.erl",
                   ["%% demo.erl\n-module(demo).\n-export([main/1]).\n\n", Source]).</input>
 ok
@@ -299,14 +286,12 @@ ok
      {beam,&lt;&lt;70,79,82,49,0,0,3,68,66,69,65,77,65,116,
              111,109,0,0,0,83,0,0,0,9,...&gt;&gt;}]}
 &gt; <input>os:cmd("escript demo.beam").</input>
-"true"
-</pre>
-	<p>Here we create an archive script containing both Erlang
-	code as well as beam code. Then we iterate over all files in
-	the archive and collect their contents and some info about
-	them.
-	</p>
-<pre>
+"true"</pre>
+        <p>Here we create an archive script containing both Erlang
+          code and Beam code, then we iterate over all files in
+          the archive and collect their contents and some information about
+          them:</p>
+        <pre>
 &gt; <input>{ok, SourceCode} = file:read_file("demo.erl").</input>
 {ok,&lt;&lt;"%% demo.erl\n-module(demo).\n-export([main/1]).\n\n%% Demo\nmain(_Arg"...&gt;&gt;}
 &gt; <input>escript:create("demo.escript",
@@ -339,43 +324,43 @@ ok
       &lt;&lt;"%% demo.erl\n-module(demo).\n-export([main/1]).\n\n%% Demo\nmain(_Arg"...&gt;&gt;}]}</pre>
       </desc>
     </func>
+
     <func>
-      <name>escript:extract(File, Options) -> {ok, Sections} | {error, term()}</name>
-      <fsummary>Parses an escript and extracts its sections</fsummary>
+      <name>escript:extract(File, Options) -> {ok, Sections} |
+        {error, term()}</name>
+      <fsummary>Parse an escript and extract its sections.</fsummary>
       <type>
         <v>File = filename()</v>
         <v>Options = [] | [compile_source]</v>
         <v>Sections = Headers Body</v>
         <v>Headers =  {shebang, Shebang}
-                      {comment, Comment}
-                      {emu_args, EmuArgs}</v>
+          {comment, Comment}
+          {emu_args, EmuArgs}</v>
         <v>Shebang = string() | 'default' | 'undefined'</v>
         <v>Comment = string() | 'default' | 'undefined'</v>
         <v>EmuArgs = string() | 'undefined'</v>
         <v>Body = {source, SourceCode}
-                | {source, BeamCode}
-                | {beam, BeamCode}
-	        | {archive, ZipArchive}</v>
+        &nbsp;&nbsp;&nbsp;| {source, BeamCode}
+        &nbsp;&nbsp;&nbsp;| {beam, BeamCode}
+        &nbsp;&nbsp;&nbsp;| {archive, ZipArchive}</v>
         <v>SourceCode = BeamCode = ZipArchive = binary()</v>
       </type>
       <desc>
-        <p>The <marker id="extract_2"></marker> <c>extract/2</c>
-        function parses an escript and extracts its sections. This is
-        the reverse of <c>create/2</c>.</p>
-
-	<p>All sections are returned even if they do not exist in the
-	escript. If a particular section happens to have the same
-	value as the default value, the extracted value is set to the
-	atom <c>default</c>. If a section is missing, the extracted
-	value is set to the atom <c>undefined</c>.  </p>
-
-	<p>The <c>compile_source</c> option only affects the result if
-	the escript contains <c>source</c> code. In that case the
-	Erlang code is automatically compiled and <c>{source,
-	BeamCode}</c> is returned instead of <c>{source,
-	SourceCode}</c>.</p>
-
-	<pre>
+        <p><marker id="extract_2"></marker>
+          Parses an escript and extracts its sections. This is the reverse
+          of <seealso marker="#create_2"><c>create/2</c></seealso>.</p>
+        <p>All sections are returned even if they do not exist in the
+          escript. If a particular section happens to have the same
+          value as the default value, the extracted value is set to the
+          atom <c>default</c>. If a section is missing, the extracted
+          value is set to the atom <c>undefined</c>.</p>
+        <p>Option <c>compile_source</c> only affects the result if
+          the escript contains <c>source</c> code. In this case the
+          Erlang code is automatically compiled and <c>{source,
+          BeamCode}</c> is returned instead of <c>{source,
+          SourceCode}</c>.</p>
+        <p>Example:</p>
+        <pre>
 &gt; <input>escript:create("demo.escript",
                  [shebang, {archive, [{"demo.erl", SourceCode},
                                       {"demo.beam", BeamCode}], []}]).</input>
@@ -385,52 +370,51 @@ ok
               escript:extract("demo.escript", []).</input>
 {ok,[{{archive,&lt;&lt;80,75,3,4,20,0,0,0,8,0,118,7,98,60,105,
                 152,61,93,107,0,0,0,118,0,...&gt;&gt;}
-     {emu_args,undefined}]}
-	</pre>
+     {emu_args,undefined}]}</pre>
       </desc>
     </func>
+
     <func>
       <name>escript:script_name() -> File</name>
-      <fsummary>Returns the name of an escript</fsummary>
+      <fsummary>Return the name of an escript.</fsummary>
       <type>
         <v>File = filename()</v>
       </type>
       <desc>
-        <p>The <marker id="script_name_0"></marker>
-        <c>script_name/0</c> function returns the name of the escript
-        being executed. If the function is invoked outside the context
-        of an escript, the behavior is undefined.</p>
+        <p><marker id="script_name_0"></marker>
+          Returns the name of the escript that is executed.
+          If the function is invoked outside the context
+          of an escript, the behavior is undefined.</p>
       </desc>
     </func>
   </funcs>
 
   <section>
-    <title>Options accepted by escript</title>
+    <title>Options Accepted By escript</title>
     <taglist>
-      <tag>-c</tag>
-      <item>Compile the escript regardless of the value of the mode attribute.
+      <tag><c>-c</c></tag>
+      <item>Compiles the escript regardless of the value of the mode attribute.
       </item>
-
-      <tag>-d</tag>
-      <item>Debug the escript. Starts the debugger, loads the module
-      containing the <c>main/1</c> function into the debugger, sets a
-      breakpoint in <c>main/1</c> and invokes <c>main/1</c>. If the
-      module is precompiled, it must be explicitly compiled with the
-      <c>debug_info</c> option.
+      <tag><c>-d</c></tag>
+      <item>Debugs the escript. Starts the debugger, loads the module
+        containing the <c>main/1</c> function into the debugger, sets a
+        breakpoint in <c>main/1</c>, and invokes <c>main/1</c>. If the
+        module is precompiled, it must be explicitly compiled with option
+        <c>debug_info</c>.
       </item>
-
-      <tag>-i</tag>
-      <item>Interpret the escript regardless of the value of the mode attribute.
+      <tag><c>-i</c></tag>
+      <item>Interprets the escript regardless of the value of the mode
+        attribute.
+      </item>
+      <tag><c>-s</c></tag>
+      <item>Performs a syntactic and semantic check of the script file.
+        Warnings and errors (if any) are written to the standard output, but
+        the script will not be run. The exit status is <c>0</c> if any errors
+        are found, otherwise <c>127</c>.
+      </item>
+      <tag><c>-n</c></tag>
+      <item>Compiles the escript using flag <c>+native</c>.
       </item>
-
-      <tag>-s</tag>
-      <item>Only perform a syntactic and semantic check of the script file.
-       Warnings and errors (if any) are written to the standard output, but
-       the script will not be run. The exit status will be 0 if there were
-       no errors, and 127 otherwise.</item>
-
-       <tag>-n</tag>
-      <item>Compile the escript using the +native flag.</item>
     </taglist>
   </section>
 </comref>
diff --git a/erts/doc/src/inet_cfg.xml b/erts/doc/src/inet_cfg.xml
index 027fe600d7..37653a08e9 100644
--- a/erts/doc/src/inet_cfg.xml
+++ b/erts/doc/src/inet_cfg.xml
@@ -22,7 +22,7 @@
 
     </legalnotice>
 
-    <title>Inet configuration</title>
+    <title>Inet Configuration</title>
     <prepared>Peter Andersson</prepared>
     <docno></docno>
     <date>2004-03-02</date>
@@ -32,374 +32,341 @@
 
   <section>
     <title>Introduction</title>
-    <p>This chapter tells you how the Erlang runtime system is configured
-      for IP communication. It also explains how you may configure it 
-      for your own particular needs by means of a configuration file.
-      The information here is mainly intended for users with special 
-      configuration needs or problems. There should normally be no need
-      for specific settings for Erlang to function properly on a correctly 
-      IP configured platform.      </p>
-    <p>When Erlang starts up it will read the kernel variable 
-      <c><![CDATA[inetrc]]></c> which, if defined, should specify the location and 
-      name of a user configuration file. Example:</p>
-    <p><c><![CDATA[% erl -kernel inetrc '"./cfg_files/erl_inetrc"']]></c></p>
-    <p>Note that the usage of a <c><![CDATA[.inetrc]]></c> file, which was
-      supported in earlier Erlang versions, is now obsolete.</p>
-    <p>A second way to specify the configuration file is to set the
-      environment variable <c><![CDATA[ERL_INETRC]]></c> to the full name of the file. Example (bash):</p>
-    <p><c><![CDATA[% export ERL_INETRC=./cfg_files/erl_inetrc]]></c></p>
-    <p>Note that the kernel variable <c><![CDATA[inetrc]]></c> overrides this environment variable.</p>
+    <p>This section describes how the Erlang runtime system is configured
+      for IP communication. It also explains how you can configure it
+      for your needs by a configuration file.
+      The information is primarily intended for users with special
+      configuration needs or problems. There is normally no need
+      for specific settings for Erlang to function properly on a correctly
+      IP-configured platform.</p>
+
+    <p>When Erlang starts up it reads the <c>Kernel</c> variable 
+      <c><![CDATA[inetrc]]></c>, which, if defined, is to specify the location
+      and name of a user configuration file. Example:</p>
+
+    <code type="none"><![CDATA[
+% erl -kernel inetrc '"./cfg_files/erl_inetrc"']]></code>
+
+    <p>Notice that the use of an <c><![CDATA[.inetrc]]></c> file, which was
+      supported in earlier Erlang/OTP versions, is now obsolete.</p>
+
+    <p>A second way to specify the configuration file is to set
+      environment variable <c><![CDATA[ERL_INETRC]]></c> to the full name of
+      the file. Example (bash):</p>
+
+    <code type="none"><![CDATA[
+% export ERL_INETRC=./cfg_files/erl_inetrc]]></code>
+
+    <p>Notice that the <c>Kernel</c> variable <c><![CDATA[inetrc]]></c>
+      overrides this environment variable.</p>
+
     <p>If no user configuration file is specified and Erlang is started
-      in non-distributed or short name distributed mode, Erlang will use 
-      default configuration settings and a native lookup method that should 
-      work correctly under most circumstances. Erlang 
-      will not read any information from system inet configuration files 
-      (like /etc/host.conf, /etc/nsswitch.conf, etc) in these modes,
-      except for /etc/resolv.conf and /etc/hosts that is read and monitored
-      for changes on Unix platforms for the internal DNS client
-      <seealso marker="kernel:inet_res">inet_res</seealso>.</p>
+      in non-distributed or short name distributed mode, Erlang uses
+      default configuration settings and a native lookup method that
+      works correctly under most circumstances. Erlang reads no
+      information from system <c>inet</c> configuration files (such as 
+      <c>/etc/host.conf</c> and <c>/etc/nsswitch.conf</c>) in these modes,
+      except for <c>/etc/resolv.conf</c> and <c>/etc/hosts</c> that is read and
+      monitored for changes on Unix platforms for the internal DNS client
+      <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>.</p>
+
     <p>If Erlang is started in long name distributed mode, it needs to
-      get the domain name from somewhere and will read system inet
+      get the domain name from somewhere and reads system <c>inet</c>
       configuration files for this information. Any hosts and resolver
-      information found then is also recorded, but not 
-      used as long as Erlang is configured for native lookups. (The
+      information found is also recorded, but not
+      used as long as Erlang is configured for native lookups. The
       information becomes useful if the lookup method is changed to 
-      <c><![CDATA['file']]></c> or <c><![CDATA['dns']]></c>, see below).</p>
-    <p>Native lookup (system calls) is always the default resolver method. This
-      is true for all platforms except VxWorks and OSE Delta where <c><![CDATA['file']]></c> 
-      or <c><![CDATA['dns']]></c> is used (in that order of priority).</p>
-    <p>On Windows platforms, Erlang will search the system registry rather than
-      look for configuration files when started in long name distributed mode. </p>
+      <c><![CDATA['file']]></c> or <c><![CDATA['dns']]></c>, see below.</p>
+
+    <p>Native lookup (system calls) is always the default resolver method.
+      This is true for all platforms, except VxWorks and OSE Delta where
+      <c><![CDATA['file']]></c> or <c><![CDATA['dns']]></c> is used (in that
+      priority order).</p>
+
+    <p>On Windows platforms, Erlang searches the system registry rather than
+      looks for configuration files when started in long name distributed
+      mode.</p>
   </section>
 
   <section>
     <title>Configuration Data</title>
     <p>Erlang records the following data in a local database if found in system 
-      inet configuration files (or system registry):</p>
-    <list type="bulleted">
-      <item>Host names and addresses</item>
+      <c>inet</c> configuration files (or system registry):</p>
+
+   <list type="bulleted">
+      <item>Hostnames and host addresses</item>
       <item>Domain name</item>
       <item>Nameservers</item>
       <item>Search domains</item>
       <item>Lookup method</item>
     </list>
-    <p>This data may also be specified explicitly in the user
-      configuration file. The configuration file should contain lines
-      of configuration parameters (each terminated with a full
-      stop). Some parameters add data to the configuration (e.g. host
+
+    <p>This data can also be specified explicitly in the user
+      configuration file. This file is to contain lines
+      of configuration parameters (each terminated with a full stop).
+      Some parameters add data to the configuration (such as host
       and nameserver), others overwrite any previous settings
-      (e.g. domain and lookup). The user configuration file is always
+      (such as domain and lookup). The user configuration file is always
       examined last in the configuration process, making it possible
       for the user to override any default values or previously made
       settings. Call <c><![CDATA[inet:get_rc()]]></c> to view the state of the
-      inet configuration database.</p>
-    <p>These are the valid configuration parameters:</p>
-    <p></p>
+      <c>inet</c> configuration database.</p>
+
+    <p>The valid configuration parameters are as follows:</p>
+
     <taglist>
-      <tag><em><c><![CDATA[{file, Format, File}.]]></c></em></tag>
+      <tag><c><![CDATA[{file, Format, File}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Format = atom()]]></c></p>
         <p><c><![CDATA[File = string()]]></c></p>
-        <p></p>
-        <p>Specify a system file that Erlang should read configuration
-          data from. <c><![CDATA[Format]]></c> tells the parser how the file should be
-          interpreted: <c><![CDATA[resolv]]></c> (Unix resolv.conf), <c><![CDATA[host_conf_freebsd]]></c> 
-          (FreeBSD host.conf), <c><![CDATA[host_conf_bsdos]]></c> (BSDOS host.conf), 
-          <c><![CDATA[host_conf_linux]]></c> (Linux host.conf), <c><![CDATA[nsswitch_conf]]></c>
-          (Unix nsswitch.conf) or <c><![CDATA[hosts]]></c> (Unix hosts). <c><![CDATA[File]]></c> should
-          specify the name of the file with full path.</p>
-        <p></p>
+        <p>Specify a system file that Erlang is to read configuration data from.
+          <c><![CDATA[Format]]></c> tells the parser how the file is to be
+          interpreted:</p>
+        <list type="bulleted">
+          <item><c><![CDATA[resolv]]></c> (Unix resolv.conf)</item>
+          <item><c><![CDATA[host_conf_freebsd]]></c> (FreeBSD host.conf)</item>
+          <item><c><![CDATA[host_conf_bsdos]]></c> (BSDOS host.conf)</item>
+          <item><c><![CDATA[host_conf_linux]]></c> (Linux host.conf)</item>
+          <item><c><![CDATA[nsswitch_conf]]></c> (Unix nsswitch.conf)</item>
+          <item><c><![CDATA[hosts]]></c> (Unix hosts)</item>
+        </list>
+        <p><c><![CDATA[File]]></c> is to specify the filename with full
+          path.</p>
       </item>
-      <tag><em><c><![CDATA[{resolv_conf, File}.]]></c></em></tag>
+      <tag><c><![CDATA[{resolv_conf, File}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[File = string()]]></c></p>
-        <p></p>
-        <p>Specify a system file that Erlang should read resolver
+        <p>Specify a system file that Erlang is to read resolver
           configuration from for the internal DNS client
-          <seealso marker="kernel:inet_res">inet_res</seealso>,
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>,
           and monitor for changes, even if it does not exist.
           The path must be absolute.</p>
-        <p>This may override the configuration parameters
+        <p>This can override the configuration parameters
           <c><![CDATA[nameserver]]></c> and
           <c><![CDATA[search]]></c> depending on the contents
-          of the specified file. They may also change any time in the future
+          of the specified file. They can also change any time in the future
           reflecting the file contents.</p>
-        <p>If the file is specified as an empty string "",
-          no file is read nor monitored in the future. This emulates
-          the old behaviour of not configuring the DNS client when
+        <p>If the file is specified as an empty string <c>""</c>,
+          no file is read or monitored in the future. This emulates
+          the old behavior of not configuring the DNS client when
           the node is started in short name distributed mode.</p>
-        <p>If this parameter is not specified it defaults to
-          <c><![CDATA[/etc/resolv.conf]]></c> unless the environment variable
-          <c><![CDATA[ERL_INET_ETC_DIR]]></c> is set which defines
+        <p>If this parameter is not specified, it defaults to
+          <c><![CDATA[/etc/resolv.conf]]></c> unless environment variable
+          <c><![CDATA[ERL_INET_ETC_DIR]]></c> is set, which defines
           the directory for this file to some maybe other than
           <c><![CDATA[/etc]]></c>.</p>
-        <p></p>
       </item>
-      <tag><em><c><![CDATA[{hosts_file, File}.]]></c></em></tag>
+      <tag><c><![CDATA[{hosts_file, File}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[File = string()]]></c></p>
-        <p></p>
-        <p>Specify a system file that Erlang should read resolver
-          configuration from for the internal hosts file resolver
+        <p>Specify a system file that Erlang is to read resolver
+          configuration from for the internal hosts file resolver,
           and monitor for changes, even if it does not exist.
           The path must be absolute.</p>
         <p>These host entries are searched after all added with
           <c>{file, hosts, File}</c> above or
-          <c>{host, IP, Aliases}</c> below when the lookup option
+          <c>{host, IP, Aliases}</c> below when lookup option
           <c>file</c> is used.</p>
-        <p>If the file is specified as an empty string "",
-          no file is read nor monitored in the future. This emulates
-          the old behaviour of not configuring the DNS client when
+        <p>If the file is specified as an empty string <c>""</c>,
+          no file is read or monitored in the future. This emulates
+          the old behavior of not configuring the DNS client when
           the node is started in short name distributed mode.</p>
-        <p>If this parameter is not specified it defaults to
-          <c><![CDATA[/etc/hosts]]></c> unless the environment variable
-          <c><![CDATA[ERL_INET_ETC_DIR]]></c> is set which defines
+        <p>If this parameter is not specified, it defaults to
+          <c><![CDATA[/etc/hosts]]></c> unless environment variable
+          <c><![CDATA[ERL_INET_ETC_DIR]]></c> is set, which defines
           the directory for this file to some maybe other than
           <c><![CDATA[/etc]]></c>.</p>
-        <p></p>
       </item>
-      <tag><em><c><![CDATA[{registry, Type}.]]></c></em></tag>
+      <tag><c><![CDATA[{registry, Type}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Type = atom()]]></c></p>
-        <p></p>
-        <p>Specify a system registry that Erlang should read configuration
-          data from. Currently, <c><![CDATA[win32]]></c> is the only valid option.</p>
-        <p></p>
+        <p>Specify a system registry that Erlang is to read configuration
+          data from. <c><![CDATA[win32]]></c> is the only valid option.</p>
       </item>
-      <tag><em><c><![CDATA[{host, IP, Aliases}.]]></c></em></tag>
+      <tag><c><![CDATA[{host, IP, Aliases}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[IP = tuple()]]></c></p>
         <p><c><![CDATA[Aliases = [string()]]]></c></p>
-        <p></p>
         <p>Add host entry to the hosts table.</p>
-        <p></p>
       </item>
-      <tag><em><c><![CDATA[{domain, Domain}.]]></c></em></tag>
+      <tag><c><![CDATA[{domain, Domain}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Domain = string()]]></c></p>
-        <p></p>
         <p>Set domain name.</p>
-        <p></p>
       </item>
-      <tag><em><c><![CDATA[{nameserver, IP [,Port]}.]]></c></em></tag>
+      <tag><c><![CDATA[{nameserver, IP [,Port]}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[IP = tuple()]]></c></p>
         <p><c><![CDATA[Port = integer()]]></c></p>
-        <p></p>
-        <p>Add address (and port, if other than default) of primary 
+        <p>Add address (and port, if other than default) of the primary
           nameserver to use for
-         <seealso marker="kernel:inet_res">inet_res</seealso>.</p>
-        <p></p>
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>.
+        </p>
       </item>
-      <tag><em><c><![CDATA[{alt_nameserver, IP [,Port]}.]]></c></em></tag>
+      <tag><c><![CDATA[{alt_nameserver, IP [,Port]}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[IP = tuple()]]></c></p>
         <p><c><![CDATA[Port = integer()]]></c></p>
-        <p></p>
-        <p>Add address (and port, if other than default) of secondary 
+        <p>Add address (and port, if other than default) of the secondary
           nameserver for
-         <seealso marker="kernel:inet_res">inet_res</seealso>.</p>
-        <p></p>
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>.
+        </p>
       </item>
-      <tag><em><c><![CDATA[{search, Domains}.]]></c></em></tag>
+      <tag><c><![CDATA[{search, Domains}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Domains = [string()]]]></c></p>
-        <p></p>
         <p>Add search domains for
-         <seealso marker="kernel:inet_res">inet_res</seealso>.</p>
-        <p></p>
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>.
+        </p>
       </item>
-      <tag><em><c><![CDATA[{lookup, Methods}.]]></c></em></tag>
+      <tag><c><![CDATA[{lookup, Methods}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Methods = [atom()]]]></c></p>
-        <p></p>
-        <p>Specify lookup methods and in which order to try them. 
-          The valid methods are: <c><![CDATA[native]]></c> (use system calls),
-          <c><![CDATA[file]]></c> (use host data retrieved from
-          system configuration files and/or 
-          the user configuration file) or <c><![CDATA[dns]]></c>
-          (use the Erlang DNS client
-          <seealso marker="kernel:inet_res">inet_res</seealso>
-          for nameserver queries).</p>
+        <p>Specify lookup methods and in which order to try them.
+          The valid methods are as follows:</p>
+        <list type="bulleted">
+          <item><c><![CDATA[native]]></c> (use system calls)</item>
+          <item><c><![CDATA[file]]></c> (use host data retrieved from system
+            configuration files and/or the user configuration file)</item>
+          <item><c><![CDATA[dns]]></c> (use the Erlang DNS client
+            <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>
+            for nameserver queries)</item>
+        </list>
 	<p>The lookup method <c><![CDATA[string]]></c> tries to
-	  parse the hostname as a IPv4 or IPv6 string and return
+	  parse the hostname as an IPv4 or IPv6 string and return
 	  the resulting IP address. It is automatically tried
 	  first when <c><![CDATA[native]]></c> is <em>not</em>
-	  in the <c><![CDATA[Methods]]></c> list. To skip it in this case
+	  in the <c><![CDATA[Methods]]></c> list. To skip it in this case,
 	  the pseudo lookup method <c><![CDATA[nostring]]></c> can be
 	  inserted anywhere in the <c><![CDATA[Methods]]></c> list.</p>
-        <p></p>
       </item>
-      <tag><em><c><![CDATA[{cache_size, Size}.]]></c></em></tag>
+      <tag><c><![CDATA[{cache_size, Size}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Size = integer()]]></c></p>
-        <p></p>
-        <p>Set size of resolver cache. Default is 100 DNS records.</p>
-        <p></p>
+        <p>Set the resolver cache size. Defaults to 100 DNS records.</p>
       </item>
-      <tag><em><c><![CDATA[{cache_refresh, Time}.]]></c></em></tag>
-      <item>
-        <p></p>
+      <tag><c><![CDATA[{cache_refresh, Time}.]]></c></tag>
+        <item>
         <p><c><![CDATA[Time = integer()]]></c></p>
-        <p></p>
-        <p>Set how often (in millisec)
-          the resolver cache for
-          <seealso marker="kernel:inet_res">inet_res</seealso>.
-          is refreshed (i.e. expired DNS records are deleted).
-          Default is 1 h.</p>
-        <p></p>
+        <p>Set how often (in milliseconds) the resolver cache for
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>
+          is refreshed (that is, expired DNS records are deleted).
+          Defaults to 1 hour.</p>
       </item>
-      <tag><em><c><![CDATA[{timeout, Time}.]]></c></em></tag>
+      <tag><c><![CDATA[{timeout, Time}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Time = integer()]]></c></p>
-        <p></p>
-        <p>Set the time to wait until retry (in millisec) for DNS queries
+        <p>Set the time to wait until retry (in milliseconds) for DNS queries
           made by
-          <seealso marker="kernel:inet_res">inet_res</seealso>.
-          Default is 2 sec.</p>
-        <p></p>
+          <seealso marker="kernel:inet_res"><c>kernel;inet_res</c></seealso>.
+          Defaults to 2 seconds.</p>
       </item>
-      <tag><em><c><![CDATA[{retry, N}.]]></c></em></tag>
+      <tag><c><![CDATA[{retry, N}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[N = integer()]]></c></p>
-        <p></p>
         <p>Set the number of DNS queries
-          <seealso marker="kernel:inet_res">inet_res</seealso>
-          will try before giving up.
-          Default is 3.</p>
-        <p></p>
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>
+          will try before giving up. Defaults to 3.</p>
       </item>
-      <tag><em><c><![CDATA[{inet6, Bool}.]]></c></em></tag>
+      <tag><c><![CDATA[{inet6, Bool}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Bool = true | false]]></c></p>
-        <p></p>
-        <p>Tells the DNS client 
-          <seealso marker="kernel:inet_res">inet_res</seealso>
-          to look up IPv6 addresses. Default is false.</p>
-        <p></p>
+        <p>Tells the DNS client
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>
+          to look up IPv6 addresses. Defaults to <c>false</c>.</p>
       </item>
-      <tag><em><c><![CDATA[{usevc, Bool}.]]></c></em></tag>
+      <tag><c><![CDATA[{usevc, Bool}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Bool = true | false]]></c></p>
-        <p></p>
-        <p>Tells the DNS client 
-          <seealso marker="kernel:inet_res">inet_res</seealso>
-          to use TCP (Virtual Circuit) instead of UDP. Default is false.</p>
-        <p></p>
+        <p>Tells the DNS client
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>
+          to use TCP (Virtual Circuit) instead of UDP. Defaults to
+          <c>false</c>.</p>
       </item>
-      <tag><em><c><![CDATA[{edns, Version}.]]></c></em></tag>
+      <tag><c><![CDATA[{edns, Version}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Version = false | 0]]></c></p>
-        <p></p>
         <p>Sets the EDNS version that
-          <seealso marker="kernel:inet_res">inet_res</seealso>
-          will use. The only allowed is zero. Default is false
-          which means to not use EDNS.</p>
-        <p></p>
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>
+          will use. The only allowed version is zero. Defaults to <c>false</c>,
+          which means not to use EDNS.</p>
       </item>
-      <tag><em><c><![CDATA[{udp_payload_size, Size}.]]></c></em></tag>
+      <tag><c><![CDATA[{udp_payload_size, Size}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[N = integer()]]></c></p>
-        <p></p>
         <p>Sets the allowed UDP payload size
-          <seealso marker="kernel:inet_res">inet_res</seealso>
+          <seealso marker="kernel:inet_res"><c>kernel:inet_res</c></seealso>
           will advertise in EDNS queries. Also sets the limit
           when the DNS query will be deemed too large for UDP
-          forcing a TCP query instead, which is not entirely
-          correct since the advertised UDP payload size of the
-          individual nameserver is what should be used,
+          forcing a TCP query instead; this  is not entirely
+          correct, as the advertised UDP payload size of the
+          individual nameserver is what is to be used,
           but this simple strategy will do until a more intelligent
-          (probing, caching) algorithm need be implemented.
-          The default is 1280 which stems from the
-          standard Ethernet MTU size.</p>
-        <p></p>
+          (probing, caching) algorithm needs to be implemented.
+          Default to 1280, which stems from the standard Ethernet MTU size.</p>
       </item>
-      <tag><em><c><![CDATA[{udp, Module}.]]></c></em></tag>
+      <tag><c><![CDATA[{udp, Module}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Module = atom()]]></c></p>
-        <p></p>
-        <p>Tell Erlang to use other primitive UDP module than inet_udp.</p>
-        <p></p>
+        <p>Tell Erlang to use another primitive UDP module than
+          <c>inet_udp</c>.</p>
       </item>
-      <tag><em><c><![CDATA[{tcp, Module}.]]></c></em></tag>
+      <tag><c><![CDATA[{tcp, Module}.]]></c></tag>
       <item>
-        <p></p>
         <p><c><![CDATA[Module = atom()]]></c></p>
-        <p></p>
-        <p>Tell Erlang to use other primitive TCP module than inet_tcp.</p>
-        <p></p>
+        <p>Tell Erlang to use another primitive TCP module than
+          <c>inet_tcp</c>.</p>
       </item>
-      <tag><em><c><![CDATA[clear_hosts.]]></c></em></tag>
+      <tag><c><![CDATA[clear_hosts.]]></c></tag>
       <item>
-        <p></p>
         <p>Clear the hosts table.</p>
-        <p></p>
       </item>
-      <tag><em><c><![CDATA[clear_ns.]]></c></em></tag>
+      <tag><c><![CDATA[clear_ns.]]></c></tag>
       <item>
-        <p></p>
         <p>Clear the list of recorded nameservers (primary and secondary).</p>
-        <p></p>
       </item>
-      <tag><em><c><![CDATA[clear_search.]]></c></em></tag>
+      <tag><c><![CDATA[clear_search.]]></c></tag>
       <item>
-        <p></p>
         <p>Clear the list of search domains.</p>
-        <p></p>
       </item>
     </taglist>
   </section>
 
   <section>
     <title>User Configuration Example</title>
-    <p>Here follows a user configuration example.</p>
-    <p>Assume a user does not want Erlang to use the native lookup method, 
-      but wants Erlang to read all information necessary from start and use 
-      that for resolving names and addresses. In case lookup fails, Erlang 
-      should request the data from a nameserver (using the Erlang 
+    <p>Assume that a user does not want Erlang to use the native lookup method,
+      but wants Erlang to read all information necessary from start and use
+      that for resolving names and addresses. If lookup fails, Erlang
+      is to request the data from a nameserver (using the Erlang
       DNS client, set to use EDNS allowing larger responses).
-      The resolver configuration will be updated when
-      its configuration file changes, furthermore, DNS records
-      should never be cached. The user configuration file
+      The resolver configuration is updated when
+      its configuration file changes. Also, DNS records
+      are never to be cached. The user configuration file
       (in this example named <c><![CDATA[erl_inetrc]]></c>, stored
-      in directory <c><![CDATA[./cfg_files]]></c>) could then look like this 
+      in directory <c><![CDATA[./cfg_files]]></c>) can then look as follows
       (Unix):</p>
+
     <pre>
-      %% -- ERLANG INET CONFIGURATION FILE --
-      %% read the hosts file
-      {file, hosts, "/etc/hosts"}.
-      %% add a particular host
-      {host, {134,138,177,105}, ["finwe"]}.
-      %% do not monitor the hosts file
-      {hosts_file, ""}.
-      %% read and monitor nameserver config from here
-      {resolv_conf, "/usr/local/etc/resolv.conf"}.
-      %% enable EDNS
-      {edns,0}.
-      %% disable caching
-      {cache_size, 0}.
-      %% specify lookup method
-      {lookup, [file, dns]}.</pre>
-    <p>And Erlang could, for example, be started like this:</p>
-    <p><c><![CDATA[% erl -sname my_node -kernel inetrc '"./cfg_files/erl_inetrc"']]></c></p>
+%% -- ERLANG INET CONFIGURATION FILE --
+%% read the hosts file
+{file, hosts, "/etc/hosts"}.
+%% add a particular host
+{host, {134,138,177,105}, ["finwe"]}.
+%% do not monitor the hosts file
+{hosts_file, ""}.
+%% read and monitor nameserver config from here
+{resolv_conf, "/usr/local/etc/resolv.conf"}.
+%% enable EDNS
+{edns,0}.
+%% disable caching
+{cache_size, 0}.
+%% specify lookup method
+{lookup, [file, dns]}.</pre>
+
+    <p>And Erlang can, for example, be started as follows:</p>
+
+    <code type="none"><![CDATA[
+% erl -sname my_node -kernel inetrc '"./cfg_files/erl_inetrc"']]></code>
   </section>
 </chapter>
 
diff --git a/erts/doc/src/init.xml b/erts/doc/src/init.xml
index a88a815ef6..54507c6572 100644
--- a/erts/doc/src/init.xml
+++ b/erts/doc/src/init.xml
@@ -19,7 +19,7 @@
       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
       See the License for the specific language governing permissions and
       limitations under the License.
-    
+
     </legalnotice>
 
     <title>init</title>
@@ -30,128 +30,140 @@
     <file>init.xml</file>
   </header>
   <module>init</module>
-  <modulesummary>Coordination of System Startup</modulesummary>
+  <modulesummary>Coordination of system startup.</modulesummary>
   <description>
-    <p>The <c>init</c> module is pre-loaded and contains the code for
-      the <c>init</c> system process which coordinates the start-up of
-      the system. The first function evaluated at start-up is
-      <c>boot(BootArgs)</c>, where <c>BootArgs</c> is a list of command
-      line arguments supplied to the Erlang runtime system from
-      the local operating system. See
-      <seealso marker="erts:erl">erl(1)</seealso>.</p>
-    <p><c>init</c> reads the boot script which contains instructions on
-      how to initiate the system. See
-      <seealso marker="sasl:script">script(4)</seealso> for more
-      information about boot scripts.</p>
+    <p>This module is preloaded and contains the code for
+      the <c>init</c> system process that coordinates the startup of
+      the system. The first function evaluated at startup is
+      <c>boot(BootArgs)</c>, where <c>BootArgs</c> is a list of
+      command-line arguments supplied to the Erlang runtime system from
+      the local operating system; see
+      <seealso marker="erts:erl"><c>erl(1)</c></seealso>.</p>
+
+    <p><c>init</c> reads the boot script, which contains instructions on
+      how to initiate the system. For more information about boot scripts, see
+      <seealso marker="sasl:script"><c>sasl:script(4)</c></seealso>.</p>
+
     <p><c>init</c> also contains functions to restart, reboot, and stop
       the system.</p>
   </description>
+
   <funcs>
     <func>
       <name name="boot" arity="1"/>
-      <fsummary>Start the Erlang runtime system</fsummary>
+      <fsummary>Start the Erlang runtime system.</fsummary>
       <desc>
         <p>Starts the Erlang runtime system. This function is called
-          when the emulator is started and coordinates system start-up.</p>
-        <p><c><anno>BootArgs</anno></c> are all command line arguments except
-          the emulator flags, that is, flags and plain arguments. See
-          <seealso marker="erts:erl">erl(1)</seealso>.</p>
-        <p><c>init</c> itself interprets some of the flags, see
-          <seealso marker="#flags">Command Line Flags</seealso> below.
+          when the emulator is started and coordinates system startup.</p>
+        <p><c><anno>BootArgs</anno></c> are all command-line arguments except
+          the emulator flags, that is, flags and plain arguments; see
+          <seealso marker="erts:erl"><c>erl(1)</c></seealso>.</p>
+        <p><c>init</c> interprets some of the flags, see section
+          <seealso marker="#flags">Command-Line Flags</seealso> below.
           The remaining flags ("user flags") and plain arguments are
           passed to the <c>init</c> loop and can be retrieved by calling
-          <c>get_arguments/0</c> and <c>get_plain_arguments/0</c>,
-          respectively.</p>
+          <seealso marker="#get_arguments/0"><c>get_arguments/0</c></seealso>
+          and <seealso marker="#get_plain_arguments/0">
+          <c>get_plain_arguments/0</c></seealso>, respectively.</p>
       </desc>
     </func>
+
     <func>
       <name name="get_argument" arity="1"/>
-      <fsummary>Get the values associated with a command line user flag</fsummary>
+      <fsummary>Get the values associated with a command-line user flag.
+      </fsummary>
       <desc>
-        <p>Returns all values associated with the command line user flag
-          <c><anno>Flag</anno></c>. If <c><anno>Flag</anno></c> is provided several times, each
-          <c><anno>Values</anno></c> is returned in preserved order.</p>
+        <p>Returns all values associated with the command-line user flag
+          <c><anno>Flag</anno></c>. If <c><anno>Flag</anno></c> is provided
+          several times, each <c><anno>Values</anno></c> is returned in
+          preserved order. Example:</p>
         <pre>
 % <input>erl -a b c -a d</input>
 ...
 1> <input>init:get_argument(a).</input>
 {ok,[["b","c"],["d"]]}</pre>
-        <p>There are also a number of flags, which are defined
+        <p>The following flags are defined
           automatically and can be retrieved using this function:</p>
         <taglist>
           <tag><c>root</c></tag>
           <item>
-            <p>The installation directory of Erlang/OTP, <c>$ROOT</c>.</p>
+            <p>The installation directory of Erlang/OTP, <c>$ROOT</c>:</p>
             <pre>
 2> <input>init:get_argument(root).</input>
 {ok,[["/usr/local/otp/releases/otp_beam_solaris8_r10b_patched"]]}</pre>
           </item>
           <tag><c>progname</c></tag>
           <item>
-            <p>The name of the program which started Erlang.</p>
+            <p>The name of the program which started Erlang:</p>
             <pre>
 3> <input>init:get_argument(progname).</input>
 {ok,[["erl"]]}</pre>
           </item>
           <tag><c>home</c></tag>
           <item>
-            <p>The home directory.</p>
+            <p>The home directory:</p>
             <pre>
 4> <input>init:get_argument(home).</input>
 {ok,[["/home/harry"]]}</pre>
           </item>
         </taglist>
-        <p>Returns <c>error</c> if there is no value associated with
-          <c>Flag</c>.</p>
+        <p>Returns <c>error</c> if no value is associated with <c>Flag</c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="get_arguments" arity="0"/>
-      <fsummary>Get all command line user flags</fsummary>
+      <fsummary>Get all command-line user flags.</fsummary>
       <desc>
-        <p>Returns all command line flags, as well as the system
-          defined flags, see <c>get_argument/1</c>.</p>
+        <p>Returns all command-line flags and the system-defined flags, see
+          <seealso marker="#get_argument/1"><c>get_argument/1</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="get_plain_arguments" arity="0"/>
-      <fsummary>Get all non-flag command line arguments</fsummary>
+      <fsummary>Get all non-flag command-line arguments.</fsummary>
       <desc>
-        <p>Returns any plain command line arguments as a list of strings
+        <p>Returns any plain command-line arguments as a list of strings
           (possibly empty).</p>
       </desc>
     </func>
+
     <func>
       <name name="get_status" arity="0"/>
-      <fsummary>Get system status information</fsummary>
+      <fsummary>Get system status information.</fsummary>
       <type name="internal_status"/>
       <desc>
         <p>The current status of the <c>init</c> process can be
           inspected. During system startup (initialization),
           <c><anno>InternalStatus</anno></c> is <c>starting</c>, and
-          <c><anno>ProvidedStatus</anno></c> indicates how far the boot script has
-          been interpreted. Each <c>{progress, Info}</c> term
-          interpreted in the boot script affects <c><anno>ProvidedStatus</anno></c>,
-          that is, <c><anno>ProvidedStatus</anno></c> gets the value of <c>Info</c>.</p>
+          <c><anno>ProvidedStatus</anno></c> indicates how far the boot
+          script has been interpreted. Each <c>{progress, Info}</c> term
+          interpreted in the boot script affects
+          <c><anno>ProvidedStatus</anno></c>, that is,
+          <c><anno>ProvidedStatus</anno></c> gets the value of <c>Info</c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="reboot" arity="0"/>
-      <fsummary>Take down and restart an Erlang node smoothly</fsummary>
+      <fsummary>Take down and restart an Erlang node smoothly.</fsummary>
       <desc>
         <p>All applications are taken down smoothly, all code is
           unloaded, and all ports are closed before the system
-          terminates. If the <c>-heart</c> command line flag was given,
-          the <c>heart</c> program will try to reboot the system. Refer
-          to <c>heart(3)</c> for more information.</p>
+          terminates. If command-line flag <c>-heart</c> was specified,
+          the <c>heart</c> program tries to reboot the system. For more
+          information, see
+          <seealso marker="kernel:heart"><c>kernel:heart(3)</c></seealso>.</p>
         <p>To limit the shutdown time, the time <c>init</c> is allowed
-          to spend taking down applications, the <c>-shutdown_time</c>
-          command line flag should be used.</p>
+          to spend taking down applications, command-line flag
+          <c>-shutdown_time</c> is to be used.</p>
       </desc>
     </func>
+
     <func>
       <name name="restart" arity="0"/>
-      <fsummary>Restart the running Erlang node</fsummary>
+      <fsummary>Restart the running Erlang node.</fsummary>
       <desc>
         <p>The system is restarted <em>inside</em> the running Erlang
           node, which means that the emulator is not restarted. All
@@ -160,80 +172,91 @@
           the same way as initially started. The same <c>BootArgs</c>
           are used again.</p>
         <p>To limit the shutdown time, the time <c>init</c> is allowed
-          to spend taking down applications, the <c>-shutdown_time</c>
-          command line flag should be used.</p>
+          to spend taking down applications, command-line flag
+          <c>-shutdown_time</c> is to be used.</p>
       </desc>
     </func>
+
     <func>
       <name name="script_id" arity="0"/>
-      <fsummary>Get the identity of the used boot script</fsummary>
+      <fsummary>Get the identity of the used boot script.</fsummary>
       <desc>
-        <p>Get the identity of the boot script used to boot the system.
+        <p>Gets the identity of the boot script used to boot the system.
           <c><anno>Id</anno></c> can be any Erlang term. In the delivered boot
-          scripts, <c><anno>Id</anno></c> is <c>{Name, Vsn}</c>. <c>Name</c> and
-          <c>Vsn</c> are strings.</p>
+          scripts, <c><anno>Id</anno></c> is <c>{Name, Vsn}</c>. <c>Name</c>
+          and <c>Vsn</c> are strings.</p>
       </desc>
     </func>
+
     <func>
       <name name="stop" arity="0"/>
-      <fsummary>Take down an Erlang node smoothly</fsummary>
+      <fsummary>Take down an Erlang node smoothly.</fsummary>
       <desc>
         <p>The same as
 	<seealso marker="#stop/1"><c>stop(0)</c></seealso>.</p>
       </desc>
     </func>
+
     <func>
       <name name="stop" arity="1"/>
-      <fsummary>Take down an Erlang node smoothly</fsummary>
+      <fsummary>Take down an Erlang node smoothly.</fsummary>
       <desc>
         <p>All applications are taken down smoothly, all code is
           unloaded, and all ports are closed before the system
-          terminates by calling <c>halt(<anno>Status</anno>)</c>. If the
-          <c>-heart</c> command line flag was given, the <c>heart</c>
-          program is terminated before the Erlang node
-          terminates. Refer to <c>heart(3)</c> for more
-          information.</p>
+          terminates by calling <c>halt(<anno>Status</anno>)</c>. If
+          command-line flag <c>-heart</c> was specified, the <c>heart</c>
+          program is terminated before the Erlang node terminates.
+          For more information, see
+          <seealso marker="kernel:heart"><c>kernel:heart(3)</c></seealso>.</p>
         <p>To limit the shutdown time, the time <c>init</c> is allowed
-          to spend taking down applications, the <c>-shutdown_time</c>
-          command line flag should be used.</p>
+          to spend taking down applications, command-line flag
+          <c>-shutdown_time</c> is to be used.</p>
       </desc>
     </func>
   </funcs>
 
   <section>
     <marker id="flags"></marker>
-    <title>Command Line Flags</title>
-    <warning><p>The support for loading of code from archive files is
-     experimental. The sole purpose of releasing it before it is ready
-     is to obtain early feedback. The file format, semantics,
-     interfaces etc. may be changed in a future release. The
-     <c>-code_path_choice</c> flag is also experimental.</p></warning>
+    <title>Command-Line Flags</title>
+    <warning>
+      <p>The support for loading of code from archive files is
+        experimental. The only purpose of releasing it before it is ready
+	is to obtain early feedback. The file format, semantics,
+	interfaces, and so on, can  be changed in a future release. The
+        <c>-code_path_choice</c> flag is also experimental.</p>
+    </warning>
 
-    <p>The <c>init</c> module interprets the following command line
-      flags:</p>
+    <p>The <c>init</c> module interprets the following command-line flags:</p>
 
     <taglist>
       <tag><c>--</c></tag>
       <item>
         <p>Everything following <c>--</c> up to the next flag is
           considered plain arguments and can be retrieved using
-          <c>get_plain_arguments/0</c>.</p>
+          <seealso marker="#get_plain_arguments/0">
+          <c>get_plain_arguments/0</c></seealso>.</p>
       </item>
       <tag><c>-code_path_choice Choice</c></tag>
       <item>
-        <p>This flag can be set to <c>strict</c> or <c>relaxed</c>. It
-         controls whether each directory in the code path should be
-         interpreted strictly as it appears in the <c>boot script</c> or if
-         <c>init</c> should be more relaxed and try to find a suitable
-         directory if it can choose from a regular ebin directory and
-         an ebin directory in an archive file. This flag is particular
-         useful when you want to elaborate with code loading from
-         archives without editing the <c>boot script</c>. See <seealso
-         marker="sasl:script">script(4)</seealso> for more information
-         about interpretation of boot scripts. The flag does also have
-         a similar affect on how the code server works. See <seealso
-         marker="kernel:code">code(3)</seealso>.</p>
-	 
+        <p>Can be set to <c>strict</c> or <c>relaxed</c>. It controls how each
+          directory in the code path is to be interpreted:</p>
+        <list type="bulleted">
+          <item>
+            <p>Strictly as it appears in the <c>boot script</c>, or</p>
+          </item>
+          <item>
+            <p><c>init</c> is to be more relaxed and try to find a suitable
+              directory if it can choose from a regular <c>ebin</c> directory
+              and an <c>ebin</c> directory in an archive file.</p>
+          </item>
+        </list>
+        <p>This flag is particular
+          useful when you want to elaborate with code loading from
+          archives without editing the <c>boot script</c>. For more
+          information about interpretation of boot scripts, see
+          <seealso marker="sasl:script"><c>sasl:script(4)</c></seealso>.
+          The flag has also a similar effect on how the code server works; see
+          <seealso marker="kernel:code"><c>kernel:code(3)</c></seealso>.</p>
       </item>
       <tag><c>-epmd_module Module</c></tag>
       <item>
@@ -242,11 +265,11 @@
       </item>
       <tag><c>-eval Expr</c></tag>
       <item>
-        <p>Scans, parses and evaluates an arbitrary expression
+        <p>Scans, parses, and evaluates an arbitrary expression
           <c>Expr</c> during system initialization. If any of these
-          steps fail (syntax error, parse error or exception during
-          evaluation), Erlang stops with an error message. Here is an
-          example that uses Erlang as a hexadecimal calculator:</p>
+          steps fail (syntax error, parse error, or exception during
+          evaluation), Erlang stops with an error message. In the following
+          example Erlang is used as a hexadecimal calculator:</p>
         <pre>
 % <input>erl -noshell -eval 'R = 16#1F+16#A0, io:format("~.16B~n", [R])' \\</input>
 <input>-s erlang halt</input>
@@ -256,14 +279,15 @@ BF</pre>
           <c>-eval</c> expressions are evaluated sequentially with
           <c>-s</c> and <c>-run</c> function calls (this also in
           the order specified). As with <c>-s</c> and <c>-run</c>, an
-          evaluation that does not terminate, blocks the system
+          evaluation that does not terminate blocks the system
           initialization process.</p>
       </item>
       <tag><c>-extra</c></tag>
       <item>
         <p>Everything following <c>-extra</c> is considered plain
           arguments and can be retrieved using
-          <c>get_plain_arguments/0</c>.</p>
+          <seealso marker="#get_plain_arguments/0">
+          <c>get_plain_arguments/0</c></seealso>.</p>
       </item>
       <tag><c>-run Mod [Func [Arg1, Arg2, ...]]</c></tag>
       <item>
@@ -285,8 +309,8 @@ foo:bar()
 foo:bar(["baz", "1", "2"]).</code>
         <p>The functions are executed sequentially in an initialization
           process, which then terminates normally and passes control to
-          the user. This means that a <c>-run</c> call which does not
-          return will block further processing; to avoid this, use
+          the user. This means that a <c>-run</c> call that does not
+          return blocks further processing; to avoid this, use
           some variant of <c>spawn</c> in such cases.</p>
       </item>
       <tag><c>-s Mod [Func [Arg1, Arg2, ...]]</c></tag>
@@ -309,11 +333,11 @@ foo:bar()
 foo:bar([baz, '1', '2']).</code>
         <p>The functions are executed sequentially in an initialization
           process, which then terminates normally and passes control to
-          the user. This means that a <c>-s</c> call which does not
-          return will block further processing; to avoid this, use
+          the user. This means that a <c>-s</c> call that does not
+          return blocks further processing; to avoid this, use
           some variant of <c>spawn</c> in such cases.</p>
-        <p>Due to the limited length of atoms, it is recommended that
-          <c>-run</c> be used instead.</p>
+        <p>Because of the limited length of atoms, it is recommended to
+          use <c>-run</c> instead.</p>
       </item>
     </taglist>
   </section>
@@ -335,9 +359,9 @@ error</pre>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p><seealso marker="erl_prim_loader">erl_prim_loader(3)</seealso>, 
-      <seealso marker="kernel:heart">heart(3)</seealso></p>
+    <title>See Also</title>
+    <p><seealso marker="erl_prim_loader"><c>erl_prim_loader(3)</c></seealso>, 
+      <seealso marker="kernel:heart"><c>kernel:heart(3)</c></seealso></p>
   </section>
 </erlref>
 
diff --git a/erts/doc/src/introduction.xml b/erts/doc/src/introduction.xml
new file mode 100644
index 0000000000..97a0d5999e
--- /dev/null
+++ b/erts/doc/src/introduction.xml
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE chapter SYSTEM "chapter.dtd">
+
+<chapter>
+  <header>
+    <copyright>
+      <year>2012</year><year>2016</year>
+      <holder>Ericsson AB. All Rights Reserved.</holder>
+    </copyright>
+    <legalnotice>
+      Licensed under the Apache License, Version 2.0 (the "License");
+      you may not use this file except in compliance with the License.
+      You may obtain a copy of the License at
+ 
+          http://www.apache.org/licenses/LICENSE-2.0
+
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+
+    </legalnotice>
+
+    <title>Introduction</title>
+    <prepared></prepared>
+    <responsible></responsible>
+    <docno></docno>
+    <approved></approved>
+    <checked></checked>
+    <date>2016-05-22</date>
+    <rev>PA1</rev>
+    <file>introduction.xml</file>
+  </header>
+  <section>
+    <title>Scope</title>
+    <p>The Erlang Runtime System Application, <c>ERTS</c>, contains
+      functionality necessary to run the Erlang system.</p>
+    <note>
+      <p>By default, <c><![CDATA[ERTS]]></c> is only guaranteed to be
+        compatible with other Erlang/OTP components from the same release as
+        <c><![CDATA[ERTS]]></c> itself.</p>
+      <p>For information on how to communicate with Erlang/OTP components
+        from earlier releases, see the documentation of system flag
+        <seealso marker="erl#compat_rel"><c>+R</c></seealso> in <c>erl(1)</c>.
+      </p>
+    </note>
+  </section>
+
+  <section>
+    <title>Prerequisites</title>
+    <p>It is assumed that the reader is familiar with the Erlang programming
+      language.</p> 
+  </section>
+</chapter>
+
diff --git a/erts/doc/src/match_spec.xml b/erts/doc/src/match_spec.xml
index 7be3d15de6..ee50815fde 100644
--- a/erts/doc/src/match_spec.xml
+++ b/erts/doc/src/match_spec.xml
@@ -22,7 +22,7 @@
 
     </legalnotice>
 
-    <title>Match specifications in Erlang</title>
+    <title>Match Specifications in Erlang</title>
     <prepared>Patrik Nyblom</prepared>
     <responsible></responsible>
     <docno></docno>
@@ -32,43 +32,54 @@
     <rev>PA1</rev>
     <file>match_spec.xml</file>
   </header>
-  <p>A "match specification" (match_spec) is an Erlang term describing a
-    small "program" that will try to match something. It can be used
+  <p>A "match specification" (<c>match_spec</c>) is an Erlang term describing a
+    small "program" that tries to match something. It can be used
     to either control tracing with
     <seealso marker="erlang#trace_pattern/3">erlang:trace_pattern/3</seealso>
     or to search for objects in an ETS table with for example
     <seealso marker="stdlib:ets#select/2">ets:select/2</seealso>.
-    The match_spec in many ways works like a small function in Erlang, but is
-    interpreted/compiled by the Erlang runtime system to something much more
-    efficient than calling an Erlang function. The match_spec is also
+    The match specification in many ways works like a small function in Erlang,
+    but is interpreted/compiled by the Erlang runtime system to something much more
+    efficient than calling an Erlang function. The match specification is also
     very limited compared to the expressiveness of real Erlang functions.</p>
-  <p>The most notable difference between a match_spec and an Erlang fun is
-    of course the syntax. Match specifications are Erlang terms, not
-    Erlang code.  A match_spec also has a somewhat strange concept of
-    exceptions. An exception (e.g., <c><![CDATA[badarg]]></c>) in the <c><![CDATA[MatchCondition]]></c>
-    part,
-    which resembles an Erlang guard, will generate immediate failure,
-    while an exception in the <c><![CDATA[MatchBody]]></c> part, which resembles the body of an
-    Erlang function, is implicitly caught and results in the single atom
-    <c><![CDATA['EXIT']]></c>.
-    </p>
+  <p>The most notable difference between a match specification and an Erlang
+    fun is the syntax. Match specifications are Erlang terms, not Erlang code.
+    Also, a match specification has a strange concept of exceptions:</p>
+
+  <list type="bulleted">
+    <item>
+      <p>An exception (such as <c><![CDATA[badarg]]></c>) in the
+        <c><![CDATA[MatchCondition]]></c> part, which resembles an Erlang guard,
+        generates immediate failure.</p>
+    </item>
+    <item>
+      <p>An exception in the <c><![CDATA[MatchBody]]></c> part, which resembles
+        the body of an Erlang function, is implicitly caught and results in the
+        single atom <c><![CDATA['EXIT']]></c>.</p>
+    </item>
+  </list>
 
   <section>
     <title>Grammar</title>
-    <p>A match_spec used in tracing can be described in this <em>informal</em> grammar:</p>
+    <p>A match specification used in tracing can be described in the following
+      <em>informal</em> grammar:</p>
+
     <list type="bulleted">
       <item>MatchExpression ::= [ MatchFunction, ... ]
       </item>
       <item>MatchFunction ::= { MatchHead, MatchConditions, MatchBody }
       </item>
-      <item>MatchHead ::=  MatchVariable | <c><![CDATA['_']]></c> | [ MatchHeadPart, ... ]
+      <item>MatchHead ::=  MatchVariable | <c><![CDATA['_']]></c> |
+        [ MatchHeadPart, ... ]
+      </item>
+      <item>MatchHeadPart ::= term() | MatchVariable | <c><![CDATA['_']]></c>
       </item>
-      <item>MatchHeadPart ::= term() | MatchVariable | <c><![CDATA['_']]></c></item>
       <item>MatchVariable ::= '$&lt;number&gt;'
       </item>
-      <item>MatchConditions ::= [ MatchCondition, ...] | <c><![CDATA[[]]]></c></item>
-      <item>MatchCondition ::= { GuardFunction } | 
-       { GuardFunction, ConditionExpression, ... }
+      <item>MatchConditions ::= [ MatchCondition, ...] | <c><![CDATA[[]]]></c>
+      </item>
+      <item>MatchCondition ::= { GuardFunction } | { GuardFunction,
+        ConditionExpression, ... }
       </item>
       <item>BoolFunction ::= <c><![CDATA[is_atom]]></c> |
         <c><![CDATA[is_float]]></c> | <c><![CDATA[is_integer]]></c> |
@@ -79,58 +90,77 @@
         <c><![CDATA[is_function]]></c> | <c><![CDATA[is_record]]></c> |
         <c><![CDATA[is_seq_trace]]></c> | <c><![CDATA['and']]></c> |
         <c><![CDATA['or']]></c> | <c><![CDATA['not']]></c> |
-        <c><![CDATA['xor']]></c> | <c><![CDATA[andalso]]></c> |
-        <c><![CDATA[orelse]]></c></item>
+        <c><![CDATA['xor']]></c> | <c><![CDATA['andalso']]></c> |
+        <c><![CDATA['orelse']]></c>
+      </item>
       <item>ConditionExpression ::= ExprMatchVariable | { GuardFunction } |
-       { GuardFunction, ConditionExpression, ... } | TermConstruct
+        { GuardFunction, ConditionExpression, ... } | TermConstruct
+      </item>
+      <item>ExprMatchVariable ::= MatchVariable (bound in the MatchHead) |
+        <c><![CDATA['$_']]></c> | <c><![CDATA['$$']]></c>
       </item>
-      <item>ExprMatchVariable ::= MatchVariable (bound in the MatchHead) | 
-      <c><![CDATA['$_']]></c> | <c><![CDATA['$$']]></c></item>
       <item>TermConstruct = {{}} | {{ ConditionExpression, ... }} |
         <c><![CDATA[[]]]></c> | [ConditionExpression, ...] |
         <c><![CDATA[#{}]]></c> | #{term() => ConditionExpression, ...} |
-        NonCompositeTerm | Constant</item>
-      <item>NonCompositeTerm ::= term() (not list or tuple or map)</item>
+        NonCompositeTerm | Constant
+      </item>
+      <item>NonCompositeTerm ::= term() (not list or tuple or map)
+      </item>
       <item>Constant ::= {<c><![CDATA[const]]></c>, term()}
       </item>
       <item>GuardFunction ::= BoolFunction | <c><![CDATA[abs]]></c> |
-      <c><![CDATA[element]]></c> | <c><![CDATA[hd]]></c> | <c><![CDATA[length]]></c> | <c><![CDATA[node]]></c> |
-      <c><![CDATA[round]]></c> | <c><![CDATA[size]]></c> | <c><![CDATA[tl]]></c> | <c><![CDATA[trunc]]></c> |
-      <c><![CDATA['+']]></c> | <c><![CDATA['-']]></c> | <c><![CDATA['*']]></c> | <c><![CDATA['div']]></c> |
-      <c><![CDATA['rem']]></c> | <c><![CDATA['band']]></c> | <c><![CDATA['bor']]></c> | <c><![CDATA['bxor']]></c> |
-      <c><![CDATA['bnot']]></c> | <c><![CDATA['bsl']]></c> | <c><![CDATA['bsr']]></c> | <c><![CDATA['>']]></c> | 
-      <c><![CDATA['>=']]></c> | <c><![CDATA['<']]></c> | <c><![CDATA['=<']]></c> | <c><![CDATA['=:=']]></c> | 
-      <c><![CDATA['==']]></c> | <c><![CDATA['=/=']]></c> | <c><![CDATA['/=']]></c> | <c><![CDATA[self]]></c> |
-      <c><![CDATA[get_tcw]]></c></item>
+        <c><![CDATA[element]]></c> | <c><![CDATA[hd]]></c> |
+        <c><![CDATA[length]]></c> | <c><![CDATA[node]]></c> |
+        <c><![CDATA[round]]></c> | <c><![CDATA[size]]></c> |
+        <c><![CDATA[tl]]></c> | <c><![CDATA[trunc]]></c> |
+        <c><![CDATA['+']]></c> | <c><![CDATA['-']]></c> |
+        <c><![CDATA['*']]></c> | <c><![CDATA['div']]></c> |
+        <c><![CDATA['rem']]></c> | <c><![CDATA['band']]></c> |
+        <c><![CDATA['bor']]></c> | <c><![CDATA['bxor']]></c> |
+        <c><![CDATA['bnot']]></c> | <c><![CDATA['bsl']]></c> |
+        <c><![CDATA['bsr']]></c> | <c><![CDATA['>']]></c> |
+        <c><![CDATA['>=']]></c> | <c><![CDATA['<']]></c> |
+        <c><![CDATA['=<']]></c> | <c><![CDATA['=:=']]></c> |
+        <c><![CDATA['==']]></c> | <c><![CDATA['=/=']]></c> |
+        <c><![CDATA['/=']]></c> | <c><![CDATA[self]]></c> |
+        <c><![CDATA[get_tcw]]></c>
+      </item>
       <item>MatchBody ::= [ ActionTerm ]
       </item>
       <item>ActionTerm ::= ConditionExpression | ActionCall
       </item>
-      <item>ActionCall ::= {ActionFunction} | 
-       {ActionFunction, ActionTerm, ...}
+      <item>ActionCall ::= {ActionFunction} | {ActionFunction, ActionTerm, ...}
       </item>
       <item>ActionFunction ::= <c><![CDATA[set_seq_token]]></c> |
-      <c><![CDATA[get_seq_token]]></c> | <c><![CDATA[message]]></c> |
-      <c><![CDATA[return_trace]]></c> | <c><![CDATA[exception_trace]]></c> | <c><![CDATA[process_dump]]></c> |
-      <c><![CDATA[enable_trace]]></c> | <c><![CDATA[disable_trace]]></c> | <c><![CDATA[trace]]></c> |
-      <c><![CDATA[display]]></c> | <c><![CDATA[caller]]></c> | <c><![CDATA[set_tcw]]></c> |
-      <c><![CDATA[silent]]></c></item>
+        <c><![CDATA[get_seq_token]]></c> | <c><![CDATA[message]]></c> |
+        <c><![CDATA[return_trace]]></c> | <c><![CDATA[exception_trace]]></c> |
+        <c><![CDATA[process_dump]]></c> | <c><![CDATA[enable_trace]]></c> |
+        <c><![CDATA[disable_trace]]></c> | <c><![CDATA[trace]]></c> |
+        <c><![CDATA[display]]></c> | <c><![CDATA[caller]]></c> |
+        <c><![CDATA[set_tcw]]></c> | <c><![CDATA[silent]]></c>
+      </item>
     </list>
 
-    <p>A match_spec used in ets can be described in this <em>informal</em> grammar:</p>
+    <p>A match specification  used in
+      <seealso marker="stdlib:ets"><c>stdlib:ets</c></seealso>
+      can be described in the following <em>informal</em> grammar:</p>
+
     <list type="bulleted">
       <item>MatchExpression ::= [ MatchFunction, ... ]
       </item>
       <item>MatchFunction ::= { MatchHead, MatchConditions, MatchBody }
       </item>
-      <item>MatchHead ::=  MatchVariable | <c><![CDATA['_']]></c> | { MatchHeadPart, ... }
+      <item>MatchHead ::=  MatchVariable | <c><![CDATA['_']]></c> |
+        { MatchHeadPart, ... }
+      </item>
+      <item>MatchHeadPart ::= term() | MatchVariable | <c><![CDATA['_']]></c>
       </item>
-      <item>MatchHeadPart ::= term() | MatchVariable | <c><![CDATA['_']]></c></item>
       <item>MatchVariable ::= '$&lt;number&gt;'
       </item>
-      <item>MatchConditions ::= [ MatchCondition, ...] | <c><![CDATA[[]]]></c></item>
+      <item>MatchConditions ::= [ MatchCondition, ...] | <c><![CDATA[[]]]></c>
+      </item>
       <item>MatchCondition ::= { GuardFunction } |
-       { GuardFunction, ConditionExpression, ... }
+        { GuardFunction, ConditionExpression, ... }
       </item>
       <item>BoolFunction ::= <c><![CDATA[is_atom]]></c> |
         <c><![CDATA[is_float]]></c> | <c><![CDATA[is_integer]]></c> |
@@ -141,243 +171,324 @@
         <c><![CDATA[is_function]]></c> | <c><![CDATA[is_record]]></c> |
         <c><![CDATA[is_seq_trace]]></c> | <c><![CDATA['and']]></c> |
         <c><![CDATA['or']]></c> | <c><![CDATA['not']]></c> |
-        <c><![CDATA['xor']]></c> | <c><![CDATA[andalso]]></c> |
-        <c><![CDATA[orelse]]></c></item>
+        <c><![CDATA['xor']]></c> | <c><![CDATA['andalso']]></c> |
+        <c><![CDATA['orelse']]></c>
+      </item>
       <item>ConditionExpression ::= ExprMatchVariable | { GuardFunction } |
-       { GuardFunction, ConditionExpression, ... } | TermConstruct
+        { GuardFunction, ConditionExpression, ... } | TermConstruct
       </item>
       <item>ExprMatchVariable ::= MatchVariable (bound in the MatchHead) |
-      <c><![CDATA['$_']]></c> | <c><![CDATA['$$']]></c></item>
+        <c><![CDATA['$_']]></c> | <c><![CDATA['$$']]></c>
+      </item>
       <item>TermConstruct = {{}} | {{ ConditionExpression, ... }} |
         <c><![CDATA[[]]]></c> | [ConditionExpression, ...] | #{} |
-        #{term() => ConditionExpression, ...} | NonCompositeTerm |
-        Constant</item>
-      <item>NonCompositeTerm ::= term() (not list or tuple or map)</item>
+        #{term() => ConditionExpression, ...} | NonCompositeTerm | Constant
+      </item>
+      <item>NonCompositeTerm ::= term() (not list or tuple or map)
+      </item>
       <item>Constant ::= {<c><![CDATA[const]]></c>, term()}
       </item>
       <item>GuardFunction ::= BoolFunction | <c><![CDATA[abs]]></c> |
-      <c><![CDATA[element]]></c> | <c><![CDATA[hd]]></c> | <c><![CDATA[length]]></c> | <c><![CDATA[node]]></c> |
-      <c><![CDATA[round]]></c> | <c><![CDATA[size]]></c> | <c><![CDATA[tl]]></c> | <c><![CDATA[trunc]]></c> |
-      <c><![CDATA['+']]></c> | <c><![CDATA['-']]></c> | <c><![CDATA['*']]></c> | <c><![CDATA['div']]></c> |
-      <c><![CDATA['rem']]></c> | <c><![CDATA['band']]></c> | <c><![CDATA['bor']]></c> | <c><![CDATA['bxor']]></c> |
-      <c><![CDATA['bnot']]></c> | <c><![CDATA['bsl']]></c> | <c><![CDATA['bsr']]></c> | <c><![CDATA['>']]></c> |
-      <c><![CDATA['>=']]></c> | <c><![CDATA['<']]></c> | <c><![CDATA['=<']]></c> | <c><![CDATA['=:=']]></c> |
-      <c><![CDATA['==']]></c> | <c><![CDATA['=/=']]></c> | <c><![CDATA['/=']]></c> | <c><![CDATA[self]]></c> |
-      <c><![CDATA[get_tcw]]></c></item>
-      <item>MatchBody ::= [ ConditionExpression, ... ]</item>
+        <c><![CDATA[element]]></c> | <c><![CDATA[hd]]></c> |
+        <c><![CDATA[length]]></c> | <c><![CDATA[node]]></c> |
+        <c><![CDATA[round]]></c> | <c><![CDATA[size]]></c> |
+        <c><![CDATA[tl]]></c> | <c><![CDATA[trunc]]></c> |
+        <c><![CDATA['+']]></c> | <c><![CDATA['-']]></c> |
+        <c><![CDATA['*']]></c> | <c><![CDATA['div']]></c> |
+        <c><![CDATA['rem']]></c> | <c><![CDATA['band']]></c> |
+        <c><![CDATA['bor']]></c> | <c><![CDATA['bxor']]></c> |
+        <c><![CDATA['bnot']]></c> | <c><![CDATA['bsl']]></c> |
+        <c><![CDATA['bsr']]></c> | <c><![CDATA['>']]></c> |
+        <c><![CDATA['>=']]></c> | <c><![CDATA['<']]></c> |
+        <c><![CDATA['=<']]></c> | <c><![CDATA['=:=']]></c> |
+        <c><![CDATA['==']]></c> | <c><![CDATA['=/=']]></c> |
+        <c><![CDATA['/=']]></c> | <c><![CDATA[self]]></c> |
+        <c><![CDATA[get_tcw]]></c>
+      </item>
+      <item>MatchBody ::= [ ConditionExpression, ... ]
+      </item>
     </list>
   </section>
 
   <section>
-    <title>Function descriptions</title>
-
+    <title>Function Descriptions</title>
     <section>
-      <title>Functions allowed in all types of match specifications</title>
-      <p>The different functions allowed in <c><![CDATA[match_spec]]></c> work like this:
-        </p>
-      <p><em>is_atom, is_float, is_integer, is_list, is_number, is_pid, is_port,
-        is_reference, is_tuple, is_map, is_binary, is_function:</em> Like the
-        corresponding guard tests in Erlang, return <c><![CDATA[true]]></c> or
-        <c><![CDATA[false]]></c>.</p>
-      <p><em>is_record: </em>Takes an additional parameter, which SHALL
-        be the result of <c><![CDATA[record_info(size, <record_type>)]]></c>,
-        like in <c><![CDATA[{is_record, '$1', rectype, record_info(size, rectype)}]]></c>.
-        </p>
-      <p><em>'not': </em>Negates its single argument (anything other
-        than <c><![CDATA[false]]></c> gives <c><![CDATA[false]]></c>).
-        </p>
-      <p><em>'and': </em>Returns <c><![CDATA[true]]></c> if all its arguments
-        (variable length argument list) evaluate to <c><![CDATA[true]]></c>, else
-        <c><![CDATA[false]]></c>. Evaluation order is undefined.
-        </p>
-      <p><em>'or': </em>Returns <c><![CDATA[true]]></c> if any of its arguments
-        evaluates to <c><![CDATA[true]]></c>. Variable length argument
-        list. Evaluation order is undefined.
-        </p>
-      <p><em>andalso: </em>Like <c><![CDATA['and']]></c>, but quits evaluating its
-        arguments as soon as one argument evaluates to something else
-        than true. Arguments are evaluated left to right.
-        </p>
-      <p><em>orelse: </em>Like <c><![CDATA['or']]></c>, but quits evaluating as soon
-        as one of its arguments evaluates to <c><![CDATA[true]]></c>. Arguments are
-        evaluated left to right.
-        </p>
-      <p><em>'xor': </em>Only two arguments, of which one has to be true
-        and the other false to return <c><![CDATA[true]]></c>; otherwise
-        <c><![CDATA['xor']]></c> returns false.
-        </p>
-      <p><em>abs, element, hd, length, node, round, size, tl, trunc, '+', '-', '*', 'div', 'rem', 'band', 'bor', 'bxor', 'bnot', 'bsl', 'bsr', '>', '>=', '&lt;', '=&lt;', '=:=', '==', '=/=', '/=', self: </em>Work as the corresponding Erlang bif's (or
-        operators). In case of bad arguments, the result depends on
-        the context. In the <c><![CDATA[MatchConditions]]></c> part of the
-        expression, the test fails immediately (like in an Erlang
-        guard), but in the <c><![CDATA[MatchBody]]></c>, exceptions are implicitly
-        caught and the call results in the atom <c><![CDATA['EXIT']]></c>.</p>
+      <title>Functions Allowed in All Types of Match Specifications</title>
+      <p>The functions allowed in <c><![CDATA[match_spec]]></c> work as
+        follows:</p>
+
+      <taglist>
+        <tag><c>is_atom</c>, <c>is_float</c>, <c>is_integer</c>, <c>is_list</c>,
+          <c>is_number</c>, <c>is_pid</c>, <c>is_port</c>, <c>is_reference</c>,
+          <c>is_tuple</c>, <c>is_map</c>, <c>is_binary</c>, <c>is_function</c>
+        </tag>
+        <item>
+          <p>Same as the corresponding guard tests in Erlang, return
+            <c><![CDATA[true]]></c> or <c><![CDATA[false]]></c>.</p>
+        </item>
+        <tag><c>is_record</c></tag>
+        <item>
+          <p>Takes an additional parameter, which <em>must</em> be the result
+            of <c><![CDATA[record_info(size, <record_type>)]]></c>, like in
+            <c><![CDATA[{is_record, '$1', rectype, record_info(size,
+            rectype)}]]></c>.</p>
+        </item>
+        <tag><c>'not'</c></tag>
+        <item>
+          <p>Negates its single argument (anything other
+            than <c><![CDATA[false]]></c> gives <c><![CDATA[false]]></c>).</p>
+        </item>
+        <tag><c>'and'</c></tag>
+        <item>
+          <p>Returns <c><![CDATA[true]]></c> if all its arguments (variable
+            length argument list) evaluate to <c><![CDATA[true]]></c>, otherwise
+            <c><![CDATA[false]]></c>. Evaluation order is undefined.</p>
+        </item>
+        <tag><c>'or'</c></tag>
+        <item>
+          <p>Returns <c><![CDATA[true]]></c> if any of its arguments
+            evaluates to <c><![CDATA[true]]></c>. Variable length argument
+            list. Evaluation order is undefined.</p>
+        </item>
+        <tag><c>'andalso'</c></tag>
+        <item>
+          <p>Works as <c><![CDATA['and']]></c>, but quits evaluating its
+            arguments when one argument evaluates to something else
+            than <c>true</c>. Arguments are evaluated left to right.</p>
+        </item>
+        <tag><c>'orelse'</c></tag>
+        <item>
+          <p>Works as <c><![CDATA['or']]></c>, but quits evaluating as soon
+            as one of its arguments evaluates to <c><![CDATA[true]]></c>.
+            Arguments are evaluated left to right.</p>
+        </item>
+        <tag><c>'xor'</c></tag>
+        <item>
+          <p>Only two arguments, of which one must be <c>true</c> and the
+            other <c>false</c> to return <c><![CDATA[true]]></c>; otherwise
+            <c><![CDATA['xor']]></c> returns false.</p>
+        </item>
+        <tag><c>abs</c>, <c>element</c>, <c>hd</c>, <c>length</c>, <c>node</c>,
+          <c>round</c>, <c>size</c>, <c>tl</c>, <c>trunc</c>, <c>'+'</c>,
+          <c>'-'</c>, <c>'*'</c>, <c>'div'</c>, <c>'rem'</c>, <c>'band'</c>,
+          <c>'bor'</c>, <c>'bxor'</c>, <c>'bnot'</c>, <c>'bsl'</c>,
+          <c>'bsr'</c>, <c>'>'</c>, <c>'>='</c>, <c>'&lt;'</c>, <c>'=&lt;'</c>,
+          <c>'=:='</c>, <c>'=='</c>, <c>'=/='</c>, <c>'/='</c>,
+          <c>self</c></tag>
+        <item>
+          <p>Same as the corresponding Erlang BIFs (or operators). In case of
+            bad arguments, the result depends on the context. In the
+            <c><![CDATA[MatchConditions]]></c> part of the expression, the test
+            fails immediately (like in an Erlang guard). In the
+            <c><![CDATA[MatchBody]]></c> part, exceptions are implicitly caught
+            and the call results in the atom <c><![CDATA['EXIT']]></c>.</p>
+        </item>
+      </taglist>
     </section>
 
     <section>
-      <title>Functions allowed only for tracing</title>
-      <p><em>is_seq_trace: </em>Returns <c><![CDATA[true]]></c> if a sequential
-        trace token is set for the current process, otherwise <c><![CDATA[false]]></c>.
-        </p>
-      <p><em>set_seq_token:</em> Works like
-        <c><![CDATA[seq_trace:set_token/2]]></c>, but returns <c><![CDATA[true]]></c> on success
-        and <c><![CDATA['EXIT']]></c> on error or bad argument. Only allowed in the
-        <c><![CDATA[MatchBody]]></c> part and only allowed when tracing.
-        </p>
-      <p><em>get_seq_token:</em> Works just like 
-        <c><![CDATA[seq_trace:get_token/0]]></c>, and is only allowed in the 
-        <c><![CDATA[MatchBody]]></c> part when tracing.
-        </p>
-      <p><em>message:</em> Sets an additional message appended to the
-        trace message sent. One can only set one additional message in
-        the body; subsequent calls will replace the appended message. As
-        a special case, <c><![CDATA[{message, false}]]></c> disables sending of
-        trace messages ('call' and 'return_to') 
-        for this function call, just like if the match_spec had not matched,
-        which can be useful if only the side effects of 
-        the <c><![CDATA[MatchBody]]></c> are desired. 
-        Another special case is <c><![CDATA[{message, true}]]></c> which
-        sets the default behavior, as if the function had no match_spec, 
-        trace message is sent with no extra
-        information (if no other calls to <c><![CDATA[message]]></c> are placed
-        before <c><![CDATA[{message, true}]]></c>, it is in fact a "noop"). 
-        </p>
-      <p>Takes one argument, the message. Returns <c><![CDATA[true]]></c> and can
-        only be used in the <c><![CDATA[MatchBody]]></c> part and when tracing.
-        </p>
-      <p><em>return_trace:</em> Causes a <c><![CDATA[return_from]]></c> trace 
-        message to be sent upon return from the current function.
-        Takes no arguments, returns <c><![CDATA[true]]></c> and can only be used 
-        in the <c><![CDATA[MatchBody]]></c> part when tracing.
-        If the process trace flag <c><![CDATA[silent]]></c>
-        is active the <c><![CDATA[return_from]]></c> trace message is inhibited.
-        </p>
-      <p>NOTE! If the traced function is tail recursive, this match 
-        spec function destroys that property. 
-        Hence, if a match spec executing this function is used on a 
-        perpetual server process, it may only be active for a limited 
-        time, or the emulator will eventually use all memory in the host 
-        machine and crash. If this match_spec function is inhibited
-        using the <c><![CDATA[silent]]></c> process trace flag 
-        tail recursiveness still remains.
-        </p>
-      <p><em>exception_trace:</em> Same as <em>return_trace</em>,
-        plus; if the traced function exits due to an exception,
-        an <c><![CDATA[exception_from]]></c> trace message is generated,
-        whether the exception is caught or not.
-        </p>
-      <p><em>process_dump:</em> Returns some textual information about
-        the current process as a binary. Takes no arguments and is only
-        allowed in the <c><![CDATA[MatchBody]]></c> part when tracing.
-        </p>
-      <p><em>enable_trace:</em> With one parameter this function turns
-        on tracing like the Erlang call <c><![CDATA[erlang:trace(self(), true, [P2])]]></c>, where <c><![CDATA[P2]]></c> is the parameter to
-        <c><![CDATA[enable_trace]]></c>. With two parameters, the first parameter
-        should be either a process identifier or the registered name of
-        a process. In this case tracing is turned on for the designated
-        process in the same way as in the Erlang call  <c><![CDATA[erlang:trace(P1, true, [P2])]]></c>, where P1 is the first and P2 is the second
-        argument. The process <c><![CDATA[P1]]></c> gets its trace messages sent to the same
-        tracer as the process executing the statement uses. <c><![CDATA[P1]]></c>
-        can <em>not</em> be one of the atoms <c><![CDATA[all]]></c>, <c><![CDATA[new]]></c> or 
-        <c><![CDATA[existing]]></c> (unless, of course, they are registered names).
-        <c><![CDATA[P2]]></c> can <em>not</em> be <c><![CDATA[cpu_timestamp]]></c> nor
-        <c><![CDATA[tracer]]></c>.
-        Returns <c><![CDATA[true]]></c> and may only be used in
-        the <c><![CDATA[MatchBody]]></c> part when tracing.
-        </p>
-      <p><em>disable_trace:</em> With one parameter this function
-        disables tracing like the Erlang call <c><![CDATA[erlang:trace(self(), false, [P2])]]></c>, where <c><![CDATA[P2]]></c> is the parameter to
-        <c><![CDATA[disable_trace]]></c>. With two parameters it works like the
-        Erlang call <c><![CDATA[erlang:trace(P1, false, [P2])]]></c>, where P1 can
-        be either a process identifier or a registered name and is given
-        as the first argument to the match_spec function. 
-        <c><![CDATA[P2]]></c> can <em>not</em> be <c><![CDATA[cpu_timestamp]]></c> nor
-        <c><![CDATA[tracer]]></c>. Returns
-        <c><![CDATA[true]]></c> and may only be used in the <c><![CDATA[MatchBody]]></c> part
-        when tracing.
-        </p>
-      <p><em>trace:</em> With two parameters this function takes a list
-        of trace flags to disable as first parameter and a list
-        of trace flags to enable as second parameter. Logically, the
-        disable list is applied first, but effectively all changes
-        are applied atomically. The trace flags
-        are the same as for <c><![CDATA[erlang:trace/3]]></c> not including
-        <c><![CDATA[cpu_timestamp]]></c> but including <c><![CDATA[tracer]]></c>. If a
-        tracer is specified in both lists, the tracer in the 
-        enable list takes precedence. If no tracer is specified the
-        same tracer as the process executing the match spec is 
-        used. When using a <seealso marker="erl_tracer">tracer module</seealso>
-        the module has to be loaded before the match specification is executed.
-        If it is not loaded the match will fail.
-        With three parameters to this function the first is
-        either a process identifier or the registered name of a
-        process to set trace flags on, the second is the disable
-        list, and the third is the enable list. Returns
-        <c><![CDATA[true]]></c> if any trace property was changed for the
-        trace target process or <c><![CDATA[false]]></c> if not. It may only
-        be used in the <c><![CDATA[MatchBody]]></c> part when tracing.
-        </p>
-      <p><em>caller:</em> 
-        Returns the calling function as a tuple {Module,
-        Function, Arity} or the atom <c><![CDATA[undefined]]></c> if the calling
-        function cannot be determined. May only be used in the 
-        <c><![CDATA[MatchBody]]></c> part when tracing.
-        </p>
-      <p>Note that if a "technically built in function" (i.e. a
-        function not written in Erlang) is traced, the <c><![CDATA[caller]]></c>
-        function will sometimes return the atom <c><![CDATA[undefined]]></c>. The calling
-        Erlang function is not available during such calls.
-        </p>
-      <p><em>display:</em> For debugging purposes only; displays the
-        single argument as an Erlang term on stdout, which is seldom
-        what is wanted. Returns <c><![CDATA[true]]></c> and may only be used in the
-        <c><![CDATA[MatchBody]]></c> part when tracing.
-        </p>
-      <p>        <marker id="get_tcw"></marker>
-<em>get_tcw:</em> 
-        Takes no argument and returns the value of the node's trace
-        control word. The same is done by
-        <c><![CDATA[erlang:system_info(trace_control_word)]]></c>. 
-        </p>
-      <p>The trace control word is a 32-bit unsigned integer intended for
-        generic trace control. The trace control word can be tested and 
-        set both from within trace match specifications and with BIFs. 
-        This call is only allowed when tracing. 
-        </p>
-      <p>        <marker id="set_tcw"></marker>
-<em>set_tcw:</em>
-        Takes one unsigned integer argument, sets the value of 
-        the node's trace control word to the value of the argument 
-        and returns the previous value. The same is done by 
-        <c><![CDATA[erlang:system_flag(trace_control_word, Value)]]></c>. It is only
-        allowed to use <c><![CDATA[set_tcw]]></c> in the <c><![CDATA[MatchBody]]></c> part 
-        when tracing.
-        </p>
-      <p><em>silent:</em>
-        Takes one argument. If the argument is <c><![CDATA[true]]></c>, the call
-        trace message mode for the current process is set to silent
-        for this call and all subsequent, i.e call trace messages
-        are inhibited even if <c><![CDATA[{message, true}]]></c> is called in the
-        <c><![CDATA[MatchBody]]></c> part for a traced function. 
-        </p>
-      <p>This mode can also be activated with the <c><![CDATA[silent]]></c> flag
-        to <c><![CDATA[erlang:trace/3]]></c>.
-        </p>
-      <p>If the argument is <c><![CDATA[false]]></c>, the call trace message mode
-        for the current process is set to normal (non-silent) for
-        this call and all subsequent.
-        </p>
-      <p>If the argument is neither <c><![CDATA[true]]></c> nor <c><![CDATA[false]]></c>, 
-        the call trace message mode is unaffected.</p>
+      <title>Functions Allowed Only for Tracing</title>
+      <p>The functions allowed only for tracing work as follows:</p>
+
+      <taglist>
+        <tag><c>is_seq_trace</c></tag>
+        <item>
+          <p>Returns <c><![CDATA[true]]></c> if a sequential trace token is set
+            for the current process, otherwise <c><![CDATA[false]]></c>.</p>
+        </item>
+        <tag><c>set_seq_token</c></tag>
+        <item>
+          <p>Works as <c><![CDATA[seq_trace:set_token/2]]></c>, but returns
+            <c><![CDATA[true]]></c> on success, and <c><![CDATA['EXIT']]></c>
+            on error or bad argument. Only allowed in the
+            <c><![CDATA[MatchBody]]></c> part and only allowed when tracing.</p>
+        </item>
+        <tag><c>get_seq_token</c></tag>
+        <item>
+          <p>Same as <c><![CDATA[seq_trace:get_token/0]]></c> and only
+            allowed in the <c><![CDATA[MatchBody]]></c> part when tracing.</p>
+        </item>
+        <tag><c>message</c></tag>
+        <item>
+          <p>Sets an additional message appended to the
+            trace message sent. One can only set one additional message in
+            the body. Later calls replace the appended message.</p>
+          <p>As a special case, <c><![CDATA[{message, false}]]></c> disables
+            sending of trace messages ('call' and 'return_to') for this function
+            call, just like if the match specification had not matched.
+            This can be useful if only the side effects of 
+            the <c><![CDATA[MatchBody]]></c> part are desired.</p>
+          <p>Another special case is <c><![CDATA[{message, true}]]></c>, which
+            sets the default behavior, as if the function had no match
+            specification; trace message is sent with no extra information
+            (if no other calls to <c><![CDATA[message]]></c> are placed before
+            <c><![CDATA[{message, true}]]></c>, it is in fact a "noop").</p>
+          <p>Takes one argument: the message. Returns <c><![CDATA[true]]></c>
+            and can only be used in the <c><![CDATA[MatchBody]]></c> part and
+            when tracing.</p>
+        </item>
+        <tag><c>return_trace</c></tag>
+        <item>
+          <p>Causes a <c><![CDATA[return_from]]></c> trace message to be sent
+            upon return from the current function. Takes no arguments, returns
+            <c><![CDATA[true]]></c> and can only be used in the
+            <c><![CDATA[MatchBody]]></c> part when tracing.
+            If the process trace flag <c><![CDATA[silent]]></c> is active, the
+            <c><![CDATA[return_from]]></c> trace message is inhibited.</p>
+          <p><em>Warning:</em> If the traced function is tail-recursive, this
+            match specification function destroys that property. Hence, if a
+            match specification executing this function is used on a
+            perpetual server process, it can only be active for a limited
+            period of time, or the emulator will eventually use all memory in
+            the host machine and crash. If this match specification function is
+            inhibited using process trace flag <c><![CDATA[silent]]></c>,
+            tail-recursiveness still remains.</p>
+        </item>
+        <tag><c>exception_trace</c></tag>
+        <item>
+          <p>Works as <c>return_trace</c> plus; if the traced function exits
+            because of an exception,
+            an <c><![CDATA[exception_from]]></c> trace message is generated,
+            regardless of the exception is caught or not.</p>
+        </item>
+        <tag><c>process_dump</c></tag>
+        <item>
+          <p>Returns some textual information about
+            the current process as a binary. Takes no arguments and is only
+            allowed in the <c><![CDATA[MatchBody]]></c> part when tracing.</p>
+        </item>
+        <tag><c>enable_trace</c></tag>
+        <item>
+          <p>With one parameter this function turns on tracing like the Erlang
+            call <c><![CDATA[erlang:trace(self(), true, [P2])]]></c>, where
+            <c><![CDATA[P2]]></c> is the parameter to
+            <c><![CDATA[enable_trace]]></c>.</p>
+          <p>With two parameters, the first parameter is to be either a process
+            identifier or the registered name of a process. In this case tracing
+            is turned on for the designated process in the same way as in the
+            Erlang call <c><![CDATA[erlang:trace(P1, true, [P2])]]></c>, where
+            <c>P1</c> is the first and <c>P2</c> is the second argument. The
+            process <c><![CDATA[P1]]></c> gets its trace messages sent to the
+            same tracer as the process executing the statement uses.
+            <c><![CDATA[P1]]></c> <em>cannot</em> be one of the atoms
+            <c><![CDATA[all]]></c>, <c><![CDATA[new]]></c> or 
+            <c><![CDATA[existing]]></c> (unless they are registered names).
+            <c><![CDATA[P2]]></c> <em>cannot</em> be
+            <c><![CDATA[cpu_timestamp]]></c> or <c><![CDATA[tracer]]></c>.</p>
+          <p>Returns <c><![CDATA[true]]></c> and can only be used in
+            the <c><![CDATA[MatchBody]]></c> part when tracing.</p>
+        </item>
+        <tag><c>disable_trace</c></tag>
+        <item>
+          <p>With one parameter this function disables tracing like the Erlang
+            call <c><![CDATA[erlang:trace(self(), false, [P2])]]></c>, where
+            <c><![CDATA[P2]]></c> is the parameter to
+            <c><![CDATA[disable_trace]]></c>.</p>
+          <p>With two parameters this function works as the Erlang call
+            <c><![CDATA[erlang:trace(P1, false, [P2])]]></c>, where <c>P1</c>
+            can be either a process identifier or a registered name and is
+            specified as the first argument to the match specification function.
+            <c><![CDATA[P2]]></c> <em>cannot</em> be
+            <c><![CDATA[cpu_timestamp]]></c> or <c><![CDATA[tracer]]></c>.</p>
+          <p>Returns <c><![CDATA[true]]></c> and can only be used in the
+            <c><![CDATA[MatchBody]]></c> part when tracing.</p>
+        </item>
+        <tag><c>trace</c></tag>
+        <item>
+          <p>With two parameters this function takes a list
+            of trace flags to disable as first parameter and a list
+            of trace flags to enable as second parameter. Logically, the
+            disable list is applied first, but effectively all changes
+            are applied atomically. The trace flags
+            are the same as for <c><![CDATA[erlang:trace/3]]></c>,
+            not including <c><![CDATA[cpu_timestamp]]></c>, but including
+            <c><![CDATA[tracer]]></c>.</p>
+          <p>If a tracer is specified in both lists, the tracer in the
+            enable list takes precedence. If no tracer is specified, the same
+            tracer as the process executing the match specification is used.</p>
+          <p>When using a <seealso marker="erl_tracer">tracer module</seealso>,
+            the module must be loaded before the match specification is
+            executed. If it is not loaded, the match fails.</p>
+          <p>With three parameters to this function, the first is
+            either a process identifier or the registered name of a
+            process to set trace flags on, the second is the disable
+            list, and the third is the enable list.</p>
+          <p>Returns <c><![CDATA[true]]></c> if any trace property was changed
+            for the trace target process, otherwise <c><![CDATA[false]]></c>.
+            Can only be used in the <c><![CDATA[MatchBody]]></c> part when
+            tracing.</p>
+        </item>
+        <tag><c>caller</c></tag>
+        <item>
+          <p>Returns the calling function as a tuple <c>{Module, Function,
+             Arity}</c> or the atom <c><![CDATA[undefined]]></c> if the calling
+             function cannot be determined. Can only be used in the
+             <c><![CDATA[MatchBody]]></c> part when tracing.</p>
+           <p>Notice that if a "technically built in function" (that is, a
+             function not written in Erlang) is traced, the
+             <c><![CDATA[caller]]></c> function sometimes returns the atom
+             <c><![CDATA[undefined]]></c>. The calling
+             Erlang function is not available during such calls.</p>
+        </item>
+        <tag><c>display</c></tag>
+          <item>
+            <p>For debugging purposes only. Displays the single argument as an
+              Erlang term on <c>stdout</c>, which is seldom what is wanted.
+              Returns <c><![CDATA[true]]></c> and can only be used in the
+              <c><![CDATA[MatchBody]]></c> part when tracing.</p>
+          <marker id="get_tcw"></marker>
+          </item>
+        <tag><c>get_tcw</c></tag>
+        <item>
+          <p>Takes no argument and returns the value of the node's trace
+            control word. The same is done by
+            <c><![CDATA[erlang:system_info(trace_control_word)]]></c>.</p>
+          <p>The trace control word is a 32-bit unsigned integer intended for
+            generic trace control. The trace control word can be tested and
+            set both from within trace match specifications and with BIFs.
+            This call is only allowed when tracing.</p>
+        <marker id="set_tcw"></marker>
+        </item>
+        <tag><c>set_tcw</c></tag>
+        <item>
+          <p>Takes one unsigned integer argument, sets the value of
+            the node's trace control word to the value of the argument,
+            and returns the previous value. The same is done by
+            <c><![CDATA[erlang:system_flag(trace_control_word, Value)]]></c>.
+            It is only allowed to use <c><![CDATA[set_tcw]]></c> in the
+            <c><![CDATA[MatchBody]]></c> part when tracing.</p>
+        </item>
+        <tag><c>silent</c></tag>
+        <item>
+          <p>Takes one argument. If the argument is <c><![CDATA[true]]></c>,
+            the call trace message mode for the current process is set to
+            silent for this call and all later calls, that is, call trace
+            messages are inhibited even if
+            <c><![CDATA[{message, true}]]></c> is called in the
+            <c><![CDATA[MatchBody]]></c> part for a traced function.</p>
+          <p>This mode can also be activated with flag
+            <c><![CDATA[silent]]></c> to
+            <c><![CDATA[erlang:trace/3]]></c>.</p>
+          <p>If the argument is <c><![CDATA[false]]></c>, the call trace
+            message mode for the current process is set to normal
+            (non-silent) for this call and all later calls.</p>
+          <p>If the argument is not <c><![CDATA[true]]></c> or
+            <c><![CDATA[false]]></c>, the call trace message mode is
+            unaffected.</p>
+        </item>
+      </taglist>
     </section>
-    <p><em>Note</em> that all "function calls" have to be tuples, 
-      even if they take no arguments. The value of <c><![CDATA[self]]></c> is 
-      the atom() <c><![CDATA[self]]></c>, but the value of <c><![CDATA[{self}]]></c> is 
-      the pid() of the current process.</p>
+
+    <note>
+      <p>All "function calls" must be tuples, even if they take no arguments.
+        The value of <c><![CDATA[self]]></c> is  the atom()
+        <c><![CDATA[self]]></c>, but the value of <c><![CDATA[{self}]]></c> is
+        the pid() of the current process.</p>
+    </note>
   </section>
 
-  <marker id="match_target"></marker>
   <section>
+    <marker id="match_target"/>
     <title>Match target</title>
     <p>Each execution of a match specification is done against
       a match target term. The format and content of the target term
@@ -422,217 +533,268 @@
   </section>
 
   <section>
-    <title>Variables and literals</title>
-    <p>Variables take the form <c><![CDATA['$<number>']]></c> where
-      <c><![CDATA[<number>]]></c> is an integer between 0 (zero) and
-      100000000 (1e+8), the behavior if the number is outside these
-      limits is <em>undefined</em>.  In the <c><![CDATA[MatchHead]]></c> part, the special
-      variable <c><![CDATA['_']]></c> matches anything, and never gets bound (like
-      <c><![CDATA[_]]></c> in Erlang). In the <c><![CDATA[MatchCondition/MatchBody]]></c>
-      parts, no unbound variables are allowed, why <c><![CDATA['_']]></c> is
-      interpreted as itself (an atom). Variables can only be bound in
-      the <c><![CDATA[MatchHead]]></c> part. In the <c><![CDATA[MatchBody]]></c> and
-      <c><![CDATA[MatchCondition]]></c> parts, only variables bound previously may
-      be used. As a special case, in the
-      <c><![CDATA[MatchCondition/MatchBody]]></c> parts, the variable <c><![CDATA['$_']]></c>
-      expands to the whole <seealso marker="#match_target">match target</seealso>
-      term and the variable <c><![CDATA['$$']]></c> expands to a list
-      of the values of all bound variables in order 
-      (i.e. <c><![CDATA[['$1','$2', ...]]]></c>).
-      </p>
-    <p>In the <c><![CDATA[MatchHead]]></c> part, all literals (except the variables
-      noted above) are interpreted as is. In the
-      <c><![CDATA[MatchCondition/MatchBody]]></c> parts, however, the
-      interpretation is in some ways different.  Literals in the
-      <c><![CDATA[MatchCondition/MatchBody]]></c> can either be written as is,
-      which works for all literals except tuples, or by using the
-      special form <c><![CDATA[{const, T}]]></c>, where <c><![CDATA[T]]></c> is any Erlang
-      term. For tuple literals in the match_spec, one can also use
-      double tuple parentheses, i.e., construct them as a tuple of
+    <title>Variables and Literals</title>
+    <p>Variables take the form <c><![CDATA['$<number>']]></c>, where
+      <c><![CDATA[<number>]]></c> is an integer between 0 and
+      100,000,000 (1e+8). The behavior if the number is outside these limits
+      is <em>undefined</em>. In the <c><![CDATA[MatchHead]]></c> part, the
+      special variable <c><![CDATA['_']]></c> matches anything, and never gets
+      bound (like <c><![CDATA[_]]></c> in Erlang).</p>
+
+    <list type="bulleted">
+      <item>
+        <p>In the <c><![CDATA[MatchCondition/MatchBody]]></c> parts,
+          no unbound variables are allowed, so <c><![CDATA['_']]></c> is
+          interpreted as itself (an atom). Variables can only be bound in the
+          <c><![CDATA[MatchHead]]></c> part.</p>
+      </item>
+      <item>
+        <p>In the <c><![CDATA[MatchBody]]></c> and
+          <c><![CDATA[MatchCondition]]></c> parts, only variables bound
+          previously can be used.</p>
+      </item>
+      <item>
+        <p>As a special case, the following apply in the
+          <c><![CDATA[MatchCondition/MatchBody]]></c> parts:</p>
+        <list type="bulleted">
+          <item>
+            <p>The variable <c><![CDATA['$_']]></c> expands to the whole
+            <seealso marker="#match_target">match target</seealso> term.
+            </p>
+          </item>
+          <item>
+            <p>The variable <c><![CDATA['$$']]></c> expands to a list of the
+              values of all bound variables in order (that is,
+              <c><![CDATA[['$1','$2', ...]]]></c>).</p>
+          </item>
+        </list>
+      </item>
+    </list>
+
+    <p>In the <c><![CDATA[MatchHead]]></c> part, all literals (except the
+      variables above) are interpreted "as is".</p>
+
+    <p>In the <c><![CDATA[MatchCondition/MatchBody]]></c> parts, the
+      interpretation is in some ways different. Literals in these parts
+      can either be written "as is", which works for all literals except
+      tuples, or by using the special form <c><![CDATA[{const, T}]]></c>,
+      where <c><![CDATA[T]]></c> is any Erlang term.</p>
+
+    <p>For tuple literals in the match specification, double tuple parentheses
+      can also be used, that is, construct them as a tuple of
       arity one containing a single tuple, which is the one to be
       constructed. The "double tuple parenthesis" syntax is useful to
       construct tuples from already bound variables, like in
-      <c><![CDATA[{{'$1', [a,b,'$2']}}]]></c>. Some examples may be needed:
-      </p>
+      <c><![CDATA[{{'$1', [a,b,'$2']}}]]></c>. Examples:</p>
+
     <table>
       <row>
-        <cell align="left" valign="middle">Expression		</cell>
-        <cell align="left" valign="middle">Variable bindings		</cell>
-        <cell align="left" valign="middle">Result	</cell>
+        <cell align="left" valign="middle"><em>Expression</em></cell>
+        <cell align="left" valign="middle"><em>Variable Bindings</em></cell>
+        <cell align="left" valign="middle"><em>Result</em></cell>
       </row>
       <row>
-        <cell align="left" valign="middle">{{'$1','$2'}}		</cell>
+        <cell align="left" valign="middle">{{'$1','$2'}}</cell>
         <cell align="left" valign="middle">'$1' = a, '$2' = b</cell>
         <cell align="left" valign="middle">{a,b}</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">{const, {'$1', '$2'}}	</cell>
-        <cell align="left" valign="middle">doesn't matter</cell>
+        <cell align="left" valign="middle">{const, {'$1', '$2'}}</cell>
+        <cell align="left" valign="middle">Irrelevant</cell>
         <cell align="left" valign="middle">{'$1', '$2'}</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">a			</cell>
-        <cell align="left" valign="middle">doesn't matter			</cell>
+        <cell align="left" valign="middle">a</cell>
+        <cell align="left" valign="middle">Irrelevant</cell>
         <cell align="left" valign="middle">a</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">'$1'			</cell>
-        <cell align="left" valign="middle">'$1' = []			</cell>
+        <cell align="left" valign="middle">'$1'</cell>
+        <cell align="left" valign="middle">'$1' = []</cell>
         <cell align="left" valign="middle">[]</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">['$1']			</cell>
-        <cell align="left" valign="middle">'$1' = []			</cell>
+        <cell align="left" valign="middle">['$1']</cell>
+        <cell align="left" valign="middle">'$1' = []</cell>
         <cell align="left" valign="middle">[[]]</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">[{{a}}]			</cell>
-        <cell align="left" valign="middle">doesn't matter</cell>
+        <cell align="left" valign="middle">[{{a}}]</cell>
+        <cell align="left" valign="middle">Irrelevant</cell>
         <cell align="left" valign="middle">[{a}]</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">42			</cell>
-        <cell align="left" valign="middle">doesn't matter</cell>
+        <cell align="left" valign="middle">42</cell>
+        <cell align="left" valign="middle">Irrelevant</cell>
         <cell align="left" valign="middle">42</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">"hello"			</cell>
-        <cell align="left" valign="middle">doesn't matter</cell>
+        <cell align="left" valign="middle">"hello"</cell>
+        <cell align="left" valign="middle">Irrelevant</cell>
         <cell align="left" valign="middle">"hello"</cell>
       </row>
       <row>
-        <cell align="left" valign="middle">$1			</cell>
-        <cell align="left" valign="middle">doesn't matter</cell>
-        <cell align="left" valign="middle">49 (the ASCII value for the character '1')</cell>
+        <cell align="left" valign="middle">$1</cell>
+        <cell align="left" valign="middle">Irrelevant</cell>
+        <cell align="left" valign="middle">49 (the ASCII value for
+          character '1')</cell>
       </row>
-      <tcaption>Literals in the MatchCondition/MatchBody parts of a match_spec</tcaption>
+      <tcaption>Literals in MatchCondition/MatchBody Parts of a Match
+        Specification</tcaption>
     </table>
   </section>
 
   <section>
-    <title>Execution of the match</title>
+    <title>Execution of the Match</title>
     <p>The execution of the match expression, when the runtime system
-      decides whether a trace message should be sent, goes as follows:
-      </p>
-    <p>For each tuple in the <c><![CDATA[MatchExpression]]></c> list and while no
-      match has succeeded:</p>
-    <list type="bulleted">
-      <item>Match the <c><![CDATA[MatchHead]]></c> part against the
-       match target term,
-       binding the <c><![CDATA['$<number>']]></c> variables (much like in
-      <c><![CDATA[ets:match/2]]></c>).
-       If the <c><![CDATA[MatchHead]]></c> cannot match the arguments, the match fails.
-      </item>
-      <item>Evaluate each <c><![CDATA[MatchCondition]]></c> (where only
-      <c><![CDATA['$<number>']]></c> variables previously bound in the
-      <c><![CDATA[MatchHead]]></c> can occur) and expect it to return the atom
-      <c><![CDATA[true]]></c>. As soon as a condition does not evaluate to
-      <c><![CDATA[true]]></c>, the match fails. If any BIF call generates an
-       exception, also fail.
+      decides whether a trace message is to be sent, is as follows:</p>
+
+    <p>For each tuple in the <c><![CDATA[MatchExpression]]></c> list and while
+      no match has succeeded:</p>
+
+    <list type="ordered">
+      <item>
+        <p>Match the <c><![CDATA[MatchHead]]></c> part against the match target
+          term, binding the <c><![CDATA['$<number>']]></c> variables
+          (much like in <c><![CDATA[ets:match/2]]></c>). If the
+          <c><![CDATA[MatchHead]]></c> part cannot match the arguments, the
+          match fails.</p>
       </item>
       <item>
+        <p>Evaluate each <c><![CDATA[MatchCondition]]></c> (where only
+          <c><![CDATA['$<number>']]></c> variables previously bound in the
+          <c><![CDATA[MatchHead]]></c> part can occur) and expect it to return
+          the atom <c><![CDATA[true]]></c>. When a condition does not evaluate
+          to <c><![CDATA[true]]></c>, the match fails. If any BIF call
+          generates an exception, the match also fails.</p>
+      </item>
+      <item>
+        <p>Two cases can occur:</p>
         <list type="bulleted">
-          <item><em>If the match_spec is executing when tracing:</em><br></br>
-           Evaluate each <c><![CDATA[ActionTerm]]></c> in the same way as the
-          <c><![CDATA[MatchConditions]]></c>, but completely ignore the return
-           values. Regardless of what happens in this part, the match has
-           succeeded.</item>
-          <item><em>If the match_spec is executed when selecting objects from an ETS table:</em><br></br>
-           Evaluate the expressions in order and return the value of
-           the last expression (typically there is only one expression
-           in this context)</item>
+          <item>
+            <p>If the match specification is executing when tracing:</p>
+            <p>Evaluate each <c><![CDATA[ActionTerm]]></c> in the same way as
+              the <c><![CDATA[MatchConditions]]></c>, but ignore the return
+              values. Regardless of what happens in this part, the match has
+              succeeded.</p>
+          </item>
+          <item>
+            <p>If the match specification is executed when selecting objects
+              from an <c>ets</c> table:</p>
+            <p>Evaluate the expressions in order and return the value of
+              the last expression (typically there is only one expression
+              in this context).</p>
+          </item>
         </list>
       </item>
     </list>
   </section>
 
   <section>
-    <title>Differences between match specifications in ETS and tracing</title>
-    <p>ETS match specifications are there to produce a return
-      value. Usually the <c><![CDATA[MatchBody]]></c> contains one single
-      <c><![CDATA[ConditionExpression]]></c> which defines the return value without having
-      any side effects. Calls with side effects are not allowed in the
-      ETS context.</p>
+    <marker id="differences_ets_tracing"/>
+    <title>Differences between Match Specifications in ETS and Tracing</title>
+    <p><c>ets</c> match specifications produce a return value.
+        Usually the <c><![CDATA[MatchBody]]></c> contains one single
+        <c><![CDATA[ConditionExpression]]></c> that defines the return value
+        without any side effects. Calls with side effects are not allowed in
+        the <c>ets</c> context.</p>
+
     <p>When tracing there is no return value to produce, the
-      match specification either matches or doesn't. The effect when the
-      expression matches is a trace message rather then a returned
-      term. The <c><![CDATA[ActionTerm]]></c>'s are executed as in an imperative
-      language, i.e. for their side effects. Functions with side effects
+      match specification either matches or does not. The effect when the
+      expression matches is a trace message rather than a returned
+      term. The <c><![CDATA[ActionTerm]]></c>s are executed as in an imperative
+      language, that is, for their side effects. Functions with side effects
       are also allowed when tracing.</p>
   </section>
 
   <section>
     <title>Tracing Examples</title>
-    <p>Match an argument list of three where the first and third arguments 
+    <p>Match an argument list of three, where the first and third arguments
       are equal:</p>
+
     <code type="none"><![CDATA[
 [{['$1', '_', '$1'],
   [],
   []}]
     ]]></code>
-    <p>Match an argument list of three where the second argument is 
-      a number greater than three:</p>
+
+    <p>Match an argument list of three, where the second argument is
+      a number &gt; 3:</p>
+
     <code type="none"><![CDATA[
 [{['_', '$1', '_'],
   [{ '>', '$1', 3}],
   []}]
     ]]></code>
-    <p>Match an argument list of three, where the third argument
-      is a tuple containing argument one and two <em>or</em> a list
-      beginning with argument one and two (i. e. <c><![CDATA[[a,b,[a,b,c]]]]></c> or 
-      <c><![CDATA[[a,b,{a,b}]]]></c>):
-      </p>
+
+    <p>Match an argument list of three, where the third argument is
+      either a tuple containing argument one and two, <em>or</em> a list
+      beginning with argument one and two (that is,
+      <c><![CDATA[[a,b,[a,b,c]]]]></c> or <c><![CDATA[[a,b,{a,b}]]]></c>):</p>
+
     <code type="none"><![CDATA[
 [{['$1', '$2', '$3'],
-  [{orelse, 
+  [{'orelse', 
       {'=:=', '$3', {{'$1','$2'}}},
       {'and', 
         {'=:=', '$1', {hd, '$3'}},
         {'=:=', '$2', {hd, {tl, '$3'}}}}}],
   []}]
     ]]></code>
-    <p>The above problem may also be solved like this:</p>
+
+    <p>The above problem can also be solved as follows:</p>
+
     <code type="none"><![CDATA[
 [{['$1', '$2', {'$1', '$2}], [], []},
  {['$1', '$2', ['$1', '$2' | '_']], [], []}]
     ]]></code>
-    <p>Match two arguments where the first is a tuple beginning with
-      a list which in turn begins with the second argument times
-      two (i. e. [{[4,x],y},2] or [{[8], y, z},4])</p>
+
+    <p>Match two arguments, where the first is a tuple beginning with
+      a list that in turn begins with the second argument times
+      two (that is, <c>[{[4,x],y},2]</c> or <c>[{[8], y, z},4])</c>:</p>
+
     <code type="none"><![CDATA[
 [{['$1', '$2'],[{'=:=', {'*', 2, '$2'}, {hd, {element, 1, '$1'}}}],
   []}]
     ]]></code>
+
     <p>Match three arguments. When all three are equal and are
-      numbers, append the process dump to the trace message, else
-      let the trace message be as is, but set the sequential trace
-      token label to 4711.</p>
+      numbers, append the process dump to the trace message, otherwise
+      let the trace message be "as is", but set the sequential trace
+      token label to 4711:</p>
+
     <code type="none"><![CDATA[
 [{['$1', '$1', '$1'],
   [{is_number, '$1'}],
   [{message, {process_dump}}]},
  {'_', [], [{set_seq_token, label, 4711}]}]
     ]]></code>
-    <p>As can be noted above, the parameter list can be matched
-      against a single <c><![CDATA[MatchVariable]]></c> or an <c><![CDATA['_']]></c>. To replace the
-      whole
-      parameter list with a single variable is a special case. In all 
-      other cases the <c><![CDATA[MatchHead]]></c> has to be a <em>proper</em> list.
-      </p>
-    <p>Only generate trace message if trace control word is set to 1:</p>
+
+    <p>As can be noted above, the parameter list can be matched aginst a
+      single <c><![CDATA[MatchVariable]]></c> or an <c><![CDATA['_']]></c>.
+      To replace the whole parameter list with a single variable is a special
+      case. In all other cases the <c><![CDATA[MatchHead]]></c> must be a
+      <em>proper</em> list.</p>
+
+    <p>Generate a trace message only if the trace control word is set to 1:</p>
+
     <code type="none"><![CDATA[
 [{'_',
   [{'==',{get_tcw},{const, 1}}],
   []}]
     ]]></code>
-    <p>Only generate trace message if there is a seq trace token:</p>
+
+    <p>Generate a trace message only if there is a <c>seq_trace</c> token:</p>
+
     <code type="none"><![CDATA[
 [{'_',
   [{'==',{is_seq_trace},{const, 1}}],
   []}]
     ]]></code>
-    <p>Remove 'silent' trace flag when first argument is 'verbose'
-    and add it when it is 'silent':</p>
+
+    <p>Remove the <c>'silent'</c> trace flag when the first argument is
+      <c>'verbose'</c>, and add it when it is <c>'silent':</c></p>
+
     <code type="none"><![CDATA[
 [{'$1',
   [{'==',{hd, '$1'},verbose}],
@@ -641,14 +803,19 @@
   [{'==',{hd, '$1'},silent}],
   [{trace, [],[silent]}]}]
     ]]></code>
-    <p>Add return_trace message if function is of arity 3:</p>
+
+    <p>Add a <c>return_trace</c> message if the function is of arity 3:</p>
+
     <code type="none"><![CDATA[
 [{'$1',
   [{'==',{length, '$1'},3}],
   [{return_trace}]},
  {'_',[],[]}]
     ]]></code>
-    <p>Only generate trace message if function is of arity 3 and first argument is 'trace':</p>
+
+    <p>Generate a trace message only if the function is of arity 3 and the
+      first argument is <c>'trace'</c>:</p>
+
     <code type="none"><![CDATA[
 [{['trace','$2','$3'],
   [],
@@ -659,29 +826,35 @@
 
   <section>
     <title>ETS Examples</title>
-    <p>Match all objects in an ets table where the first element is
-      the atom 'strider' and the tuple arity is 3 and return the whole
-      object.</p>
+    <p>Match all objects in an <c>ets</c> table, where the first element is
+      the atom <c>'strider'</c> and the tuple arity is 3, and return the whole
+      object:</p>
+
     <code type="none"><![CDATA[
 [{{strider,'_','_'},
   [],
   ['$_']}]
     ]]></code>
-    <p>Match all objects in an ets table with arity &gt; 1 and the first
-      element is 'gandalf', return element 2.</p>
+
+    <p>Match all objects in an <c>ets</c> table with arity &gt; 1 and the first
+      element is 'gandalf', and return element 2:</p>
+
     <code type="none"><![CDATA[
 [{'$1',
   [{'==', gandalf, {element, 1, '$1'}},{'>=',{size, '$1'},2}],
   [{element,2,'$1'}]}]
     ]]></code>
-    <p>In the above example, if the first element had been the key,
-      it's much more efficient to match that key in the <c><![CDATA[MatchHead]]></c>
-      part than in the <c><![CDATA[MatchConditions]]></c> part. The search space of
-      the tables is restricted with regards to the <c><![CDATA[MatchHead]]></c> so
-      that only objects with the matching key are searched.
-      </p>
-    <p>Match tuples of 3 elements where the second element is either
-      'merry' or 'pippin', return the whole objects.</p>
+
+    <p>In this example, if the first element had been the key, it is
+      much more efficient to match that key in the <c><![CDATA[MatchHead]]></c>
+      part than in the <c><![CDATA[MatchConditions]]></c> part.
+      The search space of the tables is restricted with regards to the
+      <c><![CDATA[MatchHead]]></c> so
+      that only objects with the matching key are searched.</p>
+
+    <p>Match tuples of three elements, where the second element is either
+      <c>'merry'</c> or <c>'pippin'</c>, and return the whole objects:</p>
+
     <code type="none"><![CDATA[
 [{{'_',merry,'_'},
   [],
@@ -690,8 +863,9 @@
   [],
   ['$_']}]
     ]]></code>
-    <p>The function <c><![CDATA[ets:test_ms/2]]></c> can be useful for testing
-      complicated ets matches.</p>
+
+    <p>Function <c><![CDATA[ets:test_ms/2]]></c> can be useful for testing
+      complicated <c>ets</c> matches.</p>
   </section>
 </chapter>
 
diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml
index 4b5b01d2b1..b3f5e1073b 100644
--- a/erts/doc/src/notes.xml
+++ b/erts/doc/src/notes.xml
@@ -541,9 +541,7 @@
 	    Own Id: OTP-13440</p>
         </item>
         <item>
-          <p>
-	    Add the following NIF API functions:</p>
-          <p>
+          <p>Add the following NIF API functions:</p>
 	    <list> <item><seealso
 	    marker="erl_nif#enif_cpu_time"><c>enif_cpu_time</c></seealso></item>
 	    <item><seealso
@@ -560,9 +558,9 @@
 	    marker="erl_nif#enif_binary_to_term"><c>enif_binary_to_term</c></seealso></item>
 	    <item><seealso
 	    marker="erl_nif#enif_port_command"><c>enif_port_command</c></seealso></item>
-	    </list></p>
+	    </list>
           <p>
-	    for details of what each function does, see the erl_nif
+	    For details of what each function does, see the erl_nif
 	    documentation.</p>
           <p>
 	    Own Id: OTP-13442</p>
diff --git a/erts/doc/src/part.xml b/erts/doc/src/part.xml
index b2abfc62ca..d583b873a0 100644
--- a/erts/doc/src/part.xml
+++ b/erts/doc/src/part.xml
@@ -30,8 +30,8 @@
     <file>part.xml</file>
   </header>
   <description>
-    <p>The Erlang Runtime System Application <em>ERTS</em>.</p>
   </description>
+  <xi:include href="introduction.xml"/>
   <xi:include href="communication.xml"/>
   <xi:include href="time_correction.xml"/>
   <xi:include href="match_spec.xml"/>
diff --git a/erts/doc/src/ref_man.xml b/erts/doc/src/ref_man.xml
index e45402a397..e3f7b1692b 100644
--- a/erts/doc/src/ref_man.xml
+++ b/erts/doc/src/ref_man.xml
@@ -30,16 +30,9 @@
     <file>application.xml</file>
   </header>
   <description>
-    <p>The Erlang Runtime System Application <em>ERTS</em>.</p>
-    <note>
-      <p>By default, the <c><![CDATA[erts]]></c> is only guaranteed to be compatible
-        with other Erlang/OTP components from the same release as
-        the <c><![CDATA[erts]]></c> itself. See the documentation of the system flag
-        <seealso marker="erl#compat_rel">+R</seealso> on how to communicate
-        with Erlang/OTP components from earlier releases.</p>
-    </note>
   </description>
   <xi:include href="erl_prim_loader.xml"/>
+  <xi:include href="erl_tracer.xml"/>
   <xi:include href="erlang.xml"/>
   <xi:include href="init.xml"/>
   <xi:include href="zlib.xml"/>
@@ -56,6 +49,5 @@
   <xi:include href="driver_entry.xml"/>
   <xi:include href="erts_alloc.xml"/>
   <xi:include href="erl_nif.xml"/>
-  <xi:include href="erl_tracer.xml"/>
 </application>
 
diff --git a/erts/doc/src/run_erl.xml b/erts/doc/src/run_erl.xml
index 6b0fef7c0a..21a7f86011 100644
--- a/erts/doc/src/run_erl.xml
+++ b/erts/doc/src/run_erl.xml
@@ -28,137 +28,184 @@
     <docno></docno>
     <approved></approved>
     <checked></checked>
-    <date>99-12-15</date>
+    <date>1999-12-15</date>
     <rev></rev>
     <file>run_erl.xml</file>
   </header>
   <com>run_erl</com>
-  <comsummary>Redirect Erlang input and output streams on Solaris&reg;</comsummary>
+  <comsummary>Redirect Erlang input and output streams on Solaris.</comsummary>
   <description>
-    <p>This describes the <c><![CDATA[run_erl]]></c> program specific to
-      Solaris/Linux. This program redirect the standard input and standard
-      output streams so that all output can be logged. It also let the
-      program <c><![CDATA[to_erl]]></c> connect to the Erlang console making it
-      possible to monitor and debug an embedded system remotely.</p>
-    <p>You can read more about the use in the <c><![CDATA[Embedded System User's Guide]]></c>.</p>
+    <p>The <c><![CDATA[run_erl]]></c> program is specific to Solaris/Linux.
+      This program redirects the standard input and standard
+      output streams so that all output can be logged. It also lets the
+      program <c><![CDATA[to_erl]]></c> connect to the Erlang console, making
+      it possible to monitor and debug an embedded system remotely.</p>
+
+    <p>For more information about the use, see the
+      <seealso marker="doc/embedded:embedded_solaris">
+      Embedded System User's Guide</seealso> in System Documentation.</p>
   </description>
+
   <funcs>
     <func>
-      <name>run_erl [-daemon] pipe_dir/ log_dir "exec command [command_arguments]"</name>
-      <fsummary>Start the Erlang emulator without attached terminal</fsummary>
+      <name>run_erl [-daemon] pipe_dir/ log_dir "exec command
+        [command_arguments]"</name>
+      <fsummary>Start the Erlang emulator without attached terminal.</fsummary>
       <desc>
-        <p>The <c><![CDATA[run_erl]]></c> program arguments are:</p>
+        <p>Arguments:</p>
         <taglist>
-          <tag>-daemon</tag>
-          <item>This option is highly recommended. It makes run_erl run in
-           the background completely detached from any controlling
-           terminal and the command returns to the caller immediately.
-           Without this option, run_erl must be started using several
-           tricks in the shell to detach it completely from the
-           terminal in use when starting it. The option must be the
-           first argument to run_erl on the command line.</item>
-          <tag>pipe_dir</tag>
-          <item>This is where to put the named pipe, usually
-          <c><![CDATA[/tmp/]]></c>. It shall be suffixed by a <c><![CDATA[/]]></c> (slash),
-           i.e. not <c><![CDATA[/tmp/epipies]]></c>, but <c><![CDATA[/tmp/epipes/]]></c>. </item>
-          <tag>log_dir</tag>
-          <item>This is where the log files are written. There will be one
-           log file, <c><![CDATA[run_erl.log]]></c> that log progress and
-           warnings from the <c><![CDATA[run_erl]]></c> program itself and there
-           will be up to five log files at maximum 100KB each (both
-           number of logs and sizes can be
-           changed by environment variables, see below) with
-           the content of the standard streams from and to the
-           command. When the logs are full <c><![CDATA[run_erl]]></c> will delete
-           and reuse the oldest log file.</item>
-          <tag>"exec command [command_arguments]"</tag>
-          <item>In the third argument <c><![CDATA[command]]></c> is the to execute
-           where everything written to stdin and stdout is logged to
-          <c><![CDATA[log_dir]]></c>.</item>
+          <tag><c>-daemon</c></tag>
+          <item>
+            <p>This option is highly recommended. It makes <c>run_erl</c> run
+              in the background completely detached from any controlling
+              terminal and the command returns to the caller immediately.
+              Without this option, <c>run_erl</c> must be started using several
+              tricks in the shell to detach it completely from the
+              terminal in use when starting it. The option must be the
+              first argument to <c>run_erl</c> on the command line.</p>
+          </item>
+          <tag><c>pipe_dir</c></tag>
+          <item>
+            <p>The named pipe, usually <c><![CDATA[/tmp/]]></c>. It must be
+              suffixed by a <c><![CDATA[/]]></c> (slash), that is,
+              <c><![CDATA[/tmp/epipes/]]></c>, not
+              <c><![CDATA[/tmp/epipes]]></c>.</p>
+          </item>
+          <tag><c>log_dir</c></tag>
+          <item>
+            <p>The log files, that is:</p>
+            <list type="bulleted">
+              <item>
+                <p>One log file, <c><![CDATA[run_erl.log]]></c>, which logs
+                  progress and warnings from the <c><![CDATA[run_erl]]></c>
+                  program itself.</p>
+              </item>
+              <item>
+                <p>Up to five log files at maximum 100 KB each with the content
+                  of the standard streams from and to the command. (Both the
+                  number of logs and sizes can be changed by environment
+                  variables, see section <seealso
+                  marker="environment_variables">Environment Variables</seealso>
+                  below.)</p>
+                <p>When the logs are full, <c><![CDATA[run_erl]]></c> deletes
+                  and reuses the oldest log file.</p>
+              </item>
+            </list>
+          </item>
+          <tag><c>"exec command [command_arguments]"</c></tag>
+          <item>
+            <p>In the third argument, <c><![CDATA[command]]></c> is the
+              executable to execute where everything written to <c>stdin</c>
+              and <c>stdout</c> is logged to <c><![CDATA[log_dir]]></c>.</p>
+          </item>
         </taglist>
       </desc>
     </func>
   </funcs>
 
   <section>
-    <title>Notes concerning the log files</title>
-    <p>While running, run_erl (as stated earlier) sends all output,
-      uninterpreted, to a log file. The file is called
-      <c><![CDATA[erlang.log.N]]></c>, where N is a number. When the log is "full",
-      default after 100KB, run_erl starts to log in file
-      <c><![CDATA[erlang.log.(N+1)]]></c>, until N reaches a certain number (default
-      5), where after N starts at 1 again and the oldest files start
-      getting overwritten. If no output comes from the erlang shell, but
-      the erlang machine still seems to be alive, an "ALIVE" message is
-      written to the log, it is a timestamp and is written, by default,
-      after 15 minutes of inactivity. Also, if output from erlang is
-      logged but it's been more than 5 minutes (default) since last time
-      we got anything from erlang, a timestamp is written in the
-      log. The "ALIVE" messages look like this:</p>
+    <title>Notes concerning the Log Files</title>
+    <p>While running, <c>run_erl</c> (as stated earlier) sends all output,
+      uninterpreted, to a log file. The file is named
+      <c><![CDATA[erlang.log.N]]></c>, where <c>N</c> is an integer. When the
+      log is "full" (default log size is 100 KB), <c>run_erl</c> starts to log
+      in file <c><![CDATA[erlang.log.(N+1)]]></c>, until <c>N</c> reaches a
+      certain number (default 5), whereupon <c>N</c> starts at 1 again and
+      the oldest files start getting overwritten.</p>
+
+    <p>If no output comes from the Erlang shell, but
+      the Erlang machine still seems to be alive, an "ALIVE" message is
+      written to the log; it is a time stamp and is written, by default,
+      after 15 minutes of inactivity. Also, if output from Erlang is
+      logged, but more than 5 minutes (default) has passed since last time
+      we got anything from Erlang, a time stamp is written in the
+      log. The "ALIVE" messages look as follows:</p>
+
     <code type="none"><![CDATA[
-      ===== ALIVE <date-time-string>
-    ]]></code>
-    <p>while the other timestamps look like this:</p>
+===== ALIVE <date-time-string>    ]]></code>
+
+    <p>The other time stamps look as follows:</p>
+
     <code type="none"><![CDATA[
-      ===== <date-time-string>
-    ]]></code>
-    <p>The <c><![CDATA[date-time-string]]></c> is the date and time the message is
-      written, default in local time (can be changed to GMT if one wants
-      to) and is formatted with the ANSI-C function <c><![CDATA[strftime]]></c>
-      using the format string <c><![CDATA[%a %b %e %T %Z %Y]]></c>, which produces
-      messages on the line of <c><![CDATA[===== ALIVE Thu May 15 10:13:36 MEST 2003]]></c>, this can be changed, see below.</p>
+===== <date-time-string>    ]]></code>
+
+    <p><c><![CDATA[date-time-string]]></c> is the date and time the message is
+      written, default in local time (can be changed to UTC if needed).
+      It is formatted with the ANSI-C function <c><![CDATA[strftime]]></c>
+      using the format string <c><![CDATA[%a %b %e %T %Z %Y]]></c>, which
+      produces messages like
+      <c><![CDATA[===== ALIVE Thu May 15 10:13:36 MEST 2003]]></c>; this can
+      be changed, see the next section.</p>
   </section>
 
   <section>
-    <title>Environment variables</title>
-    <p>The following environment variables are recognized by run_erl
-      and change the logging behavior. Also see the notes above to get
-      more info on how the log behaves.</p>
+    <marker id="environment_variables"/>
+    <title>Environment Variables</title>
+    <p>The following environment variables are recognized by <c>run_erl</c>
+      and change the logging behavior. For more information, see the previous
+      section.</p>
+
     <taglist>
-      <tag>RUN_ERL_LOG_ALIVE_MINUTES</tag>
-      <item>How long to wait for output (in minutes) before writing an
-       "ALIVE" message to the log. Default is 15, can never be less
-       than 1.</item>
-      <tag>RUN_ERL_LOG_ACTIVITY_MINUTES</tag>
-      <item>How long erlang need to be inactive before output will be
-       preceded with a timestamp. Default is
-       RUN_ERL_LOG_ALIVE_MINUTES div 3, but never less than 1.</item>
-      <tag>RUN_ERL_LOG_ALIVE_FORMAT</tag>
-      <item>Specifies another format string to be used in the strftime
-       C library call. i.e specifying this to <c><![CDATA["%e-%b-%Y, %T %Z"]]></c>
-       will give log messages with timestamps looking like 
-      <c><![CDATA[15-May-2003, 10:23:04 MET]]></c> etc. See the documentation
-       for the C library function strftime for more
-       information. Default is <c><![CDATA["%a %b %e %T %Z %Y"]]></c>.</item>
-      <tag>RUN_ERL_LOG_ALIVE_IN_UTC</tag>
-      <item>If set to anything else than "0", it will make all
-       times displayed by run_erl to be in UTC (GMT,CET,MET, without
-       DST), rather than
-       in local time. This does not affect data coming from erlang,
-       only the logs output directly by run_erl. The application
-      <c><![CDATA[sasl]]></c> can be modified accordingly by setting the erlang
-       application variable <c><![CDATA[utc_log]]></c> to <c><![CDATA[true]]></c>.</item>
-      <tag>RUN_ERL_LOG_GENERATIONS</tag>
-      <item>Controls the number of log files written before older
-       files are being reused. Default is 5, minimum is 2, maximum is 1000.</item>
-      <tag>RUN_ERL_LOG_MAXSIZE</tag>
-      <item>The size (in bytes) of a log file before switching to a
-       new log file. Default is 100000, minimum is 1000 and maximum is
-       approximately 2^30.</item>
-      <tag>RUN_ERL_DISABLE_FLOWCNTRL</tag>
-      <item>If defined, disables input and output flow control for the pty opend by run_erl.
-       Useful if you want to remove any risk of accidentally blocking the flow control
-       by hit Ctrl-S (instead of Ctrl-D to detach).
-       Which may result in blocking of the entire beam process
-       and in the case of running heart as supervisor
-       even the heart process will be blocked when writing log message to terminal.
-       Leaving the heart process unable to do its work.</item>
+      <tag><c>RUN_ERL_LOG_ALIVE_MINUTES</c></tag>
+      <item>
+        <p>How long to wait for output (in minutes) before writing an
+          "ALIVE" message to the log. Defaults to 15, minimum is 1.</p>
+      </item>
+      <tag><c>RUN_ERL_LOG_ACTIVITY_MINUTES</c></tag>
+      <item>
+        <p>How long Erlang needs to be inactive before output is
+          preceded with a time stamp. Defaults to
+          <c>RUN_ERL_LOG_ALIVE_MINUTES div 3</c>, minimum is 1.</p>
+      </item>
+      <tag><c>RUN_ERL_LOG_ALIVE_FORMAT</c></tag>
+      <item>
+        <p>Specifies another format string to be used in the <c>strftime</c>
+          C library call. That is, specifying this to
+          <c><![CDATA["%e-%b-%Y, %T %Z"]]></c> gives
+          log messages with time stamps like
+          <c><![CDATA[15-May-2003, 10:23:04 MET]]></c>. For more information,
+          see the documentation for the C library function <c>strftime</c>.
+          Defaults to <c><![CDATA["%a %b %e %T %Z %Y"]]></c>.</p>
+      </item>
+      <tag><c>RUN_ERL_LOG_ALIVE_IN_UTC</c></tag>
+      <item>
+        <p>If set to anything else than <c>0</c>, it makes all
+          times displayed by <c>run_erl</c> to be in UTC (GMT, CET, MET,
+          without Daylight Saving Time), rather than in local time.
+          This does not affect data coming from Erlang,
+          only the logs output directly by <c>run_erl</c>. Application
+          <c>SASL</c> can be modified accordingly by setting the Erlang
+          application variable <c><![CDATA[utc_log]]></c> to
+          <c><![CDATA[true]]></c>.</p>
+      </item>
+      <tag><c>RUN_ERL_LOG_GENERATIONS</c></tag>
+      <item>
+        <p>Controls the number of log files written before older
+          files are reused. Defaults to 5, minimum is 2, maximum is 1000.</p>
+      </item>
+      <tag><c>RUN_ERL_LOG_MAXSIZE</c></tag>
+      <item>
+        <p>The size, in bytes, of a log file before switching to a
+          new log file. Defaults to 100000, minimum is 1000, maximum is
+          about 2^30.</p>
+      </item>
+      <tag><c>RUN_ERL_DISABLE_FLOWCNTRL</c></tag>
+      <item>
+        <p>If defined, disables input and output flow control for the pty
+          opend by <c>run_erl</c>. Useful if you want to remove any risk of
+          accidentally blocking the flow control by using Ctrl-S (instead of
+          Ctrl-D to detach), which can result in blocking of the entire Beam
+          process, and in the case of running heart as supervisor even the
+          heart process becomes blocked when writing log message to terminal,
+          leaving the heart process unable to do its work.</p>
+      </item>
     </taglist>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p>start(1), start_erl(1)</p>
+    <title>See Also</title>
+    <p><seealso marker="start"><c>start(1)</c></seealso>,
+      <seealso marker="start_erl"><c>start_erl(1)</c></seealso></p>
   </section>
 </comref>
 
diff --git a/erts/doc/src/start.xml b/erts/doc/src/start.xml
index adacf5b98d..6eac47fe94 100644
--- a/erts/doc/src/start.xml
+++ b/erts/doc/src/start.xml
@@ -28,38 +28,46 @@
     <docno></docno>
     <approved></approved>
     <checked></checked>
-    <date>99-12-15</date>
+    <date>1999-12-15</date>
     <rev></rev>
     <file>start.xml</file>
   </header>
   <com>start</com>
-  <comsummary>OTP start script example for Unix</comsummary>
+  <comsummary>OTP start script example for Unix.</comsummary>
   <description>
-    <p>This describes the <c><![CDATA[start]]></c> script that is an example script on
-      how to startup the Erlang system in embedded mode on Unix.</p>
-    <p>You can read more about the use in the <c><![CDATA[Embedded System User's Guide]]></c>.</p>
+    <p>The <c><![CDATA[start]]></c> script is an example script on
+      how to start up the Erlang system in embedded mode on Unix.</p>
+
+    <p>For more information about the use, see the
+      <seealso marker="doc/embedded:embedded_solaris">
+      Embedded System User's Guide</seealso> in System Documentation.</p>
   </description>
+
   <funcs>
     <func>
       <name>start [ data_file ]</name>
-      <fsummary>This is an example script on how to startup the Erlang system in embedded mode on Unix.</fsummary>
+      <fsummary>Example script on how to start up the Erlang system in embedded
+        mode on Unix.</fsummary>
       <desc>
-        <p>In the example there is one argument</p>
+        <p>Argument:</p>
         <taglist>
-          <tag>data_file</tag>
-          <item>Optional, specifies what <c><![CDATA[start_erl.data]]></c> file
-           to use.</item>
+          <tag><c>data_file</c></tag>
+          <item>
+            <p>Optional. Specifies what <c><![CDATA[start_erl.data]]></c> file
+              to use.</p>
+          </item>
         </taglist>
-        <p>There is also an environment variable <c><![CDATA[RELDIR]]></c> that can
-          be set prior to calling this example that set the directory
+        <p>Environment variable <c><![CDATA[RELDIR]]></c> can
+          be set before calling this example, which sets the directory
           where to find the release files.</p>
       </desc>
     </func>
   </funcs>
 
   <section>
-    <title>SEE ALSO</title>
-    <p>run_erl(1), start_erl(1)</p>
+    <title>See Also</title>
+    <p><seealso marker="run_erl"><c>run_erl(1)</c></seealso>,
+      <seealso marker="start_erl"><c>start_erl(1)</c></seealso></p>
   </section>
 </comref>
 
diff --git a/erts/doc/src/start_erl.xml b/erts/doc/src/start_erl.xml
index 243aeaa717..50f8c58a48 100644
--- a/erts/doc/src/start_erl.xml
+++ b/erts/doc/src/start_erl.xml
@@ -28,117 +28,142 @@
     <docno></docno>
     <approved></approved>
     <checked></checked>
-    <date>98-08-05</date>
+    <date>1998-08-05</date>
     <rev></rev>
     <file>start_erl.xml</file>
   </header>
   <com>start_erl</com>
-  <comsummary>Start Erlang for embedded systems on Windows NT&reg;</comsummary>
+  <comsummary>Start Erlang for embedded systems on Windows systems.</comsummary>
   <description>
-    <p>This describes the <c><![CDATA[start_erl]]></c> program specific to Windows
-      NT. Although there exists programs with the same name on other
-      platforms, their functionality is not the same.</p>
-    <p>The <c><![CDATA[start_erl]]></c> program is distributed both in compiled
+    <p>The <c><![CDATA[start_erl]]></c> program is specific to
+      Windows NT/2000/XP (and later versions of Windows).
+      Although there are programs with the same name on other
+      platforms, their functionality is different.</p>
+
+    <p>This program is distributed both in compiled
       form (under &lt;Erlang root&gt;\\erts-&lt;version&gt;\\bin) and
-      in source form (under &lt;Erlang
-      root&gt;\\erts-&lt;version&gt;\\src).
-      The purpose of the source code is to make it possible to easily
-      customize the program for local needs, such as cyclic restart
-      detection etc. There is also a "make"-file, written for the
-      <c><![CDATA[nmake]]></c> program distributed with Microsoft&reg; Visual
-      C++&reg;. The program can however be compiled with
-      any Win32 C compiler (possibly with slight modifications).</p>
-    <p>The purpose of the program is to aid release handling on
-      Windows NT&reg;. The program should be called by the
+      in source form (under &lt;Erlang root&gt;\\erts-&lt;version&gt;\\src).
+      The purpose of the source code is to ease customization of the
+      program for local needs, such as cyclic restart
+      detection. There is also a "make"-file, written for the
+      <c><![CDATA[nmake]]></c> program distributed with Microsoft Visual
+      C++. This program can, however, be compiled with
+      any Win32 C compiler (possibly with minor modifications).</p>
+
+    <p>This program aids release handling on Windows systems.
+      The program is to be called by the
       <c><![CDATA[erlsrv]]></c> program, read up the release data file
-      start_erl.data and start Erlang. Certain options to start_erl
-      are added and removed by the release handler during upgrade with
-      emulator restart (more specifically the <c><![CDATA[-data]]></c> option).</p>
+      <c>start_erl.data</c>, and start Erlang. Some options to
+      <c>start_erl</c> are added and removed by the release handler
+      during upgrade with emulator restart (more specifically option
+      <c><![CDATA[-data]]></c>).</p>
   </description>
+
   <funcs>
     <func>
       <name>start_erl [&lt;erl options>] ++ [&lt;start_erl options>]</name>
-      <fsummary>Start the Erlang emulator with the correct release data</fsummary>
+      <fsummary>Start the Erlang emulator with the correct release data.
+      </fsummary>
       <desc>
-        <p>The <c><![CDATA[start_erl]]></c> program  in its original form 
+        <p>The <c><![CDATA[start_erl]]></c> program in its original form
           recognizes the following options:</p>
         <taglist>
-          <tag>++</tag>
-          <item>Mandatory, delimits start_erl options from normal Erlang
-           options. Everything on the command line <em>before</em> the
-          <c><![CDATA[++]]></c> is interpreted as options to be sent to the
-          <c><![CDATA[erl]]></c> program. Everything <em>after</em><c><![CDATA[++]]></c> is
-           interpreted as options to <c><![CDATA[start_erl]]></c> itself.</item>
-          <tag>-reldir &lt;release root&gt;</tag>
-
-          <item>Mandatory if the environment variable
-          <c><![CDATA[RELDIR]]></c> is not specified and no
-          <c>-rootdir</c> option is given. Tells start_erl where the
-          root of the release tree is placed in the file-system (typically
-          &lt;Erlang root&gt;\\releases). The
-          <c><![CDATA[start_erl.data]]></c> file is expected to be
-          placed in this directory (if not otherwise specified). If
-          only the <c>-rootdir</c> option is given, the directory is
-          assumed to be &lt;Erlang root&gt;\\releases.</item>
-
-	  <tag>-rootdir &lt;Erlang root directory&gt;</tag> 
-
-	  <item>Mandatory if <c>-reldir</c> is not given and there is
-	  no <c><![CDATA[RELDIR]]></c> in the environment. This
-	  specifies the Erlang installation root directory (under
-	  which the <c>lib</c>, <c>releases</c> and
-	  <c>erts-&lt;Version&gt;</c> directories are placed). If only
-	  <c>-reldir</c> (or the environment variable
-	  <c><![CDATA[RELDIR]]></c>) is given, the Erlang root is assumed to
-	  be the directory exactly one level above the release
-	  directory.</item>
-
-          <tag>-data &lt;data file name&gt;</tag>
-          <item>Optional, specifies another data file than start_erl.data
-           in the &lt;release root&gt;. It is specified relative to the
-           &lt;release root&gt; or absolute (including drive letter
-           etc.). This option is used by the release handler during
-           upgrade and should not be used during normal
-           operation. The release data file should not normally be
-           named differently.</item>
-          <tag>-bootflags &lt;boot flags file name&gt;</tag>
-          <item>Optional, specifies a file name relative to actual release
-           directory (that is the subdirectory of &lt;release
-           root&gt; where the <c><![CDATA[.boot]]></c> file etc. are placed).
-           The contents of this file is appended to the command line
-           when Erlang is started. This makes it easy to start the
-           emulator with different options for different releases.</item>
+          <tag><c>++</c></tag>
+          <item>
+            <p>Mandatory. Delimits <c>start_erl</c> options from normal Erlang
+              options. Everything on the command line <em>before</em>
+              <c><![CDATA[++]]></c> is interpreted as options to be sent to the
+              <c><![CDATA[erl]]></c> program. Everything <em>after</em>
+              <c><![CDATA[++]]></c> is interpreted as options to
+              <c><![CDATA[start_erl]]></c> itself.</p>
+          </item>
+          <tag><c>-reldir &lt;release root&gt;</c></tag>
+          <item>
+            <p>Mandatory if environment variable
+              <c><![CDATA[RELDIR]]></c> is not specified and no
+              <c>-rootdir</c> option is specified. Tells <c>start_erl</c> where
+              the root of the release tree is located in the file system
+              (typically &lt;Erlang root&gt;\\releases). The
+              <c><![CDATA[start_erl.data]]></c> file is expected to be
+              located in this directory (unless otherwise specified). If
+              only option <c>-rootdir</c> is specified, the directory is
+              assumed to be &lt;Erlang root&gt;\\releases.</p>
+          </item>
+          <tag><c>-rootdir &lt;Erlang root directory&gt;</c></tag> 
+          <item>
+            <p>Mandatory if <c>-reldir</c> is not specified and no
+              <c><![CDATA[RELDIR]]></c> exists in the environment. This
+              specifies the Erlang installation root directory (under
+              which the <c>lib</c>, <c>releases</c>, and
+              <c>erts-&lt;Version&gt;</c> directories are located). If only
+              <c>-reldir</c> (or environment variable <c><![CDATA[RELDIR]]></c>)
+              is specified, the Erlang root is assumed to
+              be the directory exactly one level above the release
+              directory.</p>
+          </item>
+          <tag><c>-data &lt;data file name&gt;</c></tag>
+          <item>
+            <p>Optional. Specifies another data file than <c>start_erl.data</c>
+              in the &lt;release root&gt;. It is specified relative to the
+              &lt;release root&gt; or absolute (including drive letter, and so
+              on). This option is used by the release handler during
+              upgrade and is not to be used during normal
+              operation. Normally the release data file is not to be
+              named differently.</p>
+          </item>
+          <tag><c>-bootflags &lt;boot flags file name&gt;</c></tag>
+          <item>
+            <p>Optional. Specifies a file name relative to the release
+              directory (that is, the subdirectory of &lt;release root&gt;
+              where the <c><![CDATA[.boot]]></c> file and others are located).
+              The contents of this file is appended to the command line
+              when Erlang is started. This makes it easy to start the
+              emulator with different options for different releases.</p>
+          </item>
         </taglist>
       </desc>
     </func>
   </funcs>
 
   <section>
-    <title>NOTES</title>
-    <p>As the source code is distributed, it can easily be modified to
-      accept other options. The program must still accept the
-      <c><![CDATA[-data]]></c> option with the semantics described above for the
-      release handler to work correctly.</p>
-    <p>The Erlang emulator is found by examining the registry keys for
-      the emulator version specified in the release data file. The new
-      emulator needs to be properly installed before the upgrade for
-      this to work.</p>
-    <p>Although the program is located together with files specific to
-      emulator version, it is not expected to be specific to the
-      emulator version. The release handler does <em>not</em> change the
-      <c><![CDATA[-machine]]></c> option to <c><![CDATA[erlsrv]]></c> during emulator restart.
-      Place the (possibly customized) <c><![CDATA[start_erl]]></c> program so that
-      it is not overwritten during upgrade. </p>
-    <p>The <c><![CDATA[erlsrv]]></c> program's default options are not
-      sufficient for release handling. The machine <c><![CDATA[erlsrv]]></c>
-      starts should be specified as the <c><![CDATA[start_erl]]></c> program and
-      the arguments should contain the <c><![CDATA[++]]></c> followed by desired
-      options.</p>
+    <title>Notes</title>
+    <list type="bulleted">
+      <item>
+        <p>As the source code is distributed, it can easily be modified to
+          accept other options. The program must still accept option
+          <c><![CDATA[-data]]></c> with the semantics described above for the
+          release handler to work correctly.</p>
+      </item>
+      <item>
+        <p>The Erlang emulator is found by examining the registry keys for
+          the emulator version specified in the release data file. The new
+          emulator must be properly installed before the upgrade for
+          this to work.</p>
+      </item>
+      <item>
+        <p>Although the program is located together with files specific to the
+          emulator version, it is not expected to be specific to the
+          emulator version. The release handler does <em>not</em> change option
+          <c><![CDATA[-machine]]></c> to <c><![CDATA[erlsrv]]></c> during
+          emulator restart. Locate the (possibly customized)
+          <c><![CDATA[start_erl]]></c> program so that it is not overwritten
+          during upgrade.</p>
+      </item>
+      <item>
+        <p>The default options of the <c><![CDATA[erlsrv]]></c> program are not
+          sufficient for release handling. The machine started by
+          <c><![CDATA[erlsrv]]></c> is be specified as the
+          <c><![CDATA[start_erl]]></c> program and the arguments are to contain
+          <c><![CDATA[++]]></c> followed by the desired options.</p>
+      </item>
+    </list>
   </section>
 
   <section>
-    <title>SEE ALSO</title>
-    <p>erlsrv(1), release_handler(3)</p>
+    <title>See Also</title>
+    <p><seealso marker="erlsrv"><c>erlsrv(1)</c></seealso>,
+      <seealso marker="sasl:release_handler">
+      <c>sasl:release_handler(3)</c></seealso></p>
   </section>
 </comref>
 
diff --git a/erts/doc/src/time_correction.xml b/erts/doc/src/time_correction.xml
index 236fe679cb..dbaae4d852 100644
--- a/erts/doc/src/time_correction.xml
+++ b/erts/doc/src/time_correction.xml
@@ -35,12 +35,12 @@
 
   <section>
     <title>New Extended Time Functionality</title>
-    <note><p>As of OTP 18 (<c>ERTS</c> version 7.0) the time functionality of
-    Erlang has been extended. This includes a
+    <note><p>As from Erlang/OTP 18 (<c>ERTS</c> 7.0) the time functionality
+    has been extended. This includes a
     <seealso marker="#The_New_Time_API">new API</seealso>
     for time and
     <seealso marker="#Time_Warp_Modes">time warp
-    modes</seealso> that alter the system behavior when
+    modes</seealso> that change the system behavior when
     system time changes.</p>
 
     <p>The <seealso marker="#No_Time_Warp_Mode">default
@@ -106,14 +106,18 @@
     <section>
       <title>POSIX Time</title>
       <p>Time since
-      <url href="http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap03.html#tag_21_03_00_17">Epoch</url>.
+      <url href="http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap03.html#tag_21_03_00_17">
+      Epoch</url>.
       Epoch is defined to be 00:00:00 <seealso marker="#UTC">UTC</seealso>,
       1970-01-01.
-      <url href="http://pubs.opengroup.org/onlinepubs/009604499/basedefs/xbd_chap04.html#tag_04_14">A day in POSIX time</url>
-      is defined to be exactly 86400 seconds long. Strangely enough
+      <url href="http://pubs.opengroup.org/onlinepubs/009604499/basedefs/xbd_chap04.html#tag_04_14">
+      A day in POSIX time</url>
+      is defined to be exactly 86400 seconds long. Strangely enough,
       Epoch is defined to be a time in UTC, and UTC has another
       definition of how long a day is. Quoting the Open Group
-      <url href="http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap04.html#tag_21_04_15">"POSIX time is therefore not necessarily UTC, despite its appearance"</url>.
+      <url href="http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap04.html#tag_21_04_15">
+      "POSIX time is therefore not necessarily UTC, despite its
+      appearance"</url>.
       The effect of this is that when an UTC leap second is
       inserted, POSIX time either stops for a second, or repeats the
       last second. If an UTC leap second would be deleted (which has not
@@ -157,7 +161,8 @@
       <p>The operating systems view of
       <seealso marker="#POSIX_Time">POSIX time</seealso>. To
       retrieve it, call
-      <seealso marker="kernel:os#system_time/0"><c>os:system_time()</c></seealso>.
+      <seealso marker="kernel:os#system_time/0">
+      <c>os:system_time()</c></seealso>.
       This may or may not be an accurate view of POSIX time. This time
       may typically be adjusted both backwards and forwards without
       limitation. That is, <seealso marker="#Time_Warp">time warps</seealso>
@@ -165,25 +170,26 @@
 
       <p>To get information about the Erlang runtime
       system's source of OS system time, call
-      <seealso marker="erlang#system_info_os_system_time_source"><c>erlang:system_info(os_system_time_source)</c></seealso>.</p>
+      <seealso marker="erlang#system_info_os_system_time_source">
+      <c>erlang:system_info(os_system_time_source)</c></seealso>.</p>
     </section>
 
     <marker id="OS_Monotonic_Time"/>
     <section>
       <title>OS Monotonic Time</title>
-      <p>A monotonically increasing time provided by the operating
-      system. This time does not leap and has a relatively steady
+      <p>A monotonically increasing time provided by the OS.
+      This time does not leap and has a relatively steady
       frequency although not completely correct. However, it is not
       uncommon that OS monotonic time stops if the system is
       suspended. This time typically increases since some
       unspecified point in time that is not connected to
       <seealso marker="#OS_System_Time">OS system time</seealso>.
-      This type of time is not necessarily provided by all
-      operating systems.</p>
+      This type of time is not necessarily provided by all OSs.</p>
 
       <p>To get information about the Erlang
       runtime system's source of OS monotonic time, call
-      <seealso marker="erlang#system_info_os_monotonic_time_source"><c>erlang:system_info(os_monotonic_time_source)</c></seealso>.</p>
+      <seealso marker="erlang#system_info_os_monotonic_time_source">
+      <c>erlang:system_info(os_monotonic_time_source)</c></seealso>.</p>
     </section>
 
     <marker id="Erlang_System_Time"/>
@@ -192,7 +198,8 @@
       <p>The Erlang runtime systems view of
       <seealso marker="#POSIX_Time">POSIX time</seealso>. To
       retrieve it, call
-      <seealso marker="erlang#system_time/0"><c>erlang:system_time()</c></seealso>.</p>
+      <seealso marker="erlang#system_time/0">
+      <c>erlang:system_time()</c></seealso>.</p>
 
       <p>This time may or may not be an accurate view of POSIX time,
       and may
@@ -211,8 +218,8 @@
       <p>A monotonically increasing time provided by the
       Erlang runtime system. Erlang monotonic time increases since
       some unspecified point in time. To retrieve it, call
-      <seealso marker="erlang#monotonic_time/0"><c>erlang:monotonic_time()</c></seealso>.
-      </p>
+      <seealso marker="erlang#monotonic_time/0">
+      <c>erlang:monotonic_time()</c></seealso>.</p>
 
       <p>The <seealso marker="#Time_Accuracy">accuracy</seealso> and
       <seealso marker="#Time_Precision">precision</seealso> of Erlang
@@ -225,7 +232,8 @@
         <item>Accuracy and precision of
           <seealso marker="#OS_System_Time">OS system time</seealso>
         </item>
-          <item><seealso marker="#Time_Warp_Modes">time warp mode</seealso> used
+        <item><seealso marker="#Time_Warp_Modes">
+          time warp mode</seealso> used
         </item>
       </list>
 
@@ -238,16 +246,17 @@
       time is the "time engine" that is used for more or less
       everything that has anything to do with time. All timers,
       regardless of it is a <c>receive ... after</c> timer, BIF timer,
-      or a timer in the <c>timer</c> module, are triggered
-      relative Erlang monotonic time. Even
+      or a timer in the
+      <seealso marker="stdlib:timer"><c>stdlib:timer</c></seealso>
+      module, are triggered relative Erlang monotonic time. Even
       <seealso marker="#Erlang_System_Time">Erlang system
       time</seealso> is based on Erlang monotonic time.
       By adding current Erlang monotonic time with current time
       offset, you get current Erlang system time.</p>
 
-      <p>To retrieve current time offset, call
-      <seealso marker="erlang#time_offset/0"><c>erlang:time_offset/0</c></seealso>.
-      </p>
+      <p>To retrieve the current time offset, call
+      <seealso marker="erlang#time_offset/0">
+      <c>erlang:time_offset/0</c></seealso>.</p>
     </section>
 
   </section>
@@ -278,7 +287,7 @@
   less potent time-keeper than an atomic clock is used.</p>
 
   <p>However, NTP is not fail-safe. The NTP server can be unavailable,
-  <c>ntp.conf</c> can be wrongly configured, or your computer may
+  <c>ntp.conf</c> can be wrongly configured, or your computer can
   sometimes be disconnected from Internet. Furthermore, you can have a
   user (or even system administrator) who thinks the correct
   way to handle Daylight Saving Time is to adjust the clock one
@@ -327,16 +336,18 @@
     implementation in the Erlang runtime system using
     OS monotonic time. To check if your system has support
     for OS monotonic time, call
-    <seealso marker="erlang#system_info_os_monotonic_time_source"><c>erlang:system_info(os_monotonic_time_source)</c></seealso>.
+    <seealso marker="erlang#system_info_os_monotonic_time_source">
+    <c>erlang:system_info(os_monotonic_time_source)</c></seealso>.
     To check if time correction is enabled on your system, call
-    <seealso marker="erlang#system_info_time_correction"><c>erlang:system_info(time_correction)</c></seealso>.</p>
+    <seealso marker="erlang#system_info_time_correction">
+    <c>erlang:system_info(time_correction)</c></seealso>.</p>
 
     <p>To enable or disable time correction, pass command-line argument
-    <seealso marker="erl#+c"><c>+c [true|false]</c></seealso>
-    to <c>erl</c>.</p>
+    <seealso marker="erl#+c"><c>+c [true|false]</c></seealso> to
+    <seealso marker="erl"><c>erl(1)</c></seealso>.</p>
 
     <p>If time correction is disabled, Erlang monotonic time
-    may warp forwards or stop, or even freeze for extended
+    can warp forwards or stop, or even freeze for extended
     periods of time. There are then no guarantees that the frequency
     of the Erlang monotonic clock is accurate or stable.</p>
 
@@ -369,7 +380,7 @@
     <c>erlang:now/0</c> are suboptimal</em> from a performance
     and scalability perspective. So you really want to replace
     the use of it with other functionality. For examples
-    of how to replace the use of <c>erlang:now/0</c>, see Section
+    of how to replace the use of <c>erlang:now/0</c>, see section
     <seealso marker="#Dos_and_Donts">How to Work with the New
     API</seealso>.</p>
   </section>
@@ -378,7 +389,7 @@
     <title>Time Warp Modes</title>
     <marker id="Time_Warp_Modes"/>
     <p>Current <seealso marker="#Erlang_System_Time">Erlang system
-    time</seealso> is determined by adding current
+    time</seealso> is determined by adding the current
     <seealso marker="erlang#monotonic_time/0">Erlang monotonic time</seealso>
     with current
     <seealso marker="erlang#time_offset/0">time offset</seealso>. The
@@ -387,8 +398,8 @@
 
     <p>To set the time warp mode, pass command-line argument
     <seealso marker="erl#+C_"><c>+C
-    [no_time_warp|single_time_warp|multi_time_warp]</c></seealso>
-    to <c>erl</c>.</p>
+    [no_time_warp|single_time_warp|multi_time_warp]</c></seealso> to
+    <seealso marker="erl"><c>erl(1)</c></seealso>.</p>
 
     <marker id="No_Time_Warp_Mode"/>
     <section>
@@ -398,7 +409,7 @@
       not because it is the best mode (which it is not). It is
       default <em>only</em> because this is how the runtime system
       behaved until <c>ERTS</c> 7.0.
-      Ensure that your Erlang code that may execute during a time
+      Ensure that your Erlang code that can execute during a time
       warp is <seealso marker="#Time_Warp_Safe_Code">time warp
       safe</seealso> before enabling other modes.</p>
 
@@ -422,8 +433,8 @@
     <marker id="Single_Time_Warp_Mode"/>
     <section>
       <title>Single Time Warp Mode</title>
-      <p>This mode is more or less a backwards compatibility mode
-      as of its introduction.</p>
+      <p>This mode is more or less a backward compatibility mode
+      as from its introduction.</p>
 
       <p>On an embedded system it is not uncommon that the system
       has no power supply, not even a battery, when it is
@@ -475,11 +486,12 @@
 	<item>
 	  <p>This phase begins when the user finalizes the time
 	  offset by calling
-	  <seealso marker="erlang#system_flag_time_offset"><c>erlang:system_flag(time_offset, finalize)</c></seealso>.
+	  <seealso marker="erlang#system_flag_time_offset">
+	  <c>erlang:system_flag(time_offset, finalize)</c></seealso>.
 	  The finalization can only be performed once.</p>
 
 	  <p>During finalization, the time offset is adjusted and
-	  fixated so that current Erlang system time aligns with
+	  fixed so that current Erlang system time aligns with the
 	  current OS system time. As the time offset can
 	  change during the finalization, Erlang system time
 	  can do a time warp at this point. The time offset is
@@ -488,7 +500,7 @@
 	  correction from now on also makes adjustments
 	  to align Erlang system time with OS system
 	  time. When the system is in the final phase, it behaves
-	  exactly as in the <seealso marker="#No_Time_Warp_Mode">no
+	  exactly as in <seealso marker="#No_Time_Warp_Mode">no
 	  time warp mode</seealso>.</p>
 	</item>
       </taglist>
@@ -520,7 +532,7 @@
       may behave very bad.</p>
 
       <p>Assuming that these requirements are fulfilled,
-      time correction is enabled, and that OS system time
+      time correction is enabled, and OS system time
       is adjusted using a time adjustment protocol such as NTP,
       only small adjustments of Erlang monotonic
       time are needed to keep system times
@@ -529,9 +541,10 @@
       inserted (or deleted) leap seconds.</p>
 
       <warning><p>To use this mode, ensure that
-      all Erlang code that will execute in both phases are
+      all Erlang code that will execute in both phases is
       <seealso marker="#Time_Warp_Safe_Code">time warp
       safe</seealso>.</p>
+
       <p>Code executing only in the final phase does not have
       to be able to cope with the time warp.</p></warning>
     </section>
@@ -542,13 +555,13 @@
       <p><em>Multi-time warp mode in combination with time
       correction is the preferred configuration</em>. This as
       the Erlang runtime system have better performance, scale
-      better, and behave better on almost all platforms. In
-      addition, the accuracy and precision of time measurements
+      better, and behave better on almost all platforms.
+      Also, the accuracy and precision of time measurements
       are better. Only Erlang runtime systems executing on
       ancient platforms benefit from another configuration.</p>
 
-      <p>The time offset may change at any time without limitations.
-      That is, Erlang system time may perform time warps both
+      <p>The time offset can change at any time without limitations.
+      That is, Erlang system time can perform time warps both
       forwards and backwards at <em>any</em> time. As we align
       Erlang system time with OS system time by changing
       the time offset, we can enable a time correction that tries
@@ -582,8 +595,8 @@
     such issues. To improve this, the new API spreads different
     functionality over multiple functions.</p>
 
-    <p>To be backwards compatible, <c>erlang:now/0</c>
-    remains as is, but <em>you are strongly discouraged from using
+    <p>To be backward compatible, <c>erlang:now/0</c>
+    remains "as is", but <em>you are strongly discouraged from using
     it</em>. Many use cases of <c>erlang:now/0</c>
     prevents you from using the new
     <seealso marker="#Multi_Time_Warp_Mode">multi-time warp
@@ -597,38 +610,60 @@
     <p>The new API consists of the following new BIFs:</p>
 
     <list>
-      <item><p><seealso marker="erlang#convert_time_unit/3"><c>erlang:convert_time_unit/3</c></seealso></p></item>
-      <item><p><seealso marker="erlang#monotonic_time/0"><c>erlang:monotonic_time/0</c></seealso></p></item>
-      <item><p><seealso marker="erlang#monotonic_time/1"><c>erlang:monotonic_time/1</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_time/0"><c>erlang:system_time/0</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_time/1"><c>erlang:system_time/1</c></seealso></p></item>
-      <item><p><seealso marker="erlang#time_offset/0"><c>erlang:time_offset/0</c></seealso></p></item>
-      <item><p><seealso marker="erlang#time_offset/1"><c>erlang:time_offset/1</c></seealso></p></item>
-      <item><p><seealso marker="erlang#timestamp/0"><c>erlang:timestamp/0</c></seealso></p></item>
-      <item><p><seealso marker="erlang#unique_integer/0"><c>erlang:unique_integer/0</c></seealso></p></item>
-      <item><p><seealso marker="erlang#unique_integer/1"><c>erlang:unique_integer/1</c></seealso></p></item>
-      <item><p><seealso marker="kernel:os#system_time/0"><c>os:system_time/0</c></seealso></p></item>
-      <item><p><seealso marker="kernel:os#system_time/1"><c>os:system_time/1</c></seealso></p></item>
+      <item><p><seealso marker="erlang#convert_time_unit/3">
+        <c>erlang:convert_time_unit/3</c></seealso></p></item>
+      <item><p><seealso marker="erlang#monotonic_time/0">
+        <c>erlang:monotonic_time/0</c></seealso></p></item>
+      <item><p><seealso marker="erlang#monotonic_time/1">
+        <c>erlang:monotonic_time/1</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_time/0">
+        <c>erlang:system_time/0</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_time/1">
+        <c>erlang:system_time/1</c></seealso></p></item>
+      <item><p><seealso marker="erlang#time_offset/0">
+        <c>erlang:time_offset/0</c></seealso></p></item>
+      <item><p><seealso marker="erlang#time_offset/1">
+        <c>erlang:time_offset/1</c></seealso></p></item>
+      <item><p><seealso marker="erlang#timestamp/0">
+        <c>erlang:timestamp/0</c></seealso></p></item>
+      <item><p><seealso marker="erlang#unique_integer/0">
+        <c>erlang:unique_integer/0</c></seealso></p></item>
+      <item><p><seealso marker="erlang#unique_integer/1">
+        <c>erlang:unique_integer/1</c></seealso></p></item>
+      <item><p><seealso marker="kernel:os#system_time/0">
+        <c>os:system_time/0</c></seealso></p></item>
+      <item><p><seealso marker="kernel:os#system_time/1">
+        <c>os:system_time/1</c></seealso></p></item>
     </list>
 
-    <p>The new API also consists of extensions of the following existing BIFs:</p>
+    <p>The new API also consists of extensions of the following existing BIFs:
+    </p>
 
     <list>
-      <item><p><seealso marker="erlang#monitor/2"><c>erlang:monitor(time_offset, clock_service)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_flag_time_offset"><c>erlang:system_flag(time_offset, finalize)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_info_os_monotonic_time_source"><c>erlang:system_info(os_monotonic_time_source)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_info_os_system_time_source"><c>erlang:system_info(os_system_time_source)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_info_time_offset"><c>erlang:system_info(time_offset)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_info_time_warp_mode"><c>erlang:system_info(time_warp_mode)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_info_time_correction"><c>erlang:system_info(time_correction)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_info_start_time"><c>erlang:system_info(start_time)</c></seealso></p></item>
-      <item><p><seealso marker="erlang#system_info_end_time"><c>erlang:system_info(end_time)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#monitor/2">
+        <c>erlang:monitor(time_offset, clock_service)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_flag_time_offset">
+        <c>erlang:system_flag(time_offset, finalize)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_info_os_monotonic_time_source">
+        <c>erlang:system_info(os_monotonic_time_source)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_info_os_system_time_source">
+        <c>erlang:system_info(os_system_time_source)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_info_time_offset">
+        <c>erlang:system_info(time_offset)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_info_time_warp_mode">
+        <c>erlang:system_info(time_warp_mode)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_info_time_correction">
+        <c>erlang:system_info(time_correction)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_info_start_time">
+        <c>erlang:system_info(start_time)</c></seealso></p></item>
+      <item><p><seealso marker="erlang#system_info_end_time">
+        <c>erlang:system_info(end_time)</c></seealso></p></item>
     </list>
 
     <marker id="The_New_Erlang_Monotonic_Time"/>
     <section>
       <title>New Erlang Monotonic Time</title>
-      <p>Erlang monotonic time as such is new as of <c>ERTS</c> 7.0.
+      <p>Erlang monotonic time as such is new as from <c>ERTS</c> 7.0.
       It is introduced to detach time measurements, such as elapsed
       time from calendar time. In many use cases there is a need to
       measure elapsed time or specify a time relative to another point
@@ -649,7 +684,7 @@
       modes, and only fully separated in the
       <seealso marker="#Multi_Time_Warp_Mode">multi-time
       warp mode</seealso>. All other modes than the
-      multi-time warp mode are for backwards
+      multi-time warp mode are for backward
       compatibility reasons. When using these modes, the
       accuracy of Erlang monotonic time suffer, as
       the adjustments of Erlang monotonic time in these
@@ -672,15 +707,17 @@
 
       <p>To be able to react to a change in Erlang
       system time, you must be able to detect that it
-      happened. The change in Erlang system time occurs when
+      happened. The change in Erlang system time occurs when the
       current time offset is changed. We have therefore
       introduced the possibility to monitor the time offset using
-      <seealso marker="erlang#monitor/2"><c>erlang:monitor(time_offset, clock_service)</c></seealso>.
+      <seealso marker="erlang#monitor/2">
+      <c>erlang:monitor(time_offset, clock_service)</c></seealso>.
       A process monitoring the time
       offset is sent a message on the following format
       when the time offset is changed:</p>
 
-      <code type="none">{'CHANGE', MonitorReference, time_offset, clock_service, NewTimeOffset}</code>
+      <code type="none">
+{'CHANGE', MonitorReference, time_offset, clock_service, NewTimeOffset}</code>
     </section>
 
     <marker id="Unique_Values"/>
@@ -690,8 +727,8 @@
       produces unique and strictly monotonically increasing
       values. To detach this functionality from
       time measurements, we have introduced
-      <seealso marker="erlang#unique_integer/1"><c>erlang:unique_integer()</c></seealso>.
-      </p>
+      <seealso marker="erlang#unique_integer/1">
+      <c>erlang:unique_integer()</c></seealso>.</p>
     </section>
 
     <marker id="Dos_and_Donts"/>
@@ -699,27 +736,28 @@
       <title>How to Work with the New API</title>
       <p>Previously <c>erlang:now/0</c> was the only option for doing
       many things. This section deals with some things that
-      <c>erlang:now/0</c> can be used for, and how you are to
-      these using the new API.</p>
+      <c>erlang:now/0</c> can be used for, and how you use the new API.</p>
 
       <marker id="Dos_and_Donts_Retrieve_Erlang_System_Time"/>
       <section>
 	<title>Retrieve Erlang System Time</title>
 	<dont>
 	  <p>
-	    Use <c>erlang:now/0</c> to retrieve current Erlang system time.
+	    Use <c>erlang:now/0</c> to retrieve the current Erlang system time.
 	  </p>
 	</dont>
 	<do>
 	  <p>
 	    Use
-	    <seealso marker="erlang#system_time/1"><c>erlang:system_time/1</c></seealso>
-	    to retrieve current Erlang system time on the
+            <seealso marker="erlang#system_time/1">
+            <c>erlang:system_time/1</c></seealso>
+	    to retrieve the current Erlang system time on the
 	    <seealso marker="erlang#type_time_unit">time unit</seealso>
 	    of your choice.</p>
-	    <p>If you want the same format as returned by <c>erlang:now/0</c>, use
-	    <seealso marker="erlang#timestamp/0"><c>erlang:timestamp/0</c></seealso>.
-	   </p>
+            <p>If you want the same format as returned by <c>erlang:now/0</c>,
+            use <seealso marker="erlang#timestamp/0">
+	    <c>erlang:timestamp/0</c></seealso>.
+	  </p>
 	</do>
       </section>
 
@@ -728,28 +766,31 @@
 	<title>Measure Elapsed Time</title>
 	<dont>
 	  <p>
-	    Take timestamps with <c>erlang:now/0</c> and calculate
+	    Take time stamps with <c>erlang:now/0</c> and calculate
 	    the difference in time with
-	    <seealso marker="stdlib:timer#now_diff/2"><c>timer:now_diff/2</c></seealso>.
+            <seealso marker="stdlib:timer#now_diff/2">
+            <c>timer:now_diff/2</c></seealso> in <c>STDLIB</c>.
 	  </p>
 	</dont>
 	<do>
 	  <p>
-	    Take timestamps with
-	    <seealso marker="erlang#monotonic_time/0"><c>erlang:monotonic_time/0</c></seealso>
+	    Take time stamps with
+            <seealso marker="erlang#monotonic_time/0">
+            <c>erlang:monotonic_time/0</c></seealso>
 	    and calculate the time difference using ordinary subtraction.
-	    The result will be in <c>native</c>
+	    The result is in <c>native</c>
 	    <seealso marker="erlang#type_time_unit">time unit</seealso>.
 	    If you want to convert the
 	    result to another time unit, you can use
-	    <seealso marker="erlang#convert_time_unit/3"><c>erlang:convert_time_unit/3</c></seealso>.
-	    </p>
-
-	    <p>An easier way to do this is to use
-	    <seealso marker="erlang#monotonic_time/1"><c>erlang:monotonic_time/1</c></seealso>
+            <seealso marker="erlang#convert_time_unit/3">
+            <c>erlang:convert_time_unit/3</c></seealso>.
+	  </p>
+	  <p>An easier way to do this is to use
+	    <seealso marker="erlang#monotonic_time/1">
+	    <c>erlang:monotonic_time/1</c></seealso>
 	    with the desired time unit. However, you can then lose accuracy
 	    and precision.
-	    </p>
+	  </p>
 	</do>
       </section>
 
@@ -758,7 +799,7 @@
 	<title>Determine Order of Events</title>
 	<dont>
 	  <p>
-	    Determine the order of events by saving a timestamp
+	    Determine the order of events by saving a time stamp
 	    with <c>erlang:now/0</c> when the event occurs.
 	  </p>
 	</dont>
@@ -766,8 +807,9 @@
 	  <p>
 	    Determine the order of events by saving the integer
 	    returned by
-	    <seealso marker="erlang#unique_integer/1"><c>erlang:unique_integer([monotonic])</c></seealso>
-	    when the event occurs. These integers will be strictly
+	    <seealso marker="erlang#unique_integer/1">
+	    <c>erlang:unique_integer([monotonic])</c></seealso>
+	    when the event occurs. These integers are strictly
 	    monotonically ordered on current runtime system instance
 	    corresponding to creation time.
 	  </p>
@@ -779,7 +821,7 @@
 	<title>Determine Order of Events with Time of the Event</title>
 	<dont>
 	  <p>
-	    Determine the order of events by saving a timestamp
+	    Determine the order of events by saving a time stamp
 	    with <c>erlang:now/0</c> when the event occurs.
 	  </p>
 	</dont>
@@ -795,18 +837,19 @@ Time = erlang:monotonic_time(),
 UMI = erlang:unique_integer([monotonic]),
 EventTag = {Time, UMI}</code>
 
-	    <p>These tuples will be strictly monotonically ordered
-	    on current runtime system instance according to
+	    <p>These tuples are strictly monotonically ordered
+	    on the current runtime system instance according to
 	    creation time. It is important that the
 	    monotonic time is in the first element (the most
-	    significant element when comparing 2-tuples). Using
+	    significant element when comparing two-tuples). Using
 	    the monotonic time in the tuples, you can calculate time
 	    between events.</p>
 
 	    <p>If you are interested in Erlang system time at the
 	    time when the event occurred, you can also save the time
 	    offset before or after saving the events using
-	    <seealso marker="erlang#time_offset/0"><c>erlang:time_offset/0</c></seealso>.
+	    <seealso marker="erlang#time_offset/0">
+	    <c>erlang:time_offset/0</c></seealso>.
 	    Erlang monotonic time added with the time
 	    offset corresponds to Erlang system time.</p>
 
@@ -814,7 +857,7 @@ EventTag = {Time, UMI}</code>
 	    can change, and you want to get the actual
 	    Erlang system time when the event occurred, you can
 	    save the time offset as a third element in the tuple
-	    (the least significant element when comparing 3-tuples).</p>
+	    (the least significant element when comparing three-tuples).</p>
 	</do>
       </section>
 
@@ -830,10 +873,12 @@ EventTag = {Time, UMI}</code>
 	<do>
 	  <p>
 	    Use the value returned from
-	    <seealso marker="erlang#unique_integer/0"><c>erlang:unique_integer/0</c></seealso>
+	    <seealso marker="erlang#unique_integer/0">
+	    <c>erlang:unique_integer/0</c></seealso>
 	    to create a name unique on the current runtime system
 	    instance. If you only want positive integers, you can use
-	    <seealso marker="erlang#unique_integer/1"><c>erlang:unique_integer([positive])</c></seealso>.
+	    <seealso marker="erlang#unique_integer/1">
+	    <c>erlang:unique_integer([positive])</c></seealso>.
 	  </p>
 	</do>
       </section>
@@ -849,12 +894,15 @@ EventTag = {Time, UMI}</code>
 	<do>
 	  <p>
 	    Seed random number generation using a combination of
-	    <seealso marker="erlang#monotonic_time/0"><c>erlang:monotonic_time()</c></seealso>,
-	    <seealso marker="erlang#time_offset/0"><c>erlang:time_offset()</c></seealso>,
-	    <seealso marker="erlang#unique_integer/0"><c>erlang:unique_integer()</c></seealso>,
+	    <seealso marker="erlang#monotonic_time/0">
+	    <c>erlang:monotonic_time()</c></seealso>,
+	    <seealso marker="erlang#time_offset/0">
+	    <c>erlang:time_offset()</c></seealso>,
+	    <seealso marker="erlang#unique_integer/0">
+	    <c>erlang:unique_integer()</c></seealso>,
             and other functionality.
 	  </p>
-	  </do>
+	</do>
       </section>
 
       <p>To sum up this section: <em>Do not use <c>erlang:now/0</c>.</em></p>
@@ -867,9 +915,9 @@ EventTag = {Time, UMI}</code>
     <p>It can be required that your code must run on a variety
     of OTP installations of different OTP releases. If so, you
     cannot use the new API out of the box, as it will
-    not be available on old pre OTP 18 releases. The solution
+    not be available on old pre-OTP 18 releases. The solution
     is <em>not</em> to avoid using the new API, as your
-    code then would not benefit from the scalability
+    code would then not benefit from the scalability
     and accuracy improvements made. Instead, use the
     new API when available, and fall back on <c>erlang:now/0</c>
     when the new API is unavailable.</p>
@@ -879,16 +927,20 @@ EventTag = {Time, UMI}</code>
 
     <list type="bulleted">
       <item>
-        <seealso marker="erlang#system_info_start_time"><c>erlang:system_info(start_time)</c></seealso>
+        <seealso marker="erlang#system_info_start_time">
+	<c>erlang:system_info(start_time)</c></seealso>
       </item>
       <item>
-        <seealso marker="erlang#system_info_end_time"><c>erlang:system_info(end_time)</c></seealso>
+        <seealso marker="erlang#system_info_end_time">
+	<c>erlang:system_info(end_time)</c></seealso>
       </item>
       <item>
-        <seealso marker="erlang#system_info_os_monotonic_time_source"><c>erlang:system_info(os_monotonic_time_source)</c></seealso>
+        <seealso marker="erlang#system_info_os_monotonic_time_source">
+	<c>erlang:system_info(os_monotonic_time_source)</c></seealso>
       </item>
       <item>
-        <seealso marker="erlang#system_info_os_system_time_source"><c>erlang:system_info(os_system_time_source)</c></seealso>)
+        <seealso marker="erlang#system_info_os_system_time_source">
+	<c>erlang:system_info(os_system_time_source)</c></seealso>)
       </item>
     </list>
 
diff --git a/erts/doc/src/tty.xml b/erts/doc/src/tty.xml
index b2866c82cf..51db1ba8e2 100644
--- a/erts/doc/src/tty.xml
+++ b/erts/doc/src/tty.xml
@@ -22,7 +22,7 @@
 
     </legalnotice>
 
-    <title>tty - A command line interface</title>
+    <title>tty - A Command-Line Interface</title>
     <prepared>ETX/B/SFP C. Granbom</prepared>
     <responsible></responsible>
     <docno></docno>
@@ -32,24 +32,48 @@
     <rev>A</rev>
     <file>tty.xml</file>
   </header>
-  <p><c><![CDATA[tty]]></c> is a simple command line interface program where keystrokes are collected and interpreted. Completed lines are sent to the shell for interpretation. There is a simple history mechanism, which saves previous lines. These can be edited before sending them to the shell.
-    <c><![CDATA[tty]]></c> is started when Erlang is started with the command:<br></br></p>
-  <p><em>erl</em></p>
-  <p><c><![CDATA[tty]]></c> operates in one of two modes:<br></br></p>
+  <p><c><![CDATA[tty]]></c> is a simple command-line interface program where
+    keystrokes are collected and interpreted. Completed lines are sent to the
+    shell for interpretation. A simple history mechanism saves previous lines,
+    which can be edited before sending them to the shell. <c><![CDATA[tty]]></c>
+    is started when Erlang is started with the following command:</p>
+
+  <pre>
+erl</pre>
+
+  <p><c><![CDATA[tty]]></c> operates in one of two modes:</p>
+
   <list type="bulleted">
     <item>
-      <p><em>normal mode</em>, in which lines of text can be edited and sent to the shell.</p>
+      <p>Normal mode, in which text lines can be edited and sent to the
+      shell.</p>
     </item>
     <item>
-      <p><em>shell break</em> mode, which allows the user to kill the current shell, start multiple shells etc. Shell break mode is started by typing <em>Control G</em>.</p>
+      <p>Shell break mode, which allows the user to kill the current shell,
+        start multiple shells, and so on.</p>
     </item>
   </list>
 
   <section>
     <title>Normal Mode</title>
-    <p>In normal mode keystrokes from the user are collected and interpreted by <c><![CDATA[tty]]></c>. Most of the <em>emacs</em> line editing commands are supported. The following is a complete list of the supported line editing commands.<br></br></p>
-    <p><em>Note:</em>	The notation <c><![CDATA[C-a]]></c> means pressing the control key and the letter <c><![CDATA[a]]></c> simultaneously. <c><![CDATA[M-f]]></c> means pressing the <c><![CDATA[ESC]]></c> key followed by the letter <c><![CDATA[f]]></c>. <c><![CDATA[Home]]></c> and <c><![CDATA[End]]></c> represent the keys with the same name on the keyboard, whereas <c><![CDATA[Left]]></c> and <c><![CDATA[Right]]></c> represent the corresponding arrow keys.
-      </p>
+    <p>In normal mode keystrokes from the user are collected and interpreted by
+      <c><![CDATA[tty]]></c>. Most of the <em>Emacs</em> line-editing commands
+      are supported. The following is a complete list of the supported
+      line-editing commands.</p>
+
+    <p>Typographic conventions:</p>
+
+    <list type="bulleted">
+      <item><c>C-a</c> means pressing the <em>Ctrl</em> key and the letter
+        <c>a</c> simultaneously.</item>
+      <item><c>M-f</c> means pressing the <em>Esc</em> key and the letter
+        <c>f</c> in sequence.</item>
+      <item><c>Home</c> and <c>End</c> represent the keys with the same
+        name on the keyboard.</item>
+      <item><c>Left</c> and <c>Right</c> represent the corresponding arrow
+        keys.</item>
+    </list>
+
     <table>
       <row>
         <cell align="left" valign="middle"><em>Key Sequence</em></cell>
@@ -121,11 +145,13 @@
       </row>
       <row>
         <cell align="left" valign="middle">C-n</cell>
-        <cell align="left" valign="middle">Fetch next line from the history buffer</cell>
+        <cell align="left" valign="middle">Fetch next line from the history
+          buffer</cell>
       </row>
       <row>
         <cell align="left" valign="middle">C-p</cell>
-        <cell align="left" valign="middle">Fetch previous line from the history buffer</cell>
+        <cell align="left" valign="middle">Fetch previous line from the history
+          buffer</cell>
       </row>
       <row>
         <cell align="left" valign="middle">C-t</cell>
@@ -139,23 +165,18 @@
         <cell align="left" valign="middle">C-y</cell>
         <cell align="left" valign="middle">Insert previously killed text</cell>
       </row>
-      <tcaption>tty text editing</tcaption>
+      <tcaption>tty Text Editing</tcaption>
     </table>
   </section>
 
   <section>
     <title>Shell Break Mode</title>
-    <p><em>tty</em> enters <em>shell</em> break mode when you type <em>Control G</em>. In this mode you can:<br></br></p>
+    <p>In this mode the following can be done:</p>
+
     <list type="bulleted">
-      <item>
-        <p>Kill or suspend the current shell</p>
-      </item>
-      <item>
-        <p>Connect to a suspended shell</p>
-      </item>
-      <item>
-        <p>Start a new shell</p>
-      </item>
+      <item>Kill or suspend the current shell</item>
+      <item>Connect to a suspended shell</item>
+      <item>Start a new shell</item>
     </list>
   </section>
 </chapter>
diff --git a/erts/doc/src/werl.xml b/erts/doc/src/werl.xml
index 1a3cb6f502..995095c0d8 100644
--- a/erts/doc/src/werl.xml
+++ b/erts/doc/src/werl.xml
@@ -28,62 +28,91 @@
     <docno>1</docno>
     <approved>Bjarne D&auml;cker</approved>
     <checked></checked>
-    <date>98-01-26</date>
+    <date>1998-01-26</date>
     <rev>A</rev>
     <file>werl.xml</file>
   </header>
   <com>werl</com>
   <comsummary>The Erlang Emulator</comsummary>
   <description>
-    <p>On Windows, the preferred way to start the Erlang system for interactive use is:</p>
+    <p>On Windows, the preferred way to start the Erlang system for interactive
+      use is as follows:</p>
+
     <p><c><![CDATA[werl <arguments>]]></c></p>
 
-    <p>This will start Erlang in its own window, with fully
-      functioning command-line editing and scrollbars.  All flags
+    <p>This starts Erlang in its own window, with fully
+      functioning command-line editing and scrollbars. All flags
       except <c><![CDATA[-oldshell]]></c> work as they do for
-      the <seealso marker="erl">erl</seealso> command.</p>
+      command <seealso marker="erl"><c>erl</c></seealso>.</p>
+
+    <list type="bulleted">
+      <item>
+        <p>To copy text to the clipboard, use <c>Ctrl-C</c>.</p>
+      </item>
+      <item>
+        <p>To paste text, use <c>Ctrl-V</c>.</p>
+      </item>
+      <item>
+        <p>To interrupt the runtime system or the shell process (depending
+          on what has been specified with system flag <c>+B</c>), use
+          <c>Ctrl-Break</c>.</p>
+      </item>
+    </list>
 
-    <p>Ctrl-C is reserved for copying text to the clipboard (Ctrl-V to paste).
-      To interrupt the runtime system or the shell process (depending on what
-      has been specified with the +B system flag), you should use Ctrl-Break.</p>
     <p>In cases where you want to redirect standard input and/or
-      standard output or use Erlang in a pipeline, the <c>werl</c> is
-      not suitable, and the <c>erl</c> program should be used instead.</p>
+      standard output or use Erlang in a pipeline, <c>werl</c> is
+      not suitable, and the <c>erl</c> program is to be used instead.</p>
     
-    <p>The <c>werl</c> window is in many ways modelled after the <c>xterm</c> 
+    <p>The <c>werl</c> window is in many ways modeled after the <c>xterm</c>
       window present on other platforms, as the <c>xterm</c> model
-      fits well with line oriented command based interaction. This
-      means that selecting text is line oriented rather than rectangle
-      oriented.</p>
-
-    <p>To select text in the <c>werl</c> window , simply press and hold
-      the left mouse button and drag the mouse over the text you want
-      to select. If the selection crosses line boundaries, the
-      selected text will consist of complete lines where applicable
-      (just like in a word processor). To select more text than fits
-      in the window, start by selecting a small portion in the
-      beginning of the text you want, then use the scrollbar
-      to view the end of the desired selection, point to it and press
-      the <em>right</em> mouse-button. The whole area between your
-      first selection and the point where you right-clicked will be
-      included in the selection.</p>
+      fits well with line-oriented command-based interaction. This
+      means that selecting text is line-oriented rather than
+      rectangle-oriented.</p>
 
-    <p>The selected text is copied to the clipboard by either
-      pressing <c>Ctrl-C</c>, using the menu or pressing the copy 
-      button in the toolbar.</p>
+    <list type="bulleted">
+      <item>
+        <p>To select text in the <c>werl</c> window, press and hold
+          the left mouse button and drag the mouse over the text you want
+          to select. If the selection crosses line boundaries, the
+          selected text consists of complete lines where applicable
+          (just like in a word processor).</p>
+      </item>
+      <item>
+        <p>To select more text than fits
+          in the window, start by selecting a small part in the
+          beginning of the text you want, then use the scrollbar
+          to view the end of the desired selection, point to it, and press
+          the <em>right</em> mouse button. The whole area between your
+          first selection and the point where you right-clicked is
+          included in the selection.</p>
+      </item>
+      <item>
+        <p>To copy the selected text to the clipboard, either
+          use <c>Ctrl-C</c>, use the menu, or press the copy
+          button in the toolbar.</p>
+      </item>
+    </list>
 
-    <p>Pasted text is always inserted at the current prompt position
-      and will be interpreted by Erlang as usual keyboard input.</p>
+    <p>Pasted text is inserted at the current prompt position
+      and is interpreted by Erlang as usual keyboard input.</p>
 
-    <p>Previous command lines can be retrieved by pressing the <c>Up
-      arrow</c> or by pressing <c>Ctrl-P</c>. There is also a drop
-      down box in the toolbar containing the command
-      history. Selecting a command in the drop down box will insert it
-      at the prompt, just as if you used the keyboard to retrieve the
+    <list type="bulleted">
+      <item>
+        <p>To retrieve previous command lines, press the <c>Up arrow</c> or
+          use <c>Ctrl-P</c>.</p>
+      </item>
+    </list>
+      
+    <p>A drop-down box in the toolbar contains the command
+      history. Selecting a command in the drop-down box inserts the command
+      at the prompt, as if you used the keyboard to retrieve the
       command.</p>
-   
-    <p>Closing the <c>werl</c> window will stop the Erlang emulator.</p>
 
+    <list type="bulleted">
+      <item>
+        <p>To stop the Erlang emulator, close the <c>werl</c> window.</p>
+      </item>
+    </list>
   </description>
 </comref>
 
diff --git a/erts/doc/src/zlib.xml b/erts/doc/src/zlib.xml
index a3c94e4a7f..138414a880 100644
--- a/erts/doc/src/zlib.xml
+++ b/erts/doc/src/zlib.xml
@@ -30,13 +30,18 @@
     <file>zlib.xml</file>
   </header>
   <module>zlib</module>
-  <modulesummary>Zlib Compression interface.</modulesummary>
+  <modulesummary>zlib compression interface.</modulesummary>
   <description>
-    <p>The zlib module provides an API for the zlib library
-      (http://www.zlib.org).
-      It is used to compress and decompress data. The
-      data format is described by RFCs 1950 to 1952.</p>
-    <p>A typical (compress) usage looks like:</p>
+    <p>This module provides an API for the zlib library
+      (<url href="http://www.zlib.net">www.zlib.net</url>).
+      It is used to compress and decompress data.
+      The data format is described by
+      <url href="https://www.ietf.org/rfc/rfc1950.txt">RFC 1950</url>,
+      <url href="https://www.ietf.org/rfc/rfc1951.txt">RFC 1951</url>, and
+      <url href="https://www.ietf.org/rfc/rfc1952.txt">RFC 1952</url>.</p>
+
+    <p>A typical (compress) usage is as follows:</p>
+
     <pre>
 Z = zlib:open(),
 ok = zlib:deflateInit(Z,default),
@@ -50,29 +55,25 @@ Last = zlib:deflate(Z, [], finish),
 ok = zlib:deflateEnd(Z),
 zlib:close(Z),
 list_to_binary([Compressed|Last])</pre>
+
     <p>In all functions errors, <c>{'EXIT',{Reason,Backtrace}}</c>,
-      might be thrown, where <c>Reason</c> describes the
-      error. Typical reasons are:</p>
+      can be thrown, where <c>Reason</c> describes the error.</p>
+
+    <p>Typical <c>Reasons</c>s:</p>
+
     <taglist>
       <tag><c>badarg</c></tag>
-      <item>
-        <p>Bad argument</p>
+      <item>Bad argument.
       </item>
       <tag><c>data_error</c></tag>
-      <item>
-        <p>The data contains errors</p>
+      <item>The data contains errors.
       </item>
       <tag><c>stream_error</c></tag>
-      <item>
-        <p>Inconsistent stream state</p>
-      </item>
+      <item>Inconsistent stream state.</item>
       <tag><c>einval</c></tag>
-      <item>
-        <p>Bad value or wrong function called</p>
-      </item>
+      <item>Bad value or wrong function called.</item>
       <tag><c>{need_dictionary,Adler32}</c></tag>
-      <item>
-        <p>See <c>inflate/2</c></p>
+      <item>See <seealso marker="#inflate/2"><c>inflate/2</c></seealso>.
       </item>
     </taglist>
   </description>
@@ -81,7 +82,7 @@ list_to_binary([Compressed|Last])</pre>
     <datatype>
       <name name="zstream"/>
       <desc>
-        <p>A zlib stream, see <seealso marker="#open/0">open/0</seealso>.
+        <p>A zlib stream, see <seealso marker="#open/0"><c>open/0</c></seealso>.
         </p>
        </desc>
     </datatype>
@@ -104,129 +105,144 @@ list_to_binary([Compressed|Last])</pre>
       </desc>
     </datatype>
   </datatypes>
+
   <funcs>
     <func>
       <name name="adler32" arity="2"/>
-      <fsummary>Calculate the adler checksum</fsummary>
+      <fsummary>Calculate the Adler checksum.</fsummary>
       <desc>
-        <p>Calculate the Adler-32 checksum for <c><anno>Data</anno></c>.</p>
+        <p>Calculates the Adler-32 checksum for <c><anno>Data</anno></c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="adler32" arity="3"/>
-      <fsummary>Calculate the adler checksum</fsummary>
+      <fsummary>Calculate the Adler checksum.</fsummary>
       <desc>
-        <p>Update a running Adler-32 checksum for <c><anno>Data</anno></c>.
-          If <c><anno>Data</anno></c> is the empty binary or the empty iolist, this function returns
-          the required initial value for the checksum.</p>
+        <p>Updates a running Adler-32 checksum for <c><anno>Data</anno></c>.
+          If <c><anno>Data</anno></c> is the empty binary or the empty iolist,
+          this function returns the required initial value for the checksum.</p>
+        <p>Example:</p>
         <pre>
 Crc = lists:foldl(fun(Data,Crc0) ->
                       zlib:adler32(Z, Crc0, Data),
                   end, zlib:adler32(Z,&lt;&lt; &gt;&gt;), Datas)</pre>
       </desc>
     </func>
+
     <func>
       <name name="adler32_combine" arity="4"/>
-      <fsummary>Combine two Adler-32 checksums</fsummary>
+      <fsummary>Combine two Adler-32 checksums.</fsummary>
       <desc>
-	<p>Combine two Adler-32 checksums into one.  For two binaries or iolists,
-	  <c>Data1</c> and <c>Data2</c> with sizes of <c>Size1</c> and
-	  <c><anno>Size2</anno></c>, with Adler-32 checksums <c><anno>Adler1</anno></c> and
-	  <c><anno>Adler2</anno></c>.  <c>adler32_combine/4</c> returns the <c><anno>Adler</anno></c>
-	  checksum of <c>[Data1,Data2]</c>, requiring
-	  only <c><anno>Adler1</anno></c>, <c><anno>Adler2</anno></c>, and <c><anno>Size2</anno></c>.
-	</p>
+        <p>Combines two Adler-32 checksums into one. For two binaries or
+          iolists, <c>Data1</c> and <c>Data2</c> with sizes of <c>Size1</c>
+          and <c><anno>Size2</anno></c>, with Adler-32 checksums
+          <c><anno>Adler1</anno></c> and <c><anno>Adler2</anno></c>.</p>
+        <p>This function returns the <c><anno>Adler</anno></c> checksum of
+          <c>[Data1,Data2]</c>, requiring only <c><anno>Adler1</anno></c>,
+          <c><anno>Adler2</anno></c>, and <c><anno>Size2</anno></c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="close" arity="1"/>
-      <fsummary>Close a stream</fsummary>
+      <fsummary>Close a stream.</fsummary>
       <desc>
         <p>Closes the stream referenced by <c><anno>Z</anno></c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="compress" arity="1"/>
-      <fsummary>Compress data with standard zlib functionality</fsummary>
+      <fsummary>Compress data with standard zlib functionality.</fsummary>
       <desc>
-        <p>Compress data (with zlib headers and checksum).</p>
+        <p>Compresses data with zlib headers and checksum.</p>
       </desc>
     </func>
+
     <func>
       <name name="crc32" arity="1"/>
-      <fsummary>Get current CRC</fsummary>
+      <fsummary>Get current CRC.</fsummary>
       <desc>
-        <p>Get the current calculated CRC checksum.</p>
+        <p>Gets the current calculated CRC checksum.</p>
       </desc>
     </func>
+
     <func>
       <name name="crc32" arity="2"/>
-      <fsummary>Calculate CRC</fsummary>
+      <fsummary>Calculate CRC.</fsummary>
       <desc>
-        <p>Calculate the CRC checksum for <c><anno>Data</anno></c>.</p>
+        <p>Calculates the CRC checksum for <c><anno>Data</anno></c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="crc32" arity="3"/>
-      <fsummary>Calculate CRC</fsummary>
+      <fsummary>Calculate CRC.</fsummary>
       <desc>
-        <p>Update a running CRC checksum for <c><anno>Data</anno></c>.
-          If <c><anno>Data</anno></c> is the empty binary or the empty iolist, this function returns
-          the required initial value for the crc.</p>
+        <p>Updates a running CRC checksum for <c><anno>Data</anno></c>.
+          If <c><anno>Data</anno></c> is the empty binary or the empty iolist,
+          this function returns the required initial value for the CRC.</p>
+        <p>Example:</p>
         <pre>
 Crc = lists:foldl(fun(Data,Crc0) ->
                       zlib:crc32(Z, Crc0, Data),
                   end, zlib:crc32(Z,&lt;&lt; &gt;&gt;), Datas)</pre>
       </desc>
     </func>
+
     <func>
       <name name="crc32_combine" arity="4"/>
-      <fsummary>Combine two CRC's</fsummary>
+      <fsummary>Combine two CRCs.</fsummary>
       <desc>
-	<p>Combine two CRC checksums into one.  For two binaries or iolists,
-	  <c>Data1</c> and <c>Data2</c> with sizes of <c>Size1</c> and
-	  <c><anno>Size2</anno></c>, with CRC checksums <c><anno>CRC1</anno></c> and
-	  <c><anno>CRC2</anno></c>.  <c>crc32_combine/4</c> returns the <c><anno>CRC</anno></c>
-	  checksum of <c>[Data1,Data2]</c>, requiring
-	  only <c><anno>CRC1</anno></c>, <c><anno>CRC2</anno></c>, and <c><anno>Size2</anno></c>.
-	</p>
+        <p>Combines two CRC checksums into one. For two binaries or iolists,
+          <c>Data1</c> and <c>Data2</c> with sizes of <c>Size1</c> and
+          <c><anno>Size2</anno></c>, with CRC checksums <c><anno>CRC1</anno></c>
+          and <c><anno>CRC2</anno></c>.</p>
+        <p>This function returns the <c><anno>CRC</anno></c> checksum of
+          <c>[Data1,Data2]</c>, requiring only <c><anno>CRC1</anno></c>,
+          <c><anno>CRC2</anno></c>, and <c><anno>Size2</anno></c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="deflate" arity="2"/>
-      <fsummary>Compress data</fsummary>
+      <fsummary>Compress data.</fsummary>
       <desc>
         <p>Same as <c>deflate(<anno>Z</anno>, <anno>Data</anno>, none)</c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="deflate" arity="3"/>
-      <fsummary>Compress data</fsummary>
+      <fsummary>Compress data.</fsummary>
       <desc>
-        <p><c>deflate/3</c> compresses as much data as possible, and
-          stops when the input buffer becomes empty. It may introduce
+        <p>Compresses as much data as possible, and
+          stops when the input buffer becomes empty. It can introduce
           some output latency (reading input without producing any
           output) except when forced to flush.</p>
-        <p>If the parameter <c><anno>Flush</anno></c> is set to <c>sync</c>, all
+        <p>If <c><anno>Flush</anno></c> is set to <c>sync</c>, all
           pending output is flushed to the output buffer and the
           output is aligned on a byte boundary, so that the
           decompressor can get all input data available so far. 
-          Flushing may degrade compression for some compression algorithms and so
-          it should be used only when necessary.</p>
-        <p>If <c><anno>Flush</anno></c> is set to <c>full</c>, all output is flushed as with
-          <c>sync</c>, and the compression state is reset so that decompression can
-          restart from this point if previous compressed data has been damaged or if
-          random access is desired. Using <c>full</c> too often can seriously degrade
-          the compression.</p>
-        <p>If the parameter <c><anno>Flush</anno></c> is set to <c>finish</c>,
-          pending input is processed, pending output is flushed and
-          <c>deflate/3</c> returns. Afterwards the only possible
-          operations on the stream are <c>deflateReset/1</c> or <c>deflateEnd/1</c>.</p>
-        <p><c><anno>Flush</anno></c> can be set to <c>finish</c> immediately after
-          <c>deflateInit</c> if all compression is to be done in one step.</p>
+          Flushing can degrade compression for some compression algorithms;
+          thus, use it only when necessary.</p>
+        <p>If <c><anno>Flush</anno></c> is set to <c>full</c>, all output is
+          flushed as with <c>sync</c>, and the compression state is reset so
+          that decompression can restart from this point if previous compressed
+          data has been damaged or if random access is desired. Using
+          <c>full</c> too often can seriously degrade the compression.</p>
+        <p>If <c><anno>Flush</anno></c> is set to <c>finish</c>,
+          pending input is processed, pending output is flushed, and
+          <c>deflate/3</c> returns. Afterwards the only possible operations
+          on the stream are
+          <seealso marker="#deflateReset/1"><c>deflateReset/1</c></seealso> or
+          <seealso marker="#deflateEnd/1"><c>deflateEnd/1</c></seealso>.</p>
+        <p><c><anno>Flush</anno></c> can be set to <c>finish</c> immediately
+          after <seealso marker="#deflateInit/1"><c>deflateInit</c></seealso>
+          if all compression is to be done in one step.</p>
+        <p>Example:</p>
         <pre>
- 
 zlib:deflateInit(Z),
 B1 = zlib:deflate(Z,Data),
 B2 = zlib:deflate(Z,&lt;&lt; &gt;&gt;,finish),
@@ -237,184 +253,231 @@ list_to_binary([B1,B2])</pre>
 
     <func>
       <name name="deflateEnd" arity="1"/>
-      <fsummary>End deflate session</fsummary>
+      <fsummary>End deflate session.</fsummary>
       <desc>
-        <p>End the deflate session and cleans all data used.
-          Note that this function will throw an <c>data_error</c>
-          exception if the last call to
-          <c>deflate/3</c> was not called with <c>Flush</c> set to
-          <c>finish</c>.</p>
+        <p>Ends the deflate session and cleans all data used. Notice that this
+          function throws a <c>data_error</c> exception if the last call to
+          <seealso marker="#deflate/3"><c>deflate/3</c></seealso>
+          was not called with <c>Flush</c> set to <c>finish</c>.</p>
       </desc>
     </func>
 
     <func>
       <name name="deflateInit" arity="1"/>
-      <fsummary>Initialize a session for compression</fsummary>
+      <fsummary>Initialize a session for compression.</fsummary>
       <desc>
         <p>Same as <c>zlib:deflateInit(<anno>Z</anno>, default)</c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="deflateInit" arity="2"/>
-      <fsummary>Initialize a session for compression</fsummary>
+      <fsummary>Initialize a session for compression.</fsummary>
       <desc>
-        <p>Initialize a zlib stream for compression.</p>
-        <p><c><anno>Level</anno></c> decides the compression level to be used, 0
-          (<c>none</c>), gives no compression at all, 1
-          (<c>best_speed</c>) gives best speed and 9
-          (<c>best_compression</c>) gives best compression.</p>
+        <p>Initializes a zlib stream for compression.</p>
+        <p><c><anno>Level</anno></c> decides the compression level to be
+          used:</p>
+        <list type="bulleted">
+          <item>0 (<c>none</c>), gives no compression</item>
+          <item>1 (<c>best_speed</c>) gives best speed</item>
+          <item>9 (<c>best_compression</c>) gives best compression</item>
+        </list>
       </desc>
     </func>
+
     <func>
       <name name="deflateInit" arity="6"/>
-      <fsummary>Initialize a session for compression</fsummary>
+      <fsummary>Initialize a session for compression.</fsummary>
       <desc>
         <p>Initiates a zlib stream for compression.</p>
-        <p>The <c><anno>Level</anno></c> parameter decides the compression level to be
-          used, 0 (<c>none</c>), gives no compression at all, 1
-          (<c>best_speed</c>) gives best speed and 9
-          (<c>best_compression</c>) gives best compression.</p>
-        <p>The <c><anno>Method</anno></c> parameter decides which compression method to use,
-          currently the only supported method is <c>deflated</c>.</p>
-        <p>The <c><anno>WindowBits</anno></c> parameter is the base two logarithm
-          of the window size (the size of the history buffer).  It
-          should be in the range 8 through 15. Larger values
-          of this parameter result in better compression at the
-          expense of memory usage. The default value is 15 if
-          <c>deflateInit/2</c>. A negative <c><anno>WindowBits</anno></c>
-          value suppresses the zlib header (and checksum) from the
-          stream. Note that the zlib source mentions this only as a
-          undocumented feature.</p>
-        <p>The <c><anno>MemLevel</anno></c> parameter specifies how much memory
-          should be allocated for the internal compression
-          state. <c><anno>MemLevel</anno></c>=1 uses minimum memory but is slow and
-          reduces compression ratio; <c><anno>MemLevel</anno></c>=9 uses maximum
-          memory for optimal speed. The default value is 8.</p>
-        <p>The <c><anno>Strategy</anno></c> parameter is used to tune
-        the compression algorithm. Use the value <c>default</c> for
-        normal data, <c>filtered</c> for data produced by a filter (or
-        predictor), <c>huffman_only</c> to force Huffman encoding
-        only (no string match), or <c>rle</c> to limit match
-        distances to one (run-length encoding).  Filtered data
-        consists mostly of small values with a somewhat random
-        distribution. In this case, the compression algorithm is tuned
-        to compress them better. The effect of <c>filtered</c>is to
-        force more Huffman coding and less string matching; it is
-        somewhat intermediate between <c>default</c> and
-        <c>huffman_only</c>. <c>rle</c> is designed to be almost as
-        fast as <c>huffman_only</c>, but give better compression for PNG
-        image data. The <c><anno>Strategy</anno></c> parameter only
-        affects the compression ratio but not the correctness of the
-        compressed output even if it is not set appropriately.</p>
+        <taglist>
+          <tag><c><anno>Level</anno></c></tag>
+          <item>
+            <p>Compression level to use:</p>
+            <list type="bulleted">
+              <item>0 (<c>none</c>), gives no compression</item>
+              <item>1 (<c>best_speed</c>) gives best speed</item>
+              <item>9 (<c>best_compression</c>) gives best compression</item>
+            </list>
+          </item>
+          <tag><c><anno>Method</anno></c></tag>
+          <item>
+            <p>Compression method to use, currently the only supported method
+              is <c>deflated</c>.</p>
+          </item>
+          <tag><c><anno>WindowBits</anno></c></tag>
+          <item>
+            <p>The base two logarithm of the window size (the size of the
+              history buffer). It is to be in the range 8 through 15. Larger
+              values result in better compression at the expense of memory
+              usage. Defaults to 15 if <seealso marker="#deflateInit/2">
+              <c>deflateInit/2</c></seealso> is used. A negative
+              <c><anno>WindowBits</anno></c> value suppresses the zlib header
+              (and checksum) from the stream. Notice that the zlib source
+              mentions this only as a undocumented feature.</p>
+          </item>
+          <tag><c><anno>MemLevel</anno></c></tag>
+          <item>
+            <p>Specifies how much memory is to be allocated for the internal
+              compression state: <c><anno>MemLevel</anno></c>=1 uses minimum
+              memory but is slow and reduces compression ratio;
+              <c><anno>MemLevel</anno></c>=9 uses maximum memory for optimal
+              speed. Defaults to 8.</p>
+          </item>
+          <tag><c><anno>Strategy</anno></c></tag>
+          <item>
+            <p>Tunes the compression algorithm. Use the following values:</p>
+            <list type="bulleted">
+              <item><c>default</c> for normal data</item>
+              <item><c>filtered</c> for data produced by a filter (or
+                predictor)</item>
+              <item><c>huffman_only</c> to force Huffman encoding only
+                (no string match)</item>
+              <item><c>rle</c> to limit match distances to one (run-length
+                encoding)</item>
+            </list>
+            <p>Filtered data consists mostly of small values with a somewhat
+              random distribution. In this case, the compression algorithm is
+              tuned to compress them better. The effect of <c>filtered</c> is to
+              force more Huffman coding and less string matching; it is somewhat
+              intermediate between <c>default</c> and <c>huffman_only</c>.
+              <c>rle</c> is designed to be almost as fast as
+              <c>huffman_only</c>, but gives better compression for PNG image
+              data.</p>
+            <p><c><anno>Strategy</anno></c> affects only the compression ratio,
+              but not the correctness of the compressed output even if it is not
+              set appropriately.</p>
+          </item>
+        </taglist>
       </desc>
     </func>
+
     <func>
       <name name="deflateParams" arity="3"/>
-      <fsummary>Dynamicly update deflate parameters</fsummary>
+      <fsummary>Dynamicly update deflate parameters.</fsummary>
       <desc>
-        <p>Dynamically update the compression level and compression
-          strategy.  The interpretation of <c><anno>Level</anno></c> and
-          <c><anno>Strategy</anno></c> is as in <c>deflateInit/6</c>.  This can be
+        <p>Dynamically updates the compression level and compression
+          strategy. The interpretation of <c><anno>Level</anno></c> and
+          <c><anno>Strategy</anno></c> is as in
+          <seealso marker="#deflateInit/6"><c>deflateInit/6</c></seealso>.
+          This can be
           used to switch between compression and straight copy of the
           input data, or to switch to a different kind of input data
           requiring a different strategy. If the compression level is
           changed, the input available so far is compressed with the
-          old level (and may be flushed); the new level will take
-          effect only at the next call of <c>deflate/3</c>.</p>
-        <p>Before the call of <c>deflateParams</c>, the stream state must be set as for
-          a call of <c>deflate/3</c>, since the currently available input may have to
-          be compressed and flushed.</p>
+          old level (and can be flushed); the new level takes
+          effect only at the next call of
+          <seealso marker="#deflate/3"><c>deflate/3</c></seealso>.</p>
+        <p>Before the call of <c>deflateParams</c>, the stream state must be
+          set as for a call of <c>deflate/3</c>, as the currently available
+          input may have to be compressed and flushed.</p>
       </desc>
     </func>
+
     <func>
       <name name="deflateReset" arity="1"/>
-      <fsummary>Reset the deflate session</fsummary>
-      <desc>
-        <p>This function is equivalent to <c>deflateEnd/1</c>
-          followed by <c>deflateInit/[1|2|6]</c>, but does not free
-          and reallocate all the internal compression state.  The
-          stream will keep the same compression level and any other
+      <fsummary>Reset the deflate session.</fsummary>
+      <desc>
+        <p>Equivalent to
+          <seealso marker="#deflateEnd/1"><c>deflateEnd/1</c></seealso>
+          followed by
+          <seealso marker="#deflateInit/1"><c>deflateInit/1,2,6</c></seealso>,
+          but does not free and reallocate all the internal compression state.
+          The stream keeps the same compression level and any other
           attributes.</p>
       </desc>
     </func>
+
     <func>
       <name name="deflateSetDictionary" arity="2"/>
-      <fsummary>Initialize the compression dictionary</fsummary>
+      <fsummary>Initialize the compression dictionary.</fsummary>
       <desc>
-        <p>Initializes the compression dictionary from the given byte
-          sequence without producing any compressed output. This
-          function must be called immediately after
-          <c>deflateInit/[1|2|6]</c> or <c>deflateReset/1</c>, before
-          any call of <c>deflate/3</c>. The compressor and
-          decompressor must use exactly the same dictionary (see
-          <c>inflateSetDictionary/2</c>). The adler checksum of the
-          dictionary is returned.</p>
+        <p>Initializes the compression dictionary from the specified byte
+          sequence without producing any compressed output.</p>
+        <p>This function must be called immediately after
+          <seealso marker="#deflateInit/1"><c>deflateInit/1,2,6</c></seealso> or
+          <seealso marker="#deflateReset/1"><c>deflateReset/1</c></seealso>,
+          before any call of
+          <seealso marker="#deflate/3"><c>deflate/3</c></seealso>.
+          The compressor and decompressor must use the same dictionary (see
+          <seealso marker="#inflateSetDictionary/2">
+          <c>inflateSetDictionary/2</c></seealso>).</p>
+        <p>The Adler checksum of the dictionary is returned.</p>
       </desc>
     </func>
+
     <func>
       <name name="getBufSize" arity="1"/>
-      <fsummary>Get buffer size</fsummary>
+      <fsummary>Get buffer size.</fsummary>
       <desc>
-        <p>Get the size of intermediate buffer.</p>
+        <p>Gets the size of the intermediate buffer.</p>
       </desc>
     </func>
+
     <func>
       <name name="gunzip" arity="1"/>
-      <fsummary>Uncompress data with gz header</fsummary>
+      <fsummary>Uncompress data with gz header.</fsummary>
       <desc>
-        <p>Uncompress data (with gz headers and checksum).</p>
+        <p>Uncompresses data with gz headers and checksum.</p>
       </desc>
     </func>
+
     <func>
       <name name="gzip" arity="1"/>
-      <fsummary>Compress data with gz header</fsummary>
+      <fsummary>Compress data with gz header.</fsummary>
       <desc>
-        <p>Compress data (with gz headers and checksum).</p>
+        <p>Compresses data with gz headers and checksum.</p>
       </desc>
     </func>
+
     <func>
       <name name="inflate" arity="2"/>
-      <fsummary>Decompress data</fsummary>
+      <fsummary>Decompress data.</fsummary>
       <desc>
-        <p><c>inflate/2</c> decompresses as much data as possible.
-          It may introduce some output latency (reading
+        <p>Decompresses as much data as possible.
+          It can introduce some output latency (reading
           input without producing any output).</p>
         <p>If a preset dictionary is needed at this point (see
-          <c>inflateSetDictionary</c> below), <c>inflate/2</c> throws a
-          <c>{need_dictionary,Adler}</c> exception where <c>Adler</c> is 
-          the adler32 checksum of the dictionary chosen by the
-          compressor.</p>
+          <seealso marker="#inflateSetDictionary/2">
+          <c>inflateSetDictionary/2</c></seealso>), <c>inflate/2</c> throws a
+          <c>{need_dictionary,Adler}</c> exception, where <c>Adler</c> is
+          the Adler-32 checksum of the dictionary chosen by the compressor.</p>
       </desc>
     </func>
+
     <func>
       <name name="inflateChunk" arity="1"/>
-      <fsummary>Read next uncompressed chunk</fsummary>
+      <fsummary>Read next uncompressed chunk.</fsummary>
       <desc>
-        <p>Read next chunk of uncompressed data, initialized by
-          <c>inflateChunk/2</c>.</p>
-        <p>This function should be repeatedly called, while it returns
+        <p>Reads the next chunk of uncompressed data, initialized by
+          <seealso marker="#inflateChunk/2"><c>inflateChunk/2</c></seealso>.</p>
+        <p>This function is to be repeatedly called, while it returns
           <c>{more, Decompressed}</c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="inflateChunk" arity="2"/>
-      <fsummary>Decompress data with limited output size</fsummary>
+      <fsummary>Decompress data with limited output size.</fsummary>
       <desc>
-        <p>Like <c>inflate/2</c>, but decompress no more data than
-          will fit in the buffer configured via <c>setBufSize/2</c>.
+        <p>Like <seealso marker="#inflate/2"><c>inflate/2</c></seealso>,
+          but decompresses no more data than will fit in the buffer configured
+          through <seealso marker="#setBufSize/2"><c>setBufSize/2</c></seealso>.
           Is is useful when decompressing a stream with a high compression
-          ratio such that a small amount of compressed input may expand up to
-          1000 times.
-          It returns <c>{more, Decompressed}</c>, when there is more output
-          available, and <c>inflateChunk/1</c> should be used to read it.
-          It may introduce some output latency (reading
+          ratio, such that a small amount of compressed input can expand up to
+          1000 times.</p>
+        <p>This function returns <c>{more, Decompressed}</c>, when there is
+          more output available, and
+          <seealso marker="#inflateChunk/1"><c>inflateChunk/1</c></seealso>
+          is to be used to read it.</p>
+        <p>This function can introduce some output latency (reading
           input without producing any output).</p>
         <p>If a preset dictionary is needed at this point (see
-          <c>inflateSetDictionary</c> below), <c>inflateChunk/2</c> throws a
-          <c>{need_dictionary,Adler}</c> exception where <c>Adler</c> is
-          the adler32 checksum of the dictionary chosen by the
-          compressor.</p>
-
+          <seealso marker="#inflateSetDictionary/2">
+          <c>inflateSetDictionary/2</c></seealso>), this function throws a
+          <c>{need_dictionary,Adler}</c> exception, where <c>Adler</c> is
+          the Adler-32 checksum of the dictionary chosen by the compressor.</p>
+        <p>Example:</p>
         <pre>
 walk(Compressed, Handler) ->
     Z = zlib:open(),
@@ -429,65 +492,76 @@ loop(Z, Handler, {more, Uncompressed}) ->
     Handler(Uncompressed),
     loop(Z, Handler, zlib:inflateChunk(Z));
 loop(Z, Handler, Uncompressed) ->
-    Handler(Uncompressed).
-        </pre>
+    Handler(Uncompressed).</pre>
       </desc>
     </func>
+
     <func>
       <name name="inflateEnd" arity="1"/>
-      <fsummary>End inflate session</fsummary>
+      <fsummary>End inflate session.</fsummary>
       <desc>
-        <p>End the inflate session and cleans all data used. Note
-          that this function will throw a <c>data_error</c> exception
+        <p>Ends the inflate session and cleans all data used. Notice
+          that this function throws a <c>data_error</c> exception
           if no end of stream was found (meaning that not all data
           has been uncompressed).</p>
       </desc>
     </func>
+
     <func>
       <name name="inflateInit" arity="1"/>
-      <fsummary>Initialize a session for decompression</fsummary>
+      <fsummary>Initialize a session for decompression.</fsummary>
       <desc>
-        <p>Initialize a zlib stream for decompression.</p>
+        <p>Initializes a zlib stream for decompression.</p>
       </desc>
     </func>
+
     <func>
       <name name="inflateInit" arity="2"/>
-      <fsummary>Initialize a session for decompression</fsummary>
+      <fsummary>Initialize a session for decompression.</fsummary>
       <desc>
-        <p>Initialize decompression session on zlib stream.</p>
-        <p>The <c><anno>WindowBits</anno></c> parameter is the base two logarithm
+        <p>Initializes a decompression session on zlib stream.</p>
+        <p><c><anno>WindowBits</anno></c> is the base two logarithm
           of the maximum window size (the size of the history buffer).
-          It should be in the range 8 through 15.
-          The default value is 15 if <c>inflateInit/1</c> is used.
-          If a compressed stream with a larger window size is
-          given as input, inflate() will throw the <c>data_error</c>
-          exception. A negative <c><anno>WindowBits</anno></c> value makes zlib ignore the
-          zlib header (and checksum) from the stream.  Note that the zlib
-          source mentions this only as a undocumented feature.</p>
+          It is to be in the range 8 through 15. Default to 15 if
+          <seealso marker="#inflateInit/1"><c>inflateInit/1</c></seealso>
+          is used.</p>
+        <p>If a compressed stream with a larger window size is specified as
+          input, <seealso marker="#inflate/2"><c>inflate/2</c></seealso>
+          throws the <c>data_error</c> exception.</p>
+        <p>A negative <c><anno>WindowBits</anno></c> value makes zlib
+          ignore the zlib header (and checksum) from the stream. Notice that
+          the zlib source mentions this only as a undocumented feature.</p>
       </desc>
     </func>
+
     <func>
       <name name="inflateReset" arity="1"/>
-      <fsummary>>Reset the inflate session</fsummary>
+      <fsummary>>Reset the inflate session.</fsummary>
       <desc>
-        <p>This function is equivalent to <c>inflateEnd/1</c> followed
-          by <c>inflateInit/1</c>, but does not free and reallocate all
-          the internal decompression state.  The stream will keep
-          attributes that may have been set by <c>inflateInit/[1|2]</c>.</p>
+        <p>Equivalent to
+          <seealso marker="#inflateEnd/1"><c>inflateEnd/1</c></seealso>
+          followed by
+          <seealso marker="#inflateInit/1"><c>inflateInit/1</c></seealso>,
+          but does not free and reallocate all the internal decompression state.
+          The stream will keep attributes that could have been set by
+          <c>inflateInit/1,2</c>.</p>
       </desc>
     </func>
+
     <func>
       <name name="inflateSetDictionary" arity="2"/>
-      <fsummary>Initialize the decompression dictionary</fsummary>
+      <fsummary>Initialize the decompression dictionary.</fsummary>
       <desc>
-        <p>Initializes the decompression dictionary from the given
+        <p>Initializes the decompression dictionary from the specified
           uncompressed byte sequence. This function must be called
-          immediately after a call of <c>inflate/2</c> if this call
-          threw a <c>{need_dictionary,Adler}</c> exception.
-          The dictionary chosen by the
-          compressor can be determined from the Adler value thrown
-          by the call to <c>inflate/2</c>. The compressor and decompressor
-          must use exactly the same dictionary (see <c>deflateSetDictionary/2</c>).</p>
+          immediately after a call of
+          <seealso marker="#inflate/2"><c>inflate/2</c></seealso>
+          if this call threw a <c>{need_dictionary,Adler}</c> exception.
+          The dictionary chosen by the compressor can be determined from the
+          Adler value thrown by the call to <c>inflate/2</c>.
+          The compressor and decompressor must use the same dictionary (see
+          <seealso marker="#deflateSetDictionary/2">
+          <c>deflateSetDictionary/2</c></seealso>).</p>
         <p>Example:</p>
         <pre>
 unpack(Z, Compressed, Dict) ->
@@ -500,39 +574,44 @@ unpack(Z, Compressed, Dict) ->
      end.</pre>
       </desc>
     </func>
+
     <func>
       <name name="open" arity="0"/>
-      <fsummary>Open a stream and return a stream reference</fsummary>
+      <fsummary>Open a stream and return a stream reference.</fsummary>
       <desc>
-        <p>Open a zlib stream.</p>
+        <p>Opens a zlib stream.</p>
       </desc>
     </func>
+
     <func>
       <name name="setBufSize" arity="2"/>
-      <fsummary>Set buffer size</fsummary>
+      <fsummary>Set buffer size.</fsummary>
       <desc>
         <p>Sets the intermediate buffer size.</p>
       </desc>
     </func>
+
     <func>
       <name name="uncompress" arity="1"/>
-      <fsummary>Uncompress data with standard zlib functionality</fsummary>
+      <fsummary>Uncompress data with standard zlib functionality.</fsummary>
       <desc>
-        <p>Uncompress data (with zlib headers and checksum).</p>
+        <p>Uncompresses data with zlib headers and checksum.</p>
       </desc>
     </func>
+
     <func>
       <name name="unzip" arity="1"/>
-      <fsummary>Uncompress data without the zlib headers</fsummary>
+      <fsummary>Uncompress data without the zlib headers.</fsummary>
       <desc>
-        <p>Uncompress data (without zlib headers and checksum).</p>
+        <p>Uncompresses data without zlib headers and checksum.</p>
       </desc>
     </func>
+
     <func>
       <name name="zip" arity="1"/>
-      <fsummary>Compress data without the zlib headers</fsummary>
+      <fsummary>Compress data without the zlib headers.</fsummary>
       <desc>
-        <p>Compress data (without zlib headers and checksum).</p>
+        <p>Compresses data without zlib headers and checksum.</p>
       </desc>
     </func>
   </funcs>