From f385db63f91dbce3cf8bea2c0759f472cac11faf Mon Sep 17 00:00:00 2001 From: oktay Aslan Date: Sun, 15 Dec 2024 20:31:58 +0300 Subject: [PATCH] Fix typos This PR improves the "Why Coverage?" section by adding clarity, ensuring consistency, and enhancing professionalism. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c6183f6ab6183e..8441fb8a39a86e 100644 --- a/README.md +++ b/README.md @@ -108,7 +108,7 @@ some problem. Our unit-test suite is how we encode the set of *problems* the co the test suite should indicate that your change didn't *infringe* on anyone else's solutions. Adding a test *protects* your solution from future changes. Say you don't understand why a line of code exists, try deleting it and running the unit-tests. The nearest test failure should tell you what problem -was solved by that code. If no test fails, go ahead and submit a Pull Request that asks, "what +was solved by that code. If no test fails, go ahead and submit a Pull Request that asks, "What problem is solved by this code?" On the other hand, if a test does fail and you can think of a better way to solve the same problem, a Pull Request with your solution would most certainly be welcome! Likewise, if rewriting a test can better communicate what code it's protecting, please