fix NPM -> npm (#25355)

dictionary.txt

@@ -1343,7 +1343,7 @@ Novela
 Novia
 Novikov
 npm
-NPM
+*NPM
 npm-check
 npm-force-resolutions
 npx
@@ -2187,4 +2187,4 @@ Zuri
 складних
 создать
 створення
-створюємо
+створюємо

docs/blog/2017-02-21-1-0-progress-update-where-came-from-where-going/index.md

@@ -23,7 +23,7 @@ This framework would have to be:
 - **JavaScript-driven**, the web is huge and intensely competitive. Sites that
   win are fast and richly interactive. Your framework must make it trivial to
   use advanced JavaScript.
-- **team ready**, use industry standard collaboration tools like NPM, Git, and
+- **team ready**, use industry standard collaboration tools like npm, Git, and
   continuous deployment, so your team is always on the same page and shipping
   new features is easy.
 - **modular**, allows for cleanly separated features so fixing bugs and adding
@@ -205,8 +205,8 @@ The plugin system will let you hook into lifecycle APIs from events during the
 bootstrap and build processes and in the browser.
 
 There are a [number of official Gatsby plugins](/docs/plugins/) already
-built—all distributed as separate NPM packages. It'll be easy to create your own
-plugins for internal projects and as open source projects published on NPM.
+built—all distributed as separate npm packages. It'll be easy to create your own
+plugins for internal projects and as open source projects published on npm.
 
 Plugins can:
 
@@ -226,7 +226,7 @@ Themes will also be able to _compose_ other themes. So a large organization
 could have a standard "base" theme and then individual departments could extend
 the base theme to meet their specific requirements.
 
-Themes (like plugins) will be published on NPM. So soon, starting a new Gatsby
+Themes (like plugins) will be published on npm. So soon, starting a new Gatsby
 blog will be as simple as:
 
 ```shell

docs/blog/2017-09-21-community-roundup-1/index.md

@@ -14,7 +14,7 @@ It's been a wild 77 days since Gatsby 1.0.0 was released into the world on July
 By the numbers we've seen:
 
 - 3150 new GitHub stars
-- ~380,000 new NPM downloads
+- ~380,000 new npm downloads
 - 110 new contributors (hey y'all!)
 - ~400 merged PRs
 - dozens of new plugins

docs/blog/2017-10-16-making-website-building-fun/index.md

@@ -13,7 +13,7 @@ I decided to port to React [headroom.js](http://wicky.nillia.ms/headroom.js/)—
 JavaScript library that shows & hides headers as you scroll up & down a site.
 
 After a day or two of working through the niceties of writing a React component
-and publishing it to NPM, I started writing the documentation and realized…
+and publishing it to npm, I started writing the documentation and realized…
 there was almost nothing to write.
 
 Using [react-headroom](https://github.com/KyleAMathews/react-headroom) is so
@@ -216,7 +216,7 @@ export default function Page({ data }) {
 }
 ```
 
-So this is all very nice and it's far better to be able to use this from NPM vs.
+So this is all very nice and it's far better to be able to use this from npm vs.
 implementing it yourself or cobbling together several standalone libraries.
 
 But if this was all gatsby-image did, it'd be a nice new component to have

docs/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/index.md

@@ -130,7 +130,7 @@ for grabbing content as well, but how you deal with actually pulling it into
 your React components/pages with GraphQL is beautiful.
 
 After you install the `gatsby-source-contentful`
-[plugin](/packages/gatsby-source-contentful/) with NPM
+[plugin](/packages/gatsby-source-contentful/) with npm
 and add your Contentful API credentials to the gatsby-config file, the fun
 begins.
 

docs/blog/2018-05-24-launching-new-gatsby-company/index.md

@@ -41,7 +41,7 @@ During my years building Drupal sites, I’d occasionally cast envious eyes at a
 
 Then, in late 2010, the initial version of Backbone.js was released. I started playing with it and got super excited because things finally clicked for me: this was how to build rich, real-time JavaScript apps. The next year, I started my first full-time software development job at [Pantheon.io](https://pantheon.io/) and had a fantastic time building the Pantheon dashboard with Backbone.js to support Drupal & WordPress developers. I attended Backbone.js meetups and the first few Backbone.js conferences. Developer excitement online and at meetups was palpable. We could all feel that the world of web applications was starting to change dramatically.
 
-Node.js, then only a couple of years old, was gaining traction fast. For the first time, NPM enabled the easy sharing of JavaScript libraries. Consequently, the number of libraries exploded. With a server runtime and ecosystem developing around JS, more and more web development tools started being written in JavaScript.
+Node.js, then only a couple of years old, was gaining traction fast. For the first time, npm enabled the easy sharing of JavaScript libraries. Consequently, the number of libraries exploded. With a server runtime and ecosystem developing around JS, more and more web development tools started being written in JavaScript.
 
 The fast paced world of the web was reinventing itself again.
 

docs/blog/2018-07-07-the-gatsby-plugin-page-creator/index.md

@@ -78,7 +78,7 @@ having to give up on the most powerful out-of-the-box feature.
 
 ## Community reception
 
-![NPM stats for gatsby plugin page creator](npm-stats.png)
+![npm stats for gatsby plugin page creator](npm-stats.png)
 
 This plugin has by far been the most impactful open source contribution I have made
 to date. As of writing, the newly published Gatsby plugin has been

docs/blog/2019-02-14-behind-the-scenes-q-and-a/index.md

@@ -91,7 +91,7 @@ To watch the full recorded webinar, [register here](https://www.gatsbyjs.com/beh
 **Answer:** We don't really have an official opinion--we want you to build apps however you prefer! That being said, I quite like CSS in JS (particularly emotion). I did a little podcast with Chris Coyier if you're interested--[CSS-in-JS Podcast on CSS Tricks](https://css-tricks.com/video-screencasts/168-css-in-js/)
 
 **Question:** How about best practices with Styles and Web Fonts?
-**Answer:** Re: Styles, I'd recommend using something like CSS Modules (enabled by default!) or a CSS in JS solution if you're into that. We're not opinionated and want to enable everyone to build performant sites, by default! As far as web fonts, depends! You could use gatsby-plugin-typography and load google fonts if that's your thing. [Typefaces](https://github.com/kyleamathews/typefaces) lets you add open source fonts from NPM packages.
+**Answer:** Re: Styles, I'd recommend using something like CSS Modules (enabled by default!) or a CSS in JS solution if you're into that. We're not opinionated and want to enable everyone to build performant sites, by default! As far as web fonts, depends! You could use gatsby-plugin-typography and load google fonts if that's your thing. [Typefaces](https://github.com/kyleamathews/typefaces) lets you add open source fonts from npm packages.
 
 ### Content Management Systems (CMS)
 

docs/blog/2019-09-26-announcing-gatsby-15m-series-a-funding-round/index.md

@@ -12,7 +12,7 @@ Gatsby is a free and open-source web framework based on React that helps develop
 
 ## Why the excitement and growth?
 
-The answer is simple. Gatsby was founded around a big idea, and that idea is starting to go mainstream. We believe that the basic architecture of websites is being reinvented. The dominant web architecture, the LAMP stack, was founded at the dawn of the web before paradigm-shifting technologies were invented, like virtual machines, AWS, smartphones, Git, Node/NPM, React, and Serverless—elements of modern engineering we now take for granted.
+The answer is simple. Gatsby was founded around a big idea, and that idea is starting to go mainstream. We believe that the basic architecture of websites is being reinvented. The dominant web architecture, the LAMP stack, was founded at the dawn of the web before paradigm-shifting technologies were invented, like virtual machines, AWS, smartphones, Git, Node/npm, React, and Serverless—elements of modern engineering we now take for granted.
 
 With Gatsby, we’re reinventing website technology so people can create sites that are lightning fast, incredibly secure, and stable. Web developers can now take advantage of the most productive and powerful modern engineering technologies and practices including Git, React, GraphQL, and continuous deployment.
 

docs/blog/2020-03-11-netlify-functions-and-gatsby-cloud/index.md

@@ -136,7 +136,7 @@ Let's say we have two functions, `track-hit.js` and `like-content.js`. And let's
             └── some-other-faunadb-dependency
 ```
 
-Because the folks at Netlify are wonderful wizards, they extracted the module that prepares functions and published it on NPM as `@netlify/zip-it-and-ship-it`. This means we can leverage this critical part of Netlify's build process even though we aren't building on Netlify.
+Because the folks at Netlify are wonderful wizards, they extracted the module that prepares functions and published it on npm as `@netlify/zip-it-and-ship-it`. This means we can leverage this critical part of Netlify's build process even though we aren't building on Netlify.
 
 ### Cold and warm builds
 

docs/blog/2020-04-15-announcing-gatsby-recipes/index.md

@@ -9,7 +9,7 @@ I'm excited to announce Gatsby Recipes, a new tool to automate common site build
 
 Recipes are run from the CLI and automate common tasks like creating pages and layouts, installing and setting up plugins, adding a blog to a site, setting up TypeScript, and many more.
 
-Gatsby ships with a number of default recipes and it's easy to create your own for use on your sites. Recipes allow you to install NPM packages, add Gatsby plugins, generate pages and other code. Recipes are written using Markdown and React components.
+Gatsby ships with a number of default recipes and it's easy to create your own for use on your sites. Recipes allow you to install npm packages, add Gatsby plugins, generate pages and other code. Recipes are written using Markdown and React components.
 
 To kickstart the new era of Gatsby Recipes, we’ve created 11 official recipes with more on the way! These include recipes for adding TypeScript, Theme UI, Sass, Cypress, and setting up useful techniques like animated page transitions, and persistent layout components.
 
@@ -51,7 +51,7 @@ We're very excited to ship Recipes. We care a lot about the Gatsby developer exp
 
 ### What does a recipe look like?
 
-Recipes are written in MDX, so a combination of Markdown and React components. The React components instruct Gatsby Recipes to make sure things exist like files or NPM packages e.g. Emotion.
+Recipes are written in MDX, so a combination of Markdown and React components. The React components instruct Gatsby Recipes to make sure things exist like files or npm packages e.g. Emotion.
 
 A full recipe for adding the CSS-in-JS library Emotion looks like the following:
 

docs/blog/2020-06-23-Reconfiguring-Gatsby-Days/index.md

@@ -57,7 +57,7 @@ https://www.youtube.com/watch?v=B7D_B2HTbko
 
 **Kyle Mathews, Co-founder and CEO of Gatsby**
 
-Let’s take a look at the coming Admin version of Gatsby Recipes and how we can create a brand new blog from scratch in less than two minutes with no coding required. We are using the Contentful Blog Recipe for, you guessed it, setting up our new blog on Contentful. Ready? First step: The Recipe informs you of the changes it will make to your site on your behalf, installing the necessary NPM packages and plugins, like `gatsby-source-contentful`, to pull data from your new Contentful space, which it also nicely and automatically creates for you. The first, and really only, thing you need to do is enter some information, like what you want to name your blog, plus the title and some content for your first post. (It’s ok for these to be placeholders for now, you can edit them easily once the blog is set up on Contentful). You enter these into text boxes, which behind the scenes is setting up the new Contentful space and specifying the `BlogPost`content type. Gatsby uses source plugins to automatically and very efficiently power your site with data from different sources, and using Admin means zero configuration work from the user is required.
+Let’s take a look at the coming Admin version of Gatsby Recipes and how we can create a brand new blog from scratch in less than two minutes with no coding required. We are using the Contentful Blog Recipe for, you guessed it, setting up our new blog on Contentful. Ready? First step: The Recipe informs you of the changes it will make to your site on your behalf, installing the necessary npm packages and plugins, like `gatsby-source-contentful`, to pull data from your new Contentful space, which it also nicely and automatically creates for you. The first, and really only, thing you need to do is enter some information, like what you want to name your blog, plus the title and some content for your first post. (It’s ok for these to be placeholders for now, you can edit them easily once the blog is set up on Contentful). You enter these into text boxes, which behind the scenes is setting up the new Contentful space and specifying the `BlogPost`content type. Gatsby uses source plugins to automatically and very efficiently power your site with data from different sources, and using Admin means zero configuration work from the user is required.
 
 Second, hit the “install Recipe” button. A few seconds to install the plugins and create the spaces, and there you go! Head over to Contentful and you will find the blog space that we just created. Click on the “Content model” tab and there’s your brand new blog and your first example blog post. Click on that to start writing/editing (Hello, World!) and view your brand new site. Yes, this took less than two minutes. Yes, it’s that easy.
 

docs/blog/gatsby-v1.md

@@ -36,7 +36,7 @@ In the last year, Gatsby community and usage have exploded. Milestones reached:
   [our chat room on Discord](https://discord.gg/0ZcbPKXt5bVoxkfV)).
 - 10,000 stars on GitHub
 - 1000 followers on Twitter
-- 500,000 NPM downloads (100,000 in the last month!!)
+- 500,000 npm downloads (100,000 in the last month!!)
 
 ![Gatsby npm downloads year over year](./images/gatsby-npm-downloads.png)
 
@@ -97,7 +97,7 @@ during the bootstrap and build processes and in the browser.
 
 There are already many
 [official Gatsby plugins](/docs/plugins/#official-plugins) built—all distributed
-as individual NPM packages. It is easy to create your own plugins for internal
+as individual npm packages. It is easy to create your own plugins for internal
 projects and for contributing back to Gatsby.
 
 Plugins can:

docs/contributing/setting-up-your-local-dev-environment.md

@@ -9,7 +9,7 @@ This page outlines how to get set up to contribute to Gatsby core and its ecosys
 
 ## Using Yarn
 
-Yarn is a package manager for your code, similar to [NPM](https://www.npmjs.com/). While NPM is used to develop Gatsby sites with the CLI, contributing to the Gatsby repo requires Yarn for the following reason: we use Yarn's [workspaces](https://yarnpkg.com/lang/en/docs/workspaces/) feature that comes really handy for monorepos. It allows us to install dependencies from multiple `package.json` files in sub-folders, enabling a faster and lighter installation process.
+Yarn is a package manager for your code, similar to [npm](https://www.npmjs.com/). While npm is used to develop Gatsby sites with the CLI, contributing to the Gatsby repo requires Yarn for the following reason: we use Yarn's [workspaces](https://yarnpkg.com/lang/en/docs/workspaces/) feature that comes really handy for monorepos. It allows us to install dependencies from multiple `package.json` files in sub-folders, enabling a faster and lighter installation process.
 
 ```json:title=package.json
 {

docs/docs/creating-a-transformer-plugin.md

@@ -25,7 +25,7 @@ This loose coupling between the data source and transformer plugins allow Gatsby
 
 ## How do you create a transformer plugin?
 
-Just like a source plugin, a transformer plugin is a normal NPM package. It has a `package.json` file with optional dependencies as well as a `gatsby-node.js` file where you implement Gatsby's Node.js APIs.
+Just like a source plugin, a transformer plugin is a normal npm package. It has a `package.json` file with optional dependencies as well as a `gatsby-node.js` file where you implement Gatsby's Node.js APIs.
 
 `gatsby-transformer-yaml` is transformer plugin that looks for new nodes with a media type of text/YAML (e.g. a `.yaml` file) and creates new YAML child node(s) by parsing the YAML source into JavaScript objects.
 

docs/docs/debugging-html-builds.md

@@ -51,7 +51,7 @@ const module = typeof window !== `undefined` ? require("module") : null
 
 ## Fixing third-party modules
 
-So, the worst has happened and you're using an NPM module that expects `window`
+So, the worst has happened and you're using an npm module that expects `window`
 to be defined. You may be able to file an issue and get the module patched, but
 what to do in the mean time?
 

docs/docs/deploying-to-clodui.md

@@ -22,7 +22,7 @@ Clodui supports the following features to improve your website speed and develop
 
 Follow these steps to deploy your website to Clodui.
 
-1. [Sign up](https://app.clodui.com/auth/signup) to create an account using your email and password.  
+1. [Sign up](https://app.clodui.com/auth/signup) to create an account using your email and password.
    _**Note :** Don't use social login like Google or Facebook to sign up because Clodui CLI doesn't support it yet._
 2. Install the [Clodui CLI]:
    ```shell
@@ -89,7 +89,7 @@ Here Clodui credentials and website id are fetched from the GitHub secret store.
 
 - [Clodui CLI documentation](https://www.clodui.com/docs/clodui-cli/)
 - [Clodui Actions marketplace](https://github.com/marketplace/actions/clodui-actions)
-- [Clodui CLI NPM package](https://www.npmjs.com/package/@clodui/cli)
+- [Clodui CLI npm package](https://www.npmjs.com/package/@clodui/cli)
 
 [clodui]: https://www.clodui.com
 [clodui cli]: https://www.npmjs.com/package/@clodui/cli

docs/docs/environment-variables.md

@@ -65,7 +65,7 @@ MY_ENV_VAR=foo npm run develop
 In Windows it's a little more complex. [Check out this Stack Overflow article for some options](https://stackoverflow.com/questions/1420719/powershell-setting-an-environment-variable-for-a-single-command-only)
 
 Project environment variables that you defined in the `.env.*` files will _NOT_ be immediately available
-in your Node.js scripts. To use those variables, use NPM package [dotenv](https://www.npmjs.com/package/dotenv) to
+in your Node.js scripts. To use those variables, use npm package [dotenv](https://www.npmjs.com/package/dotenv) to
 examine the active `.env.*` file and attach those values.
 `dotenv` is already a dependency of Gatsby, so you can require it in your `gatsby-config.js` or `gatsby-node.js` like this:
 

docs/docs/gatsby-lifecycle-apis.md

@@ -11,7 +11,7 @@ Gatsby's design principles include:
   code.
 - Extracting logic and configuration into [plugins](/docs/plugins/) should be
   trivial and encouraged.
-- Plugins are easy to open source and reuse. They're just NPM packages.
+- Plugins are easy to open source and reuse. They're just npm packages.
 
 ## High level Overview
 

docs/docs/gatsby-on-windows.md

@@ -79,7 +79,7 @@ further instructions and contact the `node-gyp`team on
 
 ## gatsby-plugin-sharp requires Node x64
 
-Some plugins which depend on native NPM dependencies require the Node x64 build of Node.js. If you're struggling to install gatsby-plugin-sharp, try installing Node x64 and removing `node_modules` and running `npm install`.
+Some plugins which depend on native npm dependencies require the Node x64 build of Node.js. If you're struggling to install gatsby-plugin-sharp, try installing Node x64 and removing `node_modules` and running `npm install`.
 
 ## gatsby-plugin-sharp requires libvips
 

docs/docs/glossary.md

@@ -244,7 +244,7 @@ A program that lets you run [JavaScript](#javascript) on your computer. Gatsby i
 
 ### Package
 
-A package usually describes a [JavaScript](#javascript) program that has additional information about how it should be distributed and used, such as its version number. [NPM](#npm) and [Yarn](#yarn) manages and installs the packages your project uses. [Gatsby](#gatsby) itself is a package.
+A package usually describes a [JavaScript](#javascript) program that has additional information about how it should be distributed and used, such as its version number. [npm](#npm) and [Yarn](#yarn) manages and installs the packages your project uses. [Gatsby](#gatsby) itself is a package.
 
 ### Page
 
@@ -376,6 +376,6 @@ A WordPress plugin that adds [GraphQL](#graphql) capabilities to WordPress. It's
 
 ### [Yarn](/docs/glossary/yarn/)
 
-A [package](#package) manager that some prefer to [NPM](#npm). It is also required for [developing Gatsby](/contributing/setting-up-your-local-dev-environment/#using-yarn).
+A [package](#package) manager that some prefer to [npm](#npm). It is also required for [developing Gatsby](/contributing/setting-up-your-local-dev-environment/#using-yarn).
 
 ## Z