From cc8d9bdc7fedb410917ee26347cbf2650e7cf7f9 Mon Sep 17 00:00:00 2001
From: Tony Torralba <atorralba@users.noreply.github.com>
Date: Wed, 24 Nov 2021 13:57:34 +0100
Subject: [PATCH] Update ql/src/Security/CWE-117/LogInjection.qhelp

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
---
 ql/src/Security/CWE-117/LogInjection.qhelp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ql/src/Security/CWE-117/LogInjection.qhelp b/ql/src/Security/CWE-117/LogInjection.qhelp
index 23ac820b0db..31a05e6faa1 100644
--- a/ql/src/Security/CWE-117/LogInjection.qhelp
+++ b/ql/src/Security/CWE-117/LogInjection.qhelp
@@ -9,7 +9,7 @@ be able to forge new log entries.</p>
 <p>Forgery can occur if a user provides some input with characters that are interpreted
 when the log output is displayed. If the log is displayed as a plain text file, then new
 line characters can be used by a malicious user. If the log is displayed as HTML, then
-arbitrary HTML may be include to spoof log entries.</p>
+arbitrary HTML may be included to spoof log entries.</p>
 </overview>
 
 <recommendation>