anchor.diff:  
   ## <a id='service-connection'></a>Step 6: (Optional) Configure Service Connections ##
   
  -If you bound a service to the application that you deployed, you might need to 
  +If you bound a service to the application that you deployed, you might need to
   configure your application with the service URL and credentials.
   For more information, see the specific documentation for your application
   framework:
  
positive.code: 
  For more information about the manifest file, see the [Deploying with Application Manifests](./manifest.html) topic.
  
  ## <a id='push'></a>Step 5: Push the Application ##
  
  Run the following command to deploy an application without a manifest:
  
    `cf push APP-NAME`
  
  If you provide the application name in a manifest, you can reduce the command to 
  `cf push`.
  See [Deploying with Application Manifests](./manifest.html).
  
  
negative.code: You can also use command-line options to specify these and additional
  attributes.
  
  The following transcript illustrates  how Cloud Foundry assigns default values
  to application when given a `cf push` command.
  
  <p class ="note"><strong>Note</strong>: When deploying your own apps, avoid generic names like <code>my-app</code>. Cloud Foundry uses the app name to compose the route to the app, and deployment fails unless the app has a globally unique route.</p>
  