Fixed a couple of typo in dev doc.

Author: Clément

.github/CONTRIBUTING.md

@@ -1,3 +1,3 @@
 # Contributing Guidelines
 
-See: [docs/contributing](https://github.com/princomp/princomp.github.io/blob/main/docs/contributing.md)
+See: [docs/about/contributing](https://princomp.github.io/docs/about/contributing)

source/docs/about/dev_guide.md

@@ -217,9 +217,10 @@ A `{ width=80% }` attribute at the end of this string could help in resizing the
 
 ##### Images generated by LaTeX
 
+<!-- TODO: update the following. -->
+
 Some images are generated by LaTeX: the `.tex` file is what is used to generate the `.pdf` file, and then pdf2svg converts the `.pdf` into a `.svg` file.
 pdftoppm furthermore convert the `.pdf` into a `.png`.
-<!-- TODO: update the following. -->
 The `.svg` files are used in the `.html`, `.odt` and `.docx` documents, while the `.pdf` is used in the `.pdf` documents.
 The resulting images are added to the repository so that there is no need to re-compile them every time, or to set-up LaTeX and latexmk on each system.
 
@@ -258,11 +259,10 @@ Graphs are used to represent binary trees.
 
 To create a new class diagram, say for a `BTree_Example`, follow those steps:
 
-1. Create a `BTree_Example.txt` file in `source/diag/gra` that follows [the syntax for flowchart diagrams](https://mermaid.js.org/syntax/flowchart.html) (note that there is no need to add `flowchart` at the beginning, it will be done automatically),
-2. Add on the first line a comment `%% title` with "title" the title of the diagram,
-3. Run (from the `source/` folder) `make diag/gra/BTree_Example.md`,
-4. Integrate the resulting drawing, properly captioned and with links to `BTree_Example.txt`, `BTree_Example.svg` and `BTree_Example.png` files using `!include diag/flo/BTree_Example.md`.
-
+#. Create a `BTree_Example.txt` file in `source/diag/gra` that follows [the syntax for flowchart diagrams](https://mermaid.js.org/syntax/flowchart.html) (note that there is no need to add `flowchart` at the beginning, it will be done automatically),
+#. Add on the first line a comment `%% title` with "title" the title of the diagram,
+#. Run (from the `source/` folder) `make diag/gra/BTree_Example.md`,
+#. Integrate the resulting drawing, properly captioned and with links to `BTree_Example.txt`, `BTree_Example.svg` and `BTree_Example.png` files using `!include diag/flo/BTree_Example.md`.
 
 #### Source code
 
@@ -282,9 +282,6 @@ To create a new class diagram, say for a `BTree_Example`, follow those steps:
         Do **not** add solution (`sln`) or project (`csproj`) files: they will be created automatically using the project and solution's name you specified (and a makefile rule [similar to this one](https://github.com/csci-1301/C-Sharp-project-maker)), if multiple classes are present they will all be linked, and the resulting archive will be hosted at `content/code/projects/<solution>.zip`.
 
 - Source code that is faulty, partial, or does not terminate can be included in markdown as inline code block.
-<!--
-- We can automatically check these code snippets for syntactical correctness if these guidelines are followed
--->
 
 Code snippets can be included in markdown documents using [pandoc-include](https://github.com/DCsunset/pandoc-include) filter: