Update rules/Proj0039.md

Co-authored-by: Laura Kramer <[email protected]>

Author: Corniel

rules/Proj0039.md

@@ -19,7 +19,7 @@ Developers that are not capable to solve a warning (correctly) are still not abl
 A specific, but common scenario is when a new version of a package is released, suddenly some code has been deprecated. Obviously the code has to be adjusted once, but it is not said that the moment you need the new version of the package is also the moment to refactor all code that relies on this now deprecated code.
 
 ## 3. New rules
-The introduction of new rules (both because introduced by an existing analyser or because a new analyser was introduced) will potentially report a lot of issues. They might be valid points, but no reason to halt the release of all features until all issues are solved. By (temporarily) disabling such rules, newly added code will not yet benefit from this rule.
+The introduction of new rules (introduced by an existing analyser or by a newly added analyser) will potentially report a lot of issues. They might be valid points, but you don't necessarily want to halt the release of all features until all issues are solved. By (temporarily) disabling such rules, newly added code will not yet benefit from this rule.
 
 ## 4. Warnings are not errors
 It is possible to create static code analysis with an error severity. The reason that this is not done by the maker of the rule is with a reason. Apparently the code is not wrong per se, but you are warned that is beneficial to change the code.