anchor.diff:  ssi: enabled
   ```
   
  -### <a id='pushstate'></a> Pushstate Routing ###
  +### <a id='pushstate'></a> Enable Pushstate Routing ###
   
  -To keep visible URLs simple with a Javascript app that serves multiple routes, you can enable pushstate routing. Add the following line to your `Staticfile` to enable support for pushstate routing:
  +With client-side JavaScript apps that serve multiple routes, pushstate routing keeps browser-visible URLs clean. For example, pushstate routing allows a single JavaScript file route to multiple anchor-tagged URLs that look like `/some/path1` instead of `/some#path1`.
  +
  +To enable support for pushstate routing, add the following line to your `Staticfile`:
   
   ```
   pushstate: enabled
   ```
   
  -Pushstate routing allows for cleaner URLs with some client-side JS apps. It lets a single JS file route to multiple URLs that look like `/some/path1` instead of `/some#path1` when navigating page elements such as anchor tags.
  -
  -### <a id='gzip'></a> GZip Static ###
  +### <a id='gzip'></a> Disable Serving and Decompressing GZip Files ###
   
   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.
  +`gzip_static` enables Nginx to serve files stored in compressed `.gz` format, and `gunzip` uncompresses them 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`:
  +To disable these modules, specify the following in your custom `nginx.conf`:
   
   ```
   gunzip off;
  
positive.code: 
  <strong><%= modified_date %></strong>
  
  The Staticfile buildpack works for apps and content that requires no backend code besides an nginx webserver, which the buildpack provides. Examples include front-end JavaScript apps, static HTML content, and HTML/JavaScript forms. It also supports apps with backends hosted elsewhere.
  
  The version of nginx used by the staticfile buildpack can be found [in the release notes](https://github.com/cloudfoundry/staticfile-buildpack/releases).
  
  ## <a id='pushing_apps'></a> Pushing Apps ##
  
  
negative.code: 
  ## <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/`.
  