anchor.diff:  
          cd ~/habitat-example-plans/mytutorialapp
   
  -The `/source` directory contains three files that comprise the Node.js application: `server.js`, `package.json`, and `config.json`. 
  +The `/source` directory contains three files that comprise the Node.js application: `server.js`, `package.json`, and `config.json`.
   
  -The `server.js` file is the main file in our web app. It uses the [nconf module](https://github.com/indexzero/nconf) to retrieve the `message` and `port` configuration values that are set in the `config/config.json` file. 
  +The `server.js` file is the main file in our web app. It uses the [nconf module](https://github.com/indexzero/nconf) to retrieve the `message` and `port` configuration values that are set in the `config/config.json` file.
   
  -The `config.json` file is the default configuration file that you would use if this was an existing application running on a VM or in a container. When you create and configure your package, you will create a templatized version of this file that will be used when the service starts up. 
  +The `config.json` file is the default configuration file that you would use if this was an existing application running on a VM or in a container. When you create and configure your package, you will create a templatized version of this file that will be used when the service starts up.
   
   And finally, because we are using npm to start up our Node.js web app, the npm binary looks for a `package.json` file to describe the Node.js app project and its dependencies.
   
  
positive.code:        pkg_version=0.2.0
         pkg_maintainer="The Habitat Maintainers <humans@habitat.sh>"
         pkg_license=()
         pkg_deps=()
         pkg_expose=()
  
  
negative.code: > Note: The habitat-example-plans repo also contains a `mytutorialapp_finished` directory that you can reference at any time. It also contains an alternative `plan.sh` file that downloads the Node.js application source from a tarball instead of a local directory to show you how you would need to alter your `plan.sh` file in that scenario.
  
  ## Start with the basics
  Now that you have cloned the `habitat-example-plans` repo and understood its structure, it is time to define the plan. At a bare minimum, a plan must have a `plan.sh` at the root of the directory. This file specifies where the source code or binary is, how it should be built by the `hab-pkg-build` command, and how the supervisor should start it at runtime.
  
  In your terminal window, do the following:
  
  