Fix link errors in common_test documentation

These were introduced when converting from edoc to xml files for the
common_test documentation.

1 files changed, 5 insertions, 5 deletions

diff --git a/lib/common_test/doc/src/dependencies_chapter.xml b/lib/common_test/doc/src/dependencies_chapter.xml
index d96a41473f..29c54e819a 100644
--- a/lib/common_test/doc/src/dependencies_chapter.xml
+++ b/lib/common_test/doc/src/dependencies_chapter.xml
@@ -87,8 +87,8 @@
       <p>To avoid this, we can consider starting and stopping the server for every test.
       We can thus implement the start and stop action as common functions to be 
       called from 
-      <seealso marker="common_test_app#Module:init_per_testcase-2"><c>init_per_testcase</c></seealso> and 
-      <seealso marker="common_test_app#Module:end_per_testcase-2"><c>end_per_testcase</c></seealso>. 
+      <seealso marker="common_test#Module:init_per_testcase-2"><c>init_per_testcase</c></seealso> and 
+      <seealso marker="common_test#Module:end_per_testcase-2"><c>end_per_testcase</c></seealso>. 
       (Remember to test the start and stop functionality separately.) 
       The configuration can also be implemented as a common function, maybe grouped 
       with the start function. Finally, the testing of connecting and disconnecting a 
@@ -194,9 +194,9 @@
 
       <p>To pass data from one test suite to another, the same mechanism is used. The data
 	is to be saved by finction
-	<seealso marker="common_test_app#Module:end_per_suite-1"><c>end_per_suite</c></seealso> 
+	<seealso marker="common_test#Module:end_per_suite-1"><c>end_per_suite</c></seealso> 
 	and read by function
-	<seealso marker="common_test_app#Module:init_per_suite-1"><c>init_per_suite</c></seealso>
+	<seealso marker="common_test#Module:init_per_suite-1"><c>init_per_suite</c></seealso>
 	in the suite that follows. When passing data between suites, <c>Saver</c> carries the 
 	name of the test suite.</p>
 
@@ -306,7 +306,7 @@
         any property, that is, they are not required to also be sequences. If you want the 
 	status of the subgroup to affect the sequence on the level above, return 
 	<c>{return_group_result,Status}</c> from 
-	<seealso marker="common_test_app#Module:end_per_group-2"><c>end_per_group/2</c></seealso>, 
+	<seealso marker="common_test#Module:end_per_group-2"><c>end_per_group/2</c></seealso>, 
 	as described in section
 	<seealso marker="write_test_chapter#repeated_groups">Repeated Groups</seealso>
 	in Writing Test Suites.