X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/086b90c313820b91596f07ed2a05671e321c6f98..ab4f499c8d903b3e66655b42202a29ece975112b:/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn?ds=sidebyside

diff --git a/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn b/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn
index 17be5b9b2..6bef2619e 100644
--- a/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn
+++ b/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn
@@ -50,7 +50,7 @@ This is the most important feature of a requirements engineering tool. How to do
  * One simple solution: Links. Just link from one requirement to another one to create a traceable directional connection
  * One harder: file attributes (see section about requirements just above)
 
-For coverage analysis , using [ikiwiki/directive/pagecount] is the perfect solution to summarize and show covered and uncovered requirements. We could add several pages per module - probably using template pages-  with ready made coverage analysis reports... Wow!!! [ikiwiki/directive/linkmap] directive can show traceability information graphically.
+For coverage analysis , using [[ikiwiki/directive/pagecount]] is the perfect solution to summarize and show covered and uncovered requirements. We could add several pages per module - probably using template pages-  with ready made coverage analysis reports... Wow!!! [[ikiwiki/directive/linkmap]] directive can show traceability information graphically.
 
 Navigating among requirements needs... Nothing!!! Just follow the links of referring pages that ikiwiki adds by default.