anchor.diff:  
   Before you can push your application to Cloud Foundry you need to know:
   
  -* The URL to target for your Cloud Foundry instance.
  -Typically this is a URL that begins with "api."
  -Consult your cloud operator if you are unsure of your target URL.
  +* The API endpoint, also known as the target URL, for your Cloud Foundry instance.
  +This is a URL that typically begins with "api."
  +Consult your cloud operator if you are unsure of your API endpoint.
   * Your username and password for your Cloud Foundry instance.
   * The organization and space where you want to deploy your application.
   A Cloud Foundry workspace is organized into organizations, and within them,
  
positive.code: * **Start Command**: This is the command that Cloud Foundry uses to start
  each instance of your application.
  This start command varies by application framework.
  * **URL and Domain**: The URL is the subdomain for your application. It is hosted at the
  primary domain you choose.
  The combination of the URL and domain must be globally unique.
  * **Services**: Applications can bind to services such as databases, messaging, and key-value stores.
  Applications are deployed into App Spaces.
  An application can only bind to services that exist in the target App Space before the application is deployed.
  
  ### <a id='defining-options'></a>Defining Deployment Options ###
  
  You can define deployment options on the command line, in a
  manifest file, or both together.
  See [Application Manifests](./manifest.html) to learn how applications settings change from push to push, and how command-line options, manifests, and commands like `cf scale` interact.
  
  When you deploy an application while it is running, `cf` stops all instances of
  that application and then deploys.
  
negative.code: An application that uses services, such as a database, messaging, or email
  server, is not fully functional until you *provision* the service and, if
  required, *bind* the service to the application.
  
  ## <a id='prepare'></a>Step 1: Prepare to Deploy ##
  
  