Update docs/standards/developer-testing.md

Co-authored-by: Robert Deniszczyc <[email protected]>

docs/standards/developer-testing.md

@@ -24,10 +24,10 @@ A good test should be clear on the intent of the test, have one test case, be re
 
 Testing can come in different forms, for example unit/integration/mutation/property based, but all must adhere to the requirements as the following benefits can be achieved:
 
-- Easy to correct failures in code from failed tests.
+- Easy to correct failures in code from failed tests
 - Security & confidence when continously integrating code
 - Easy to understand intent and functionality of code
-- Tests are owned by the same team who owns the code and not within a silo external to the team.
+- Tests are owned by the same team who owns the code and not within a silo external to the team
 
 ---