Merge branch 'hb/correct_doc_tags' into maint

* hb/correct_doc_tags:
  [erl_docgen] Correct documentation
  [dialyzer] Correct documentation
  [hipe] Correct documentation
  [test_server] Correct documentation
  [tools] Correct documentation
  [erts] Correct documentation
  [stdlib] Correct documentation
  [kernel] Correct documentation

16 files changed, 95 insertions, 84 deletions

diff --git a/lib/kernel/doc/src/app.xml b/lib/kernel/doc/src/app.xml
index 1591d589af..d6d6167923 100644
--- a/lib/kernel/doc/src/app.xml
+++ b/lib/kernel/doc/src/app.xml
@@ -191,7 +191,7 @@ RTDeps       [ApplicationVersion] []
           start phases must be a subset of the set of phases defined
           for the primary application. Refer to <em>OTP Design Principles</em> for more information.</p>
       </item>
-      <tag><marker id="runtime_dependencies"><c>runtime_dependencies</c></marker></tag>
+      <tag><marker id="runtime_dependencies"></marker><c>runtime_dependencies</c></tag>
       <item><p>A list of application versions that the application
       depends on. An example of such an application version is
       <c>"kernel-3.0"</c>. Application versions specified as runtime
diff --git a/lib/kernel/doc/src/application.xml b/lib/kernel/doc/src/application.xml
index 0fe774a73f..4d8e6ce94b 100644
--- a/lib/kernel/doc/src/application.xml
+++ b/lib/kernel/doc/src/application.xml
@@ -60,8 +60,9 @@
     </datatype>
     <datatype>
       <!-- Parameterized opaque types are NYI: -->
-      <name><marker id="type-tuple_of">tuple_of(T)</marker></name>
-      <desc><p>A tuple where the elements are of type <c>T</c>.</p></desc>
+      <name>tuple_of(T)</name>
+      <desc><p><marker id="type-tuple_of"/>
+        A tuple where the elements are of type <c>T</c>.</p></desc>
     </datatype>
   </datatypes>
   <funcs>
diff --git a/lib/kernel/doc/src/auth.xml b/lib/kernel/doc/src/auth.xml
index 9ebc6f8f1a..71b1863e96 100644
--- a/lib/kernel/doc/src/auth.xml
+++ b/lib/kernel/doc/src/auth.xml
@@ -50,7 +50,7 @@
           be established in this case. Returns <c>no</c> if <c><anno>Node</anno></c>
           does not exist or communication is not authorized (it has
           another cookie than <c>auth</c> thinks it has).</p>
-        <p>Use <seealso marker="net_adm#ping/1">net_adm:ping(<anno>Node</anno>)</seealso>
+        <p>Use <seealso marker="net_adm#ping/1">net_adm:ping(<c><anno>Node</anno></c>)</seealso>
           instead.</p>
       </desc>
     </func>
@@ -71,7 +71,7 @@
       </type_desc>
       <desc>
         <p>Use
-          <seealso marker="erts:erlang#erlang:set_cookie/2">erlang:set_cookie(node(), <anno>Cookie</anno>)</seealso>
+          <seealso marker="erts:erlang#erlang:set_cookie/2">erlang:set_cookie(node(), <c><anno>Cookie</anno></c>)</seealso>
           instead.</p>
       </desc>
     </func>
@@ -94,8 +94,8 @@
         <p>Sets the magic cookie of <c><anno>Node</anno></c> to <c><anno>Cookie</anno></c>, and
           verifies the status of the authorization.
           Equivalent to calling
-          <seealso marker="erts:erlang#erlang:set_cookie/2">erlang:set_cookie(<anno>Node</anno>, <anno>Cookie</anno>)</seealso>, followed by
-          <seealso marker="#is_auth/1">auth:is_auth(<anno>Node</anno>)</seealso>.</p>
+          <seealso marker="erts:erlang#erlang:set_cookie/2">erlang:set_cookie(<c><anno>Node</anno></c>, <c><anno>Cookie</anno>)</c></seealso>, followed by
+          <seealso marker="#is_auth/1">auth:is_auth(<c><anno>Node</anno></c>)</seealso>.</p>
       </desc>
     </func>
   </funcs>
diff --git a/lib/kernel/doc/src/code.xml b/lib/kernel/doc/src/code.xml
index 7cdedfa0ba..4e3be35079 100644
--- a/lib/kernel/doc/src/code.xml
+++ b/lib/kernel/doc/src/code.xml
@@ -180,7 +180,7 @@
      example, the call
      <c>erl_prim_loader:list_dir( "/otp/root/lib/mnesia-4.4.7.ez/mnesia-4.4.7/examples/bench)"</c>
      would list the contents of a directory inside an archive.
-     See <seealso marker="erts:erl_prim_loader">erl_prim_loader(3)</seealso></p>.
+     See <seealso marker="erts:erl_prim_loader">erl_prim_loader(3)</seealso>.</p>
 
     <p>An application archive file and a regular application directory
      may coexist. This may be useful when there is a need of having
@@ -242,7 +242,7 @@
      particular useful to set the flag to <c>relaxed</c> when you want
      to elaborate with code loading from archives without editing the
      <c>boot script</c>. The default is <c>relaxed</c>. See <seealso
-     marker="erts:init">init(3)</seealso></p> </section>
+     marker="erts:init">init(3)</seealso></p></section>
 
   <section>
 
diff --git a/lib/kernel/doc/src/disk_log.xml b/lib/kernel/doc/src/disk_log.xml
index 32488a9f01..7d4a9687ea 100644
--- a/lib/kernel/doc/src/disk_log.xml
+++ b/lib/kernel/doc/src/disk_log.xml
@@ -233,11 +233,11 @@
     <func>
       <name name="alog" arity="2"/>
       <name name="balog" arity="2"/>
+      <fsummary>Asynchronously log an item onto a disk log.</fsummary>
       <type variable="Log"/>
       <type variable="Term" name_i="1"/>
       <type variable="Bytes"/>
       <type name="notify_ret"/>
-      <fsummary>Asynchronously log an item onto a disk log.</fsummary>
       <desc>
         <p>The <c>alog/2</c> and <c>balog/2</c> functions asynchronously
           append an item to a disk log. The function <c>alog/2</c> is 
@@ -288,8 +288,8 @@
     <func>
       <name name="block" arity="1"/>
       <name name="block" arity="2"/>
-      <type name="block_error_rsn"/>
       <fsummary>Block a disk log.</fsummary>
+      <type name="block_error_rsn"/>
       <desc>
         <p>With a call to <c>block/1,2</c> a process can block a log.
           If the blocking process is not an owner of the log, a temporary
@@ -663,8 +663,8 @@
     <func>
       <name name="lclose" arity="1"/>
       <name name="lclose" arity="2"/>
-      <type name="lclose_error_rsn"/>
       <fsummary>Close a disk log on one node.</fsummary>
+      <type name="lclose_error_rsn"/>
       <desc>
         <p>The function <c>lclose/1</c> closes a local log or an
           individual distributed log on the current node.
@@ -744,6 +744,7 @@
     </func>
     <func>
       <name name="open" arity="1"/>
+      <fsummary>Open a disk log file.</fsummary>
       <type name="dlog_options"/>
       <type name="dlog_option"/>
       <type name="open_ret"/>
@@ -753,7 +754,6 @@
       <type name="open_error_rsn"/>
       <type name="dlog_optattr"/>
       <type name="dlog_size"/>
-      <fsummary>Open a disk log file.</fsummary>
       <desc>
         <p>The <c><anno>ArgL</anno></c> parameter is a list of options which have
           the following meanings:</p>
@@ -1043,8 +1043,8 @@ If
     </func>
     <func>
       <name name="sync" arity="1"/>
-      <type name="sync_error_rsn"/>
       <fsummary>Flush the contents of a disk log to the disk.</fsummary>
+      <type name="sync_error_rsn"/>
       <desc>
         <p>The <c>sync/1</c> function ensures that the contents of the 
           log are actually written to the disk. 
@@ -1086,8 +1086,8 @@ If
     </func>
     <func>
       <name name="unblock" arity="1"/>
-      <type name="unblock_error_rsn"/>
       <fsummary>Unblock a disk log.</fsummary>
+      <type name="unblock_error_rsn"/>
       <desc>
         <p>The <c>unblock/1</c> function unblocks a log. 
           A log can only be unblocked by the blocking process.
diff --git a/lib/kernel/doc/src/erl_ddll.xml b/lib/kernel/doc/src/erl_ddll.xml
index d622725ba0..8d71883cf4 100644
--- a/lib/kernel/doc/src/erl_ddll.xml
+++ b/lib/kernel/doc/src/erl_ddll.xml
@@ -388,14 +388,14 @@
           remove a monitor.</p>
         <p>The function accepts the following parameters:</p>
         <taglist>
-          <tag><em><anno>Tag</anno></em></tag>
+          <tag><em><c><anno>Tag</anno></c></em></tag>
           <item>
             <p>The monitor tag is always <c>driver</c> as this function
               can only be used to create driver monitors. In the future,
               driver monitors will be integrated with process monitors,
               why this parameter has to be given for consistence.</p>
           </item>
-          <tag><em><anno>Item</anno></em></tag>
+          <tag><em><c><anno>Item</anno></c></em></tag>
           <item>
             <p>The <c><anno>Item</anno></c> parameter specifies which driver one
               wants to monitor (the name of the driver) as well as
@@ -642,7 +642,7 @@
         </note>
         <p>The function accepts the following parameters:</p>
         <taglist>
-          <tag><em><anno>Path</anno></em></tag>
+          <tag><em><c><anno>Path</anno></c></em></tag>
           <item>
             <p>The filesystem path to the directory where the driver
               object file is situated. The filename of the object file
@@ -665,7 +665,7 @@
               to have <em>only one loader</em> of a driver one wants to
               upgrade in a running system!  </p>
           </item>
-          <tag><em><anno>Name</anno></em></tag>
+          <tag><em><c><anno>Name</anno></c></em></tag>
           <item>
             <p>The name parameter is the name of the driver to be used
               in subsequent calls to <seealso marker="erts:erlang#open_port/2">open_port</seealso>. The
@@ -678,14 +678,14 @@
               with this <c><anno>Name</anno></c> parameter, much as a beam-file's
               module name much correspond to its filename.</p>
           </item>
-          <tag><em><anno>OptionList</anno></em></tag>
+          <tag><em><c><anno>OptionList</anno></c></em></tag>
           <item>
             <p>A number of options can be specified to control the
               loading operation. The options are given as a list of
               two-tuples, the tuples having the following values and
               meanings:</p>
             <taglist>
-              <tag><em>{driver_options, <anno>DriverOptionList</anno>}</em></tag>
+              <tag><em>{driver_options, <c><anno>DriverOptionList</anno></c>}</em></tag>
               <item>
                 <p>This option is to provide options that will change
                   its general behavior and will "stick" to the driver
@@ -701,7 +701,7 @@
                   when the last <seealso marker="#users">user</seealso> calls <seealso marker="#try_unload/2">try_unload/2</seealso>, or
                   the last process having loaded the driver exits.</p>
               </item>
-              <tag><em>{monitor, <anno>MonitorOption</anno>}</em></tag>
+              <tag><em>{monitor, <c><anno>MonitorOption</anno></c>}</em></tag>
               <item>
                 <p>A <c><anno>MonitorOption</anno></c> tells <c>try_load/3</c> to
                   trigger a driver monitor under certain
@@ -732,7 +732,7 @@
                   <c>{monitor, pending_driver}</c> in production
                   code (see the monitor discussion above). </p>
               </item>
-              <tag><em>{reload,<anno>ReloadOption</anno>}</em></tag>
+              <tag><em>{reload, <c><anno>ReloadOption</anno></c>}</em></tag>
               <item>
                 <p>This option is used when one wants to
                   <em>reload</em> a driver from disk, most often in a
@@ -910,13 +910,13 @@
         </taglist>
         <p>The function accepts the following parameters:</p>
         <taglist>
-          <tag><em><anno>Name</anno></em></tag>
+          <tag><em><c><anno>Name</anno></c></em></tag>
           <item>
             <p>The name parameter is the name of the driver to be
               unloaded. The name can be specified either as an
               <c>iolist()</c> or as an <c>atom()</c>. </p>
           </item>
-          <tag><em><anno>OptionList</anno></em></tag>
+          <tag><em><c><anno>OptionList</anno></c></em></tag>
           <item>
             <p>The <c><anno>OptionList</anno></c> argument can be used to specify
               certain behavior regarding ports as well as triggering
@@ -934,7 +934,7 @@
                   unloads, one should use the driver option
                   <c>kill_ports</c> when loading the driver instead.</p>
               </item>
-              <tag><em>{monitor, <anno>MonitorOption</anno>}</em></tag>
+              <tag><em>{monitor, <c><anno>MonitorOption</anno></c>}</em></tag>
               <item>
                 <p>This option creates a driver monitor if the condition
                   given in <c><anno>MonitorOption</anno></c> is true. The valid
diff --git a/lib/kernel/doc/src/error_logger.xml b/lib/kernel/doc/src/error_logger.xml
index f83fe53084..92e14c2bef 100644
--- a/lib/kernel/doc/src/error_logger.xml
+++ b/lib/kernel/doc/src/error_logger.xml
@@ -299,12 +299,12 @@ ok</pre>
       <name name="logfile" arity="1" clause_i="1"/>
       <name name="logfile" arity="1" clause_i="2"/>
       <name name="logfile" arity="1" clause_i="3"/>
+      <fsummary>Enable or disable error printouts to a file</fsummary>
       <type variable="Filename"/>
       <type variable="OpenReason" name_i="1"/>
       <type variable="CloseReason" name_i="2"/>
       <type variable="FilenameReason" name_i="3"/>
       <type name="open_error"/>
-      <fsummary>Enable or disable error printouts to a file</fsummary>
       <desc>
         <p>Enables or disables printout of standard events to a file.</p>
         <p>This is done by adding or deleting the standard event handler
diff --git a/lib/kernel/doc/src/file.xml b/lib/kernel/doc/src/file.xml
index 4954568086..9cd4cfa712 100644
--- a/lib/kernel/doc/src/file.xml
+++ b/lib/kernel/doc/src/file.xml
@@ -87,9 +87,10 @@
       <name name="deep_list"/>
     </datatype>
     <datatype>
-      <name><marker id="type-fd">fd()</marker></name>
+      <name>fd()</name>
       <desc>
-        <p>A file descriptor representing a file opened in <seealso
+        <p><marker id="type-fd"/>
+          A file descriptor representing a file opened in <seealso
           marker="#raw">raw</seealso> mode.</p>
       </desc>
     </datatype>
@@ -491,7 +492,7 @@
       <name name="list_dir" arity="1"/>
       <fsummary>List files in a directory</fsummary>
       <desc>
-        <p>Lists all files in a directory, <b>except</b> files
+        <p>Lists all files in a directory, <em>except</em> files
 	with "raw" names. Returns
           <c>{ok, <anno>Filenames</anno>}</c> if successful.
           Otherwise, it returns <c>{error, <anno>Reason</anno>}</c>.
@@ -1307,15 +1308,15 @@
           <item>
             <p>The current system access to the file.</p>
           </item>
-          <tag><c>atime = <seealso marker="#type-date_time">date_time()</seealso> | integer() >= 0</c></tag>
+          <tag><c>atime = </c><seealso marker="#type-date_time">date_time()</seealso><c> | integer() >= 0</c></tag>
           <item>
             <p>The last time the file was read.</p>
           </item>
-          <tag><c>mtime = <seealso marker="#type-date_time">date_time()</seealso> | integer() >= 0</c></tag>
+          <tag><c>mtime = </c><seealso marker="#type-date_time">date_time()</seealso><c> | integer() >= 0</c></tag>
           <item>
             <p>The last time the file was written.</p>
           </item>
-          <tag><c>ctime = <seealso marker="#type-date_time">date_time()</seealso> | integer() >=0</c></tag>
+          <tag><c>ctime = </c><seealso marker="#type-date_time">date_time()</seealso><c> | integer() >=0</c></tag>
           <item>
             <p>The interpretation of this time field depends on
               the operating system. On Unix, it is the last time
@@ -1745,7 +1746,7 @@
 	See <seealso marker="gen_tcp#controlling_process-2">gen_tcp:controlling_process/2</seealso></p>
 	<p>If the OS used does not support sendfile, an Erlang fallback
 	using file:read and gen_tcp:send is used.</p>
-	<p>The option list can contain the following options:
+	<p>The option list can contain the following options:</p>
 	<taglist>
           <tag><c>chunk_size</c></tag>
           <item>The chunk size used by the erlang fallback to send
@@ -1760,7 +1761,6 @@
 	  the sendfile call will return <c>{error,einval}</c>.
 	  Introduced in Erlang/OTP 17.0. Default is false.</item>
 	</taglist>
-	</p>
       </desc>
     </func>
     <func>
@@ -1851,22 +1851,21 @@
 			Type <c>local</c> will interpret the time set as local, <c>universal</c> will
 			interpret it as universal time and <c>posix</c> must be seconds since
 			or before unix time epoch which is 1970-01-01 00:00 UTC.
-			Default is <c>{time, local}</c>.
+			Default is <c>{time, local}</c>.</p>
         <p>If the <c>raw</c> option is set, the file server will not be called
           and only informations about local files will be returned.</p>
-		</p>
         <p>The following fields are used from the record, if they are
           given.</p>
         <taglist>
-          <tag><c>atime = <seealso marker="#type-date_time">date_time()</seealso> | integer() >= 0</c></tag>
+          <tag><c>atime = </c><seealso marker="#type-date_time">date_time()</seealso><c> | integer() >= 0</c></tag>
           <item>
             <p>The last time the file was read.</p>
           </item>
-          <tag><c>mtime = <seealso marker="#type-date_time">date_time()</seealso> | integer() >= 0</c></tag>
+          <tag><c>mtime = </c><seealso marker="#type-date_time">date_time()</seealso><c> | integer() >= 0</c></tag>
           <item>
             <p>The last time the file was written.</p>
           </item>
-          <tag><c>ctime = <seealso marker="#type-date_time">date_time()</seealso> | integer() >= 0</c></tag>
+          <tag><c>ctime = </c><seealso marker="#type-date_time">date_time()</seealso><c> | integer() >= 0</c></tag>
           <item>
             <p>On Unix, any value give for this field will be ignored
               (the "ctime" for the file will be set to the current
diff --git a/lib/kernel/doc/src/gen_sctp.xml b/lib/kernel/doc/src/gen_sctp.xml
index b704d90613..456108a2fe 100644
--- a/lib/kernel/doc/src/gen_sctp.xml
+++ b/lib/kernel/doc/src/gen_sctp.xml
@@ -77,9 +77,10 @@
 
   <datatypes>
     <datatype>
-      <name><marker id="type-assoc_id">assoc_id()</marker></name>
+      <name>assoc_id()</name>
       <desc>
-        <p>An opaque term returned in for example #sctp_paddr_change{}
+        <p><marker id="type-assoc_id"/>
+	  An opaque term returned in for example #sctp_paddr_change{}
           that identifies an association for an SCTP socket. The term
           is opaque except for the special value <c>0</c> that has a
           meaning such as "the whole endpoint" or "all future associations".
@@ -98,9 +99,10 @@
       <desc><marker id="type-sctp_socket"></marker></desc>
     </datatype>
     <datatype>
-      <name><marker id="type-sctp_socket">sctp_socket()</marker></name>
+      <name>sctp_socket()</name>
       <desc>
-        <p>Socket identifier returned from <c>open/*</c>.</p>
+        <p><marker id="type-sctp_socket"/>
+	 Socket identifier returned from <c>open/*</c>.</p>
         <marker id="exports"></marker>
       </desc>
     </datatype>
@@ -146,7 +148,7 @@
           <c><anno>Addr</anno></c> and <c><anno>Port</anno></c>. The <c><anno>Timeout</anno></c>,
           is expressed in milliseconds. A socket can be associated with multiple peers.</p>
 
-        <p><b>WARNING:</b>Using a value of <c><anno>Timeout</anno></c> less than
+        <p><em>WARNING:</em>Using a value of <c><anno>Timeout</anno></c> less than
         the maximum time taken by the OS to establish an association (around 4.5 minutes
         if the default values from RFC 4960 are used) can result in
         inconsistent or incorrect return values. This is especially
@@ -170,7 +172,7 @@
         <p>The number of outbound and inbound streams can be set by
           giving an <c>sctp_initmsg</c> option to <c>connect</c>
           as in:</p>
-<pre>  connect(<anno>Socket</anno>, Ip, <anno>Port</anno>,
+<pre>  connect(Socket, Ip, Port>,
         [{sctp_initmsg,#sctp_initmsg{num_ostreams=OutStreams,
                                      max_instreams=MaxInStreams}}])        </pre>
         <p>All options <c><anno>Opt</anno></c> are set on the socket before the
diff --git a/lib/kernel/doc/src/gen_tcp.xml b/lib/kernel/doc/src/gen_tcp.xml
index 8d9f09cea7..6a19e76c4f 100644
--- a/lib/kernel/doc/src/gen_tcp.xml
+++ b/lib/kernel/doc/src/gen_tcp.xml
@@ -78,9 +78,10 @@ do_recv(Sock, Bs) ->
       <name name="listen_option"/>
     </datatype>
     <datatype>
-      <name><marker id="type-socket">socket()</marker></name>
+      <name>socket()</name>
       <desc>
-        <p>As returned by accept/1,2 and connect/3,4.</p>
+        <p><marker id="type-socket"/>
+	As returned by accept/1,2 and connect/3,4.</p>
         <marker id="connect"></marker>
       </desc>
     </datatype>
diff --git a/lib/kernel/doc/src/gen_udp.xml b/lib/kernel/doc/src/gen_udp.xml
index 6f34aba43c..79cd87dcef 100644
--- a/lib/kernel/doc/src/gen_udp.xml
+++ b/lib/kernel/doc/src/gen_udp.xml
@@ -43,9 +43,9 @@
       <name name="option_name"/>
     </datatype>
     <datatype>
-      <name><marker id="type-socket">socket()</marker></name>
+      <name>socket()</name>
       <desc>
-        <p>As returned by open/1,2.</p>
+        <p><marker id="type-socket"/>As returned by open/1,2.</p>
       </desc>
     </datatype>
   </datatypes>
diff --git a/lib/kernel/doc/src/inet.xml b/lib/kernel/doc/src/inet.xml
index e6d418dc58..088d78c1d6 100644
--- a/lib/kernel/doc/src/inet.xml
+++ b/lib/kernel/doc/src/inet.xml
@@ -4,7 +4,7 @@
 <erlref>
   <header>
     <copyright>
-      <year>1997</year><year>2013</year>
+      <year>1997</year><year>2015</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
@@ -117,8 +117,9 @@ fe80::204:acff:fe17:bf38
       </desc>
     </datatype>
     <datatype>
-      <name><marker id="type-socket">socket()</marker></name>
-      <desc><p>See <seealso marker="gen_tcp#type-socket">gen_tcp(3)</seealso>
+      <name>socket()</name>
+      <desc><p><marker id="type-socket"></marker>
+         See <seealso marker="gen_tcp#type-socket">gen_tcp(3)</seealso>
          and <seealso marker="gen_udp#type-socket">gen_udp(3)</seealso>.</p>
       </desc>
     </datatype>
@@ -222,7 +223,7 @@ fe80::204:acff:fe17:bf38
       </p>
       <p>
 	Do not rely too much on the order of <c><anno>Flag</anno></c> atoms or
-	<c><anno>Ifopt</anno></c> tuples. There are some rules, though:
+	<c><anno>Ifopt</anno></c> tuples. There are some rules, though:</p>
 	<list>
 	  <item>
 	    Immediately after <c>{addr,_}</c> follows <c>{netmask,_}</c>
@@ -238,7 +239,6 @@ fe80::204:acff:fe17:bf38
 	    tuple concerns that address.
 	  </item>
 	</list>
-      </p>
       <p>
 	The <c>{hwaddr,_}</c> tuple is not returned on Solaris since the
 	hardware address historically belongs to the link layer and only
@@ -379,14 +379,14 @@ fe80::204:acff:fe17:bf38
       <name name="ntoa" arity="1" />
       <fsummary>Convert IPv6 / IPV4 adress to ascii</fsummary>
       <desc>
-	<p>Parses an <a href="#type-ip_address">ip_address()</a> and returns an IPv4 or IPv6 address string.</p>
+	<p>Parses an <seealso marker="#type-ip_address">ip_address()</seealso> and returns an IPv4 or IPv6 address string.</p>
       </desc>
     </func>
     <func>
       <name name="parse_ipv4_address" arity="1" />
       <fsummary>Parse an IPv4 address</fsummary>
       <desc>
-	<p>Parses an IPv4 address string and returns an <a href="#type-ip4_address">ip4_address()</a>.
+	<p>Parses an IPv4 address string and returns an <seealso marker="#type-ip4_address">ip4_address()</seealso>.
 	 Accepts a shortened IPv4 shortened address string.</p>
       </desc>
     </func>
@@ -394,14 +394,14 @@ fe80::204:acff:fe17:bf38
       <name name="parse_ipv4strict_address" arity="1" />
       <fsummary>Parse an IPv4 address strict.</fsummary>
       <desc>
-	<p>Parses an IPv4 address string containing four fields, i.e <b>not</b> shortened, and returns an <a href="#type-ip4_adress">ip4_address()</a>.</p>
+	<p>Parses an IPv4 address string containing four fields, i.e <em>not</em> shortened, and returns an <seealso marker="#type-ip4_address">ip4_address()</seealso>.</p>
       </desc>
     </func>
     <func>
       <name name="parse_ipv6_address" arity="1" />
       <fsummary>Parse an IPv6 address</fsummary>
       <desc>
-	<p>Parses an IPv6 address string and returns an <a href="#type-ip6_address">ip6_address()</a>.
+	<p>Parses an IPv6 address string and returns an <seealso marker="#type-ip6_address">ip6_address()</seealso>.
 	 If an IPv4 address string is passed, an IPv4-mapped IPv6 address is returned.</p>
       </desc>
     </func>
@@ -409,22 +409,22 @@ fe80::204:acff:fe17:bf38
       <name name="parse_ipv6strict_address" arity="1" />
       <fsummary>Parse an IPv6 address strict.</fsummary>
       <desc>
-	<p>Parses an IPv6 address string and returns an <a href="#type-ip6_address">ip6_address()</a>.
-	Does <b>not</b> accept IPv4 adresses.</p>
+	<p>Parses an IPv6 address string and returns an <seealso marker="#type-ip6_address">ip6_address()</seealso>.
+	Does <em>not</em> accept IPv4 adresses.</p>
       </desc>
     </func>
     <func>
       <name name="parse_address" arity="1" />
       <fsummary>Parse an IPv4 or IPv6 address.</fsummary>
       <desc>
-	<p>Parses an IPv4 or IPv6 address string and returns an <a href="#type-ip4_address">ip4_address()</a> or <a href="#type-ip6_address">ip6_address()</a>. Accepts a shortened IPv4 address string.</p>
+	<p>Parses an IPv4 or IPv6 address string and returns an <seealso marker="#type-ip4_address">ip4_address()</seealso> or <seealso marker="#type-ip6_address">ip6_address()</seealso>. Accepts a shortened IPv4 address string.</p>
       </desc>
     </func>
     <func>
       <name name="parse_strict_address" arity="1" />
       <fsummary>Parse an IPv4 or IPv6 address strict.</fsummary>
       <desc>
-	<p>Parses an IPv4 or IPv6 address string and returns an <a href="#type-ip4_address">ip4_address()</a> or <a href="#type-ip6_adress">ip6_address()</a>. Does <b>not</b> accept a shortened IPv4 address string.</p>
+	<p>Parses an IPv4 or IPv6 address string and returns an <seealso marker="#type-ip4_address">ip4_address()</seealso> or <seealso marker="#type-ip6_address">ip6_address()</seealso>. Does <em>not</em> accept a shortened IPv4 address string.</p>
       </desc>
     </func>
     <func>
@@ -862,10 +862,10 @@ fe80::204:acff:fe17:bf38
 	    <c>CAP_SYS_ADMIN</c> according to the documentation for setns(2).
 	    However, during testing also <c>CAP_SYS_PTRACE</c>
 	    and <c>CAP_DAC_READ_SEARCH</c> has proven to be necessary.
-	    Example:<code>
+	    Example:</p><code>
 setcap cap_sys_admin,cap_sys_ptrace,cap_dac_read_search+epi beam.smp
 </code>
-            Note also that the filesystem containing the virtual machine
+            <p>Note also that the filesystem containing the virtual machine
 	    executable (<c>beam.smp</c> in the example above) has to be local,
 	    mounted without the <c>nosetuid</c> flag,
 	    support extended attributes and that
diff --git a/lib/kernel/doc/src/inet_res.xml b/lib/kernel/doc/src/inet_res.xml
index 6a2c9b1955..851a36aba9 100644
--- a/lib/kernel/doc/src/inet_res.xml
+++ b/lib/kernel/doc/src/inet_res.xml
@@ -4,7 +4,7 @@
 <erlref>
   <header>
     <copyright>
-      <year>2009</year><year>2013</year>
+      <year>2009</year><year>2015</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
@@ -77,8 +77,11 @@
       query is tried for the <c>alt_nameservers</c>.</p>
   </section>
 
+  <section>
+    <title>Resolver Types</title>
+    <p>The following data types concern the resolver:</p>
+  </section>
   <datatypes>
-    <p>Resolver types:</p>
     <datatype>
       <name name="res_option"/>
     </datatype>
@@ -88,8 +91,13 @@
     <datatype>
       <name name="res_error"/>
     </datatype>
-
-    <p><marker id="dns_types"/>DNS types:</p>
+  </datatypes>
+  <section>
+    <title>DNS Types</title>
+    <p><marker id="dns_types"/>
+      The following data types concern the DNS client:</p>
+  </section>
+  <datatypes>
     <datatype>
       <name name="dns_name"/>
       <desc><p>A string with no adjacent dots.</p></desc>
@@ -106,7 +114,7 @@
         <p>This is the start of a hiearchy of opaque data structures
           that can be examined with access functions in inet_dns that
           return lists of {Field,Value} tuples. The arity 2 functions
-          just return the value for a given field.
+          just return the value for a given field.</p>
 <pre>
 dns_msg() = DnsMsg
     inet_dns:msg(DnsMsg) ->
@@ -154,18 +162,19 @@ dns_rr() = DnsRr
                      | {version, integer()}
                      | {z, integer()}
                      | {data, dns_data()} ]
-    inet_dns:rr(DnsRr, Field) -> Value
+    inet_dns:rr(DnsRr, Field) -> Value</pre>
 
-There is an info function for the types above:
+<p>There is an info function for the types above:</p>
 
+<pre>
 inet_dns:record_type(dns_msg()) -> msg;
 inet_dns:record_type(dns_header()) -> header;
 inet_dns:record_type(dns_query()) -> dns_query;
 inet_dns:record_type(dns_rr()) -> rr;
-inet_dns:record_type(_) -> undefined.
+inet_dns:record_type(_) -> undefined.</pre>
 
-So; inet_dns:(inet_dns:record_type(X))(X) will convert
-any of these data structures into a {Field,Value} list.</pre></p>
+<p>So; inet_dns:(inet_dns:record_type(X))(X) will convert
+any of these data structures into a {Field,Value} list.</p>
       </desc>
     </datatype>
     <datatype>
@@ -272,7 +281,7 @@ any of these data structures into a {Field,Value} list.</pre></p>
         <p>Resolve a DNS record of the given type and class for the given name.
           The returned <c>dns_msg()</c> can be examined using
           access functions in <c>inet_db</c> as described 
-          in <seealso marker="#dns_types">DNS types</seealso>.
+          in <seealso marker="#dns_types">DNS Types</seealso>.
         </p><p>
           If <c><anno>Name</anno></c> is an <c>ip_address()</c>, the domain name
           to query for is generated as the standard reverse
diff --git a/lib/kernel/doc/src/net_adm.xml b/lib/kernel/doc/src/net_adm.xml
index 1072be44a5..4ef9d361f6 100644
--- a/lib/kernel/doc/src/net_adm.xml
+++ b/lib/kernel/doc/src/net_adm.xml
@@ -89,8 +89,8 @@
     <func>
       <name name="world" arity="0"/>
       <name name="world" arity="1"/>
-      <type name="verbosity"/>
       <fsummary>Lookup and connect to all nodes at all hosts in <c>.hosts.erlang</c></fsummary>
+      <type name="verbosity"/>
       <desc>
         <p>This function calls <c>names(Host)</c> for all hosts which
           are specified in the Erlang host file <c>.hosts.erlang</c>,
@@ -110,8 +110,8 @@
     <func>
       <name name="world_list" arity="1"/>
       <name name="world_list" arity="2"/>
-      <type name="verbosity"/>
       <fsummary>Lookup and connect to all nodes at specified hosts</fsummary>
+      <type name="verbosity"/>
       <desc>
         <p>As <c>world/0,1</c>, but the hosts are given as argument
           instead of being read from <c>.hosts.erlang</c>.</p>
diff --git a/lib/kernel/doc/src/notes.xml b/lib/kernel/doc/src/notes.xml
index 76db0c201f..268a8404f1 100644
--- a/lib/kernel/doc/src/notes.xml
+++ b/lib/kernel/doc/src/notes.xml
@@ -1218,7 +1218,7 @@
         </item>
         <item>
 	    <p> Fix returned error from gen_tcp:accept/1,2 when
-	    running out of ports
+	    running out of ports.</p>
           <p>
 	    The {error, enfile} return value is badly misleading and
 	    confusing for this case, since the Posix ENFILE errno
@@ -1227,7 +1227,7 @@
 	    {error, system_limit}, which is consistent with e.g.
 	    various file(3) functions. inet:format_error/1 has also
 	    been updated to support system_limit in the same manner
-	    as file:format_error/1. (Thanks to Per Hedeland)</p></p>
+	    as file:format_error/1. (Thanks to Per Hedeland)</p>
           <p>
 	    Own Id: OTP-9990</p>
         </item>
@@ -1422,7 +1422,6 @@
 	    Own Id: OTP-9764</p>
         </item>
         <item>
-          <p>
 	    <list> <item><p>Correct callback spec in application
 	    module</p></item> <item><p>Refine warning about callback
 	    specs with extra ranges</p></item> <item><p>Cleanup
@@ -1433,7 +1432,7 @@
 	    analysis</p></item> <item><p>Fix crash in
 	    Dialyzer</p></item> <item><p>Variable substitution was
 	    not generalizing any unknown variables.</p></item>
-	    </list></p>
+	    </list>
           <p>
 	    Own Id: OTP-9776</p>
         </item>
diff --git a/lib/kernel/doc/src/os.xml b/lib/kernel/doc/src/os.xml
index 2d2a690fea..682d4a2eac 100644
--- a/lib/kernel/doc/src/os.xml
+++ b/lib/kernel/doc/src/os.xml
@@ -171,8 +171,8 @@ DirOut = os:cmd("dir"), % on Win32 platform</code>
     </func>
     <func>
       <name name="timestamp" arity="0"/>
-      <type_desc variable="Timestamp">Timestamp = {MegaSecs, Secs, MicroSecs}</type_desc>
       <fsummary>Current OS system time on the erlang:timestamp/0 format</fsummary>
+      <type_desc variable="Timestamp">Timestamp = {MegaSecs, Secs, MicroSecs}</type_desc>
       <desc>
       <p>Returns current
 	<seealso marker="erts:time_correction#OS_System_Time">OS system time</seealso>
@@ -205,7 +205,7 @@ format_utc_timestamp() ->
 29 Apr 2009  9:55:30.051711
 </pre>
        <p>OS system time can also be retreived by
-	<c><seealso marker="#system_time/0"><c>os:system_time/0</c></seealso></c>,
+	<seealso marker="#system_time/0"><c>os:system_time/0</c></seealso>,
 	and <seealso marker="#system_time/1"><c>os:system_time/1</c></seealso>.</p>
       </desc>
     </func>