anchor.diff:  cf push my-php-app -m 128M
   ```
   
  -Change *my-php-app* to some unique name, otherwise you'll get an error and the push will fail.
  +Change "my-php-app" to a unique name, otherwise you get an error and the push fails.
   
  -The example above will create and push a test application, "my-php-app", to Cloud Foundry.
  +The example above creates and pushes a test application, "my-php-app", to Cloud Foundry.
   
  -Here's a breakdown of what happens when you run the example above.
  +Here is a breakdown of what happens when you run the example above:
   
     - On your workstation...
  -    - It'll create a new directory and one PHP file, which calls `phpinfo()`
  +    - It creates a new directory and one PHP file, which calls `phpinfo()`
       - Run `cf` to push your application. This will create a new application with a memory limit of 128M (more than enough here) and upload our test file.
     - On Cloud Foundry...
       - The buildpack detects that your app is a php app
       - The buildpack is executed.
         - Application files are copied to the `htdocs` folder.
  -    - Apache HTTPD & PHP 5.4 are downloaded, configured with the buildpack defaults and run.
  +    - Apache HTTPD & PHP 5.4 are downloaded, configured with the buildpack defaults, and run.
       - Your application is accessible at the default route. Use ```cf app
       my-php-app``` to view the url of your new app.
   
   ## <a id="caveats"></a>Caveats ##
   
  -The PHP buildpack doesn't work with custom commands (the `-c` argument to `cf push` or a `command:` key in an application manifest).
  +The PHP buildpack does not work with custom commands (the `-c` argument to `cf push` or a `command` key in an application manifest).
   
  -As an alternative, the `ADDITIONAL_PREPROCESS_CMDS` [configuration option] specifies commands that run prior to your app. Use this option to specify migration scripts etc.
  +As an alternative, the `ADDITIONAL_PREPROCESS_CMDS` [configuration option] specifies commands that run prior to your app. For example, use this option to specify migration scripts.
  +
   Use the `APP_START_CMD` configuration option to specify an alternate PHP script to run to start your app.
   
   ## <a id="folder-structure"></a>Folder Structure ##
   
  -The easiest way to use the buildpack is to put your assets and PHP files into a directory and push it to <%=vars.product_short%>. This way, the build pack will take your files and automatically move them into the `WEBDIR` (defaults to `htdocs`) folder, which is the directory where your chosen web server looks for the files.
  +The easiest way to use the buildpack is to put your assets and PHP files into a directory and push it to <%=vars.product_short%>. This way, the buildpack will take your files and automatically move them into the `WEBDIR` (defaults to `htdocs`) folder, which is the directory where your chosen web server looks for the files.
   
   ### URL Rewriting
   
  -If you select Apache as your webserver, you can include `.htaccess` files with your application.
  +If you select Apache as your web server, you can include `.htaccess` files with your application.
   
   Alternatively, you can [provide your own Apache or Nginx configurations].
   
   ### Preventing Access To PHP Files
   
  -The buildpack will put all of your files into a publicly accessible directory.  In some cases, you might want to have PHP files that are not publicly accessible but are on the [include_path].  To do that, you simply create a `lib` directory in your project folder and place your protected files there.
  +The buildpack will put all of your files into a publicly accessible directory.  In some cases, you might want to have PHP files that are not publicly accessible but are on the [include_path]. To do that, create a `lib` directory in your project folder and place your protected files there.
   
  -Example:
  +For example:
   
   ```bash
   $ ls -lRh
  
positive.code: 
    This log is more detailed than the stdout output, however it is still terse.
  
    0. Set the `BP_DEBUG` environment variable to `true` for more verbose logging. This instructs the build pack to set it's log level to DEBUG and it'll write to stdout. Follow [Environment Variables documentation] to set `BP_DEBUG`.
  
  [Environment Variables documentation]:../../devguide/deploy-apps/manifest.html#env-block
  [application configuration files]:./gsg-php-config.html
  [include_path]:http://us1.php.net/manual/en/ini.core.php#ini.include-path
  [extensions]:https://github.com/cloudfoundry/php-buildpack/blob/master/docs/development.md#extensions
  [provide your own Apache or Nginx
  configurations]:./gsg-php-config.html#engine-conigurations
  [configuration option]:./gsg-php-config.html
  
negative.code: -rw-r--r--  1 daniel  staff     0B Feb 27 21:40 my.class.php  <-- not public, http://app.cfapps.io/lib/my.class.php == 404
  ```
  
  This comes with a catch. If your project legitimately has a `lib` directory, these files will not be publicly available because the buildpack does not copy a top-level `lib` directory into the `WEBDIR` folder.  If your project has a `lib` directory that needs to be publicly available, then you have two options as follows:
  
  #### Option #1
  
  In your project folder, create an `htdocs` folder (or whatever you've set for `WEBDIR`). Then move any files that should be publicly accessible into this directory. In the example below, the `lib/controller.php` file is publicly accessible.
  
  Example:
  
  