Making use of the inter-documentation linking feature

manual/new/docs/en/coding-standards/coding-style.txt

@@ -162,7 +162,7 @@ class Foo
 threeArguments(1, 2, 3);
 </code>
 
-* Call-time pass by-reference is prohibited. See the function declarations section for the proper way to pass function arguments by-reference.
+* Call-time pass by-reference is prohibited. See section above for the proper way to pass function arguments by-reference.
 * For functions whose arguments permitted arrays, the function call may include the {{array}} construct and can be split into multiple lines to improve readability. In these cases, the standards for writing arrays still apply:
 
 <code type="php">

manual/new/docs/en/hierarchical-data/nested-set.txt

@@ -38,7 +38,7 @@ To set up your model as Nested Set, you must add the following code to your mode
 ...
 </code>
 
-Detailed information on Doctrine's templating model can be found in chapter 12: Class templates. These templates add some functionality to your model. In the example of the nested set, your model gets 3 additional fields: "lft", "rgt", "level". You never need to care about "lft" and "rgt". These are used internally to manage the tree structure. The "level" field however, is of interest for you because it's an integer value that represents the depth of a node within it's tree. A level of 0 means it's a root node. 1 means it's a direct child of a root node and so on. By reading the "level" field from your nodes you can easily display your tree with proper indendation. 
+Detailed information on Doctrine's templating model can be found in chapter [doc class-templates :index :name]. These templates add some functionality to your model. In the example of the nested set, your model gets 3 additional fields: "lft", "rgt", "level". You never need to care about "lft" and "rgt". These are used internally to manage the tree structure. The "level" field however, is of interest for you because it's an integer value that represents the depth of a node within it's tree. A level of 0 means it's a root node. 1 means it's a direct child of a root node and so on. By reading the "level" field from your nodes you can easily display your tree with proper indendation. 
 
 **You must never assign values to lft, rgt, level. These are managed transparently by the nested set implementation.**
 

manual/new/docs/en/plugins.txt

@@ -165,7 +165,7 @@ You can also control the name of the versioning record and the name of the versi
 
 Soft-delete is a very simple plugin for achieving the following behaviour: when a record is deleted its not removed from database. Usually the record contains some special field like 'deleted' which tells the state of the record (deleted or alive).
 
-The following code snippet shows what you need in order to achieve this kind of behaviour. Notice how we define two event hooks: preDelete and postDelete. Also notice how the preDelete hook skips the actual delete-operation with skipOperation() call. For more info about the event hooks see the Event listener section.
+The following code snippet shows what you need in order to achieve this kind of behaviour. Notice how we define two event hooks: preDelete and postDelete. Also notice how the preDelete hook skips the actual delete-operation with skipOperation() call. For more info about the event hooks see chapter [doc event-listeners :index :name].
 
 <code type="php">
 class SoftDeleteTest extends Doctrine_Record

manual/new/docs/en/relations.txt

@@ -146,7 +146,7 @@ class Phonenumber extends Doctrine_Record
 
 A tree structure is a self-referencing foreign key relation. The following definition is also called Adjacency List implementation in terms of hierarchical data concepts. 
 
-However this mainly just serves as an example how the self-referencing can be done. The definition above is rarely a good way of expressing hierarchical data, hence you should take a look at the Hierachical data chapter for how to set up efficient parent/child relations.
+However this mainly just serves as an example how the self-referencing can be done. The definition above is rarely a good way of expressing hierarchical data, hence you should take a look at chapter [doc hierarchical-data :index :name] for how to set up efficient parent/child relations.
 
 <code type="php">
 class Task extends Doctrine_Record 

manual/new/docs/en/working-with-objects/component-overview/record.txt

@@ -63,7 +63,7 @@ $users = $conn->query("FROM User WHERE User.name LIKE '%John%'");
 
 ++++ Accessing properties
 
-You can retrieve existing objects (database rows) with {{Doctrine_Table}} or {{Doctrine_Connection}}. {{Doctrine_Table}} provides simple methods like {{findBySql}}, {{findAll}} and find for finding objects whereas {{Doctrine_Connection}} provides complete OQL API for retrieving objects (see chapter 9). 
+You can retrieve existing objects (database rows) with {{Doctrine_Table}} or {{Doctrine_Connection}}. {{Doctrine_Table}} provides simple methods like {{findBySql}}, {{findAll}} and find for finding objects whereas {{Doctrine_Connection}} provides complete OQL API for retrieving objects (see chapter [doc dql-doctrine-query-language). 
 
 <code type="php">
 $user = $table->find(3);