anchor.diff:  
   ### <a id='nohosts'></a>The no-hostname attribute ###
   
  -By default if you do not provide a hostname, the URL for the app takes the form of `APP-NAME.DOMAIN`. If you want to override this and map the root domain to this app then you can set no-hostname as true.
  +By default, if you do not provide a hostname, the URL for the app takes the form of `APP-NAME.DOMAIN`. If you want to override this and map the root domain to this app then you can set no-hostname as true.
   
   <pre>
   ---
     no-hostname: true
   </pre>
   
  -The command line option that corresponds to this attribute is --no-hostname.
  +The command line option that corresponds to this attribute is `--no-hostname`.
   
   ### <a id='random-route'></a>The random-route attribute ###
   
  -Use the `random-route` attribute to create a URL that includes the app name and
  -random words.
  +Use the `random-route` attribute to create a URL that includes the app name and 
  +random words. 
   Use this attribute to avoid URL collision when pushing the same app to multiple spaces, or to avoid managing app URLs.
   
  -The command line option that corresponds to this attribute is --random-route.
  +The command line option that corresponds to this attribute is `--random-route`.
   
   <pre>
   ---
  
positive.code:   host: nifty
  </pre>
  
  A _minimal manifest_ requires only an application `name`. To create a valid minimal manifest, remove the `memory` and `host` properties from this example.
  
  Place your `manifest.yml` in the directory that contains the application files you want to push and run `cf push`. `cf push` searches the current directory for a manifest unless you specify another path with the `-p` option.
  
  ## <a id='name'></a>Always Provide an Application Name to cf push ##
  
  `cf push` requires an application name, which you provide either in a manifest or at the command line.
  
  As described in [How cf push Finds the Manifest](#find-manifest) above, the simple command `cf push` works when the `manifest.yml` file is in the current working directory.
  
  If you do _not_ use a manifest, the minimal push command looks like this:
  
  <pre class="terminal">
  cf push my-application-name
  </pre>
  
  <p class="note"><strong>Note</strong>: When you provide an application name at the command line, <code>cf push</code> 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; <code>cf</code> does not push the others.
  These behaviors are useful for testing.</p>
  
  ## <a id='find-app'></a>How cf push Finds the Application ##
  
negative.code: title: Deploying with Application Manifests
  ---
  
  _This page assumes that youare using cf CLI v6._
  
  Application manifests tell `cf push` what to do with applications. 
  This includes everything from how many instances to create and how much memory 
  to allocate to what services applications should use.
  
  A manifest can help you automate deployment, especially of multiple applications 
  at once.
  
  ##<a id='find-manifest'></a>How cf push Finds the Manifest ##
  
  