anchor.diff:  
   </pre>
   
  -### Step 4: Test the Sample App ###
  -
  -You’ve deployed your first app to <%=vars.product_short%>! Now let’s access your app online using its URL.
  -In the terminal output, the `urls` field of the `App started` block contains the app URL. This is the `HOST_NAME` you specified with the `-n` flag plus the domain `<%=vars.app_domain%>`. The image shows the resulting webpage for the `rails_sample_app`.
  +Let’s access your app online using its URL. In the terminal output, the `urls` field of the `App started` block contains the app URL. This is the `HOST_NAME` you specified with the `-n` flag plus the domain `<%=vars.app_domain%>`. The image shows the resulting webpage:
   
   <%= 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.
  +
  +### Step 8: Test a Deployed App ###
  +
  +You’ve deployed an app to <%=vars.product_short%>! 
  +
  +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 `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='cli-manage'></a>Manage Your Application with the cf CLI ##
   
  
positive.code: Example process type syntax:
      <pre class="code">
      PROCESS_TYPE: COMMAND
      </pre>
  
  To set a different production web server for your app:
  
  1. Add the gem for the web server to your Gemfile. 
  
  1. (**Optional**) In the `config/` directory of your app, create a new configuration file or modify an existing file.
  
      Refer to your web server documentation for how to configure this file.
  
  
negative.code: $ cf bind-service my-rails-app rails-postgres
  </pre>
  
  Alternately, you can configure the deployment manifest file by adding a `services` block to the `applications` block and specifying the service instance. For more information and an example on service binding using a manifest, see the next step.
  
  <%=vars.dev_console_5%>
  
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The manifest for the sample app contains a <code>services</code> subblock in the <code>applications</code>block. This binds the <code>rails-postgres</code> service instance you created in the previous step.</p>
  
  ### Step 4: Configure the Manifest File  ###
  
  You can specify app deployment options in a manifest that the `cf push` command uses. For more information about application manifests and supported attributes, refer to the [Deploying with Application Manifests](./../../devguide/deploy-apps/manifest.html) topic.
  
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. You can open the <code>manifest.yml</code> file in a text editor to view the bound service instance information. Locate the file in the app root directory and search for the <code>services</code> subblock in the <code>applications</code> block, as the example shows.
  
  <pre class="code">
  ---
  applications:
  ...
    services:
      - rails-postgres
  </pre>
  
  </p>
  
  
  ### 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%>
  
    <p class="tip"><strong>Sample App Step</strong><br />You must do this step to run the sample app.</p>
  
  
  ### Step 6: (Optional) Configure a Production Server  ###
  