From f54683e4c9550bd2c9771f0f64bff0cdb58049fe Mon Sep 17 00:00:00 2001
From: Simon Brandt <123938598+Simon-Brandt@users.noreply.github.com>
Date: Thu, 5 Jun 2025 10:31:50 +0200
Subject: [PATCH] Fix plural form

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

diff --git a/SC2034.md b/SC2034.md
index d7a57b3..bd2e895 100644
--- a/SC2034.md
+++ b/SC2034.md
@@ -37,9 +37,9 @@ export "$name"; eval "echo $name"
 declare -n name; echo "$name"
 ```
 
-This is an intentional design decision and not a bug. If you have variables that will not have direct references, consider using an associative array in bash, or just [[Ignore]] the warning. 
+This is an intentional design decision and not a bug. If you have variables that will not have direct references, consider using an associative array in bash, or just [[ignore]] the warning. 
 
-Tracking indirect references is a common problem for compilers and static analysis tool, and it is known to be unsolvable in the most general case. There are two ways to handle unresolved indirections (which in a realistic program will essentially be all of them):
+Tracking indirect references is a common problem for compilers and static analysis tools, and it is known to be unsolvable in the most general case. There are two ways to handle unresolved indirections (which in a realistic program will essentially be all of them):
 
 * Avoid false positives by assuming all variables may potentially be used (disable all unused variable warnings)
 * Keep true positives by allowing some false positives (emit unused variable warnings that may be incorrect)