anchor.diff:      - rails-postgres
   </pre>
   
  -You can also bind a service using the CLI <%=vars.dev_console_2%>.
  +You can also bind a service using the <%=vars.dev_console_2%>.
   
   ### <a id='yourapp-step5'></a>Step 5: Login to <%=vars.product_short%> and Target the API Endpoint   ###
  -Run `cf login -a [API_ENDPOINT]`, enter your login credentials, and select a space and org.
  -
  -For more information, refer to the <%=vars.gen_GSG%> 
  +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  ###
   
  
positive.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.
  
  <pre class="note"><strong>Note</strong>: You cannot perform certain tasks in the CLI <%=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%> 
  </pre>
  
  ## <a id='console-manage'></a>Manage Your Application with the <%=vars.product_short%> Developer Console ##
  You can also use the Developer Console to view and modify information about your app, such as:
  
  * Starting, stopping, and restarting your app
  * Creating, binding, unbinding, and deleting service instances
  * Creating and deleting orgs and spaces
  * Launching the URL for an app in a browser window
  * Viewing logs
  
  <%=vars.dev_console_3%> 
  
  ## <a id='troubleshoot'></a>Troubleshooting ##
  If your application fails to start on Cloud Foundry, 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.
  
  ### <a id='deploy-fails'></a>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 CLI commands or Developer Console functionality, or you might have to delete the app and redeploy.
  
  Common reasons why deploy 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. You can create and bind services using the CLI, the Developer Console, or both. You can also bind an existing service by declaring it in the manifest file. Refer to [Step 3: Configure a Service Instance for Your RoR Application](#yourapp-step3) and [Step 4: Configure the Manifest File](#yourapp-step4).
  * 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 ###
  
negative.code: 
  <%= image_tag("../images/RoR_sample_webpage.png") %>
  
  You can now use the `cf` <%=vars.dev_console_2%> to review information and administer your app and your <%=vars.product_short%> account. For example, you could edit the `rails_sample_app/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%>
  
  ## <a id='deploy-yourapp'></a>Deploy Your RoR Application ##
  
  