C++-test.md

@@ -49,8 +49,9 @@ You can add assertions in your tests that should fail and stop the execution (or
 - ...
 > **`CHECK` & `REQUIRE` Assertions :**
 >
->Each `REQUIRE` assertion has his `CHECK` equivalent. The difference lies in the fact that if a `REQUIRE`   assertion fails, the test suite will stop with SIGABRT where for a `CHECK` the test suite will keep going. 
-> Hence it is recommended to use `REQUIRE` only when you know that the tested condition if false, will impair the whole test suite. This allows for more visibility on the failures of your test suite.
+>Each `REQUIRE` assertion has his `CHECK` equivalent. The difference lies in the fact that if a `REQUIRE`   assertion fails, the test suite will stop with SIGABRT where for a `CHECK` the test suite will keep going.
+>
+> Hence it is recommended to use `REQUIRE` only when you know that the tested condition, if not met, will impair the whole test suite. This allows for more visibility on the failures of your test suite.
 
 ## Compiling unit-tests