anchor.diff:  To demonstrate Habitat code residing in the same repo as your source code, you are going to clone a simple Node.js application with a `habitat` subdirectory already created for you. Then you will modify the plan and do a test build to verify you have the basic process working correctly. By having the Habitat plan live in the same directory as your source code, the Habitat package for your application can be built right alongside your source code for testing and deployment purposes.
   
   ## Clone the project
  -The Node.js application in this tutorial is a simple web app that displays a message to anyone who connects to the application. You can configure both the listening port and the message. 
  +The Node.js application in this tutorial is a simple web app that displays a message to anyone who connects to the application. You can configure both the listening port and the message.
   
  -1. Clone the habitat-example-plans repo onto your local machine. In this example, a directory called `habitat-example-plans` will be created in the `$HOME` directory. 
  +1. Clone the habitat-example-plans repo onto your local machine. In this example, a directory called `habitat-example-plans` will be created in the `$HOME` directory.
   
          cd ~
          git clone https://github.com/habitat-sh/habitat-example-plans
  
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:
  
  