doc: many small fixes to deprecations.md by Trott · Pull Request #20519 · nodejs/node (original) (raw)

@Trott

Make the deprecation message a bit clear and concise.

@Trott

Make the text slightly more concise. Fix awkward verb tense.

@Trott

@Trott

Make deprecation text slightly more concise and direct.

@Trott

Fix a typographical error in deprecation text. Convert run-on sentence to two sentences (one in parentheses).

@Trott

Make deprecation text more concise and direct.

@Trott

Change backwards compatibility to backward compatibility.

(It's confusing because "backwards compatible" is acceptable because "backwards" can be used as an adverb like that. However, as an adjective, as in "backward compatibility", only "backward" will do. Easiest solution: Always use "backward" because it is OK in both cases. This is all compounded by the US vs UK English thing. US English tends to favor "backward", and we standardize on US English, so that's another point in favor of "backward" over "backwards" in this context.)

@Trott

Use "Node.js 6.0.0" instead of "Node.js v6.0.0". (We decided to drop "v" before version numbers to avoid confusion with the V8 JavaScript engine.)

@Trott

@Trott