anchor.diff:  
   * **Name**: You can use any series of alpha-numeric characters, without spaces,
   as the name of your application.
  -* **Instances**: Generally speaking, the more instances you run, the less downtime
  -your application is likely to have.
  +* **Instances**: Generally speaking, the more instances you run, the less
  +downtime your application is likely to have.
   If your application is still in development, running a single instance makes it
   easier to troubleshoot.
   For any production application, you should run a minimum of two instances.
  
positive.code: 
   `cf push <appname>`
  
  If you provide the application name in a manifest, you can reduce the command even further, to `cf push`.
  See [Deploying with Application Manifests](./manifest.html).
  
  Since all you have provided is the name of your application, `cf push` sets number of instances, amount of memory,
  and other attributes of your application to reasonable defaults.
  You can also use command-line options to specify these and additional attributes.
  The transcript below, generated when joeclouduser deployed a Sinatra application called `my-app`, shows how `cf` assigns
  default values to application when given a minimal push command.
  
  **Note**: For your own apps, avoid generic names like `my-app`, because a route containing a generic host like `my-app` is
  unlikely to be unique. Deployment fails unless the application has a globally unique route.
  
  <pre class="terminal">
  	$ cf push my-app
  
negative.code: To see the variables in the container environment:
  
    `cf files <appname> logs/env.log`
  
  ### <a id='logs'></a>Logs ###
  
  To see recent log entries:
  