anchor.diff:  
   ## <a id='push'></a>Step 5: Push the Application ##
   
  -The following transcript was generated when joeclouduser deployed a Sinatra application called `my-app`:
  +The minimal command for deploying an application without a manifest is:
  +
  +<pre class="terminal">
  +cf push <appname>
  +</pre>
  +
  +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.
  +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 and 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
  
positive.code: To see the environment variables that you have set using the `cf set-env` command:
  
  <pre class="terminal">
    cf env appname
  </pre>
  
  To see the variables in the container environment:
  
  <pre class="terminal">
    cf files appname logs/env.log
  </pre>
  
  ### <a id='logs'></a>Logs ###
  
negative.code: To check the health and status of your application, use:
  
  <pre class="terminal">
  cf app <appname>
  </pre>
  
  For example:
  
  <pre class="terminal">
  $ cf app my-app
  Showing health and status for app my-app in org joeclouduser-org / space development as joeclouduser@<%=vars.app_domain%>...
  OK
  
  