update documentation

doc/templates.md

@@ -30,7 +30,7 @@ They are broadly split along the classes that are generated for each datatype or
 | `[Mutable]Object.{h,cc}.jinja2` | The user facing interfaces for each datatype (living in the user layer)                                 | `[<package>/][Mutable]<datatype-name>.h`, `src/[Mutable]<datatype-name>.cc`           |
 | `Collection.{h,cc}.jinja2`      | The user facing collection interface (living in the user layer)                                         | `[<package>/]<datatype-name>Collection.h`, `src/<datatype-name>Collection.cc`         |
 | `CollectionData.{h,cc}.jinja2`  | The classes managing the collection storage (not user facing!)                                          | `[<package>/]<datatype-name>CollectionData.h`, `src/<datatype-name>CollectionData.cc` |
-| `DictLinkDef.h.jinja2`          | The `LinkDef.h` file that is necessary for generating a root dictionary for the generated datamodel | `[<package>/]LinkDef.h`                                                                   |
+| `DictLinkDef.h.jinja2`          | The `LinkDef.h` file that is necessary for generating a root dictionary for the generated datamodel | `src/LinkDef.h`                                                                   |
 | `SIOBlock.{h,cc}.jinja2`        | The SIO blocks that are necessary for the SIO backend                                                   | `[<package>/]<datatype-name>SIOBlock.h`, `src/<datatype-name>SIOBlock.cc`             |
 
 The presence of a `[<package>]` subdirectory for the header files is controlled by the `includeSubfolder` option in the yaml definition file.