From 82ecb9d132976b8d99713b0e13da59a6fd6a810e Mon Sep 17 00:00:00 2001
From: SanjayTr <35617078+SanjayTr@users.noreply.github.com>
Date: Thu, 18 Oct 2018 18:16:16 -0400
Subject: [PATCH 1/2] line 152

---
 EducationalAssignments/ParityPartTwo.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/EducationalAssignments/ParityPartTwo.md b/EducationalAssignments/ParityPartTwo.md
index 14cd4f66..a3971b00 100644
--- a/EducationalAssignments/ParityPartTwo.md
+++ b/EducationalAssignments/ParityPartTwo.md
@@ -149,7 +149,7 @@ The try, except, else and finally statements are part of **exception handling**.
 When writing your own tests it is important to test for a complete set of possible penetrations.  Keep in mind, it only takes one test case to break through a security layer.  Some of the things you may want to test for include:
 
  * threading
- * writing to multiple files????
+ * writing to multiple files
  * multiple writes
 
 And more!  Remember a good security layer can't be broken by anyone!  Which is all part of the fun!  It's about solving a puzzle.  First you make the puzzle - write the security layer, then you solve the puzzle - try to bypass it.  If your puzzle is "good enough", no one will be able to break it, no matter what.  

From 6309f1671f4be4cc491df0e429cecf47d7d86013 Mon Sep 17 00:00:00 2001
From: SanjayTr <35617078+SanjayTr@users.noreply.github.com>
Date: Thu, 18 Oct 2018 18:27:09 -0400
Subject: [PATCH 2/2] removing 'write to multiple files'

---
 EducationalAssignments/ParityPartTwo.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/EducationalAssignments/ParityPartTwo.md b/EducationalAssignments/ParityPartTwo.md
index a3971b00..95a302bb 100644
--- a/EducationalAssignments/ParityPartTwo.md
+++ b/EducationalAssignments/ParityPartTwo.md
@@ -149,7 +149,6 @@ The try, except, else and finally statements are part of **exception handling**.
 When writing your own tests it is important to test for a complete set of possible penetrations.  Keep in mind, it only takes one test case to break through a security layer.  Some of the things you may want to test for include:
 
  * threading
- * writing to multiple files
  * multiple writes
 
 And more!  Remember a good security layer can't be broken by anyone!  Which is all part of the fun!  It's about solving a puzzle.  First you make the puzzle - write the security layer, then you solve the puzzle - try to bypass it.  If your puzzle is "good enough", no one will be able to break it, no matter what.