anchor.diff:  domain: unique-example.com
   ~~~
   
  -The command-line option that overrides this attribute is `-d`.
  +The command line option that overrides this attribute is `-d`.
  +
  +### <a id='instances'></a>The instances attribute ###
  +
  +Use the `instances` attribute to specify the number of app instances you want to start upon push:
  +
  +~~~
  +instances: 2
  +~~~
  +
  +We recommend that you run at least two instances of any apps for which fault tolerance matters.
  +
  +The command line option that overrides this attribute is `-i`.
  +
  +### <a id='memory'></a>The memory attribute ###
  +
  +Use the `memory` attribute to specify the memory limit for all instances of an app. This attribute requires a unit of measurement: `M`, `MB`, `G`, or `GB`, in upper case or lower case. For example:
  +
  +~~~
  +memory: 1024M
  +~~~
  +
  +The default memory limit is 1G. You might want to specify a lower limit to conserve memory if you know that your app instances do not require 1G of memory.
  +
  +The command line option that overrides this attribute is `-m`.
  +
  +### <a id='host'></a>The host attribute ###
  +
  +Use the `host` attribute to provide a hostname, or subdomain, in the form of a string. This segment of a route helps to ensure that the route is unique. If you do not provide a hostname, the URL for the app takes the form of `APP.DOMAIN`.
  +
  +~~~
  +host: my-app
  +~~~
  +
  +The command line option that overrides this attribute is `-n`.
  +
  +### <a id='path'></a>The path attribute
  +
  +You can use the `path` attribute to tell `cf` where to find your application. This is generally not necessary when you run `cf push` from the directory where an application is located.
  +
  +~~~
  +path: <path_to_application_bits>
  +~~~
  +
  +The command line option that overrides this attribute is `-p`.
  +
  +### <a id='timeout'></a>The timeout attribute ###
  +
  +Use the `timeout` attribute to give your application more time to start, up to 180 seconds. The default is 60 seconds. For example:
  +
  +~~~
  +timeout: 80
  +~~~
  +
  +If the app has not started by the timeout limit you set, Cloud Foundry stops trying to start the app. You might want to increase the timeout length to ensure that very large apps have sufficient time to start.
  +
  +The command line option that overrides this attribute is `-t`.
   
   ### <a id='no-route'></a>The no-route attribute ###
   
  
positive.code: buildpack: <buildpack_URL>
  ~~~
  
  **Note:** The `cf buildpacks` command lists the buildpacks that you can refer to by name in a manifest or a command-line option.
  
  The command-line option that overrides this attribute is `-b`.
  
  ### <a id='start-commands'></a>The command attribute ###
  
  
negative.code: 
  * For example, the `cf scale` command changes the number of instances.
  
  The attribute values on the server at any one time represent the cumulative result of all settings applied up to that point: defaults, attributes in the manifest, `cf push` command line options, and commands like `cf scale`.
  There is no special name for this resulting set of values on the server.
  You can think of them as the most recent values.
  
  `cf push` follows rules of precedence when setting attribute values:
  
  * Manifests override most recent values, including defaults.
  * Command line options override manifests.
  
  In general, you can think of manifests as just another input to `cf push`, to be combined with command line options and most recent values.
  
  ## <a id='optional-attributes'></a>Optional Attributes ##
  
  This section explains how to describe optional application attributes in manifests. Each of these attributes can also be specified by a command line option. Command line options override the manifest.
  
  ### <a id='buildpack'></a>The buildpack attribute
  
  