anchor.diff:  
   This section explains how to describe optional application attributes in manifests. Among the optional attributes, you should notice the differences between symbols, environment variables, and properties.
   
  -### <a id='start-commands'></a>Commands for starting applications ###
  -
  -By default, `cf push` starts an application as if you were running the application at the command line:
  -
  -~~~
  -./some_app.rb
  -~~~
  -
  -This is not appropriate for all applications. For example, some applications require a `bundle exec` command to start properly. When that is the case, use the `command` attribute.
  +### <a id='start-commands'></a>The command attribute ###
  +
  +Depending on your application framework, `cf push` may start your application with a default command.
  +You can use the `command` attribute to set a custom start command.
   
   For example:
   
  
positive.code: 
  You can deploy multiple applications with one `cf push` command by describing them in a single manifest. In doing so, you need to pay extra attention to directory structure and path lines in the manifest.
  
  Suppose you want to deploy two applications, `spark` and `flame`, and you want `cf` to create and start `spark` before `flame`. You accomplish this by listing `spark` first in the manifest.
  
  In this situation there are two sets of bits you want to push. Let’s say that they are `spark.rb` in the `spark` directory and `flame.rb` in the `flame` directory. One level up, the `fireplace` directory contains the `spark` and the `flame` directories along with the `manifest.yml` file. Your plan is to run `cf` from `fireplace`, where you know it can find the manifest.
  
  Now that you have changed the directory structure and manifest location, the standard path line of `path: . ` no longer works. How can you ensure that `cf` finds the bits you want to push?
  
  
negative.code: 
  ### <a id='env-block'></a>Environment variables ###
  
  The `env` block consists of a heading, then one or more environment variable/value pairs. The variables belong to the environment of the container to which the application is deployed on the server.
  
  For example:
  
  