anchor.diff:  
   ## <a id='bosh_trusted_cert'></a>BOSH Configured Custom Trusted Certificate Support ##
   
  -The staticfile-buildpack, based on nginx, does not make outgoing requests and does not benefit from [BOSH configured custom trusted certificates](http://bosh.io/docs/trusted-certs.html).
  +The staticfile-buildpack, based on Nginx, does not make outgoing requests and does not benefit from [BOSH configured custom trusted certificates](http://bosh.io/docs/trusted-certs.html).
   
   ## <a id='help_support'></a>Help and Support ##
   
  
positive.code: ssi: enabled
  ```
  
  ### <a id='gzip'></a> GZip Static ###
  
  The [`gzip_static`](http://nginx.org/en/docs/http/ngx_http_gzip_static_module.html) and [`gunzip`](http://nginx.org/en/docs/http/ngx_http_gunzip_module.html) modules are set to `on` by default.
  Together, these modules enable Nginx to properly serve compressed files to clients. They also decompress files for clients that do not support compressed content or responses.
  
  If you want to disable these modules, specify the following in your custom `nginx.conf`:
  
  ```
  gunzip off;
  
negative.code: 
  Why `-m 64M`? Your static assets will be served by [Nginx](http://nginx.com/) and it only requires 20M \[[reference](http://wiki.nginx.org/WhyUseIt)]. The `-m 64M` reduces the RAM allocation from the default 1G allocated to Cloud Foundry containers. In the future there may be a way for a buildpack to indicate its default RAM requirements; but not as of writing.
  
  ## <a id='configuration'></a> Configuration ##
  
  You can configure how the Staticfile buildpack accesses and serves apps by editing the `Staticfile` or `nginx.conf` files.
  
  ### <a id='root_folder'></a> Specify an Alternate Root Folder ###
  By default, the buildpack will serve `index.html` and all other assets from the root folder of your project.
  
  In many cases, you may have an alternate folder where your HTML/CSS/JavaScript files are to be served from, such as `dist/` or `public/`.
  