anchor.diff:  
   ### <a id='domain'></a>The domain attribute ###
   
  -Every `cf push` deploys applications to one particular Cloud Foundry instance. Every Cloud Foundry instance has its own default domain. When you do not specify a domain, `cf` incorporates the default domain in the route to your application.
  -
  -You can use the `domain` attribute when you want your application to be served from a domain other than the default.
  +Every `cf push` deploys applications to one particular Cloud Foundry instance.
  +Every Cloud Foundry instance may have a shared domain set by an admin.
  +Unless you specify a domain, `cf` incorporates that shared domain in the route to your application.
  +
  +You can use the `domain` attribute when you want your application to be served from a domain other than the default shared domain.
   
   ~~~
   domain: unique-example.com
  
positive.code: path: <path_to_application_bits>
  ~~~
  
  If you provide a path, it is a good idea to use either a command-line option or a manifest. Using both together is technically possible, but the resulting path may not be what you expect.
  
  The command-line option that you can use instead of this attribute is `-p`.
  
  ### <a id='env-block'></a>Environment variables ###
  
  
negative.code: 
  **Note:** When you provide an application name at the command line, `cf push` uses that application name whether or not there is a different application name in the manifest.
  If the manifest describes multiple applications, you can push a single application by providing its name at the command line; `cf` does not push the others.
  These behaviors are useful for testing.
  
  ## <a id='find-app'></a>How cf push Finds the Application ##
  
  