From a2e02549b04a5f1450205e79ec451b3e2736b326 Mon Sep 17 00:00:00 2001
From: Goran Rakic <grakic@devbase.net>
Date: Sat, 14 Jul 2012 00:57:24 +0200
Subject: [PATCH] Add comments to code sample, making more clear that
 'expensive_data' is a key for data in cache

---
 _posts/10-03-01-Object-Caching.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/_posts/10-03-01-Object-Caching.md b/_posts/10-03-01-Object-Caching.md
index df29b2e..0577b4b 100644
--- a/_posts/10-03-01-Object-Caching.md
+++ b/_posts/10-03-01-Object-Caching.md
@@ -7,7 +7,7 @@ isChild: true
 There are times when it can be beneficial to cache individual objects in your code, such as with data that is expensive
 to get or database calls where the result is unlikely to change. You can use object caching software to hold these
 pieces of data in memory for extremely fast access later on. If you save these items to a data store after you retrieve
-them, then pull them directly from the cache for following requests you can gain a significant improvement in
+them, then pull them directly from the cache for following requests, you can gain a significant improvement in
 performance as well as reduce the load on your database servers.
 
 Many of the popular bytecode caching solutions let you cache custom data as well, so there's even more reason to take
@@ -27,12 +27,16 @@ Example logic using APC:
 
 {% highlight php %}
 <?php
+// check if there is data saved as 'expensive_data' in cache
 $data = apc_fetch('expensive_data');
 if (!$data)
 {
+        // data not in cache, do expensive call and save for later use
 	$data = get_expensive_data();
 	apc_store('expensive_data', $data);
 }
+
+print_r($data);
 {% endhighlight %}
 
 Learn more about popular object caching systems: