From 183e3cf9eb9c401e9440a02485b80dee0b7d9230 Mon Sep 17 00:00:00 2001 From: Kristofer Koishigawa Date: Tue, 17 Dec 2024 20:32:49 +0900 Subject: [PATCH] fix: JS comments lecture multiple choice question (#57553) --- .../672d49e65a1c855fe7bb3fdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/curriculum/challenges/english/25-front-end-development/lecture-introduction-to-javascript/672d49e65a1c855fe7bb3fdb.md b/curriculum/challenges/english/25-front-end-development/lecture-introduction-to-javascript/672d49e65a1c855fe7bb3fdb.md index ab6814c50b7..f86b39c3dee 100644 --- a/curriculum/challenges/english/25-front-end-development/lecture-introduction-to-javascript/672d49e65a1c855fe7bb3fdb.md +++ b/curriculum/challenges/english/25-front-end-development/lecture-introduction-to-javascript/672d49e65a1c855fe7bb3fdb.md @@ -98,7 +98,7 @@ Think about how comments help clarify but should not clutter the code. --- -Only use comments for complex logic or unclear code. +Use comments to provide context and leave notes for yourself and other developers. ---