diff --git a/6-InRealEnvironment/6-Tools.ipynb b/6-InRealEnvironment/6-Tools.ipynb
index ca3280efcd7d394b2e4431f839091bd2ae117fc4..4602377e59291e2c7a2b7775ede376bcbb83ecdf 100644
--- a/6-InRealEnvironment/6-Tools.ipynb
+++ b/6-InRealEnvironment/6-Tools.ipynb
@@ -73,7 +73,7 @@
     "\n",
     "### Doctest\n",
     "\n",
-    "[doctest](https://github.com/onqtam/doctest) is a C++ testing framework but is by far the fastest both in compile times (by orders of magnitude) and runtime compared to other feature-rich alternatives. It brings the ability of compiled languages to have tests written directly in the production code thanks to a fast, transparent and flexible test runner with a clean interface.\n",
+    "[doctest](https://github.com/onqtam/doctest) is another C++ testing framework that was very appreciated by one of the teacher (Vicente) in the 2021 session of this tutorial.\n",
     "\n",
     "\n",
     "### BoostTest\n",
@@ -97,7 +97,7 @@
     "\n",
     "I can mention [Uncrustify](http://uncrustify.sourceforge.net/): plenty of options to configure, even if they're not easy to figure out.\n",
     "\n",
-    "[clang-format](https://clang.llvm.org/docs/ClangFormat.html) probably provides a better trade-off power/complexity but requires LLVM clang to be installed on your system (AppleClang won't do). Can be easily installed through Homebrew though.\n",
+    "[clang-format](https://clang.llvm.org/docs/ClangFormat.html) probably provides a better trade-off power/complexity but requires LLVM clang to be installed on your system (AppleClang won't do, but you can easily install it on macOS with Homebrew). Can be easily installed through Homebrew though.\n",
     "\n",
     "\n",
     "## Doxygen\n",
@@ -106,10 +106,10 @@
     "\n",
     "It is rather easy to set up to easy task but may become a tad more difficult once you want to tackle more advanced features. Nonetheless it is the de-facto standard for C++ documentation and it's really something you should set up quite early if you're working on a project meant to stay for a while: it's really a hassle to spend countless hours providing after the fact such guidance in the code. As for compilers, you should strive to provide a documentation without any warning.\n",
     "\n",
-    "An important drawback of Doxygen is that its \"compilation\" of your project is much less advanced than the one provided by your compiler:\n",
+    "An important drawback of Doxygen is that its \"compilation\" of your project is much less advanced than the one provided by your compiler (even if they clearly upped their game in recent years):\n",
     "\n",
     "* No parallelism in some steps.\n",
-    "* Everything is redone at each Doxygen call.\n",
+    "* A lot is done again at each Doxygen call.\n",
     "\n",
     "So expect for important projects the time to generate Doxygen documentation to be bigger than compilation time. \n",
     "\n",