From 6ed86c957fda153f7db76c535d2f149a4a08f64c Mon Sep 17 00:00:00 2001 From: Brent Guffens Date: Fri, 19 Jan 2018 14:23:48 +0100 Subject: [PATCH] Typo --- 1-js/03-code-quality/03-comments/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/03-code-quality/03-comments/article.md b/1-js/03-code-quality/03-comments/article.md index 480bffe3..2683f139 100644 --- a/1-js/03-code-quality/03-comments/article.md +++ b/1-js/03-code-quality/03-comments/article.md @@ -146,7 +146,7 @@ Document a function usage Also, there are tools like [JSDoc 3](https://github.com/jsdoc3/jsdoc) that can generate HTML-documentation from the comments. You can read more information about JSDoc at . Why is the task solved this way? -: What's written is important. But what's *not* written maybe even more important to understand what's going on. Why is the task solved exactly this way? The code gives no answer. +: What's written is important. But what's *not* written may be even more important to understand what's going on. Why is the task solved exactly this way? The code gives no answer. If there are many ways to solve the task, why this one? Especially when it's not the most obvious one.