diff --git a/_posts/10-02-01-Bytecode-Cache.md b/_posts/10-02-01-Bytecode-Cache.md
index 1c35c10..fd535f1 100644
--- a/_posts/10-02-01-Bytecode-Cache.md
+++ b/_posts/10-02-01-Bytecode-Cache.md
@@ -7,11 +7,11 @@ isChild: true
 When PHP file is executed, under the hood it is first compiled to bytecode (also known as opcode) and only then, the bytecode is executed.
 If PHP file is not modified, then bytecode will always be same, which means that compilation step is a waste of CPU resources.
 
-This is where Bytecode cache comes in - it prevents redundant compilation by storing bytecode in memory and reusing it on successive calls.
+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.
 
 Popular bytecodes caches are:
 
 [APC](http://php.net/manual/en/book.apc.php)
-[xCache](http://xcache.lighttpd.net/)
+[XCache](http://xcache.lighttpd.net/)
 [Zend Optimizer+](http://www.zend.com/products/server/) (part of Zend Server package)
\ No newline at end of file