From 16275b89c9dc472f2dfb4170cc8ff6d403778336 Mon Sep 17 00:00:00 2001 From: Flo Edelmann Date: Fri, 18 Dec 2020 15:27:55 +0100 Subject: [PATCH] Fix link in `new-for-builtins` rule documentation (#939) * Fix link in `new-for-builtins` rule documentation * Fix typo --- docs/rules/new-for-builtins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rules/new-for-builtins.md b/docs/rules/new-for-builtins.md index f17ae84b4d..1ba48b8fe4 100644 --- a/docs/rules/new-for-builtins.md +++ b/docs/rules/new-for-builtins.md @@ -39,7 +39,7 @@ Disallows the use of `new` for following builtins. > These should not use `new` as that would create object wrappers for the primitive values, which is not what you want. However, without `new` they can be useful for coercing a value to that type. -This rule is fixable, except `new String()`, `new Number()`, and `new Boolean()`, [they returns wrapped object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String#String_primitives_and_String_objects#String_primitives_and_String_objects). +This rule is fixable, except `new String()`, `new Number()`, and `new Boolean()`, [they return wrapped object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String#String_primitives_and_String_objects). ## Fail