Skip to content

Commit b692fd9

Browse files
committed
# Conflicts: # 1-js/05-data-types/06-iterable/article.md
2 parents 9909532 + dcb9d87 commit b692fd9

282 files changed

Lines changed: 2190 additions & 1648 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 1 addition & 1 deletion
Loading
Lines changed: 1 addition & 1 deletion
Loading

1-js/02-first-steps/12-while-for/article.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ But we can force the exit at any time using the special `break` directive.
212212

213213
For example, the loop below asks the user for a series of numbers, "breaking" when no number is entered:
214214

215-
```js
215+
```js run
216216
let sum = 0;
217217

218218
while (true) {

1-js/02-first-steps/15-function-expressions-arrows/article.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -350,7 +350,7 @@ welcome(); // ok now
350350
```smart header="When to choose Function Declaration versus Function Expression?"
351351
As a rule of thumb, when we need to declare a function, the first to consider is Function Declaration syntax. It gives more freedom in how to organize our code, because we can call such functions before they are declared.
352352
353-
That's also better for readability, as it's easier to look up `function f(…) {…}` in the code than `let f = function(…) {…}`. Function Declarations are more "eye-catching".
353+
That's also better for readability, as it's easier to look up `function f(…) {…}` in the code than `let f = function(…) {…};`. Function Declarations are more "eye-catching".
354354
355355
...But if a Function Declaration does not suit us for some reason, or we need a conditional declaration (we've just seen an example), then Function Expression should be used.
356356
```

0 commit comments

Comments
 (0)