Merge pull request #2404 from MikeMcC399/npm-branding

docs: correct npm branding - use lower case

Author: nschonni

CONTRIBUTING.md

@@ -17,7 +17,7 @@ the Node.js TSC as final arbiter.
 
 New **Node.js** releases are released as soon as possible.
 
-New **NPM** releases are not tracked. We simply use the NPM version bundled in the corresponding Node.js release.
+New **npm** releases are not tracked. We simply use the npm version bundled in the corresponding Node.js release.
 
 **Yarn** is updated to the latest version only when there is a new Node.js SemVer PATCH release (unless Yarn has received a security update), and it's updated only in the branch with the new release, preferably in the same PR. The `update.sh` script does this automatically when invoked with a specific branch, e.g. `./update.sh 6.10`.
 

README.md

@@ -19,7 +19,7 @@ The official Node.js docker image, made with love by the node community.
   - [Verbosity](#verbosity)
     - [Dockerfile](#dockerfile)
     - [Docker Run](#docker-run)
-    - [NPM run](#npm-run)
+    - [npm run](#npm-run)
 - [Image Variants](#image-variants)
   - [`node:<version>`](#nodeversion)
   - [`node:alpine`](#nodealpine)
@@ -135,7 +135,7 @@ override `NPM_CONFIG_LOGLEVEL`.
 $ docker run -e NPM_CONFIG_LOGLEVEL=info node ...
 ```
 
-#### NPM run
+#### npm run
 
 If you are running npm commands, you can use `--loglevel` to control the
 verbosity of the output.