From 5d81f42f9ddc4aa0a0721057eff8b8e24b65861c Mon Sep 17 00:00:00 2001
From: Rafael <37901937+ralomach@users.noreply.github.com>
Date: Sat, 27 Apr 2019 10:23:25 -0300
Subject: [PATCH] Docs: Fix typo in Explaining Globs (#2326)

---
 docs/getting-started/6-explaining-globs.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/getting-started/6-explaining-globs.md b/docs/getting-started/6-explaining-globs.md
index de524d843..d362c28c5 100644
--- a/docs/getting-started/6-explaining-globs.md
+++ b/docs/getting-started/6-explaining-globs.md
@@ -52,13 +52,13 @@ Here, the glob is appropriately restricted to the `scripts/` directory. It will
 Since globs are matched in array order, a negative glob must follow at least one non-negative glob in an array. The first finds a set of matches, then the negative glob removes a portion of those results. These are most performant when they only include literal characters.
 
 ```js
-['script/**/*.js', '!scripts/vendor/']
+['scripts/**/*.js', '!scripts/vendor/']
 ```
 
 If any non-negative globs follow a negative, nothing will be removed from the later set of matches.
 
 ```js
-['script/**/*.js', '!scripts/vendor/', 'scripts/vendor/react.js']
+['scripts/**/*.js', '!scripts/vendor/', 'scripts/vendor/react.js']
 ```
 
 Negative globs can be used as an alternative for restricting double-star globs.