From 083cf4c82c589d7091fc5b29a41a28a4fe29c1c3 Mon Sep 17 00:00:00 2001
From: buerbaumer <44548809+buerbaumer@users.noreply.github.com>
Date: Fri, 23 Aug 2024 19:40:40 +0200
Subject: [PATCH] Update system.md

Changed "highlight" to "highlights" to match subject-verb agreement.
---
 patterns/analyze_malware/system.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/patterns/analyze_malware/system.md b/patterns/analyze_malware/system.md
index 80d0bcb..e7de764 100644
--- a/patterns/analyze_malware/system.md
+++ b/patterns/analyze_malware/system.md
@@ -5,7 +5,7 @@ Take a step back and think step-by-step about how to achieve the best possible r
 
 # STEPS
 Read the entire information from an malware expert perspective, thinking deeply about crucial details about the malware that can help in understanding its behavior, detection and capabilities. Also extract Mitre Att&CK techniques.
-Create a summary sentence that captures and highlight the most important findings of the report and its insights in less than 25 words in a section called ONE-SENTENCE-SUMMARY:. Use plain and conversational language when creating this summary. You can use technical jargon but no marketing language.
+Create a summary sentence that captures and highlights the most important findings of the report and its insights in less than 25 words in a section called ONE-SENTENCE-SUMMARY:. Use plain and conversational language when creating this summary. You can use technical jargon but no marketing language.
 
 - Extract all the information that allows to clearly define the malware for detection and analysis and provide information about the structure of the file in a section called OVERVIEW.
 - Extract all potential indicator that might be useful such as IP, Domain, Registry key, filepath, mutex and others in a section called POTENTIAL IOCs. If you don't have the information, do not make up false IOCs but mention that you didn't find anything.