anchor.diff:  
   If this happens, try the following:
   
  -**Find the reason app is failing and modify your code.**
  -Run `cf events APP-NAME` and `cf logs APP-NAME --recent` and look for
  +  * **Find the reason app is failing and modify your code.**
  +    Run `cf events APP-NAME` and `cf logs APP-NAME --recent` and look for
   messages similar to this:
  -
  -  `2014-04-29T17:52:34.00-0700   app.crash          index: 0, reason: CRASHED, exit_description: app instance exited, exit_status: 1`
  -
  -These messages may identify a memory or port issue.
  -If they do, take that as a starting point when you re-examine and fix your
  +  <pre class="terminal">
  +  2014-04-29T17:52:34.00-0700   app.crash          index: 0, reason: CRASHED,
  +  exit\_description: app instance exited, exit\_status: 1
  +  </pre>
  +  These messages may identify a memory or port issue.
  +  If they do, take that as a starting point when you re-examine and fix your
   application code.
   
     * **Make sure your application code uses the `PORT` environment variable.**
   Your application may be failing because it is listening on the wrong port.
   Instead of hard coding the port on which your application listens, use the `PORT` environment variable.
  -
  -For example, this Ruby snippet assigns the port value to the `listen_here`
  +    
  +    For example, this Ruby snippet assigns the port value to the `listen_here`
   variable:
  -
  -  `listen_here = ENV['PORT']`
  -
  -For more examples specific to your application framework, see the
  +     `listen_here = ENV['PORT']`
  +   
  +    For more examples specific to your application framework, see the
   appropriate [buildpacks documentation](../../buildpacks/) for your app's language.
   
     * **Make sure your app adheres to the principles of the
  
positive.code: These texts explain how to prevent situations where your app builds locally but
  fails to build in the cloud.
  
    * **Verify the timeout configuration of your app.** Application health checks use
  a timeout setting when an app starts up for the first time. See [Using Application Health Checks](./healthchecks.html)
  
  ### <a id='out-of-memory'></a>App consumes too much memory, then crashes ###
  
  
negative.code: * You did not successfully create and bind a needed service instance to the app, such as a PostgreSQL or MongoDB service instance. Refer to Step 3: Create and Bind a Service Instance for a RoR Application.
  * You did not successfully create a unique URL for the app. Refer to the troubleshooting tip App Requires Unique URL.
  
  ### <a id='unique_url'></a> App Requires Unique URL ###
  <%=vars.product_short%> requires that each app that you deploy has a unique URL. Otherwise, the new app URL collides with an existing app URL and <%=vars.product_short%> cannot successfully deploy the app. You can resolve this issue by running `cf push` with either of the following flags to create a unique URL:
  
  * `-n` to assign a different HOST name for the app.
  