anchor.diff:  
   When you bind an app to a service instance, <%=vars.product_short%> writes information about the service instance to the VCAP_SERVICES app environment variable. The app can use this information to integrate with the service instance.
   
  -Most services support bindable service instances. Refer to your service provider's documentation to confirm if they support this functionality.
  +Most services support bindable service instances. Refer to your service provider's documentation to confirm whether they support this functionality.
   
   To bind a service to an application, run `cf bind-service APPLICATION SERVICE_INSTANCE`.
   
  
positive.code: 
  #### Configure a Production Server ####
  
  <%=vars.product_short%> uses the default standard 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. If your app requires a more robust web server, refer to the [Configure a Production Server](./ruby-prod-server.html) topic for help configuring server other than WEBrick.
  
  ### Step 4: Log in and Target the API Endpoint ###
  
  
negative.code: * `--random-route` to create a URL that includes the app name and random words.
  * `cf help push` to view other options for this command.
  
  To view log activity while the app deploys, launch a new terminal window and run `cf logs [APP-NAME]`.
  
  In the terminal output of the `cf push` command, 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%>`. Once your app deploys, use this URL to access the app online.
  
  