anchor.diff:  ### <a id='service'></a>Confirm Service Accessibility
   
   Apps use services such as databases, messaging, and key-value stores.
  -To use a service, the app must bind to an instance of the service running in the same space, or shared with its space. Before pushing an app, you must:
  +To use a service, the app must bind to an instance of the service that is running in the same space or shared with its space. Before pushing an app, you must:
   
   * Confirm that every service that your app uses has an instance that the app can access.
   
  
positive.code: 
  ## <a id='services'></a>(Optional) Configure App Services
  
  If a newly-pushed app has the same name and route as an older app version that is already bound and configured for the services it uses, the new app retains the bindings and service configuration of the previously-running version.
  
  For apps that are not already set up for the services that they use, you need to:
  
  
negative.code: 
    `cf push APP-NAME`
  
  To specify options, as described in [Determine cf push Options](#options), you can include them in the `cf push` command itself, in a `manifest.yml` file, or both.
  
  A manifest file can also include a [Services](./manifest-attributes.html#services-block) block that lists service instances for the app to bind to automatically.
  
  