From 927dfed81ff72a4d6aa8f9fcef48049f0da89ffa Mon Sep 17 00:00:00 2001
From: James <85808999+TheGreatSageEqualToHeaven@users.noreply.github.com>
Date: Thu, 15 Feb 2024 18:11:15 +0000
Subject: [PATCH] Update syntax-if-statements-initializers.md

---
 docs/syntax-if-statements-initializers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/syntax-if-statements-initializers.md b/docs/syntax-if-statements-initializers.md
index 27ca3c0..e1f0026 100644
--- a/docs/syntax-if-statements-initializers.md
+++ b/docs/syntax-if-statements-initializers.md
@@ -12,7 +12,7 @@ The reduced scope pollution improves register space in extreme cases (or auto-ge
 
 # Design
 
-If statements with initializers must match (following the Luau grammar) `'if' 'local' bindinglist ['=' explist] 'then'` and `'local' bindinglist ['=' explist] where exp 'then'` syntax. Parenthesis are also allowed around the initializer for consistency with other expressions. The variables declared by the initializer are only available to the block of that condition and will be undefined to the `elseif` conditions and blocks as well as the `else` block; any code after the if statement won't have the variables defined either.
+If statements with initializers must match (following the Luau grammar) `'if' 'local' bindinglist ['=' explist] 'then'` and `'local' bindinglist ['=' explist] where exp 'then'` syntax. The variables declared by the initializer are only available to the block of that condition and will be undefined to the `elseif` conditions and blocks as well as the `else` block; any code after the if statement won't have the variables defined either.
 
 In the former case, the value of the first declared variable will be checked.