From 1faac313e1bf1240935bdb2f6920ba9b70087ab2 Mon Sep 17 00:00:00 2001 From: Clarence Date: Thu, 24 Apr 2025 19:34:34 +0100 Subject: [PATCH] fix(curriculum): typo in lecture the var keyword and hoisting (#59965) --- .../67335f45489c5a11b71d0ed5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/curriculum/challenges/english/25-front-end-development/lecture-the-var-keyword-and-hoisting/67335f45489c5a11b71d0ed5.md b/curriculum/challenges/english/25-front-end-development/lecture-the-var-keyword-and-hoisting/67335f45489c5a11b71d0ed5.md index 443942c281d..e48495df424 100644 --- a/curriculum/challenges/english/25-front-end-development/lecture-the-var-keyword-and-hoisting/67335f45489c5a11b71d0ed5.md +++ b/curriculum/challenges/english/25-front-end-development/lecture-the-var-keyword-and-hoisting/67335f45489c5a11b71d0ed5.md @@ -26,7 +26,7 @@ var x = 5; console.log(5); // 5 ``` -In this code even though we use `x` before declaring it we don't get an error, instead we get `undefined`. This is because JavaScript hoists the declaration `var x` to the top of its scope but not the inialization `x = 5`. It's as if the code were rewritten like this: +In this code even though we use `x` before declaring it we don't get an error, instead we get `undefined`. This is because JavaScript hoists the declaration `var x` to the top of its scope but not the initialization `x = 5`. It's as if the code were rewritten like this: ```js var x;