anchor.diff:  Using manifest file /path_to_working_directory/some_directory/some_other_directory/manifest.yml
   </pre>
   
  -If the manifest is named something other than `manifest.yml`, use the `-f` 
  +If the manifest is named something other than `manifest.yml`, use the `-f`
   option. You must include both the path and the filename with the `-f` option.
   
   <pre class="terminal">
  -$ cf push -f ./some_directory/some_other_directory/alternative_manifest.yml
  -Using manifest file /path_to_working_directory/some_directory/some_other_directory/alternative_manifest.yml
  +$ cf push -f ./some_directory/some_other_directory/alternate_manifest.yml
  +Using manifest file /path_to_working_directory/some_directory/some_other_directory/alternate_manifest.yml
   </pre>
   
   ## <a id='minimal-manifest'></a>Example Manifest ##
   
  -You can deploy applications without ever using a manifest. 
  -The benefits manifests may provide include consistency and reproducibility. 
  -When you want applications to be portable between different clouds, manifests 
  +You can deploy applications without ever using a manifest.
  +The benefits manifests may provide include consistency and reproducibility.
  +When you want applications to be portable between different clouds, manifests
   may prove especially useful.
   
   Manifests are written in YAML. The manifest below illustrates some YAML conventions, as follows:
  
positive.code: 
  <pre>
  ---
    no-hostname: true
  </pre>
  
  
negative.code: 
  <pre>
  ---
    ...
    domains:
    - domain-example1.com
    - domain-example2.org
  