From 465a3b0c628b925da35f415e00e61e88d21928e2 Mon Sep 17 00:00:00 2001
From: Dan Dascalescu <ddascalescu+github@gmail.com>
Date: Sat, 20 Jan 2018 06:53:20 -0800
Subject: [PATCH 1/3] Mention the `globals` key

---
 docs/rules/no-undef.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/rules/no-undef.md b/docs/rules/no-undef.md
index 4b21f2c05d9..8250fbeec0b 100644
--- a/docs/rules/no-undef.md
+++ b/docs/rules/no-undef.md
@@ -1,6 +1,6 @@
 # Disallow Undeclared Variables (no-undef)
 
-This rule can help you locate potential ReferenceErrors resulting from misspellings of variable and parameter names, or accidental implicit globals (for example, from forgetting the `var` keyword in a `for` loop initializer).
+This rule can help you locate potential ReferenceErrors resulting from misspellings of variable and parameter names, or accidental implicit globals (for example, from forgetting the `var` keyword in a `for` loop initializer). If you use specific globals that are defined in a different file (e.g. imported via an HTML `<script>` tag), you can specify them in the [`globals` key in the configuration file](https://eslint.org/docs/user-guide/configuring#specifying-globals).
 
 ## Rule Details
 

From c6d401e0c9dc87980be0301f846c4f85d9d757aa Mon Sep 17 00:00:00 2001
From: Dan Dascalescu <ddascalescu+github@gmail.com>
Date: Sat, 20 Jan 2018 15:26:46 -0800
Subject: [PATCH 2/3] Docs: mention specifying globals

---
 docs/rules/no-undef.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/rules/no-undef.md b/docs/rules/no-undef.md
index 8250fbeec0b..96941f818e1 100644
--- a/docs/rules/no-undef.md
+++ b/docs/rules/no-undef.md
@@ -1,6 +1,6 @@
 # Disallow Undeclared Variables (no-undef)
 
-This rule can help you locate potential ReferenceErrors resulting from misspellings of variable and parameter names, or accidental implicit globals (for example, from forgetting the `var` keyword in a `for` loop initializer). If you use specific globals that are defined in a different file (e.g. imported via an HTML `<script>` tag), you can specify them in the [`globals` key in the configuration file](https://eslint.org/docs/user-guide/configuring#specifying-globals).
+This rule can help you locate potential ReferenceErrors resulting from misspellings of variable and parameter names, or accidental implicit globals (for example, from forgetting the `var` keyword in a `for` loop initializer). If you intentionally use globals that are defined elsewhere, you can specify them in the [`globals` key in the configuration file](https://eslint.org/docs/user-guide/configuring#specifying-globals).
 
 ## Rule Details
 

From b43ad392369ecca90562a8828ea66f2df76fbfc5 Mon Sep 17 00:00:00 2001
From: Dan Dascalescu <ddascalescu+github@gmail.com>
Date: Sat, 20 Jan 2018 16:07:12 -0800
Subject: [PATCH 3/3] Docs: mention the globals key in the no-undef Rule
 Details section

---
 docs/rules/no-undef.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/rules/no-undef.md b/docs/rules/no-undef.md
index 96941f818e1..49a149fde77 100644
--- a/docs/rules/no-undef.md
+++ b/docs/rules/no-undef.md
@@ -1,10 +1,10 @@
 # Disallow Undeclared Variables (no-undef)
 
-This rule can help you locate potential ReferenceErrors resulting from misspellings of variable and parameter names, or accidental implicit globals (for example, from forgetting the `var` keyword in a `for` loop initializer). If you intentionally use globals that are defined elsewhere, you can specify them in the [`globals` key in the configuration file](https://eslint.org/docs/user-guide/configuring#specifying-globals).
+This rule can help you locate potential ReferenceErrors resulting from misspellings of variable and parameter names, or accidental implicit globals (for example, from forgetting the `var` keyword in a `for` loop initializer).
 
 ## Rule Details
 
-Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a `/*global ...*/` comment.
+Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a `/*global ...*/` comment, or specified in the [`globals` key in the configuration file](https://eslint.org/docs/user-guide/configuring#specifying-globals). A common use case for these is if you intentionally use globals that are defined elsewhere (e.g. in a script sourced from HTML).
 
 Examples of **incorrect** code for this rule: