From eb49cb934557cf2500532e9bcdec1ae6db53b098 Mon Sep 17 00:00:00 2001
From: Pushpender <46690325+pushpend3r@users.noreply.github.com>
Date: Thu, 2 Jul 2020 23:18:39 +0530
Subject: [PATCH] Type mistake

Used "unitialized" instead of "uninitialized"
---
 1-js/06-advanced-functions/03-closure/7-let-scope/solution.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/06-advanced-functions/03-closure/7-let-scope/solution.md b/1-js/06-advanced-functions/03-closure/7-let-scope/solution.md
index 404bae80be..346e4060a3 100644
--- a/1-js/06-advanced-functions/03-closure/7-let-scope/solution.md
+++ b/1-js/06-advanced-functions/03-closure/7-let-scope/solution.md
@@ -15,7 +15,7 @@ function func() {
 func();
 ```
 
-In this example we can observe the peculiar difference between a "non-existing" and "unitialized" variable.
+In this example we can observe the peculiar difference between a "non-existing" and "uninitialized" variable.
 
 As you may have read in the article [](info:closure), a variable starts in the "uninitialized" state from the moment when the execution enters a code block (or a function). And it stays uninitalized until the corresponding `let` statement.