anchor.diff:  
   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 ##
  +##<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
  +###<a id='buildpack'></a>The buildpack attribute ###
   
   If your application requires a custom buildpack, you can use the `buildpack` attribute to specify its URL or name:
   
  
positive.code: 
  The command line option that overrides this attribute is `-n`.
  
  ### <a id='hosts'></a>The hosts attribute ###
  
  Use the `hosts` attribute to provide multiple hostnames or subdomains. Each hostname generates a unique route for the app. `hosts` can be used in conjunction with `host`. If you define both attributes, Cloud Foundry creates routes for hostnames defined in both `host` and `hosts`.
  
  
negative.code: </pre>
  
  
  ###<a id='path'></a>The path attribute
  
  You can use the `path` attribute to tell Cloud Foundry where to find your application. This is generally not necessary when you run `cf push` from the directory where an application is located.
  
  