otp: Convert all <seealso> to more specific variants

We add `seemfa`, `seeerl`, `seetype`, `seeapp`, `seecom`, `seecref`
, `seefile` and `seeguide` in order to make it easier to reason
about what each link points to without examining the target.

This information will then be embedded in the EEP-48 chunks for
usage by other tools.

The tool used can be found here:
  https://gist.github.com/garazdawi/68527d92ae5b37c8f129bfbdfffdfa68

2 files changed, 6 insertions, 6 deletions

diff --git a/lib/xmerl/doc/src/xmerl_sax_parser.xml b/lib/xmerl/doc/src/xmerl_sax_parser.xml
index 0c5ecb5c2e..178d084c31 100644
--- a/lib/xmerl/doc/src/xmerl_sax_parser.xml
+++ b/lib/xmerl/doc/src/xmerl_sax_parser.xml
@@ -56,7 +56,7 @@
        <taglist>
          <tag><c>{continuation_fun, ContinuationFun}</c></tag>
          <item>
-           <seealso marker="#Module:ContinuationFun/1">ContinuationFun</seealso> is a call back function to decide what to do if
+           <seemfa marker="#Module:ContinuationFun/1">ContinuationFun</seemfa> is a call back function to decide what to do if
            the parser runs into EOF before the document is complete. 
          </item>
          <tag><c>{continuation_state, term()}</c></tag>
@@ -65,7 +65,7 @@
          </item>
          <tag><c>{event_fun, EventFun}</c></tag>
          <item>
-           <seealso marker="#Module:EventFun/3">EventFun</seealso> is the call back function for parser events.
+           <seemfa marker="#Module:EventFun/3">EventFun</seemfa> is the call back function for parser events.
          </item>
          <tag><c>{event_state, term()}</c></tag>
          <item>
diff --git a/lib/xmerl/doc/src/xmerl_ug.xmlsrc b/lib/xmerl/doc/src/xmerl_ug.xmlsrc
index e4aeaddc78..dee8166d90 100644
--- a/lib/xmerl/doc/src/xmerl_ug.xmlsrc
+++ b/lib/xmerl/doc/src/xmerl_ug.xmlsrc
@@ -210,7 +210,7 @@ Grand Danois\
     <p>If you instead receives the XML doc as a string you can
       parse it by <c>xmerl_scan:string/1</c>. Both file/2 and string/2
       exists where the second argument is a list of options to the
-      parser, see the <seealso marker="xmerl_scan">reference manual</seealso>.</p>
+      parser, see the <seeerl marker="xmerl_scan">reference manual</seeerl>.</p>
   </section>
 
   <section>
@@ -280,7 +280,7 @@ Grand Danois\
       <item>Value = IOString | atom() | integer()</item>
     </list>
     <p>See also reference manual for 
-      <seealso marker="xmerl#export_simple-3">xmerl</seealso></p>
+      <seeerl marker="xmerl#export_simple-3">xmerl</seeerl></p>
     <p>If you want to add the information about a black Harley
       Davidsson 1200 cc Sportster motorcycle from 2003 that is in
       shape as new in the motorcycles.xml document you can put the
@@ -363,7 +363,7 @@ Data =
 
   <section>
     <title>Example: Transforming XML To HTML</title>
-    <p>Assume that you want to transform the <seealso marker="#motorcyclesxml">motorcycles.xml</seealso> document to
+    <p>Assume that you want to transform the <seeguide marker="#motorcyclesxml">motorcycles.xml</seeguide> document to
       HTML. If you want the same structure and tags of the resulting
       HTML document as of the XML document then you can use the
       <c>xmerl:export/2</c> function. The following:</p>
@@ -408,7 +408,7 @@ Data =
       formats.</p>
     <p><c>xmerl_xs</c> does not implement the entire XSLT
       specification but the basic functionality. For all details see
-      the <seealso marker="xmerl_xs">reference manual</seealso></p>
+      the <seeerl marker="xmerl_xs">reference manual</seeerl></p>
     <p>First, some words about the xmerl_xs functionality:</p>
     <p>You need to write template functions to be able to control
       what kind of output you want. Thus if you want to encapsulate a