Skip to content

Commit 1044baf

Browse files
Trotttargos
authored andcommitted
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: #21701 Reviewed-By: Anatoli Papirovski <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]>
1 parent 9716793 commit 1044baf

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

doc/api/errors.md

+5-6
Original file line numberDiff line numberDiff line change
@@ -127,12 +127,11 @@ exactly how errors raised by those methods are propagated.
127127
<!--type=misc-->
128128

129129
Most asynchronous methods exposed by the Node.js core API follow an idiomatic
130-
pattern referred to as an _error-first callback_ (sometimes referred to as
131-
a _Node.js style callback_). With this pattern, a callback function is passed
132-
to the method as an argument. When the operation either completes or an error
133-
is raised, the callback function is called with
134-
the `Error` object (if any) passed as the first argument. If no error was
135-
raised, the first argument will be passed as `null`.
130+
pattern referred to as an _error-first callback_. With this pattern, a callback
131+
function is passed to the method as an argument. When the operation either
132+
completes or an error is raised, the callback function is called with the
133+
`Error` object (if any) passed as the first argument. If no error was raised,
134+
the first argument will be passed as `null`.
136135

137136
```js
138137
const fs = require('fs');

0 commit comments

Comments
 (0)