From 647d2e5c37b25513172c1b91bfb56a77b8097aa4 Mon Sep 17 00:00:00 2001
From: Giftpflanze <80504430+gifti258@users.noreply.github.com>
Date: Tue, 12 Mar 2024 07:29:55 +0100
Subject: [PATCH] docs: fix typo

---
 docs/section-3-creating-parsers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/section-3-creating-parsers.md b/docs/section-3-creating-parsers.md
index 33976442..3e1745c8 100644
--- a/docs/section-3-creating-parsers.md
+++ b/docs/section-3-creating-parsers.md
@@ -620,7 +620,7 @@ You may have noticed in the above examples that some of the grammar rule name li
 
 ### Using Fields
 
-Often, it's easier to analyze a syntax nodes if you can refer to its children by *name* instead of by their position in an ordered list. Tree-sitter grammars support this using the `field` function. This function allows you to assign unique names to some or all of a node's children:
+Often, it's easier to analyze a syntax node if you can refer to its children by *name* instead of by their position in an ordered list. Tree-sitter grammars support this using the `field` function. This function allows you to assign unique names to some or all of a node's children:
 
 ```js
 function_definition: $ => seq(