From 26e45cd6e98e7c8c5e2ace7088d8b4ff92bf0142 Mon Sep 17 00:00:00 2001 From: Clarence Bakosi Date: Wed, 4 Jun 2025 14:22:17 +0100 Subject: [PATCH] fix(curriculum): typo falsey instead of falsy (#60706) --- .../6732720e95f6a0db526a2e4d.md | 4 ++-- .../workshop-spam-filter/641cdf57c3f7ee276e1d9b32.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/curriculum/challenges/english/25-front-end-development/lecture-working-with-numbers-booleans-and-the-math-object/6732720e95f6a0db526a2e4d.md b/curriculum/challenges/english/25-front-end-development/lecture-working-with-numbers-booleans-and-the-math-object/6732720e95f6a0db526a2e4d.md index 4ff4a7eb354..7f984254d9e 100644 --- a/curriculum/challenges/english/25-front-end-development/lecture-working-with-numbers-booleans-and-the-math-object/6732720e95f6a0db526a2e4d.md +++ b/curriculum/challenges/english/25-front-end-development/lecture-working-with-numbers-booleans-and-the-math-object/6732720e95f6a0db526a2e4d.md @@ -40,7 +40,7 @@ const result = false && 0; console.log(result); // false ``` -Since `false` is a falsey value, then `false` is logged to the console. The logical AND operator is useful when you want to check multiple conditions and ensure that all are true before proceeding. Here is an example: +Since `false` is a falsy value, then `false` is logged to the console. The logical AND operator is useful when you want to check multiple conditions and ensure that all are true before proceeding. Here is an example: ```js if (2 < 3 && 3 < 4) { @@ -90,7 +90,7 @@ const result = null ?? 'default'; console.log(result); // default ``` -Since `null` is a falsey value, the string `default` would be logged to the console. The nullish coalescing operator is incredibly useful in situations where `null` or `undefined` are the only values that should trigger a fallback or default value. Here is an example of dealing with a user's preference settings: +Since `null` is a falsy value, the string `default` would be logged to the console. The nullish coalescing operator is incredibly useful in situations where `null` or `undefined` are the only values that should trigger a fallback or default value. Here is an example of dealing with a user's preference settings: ```js const userSettings = { diff --git a/curriculum/challenges/english/25-front-end-development/workshop-spam-filter/641cdf57c3f7ee276e1d9b32.md b/curriculum/challenges/english/25-front-end-development/workshop-spam-filter/641cdf57c3f7ee276e1d9b32.md index e48d745428d..14d577a0be8 100644 --- a/curriculum/challenges/english/25-front-end-development/workshop-spam-filter/641cdf57c3f7ee276e1d9b32.md +++ b/curriculum/challenges/english/25-front-end-development/workshop-spam-filter/641cdf57c3f7ee276e1d9b32.md @@ -35,7 +35,7 @@ try { } ``` -When you click your `checkMessageButton` and the `isSpam(messageInput.value)` is falsey, you should set the `textContent` property of `result` to `"This message does not seem to contain any spam."`. +When you click your `checkMessageButton` and the `isSpam(messageInput.value)` is falsy, you should set the `textContent` property of `result` to `"This message does not seem to contain any spam."`. ```js messageInput.value = "spam";