From 4010985814b52db31db3dfef8923c9555eaf4ff4 Mon Sep 17 00:00:00 2001
From: aua <77854924+rnllv@users.noreply.github.com>
Date: Fri, 21 Mar 2025 12:55:59 -0700
Subject: [PATCH] Fix typo in pattern-syntax.md

---
 website/guide/pattern-syntax.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/guide/pattern-syntax.md b/website/guide/pattern-syntax.md
index 66887217..8c026a9b 100644
--- a/website/guide/pattern-syntax.md
+++ b/website/guide/pattern-syntax.md
@@ -141,7 +141,7 @@ testFunc(1 + 1)
 testFunc(...args)
 ```
 
-Note in the example above, even if two meta variables have the same name `$_FUNC`, each occurrence of `$_FUNC` can match different content because the are not captured.
+Note in the example above, even if two meta variables have the same name `$_FUNC`, each occurrence of `$_FUNC` can match different content because they are not captured.
 
 :::info Why use non-capturing match?
 This is a useful trick to micro-optimize pattern matching speed, since we don't need to create a [HashMap](https://doc.rust-lang.org/stable/std/collections/struct.HashMap.html) for bookkeeping.
@@ -165,4 +165,4 @@ Pattern can also be an object instead of string in YAML rule.
 It is very useful to avoid ambiguity in code snippet. See [here](/guide/rule-config/atomic-rule.html#pattern) for more details.
 
 Also see our FAQ for more [guidance](/advanced/faq.html) on writing patterns.
-:::
\ No newline at end of file
+:::