Skip to content

Commit 7fc56eb

Browse files
TrottMylesBorins
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 <luigipinca@gmail.com> Reviewed-By: Christian Clauss <cclauss@me.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Gerhard Stöbich <deb2001-github@yahoo.de> Reviewed-By: Andrey Pechkurov <apechkurov@gmail.com> Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
1 parent e33c09c commit 7fc56eb

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

doc/api/errors.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -562,8 +562,7 @@ program. For a comprehensive list, see the [`errno`(3) man page][].
562562
* Extends {errors.Error}
563563

564564
Indicates that a provided argument is not an allowable type. For example,
565-
passing a function to a parameter which expects a string would be considered
566-
a `TypeError`.
565+
passing a function to a parameter which expects a string would be a `TypeError`.
567566

568567
```js
569568
require('url').parse(() => { });

0 commit comments

Comments
 (0)