anchor.diff:  Include conf/extra/httpd-my-special-config.conf # This line includes your additional file.
   ```
   
  -
   #### <a id="php_ini_d"></a> .bp-config/php/php.ini.d/
   
  -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.
  +The buildpack adds any `.bp-config/php/php.ini.d/FILE-NAME.ini` files it finds in the app to the PHP configuration. You can use this to change any value acceptable to `php.ini`. For a list of directives, see [http://php.net/manual/en/ini.list.php](http://php.net/manual/en/ini.list.php).
   
  -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.
  +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"
  
positive.code: zend_extension=opcache.so
  ``` 
  
  If an extension is already present and enabled in the compiled php, for example `intl`, you do not need to explicitly enable it to use that extension.
  
  #### PHP\_EXTENSIONS vs. ZEND\_EXTENSIONS
  
  PHP has two kinds of extensions, _PHP extensions_ and _Zend extensions_. These hook into the PHP executable in different ways. See [https://wiki.php.net/internals/extensions](https://wiki.php.net/internals/extensions) for more information about the way extensions work internally in the engine.
  
  Because they hook into the PHP executable in different ways, they are specified differently in ini files. Apps fail if a Zend extension is specified as a PHP extension, or a PHP extension is specified as a Zend extension.
  
  If you see the following error, move the `example` extension from `extension` to `zend_extension`, then re-push your app:
  
  ```
  php-fpm | [warn-ioncube] The example Loader is a Zend-Engine extension and not a module (pid 40)
  
negative.code: 
  Each directory can contain configuration files that the component understands.
  
  For example, to change HTTPD logging configuration, run:
  
  ```
  ls -l .bp-config/httpd/extra/
  total 8
  -rw-r--r--  1 daniel  staff  396 Jan  3 08:31 httpd-logging.conf
  ```
  
  In this example, the `httpd-logging.conf` file overrides the one provided by the buildpack. <%= vars.recommended_by %> recommends that you copy the default from the buildpack and modify it.
  
  You can find the default configuration files in the [PHP Buildpack `/defaults/config` directory](https://github.com/cloudfoundry/php-buildpack/tree/master/defaults/config).
  
  You should be careful when modifying configurations, as doing so can cause your app to fail, or cause <%= vars.product_name %> to fail to stage your app.
  
  You can add your own configuration files. The components do not reference them, so you must ensure that they are included. For example, you can add an include directive to the [httpd configuration](https://github.com/cloudfoundry/php-buildpack/blob/master/defaults/config/httpd/httpd.conf) to include your file:
  
  ```
  ServerRoot "${HOME}/httpd"
  