anchor.diff:    host: nifty
   </pre>
   
  -A minimal manifest requires only an application `name`. 
  -To create a valid minimal manifest, remove the `memory` and `host` properties 
  +A minimal manifest requires only an application `name`.
  +To create a valid minimal manifest, remove the `memory` and `host` properties
   from this example.
   
  -Place your `manifest.yml` in the directory that contains the application files 
  -that you want to push and run `cf push`. 
  -`cf push` searches the current directory for a manifest unless you specify 
  -another path with the `-p` option. 
  +Place your `manifest.yml` in the directory that contains the application files
  +that you want to push and run `cf push`.
  +`cf push` searches the current directory for a manifest unless you specify
  +another path with the `-p` option.
   
   ## <a id='name'></a>Always Provide an Application Name to cf push ##
   
  -`cf push` requires an application name, which you provide either in a manifest 
  +`cf push` requires an application name, which you provide either in a manifest
   or at the command line.
   
  -As described in [How cf push Finds the Manifest](#find-manifest) above, the 
  -command `cf push` works when the `manifest.yml` file is in the current working 
  +As described in [How cf push Finds the Manifest](#find-manifest) above, the
  +command `cf push` works when the `manifest.yml` file is in the current working
   directory.
   
   If you do not use a manifest, the minimal push command looks like this:
   
   <pre class="terminal">
  -cf push my-application-name
  +cf push my-app
   </pre>
   
   <p class="note"><strong>Note</strong>: When you provide an application name at the command line, <code>cf push</code> uses that application name whether or not there is a different application name in the manifest. If the manifest describes multiple applications, you can push a single application by providing its name at the command line; <code>cf</code> does not push the others.
  
positive.code:   ...
    env:
      RAILS_ENV: production
      RACK_ENV: production 
  </pre>
  
  `cf push` deploys the application to a container on the server. The variables belong to the container environment.
  
negative.code: 
  When you push an application for the first time, Cloud Foundry applies default values to any attributes that you do not set in a manifest or `cf push` command line options.
  
  * For example, `cf push my-app` with no manifest might deploy one instance of the app with one gigabyte of memory.
  In this case the default values for instances and memory are "1" and "1G", respectively.
  
  Between one push and another, attribute values can change in other ways.
  