anchor.diff:      $ 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 and navigate there to see the static app running.
  -
  -    Highlight the code output ADD
  -
  - 
  -<hr>
  -
  -## <a id='configure-and-push'></a>Configuring the buildpack and pushing the app
  -
  -### <a id='config-options'></a>Configuration options
  -
  -This list explains 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. 
  +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 ...
  -
  -* **_Pushstate routing_** — A way to keep browser-visible URLs clean for client-side JavaScript apps that serve multiple routes. 
  +* **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`.
   
  
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: The diagram below illustrates a HTTPS redirect loop and direct HTTP communication between a reverse proxy and an app server.
  
  <img src="../images/reverse-proxy.png">
  
  ### <a id='config-process'></a>Configure and push your app
  
  