From a5197f7ed087ae43a3469db3d6a14c2c21a55eb1 Mon Sep 17 00:00:00 2001
From: Patrick <50352812+Mueller-Patrick@users.noreply.github.com>
Date: Thu, 10 Jun 2021 19:07:48 +0200
Subject: [PATCH] Updated Test Plan (markdown)

---
 Test-Plan.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Test-Plan.md b/Test-Plan.md
index 9babb05..6efc704 100644
--- a/Test-Plan.md
+++ b/Test-Plan.md
@@ -117,7 +117,7 @@ The tests will mainly be written to ensure that any changes in the future don't
 
 ### 2.1 Background
 
-Testing serves to ensure that the written code does what it is intended to do. It also prevents future code changes to break existing functionality unnoticed. In the context of integration it can also prevent broken software states to be merged into secured VC branches
+Testing serves to ensure that the written code does what it is intended to do. It also prevents future code changes to break existing functionality unnoticed. In the context of integration it can also prevent broken software states to be merged into secured VC branches.
 
 ### 2.2 Evaluation Mission
 
@@ -131,7 +131,7 @@ Testing serves to ensure that the written code does what it is intended to do. I
 
 ### 2.3 Test Motivators
 
-The main test motivators are quality and technical risks as we want to make sure that every version that gets deployed to production is working and as bug-free as possible
+The main test motivators are quality and technical risks as we want to make sure that every version that gets deployed to production is working and as bug-free as possible.
 
 ## 3. Target Test Items