Skip to content

Commit 1d25e70

Browse files
Trottaddaleax
authored andcommitted
doc: remove "considered" in errors.md
"would be considered a `TypeError`" -> "would be a `TypeError`". Using "considered" introduces unnecessary ambiguity. Is is not actually a TypeError but merely "considered" one? Why is that? We don't say. Simplify to "is a TypeError". PR-URL: #34152 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Christian Clauss <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]> Reviewed-By: Vladimir de Turckheim <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
1 parent f6dff0a commit 1d25e70

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

doc/api/errors.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -560,8 +560,7 @@ program. For a comprehensive list, see the [`errno`(3) man page][].
560560
* Extends {errors.Error}
561561

562562
Indicates that a provided argument is not an allowable type. For example,
563-
passing a function to a parameter which expects a string would be considered
564-
a `TypeError`.
563+
passing a function to a parameter which expects a string would be a `TypeError`.
565564

566565
```js
567566
require('url').parse(() => { });

0 commit comments

Comments
 (0)