fixed code example to meet the standard. `listingId` changed to `listingID`
See - Naming Conventions: Acronyms and initialisms should always be all capitalized, or all lowercased.
Also update code samples to highlight ways in which ES6
currently mishandles code when relying on Automatic Semicolon
Insertion
Revise hyperlink and example
- Use more up-to-date TC39 reference page on github.io
- wrap returnless function with side-effects in curly braces
also, clean up punctuation on a long comment line
Always use single-quoted strings
Except for when the string needs to be double-quoted because the string contains apostrophes
Update second example to incorporate IIFE
An IIFE is a more realistic example of code that developers may encounter which would raise an exception when relying completely upon ASI
It came from the special characters "M-BM-":
```
diff README.md README.md.new | cat -A
651c651$
< const foo = function uniqueMoreDescriptiveLexicalFoo() {$
---$
> M-BM- M-BM- const short = function longUniqueMoreDescriptiveLexicalFoo() {$
```
Requiring operators at the beginning of the line makes code more readable. When operators are on the left hand side they mirror the syntax of method chaining and it is easy to see the build of logic in a statement. This also updates the readme and fixes a style violation as a result of adding this rule in eslint-config-airbnb/test/test-base.js and eslint-config-airbnb-base/test/test-base.js.
Remove link to polish translation as it's outdated ( last commit from 2-3 years ago ).
For example in polish translation you can read that you should use one "var" keyword to declare your vars.
example:
```js
// źle ( bad )
var items = getItems();
var goSportsTeam = true;
var dragonball = 'z';
// dobrze ( good )
var items = getItems(),
goSportsTeam = true,
dragonball = 'z';
```
There were links to eslint rules in a style that didn't match the style of the rest of the document. Specifically, most links in the document use the following style: "eslint: ['no-unneeded-ternary']", but there were badly styled links that looks like this: "eslint rule: ['no-unneeded-ternary']." Additionally, the badly styled links were on their own line, whereas all the other links are not placed on their own line.
