- Fixed up graph paths

docs/implementation/34-dependency.md

@@ -127,7 +127,7 @@ wraps the following methods and fields within it:
     -   This adds the given `DNode` as a dependency to the current
         DNode, effectively appending it to the `dependencies` array.
 
-![](docs/graphs/pandocplot390552161348119324.svg)
+![](/projects/tlang/graphs/pandocplot390552161348119324.svg)
 
 #### The `DNodeGenerator`
 
@@ -179,7 +179,7 @@ we would have done something akin to the following. Our scenario is that
 we have some sort of parse node, let's assume it was a `Variable` parse
 node which would represent a variable declaration.
 
-![](docs/graphs/pandocplot11037938885968638614.svg)
+![](/projects/tlang/graphs/pandocplot11037938885968638614.svg)
 
 ------------------------------------------------------------------------
 

docs/implementation/35-typechecking.md

@@ -100,4 +100,4 @@ the other being a `FuncCall` instruction):
 
 This would result in a situation where we have the following production
 
-![](docs/graphs/pandocplot12139419864099887541.svg)
+![](/projects/tlang/graphs/pandocplot12139419864099887541.svg)

docs/implementation/37-compiler.md

@@ -9,7 +9,7 @@ that if a requirement for a decision to be taken based on compiler flags
 is specified then such configuration paremeters can be obtained via each
 module of the compilation stage.
 
-![](docs/graphs/pandocplot6118349527803707673.svg)
+![](/projects/tlang/graphs/pandocplot6118349527803707673.svg)
 
 ### Compiler system
 

helpers.sh

@@ -39,8 +39,8 @@ function generateMarkdown()
 
         pandoc -F pandoc-plot -M plot-configuration=pandoc-plot.conf -f markdown -t markdown "$doc" -o "$outputFile"
 
-        # echo "$(cat $outputFile | sed -e s/docs//)" > "$outputFile"
-        # cat "$outputFile"
+        echo "$(cat $outputFile | sed -e s/docs\\//\\/projects\\/tlang\\//)" > "$outputFile"
+        cat "$outputFile"
         # break
 
         echo "Converting markdown for doc '$doc'... [done]"