From 73f5ea9bd95d688ebdce729741ec30646c6c413a Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Fri, 4 May 2018 10:05:44 -0700 Subject: [PATCH] doc: fix minor typographical error in DEP0079 text 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.) PR-URL: https://github.com/nodejs/node/pull/20519 Reviewed-By: Vse Mozhet Byt Reviewed-By: Refael Ackermann Reviewed-By: Luigi Pinca Reviewed-By: Ruben Bridgewater Reviewed-By: James M Snell Reviewed-By: Trivikram Kamat --- doc/api/deprecations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md index de7c2f2a2ef17c..b055f81a05c504 100644 --- a/doc/api/deprecations.md +++ b/doc/api/deprecations.md @@ -722,7 +722,7 @@ Type: Runtime Using a property named `inspect` on an object to specify a custom inspection function for [`util.inspect()`][] is deprecated. Use [`util.inspect.custom`][] -instead. For backwards compatibility with Node.js prior to version 6.4.0, both +instead. For backward compatibility with Node.js prior to version 6.4.0, both may be specified.