anchor.diff:  
   <%= vars.cookies_shared_domain_1 %> Many tracking tools such as Google Analytics and Mixpanel use the highest available domain to set their cookies. <%= vars.cookies_shared_domain_2 %> For example, an application at <code>my-app.<%= vars.app_domain %></code> might be able to access the cookies for an application at <code>your-app.<%= vars.app_domain %></code>.
   
  -Consider whether you want your applications or tools that use cookies to set and store the cookies at the highest available domain.
  +You should decide whether or not you want your applications or tools that use cookies to set and store the cookies at the highest available domain.
   
   ### <a id="ports"></a>Port Considerations ###
   
  
positive.code: </pre>
  
  The file types you will want to exclude vary, based on the application
  frameworks you use.
  The `.gitignore` templates for common frameworks, available at
  https://github.com/github/gitignore, are a useful starting point.
  
  ## <a id="increase-availability"></a>Run Multiple Instances to Increase Availability ##
  
  
negative.code: * `.git`
  * `.gitignore`
  * `.hg`
  * `manifest.yml`
  * `.svn`
  
  If the application directory contains other files, such as `temp` or `log`
  files, or complete subdirectories that are not required to build and run your
  application, you might want to add them to a `.cfignore` file to exclude them from upload. Especially with a large application, uploading unnecessary files can slow application deployment.
  
  To use a `.cfignore` file, create a text file named `.cfignore` in the root of your application directory structure. In this file, specify the files or file types you wish to exclude from upload. For example, these lines in a `.cfignore` file exclude the "tmp" and "log" directories.
  
  <pre class="terminal">
      tmp/
  