From 3cbc31904ad8aaf14eb594153a9955a011b33fa8 Mon Sep 17 00:00:00 2001 From: 11un Date: Sat, 12 Jan 2019 13:13:35 -0800 Subject: [PATCH] typo "if (it) displays" --- 1-js/02-first-steps/14-function-basics/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/02-first-steps/14-function-basics/article.md b/1-js/02-first-steps/14-function-basics/article.md index 5328a934..26e8e77c 100644 --- a/1-js/02-first-steps/14-function-basics/article.md +++ b/1-js/02-first-steps/14-function-basics/article.md @@ -374,7 +374,7 @@ A few examples of breaking this rule: - `getAge` -- would be bad if it shows an `alert` with the age (should only get). - `createForm` -- would be bad if it modifies the document, adding a form to it (should only create it and return). -- `checkPermission` -- would be bad if displays the `access granted/denied` message (should only perform the check and return the result). +- `checkPermission` -- would be bad if it displays the `access granted/denied` message (should only perform the check and return the result). These examples assume common meanings of prefixes. What they mean for you is determined by you and your team. Maybe it's pretty normal for your code to behave differently. But you should have a firm understanding of what a prefix means, what a prefixed function can and cannot do. All same-prefixed functions should obey the rules. And the team should share the knowledge. ```