diff --git a/_posts/13-02-01-Bytecode-Cache.md b/_posts/13-02-01-Bytecode-Cache.md
index 4ae98a0..ff46a22 100644
--- a/_posts/13-02-01-Bytecode-Cache.md
+++ b/_posts/13-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
\ No newline at end of file