From 01eee530e3a8dc7cabdb5a6870ba6fe2367ec581 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sat, 7 Jul 2018 13:53:24 -0700 Subject: [PATCH] doc: remove _Node.js style callback_ We refer to them only as _error-first callbacks_ in our docs. We don't call them _Node.js style callbacks_ so let's take this opporutnity to keep things a bit more concise PR-URL: https://github.com/nodejs/node/pull/21701 Reviewed-By: Anatoli Papirovski Reviewed-By: Vse Mozhet Byt --- doc/api/errors.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/api/errors.md b/doc/api/errors.md index 1e2730db4f4..46413cd4c47 100644 --- a/doc/api/errors.md +++ b/doc/api/errors.md @@ -127,12 +127,11 @@ exactly how errors raised by those methods are propagated. Most asynchronous methods exposed by the Node.js core API follow an idiomatic -pattern referred to as an _error-first callback_ (sometimes referred to as -a _Node.js style callback_). With this pattern, a callback function is passed -to the method as an argument. When the operation either completes or an error -is raised, the callback function is called with -the `Error` object (if any) passed as the first argument. If no error was -raised, the first argument will be passed as `null`. +pattern referred to as an _error-first callback_. With this pattern, a callback +function is passed to the method as an argument. When the operation either +completes or an error is raised, the callback function is called with the +`Error` object (if any) passed as the first argument. If no error was raised, +the first argument will be passed as `null`. ```js const fs = require('fs');