anchor.diff:  * `--random-route` to create a URL that includes the app name and random words
   * `cf help push` to view other options for this command
   
  -If you want to view log activity while the app deploys, launch a new terminal window and run `cf logs [APP-NAME]`.
  +If you want to view log activity while the app deploys, launch a new terminal window and run `cf logs APP-NAME`.
   
   Once your app deploys, browse to your app URL. Search for the `urls` field in the `App started` block in the output of the `cf push` command. Use the URL to access your app online.
   
   <p class="tip"><strong>Sample App Step</strong><br />
   1. Change to the <code>app</code>directory, and run <code>./grailsw war</code> to build the app.
   <br />
  -2. Run <code>cf push pong_matcher_grails -n [HOST_NAME]</code> to push the app.
  +2. Run <code>cf push pong_matcher_grails -n HOST_NAME</code> to push the app.
   <br /><br />
   Example: <code>cf push pong_matcher_grails -n my-grails-app</code>
   </p>
  
positive.code: 
  You’ve deployed an app to <%=vars.product_short%>!
  
  Use the `cf` <%=vars.dev_console_2%> to review information and administer your app and your <%=vars.product_short%> account. For example, you can edit the `manifest.yml` to increase the number of app instances from 1 to 3, and redeploy the app with a new app name and host name.
  
  See the [Manage Your Application with the cf CLI](#cli-manage) section for more information. <%=vars.dev_console_4%>
  
  
negative.code: 
  Example Procfile:
  <pre class="code">
  web: build/install/MY-PROJECT-NAME/bin/MY-PROJECT-NAME]
  </pre>
  
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The <code>pong_matcher_grails</code> app does not require a Procfile.</p>
  