Merge branch 'gh-pages' of https://github.com/codeguy/php-the-right-way into docker

_posts/06-05-01-Further-Reading.md

@@ -9,4 +9,4 @@ anchor: further_reading
 - [What is Dependency Injection?](http://fabien.potencier.org/article/11/what-is-dependency-injection)
 - [Dependency Injection: An analogy](http://mwop.net/blog/260-Dependency-Injection-An-analogy.html)
 - [Dependency Injection: Huh?](http://net.tutsplus.com/tutorials/php/dependency-injection-huh/)
-- [Dependency Injection as a tool for testing](http://www.happyaccidents.me/dependency-injection-as-a-tool-for-testing/)
+- [Dependency Injection as a tool for testing](http://philipobenito.github.io/dependency-injection-as-a-tool-for-testing/)

_posts/14-02-01-Bytecode-Cache.md

@@ -11,12 +11,15 @@ If a PHP file is not modified, the bytecode will always be the same. This means
 This is where Bytecode cache comes in. It prevents redundant compilation by storing bytecode in memory and reusing it on successive calls.
 Setting up bytecode cache is a matter of minutes, and your application will speed up significantly. There's really no reason not to use it.
 
-As of PHP 5.5, there is a built-in bytecode cache called [OPcache](http://php.net/manual/en/book.opcache.php). This is
+As of PHP 5.5, there is a built-in bytecode cache called [OPcache][opcache-book]. This is
 also available for earlier versions.
 
-Other popular bytecodes caches are:
+Read more about bytecode caches:
 
+* [OPcache][opcache-book] (built-in since PHP 5.5)
 * [APC](http://php.net/manual/en/book.apc.php) (PHP 5.4 and earlier)
 * [XCache](http://xcache.lighttpd.net/)
 * [Zend Optimizer+](http://www.zend.com/products/server/) (part of Zend Server package)
 * [WinCache](http://www.iis.net/download/wincacheforphp) (extension for MS Windows Server)
+
+[opcache-book]: http://php.net/manual/en/book.opcache.php