Skip to content

Commit 991ca66

Browse files
authored
Merge pull request #616 from jayhybrid/patch-7
Improved phrasing
2 parents 94b90c0 + b1b04d9 commit 991ca66

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

1-js/02-first-steps/14-function-basics/article.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -334,7 +334,7 @@ So, it effectively becomes an empty return. We should put the value on the same
334334
335335
## Naming a function [#function-naming]
336336
337-
Functions are actions. So their name is usually a verb. It should briefly, but as accurately as possible, describe what the function does, so that someone reading the code gets an indication of what the function does.
337+
Functions are actions. So their name is usually a verb. It should be brief, as accurate as possible and describe what the function does, so that someone reading the code gets an indication of what the function does.
338338
339339
It is a widespread practice to start a function with a verbal prefix which vaguely describes the action. There must be an agreement within the team on the meaning of the prefixes.
340340
@@ -376,9 +376,9 @@ These examples assume common meanings of prefixes. What they mean for you is det
376376
```smart header="Ultrashort function names"
377377
Functions that are used *very often* sometimes have ultrashort names.
378378

379-
For example, the [jQuery](http://jquery.com) framework defines a function `$`. The [LoDash](http://lodash.com/) library has its core function named `_`.
379+
For example, the [jQuery](http://jquery.com) framework defines a function with `$`. The [LoDash](http://lodash.com/) library has its core function named `_`.
380380

381-
These are exceptions. Generally functions names should be concise, but descriptive.
381+
These are exceptions. Generally functions names should be concise and descriptive.
382382
```
383383

384384
## Functions == Comments

0 commit comments

Comments
 (0)