anchor.diff:  
   #### <a id="php_ini_d"></a> .bp-config/php/php.ini.d/
   
  -The buildpack will add any `.bp-config/php/php.ini.d/<file>.ini` files it finds in the application to the PHP configuration. This can be used to change any value which is acceptable to php.ini [(list of directives)](http://php.net/manual/en/ini.list.php).
  +The buildpack adds any `.bp-config/php/php.ini.d/FILE-NAME.ini` files it finds in the application to the PHP configuration. You can use this to change any value acceptable to `php.ini`. See [http://php.net/manual/en/ini.list.php](http://php.net/manual/en/ini.list.php) for a list of directives.
   
  -For example adding a file `.bp-config/php/php.ini.d/something.ini` to your app, with contents
  +For example, adding a file `.bp-config/php/php.ini.d/something.ini` to your app, with the following contents, overrides both the default charset and mimetype.
   
   ```
   default_charset="UTF-8"
   default_mimetype="text/xhtml"
   ```
   
  -would override both the default charset and mimetype.
  -
   ##### Precedence
   
  -In order of highest precedence, php config values come from.
  +In order of highest precedence, php configuration values come from the following sources:
   
  -* php scripts using ini_set() to manually override config files
  -* user.ini files (for local values)
  -* .bp-config/php/php.ini.d overrides master value but, local value is still the one from user.ini
  +* php scripts using `ini_set()` to manually override config files
  +* user.ini files for local values
  +* .bp-config/php/php.ini.d to override master value, but not local values from user.ini files
   
   #### <a id="fpm_d"></a> .bp-config/php/fpm.d/
   
  -The buildpack will add any `.bp-config/php/fpm.d` files it finds in the application to the PHP-FPM configuration. This can bes used to change any value which is acceptable to `php-fpm.ini` [(list of directives)](http://php.net/manual/en/install.fpm.configuration.php)
  +The buildpack adds any `.bp-config/php/fpm.d` files it finds in the application to the PHP-FPM configuration. You can use this to change any value acceptable to `php-fpm.ini`. See [http://php.net/manual/en/install.fpm.configuration.php](http://php.net/manual/en/install.fpm.configuration.php) for a list of directives.
   
   ### <a id="php-extensions"></a> PHP Extensions
   
  -The buildpack will add any `.bp-config/php/php.ini.d/<file>.ini` files it finds in the application to the PHP configuration. This can be used to enable PHP or ZEND extensions. For example,
  +The buildpack adds any `.bp-config/php/php.ini.d/FILE-NAME.ini` files it finds in the application to the PHP configuration. You can use this to enable PHP or ZEND extensions. For example:
   
   
   ```
  
positive.code: | NGINX\_VERSION               | Sets the version of Nginx to use. By default, the buildpack uses the latest stable version.                                                                                                                                                                                                                      |
  | PHP\_VERSION                 | Sets the version of PHP to use. <br> Set to a minor instead of a patch version, <br> such as `"{PHP_70_LATEST}"`. See [options.json](https://github.com/cloudfoundry/php-buildpack/blob/4f5e50fabf66c5840210cbc64fcd4068d8a27448/cf_spec/fixtures/php_app_using_php_7_latest/.bp-config/options.json).             |
  | PHP\_EXTENSIONS              | (DEPRECATED) A list of the [extensions](#php-extensions) to enable.  `bz2`, `zlib`, `curl`, and `mcrypt` are enabled by default.                                                                                                                                                                                                                                 |
  | PHP\_MODULES                 | A list of the [modules](#php-modules) to enable.  No modules are explicitly enabled by default, however the buildpack automatically chooses `fpm` or `cli`. You can explicitly enable any or all of: `fpm`, `cli`, `cgi`, and `pear`.                                                                                           |
  | ZEND\_EXTENSIONS             | A list of the Zend extensions to enable. Nothing is enabled by default.                                                                                                                                                                                                                                                                           |
  | APP\_START\_CMD              | When the `WEB_SERVER` option is set to 'none,' this command is used to start your app. If `WEB_SERVER` and `APP_START_CMD` are not set, then the buildpack searches for `app.php`, `main.php`, `run.php`, or `start.php` (in that order). This option accepts arguments. |
  | WEBDIR                       | The root directory of the files served by the web server specified in `WEB_SERVER`. Defaults to `htdocs`. Other common settings are `public`, `static`, or `html`. Path is relative to the root of your application.           |
  | LIBDIR                       | This path is added to PHP's `include_path`. Defaults to `lib`. Path is relative to the root of your application.           |
  | HTTP\_PROXY                  | The buildpack downloads uncached dependencies using HTTP. If you are using a proxy for HTTP access, set its URL here.
  | HTTPS\_PROXY                  | The buildpack downloads uncached dependencies using HTTPS. If you are using a proxy for HTTPS access, set its URL here.
  | ADDITIONAL\_PREPROCESS\_CMDS | A list of additional commands that will run prior to the application starting. For example, you might use this command to run migration scripts or static caching tools before the application launches.
  
  For details about supported versions, please read the [release notes](https://github.com/cloudfoundry/php-buildpack/releases) for your buildpack version.
  
  ### <a id="engine-configurations"></a> HTTPD, Nginx, and PHP configuration
  
  The buildpack automatically configures HTTPD, Nginx, and PHP for your application.  This section explains how to modify the configuration.
  
  The `.bp-config` directory in your application can contain configuration overrides for these components. Name the directories `httpd`, `nginx`, and `php`. We recommend that you use [php.ini.d](#php_ini_d) or [fpm.d](#fpm_d)).
  
  <p class='note'><strong>NOTE</strong>: If you override the php.ini or php-fpm.ini files many other forms of configuration will not work.</p>
  
  For example:
  ```
  
negative.code: php-fpm | NOTICE: PHP message: PHP Fatal error:  Unable to start example Loader module in Unknown on line 0
  ```
  
  If you see the following error, move the `example` extension from `zend_extension` to `extension`, then re-push your app.
  
  ```
  NOTICE: PHP message: PHP Warning: example MUST be loaded as a Zend extension in Unknown on line 0
  ```
  
  ### <a id="php-modules"></a> PHP Modules
  
  You can include the following modules by adding them to the `PHP_MODULES` list:
  
    - `cli`, installs `php` and `phar`
    - `fpm`, installs `PHP-FPM`
    - `cgi`, installs `php-cgi`
    - `pear`, installs Pear
  
  By default, the buildpack installs the `cli` module when you push a standalone app, and installs the `fpm` module when you push a web app. You must specify `cgi` and `pear` if you want them installed.
  
  ## <a id="buildpack-extensions"></a>Buildpack Extensions
  
  The buildpack comes with extensions for its default behavior. These are the [HTTPD], [Nginx], [PHP], and [NewRelic] extensions.
  
  The buildpack is designed with an extension mechanism, allowing app developers to add behavior to the buildpack without modifying the buildpack code.
  
  When you push an app, the buildpack runs any extensions found in the `.extensions` directory of your app.
  
  The [Developer Documentation](https://github.com/cloudfoundry/php-buildpack/blob/master/README.md) explains how to write extensions.
  
  