diff --git a/usrguide/userguide/2-overview_of_titan.adoc b/usrguide/userguide/2-overview_of_titan.adoc
index 7bb53e52fe05b95ba25d87486d5f144123a718d6..848818885c45a042ac8eb66e6ee3df0b7139861f 100644
--- a/usrguide/userguide/2-overview_of_titan.adoc
+++ b/usrguide/userguide/2-overview_of_titan.adoc
@@ -37,7 +37,7 @@ image::images/titanexecutor_structure_x.png[title="Titan structure"]
 
 Creating a TTCN–3 test suite involves building an executable from the initial modules (TTCN–3, ASN.1 or both) and test port files. The process basically comprises creating and modifying a `Makefile` and using the `make` command to build the executable.
 
-For detailed information, refer to <<3-creating_executable_test_suites_from_the_command-l.adoc, Creating Executable Test Suites from the Command-line>>.
+For detailed information, refer to <<3-creating_executable_test_suites_from_the_command-l.adoc#creating-executable-test-suites-from-the-command-line, Creating Executable Test Suites from the Command-line>>.
 
 == Executing Test Suites
 
@@ -45,4 +45,4 @@ After the test suite has been created a suitable configuration file has been bui
 
 The test executor can operate in single or parallel mode. The single mode—also called non-parallel mode—is thought for TTCN–3 test suites built around a single test component. It is forbidden to create parallel test components in single mode: the test suite is not supposed to contain any `create` operation otherwise the test execution will fail. The parallel mode, on the other hand, offers full-featured test execution including distributed and parallel execution. The goal of introducing the single operating mode was to eliminate redundancies and thereby increase the speed of execution. It is possible to execute non-parallel test suites in parallel mode, but doing so results in unnecessary overhead. The {cpp} code generated by the compiler is suitable for both execution modes, there are no command line switches to select mode. The only difference is that different Base Libraries must be linked in single and parallel modes.
 
-For detailed information on executing test suites in single or parallel mode, refer to <<4-executing_test_suites.adoc, Executing Test Suites>>.
+For detailed information on executing test suites in single or parallel mode, refer to <<4-executing_test_suites.adoc#executing-test-suites, Executing Test Suites>>.
diff --git a/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc b/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc
index 48b23c2771fc087e473d6ca15cd3ec258d92ce54..cf0d68267f0c8c0745c59ad5f4475a84881bcb45 100644
--- a/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc
+++ b/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc
@@ -1,6 +1,8 @@
-= Creating Executable Test Suites from the Command-line
+[[creating-executable-test-suites-from-the-command-line]]
+= Creating Executable Test Suites from the Command line
 
-This section describes the elementary commands that comprise the build process. The primary audience of this section is the group of users who want to integrate TTCN–3 to a new or an existing build system.
+This section describes the elementary commands that comprise the build process.
+The primary audience of this section is the group of users who want to integrate TTCN–3 to a new or an existing build system.
 
 == Using `make`
 
diff --git a/usrguide/userguide/4-executing_test_suites.adoc b/usrguide/userguide/4-executing_test_suites.adoc
index 028aaf1b2d4083677c39764e7d2090e29456ff2d..0c4521e78ad144eb43404add695e38fe2343e815 100644
--- a/usrguide/userguide/4-executing_test_suites.adoc
+++ b/usrguide/userguide/4-executing_test_suites.adoc
@@ -1,3 +1,4 @@
+[[executing-test-suites]]
 = Executing Test Suites
 
 This chapter describes the modalities of test suite execution.