1 files changed, 4 insertions, 4 deletions
diff --git a/test/test.dox b/test/test.dox
index 296e2145e..114b2af85 100644
--- a/test/test.dox
+++ b/test/test.dox
@@ -46,15 +46,15 @@
  *   for this execution test, it is done automatically by a script because
  *   the entire sequence can take hours).<br>
  *   All the tests results are included as reports in the OS distribution
- *   under @p ./docs/reports.
+ *   under <tt>./docs/reports</tt>.
  * - <b>Ports</b>. The port code is tested by executing the kernel test
  *   suite on the target hardware. A port is validated only if it passes all
  *   the tests. Speed and size benchmarks for all the supported architectures
  *   are performed, both size and speed regressions are <b>monitored</b>.
  * - <b>HAL</b>. The HAL high level code and device drivers implementations
- *   are tested by use in the various demos and/or by users.
+ *   are tested through specific test applications under <tt>./testhal</tt>.
  * - <b>Various</b>. The miscellaneous code is tested by use in the various
- *   demos and/or by users.
+ *   demos.
  * - <b>External Code</b>. Not tested, external libraries or components are
  *   used as-is or with minor patching where required, problems are usually
  *   reported upstream.
@@ -65,7 +65,7 @@
  * subsystems and can report a failure/success status and/or a performance
  * index as the test suite output.<br>
  * The test suite is usually activated in the demo applications by pressing a
- * button on the target board, see the readme into the various demos
+ * button on the target board, see the readme file into the various demos
  * directories. The test suite output is usually sent through a serial port
  * and can be examined by using a terminal emulator program.
  *