diff --git a/man/manual.docbook b/man/manual.docbook
index 5c772731a..1bdca18ac 100644
--- a/man/manual.docbook
+++ b/man/manual.docbook
@@ -250,7 +250,7 @@ Checking path/file2.cpp...
     </section>
   </chapter>
 
-  <chapter>
+  <chapter id="preprocessor-configurations">
     <title>Preprocessor configurations</title>
 
     <para>By default Cppcheck will check all preprocessor configurations
@@ -263,11 +263,11 @@ Checking path/file2.cpp...
     <para>Beware that only the macros, which are given here and the macros
     defined in source files and known header files are considered. That
     excludes all the macros defined in some system header files, which are by
-    default not examined by cppcheck.</para>
+    default not examined by Cppcheck.</para>
 
     <para>The usage: if you, for example, want to limit the checking so the
-    only configuration to check should be "DEBUG=1;__cplusplus" then something
-    like this can be used:</para>
+    only configuration to check should be <literal>DEBUG=1;__cplusplus</literal>
+    then something like this can be used:</para>
 
     <programlisting>cppcheck -DDEBUG=1 -D__cplusplus path</programlisting>
   </chapter>
@@ -617,9 +617,9 @@ htmlreport/cppcheck-htmlreport --file=err.xml --report-dir=test1 --source-dir=.<
       recommended that this known functionality is redefined. But feel free to
       try it.</para>
 
-      <para>As you can read in chapter 3 in this manual the default is that
-      Cppcheck checks all configurations. So only provide preprocessor defines
-      if you want to limit the checking.</para>
+      <para>As you can read in <link linkend="preprocessor-configurations">chapter
+      3</link> in this manual the default is that Cppcheck checks all configurations.
+      So only provide preprocessor defines if you want to limit the checking.</para>
     </section>
   </chapter>
   
diff --git a/man/writing-rules-1.docbook b/man/writing-rules-1.docbook
index ec4d10111..1dd1db043 100644
--- a/man/writing-rules-1.docbook
+++ b/man/writing-rules-1.docbook
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<section>
+<section id="writing-rules-1">
   <title>Part 1 - Getting started</title>
 
   <section>
diff --git a/man/writing-rules-2.docbook b/man/writing-rules-2.docbook
index 23156266e..5a246d6c0 100644
--- a/man/writing-rules-2.docbook
+++ b/man/writing-rules-2.docbook
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<section>
+<section id="writing-rules-2">
   <title>Part 2 - The Cppcheck data representation</title>
 
   <section>
diff --git a/man/writing-rules-3.docbook b/man/writing-rules-3.docbook
index 07078c3a0..cb5b56787 100644
--- a/man/writing-rules-3.docbook
+++ b/man/writing-rules-3.docbook
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<section>
+<section id="writing-rules-3">
   <title>Part 3 - Introduction to writing rules with C++</title>
 
   <section>
@@ -83,9 +83,9 @@ void CheckOther::divisionByZeroError()
   <section>
     <title>Condition before deallocation</title>
 
-    <para>In the first <literal>Writing rules</literal> article I described a
-    rule that looks for redundant conditions. Here is the regular expression
-    that was shown:</para>
+    <para>In the first <link linkend="writing-rules-1">Writing rules</link> part
+    I described a rule that looks for redundant conditions. Here is the regular
+    expression that was shown:</para>
 
     <programlisting>if \( p \) { free \( p \) ; }</programlisting>