Fix minor punctuation errors

(1) BEFORE: Never name a parameter `arguments`, this will take precedence over the `arguments` object.
AFTER: Never name a parameter `arguments`. This will take precedence over the `arguments` object.

(2) BEFORE: Variable declarations get hoisted to the top of their scope, their assignment does not.
AFTER:
Variable declarations get hoisted to the top of their scope, but their assignment does not.

(3) BEFORE: for multiline comments
AFTER: for multi-line comments

(4)BEFORE: It’s okay to write a custom toString() method, just make sure
AFTER: It's okay to write a custom toString() method. Just make sure
This commit is contained in:
Sunshine Yin
2015-04-05 12:57:01 -07:00
parent 520b6d658f
commit 6cda67e2f5

View File

@@ -301,7 +301,7 @@
}
```
- Never name a parameter `arguments`, this will take precedence over the `arguments` object that is given to every function scope.
- Never name a parameter `arguments`. This will take precedence over the `arguments` object that is given to every function scope.
```javascript
// bad
@@ -475,7 +475,7 @@
## Hoisting
- Variable declarations get hoisted to the top of their scope, their assignment does not.
- Variable declarations get hoisted to the top of their scope, but their assignment does not.
```javascript
// we know this wouldn't work (assuming there
@@ -665,7 +665,7 @@
## Comments
- Use `/** ... */` for multiline comments. Include a description, specify types and values for all parameters and return values.
- Use `/** ... */` for multi-line comments. Include a description, specify types and values for all parameters and return values.
```javascript
// bad