anchor.diff:  
   ## <a id='npm_version'></a>Specify an npm Version##
   
  -Set `engines.npm in `package.json` to the semver range or specific version of npm you are using:
  +Set `engines.npm` in `package.json` to the semver range or specific version of npm you are using:
   
   ```
   "engines": {
  
positive.code: 
  ## <a id='pushing_apps'></a>Push Node.js Apps ##
  
  This buildpack is used automatically if there is a `package.json` file in the root directory of your project.
  
  If your Cloud Foundry deployment does not have the Node.js buildpack installed or the installed version is out of date, you can use the latest version with the command:
  ```bash
  cf push my_app -b https://github.com/cloudfoundry/buildpack-nodejs.git
  ```
  
  For more detailed information on deploying Node.js apps see the following topics:
  
  * <a href="./node-tips.html" class="subnav">Tips for Node.js Developers</a>
  * <a href="./node-environment.html" class="subnav">Environment Variables Defined by the Node Buildpack</a>
  
negative.code: 
  If you do not specify an npm version, your app uses the [default npm](https://nodejs.org/en/download/releases/) packaged with your app's Node.js version.
  
  If your environment cannot connect to the Internet and you specified a non-supported version of npm, the buildpack fails to download npm and you see the following error message:
  
  <pre class='terminal'>
  $   We're unable to download the version of npm you've provided (...).
  