From 7fc56ebd0d01d84b15c5fe7143b2a89779ab13ee Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Tue, 30 Jun 2020 21:48:16 -0700 Subject: [PATCH] doc: remove "considered" in errors.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "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: https://github.com/nodejs/node/pull/34152 Reviewed-By: Luigi Pinca Reviewed-By: Christian Clauss Reviewed-By: Matteo Collina Reviewed-By: Gerhard Stöbich Reviewed-By: Andrey Pechkurov Reviewed-By: Vladimir de Turckheim Reviewed-By: Benjamin Gruenbaum --- doc/api/errors.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/api/errors.md b/doc/api/errors.md index e768c98578e053..3efe6bcd47d712 100644 --- a/doc/api/errors.md +++ b/doc/api/errors.md @@ -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(() => { });