Update rules/Proj0039.md

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

Author: Corniel

rules/Proj0039.md

@@ -22,7 +22,7 @@ A specific, but common scenario is when a new version of a package is released,
 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.
+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. It might be inefficient, deprecated or unreadable code, but not necessarily wrong.
 
 ## 5. Conflicting IDE extensions
 Some extensions in Visual Studio (like VS Spell Checker or SonarQube IDE) add warnings to the build output as they are de facto analysers. As they are not configured by the solution but by the environment of the developer, those developers can not build the solution.