Update rules/Proj0039.md

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

Author: Corniel

rules/Proj0039.md

@@ -13,7 +13,7 @@ When a warning pops up, the developer facing it, is supposed to solve the issue.
 
 A developer that was not willing to resolve the issue as a warning is most likely also not willing to resolve it as an error beyond the bare minimum: that means by suppressing the issue, disabling the rule, or by adjusting the code just to satisfy the rule. None of these resolutions is guaranteed to be an improvement.
 
-Developers that are not capable to solve a warning (correctly) are still not able to do so once its become an error. If they did find the support to solve it correctly, what would make they would do this now? Or will they come up with the solutions equal to the unwilling developer?
+Developers that are not capable to solve a warning (correctly) are still not able to do so once it becomes an error. If they did find the support to solve it correctly, what would make they would do this now? Or will they come up with the solutions equal to the unwilling developer?
 
 ## 2. Deprecated code
 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.