diff --git a/.github/workflows/cmake.yml b/.github/workflows/cmake.yml
index 86d6601..31dfafe 100644
--- a/.github/workflows/cmake.yml
+++ b/.github/workflows/cmake.yml
@@ -53,4 +53,12 @@ jobs:
       working-directory: ${{github.workspace}}/build
       run: | 
         spack load tfel
-        make check 
+        make check
+        
+    - name: Test Report
+      uses: dorny/test-reporter@v1
+      if: success() || failure()    # run this step even if previous step failed
+      with:
+        name: Tests reports         # Name of the check run which will be created
+        path: build/**/*.xml        # Path to test results
+        reporter: jest-junit
diff --git a/docs/web/index.md b/docs/web/index.md
index c7f6fab..a8acb2c 100644
--- a/docs/web/index.md
+++ b/docs/web/index.md
@@ -61,7 +61,7 @@ integration process to guarantee that no regression would happen as
 
 In particular, the project provides:
 
-- a [`cmake`](https://cmake.org) infrastructure that can be duplicated
+- A [`cmake`](https://cmake.org) infrastructure that can be duplicated
   in (academic or industrial) derived projects. This infrastructure allows:
   - to compile `MFront` sources using all interfaces supported
     by `MFront`. For example, concerning behaviours, the behaviours can
@@ -90,9 +90,9 @@ In particular, the project provides:
   [This page](creating-derived-project.html) describes how to create a
   derived project based on the same infrastructure as the
   `MFrontGallery`.
-- a documentation of best practices to handle material knowledge
-  implemented using `MFront` implementations
-- a set of high-quality `MFront` implementations.
+- A documentation of [best practices](best-pratices.html) to handle
+  material knowledge implemented using `MFront` implementations.
+- A set of high-quality `MFront` implementations.
 
 Section @sec:mfm:introduction:statement_of_need discusses why a new
 approach to material knowledge management is needed in the context of