anchor.diff:  
   ## <a id='logon-target'></a>Step 2: Know Your Credentials and Target ##
   
  -Before you can push your application to Cloud Foundry you need to know:
  +Before you can push your app to Cloud Foundry you need to know:
   
   * The API endpoint for your Cloud Foundry instance. Also known as the target
   URL, this is <%=vars.api_endpoint%>.
   * Your username and password for your Cloud Foundry instance.
  -* The organization and space where you want to deploy your application.
  +* The organization and space where you want to deploy your app.
   A Cloud Foundry workspace is organized into organizations, and within them,
   spaces.
   As a Cloud Foundry user, you have access to one or more organizations and
  
positive.code: 
  ## <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
  configure your application with the service URL and credentials.
  For more information, see the specific documentation for your application
  framework:
  
  * [Ruby](../../buildpacks/ruby/ruby-service-bindings.html)
  
negative.code: 
  <strong><%= modified_date %></strong>
  
  <p class="note"><strong>Note:</strong> See the <a href="../../buildpacks/">buildpacks</a> documentation for complete deployment guides specific to your app language or framework, such as the <a href="../../buildpacks/ruby/gsg-ror.html">Getting Started Deploying Ruby on Rails Apps</a> guide.</p>
  
  ## <a id='intro'></a>Overview of Deployment Process ##
  
  You deploy an app to Cloud Foundry by running a `push` command from a
  Cloud Foundry Command Line Interface (cf CLI).
  Refer to the [Installing the cf CLI](../../cf-cli/install-go-cli.html) topic for more information.
  Between the time that you run `push` and the time that the app is available, Cloud Foundry performs the following tasks:
  
  * Uploads and stores app files
  * Examines and stores app metadata
  * Creates a "droplet" (the Cloud Foundry unit of execution) for the app
  * Selects an appropriate droplet execution agent (DEA) to run the droplet
  * Starts the app
  
  For more information on the lifecycle of an app, see the <a href="app-lifecycle.html">Application Container Lifecycle</a> topic.
  
  An app 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 app.
  For more information about services, see the [Services Overview](../services/index.html) topic.
  
  ## <a id='prepare'></a>Step 1: Prepare to Deploy ##
  
  Before you deploy your app to Cloud Foundry, make sure that:
  
  * Your app is *cloud-ready*.
  Cloud Foundry behaviors related to file storage, HTTP sessions, and port usage
  may require modifications to your app.
  
  * All required app resources are uploaded.
  For example, you may need to include a database driver.
  
  * Extraneous files and artifacts are excluded from upload.
  You should explicitly exclude extraneous files that reside within your
  app directory structure, particularly if your app is large.
  
  * An instance of every service that your app needs has been created.
  
  * Your Cloud Foundry instance supports the type of app you are going to
  deploy, or you have the URL of an externally available buildpack that can stage
  the app.
  
  For help preparing to deploy your app, see:
  
  * [Considerations for Designing and Running an Application in the Cloud](./prepare-to-deploy.html)
  * [Buildpacks](../../buildpacks/index.html)
  