Skip to content

Commit

Permalink
doc: remove "considered" in errors.md
Browse files Browse the repository at this point in the history
"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]>
  • Loading branch information
Trott authored and MylesBorins committed Jul 16, 2020
1 parent e33c09c commit 7fc56eb
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions doc/api/errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -562,8 +562,7 @@ program. For a comprehensive list, see the [`errno`(3) man page][].
* Extends {errors.Error}

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

```js
require('url').parse(() => { });
Expand Down

0 comments on commit 7fc56eb

Please sign in to comment.