Merge pull request #5465 from alexberriman/patch-1

docs/guide/test-overview.md

@@ -29,8 +29,8 @@ The process of developing a feature is the following:
 After it's done the process is repeated again for another feature or improvement. If existing feature is to be changed,
 tests should be changed as well.
 
-> **Tip**: If you feel that you are loosing time doing a lot of small and simple iterations try covering more by your
-> test scenario so you do more before executing tests again. If you're debugging too much try doing the opposite.
+> **Tip**: If you feel that you are losing time doing a lot of small and simple iterations, try covering more by your
+> test scenario so you do more before executing tests again. If you're debugging too much, try doing the opposite.
 
 The reason to create tests before doing any implemenation is that it allows you to focus on what do we want to achieve
 and fully dive into "how to do it" afterwards. Usually it leads to better abstractions and easier test maintenance when