From f7a9ead61ad3965d78cfe6ab6c7330fb4aa14b0d Mon Sep 17 00:00:00 2001 From: ralomach Date: Fri, 26 Apr 2019 11:48:43 -0300 Subject: [PATCH] Update 6-explaining-globs.md I was reading the documentation and maybe found 2 typos, refering to the "scripts" folder as "script", when all the examples have "scripts". --- 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.