This commit is contained in:
Ilya Kantor 2019-01-13 20:40:08 +03:00
commit a733718af3
2 changed files with 2 additions and 2 deletions

View file

@ -133,7 +133,7 @@ This leads to some interesting usage compared to a "pure, classical, boolean-onl
alert(x); // undefined, because (x = 1) not evaluated
```
If, instead, the first argument is `false`, `OR` evaluates the second one, thus running the assignment:
If, instead, the first argument is `false`, `||` evaluates the second one, thus running the assignment:
```js run no-beautify
let x;

View file

@ -296,7 +296,7 @@ Testing finished after all tests (after)
[edit src="beforeafter" title="Open the example in the sandbox."]
Usually, `beforeEach/afterEach` (`before/each`) are used to perform initialization, zero out counters or do something else between the tests (or test groups).
Usually, `beforeEach/afterEach` (`before/after`) are used to perform initialization, zero out counters or do something else between the tests (or test groups).
````
## Extending the spec