From 3e0c4176eff085498b813f8ba1732d7ed6ee44f8 Mon Sep 17 00:00:00 2001
From: PoziWorld <5961162+PoziWorld@users.noreply.github.com>
Date: Wed, 13 Feb 2019 01:16:33 -0800
Subject: [PATCH] =?UTF-8?q?Docs:=20Fix=20grammar=20in=20=E2=80=9Cthere?=
 =?UTF-8?q?=E2=80=99s=20nothing=20prevent=20you=E2=80=9D=20(#11385)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Changed
“For example, there’s nothing prevent you from writing:”
to
“For example, there’s nothing preventing you from writing:”
---
 docs/rules/no-shadow-restricted-names.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/rules/no-shadow-restricted-names.md b/docs/rules/no-shadow-restricted-names.md
index 9dfc0371906..890353da787 100644
--- a/docs/rules/no-shadow-restricted-names.md
+++ b/docs/rules/no-shadow-restricted-names.md
@@ -1,6 +1,6 @@
 # Disallow Shadowing of Restricted Names (no-shadow-restricted-names)
 
-ES5 §15.1.1 Value Properties of the Global Object (`NaN`, `Infinity`, `undefined`) as well as strict mode restricted identifiers `eval` and `arguments` are considered to be restricted names in JavaScript. Defining them to mean something else can have unintended consequences and confuse others reading the code. For example, there's nothing prevent you from writing:
+ES5 §15.1.1 Value Properties of the Global Object (`NaN`, `Infinity`, `undefined`) as well as strict mode restricted identifiers `eval` and `arguments` are considered to be restricted names in JavaScript. Defining them to mean something else can have unintended consequences and confuse others reading the code. For example, there's nothing preventing you from writing:
 
 ```js
 var undefined = "foo";