anchor.diff:  
   Within each package directory is a `spec` file which states:
   
  -* The package name.
  -* The package's dependencies.
  -* The location where BOSH can find the binaries and other files that the package needs at compile time.
  +* The package name
  +* The package's dependencies
  +* The location where BOSH can find the binaries and other files that the package needs at compile time
   
   Use your dependency graph to determine which dependencies belong in each spec.
  -Your personal preferences and style as a developer also play a role here.
  +Developer preferences and style play a role here.
   Consider our example: the spec for Ruby lists `rubygems` and `bundler` as dependencies along
   with Ruby itself.
   Some Ruby developers would do it this way; others would not.
   
  -Remember not to depend on the presence of libraries or other software on the stemcells that
  -BOSH uses to create VMs.
  -This maximizes the portability of your release across different versions of stemcells.
  -
  -To correctly describe binary locations in the `files` block of the spec:
  +To maximize portability of your release across different versions of stemcells,
  +never depend on the presence of libraries or other software on stemcells.
  +
  +To describe binary locations in the `files` block of the spec:
   
   * Find the official site for the binary in question.
   For example, Ruby might be at `http://cache.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p484.tar.gz`.
  
positive.code: `BOSH_INSTALL_TARGET`.
  See how this is done in the example packaging scripts.
  
  Write your packaging scripts now.
  To get started, study the examples.
  
  #### <a id="pkg-script-libyaml"></a> Example libyaml packaging script ####
  
  
negative.code: `<package_name>/**/*` to deep-traverse the directory in `src` where
  the source code will reside.
  
  Update the spec for each package.
  Refer to the example specs below for guidance.
  
  #### <a id="pkg-spec-libyaml"></a> Example libyaml package spec ####
  
  