Update README.md

Author: Salakar

README.md

@@ -7,27 +7,14 @@
 
 ## RediBox Memset
 
-Memset is a persistent, in memory and self updating cache tool. The main difference between Memset and [Cache](https://github.com/redibox/cache) is that Cache sets and returns data from specified triggers directly from Redis, whereas Memset consistently provides cached data from memory which is set via scheduled [Jobs](https://github.com/redibox/job).
+Memset is a persistent, in memory, self updating cache tool. The main difference between Memset and [Cache](https://github.com/redibox/cache) is that Cache sets and returns data from redis using specified triggers within your code, whereas Memset provides self updating cached data from memory which is accessible synchronously.
 
 ### When to use Memset
 
 You should consider using Memset when:
 
 - You have persistent data that doesn't need updating on demand
-- You always need certain data available quickly
-
-### Example
-
-#### Without Memset
-
-You have a large database of products that is cached on your server. When you add a new product, one user will trigger the purge of the cache by hitting the newly changed URL - that user will then be stuck with a loading message whilst the whole cache rebuilds, this could be anything upto and beyond a minute. By that time your user has already left the app.
-
-#### With Memset
-
-You have a large database of products that is stored using Memset. When you add a new product, the Job that checks for new changes will run at it's predetermined interval and add the new product to the Memset data, the user will then simply see a new product on their screen. There's no interuption for any of the users.
-
-Find out more about [Jobs](https://github.com/redibox/job).
-
+- You always need certain data available quickly and is used frequently
 
 ### Installation