From ffd8c74cd51aae2aa1a98bc0b10c0d2b550b1855 Mon Sep 17 00:00:00 2001 From: Bret Ikehara Date: Wed, 26 Oct 2016 09:24:07 -0700 Subject: [PATCH] fix typos --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9749a85..e2f31be 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,7 @@ gulpLoadPlugins({ rename: {}, // a mapping of plugins to rename renameFn: function (name) { ... }, // a function to handle the renaming of plugins (the default works) postRequireTransforms: {}, // see documentation below - maintainScope: true // toggles loadin all npm scopes like non-scoped packages + maintainScope: true // toggles loading all npm scopes like non-scoped packages }); ``` @@ -137,7 +137,7 @@ Note that if you specify the `renameFn` options with your own custom rename func ## npm Scopes -`gulp-load-plugins` comes with [npm scope](https://docs.npmjs.com/misc/scope) support. By default, the scoped plugins are accessible through an object on `plugins` that represents the scope. When `maintainScope = false`, the plugins are availble in the top level just like any other non-scoped plugins. +`gulp-load-plugins` comes with [npm scope](https://docs.npmjs.com/misc/scope) support. By default, the scoped plugins are accessible through an object on `plugins` that represents the scope. When `maintainScope = false`, the plugins are available in the top level just like any other non-scoped plugins. For example, if the plugin is `@myco/gulp-test-plugin` then you can access the plugin as shown in the following example: