anchor.diff:  
   You can also bind a service using the <%=vars.dev_console_2%>.
   
  -### <a id='yourapp-step5'></a>Step 5: Log in and Target the API Endpoint   ###
  +### Step 5: Log in and Target the API Endpoint   ###
   Run `cf login -a [API_ENDPOINT]`, enter your login credentials, and select a space and org. The API endpoint is <%=vars.api_endpoint%>.
   
  -<%=vars.gen_GSG%> 
  -
  -
  -### <a id='yourapp-step6'></a>Step 6: (Optional) Configure a Production Server  ###
  +<%=vars.gen_GSG%>
  +
  +
  +### Step 6: (Optional) Configure a Production Server  ###
   
   <%=vars.product_short%> uses the default Ruby web server library WEBrick for Ruby and RoR apps. However, <%=vars.product_short%> can support a more robust production web server, such as Phusion Passenger, Puma, Thin, or Unicorn. To set a different production web server for your app:
   
   1. Modify your app to use the production web server.
  -1. Configure the `web` setting in a Procfile to point to the production web server. 
  +1. Configure the `web` setting in a Procfile to point to the production web server.
   
   When you deploy, `cf push` detects that your app requires the Cloud Foundry Ruby [buildpack](./index.html), and that buildpack uses the modified Procfile to configure your app with the changed production web server settings. For an example of how to configure an application and a Procfile to use a different web server, refer to the [Heroku Deploying Rails Applications with Unicorn](https://devcenter.heroku.com/articles/rails-unicorn) topic.
   
  -### <a id='yourapp-step7'></a>Step 7: Deploy Your Application ###
  +### Step 7: Deploy Your Application ###
   When you deploy your application, `cf push`:
   
    * Creates a URL that is the route to your application. The URL is in the form HOST.DOMAIN, where HOST is the APP_NAME and DOMAIN is specified by your administrator. Your DOMAIN is`<%=vars.app_domain%>`.
  
positive.code: 
  1. Run `bundle install` to update your Gemfile.
  
  ### <a id='yourapp-step2'></a>Step 2: (Optional) Configure Automatically Invoked Rake Tasks for Deployed Applications ###
  
  <%=vars.product_short%> does not provide a way to run a Rake task on a deployed application. For <%=vars.product_short%> to automatically invoke a Rake task while an app is deployed, you must include the Rake task in your application and also configure the application start command with the `command` attribute in the application manifest, `manifest.yml`. 
  The following is an example of how to invoke a Rake database migration task at application startup. 
  
  1. Create a file with the Rake task name and the extension `.rake`, and store it in the `lib/tasks` directory of your application.
  
  
negative.code: 
  Run `cf help` to view a complete list of commands, grouped by task categories, and run `cf help [COMMAND]` for detailed information about a specific command. For more information about using the `cf` CLI, refer to the cf Command Line Interface (CLI) topics, especially the <%=vars.cli_v6%> topic.
  
  <p class="note"><strong>Note</strong>: You cannot perform certain tasks in the <%=vars.dev_console_2%> because these are commands that only a <%=vars.product_short%> administrator can run. If you are not a <%=vars.product_short%> administrator, the following message displays for these types of commands:
  
  <code>error code: 10003, message: You are not authorized to perform the requested action</code>
  
  <%=vars.dev_console_note%>
  </p>
  
  ## <a id='troubleshoot'></a>Troubleshooting ##
  If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
  
  ### App Deploy Fails ###
  Even when the deploy fails, the app might exist on <%=vars.product_short%>. Run `cf apps` to review the apps in the currently targeted org and space. You might be able to correct the issue using the <%=vars.dev_console_2%>, or you might have to delete the app and redeploy.
  
  Common reasons deploying an app fails include:
  
  * 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: Configure a Service Instance for Your RoR Application.
  * You did not successfully create a unique URL for the app. Refer to the troubleshooting tip App Requires Unique URL.
  
  ### App Requires Unique URL ###
  <%=vars.product_short%> requires that each app that you deploy have 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 fix 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.
  * `--random-route` to create a URL that includes the app name and random words. Using this option might create a long URL, depending on the number of words that the app name includes.
  
  
  
  
  
  
  