Readme

README.md

@@ -771,7 +771,7 @@ Phred takes the reliability of your applications exceptionally serious. Consider
 
 The unit tests with which Phred is accompanied are just one part of the Phred's effort in making your projects maximally bug-free, dependable, and therefore secure. Aside from a few classes that are still in development or require intricate testing techniques that are yet to be implemented, practically every method of every class was thoroughly tested to make sure that it will work as intended and to achieve a high method and line coverage. The Phred's unit tests are powered by [PHPUnit](http://phpunit.de/) testing framework and can be run with `run-unit-tests.php` script located in the root directory. A byproduct of the unit tests is that they can serve as an abundant source of examples showing the majority of the Phred's classes and methods is use.
 
-However, because unit tests are only run occasionally after a significant change has been introduced into the code and because the diversity in the input values and their combinations is constantly limited by how the tests were initially shaped, Phred deems unit tests not sufficient enough. With the purpose of keeping the chances of bugs getting into your application as low as possible and in order to improve bug detection and bug tracking, Phred made a move to expand testing further on the runtime by means of semantic checks.
+However, because unit tests are only run occasionally after a significant change has been introduced into the code and because the diversity of input values and their combinations are limited by how the tests were initially shaped, Phred deems unit tests not sufficient enough. For the purpose of keeping the chances of bugs getting into your applications as low as physically possible and in order to improve bug detection and bug tracking, Phred made a move to expand testing further on the runtime by means of semantic checks.
 
 ## Semantic Checks