6 files changed, 10 insertions, 18 deletions
diff --git a/lib/common_test/doc/src/cover_chapter.xml b/lib/common_test/doc/src/cover_chapter.xml
index 0d56d4824c..12db7226c4 100644
--- a/lib/common_test/doc/src/cover_chapter.xml
+++ b/lib/common_test/doc/src/cover_chapter.xml
@@ -85,7 +85,7 @@
     <p>To activate the code coverage support, specify the name of the cover 
       specification file as you start <c>Common Test</c>.
       Do this by using flag <c>-cover</c> with 
-      <seeerl marker="ct_run"><c>ct_run</c></seeerl>, 
+      <seecom marker="ct_run"><c>ct_run</c></seecom>, 
       for example:</p>
       <pre>
  $ ct_run -dir $TESTOBJS/db -cover $TESTOBJS/db/config/db.coverspec</pre>
diff --git a/lib/common_test/doc/src/ct.xml b/lib/common_test/doc/src/ct.xml
index 79420ec8a4..c3bb257f22 100644
--- a/lib/common_test/doc/src/ct.xml
+++ b/lib/common_test/doc/src/ct.xml
@@ -1339,8 +1339,8 @@
       <desc><marker id="run_test-1"/>
         <p>Runs tests as specified by the combination of options in
           <c>Opts</c>. The options are the same as those used with program
-          <c>ct_run</c>, see <seeerl marker="ct_run#ct_run">Run Tests from
-          Command Line</seeerl> in the <c>ct_run</c> manual page.</p>
+          <c>ct_run</c>, see <seecom marker="ct_run#ct_run">Run Tests from
+          Command Line</seecom> in the <c>ct_run</c> manual page.</p>
         <p>Here a <c>TestDir</c> can be used to point out the path to a
           <c>Suite</c>. Option <c>testcase</c> corresponds to option
           <c>-case</c> in program <c>ct_run</c>. Configuration files
diff --git a/lib/common_test/doc/src/event_handler_chapter.xml b/lib/common_test/doc/src/event_handler_chapter.xml
index 3ee1ea785a..ee758c3199 100644
--- a/lib/common_test/doc/src/event_handler_chapter.xml
+++ b/lib/common_test/doc/src/event_handler_chapter.xml
@@ -81,7 +81,7 @@
     <marker id="usage"></marker>
     <title>Use</title>
     <p>Event handlers can be installed by an <c>event_handler</c> start flag 
-    (<seeerl marker="ct_run"><c>ct_run</c></seeerl>) or option 
+    (<seecom marker="ct_run"><c>ct_run</c></seecom>) or option 
     <seemfa marker="ct#run_test/1"><c>ct:run_test/1</c></seemfa>, where the
     argument specifies the names of one or more event handler modules.</p>
 
diff --git a/lib/common_test/doc/src/install_chapter.xml b/lib/common_test/doc/src/install_chapter.xml
index 2cc7da98f2..17ef6c8dc1 100644
--- a/lib/common_test/doc/src/install_chapter.xml
+++ b/lib/common_test/doc/src/install_chapter.xml
@@ -36,7 +36,7 @@
 
     <p>The two main interfaces for running tests with <c>Common Test</c>
       are an executable program named 
-      <seeerl marker="ct_run"><c>ct_run</c></seeerl> and the
+      <seecom marker="ct_run"><c>ct_run</c></seecom> and the
       Erlang module <seeerl marker="ct"><c>ct</c></seeerl>. 
       <c>ct_run</c> is compiled for the underlying operating system (for example,
       Unix/Linux or Windows) during the build of the Erlang/OTP system, 
@@ -51,11 +51,3 @@
       and/or the interface functions in the <c>ct</c> module.</p>
     </section>
 </chapter>
-
-
-
-
-
-
-
-
diff --git a/lib/common_test/doc/src/run_test_chapter.xml b/lib/common_test/doc/src/run_test_chapter.xml
index f83858cbc0..0b8657ced3 100644
--- a/lib/common_test/doc/src/run_test_chapter.xml
+++ b/lib/common_test/doc/src/run_test_chapter.xml
@@ -80,7 +80,7 @@
     <p>If test suites or help modules include header files stored in other
       locations than the test directory, these include directories can be specified
       by using flag <c><![CDATA[-include]]></c> with 
-      <seeerl marker="ct_run"><c>ct_run</c></seeerl>, 
+      <seecom marker="ct_run"><c>ct_run</c></seecom>, 
       or option <c><![CDATA[include]]></c> with <c><![CDATA[ct:run_test/1]]></c>.
       Also, an include path can be specified with an OS
       environment variable, <c><![CDATA[CT_INCLUDE_PATH]]></c>.</p>
@@ -119,7 +119,7 @@
   <marker id="ct_run"></marker>
     <title>Running Tests from the OS Command Line</title>
     
-    <p>The <seeerl marker="ct_run"><c>ct_run</c></seeerl> program can be used 
+    <p>The <seecom marker="ct_run"><c>ct_run</c></seecom> program can be used 
        for running tests from the OS command line, for example, as follows:
     </p>
     <list type="bulleted">
@@ -153,7 +153,7 @@
     <seeguide marker="run_test_chapter#group_execution">Test Case Group Execution</seeguide>.</p>
 
     <p>The following flags can also be used with 
-    <seeerl marker="ct_run"><c>ct_run</c></seeerl>:</p>
+    <seecom marker="ct_run"><c>ct_run</c></seecom>:</p>
     <taglist>
       <tag><c><![CDATA[-help]]></c></tag>
       <item><p>Lists all available start flags.</p></item>
@@ -303,7 +303,7 @@
     <c>ct_run -dir ./</c></p></note>
 
     <p>For more information about the <c>ct_run</c> program, see module
-      <seeerl marker="ct_run"><c>ct_run</c></seeerl> and section
+      <seecom marker="ct_run"><c>ct_run</c></seecom> and section
       <seeguide marker="install_chapter#general">Installation</seeguide>.
     </p>
   </section>
diff --git a/lib/common_test/doc/src/write_test_chapter.xml b/lib/common_test/doc/src/write_test_chapter.xml
index cfc5b4dd6d..3c3790cfc5 100644
--- a/lib/common_test/doc/src/write_test_chapter.xml
+++ b/lib/common_test/doc/src/write_test_chapter.xml
@@ -833,7 +833,7 @@
       configured to create one dedicated private directory per
       test case and execution instead. This is accomplished with
       the flag/option <c>create_priv_dir</c> (to be used with the
-      <seeerl marker="ct_run"><c>ct_run</c></seeerl> program, the 
+      <seecom marker="ct_run"><c>ct_run</c></seecom> program, the 
       <seemfa marker="ct#run_test/1"><c>ct:run_test/1</c></seemfa> function, or
       as test specification term). There are three possible values
       for this option as follows: