anchor.diff:  
   ## <a id='domain'></a>Step 3: (Optional) Configure Domains ##
   
  -Cloud Foundry directs requests to an application using a route, which is a URL
  +Cloud Foundry directs requests to an app using a route, which is a URL
   made up of a host and a domain.
   
  -* The name of an application is the default host for that application, unless you specify the host name with the <code>-n</code> flag.
  -
  -* Every application is deployed to an application space that belongs to a
  +* The name of an app is the default host for that app, unless you specify the host name with the <code>-n</code> flag.
  +
  +* Every app is deployed to an app space that belongs to a
   domain.
   Every Cloud Foundry instance has a default domain defined.
   You can specify a non-default, or custom, domain when deploying, provided that
  -the domain is registered and is mapped to the organization which contains the target application space.
  +the domain is registered and is mapped to the organization which contains the target app space.
   
   <p class='note'><strong>Note</strong>:
   CF ​allows​ app names, but not app URLs, to include underscores. CF converts underscores to hyphens when setting a default app URL from an app name.
  
positive.code: 
  ## <a id='troubleshoot-push'></a>Step 7: Troubleshoot Deployment Problems ##
  
  If your application does not start on Cloud Foundry, first ensure that your
  application can run locally.
  
  You can troubleshoot your application in the cloud using the cf CLI.
  See [Troubleshoot Application Deployment and Health](./troubleshoot-app-health.html).
  
negative.code: 
  ### <a id='profile'></a>Configure Pre-Runtime Hooks ###
  
  <p class="note"><strong>Note</strong>: The Java buildpack does not support pre-runtime hooks.</p>
  
  To configure pre-runtime hooks, create a file named `.profile` and place it in the root of your app directory. 
  If the directory includes a `.profile` script, then Cloud Foundry executes it immediately before each instance of your app starts. 
  Because the `.profile` script executes after the buildpack, the script has access to the language runtime environment created by the buildpack.
  
  <p class="note"><strong>Note</strong>: Your app root directory may also include a <code>.profile.d</code> directory that contains bash scripts that perform initialization tasks for the buildpack. 
  Developers should not edit these scripts unless they are using a <a href="../../buildpacks/custom.html">custom buildpack</a>.</p>
  
  You can use the `.profile` script to perform app-specific initialization tasks, such as setting custom environment variables. 
  Environment variables are key-value pairs defined at the operating system level. 
  These key-value pairs provide a way to configure the apps running on a system. 
  For example, any app can access the LANG environment variable to determine which language to use for error messages and instructions, collating sequences, and date formats.
  
  To set an environment variable, add the appropriate bash commands to your `.profile` file. See the example below.
  
  ~~~bash
  # Set the default LANG for your apps
  export LANG=en_US.UTF-8
  ~~~
  
  <p class="note"><strong>Note</strong>: If you are using a PHP buildpack version prior to v4.3.18, the buildpack does not execute your PHP app's <code>.profile</code> script. Your PHP app will host the <code>.profile</code> script's contents. 
  This means that any PHP app staged using the affected PHP Buildpack versions can leak credentials placed in the <code>.profile</code> script.</p>
  
  ## <a id='push'></a>Step 5: Push the App ##
  
  Run the following command to deploy an app without a manifest:
  
    `cf push APP-NAME`
  
  If you provide the app name in a manifest, you can reduce the command to
  `cf push`.
  See [Deploying with Application Manifests](./manifest.html).
  
  Because all you have provided is the name of your app, `cf push` sets the
  number of instances, amount of memory, and other attributes of your app
  to the default values.
  You can also use command-line options to specify these and additional
  attributes.
  
  The following transcript illustrates  how Cloud Foundry assigns default values
  to app 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>
  
  