anchor.diff:  ### <id='introduction'></a>Introduction
   
   This topic describes how to configure the Staticfile buildpack and use it to push static content to the web. 
  -
  -<hr>
  -
  -### <a id='staticfile-app'></a>Definition: Staticfile app
  -
  -A **_staticfile app_** is an app or content that require no backend code except an Nginx webserver.
  -
  -Examples of staticfile apps are front-end JavaScript apps, static HTML content, and HTML/JavaScript forms.
  -
  -<hr>
  -
  -### <a id='staticfile-buildpack'></a>Definition: Staticfile buildpack
  -
  -The **_Staticfile buildpack_** is the buildpack that provides runtime support for staticfile apps and apps with backends hosted elsewhere.
  -
  -For example, works for apps and content that require no backend code besides an Nginx webserver, which the buildpack provides.
  -
  -<hr>
  -
  -### <a id='memory'></a>About memory usage
  -
  +It also shows you how to serve a simple "Hello World" page using the staticfile buildpack.
  +
  +### <a id='definitions'></a>Definitions
  +
  +**Staticfile app** — An app or content that requires no backend code other than the Nginx webserver, which the buildpack provides.
  +   Examples of staticfile apps are front-end JavaScript apps, static HTML content, and HTML/JavaScript forms.
  +
  +**Staticfile buildpack** — The buildpack that provides runtime support for staticfile apps and apps with backends hosted elsewhere.
  +
  +### <a id='memory'></a>About Memory Usage
   
   Nginx only requires 20&nbsp;M to serve static assets. 
  -Using the `-m 64 M` reduces the RAM allocation from the default 1&nbsp;G usually allocated to Cloud Foundry containers. 
  -
  -<hr>
  -
  -### <a id='sample'></a>Create and push a sample app
  -
  -The procedure below describes how to create and push a single page staticfile app using the Staticfile buildpack.
  -
  -1. Create a root directory for the sample app in your workspace:
  +This is why Pivotal recommends using the `-m 64 M` command when pushing the app to reduce the RAM allocation from the 
  +default 1&nbsp;G usually allocated to Cloud Foundry containers. 
  +
  +### <a id='sample'></a>Create and Push a Sample App
  +
  +The following procedure describes how to create and push a single page staticfile app using the Staticfile buildpack.
  +
  +1. In your local workspace, use `cf login` to log in to <%= vars.product_short %>. For more information, see [Login](../../cf-cli/getting-started.html#login).
  +
  +1. Create and change into a root directory for the sample app in your workspace:
       
       <code>
       $ mkdir sample
  -    </code>
  +    $ cd sample
  +    </code>
  +
   2. Create an `index.html` file that contains some text:
   
       <code>
  
positive.code: Use this website to create hashed username and password pairs for your website: 
  [http://www.htaccesstools.com/htpasswd-generator/](http://www.htaccesstools.com/htpasswd-generator/)
  
  ### <a id='force-https'></a>About FORCE_HTTPS with reverse proxies 
  
  If you are using a reverse proxy such as CloudFlare and you have rules to redirect HTTP, do not use FORCE_HTTPS. 
  This is because the reverse proxy is intended to communicate directly with the app through HTTP.
  
negative.code:     $ touch Staticfile
      </code>
  
  1. Use `cf login` to log in to <%= vars.product_short %>. 
  For more information, see [Login](../../cf-cli/getting-started.html#login).
  
  4. Push the sample app:
  
      <code>
      $ cf push hello -m 64M
      </code>
    
  5. Find the URL of the hello app in the output. A fragment of output is shown below:
    <pre class='terminal'>
    Creating app hello in org sample-org / space sample-space as username<span>@</span>example.com...
    OK
    &#8230; 
    requested state: started
    instances: 1/1
    usage: 64M x 1 instances
    urls: hello.example.com
    </pre>
  
  7. Navigate to the URL to see the hello app running.
  
  ## <a id='configure-and-push'></a>Configuring the Buildpack and Pushing the App
  
  This section describes...
  how to configure the staticbuildpack options by x or y and then how to push your app.
  
  ### <a id='config-options'></a>Configuration Options
  
  This list describes some of the aspects of the Staticfile buildpack that you can configure:
  
  * **Directory list** — An HTML page that displays a directory index for your site. A sample of a directory list is shown below. 
  
      ![Directory Index](../images/directory-index.png)
  
      If your site is missing an index.html, you can choose to display a directory list instead of the standard 404 error page.
  
  * **SSI** — Server Side Includes (SSI) is ... You can apply SSI to your app. [NEEDS WORK]. For more information about SSI, see the [Server Side Includes](https://en.wikipedia.org/wiki/Server_Side_Includes) entry on Wikipedia.
  
  * **Pushstate routing** — A way to keep browser-visible URLs clean for client-side JavaScript apps that serve multiple routes. 
  
      For example, pushstate routing allows a single JavaScript file route to multiple anchor-tagged URLs that look like `/some/path1` instead of `/some#path1`.
  
  