runtime_tools: Fix tags of dbg reference manual

1 files changed, 82 insertions, 73 deletions

diff --git a/lib/runtime_tools/doc/src/dbg.xml b/lib/runtime_tools/doc/src/dbg.xml
index 0128e23a47..103b8b52e9 100644
--- a/lib/runtime_tools/doc/src/dbg.xml
+++ b/lib/runtime_tools/doc/src/dbg.xml
@@ -36,8 +36,8 @@
   <modulesummary>The Text Based Trace Facility</modulesummary>
   <description>
     <p>This module implements a text based interface to the
-      <c><seealso marker="erts:erlang#trace-3">trace/3</seealso></c> and the
-      <c><seealso marker="erts:erlang#trace_pattern-2">trace_pattern/2</seealso></c> BIFs.  It makes it
+      <seealso marker="erts:erlang#trace-3"><c>trace/3</c></seealso> and the
+      <seealso marker="erts:erlang#trace_pattern-2"><c>trace_pattern/2</c></seealso> BIFs.  It makes it
       possible to trace functions, processes, ports and messages.
     </p>
     <p>
@@ -185,7 +185,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           <item>The corresponding process or port is traced. The process or port may
            be a remote process or port (on another Erlang node). The node must
            be in the list of traced nodes (see <seealso marker="#n-1"><c>n/1</c></seealso>
-           and <c><seealso marker="#tracer-3">tracer/3</seealso></c>).</item>
+           and <seealso marker="#tracer-3"><c>tracer/3</c></seealso>).</item>
           <tag><c>all</c></tag>
           <item>All processes and ports in the system as well as all processes and ports
            created hereafter are to be traced.</item>
@@ -208,22 +208,23 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           <tag><c>atom()</c></tag>
           <item>The process or port with the corresponding registered name is traced. The process or
            port may be a remote process (on another Erlang node). The node must be
-           added with the <c><seealso marker="#n-1">n/1</seealso></c> or
-           <c><seealso marker="#tracer-3">tracer/3</seealso></c> function.</item>
+           added with the <seealso marker="#n-1"><c>n/1</c></seealso> or
+           <seealso marker="#tracer-3"><c>tracer/3</c></seealso> function.</item>
           <tag><c>integer()</c></tag>
           <item>The process <c><![CDATA[<0.Item.0>]]></c> is traced.</item>
           <tag><c>{X, Y, Z}</c></tag>
           <item>The process <c><![CDATA[<X.Y.Z>]]></c> is traced. </item>
-          <tag><c>string()</c></tag>
-	  <item>If the <c>Item</c> is a string <![CDATA["<X.Y.Z>"]]>
-	    as returned from <c><seealso marker="erts:erlang#pid_to_list-1">pid_to_list/1</seealso></c>, the process
-	   <c><![CDATA[<X.Y.Z>]]></c> is traced. </item>
-        </taglist>
+              <tag><c>string()</c></tag>
+              <item>If the <c>Item</c> is a string <![CDATA["<X.Y.Z>"]]>
+                      as returned from <seealso marker="erts:erlang#pid_to_list-1"><c>pid_to_list/1</c></seealso>,
+                      the process <c><![CDATA[<X.Y.Z>]]></c> is traced.
+              </item>
+          </taglist>
 
         <p>When enabling an <c>Item</c> that represents a group of processes,
         the <c>Item</c> is enabled on all nodes added with the
-        <c><seealso marker="#n-1">n/1</seealso></c> or
-        <c><seealso marker="#tracer-3">tracer/3</seealso></c> function.</p>
+        <seealso marker="#n-1"><c>n/1</c></seealso> or
+        <seealso marker="#tracer-3"><c>tracer/3</c></seealso> function.</p>
 
         <p><c>Flags</c> can be a single atom,
           or a list of flags. The available flags are:
@@ -275,7 +276,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           <item>
             <p>This is the same as <c>sol</c>, but only for
               the first call to
-              <c><seealso marker="erts:erlang#link-1">link/1</seealso></c> by the traced process.</p>
+              <seealso marker="erts:erlang#link-1"><c>link/1</c></seealso> by the traced process.</p>
           </item>
           <tag><c>all</c></tag>
           <item>
@@ -288,7 +289,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           </item>
         </taglist>
         <p>The list can also include any of the flags allowed in 
-          <c><seealso marker="erts:erlang#trace-3">erlang:trace/3</seealso></c></p>
+            <seealso marker="erts:erlang#trace-3"><c>erlang:trace/3</c></seealso></p>
         <p>The function returns either an error tuple or a tuple
           <c>{ok, List}</c>. The <c>List</c> consists of
           specifications of how many processes and ports that matched (in the
@@ -368,11 +369,11 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           please turn to the
           <em>User's guide</em> part of the online
           documentation for the runtime system (<em>erts</em>). The
-          chapter <em><seealso marker="erts:match_spec">Match Specifications in Erlang</seealso></em>
+          chapter <seealso marker="erts:match_spec"><em>Match Specifications in Erlang</em></seealso>
           explains the general match specification "language".
           The most common generic match specifications used can be
           found as <c>Built-inAlias</c>', see
-          <c><seealso marker="#ltp-0">ltp/0</seealso></c> below for details.
+          <seealso marker="#ltp-0"><c>ltp/0</c></seealso> below for details.
           </p>
         <p>The Module, Function and/or Arity parts of the tuple may
           be specified as the atom <c>'_'</c> which is a "wild-card"
@@ -380,21 +381,21 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           Module is specified as <c>'_'</c>, the Function and Arity
           parts have to be specified as '_' too. The same holds for the
           Functions relation to the Arity.</p>
-        <p>All nodes added with <c><seealso marker="#n-1">n/1</seealso></c> or
-          <c><seealso marker="#tracer-3">tracer/3</seealso></c> will
+        <p>All nodes added with <seealso marker="#n-1"><c>n/1</c></seealso> or
+            <seealso marker="#tracer-3"><c>tracer/3</c></seealso> will
           be affected by this call, and if Module is not <c>'_'</c>
           the module will be loaded on all nodes.</p>
         <p>The function returns either an error tuple or a tuple
           <c>{ok, List}</c>. The <c>List</c> consists of specifications of how
           many functions that matched, in the same way as the processes and ports
-          are presented in the return value of <c><seealso marker="#p-2">p/2</seealso></c>. </p>
+          are presented in the return value of <seealso marker="#p-2"><c>p/2</c></seealso>. </p>
         <p>There may be a tuple <c>{saved, N}</c> in the return value,
           if the MatchSpec is other
           than []. The integer <c>N</c> may then be used in
           subsequent calls to this function and will stand as an
           "alias" for the given expression. There are also a couple of
-	  built-in aliases for common expressions, see
-          <c><seealso marker="#ltp-0">ltp/0</seealso></c> below for details.</p>
+          built-in aliases for common expressions, see
+          <seealso marker="#ltp-0"><c>ltp/0</c></seealso> below for details.</p>
         <p>If an error is returned, it can be due to errors in
           compilation of the match specification. Such errors are
           presented as a list of tuples <c>{error, string()}</c> where
@@ -433,7 +434,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       <name>tpl({Module, Function, Arity}, MatchSpec) -> {ok, MatchDesc} | {error, term()}</name>
       <fsummary>Set pattern for traced local (as well as global) function calls</fsummary>
       <desc>
-        <p>This function works as <c><seealso marker="#tp-2">tp/2</seealso></c>, but enables
+          <p>This function works as <seealso marker="#tp-2"><c>tp/2</c></seealso>, but enables
           tracing for local calls (and local functions) as well as for
           global calls (and functions).</p>
       </desc>
@@ -480,10 +481,10 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
         <p>This function disables call tracing on the specified
           functions. The semantics of the parameter is the same
           as for the corresponding function specification in
-          <c><seealso marker="#tp-2">tp/2</seealso></c> or <c><seealso marker="#tpl-2">tpl/2</seealso></c>. Both local and global call trace
+          <seealso marker="#tp-2"><c>tp/2</c></seealso> or <seealso marker="#tpl-2"><c>tpl/2</c></seealso>. Both local and global call trace
           is disabled. </p>
         <p>The return value reflects how many functions that matched,
-          and is constructed as described in <c><seealso marker="#tp-2">tp/2</seealso></c>. No tuple
+            and is constructed as described in <seealso marker="#tp-2"><c>tp/2</c></seealso>. No tuple
           <c>{saved, N}</c> is however ever returned (for obvious reasons).</p>
       </desc>
     </func>
@@ -519,8 +520,9 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       <name>ctpl({Module, Function, Arity}) -> {ok, MatchDesc} | {error, term()}</name>
       <fsummary>Clear call trace pattern for the specified functions</fsummary>
       <desc>
-        <p>This function works as <c><seealso marker="#ctp-1">ctp/1</seealso></c>, but only disables
-          tracing set up with <c><seealso marker="#tpl-2">tpl/2</seealso></c> (not with <c><seealso marker="#tp-2">tp/2</seealso></c>).</p>
+          <p>This function works as <seealso marker="#ctp-1"><c>ctp/1</c></seealso>, but only disables
+              tracing set up with <seealso marker="#tpl-2"><c>tpl/2</c></seealso>
+              (not with <seealso marker="#tp-2"><c>tp/2</c></seealso>).</p>
       </desc>
     </func>
     <func>
@@ -555,8 +557,9 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       <name>ctpg({Module, Function, Arity}) -> {ok, MatchDesc} | {error, term()}</name>
       <fsummary>Clear call trace pattern for the specified functions</fsummary>
       <desc>
-        <p>This function works as <c><seealso marker="#ctp-1">ctp/1</seealso></c>, but only disables
-          tracing set up with <c><seealso marker="#tp-2">tp/2</seealso></c> (not with <c><seealso marker="#tpl-2">tpl/2</seealso></c>).</p>
+          <p>This function works as <seealso marker="#ctp-1"><c>ctp/1</c></seealso>, but only disables
+              tracing set up with <seealso marker="#tp-2"><c>tp/2</c></seealso>
+              (not with <seealso marker="#tpl-2"><c>tpl/2</c></seealso>).</p>
       </desc>
     </func>
     <func>
@@ -565,13 +568,14 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       <desc>
         <p>Use this function to recall all match specifications previously
           used in the session (i. e. previously saved during calls
-          to <c><seealso marker="#tp-2">tp/2</seealso></c>, and built-in match specifications.
+          to <seealso marker="#tp-2"><c>tp/2</c></seealso>, and built-in match specifications.
           This is very useful, as a complicated
           match_spec can be quite awkward to write. Note that the
-          match specifications are lost if <c><seealso marker="#stop-0">stop/0</seealso></c> is called.</p>
+          match specifications are lost if <seealso marker="#stop-0"><c>stop/0</c></seealso> is called.</p>
         <p>Match specifications used can be saved in a file (if a
           read-write file system is present) for use in later
-          debugging sessions, see <c><seealso marker="#wtp-1">wtp/1</seealso></c> and <c><seealso marker="#rtp-1">rtp/1</seealso></c></p>
+          debugging sessions, see <seealso marker="#wtp-1"><c>wtp/1</c></seealso>
+          and <seealso marker="#rtp-1"><c>rtp/1</c></seealso></p>
 	<p>There are three built-in trace patterns:
 	  <c>exception_trace</c>, <c>caller_trace</c> 
 	  and <c>caller_exception_trace</c> (or <c>x</c>, <c>c</c> and 
@@ -594,10 +598,10 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       <fsummary>Delete all saved match specifications.</fsummary>
       <desc>
         <p>Use this function to "forget" all match specifications
-          saved during calls to <c><seealso marker="#tp-2">tp/2</seealso></c>.
-          This is useful when one wants to restore other match
-          specifications from a file with <c><seealso marker="#rtp-1">rtp/1</seealso></c>. Use
-          <c><seealso marker="#dtp-1">dtp/1</seealso></c> to delete specific saved match specifications. </p>
+            saved during calls to <seealso marker="#tp-2"><c>tp/2</c></seealso>.
+            This is useful when one wants to restore other match
+            specifications from a file with <seealso marker="#rtp-1"><c>rtp/1</c></seealso>. Use
+            <seealso marker="#dtp-1"><c>dtp/1</c></seealso> to delete specific saved match specifications.</p>
       </desc>
     </func>
     <func>
@@ -608,7 +612,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       </type>
       <desc>
         <p>Use this function to "forget" a specific match specification
-          saved during calls to <c><seealso marker="#tp-2">tp/2</seealso></c>.</p>
+            saved during calls to <seealso marker="#tp-2"><c>tp/2</c></seealso>.</p>
       </desc>
     </func>
     <func>
@@ -620,12 +624,12 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       </type>
       <desc>
         <p>This function will save all match specifications saved
-          during the session (during calls to <c><seealso marker="#tp-2">tp/2</seealso></c>)
+            during the session (during calls to <seealso marker="#tp-2"><c>tp/2</c></seealso>)
           and built-in match specifications in a text
           file with the name designated by <c>Name</c>. The format
           of the file is textual, why it can be edited with an
           ordinary text editor, and then restored with
-          <c><seealso marker="#rtp-1">rtp/1</seealso></c>. </p>
+          <seealso marker="#rtp-1"><c>rtp/1</c></seealso>. </p>
         <p>Each match spec in the file ends with a full stop
           (<c>.</c>) and new (syntactically correct) match
           specifications can be added to the file manually.</p>
@@ -643,7 +647,8 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       </type>
       <desc>
         <p>This function reads match specifications from a file
-          (possibly) generated by the <c><seealso marker="#wtp-1">wtp/1</seealso></c> function. It checks
+           (possibly) generated by the <seealso marker="#wtp-1"><c>wtp/1</c></seealso>
+           function. It checks
           the syntax of all match specifications and verifies that
           they are correct. The error handling principle is "all or
           nothing", i. e. if some of the match specifications are
@@ -651,7 +656,8 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           saved match specifications for the running system. </p>
         <p>The match specifications in the file are <em>merged</em>
           with the current match specifications, so that no duplicates
-          are generated. Use <c><seealso marker="#ltp-0">ltp/0</seealso></c> to see what numbers were
+          are generated. Use <seealso marker="#ltp-0"><c>ltp/0</c></seealso>
+          to see what numbers were
           assigned to the specifications from the file.</p>
         <p>The function will return an error, either due to I/O
           problems (like a non existing or non readable file) or due
@@ -670,9 +676,9 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       </type>
       <desc>
         <p>The <c>dbg</c> server keeps a list of nodes where tracing
-          should be performed. Whenever a <c><seealso marker="#tp-2">tp/2</seealso></c> call or a
-          <c><seealso marker="#p-2">p/2</seealso></c> call is made, it is executed for all nodes in this
-          list including the local node (except for <c><seealso marker="#p-2">p/2</seealso></c> with a
+            should be performed. Whenever a <seealso marker="#tp-2"><c>tp/2</c></seealso> call or a
+            <seealso marker="#p-2"><c>p/2</c></seealso> call is made, it is executed for all nodes in this
+            list including the local node (except for <seealso marker="#p-2"><c>p/2</c></seealso> with a
           specific <c>pid()</c> or <c>port()</c> as first argument, in which case the
           command is executed only on the node where the designated
           process or port resides).
@@ -684,7 +690,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           distribution). If no tracer process is running on the local
           node, the error reason <c>no_local_tracer</c> is returned. The
           tracer process on the local node must be started with the
-          <c><seealso marker="#tracer-2">tracer/0/2</seealso></c> function.
+          <seealso marker="#tracer-2"><c>tracer/0/2</c></seealso> function.
           </p>
         <p>If <c>Nodename</c> is the local node, the error reason
           <c>cant_add_local_node</c> is returned.
@@ -694,7 +700,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           a tracer process. The error reason
           <c>cant_trace_remote_pid_to_local_port</c> is returned. A
           trace port can however be started on the remote node with the
-          <c><seealso marker="#tracer-3">tracer/3</seealso></c> function.
+          <seealso marker="#tracer-3"><c>tracer/3</c></seealso> function.
           </p>
         <p>The function will also return an error if the node
           <c>Nodename</c> is not reachable.</p>
@@ -708,9 +714,10 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       </type>
       <desc>
         <p>Clears a node from the list of traced nodes. Subsequent
-          calls to <c><seealso marker="#tp-2">tp/2</seealso></c> and <c><seealso marker="#p-2">p/2</seealso></c> will not consider that
-          node, but tracing already activated on the node will continue
-          to be in effect.</p>
+            calls to <seealso marker="#tp-2"><c>tp/2</c></seealso> and
+            <seealso marker="#p-2"><c>p/2</c></seealso> will not consider that
+            node, but tracing already activated on the node will continue
+            to be in effect.</p>
         <p>Returns <c>ok</c>, cannot fail.</p>
       </desc>
     </func>
@@ -727,14 +734,14 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       <desc>
         <p>This function starts a server on the local node that will
           be the recipient of all trace messages. All subsequent calls
-          to <c><seealso marker="#p-2">p/2</seealso></c> will result in messages sent to the newly
+          to <seealso marker="#p-2"><c>p/2</c></seealso> will result in messages sent to the newly
           started trace server.</p>
         <p>A trace server started in this way will simply display the
           trace messages in a formatted way in the Erlang shell
-          (i. e. use io:format). See <c><seealso marker="#tracer-2">tracer/2</seealso></c> for a description
-          of how the trace message handler can be customized.
+          (i. e. use io:format). See <seealso marker="#tracer-2"><c>tracer/2</c></seealso>
+          for a description of how the trace message handler can be customized.
         </p>
-        <p>To start a similar tracer on a remote node, use <c><seealso marker="#n-1">n/1</seealso></c>.</p>
+        <p>To start a similar tracer on a remote node, use <seealso marker="#n-1"><c>n/1</c></seealso>.</p>
       </desc>
     </func>
     <func>
@@ -758,9 +765,9 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           by a receiving process (<c>process</c>), by a tracer port
           (<c>port</c>) or by a tracer module
           (<c>module</c>). For a description about tracer ports see
-          <c><seealso marker="#trace_port-2">trace_port/2</seealso></c>
+          <seealso marker="#trace_port-2"><c>trace_port/2</c></seealso>
           and for a tracer modules see
-          <c><seealso marker="erts:erl_tracer">erl_tracer</seealso>.</c>
+          <seealso marker="erts:erl_tracer"><c>erl_tracer</c></seealso>.
           </p>
         <p>If <c>Type</c> is <c>process</c>, a message handler function can
           be specified (<c>HandlerSpec</c>). The handler function, which
@@ -776,10 +783,10 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
         <p>If <c>Type</c> is <c>port</c>, then the second parameter should
           be a <em>fun</em> which takes no arguments and returns a
           newly opened trace port when called. Such a <em>fun</em> is
-          preferably generated by calling <c><seealso marker="#trace_port-2">trace_port/2</seealso></c>.
+          preferably generated by calling <seealso marker="#trace_port-2"><c>trace_port/2</c></seealso>.
           </p>
         <p>if <c>Type</c> is <c>module</c>, then the second parameter should
-          be either a tuple describing the <c><seealso marker="erts:erl_tracer">erl_tracer</seealso></c>
+            be either a tuple describing the <seealso marker="erts:erl_tracer"><c>erl_tracer</c></seealso>
           module to be used for tracing and the state to be used for
           that tracer module or a fun returning the same tuple.</p>
         <p>If an error is returned, it can either be due to a tracer
@@ -787,7 +794,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           due to the <c>HandlerFun</c> throwing an exception.
           </p>
         <p>To start a similar tracer on a remote node, use
-          <c><seealso marker="#tracer-3">tracer/3</seealso></c>.
+            <seealso marker="#tracer-3"><c>tracer/3</c></seealso>.
         </p>
       </desc>
     </func>
@@ -798,19 +805,19 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
         <v>Nodename = atom()</v>
       </type>
       <desc>
-        <p>This function is equivalent to <c><seealso marker="#tracer-2">tracer/2</seealso></c>, but acts on
+          <p>This function is equivalent to <seealso marker="#tracer-2"><c>tracer/2</c></seealso>, but acts on
           the given node. A tracer is started on the node
           (<c>Nodename</c>) and the node is added to the list of traced nodes.
           </p>
         <note>
-          <p>This function is not equivalent to <c><seealso marker="#n-1">n/1</seealso></c>. While
-            <c><seealso marker="#n-1">n/1</seealso></c> starts a process tracer which redirects all trace
+            <p>This function is not equivalent to <seealso marker="#n-1"><c>n/1</c></seealso>. While
+                <seealso marker="#n-1"><c>n/1</c></seealso> starts a process tracer which redirects all trace
             information to a process tracer on the local node (i.e. the
-            trace control node), <c><seealso marker="#tracer-3">tracer/3</seealso></c> starts a tracer of any
+            trace control node), <seealso marker="#tracer-3"><c>tracer/3</c></seealso> starts a tracer of any
             type which is independent of the tracer on the trace control
             node.</p>
         </note>
-        <p>For details, see <c><seealso marker="#tracer-2">tracer/2</seealso></c>.</p>
+        <p>For details, see <seealso marker="#tracer-2"><c>tracer/2</c></seealso>.</p>
       </desc>
     </func>
     <func>
@@ -842,9 +849,9 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           <c>file</c> and the <c>ip</c> trace drivers. The file driver
           sends all trace messages into one or several binary files, 
           from where they later can be fetched and processed with the
-          <c><seealso marker="#trace_client-2">trace_client/2</seealso></c> function. The ip driver opens a TCP/IP
+          <seealso marker="#trace_client-2"><c>trace_client/2</c></seealso> function. The ip driver opens a TCP/IP
           port where it listens for connections. When a client
-          (preferably started by calling <c><seealso marker="#trace_client-2">trace_client/2</seealso></c> on
+          (preferably started by calling <seealso marker="#trace_client-2"><c>trace_client/2</c></seealso> on
           another Erlang node) connects, all trace messages are sent
           over the IP network for further processing by the remote
           client. </p>
@@ -883,7 +890,8 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
           as fast as they are produced by the runtime system, a special
           message is sent, which indicates how many messages that are
           dropped. That message will arrive at the handler function
-          specified in <c><seealso marker="#trace_client-3">trace_client/3</seealso></c> as the tuple <c>{drop, N}</c> where <c>N</c> is the number of consecutive messages
+          specified in <seealso marker="#trace_client-3"><c>trace_client/3</c></seealso>
+          as the tuple <c>{drop, N}</c> where <c>N</c> is the number of consecutive messages
           dropped. In case of heavy tracing, drop's are likely to occur,
           and they surely occur if no client is reading the trace
           messages.</p>
@@ -960,8 +968,8 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
       <desc>
         <p>This function starts a trace client that reads the output
           created by a trace port driver and handles it in mostly the
-          same way as a tracer process created by the <c><seealso marker="#tracer-0">tracer/0</seealso></c>
-          function.</p>
+          same way as a tracer process created by the
+          <seealso marker="#tracer-0"><c>tracer/0</c></seealso> function.</p>
         <p>If <c>Type</c> is <c>file</c>, the client reads all trace
           messages stored in the file named <c>Filename</c> or 
           specified by <c>WrapFilesSpec</c> (must be the same as used
@@ -972,7 +980,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
         <p>If <c>Type</c> is <c>follow_file</c>, the client behaves as
           in the <c>file</c> case, but keeps trying to read (and
           process) more data
-          from the file until stopped by <c><seealso marker="#stop_trace_client-1">stop_trace_client/1</seealso></c>.
+          from the file until stopped by <seealso marker="#stop_trace_client-1"><c>stop_trace_client/1</c></seealso>.
           <c>WrapFilesSpec</c> is not allowed as second argument 
           for this <c>Type</c>.</p>
         <p>If <c>Type</c> is <c>ip</c>, the client connects to the
@@ -1028,10 +1036,10 @@ hello</pre>
         <v>InitialData = term()</v>
       </type>
       <desc>
-        <p>This function works exactly as <c><seealso marker="#trace_client-2">trace_client/2</seealso></c>, but
-          allows you to write your own handler function. The handler
+          <p>This function works exactly as <seealso marker="#trace_client-2"><c>trace_client/2</c></seealso>,
+          but allows you to write your own handler function. The handler
           function works mostly as the one described in
-          <c><seealso marker="#tracer-2">tracer/2</seealso></c>, but will also have to be prepared to handle
+          <seealso marker="#tracer-2"><c>tracer/2</c></seealso>, but will also have to be prepared to handle
           trace messages of the form <c>{drop, N}</c>, where <c>N</c> is
           the number of dropped messages. This pseudo trace message will
           only occur if the ip trace driver is used.</p>
@@ -1050,7 +1058,8 @@ hello</pre>
       <desc>
         <p>This function shuts down a previously started trace
           client. The <c>Pid</c> argument is the process id returned
-          from the <c><seealso marker="#trace_client-2">trace_client/2</seealso></c> or <c><seealso marker="#trace_client-3">trace_client/3</seealso></c> call.</p>
+          from the <seealso marker="#trace_client-2"><c>trace_client/2</c></seealso>
+          or <seealso marker="#trace_client-3"><c>trace_client/3</c></seealso> call.</p>
       </desc>
     </func>
     <func>
@@ -1203,7 +1212,7 @@ SeqTrace [0]: (&lt;0.30.0>) &lt;0.25.0> ! {dbg,{ok,&lt;0.31.0>}} [Serial: {4,5}]
       of causing a deadlock. This will happen if a group leader process generates a trace 
       message and the tracer process, by calling the trace handler function, sends an IO 
       request to the same group leader. The problem can only occur if the trace handler 
-      prints to tty using an <c>io</c> function such as <c><seealso marker="stdlib:io#format-2">format/2</seealso></c>.
+      prints to tty using an <c>io</c> function such as <seealso marker="stdlib:io#format-2"><c>format/2</c></seealso>.
       Note that when
       <c>dbg:p(all,call)</c> is called, IO processes are also traced.
       Here's an example:</p>