From 2b515d9750d8690a869c81526c36cd4e1903c194 Mon Sep 17 00:00:00 2001
From: jtimpe <111305129+jtimpe@users.noreply.github.com>
Date: Tue, 19 Nov 2024 08:43:43 -0500
Subject: [PATCH] Update
 docs/Technical-Documentation/tech-memos/parsing-log-per-file/parsing-log-per-file.md

Co-authored-by: Eric Lipe <125676261+elipe17@users.noreply.github.com>
---
 .../tech-memos/parsing-log-per-file/parsing-log-per-file.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Technical-Documentation/tech-memos/parsing-log-per-file/parsing-log-per-file.md b/docs/Technical-Documentation/tech-memos/parsing-log-per-file/parsing-log-per-file.md
index 39c124ca1..a8edd79f2 100644
--- a/docs/Technical-Documentation/tech-memos/parsing-log-per-file/parsing-log-per-file.md
+++ b/docs/Technical-Documentation/tech-memos/parsing-log-per-file/parsing-log-per-file.md
@@ -6,7 +6,7 @@
 
 ## Summary
 This technical memorandum discusses the implementation of features to bring more visibility into system behavior during file parsing. This includes:
-* Generating a storing a file for logs generated during the parsing run. The log file should be stored in s3, alongside the submitted datafile.
+* Generating and storing a file for logs generated during the parsing run. The log file should be stored in s3, alongside the submitted datafile.
 
 This memo discussed various proposed implementations and the benefits/drawbacks of each, then provides a suggested implementation taking these factors into consideration.