From 56d9e8edab7329ecc76d30b7f3f1be63c074ad76 Mon Sep 17 00:00:00 2001
From: Aaron Russell <128606235+aaronrussellHO@users.noreply.github.com>
Date: Fri, 19 Jan 2024 09:58:05 +0000
Subject: [PATCH] Update docs/standards/developer-testing.md

Co-authored-by: Robert Deniszczyc <72561986+robertdeniszczyc2@users.noreply.github.com>
---
 docs/standards/developer-testing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/standards/developer-testing.md b/docs/standards/developer-testing.md
index 315cc315..7a94e107 100644
--- a/docs/standards/developer-testing.md
+++ b/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
 
 ---